Meraki Site-to-site VPN makes it easy to connect remote networks and share network resources. In the event that VPN fails or network resources are inaccessible, there are several places to look in Dashboard to quickly resolve most problems. This article will overview common site-to-site VPN issues and recommended troubleshooting steps.
If there appears to be an issue with VPN, it is recommended to first check the Security Appliance > Monitor > VPN Status page to check the health of the appliance's connection to the VPN registry and the other peers. If one specific tunnel is having issues, it may be helpful to check the status page for the networks of each peer in case one of them is offline or disconnected from the registry:
The following sections outline common issues with site-to-site VPN and recommended troubleshooting steps:
Can't ping or access network resources on the other network
If you are unable to connect to devices on the other network from your site:
- Are both devices are online and connected to the registry?
- As outlined above, be sure to check the Security Appliance > Monitor > VPN Status page for each side's Dashboard network.
- Is the subnet you're trying to reach advertised over VPN?
- On the remote side's Dashboard network, navigate to Security Appliance > Configure > Site-to-site VPN. Under Local networks, make sure the Use VPN toggle is set to Yes for the subnet you're trying to reach. You should also check these settings on your local site's Dashboard network to ensure that the subnet you're connecting from is also advertised.
- Are any firewalls blocking this traffic on the network?
- In addition to any non-Meraki firewalls on the network that may be blocking this traffic (including firewalls that may be enabled on the device you're trying to access), check the Security Appliance > Configure > Site-to-site VPN > Organization-wide settings section to see if there are any Site-to-site inbound or outbound firewall rules.
- Are there any problems reaching out to non-VPN peers?
- Try sending pings or traceroutes to public IPs (such as 184.108.40.206) or access public websites to see if the problem isn't strictly related to VPN.
- Try pinging the public IP of the other MX from your local network. If this fails but general internet connectivity appears to be fine, there is likely an upstream ISP routing issue that is preventing the two sites from communicating directly even though they both have internet access and are connected to the VPN registry.
- Are there routes configured on both sides that point to the remote subnets?
- If the MX is not the only gateway in the network (e.g. the MX is connected to a layer 3 switch or router with its own directly connected networks), any devices that are not using the MX as their gateway will need their traffic routed to the MX in order to send traffic across the VPN. Make sure any other routing devices on the network have a route that allows them to access the remote VPN subnets via the MX's local IP address.
- For extensive details on deploying the MX as a VPN concentrator, please refer to our VPN Concentrator Deployment Guide.
- Are these devices on non-overlapping subnets?
- If the device on each end is on a subnet that overlaps with the other side, the MX will be unable to route traffic to the other side as it will believe the traffic is destined for the local network. It is recommended to have unique subnets with no overlap on each network connected to the VPN.
- If identical networks are required on each side of a tunnel, you may need to enable VPN Subnet Translation. Please note that this feature does not allow for partial overlap between subnets, and is not currently supported with non-Meraki VPN peers.
VPN status page reports an unfriendly NAT or disconnected from VPN Registry
If the Security Appliance > Monitor > VPN Status page for a given network reports either "NAT type: Unfriendly" or "VPN Registry: Disconnected", there is likely a device upstream of the MX for that site that is preventing AutoVPN from working correctly.
- NAT type: Unfriendly indicates that the upstream NAT won't allow the MX to use UDP hole punching to form the tunnel. It is recommended to set NAT Traversal to Manual Port Forwarding to bypass this issue.
- VPN Registry: Disconnected indicates that the upstream device is not allowing the MX to communicate with the VPN registry. It is recommended to configure any upstream firewalls to allow the traffic listed in Dashboard under Help > Firewall Info.
For more information on these two error messages and VPN registry troubleshooting in general, please reference our documentation regarding Troubleshooting VPN Registration for Meraki Auto-VPN.
Problems with VPN between Meraki MX/Z1 and a non-Meraki peer
If you are having issues with a non-Meraki VPN connection and the above troubleshooting tips did not resolve the issue, please reference our documentation regarding Troubleshooting Non-Meraki Site-to-Site VPN Peers.