MR may experience frequent reboots in networks where UNII-1 channels are not supported, such as Bangladesh, Bolivia, Guyana, Indonesia, Jamaica, Nigeria, Pakistan, Qatar, Tanzania (Wi-Fi 6 MRs)
Under certain conditions, successful WPA2-PSK connections are reported as failed under Wireless Health event logs (All MRs)
MR may experience intermittent Ethernet connectivity issues when negotiated at mGig speeds (Wi-Fi 6 MRs)
Scanning API v3 data intermittently did not provide data for some MR's in the network (All MRs)
When two clients had an established data flow between each other on the same MR & SSID, followed by one of the clients roaming away from the MR and then back to the original MR, packet loss was experienced (All MRs)
MR may send several RTS frames to clients who leave BSS without stateful 802.11 deauthentication or disassociation, resulting in packet loss for other clients in the BSS (Wi-Fi 5 MRs)
"Request failed" error shown when attempting to use the "Cycle port" live tool for MR30H LAN ports (MR30H)
MR may get into a state where it stops responding to 802.11 probe requests while still sending 802.11 beacons (MR45/MR55)
MAC addresses were getting altered, leading to MRs being unable to check-in to Dashboard (MR42/MR42E/MR52/MR53/MR53E/MR84)
If a client roamed away and then roamed back to the original MR within 5 minutes, the MR would disassociate the client (All MRs)
Beamforming interoperability issues with certain clients resulted in disconnections and/or poor performance (Wi-Fi 6 MRs)
AutoTX power may reduce too aggressively, potentially impacting connectivity for associated clients with low RSSI (All MRs)
General performance & stability improvements
Downstream VOIP RTP Packet Loss (MR42/MR42E/MR52/MR53/MR53E/MR84)
Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (All MRs)
It seems like Meraki is really anxious to get this update out the door. Unless I missed it (entirely possible), I think they skipped public beta and went straight to RC for this one. Also, they've already auto-scheduled it twice for us, even before moving it into the stable release bucket, and since I don't recall that ever happening before, I've cancelled it both times. Of course, RC is better than beta, but stable is better than RC, as we were bitten once in the past by a premature RC update. In any case, I'm running it on just one of our networks, with no problems seen so far, but I'm a little leery about pushing it out to the others before it's finally declared stable, especially if they did indeed skip the beta stage. The release notes do mention two jQuery related CVEs that are classified as "medium" severity, but that doesn't seem to be enough to warrant this level of urgency. Anyone have any commentary on what I might be missing in all of this?
@dfurasek with Meraki beta and RC are not the same as usual. New major versions go to beta, new minor versions go to RC.
As this is a new minor version it is therefore an RC release, as it fixes CVEs, WiFi6 AP performance issues with WiFi5 devices and the WPA Auth errors it went straight to being recommended. Once more than a certain percentage of networks are using it, it will become release.
You'll see the same for switches with 12.28 being release, 12.33 being RC and 14.12 being beta.
MXs have 14.53 as release and 15.42 as beta with no RC.
We are using 27.6 on all our networks and it has been much better than 27.5.1 so far.
I'll be using it at a brand new site that auto-loaded 27.5.1
If anyone remembers, even stable versions of code got pushed out that were horrible, like 25.14 if anyone remembers, and it took a good amount of complaining for Meraki to revoke it. My issue with that was they never let the customers who did upgrade know they should downgrade back to 25.13
Not a perfect world but still, communication is so easy to do.
Performance hop from 2 to 3 dots on my iOS and Mac devices on one of my AP.
Also roaming between 2 AP working not as expected. I use 802.11r adaptive since most of my devices came from Apple. I disable client balancing and relay on 802.11r and 802.11v but I don’t see 802.11k.
I use wpa2 enterprise network with Cisco Cloud authentication and since half year I see lots of disconnections. Only option is to disable and enable WiFi on clients. unfortunately Meraki support still can’t resolve this issue.
My devices are 2 MR33, mx67 an ms 220 8 port
when I using Ruckus or Extreme Network AP I don’t see this kind of problems
PS. Why Meraki Cloud don’t support WPA3 Enterprise?