Site-to-Site VPN Troubleshooting (2024)

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 devicesonlineand connected to the registry?
  • As outlined above, be sure to check theSecurity & SD-WAN > Monitor > VPN statuspage 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 toSecurity & SD-WAN > Configure > Site-to-site VPN. Under Local networks, make sure theUse VPNtoggle 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.
  • If using a full tunnel configuration, bear in mind thatwhen specifying a prefix to be part of a VPN, everything covered by that prefix will be allowed in the VPN. Therefore, subnets that overlap will causetraffic in amore specific subnet to be sent through the VPN, even if it is not configured to be included in the VPN. For example, if 10.0.0.0/16 is configured to be included in the VPN but 10.0.1.0/24 is not, traffic sourced from 10.0.1.50 will still be sent over the VPN.
• 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 theSecurity & SD-WAN > Configure > Site-to-site VPN > Organization-wide settingssection to see if there are any Site-to-site outbound firewall rules.
• Are there any problems reaching out to non-VPN peers?
  • Try sending pings or traceroutes to public IPs (such as 8.8.8.8) or access public websites to see if the problem isn't strictly related to VPN.
  • Try pinging the public IP of the other WAN Appliance 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 haveInternet access and are connected to the VPN registry.
• Are there routes configured on both sides that point to the remote subnets?
  • If the WAN Appliance is not the only gateway in the network (e.g. the WAN Appliance is connected to a layer 3 switch or router with its own directly connected networks), any devices that are not using the WAN Appliance as their gateway will need their traffic routed to the WAN Appliance 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 WAN Appliance's local IP address.
  • For extensive details on deploying the WAN Appliance 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 WAN Appliance 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 supported with non-Meraki VPN peers.

VPN status page reports an unfriendly NAT or disconnected from VPN Registry

If theSecurity & SD-WAN > Monitor > VPN statuspage for a given network reports either "NAT type: Unfriendly" or "VPN Registry: Disconnected", there is likely a device upstream of the WAN Appliance for that site that is preventing AutoVPN from working correctly.

• NAT type: Unfriendlyindicates that the upstream NAT won't allow the WAN Appliance to use UDP hole punching to form the tunnel. It is recommended to set NAT traversal to Manual: Port forwardingto bypass this issue.
• VPN Registry: Disconnectedindicates that the upstream device is not allowing the WAN Appliance to communicate with the VPN registry. It is recommended to configure any upstream firewalls to allow the traffic listed in Dashboard underHelp > Firewall info.

For more information on these two error messages and VPN registry troubleshooting in general, reference our documentation regardingTroubleshooting VPN Registration for Meraki AutoVPN.

Problems with VPN between Meraki MX/Z-seriesand 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, reference our documentation regarding Troubleshooting Non-Meraki Site-to-Site VPN Peers.