Hi Crew, just a quick heads up that MR 25.11 was promoted from SRC to the latest stable firmware.
Change log notes:
@PhilipDAth There is a new "25.11" section here: https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation
Thanks, this helps me keep up on the updates.
Since the update (25.11) I'm experiencing frequent channel changes with both 2.4 and 5 on models MR 42 and MR66. Any help on this as clients are dropped for about 45 to 60 seconds when this happens.
Thanks for your help
@dmo What does Wireless Health show? Have you made any recent config changes?
I'd recommend starting a new thread instead of adding to this one.
That's almost the understatement of the year!
Please note that this ALSO applies to the 5Ghz radio on the MR34.
The PR-speak "lower than expected" should be updated to reflect reality- "almost unusable" is more approriate.
This is a big issue. May have to roll our entire school district back to 23. Causing lots of issues with state testing. Please come up with a fix soon.
I've been helping them test a beta firmware for the 2.4Ghz bandwidth issue (3Mb/s... really) and can confirm that they have fixed that issue in that firmware.
However, they broke the Staff SSID (password protected, relays to a Windows DHCP) where an access point will randomly not allow a client to get a valid IP address. They can switch the the Public SSID (open, Meraki DHCP) and function except for critical internal network functions. They can go to another room and connect fine on the Staff SSID. The only cure is a reboot of the affected AP. There is no rhyme or reason.
I think they were able to gather enough info due to my troubleshooting efforts. It wasn't until last Thursday that I was able to get them on the phone while it happened after school hours here. Hopefully this issue gets fixed very soon. So far this week I've been proactively rebooting every AP first thing in the morning and it seems to have helped. It's a PITA to reboot 50 WAPs though!
So far this week I've been proactively rebooting every AP first thing in the morning and it seems to have helped. It's a PITA to reboot 50 WAPs though!
Here's a thread on some ideas to reboot WAPs: https://community.meraki.com/t5/Solutions-APIs/API-Call-to-Reboot-AP/td-p/5863