When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3
Bug fixes
General stability and performance improvements
AP sends RADIUS traffic out of the primary management interface when the alternate management interface is enabled
AutoRF channel auto-updates not occurring on MR20 APs
Failure of DNS test results in no connectivity
MR36 APs fail to auto-negotiate link with 100Mbps cable
L3 Roaming tagging client traffic with non-existent VLAN ID
VAPs incorrectly configured as NAT mode
Apple devices can’t connect to APs using SSIDs set for WPA3 and 802.11r (Wi-Fi 5 Wave 2)
Reduced throughput on Wi-Fi 6 APs
APs experience poor performance after extensive uptime (Wi-Fi 6 APs)
In high-capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
Suspected false positive DFS alerts
APs fail to receive RadSec certificates
APs not broadcasting beacon frames for Site Survey SSID on 6GHz
Security fixes
Upgraded lighttpd to v1.4.67
Known issues
Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
If my answer solves your problem please click Accept as Solution so others can benefit from it.
Does the beta version 31.1.1 contain all of these fixes/new features found in this stable release candidate version 30.7 ?... as the release notes show much fewer fixes in the 31.1.1...
Still no listed fix for the MR36H panic that causes it to reboot multiple times per hour. Disappointing, we may have to roll back to our MR30H units if it isn't fixed soon.
My customer site is running 30.6 firmware on several dozens of MR36. I found that client count under Monitor>AP>Performance page from multiple AP, it showed more than 30 clients vary up and down on a Saturday in an office. But there is no client at all from the Summary page of that particular APs. The wifi network had just launched for less than 2 months from new purchase. I already found there were more wrong showing of statistics in other areas. Opened TAC cases for days and no one know how to fix it. I am very frustrated by these non-sense statistics. Can 30.7 firmware fix that issue?
Adding 6 GHz Radio support for additional countries
Bug fixes
General stability and performance improvements
AP sends RADIUS traffic out of the primary management interface when the alternate management interface is enabled
AutoRF channel auto-updates not occurring on MR20 APs
Failure of DNS test results in no connectivity
MR36 APs fail to auto-negotiate link with 100Mbps cable
L3 Roaming tagging client traffic with non-existent VLAN ID
VAPs incorrectly configured as NAT mode
Apple devices can’t connect to APs using SSIDs set for WPA3 and 802.11r (Wi-Fi 5 Wave 2)
Reduced throughput on Wi-Fi 6 APs
APs experience poor performance after extensive uptime (Wi-Fi 6 APs)
In high-capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
Suspected false positive DFS alerts
APs fail to receive RadSec certificates
APs not broadcasting beacon frames for Site Survey SSID on 6GHz
FastCGI unresponsive
Security fixes] upgraded lighttpd to v1.4.67 [cve-2022-41556
Known issues
Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
After upgrade clients fail to connect to an Open with RADIUS SSID. Clients are setup to use MAC-based authentication to a cloud RADIUS service. Clients are unable to connect to the SSID.
Workaround is to disable Client Load Balancing in the Network Template in Wireless > Radio Settings > Basic Indoor Profile > Edit.
Clients instantly connected to the SSID with the issue as soon as I turned off Client Load Balancing in the network template.
I have a problem with the Meraki MR33 that were updated to version 30.7, an SSID with PSK access (WPA1 and WPA2) marks the network as full on the clients when they try to sign, but on the MR16 models with version 26.8.3 they enter without problem, I even changed the password and the same thing continues to happen, they enter the SSID through the MR16 but not through the MR33 and the MR33 was updated in mid-September and I cannot downgrade.
The problem I have with this version is connecting to any SSID passed 8. I have 10 configured and the clients would not connect to it but do see it. I renamed it to old and configured said-8 to that one and they are connecting fine. Some of my networks are still 29.5 and they are fine. 30.7 does not like more than 8 SSIDs it seems.
I looked and it is not enabled. Actually if I don't use radius on the networks above slot 8, they seem to work. I only have two networks with 30.7, I was able to roll back the rest.
The error that appears on cell phone clients is that the network is full and on laptops it simply does not connect to the MR33 access points and the MR16 connects correctly
As you'll be aware, the MR16 isn't running 30.7, for the network with the MR33 in, are they the first four SSIDs, or spread out amongst the 15 possible?
If my answer solves your problem please click Accept as Solution so others can benefit from it.
It doesn't make sense to me, but I moved the SSID from right to left, leaving the SSIDs active at the beginning. With this, the SSID that didn't work on the MR33 worked. Thank you very much for the help, I appreciate it infinitely.
Still having issues with 30.7 on the MR56 access points so going to roll back the firmware to 30.6 to confirm the current stable firmware has performance issues
