I am troubleshooting a L2TP setup on my route 10. When I try to connect I get no response from the route10. As a test I ping’d the DDNS FQDN and get no response. The DDNS FQDN resolves correctly but I also tried to ping the actual IP address with no success. So I then connected to the CLI on the Route10 and did a tcpdump. I can see my pings hitting the route 10 but not being replied to. I can ping from the route10 but not to it.
Is there anything I need to setup in the firewall config to firstly permit ping responses and then allow L2TP connections ? In Settings - Firewall - Filter Allow ping is already there for all zones.
Got this working. I had to explicitly allow udp ports 500, 4500 and 1701 in the firewall filter area. Still can’t get the route 10 to respond to ping on the WAN interface even though there is an explicit rule to allow ping.
Even though I previously got this working I hadn’t used the L2TP VPN is some time. There have been no changes to my route 10 but I am now getting a message saying there has been no response to the attempt to setup the L2TP VPN.
The lack of easy troubleshooting options with the route 10 is beginning to cloud my opinion of this product. How would others normally troubleshoot issues like this?
Have you looked at the Logs (Bell icon→Logs→Search icon) while trying to connect? You should hopefully at least see the client try to reach out to your L2TP server.
If you send an email to support@alta.inc they can definitely help debug the issue. Usually it’s some sort of firewall rule that’s dropping the UDP frames.