New answers tagged site-to-site-vpn
Ok, so I beliveve I figured it out. So even though my Openswan box is not behind a NAT, and has a direct NIC with a public IP I had to turn on NAT-Traversal. With this in mind I had to add leftsoureip=172.16.255.1 to tell Openswan what source address to use when communicating with the right side of the Tunnel. The last thing I had to do was to enable ...
Path MTU discovery was on but the MX60W device did not set it's MTU appropriately. Call with Meraki support got the issue resolved after ruling out client side issues.
I've found out what was the problem. I've set the static routes properly on the VPN server, but what I didn't realize is that I also have to set static routes on all the on premises machines which VPN Azure clients try to reach. The reason is that packets are properly routed to the on premises machines, but those same machines do not know where to send ...
Problem I actually used to support these routers a few years ago working for Cisco. Your main problem lies in that the WRVS4400N only supports site to site IPSEC tunnels. Windows VPN and port 1723 is PPTP, which is completely different. WRVS4400N and other small business class routers (specifically the rebranded Linksys routers) only support client-to-site ...
Top 50 recent answers are included