We are currently running Meraki side-by-side with another vendor's solution.  Networks in another data center are accessible by routing it to a next hop on each VLAN.  For example in the screenshot the 160 Main VLAN below we can reach those other networks via 10.10.51.1 and in the 163 Training WiFi VLAN we can reach those other networks via 172.27.51.2 just fine.     Here are some static routes entered in Addressing & VLANs currently.     This works fine for hosts on VLAN 160 but does not work for hosts on other VLANs.  If I change the Next hop IP for these three networks to be the gateway required for example for VLAN 163 (172.27.51.2) that VLAN can reach the remote network, but the other VLANs cannot.    What I would hope to see would be ability to set a per-VLAN static route with its own Next hop IP.  Any workarounds or someplace I am not looking?   I did find in the API a this endpoint https://developer.cisco.com/meraki/api-v1/create-network-appliance-static-route/ which allows you to specify a VLAN when creating a static route but when doing so it returns an error               ... View more