No problem @Maccaa31 I am sure this would work for you, as worked for me Answering your question, the MPLS should go to the internet port(1 or 2) on both MX devices (look at the diagram).The MX devices will treat it as an internet link, as long as you are allowing the Meraki cloud IPs from the MPLS. Technically you would be cheating the MX devices to think this is an internet link. Do not forget to allow ICMPs to Google 8.8.8.8 ... View more

In addition, for any device that routes, not just Meraki, the longest matched prefix will always be used for a given decision. E.g. if you have a packet with destination of 192.168.1.1 and there's 2 routes in the routing table of 192.168.1.0/24 and 192.168.0.0/23 the /24 will be used to route the packets as it has a longer prefix (is more specific).  ... View more

I was having the exact same problem. The issue was that the SSID firewall was set to allow clients local lan access. When I denied local lan access, it was as though the DHCP request was forced over the VPN and therefore the routing was corrected. It started working straight away.     ... View more

Without visibility into Access Point A that could be hard to identify.  By its nature, a tunnel will hide a lot of that information.  On the MX600 side of things, they'll just see client A as a locally connected client with a lot of traffic.  To dive deeper into that client's local connection you'd for sure have to look into the network with Access Point 'A'.    But what is he ultimately trying to accomplish?  Can't he just use a policy to limit the traffic so he doesn't have to constantly investigate that kind of stuff? ... View more

Thanks Tyler,   We have a MPLS network. DHCP server is located in 1 of our DC's which is connected to the MPLS network via resilient 100Mb circuits.  At one of our 450 remote sites (all connected via MPLS with centalised breakout) I have deployed an MX65.  MPLS provided router peers with the PE via a /32 loopback interface, they then advertise a /24 via BGP for us to use on the LAN.    When I physically connect the MX65 via internet port 1 to a LAN port on the Cisco router it indeed picks up an IP address from our DHCP server. The issue I have is, that when I configure one of the Meraki LAN ports to be in the same vlan as the routable /24 the devices do not pick up a DHCP reply. Packet capture can see the request hitting the DHCP server and the response coming back, but it hits the MX and then goes nowhere. I'm aware I can use the MX to manage DHCP, however it's not the way we want to go (for now at least).    As an example I have the MX WAN IP as .209 with the LAN IP as .210 with the default gateway on the Cisco router as .220.   | have spoken to the support team, and they advise that there needs to be a different subnet between the MX and the Cisco router.  I was just curious as to why this is the case, if indeed it is true.    Many Thanks     ... View more