We currently have a setup where our remote sites are coming into the Meraki 10.100.116.13 via the S2S tunnels. We also have an ASA firewall 10.100.116.5 on the same subnet. The problem is with our servers. We have 2 ingress points for each server: Traffic egressing from sites using the Meraki VPN Traffic leveraging the current Default Gateway for the environment which is the Cisco ASA In order for the traffic to route correctly back to the Meraki Sites, static routes are required on each of the servers in the environment that will require the return routes to those sites through the Meraki MX. Adding the routes can be made on any new server deployment to ensure that availability is always available to those Meraki VPN Sites. Whilst this may work for several servers, its not manageable long term. At the moment we are seeing traffic come into the Meraki > Server > ASA and then dropped as the ASA does not know where the traffic originated (without static route on server) We would like to route traffic from a test server and at a later date the entire server subnet from the Meraki > ASA > Server > ASA > Meraki. To do this I believe we will need a static route on the Meraki... I have attached an image to show the end goal we require.       When applying the static route I am getting the error below               ... View more