Dear all, I'm currently using the following simple setup for my network - which works well as expected; with the MX64 WAN configured to get its IP address dynamically via DHCP from the WAN uplink MX64 <- ethernet -> ISP router [Update] On the WAN, the MX gets its address/dns dynamically from the uplink The MX runs a DHCP server for its clients: subnet 192.168.1.0/24 (MX interface 192.168.1.1) There are no VLANs configured [/Update] I need to insert a Cisco 881 router that performs various QoS and VPN functions that the MX cannot do. [Update] The 881 runs a DHCP server for its clients with subnet 10.0.2.0 255.255.255.0, and provides DNS servers from uplink [/Update] MX64 <-ethernet-> Cisco 881 <-ethernet-> ISP router In this new setup the MX64 isn't connecting to the Meraki Cloud and local clients cannot reach the internet. When I connect locally on the MX64 (web browser to 192.168.1.1), I see the MX isn't getting IP/DNS from uplink: Ethernet: This security appliance is trying to join a network or find a working ethernet connection Internet:This security appliance is not connected to the Internet Internet: This security appliance does not have a working DNS server When trying to connect other devices than the MX64 in the new setup, everything works well as planned (tried 2 PCs) <-ethernet-> 881 <-ethernet-> ISP router In this last setup (just replacing the MX64 by a laptop), everything works well. The team who configured the 881 is telling me thousands of other users have this config and it works well. As the Meraki MX64 is not connected to the cloud, I can only see locally (on the local 192.168.1.1 interface in a browser) that the MX64 didn't receive an IP address from the WAN uplink. My questions are 1) Under what circumstances would an MX64 not receive or accept IP addresses dynamically from the uplink ? 2) How could I further troubleshoot ? Thanks! Karim.
... View more