The beta firmware seems to have corrected this issue. However, it is still loaded with beta firmware. I am expecting a new release at some point.  ... View more

More of the same DHCP issue. Contacted support again, I must be a regular by now.  They did not require me to reproduce this issue.  In this case it was just a single SSID.  Strangely, if I connect to that SSID from another location in the same building (different AP) it works, and then I roam to this unit and it continues to work.  If however you happen to be in this space, no DHCP address is received.  I will continue to post here until I see some kind of release notes indicating the problem exists and has been fixed.   ... View more

Another new AP another issue, same as above. Devices may or may not get an assigned address. Received a new RMA'd AP replacement. Decided to do a burn in test to confirm it is working.  Approximately 24 hours after the burn in test began, devices started to display a 0.0.0.0 address.  Some would stay connected and not lose their address yet others would toggle between all zeros and a valid IP address.  Contacted Meraki support Cisco MerakiCase 13503579. They confirmed the issue and loaded a beta version of firmware on this single AP. Still in test now.  So far it is NOT exhibiting the same issue, however it hasn't been long enough to make sure this doesn't happen again.  ... View more

Again, three new MR46's are all doing the same thing. Has been confirmed with a packet capture by Meraki support. "Cisco MerakiCase 13456279: MR 46 not forwarding DHCP to client" The ISP router does reply with an offer of an IP address, but it is never delivered to the client.  The most frustrating part of this is we have had eight of twenty five MR46's have been RMA'd.  Still no acknowledgment that this is a bug with a specific version of firmware. However I am here to tell you we have been living with this issue since rollout on 7/18/25.  ... View more

Update - one of the MR46's that was working normally started to display the same symptoms.  You see a client with a 0.0.0.0 address, which by itself is not unusual.  However after the next refresh cycle the device is no longer visible. It never receives a DHCP address and then usually it is not on the next refresh.  Also the number of clients varies wildly from 7 to 38 and then back to 15, or whatever. Totally inaccurate and changes on every refresh.  I reopened the ticket and let support capture traces, however they were apparently stumped too.  Replacing the AP resolved the issue but I am wondering if anyone else has seen this type of issue.  ... View more

Thanks for the Layer 3 roaming tip.  Makes alot of sense.  ... View more

Thanks for all the great input. Discovered we had missed a few vlan settings on distribution switches.  Since then, all AP's are reporting normally.   ... View more

Thanks we will be doing that next. We have an open ticket too.  ... View more

Authentication is WPA Pre shared key.  The most basic auth that will support our users easily.   ... View more

DHCP is coming from a Cisco Catalyst switch which is doing ALL of our dhcp wired and wireless.  Sometimes we can get this device to work by moving to another AP. We still have a 2504 WLAN controller and seven 3802 AP's, when we move the device within range of that system it connects flawlessly.  ... View more