Tried installing 3.16.01b on a Nanostation M2 that has been tunneled.
-Since installing the firmware, I cannot:
- ping, ssh or scp any nodes on the other side of the tunnel.
- I am not able to ping a node by it's name or IP, however I can connect to it via web-browser gui.
- I am able to ping other nodes on the same side of the node that is either client or server.
- If logging into a node that is RF connected to the tunneled node, I CAN ping, ssh and scp from any other node except from the node serving the tunnels.
All of the same tests have been performed using different hardware types.
Tested on both sides of the tunnel.
Both Server and Client nodes with the WAN connection experience the same issues.
Reverting back to 3.15.01 on the NanoStation, everything returns to working properly.
Purchases the AirRouter HP and it has exactly the same issues as other nodes running the same firmware and is tunneled.
This does not appear to be hardware dependant.
This appears to be a Firewall / permisison setting.
Anyone have any idea's what to try or how to correct ?
N4LDR
thx
Here are the Support Dumps from each end of the Tunnel.
Both are AirRouter HP.
And the file for the other end of the tunnel
Can you please re-upload them? This sounds like exactly what we need to look deeper since it is from both sides of the tunnel.
Forgot to click the Include file in display box.
The files show up in my post now.
Andre, K6AH
I think I am seeing this issue as well.
Is there a workaround I can apply on the box?
I tried to debug it for a bit, but I could not determine if it is routing or an iptables issue.
Thanks,
Ludovico
My house has a node in NAT mode with the WAN enabled, grabbing a VLAN address from the router. The other location I saw this at was with the most recent release and has the WAN disabled and is using the NAT side gateway. The VPN connects fine, and I can see his node on the network just fine, but he cannot access anything on the tunnel side.