I have discovered a bug that goes back to 3.19.3.0 firmware build. I have updated my hAP ac lite to NB-1366 and the issue still exists. When running a tunnel server, and I change the default DHCP lan server from 5 direct host to 13 or 29 direct host, my tunnel server will no longer connect to the enabled nodes.
Otherwise if the lan server DHCP is left at 5 direct host, (the default) the nodes that are enabled connect fine across the tunnel server.
I have uploaded a support file for the device.
Eric
Support File Attachment:
Eric
I recently changed my hAP-at-home node from 5 to 13 devices. Because I live in an AREDN desert, my only access to the AREDN world is via tunnel. I normally have at least seven tunnels running - five to eight as a server and two as a client. Changing the LAN size had no effect on the tunnels - other than a short drop for the required re-boot.. This change was about 2 weeks ago, and the node would have been running whatever was the current Nightly Build at that time.
This is the rule I'm seeing on your device:
-A zone_wan_prerouting -p tcp -m tcp --dport 5525 -m comment --comment "!fw3: @redirect[1]" -j DNAT --to-destination 10.5.10.97:5525
Joe AE6XE
Joe, I put that in there some time ago thinking that was needed to make the tunnel server work. I have removed the port in the firewall rules and it fixed the issue. This IP address (10.5.10.97) is the lan address of the tunnel server node (N7JYS-Russ-32-161-75-hAP) running only 5 direct host. I now see that address changes the more direct host I select. :) Thanks again for the help!!
Eric