MX with a 0.0.0.0/0 Static Route

Solved
dmbooth
Getting noticed

MX with a 0.0.0.0/0 Static Route

Hi. Could I check some MX device routing logic please? If an MX in Routed mode, with a WAN1 uplink configured with a public IP address and a gateway as normal, is it possible to configure a 0.0.0.0/0 Static Route on Configure > Addressing & VLANs page to redirect any client traffic to a different gateway, will the MX still send it's own connection traffic to dashboard directly out via the WAN1 uplink? I also presume a non-Meraki S2S VPN tunnel will continue to work as the routing entry for the tunnel's remote subnets will be more specific? Thanks.

1 Accepted Solution
alemabrahao
Kind of a big deal
Kind of a big deal

No, the MX will still send its own dashboard and control plane traffic over the WAN connection, even if you add a default LAN-side route in Addressing and VLANs.

Static routes configured in Addressing and VLANs only apply to LAN traffic. They do not influence management traffic generated by the MX.

Therefore, you can safely create a static route 0.0.0.0/0 pointing to an internal next hop to direct client traffic elsewhere, the MX itself will still use WAN1 for dashboard connectivity.

 

MX Routing Behavior - Cisco Meraki Documentation

 

But be aware that you may receive a network overlap message.

 

 

 

 

Captura de tela 2026-03-02 124023.png

 

 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

View solution in original post

2 Replies 2
alemabrahao
Kind of a big deal
Kind of a big deal

No, the MX will still send its own dashboard and control plane traffic over the WAN connection, even if you add a default LAN-side route in Addressing and VLANs.

Static routes configured in Addressing and VLANs only apply to LAN traffic. They do not influence management traffic generated by the MX.

Therefore, you can safely create a static route 0.0.0.0/0 pointing to an internal next hop to direct client traffic elsewhere, the MX itself will still use WAN1 for dashboard connectivity.

 

MX Routing Behavior - Cisco Meraki Documentation

 

But be aware that you may receive a network overlap message.

 

 

 

 

Captura de tela 2026-03-02 124023.png

 

 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
dmbooth
Getting noticed

Perfect @alemabrahao thank you for confirming

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels