Has anyone tested this? It's not working for me.
I have a spoke site with the default route box checked, so all traffic goes back to the main head-end. I also have a 0.0.0.0/0 route advertised from the hub to the spoke sites.
I added ANY 1.1.1.1/32. If I try to ping from the spoke site Meraki (vlan, default, or internet) it does not work. Doing a trace from a device connected to the Meraki shows it's still following default route.
Do we know if routes advertised from the main hub have a higher priority than the VPN exclusion?
![Aaron_Wilson_2-1596486832424.png Aaron_Wilson_2-1596486832424.png](https://community.meraki.com/t5/image/serverpage/image-id/14455i5458FF3F32815910/image-size/medium?v=v2&px=400)
![Aaron_Wilson_0-1596486733465.png Aaron_Wilson_0-1596486733465.png](https://community.meraki.com/t5/image/serverpage/image-id/14453i63FA53B97317A749/image-size/medium?v=v2&px=400)
![Aaron_Wilson_1-1596486783585.png Aaron_Wilson_1-1596486783585.png](https://community.meraki.com/t5/image/serverpage/image-id/14454i376F32883E3D1696/image-size/medium?v=v2&px=400)
Now, if I use trace route on the Meraki this uses ONLY the WAN interface rule and bypasses all settings/rules/routes. Works just fine, but this is expected.
![Aaron_Wilson_3-1596486981688.png Aaron_Wilson_3-1596486981688.png](https://community.meraki.com/t5/image/serverpage/image-id/14456iE1C1D36932EA99C7/image-size/medium?v=v2&px=400)