I think I experienced this issue first hand:
This happened as I came back to the office today from working from home since 1/25/23. My laptop was connected to an AP and had an IP address but could not ping the default gateway or traceroute out. I tried to turn off my wifi adapter but could not. I was able to put my adapter in sniffer mode as per the monitor mode packet capture instructions. After I ended the capture my laptop seemed to have even more issues. At one point all the adapters listed in System Preferences>Network disappeared and I had to reboot to recover. I was able to recover the .pcap and forwarded it to Meraki.
I am running macOS 12.6.2.
We have the same, we've started noticing it a lot due to change of our zero trust solution, when users 'lose' connectivity they see the disconnection pop up. I say lose, I've had it myself around 5 times today but we aren't seeing timeline showing disassociations in client timeline view, and the client itself doesn't show a disconnection (checked using netsh wlan show wlanreport.)
It would appear it's a loss of Layer2 and above, the radio is up but no data across it for a brief moment which is tearing things down. Here's my own laptop for past 24 hours where I've had multiple drops but as far as Meraki eventlog and timeline is concerned all is ok
We're around 99% confident rolling back to 28.X fixes on, on two smaller test networks, one with about 20 devices on firmware 29.5 on Monday had around 60 excess frame loss messages, but also a lot of "unspecified reason". Rolling back to 28.5.1 (for some reason 28.7 isn't available to us) that went to 3 for the entire day, which I guess will happen at times if users move far away from an AP with nothing to roam to
We've tried client balancing on and off, with it on we see very erratic roaming, my boss was on 4 different APs in about 30 minutes, bouncing between two of them constantly. At one point, physically his laptop had 4 APs in a line from him, and it was associating with the furthest away at around 150 foot, but there was one 20 feet from him. Around 250 clients in building with 24 APs, 16 of them in the office areas in that example
We have a mixture of models and site sizes, MR33, MR42, MR52 and MR44 (MR44 being the bulk) - 15 users, 30 users, 250 above, doesn't make a difference
We see the issue across the all sites and sizes, personally us (the internal IT) have the issue, all Windows devices, to be specific Dell Latitude 7300/10/20/30 and 5420. But we see it for MacOS devices, Intel and Apple models, iOS, Android and some static devices such as HDMI sticks running display boards
Planning to revert back Monday evening globally. Will update on what we experience in the few days afterwards, it will be pretty apparent to us if it fixes the loss of connectivity. Shame, the client balancing change in 29.X sounds nifty
wait how do you turn off client roaming? Do you mean client load balancing or client steering? To my understanding that the new version client balancing released with MR29.x is active.The new active client balancing technique has been introduced in MR 29.X firmware, where an AP would try to steer already associated 802.11v-capable clients to a better AP (if one is available) using BSS-TM frames.
When I read this I feel like this might be related to the issues we are seeing. So If I understand what you are saying is that you allow the clients to drop connections between floors and reassociate when they arrive on another floor. This makes me believe that you are doing a layer 2 roam between broadcast domains and might be turning off layer 3 roaming. I did the same because layer 3 roaming in Meraki is a complete waste of time.
