Hello, We are trying to accomplish a scenario with a private connection/MPLS to a remote subnet where a server resides. However, we have failed to make it work. The MPLS connection in the service provider network utilizes public ip addresses (but the network has no route to the internet). Uplink 1: Internet Connectivity Uplink2 OR a VLAN interface: MPLS/Private connection to a service provider network with public IP-addresses. In this network a server should be reachable for the clients. Tested Methods: Method 1# Configured the connection on UPLINK2 + added static route for the remote subnet. We have tried to configure this WAN connection as second uplink. In this method we are unable to send any traffic or ping through the network. Our idea is that this is caused by MX behavior (the MX is unable to have an uplink without Internet access? ) according to this link https://community.meraki.com/t5/Security-SD-WAN/Flow-Preference-to-a-non-internet-WAN-port/td-p/57638 Method 2# Configured the network on a new VLAN interface + added static route Therefore we have also tried to configure the connection as a local subnet/VLAN interface and created a static route. In this scenario we are able to ping from the MX firewall to the remote server / network. The clients are however not able to ping the remote network. This is probably because we are unable to configure a NAT setting that allows traffic from LAN to the remote network to be NATed. The configuration is similar to this article Integrating an MPLS Connection on the MX LAN - Cisco Meraki , however, since the private connection utilizes public IP-adresses, we also need to apply NAT. Is this supported on a local subnet , if so how do we configure it? Question: Is the above scenario supported? Can we disable the MX wan behavior that disables traffic on Uplink 2 if the MX can't ping the internet through the uplink? If we utilize method 2 , how do we configure NAT on a local subnet (in other words for traffic not exiting through an uplink interface).
... View more
