Hey folks, This might help only small % of cases but the same error: Client made a request to the DHCP server, but it did not respond. type='NO DHCP response' associated='true' radio='0' vap='0' The MX was removed, there was a modem swap and techs suspected new modem (GW Mode) being an issue. Rebooting did not resolve the issue, firmware wasn't upgraded but upon checking this was naturally related to VLAN Tagging. Everything works fine on simply disabling that, in these type of change scenarios. _________ Check from: Configuration overview SSIDs VLAN tag This column refers to VLANs set in Bridge or L3 roaming. For info about VLANs used for VPN, see the VPN column below. Then Go to: Access control Scroll down to: Client IP and VLAN Disable VLAN tagging (VLAN tagging is used to direct traffic to specific VLANs. To use VLAN tagging, all Meraki APs functioning as gateways in this network must be connected to switches that support IEEE 802.1Q. The gateways must be connected to switch ports that are configured to accept 802.1Q tagged Ethernet frames (such ports are sometimes called "trunk ports"). If you are unsure, don't enable this feature.) Hope this helps someone at least. 🙂
... View more