- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki Routing priority
Hi,
Current,
The environment is constructed with non-meraki vpn peer.
One non-meraki vpn peer sets the Private Subnet to 0.0.0.0/0.
When you check the routing, the priority is like this.
As a result, no routing to the ASA is performed,
Communication to ASA is also going to Palo Alto.
What is the priority for this?
Is this expected behavior?
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Based on your route table, if the destination IP matches the 192.168.X.0/24 network then the traffic should be routed to ASA. However, if it does not match and falls under the default route 0.0.0.0/0 then it will go to the Palo Alto because it has a higher priority than the default route over the WAN connection.
If you suspect that the traffic is not routing over the IPsec even if it matches the 192.168.X.0/24 destination subnet, then you may need to call Meraki support so they can check whether this is the case or not.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
