Tried a nightly build then went back to stable and now the clients are not connecting.
DSL modem ---> Edgerouter X (lan) --> (wan) node (hAP lite)
I can SSH in to the node and ping google.ca and internal IP's no problem.
Port is forwarded in er-x (5525 to 192.168.2.10 - WAN IP of node).
check my port - not connectable, try to telnet to port and not connectable (the packets/bytes in screenshot are of me trying to telnet in)
I've attached the support data.
Support File Attachment:
Orv W6BI
check my port - not connectable, try to telnet to port and not connectable
Did you try telnet using port 5525 or default port 23?
-----
Tried a nightly build then went back to stable and now the clients are not connecting.
Phrasing kinda indicates that tunnels worked in the nightly build. ?
You did reinstall the tunnels after loading the new firmware?
-----
Just wild guessing here, sorry.
Chuck
Did you try telnet using port 5525 or default port 23?
Port 5525 - why I'm seeing packets at the router/firewall.
Phrasing kinda indicates that tunnels worked in the nightly build. ?
It never did load (nightly) and I thought I may have bricked the unit - I had to do a fresh install of the stable build (using the elf file and VM linux)
You did reinstall the tunnels after loading the new firmware?
Yes re-installed - I have read that some times a 15 sec reset, then re-install the tunnel may work.
I do have it correct? - into the WAN port of the node from the LAN of router? No port forwarding I have to do on the node? I'm leaning towards a firewall issue at the node.
Thanks
WAN port of the node from the LAN of router? No port forwarding I have to do on the node? I'm leaning towards a firewall issue at the node.
Correct.
Router WAN (your ISP address) to Router LAN Port forward 5525 from Router LAN to hAP WAN (address is in the LAN range of Home Router).
No firewall issue at the hAP.
No port forwarding at the hAP because that is where the port 5525 packets terminate.
Outbound packets are returned to the router's LAN port on your Home Router.
NATing is then handled by your Home Router.
I sent you a personal note via the 'contact' service here at AREDN.
3s, Chuck
So bizarre
I did the 15 sec hard reset - re-installed the tunnel and set up the node as per normal. Still no connection on the node WAN port. So.....
I disabled the node WAN port, enabled NAT on the node LAN (disabled DHCP) - set the same IP 192.168.2.10 on the LAN interface (changed cable location to LAN) - didn't touch anything on the er-x.
guess what? I have connections via tun!
I'll have a read on what you sent me Chuck - thanks for your help. Still struggling to understand what is happening.
Congrats! :-)
Do you mean:
Advanced WAN Access
Allow others to use my WAN
Prevent LAN devices from accessing WAN
?
Normally, both those boxes should be unchecked (default).
I hope this helps,
Chuck
I still don't understand why it wasn't working on the node WAN port.
Oh, you are using 'LAN Mode: NAT' instead of '## host direct'.
Thanks for the image.
'Default' is '5 host direct' which should work.
Chuck