You are here

Odd problem with tunnel client

5 posts / 0 new
Last post
VA2XJM
Odd problem with tunnel client

Hi everyone,

Few days ago I configured a new hAP I had on the shelf. The tunnel client section has been to configured and tested to connect to another hAP. Everything was working properly at home including the tunnel client.

I shipped the hAP to a fellow amateur. It has been plugged this morning and it was acting up.

So once plugged, the hAP booted, WI-FI AP went up and after 30seconds, the hAP appears reboot (port #5 red led going up and then down). On the server hAP I can see the tunnel connection being established. The client hAP have mesh activated on 2Ghz and AP on 5Ghz, WAN on port 1, power through barrel plug with included adapter.

Not being able to access the GUI, both by WIFI or LAN locally, I disabled the tunnel server line corresponding to the problematic hAP on server side. It stopped the bootloop on the client side and the device was then responding. We confirmed over the phone the settings and everything is straight.

Boot hAP (server and client) are running 3.20.3.1 and vtun 3.0.3-2. The server hAP have 6 tunnels configured, 2 active and working, 1 active and standby and 3 disabled(including the faulty hAP).

Anyone is having an idea of what might be wrong ?

 

VA2XJM
Found something in the log

So in the log:
root@VA2XJM-Gateway:~/etc# logread | grep tun53
Fri Feb 12 19:47:35 2021 daemon.notice netifd: Interface 'tun53' is enabled
Fri Feb 12 19:47:35 2021 daemon.notice netifd: Network device 'tun53' link is up
Fri Feb 12 19:47:35 2021 daemon.notice netifd: Interface 'tun53' has link connectivity
Fri Feb 12 19:47:35 2021 daemon.notice netifd: Interface 'tun53' is setting up now
Fri Feb 12 19:47:35 2021 daemon.notice netifd: Interface 'tun53' is now up
Fri Feb 12 19:47:35 2021 daemon.info olsrd[26218]: Writing '0' (was 1) to /proc/sys/net/ipv4/conf/tun53/send_redirects
Fri Feb 12 19:47:35 2021 daemon.info olsrd[26218]: Writing '0' (was 0) to /proc/sys/net/ipv4/conf/tun53/rp_filter
Fri Feb 12 19:47:35 2021 daemon.info olsrd[26218]: Adding interface tun53
Fri Feb 12 19:47:35 2021 daemon.info olsrd_hotplug: [OK] ifup: 'tun53' => 'tun53'
Fri Feb 12 19:47:35 2021 daemon.debug olsrd_hotplug: [OK] interface 'tun53' => 'tun53' not used for olsrd
Fri Feb 12 19:48:44 2021 daemon.err vtund[27510]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:49:55 2021 daemon.err vtund[27710]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:51:05 2021 daemon.err vtund[27947]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:52:16 2021 daemon.err vtund[28173]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:53:28 2021 daemon.err vtund[28474]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:54:37 2021 daemon.err vtund[28746]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:55:49 2021 daemon.err vtund[28947]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:57:01 2021 daemon.err vtund[29174]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:58:11 2021 daemon.err vtund[29407]: Can't allocate tun device tun53. Resource busy(16)
Fri Feb 12 19:59:22 2021 daemon.err vtund[29612]: Can't allocate tun device tun53. Resource busy(16)

 

nc8q
nc8q's picture
Mikrotik RB952/hAP not booting when WAN connected

Try rebooting with the WAN cable disconnected.
 

VA2XJM
It does reboot with WAN

It does reboot with WAN connected without problem as long as the client can't connect to the server. As soon as the client can connect to the server, it starts the boot loop.

VA2XJM
FIX!

Ok, so I have found a fix. I've been able to replicate the problem with another device at home.

It seems that sometimes the installation of the tunnel packages seems to install a problematic package (maybe corrupted during download ? I download them straight from AREDN server at every try). To fix, I have "reset to first boot" and reinstalled the tunnel packages. I did the same process repeatedly to replicate the problem.

So now sending instructions step-by-step to my fellow amateur so he can try to fix it without me doing 90mins of road!

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer