So, I cannot change the ip scheme of 0.0.0.1/24. But what if I on a local level crave up the /24 into /30s and then point them to the Sophos. Like 0.0.0.1/32 pointing to 0.0.0.21. This way I do not break the scheme but separate the subnets.  ... View more

So, I am not in a position to change the way the network set up. ... View more

This is set through our ISP. We have all the Branches on the same MPLS network. For them to communicate they have to be on the same network to talk back and share information. The Branches all talk out of the same VLAN over MPLS to the Main site then go to the internet. Such at 0.0.0.2 talks to 0.0.0.1 or 0.0.0.4 to 0.0.0.1 then goes over the ELAN to the then go to the internet behind 0.0.0.1. ... View more

We tried that but the issue is the MPLS network is on the same VLAN. Ok the MX 0.0.0.2 is our firewall (Sophos) at the DATA center 0.0.0.1 over MPLS. We set up the LAN to do site to site VPN on for that network with the IP being 0.0.0.2. The Firewall we have at the Datacenter doesn't see the MX. The ISP also doesn't see the MX. We cannot set up a static route on the MX because it will not let me set up a static route on the same network. I then tried a source-based route. We still cannot talk to the Firewall at another location. It would then go to the internet from that Firewall. ... View more

We tried to set the static ip for the MX WAN but Meraki said that will not work. We then set up VLAN on the LAN. This also didn't work. Meraki told us that the WAN will not work with the MPLS. ... View more