Meraki support recently came back to us with the following.  We will pass on this for now and wait for it to be fully tested but FYI out there to others who may not be able to afford to wait around.      Greetings, The product team reached out and mentioned they have recently received reports of issues of this nature occurring on 26.7. They have provided a test firmware that needs to be applied on the affected networks. As this test firmware cannot be scheduled, you would need to call in during a maintenance window (as your APs will reboot on the firmware upgrade) so that we can apply it for you while on the call. ... View more

Mesh was disabled on our site and we continued to see BAD_ADDRESS. ... View more

great point but we had tested "layer 3 roaming" - successful ... View more

Bridge mode with 802.11r did not work for us (legacy client issues). We have went back from 26.6.1 to 26.7 twice to prove the issue out ... View more

We did try option 2 to no avail. Rolling back firmware to 26.6.1 did resolve our BAD_ADDRESS issue on Windows Server. ... View more

Exactly... Here is what support told me.   It could potentially be due to layer 3 roaming being enabled as devices will hold on to their IP address while roaming. You could try one of 2 things: 1. Roll this network back to 26.6.1 and review the DHCP logs 2. Disable L3 roaming for the SSIDs on this network and review the logs.   It seems they know rollback fixes issue and should only be suggesting this and need to quite offering 26.7 as a "stable release candidate".   ... View more

@cmr   Yes, this BAD_ADDRESS.  We keep seeing the clients try consecutive IPs utilizing DHCP addresses so maxing out our scope.  We have to keep clearing them out but now have a script to do this for us so we do not get calls while we troubleshoot the issue.  ... View more

Wanted to join in here.  We are seeing similar situation at two locations with DHCP issues as well.    Overview Cisco 2960XR - Core Switch Microsoft Windows 2012 - DHCP Server Site1: MR42E/MR45 Site2: MR55s   We upgraded to 26.6.1 and had issues with barcode printers connecting on 2.4 at Site1.  When we upgraded to 27.7, this fixed that issue but seems to have introduced a new issue with DHCP BAD_ADDRESS.   We are seeing DHCP Logs fill up with this coming from multiple SSID's on different VLANs.   We have this happening at two sites and the common factor is Meraki 26.7. Site2 does not have barcode printers so we will test downgrading this site.   We have window tentatively scheduled for this weekend or early morning next week so I'll post another update once testing is completed.  Do not feel I'm getting much support on ticket opened with Meraki.         ... View more