New MR 30.4 beta firmware - RTP traffic forwarding fix and general improvements

[cmr]

Wireless firmware versions MR 30.4 changelog

Important note

• While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the "Help" > "Firewall Info" page is allowed through any firewalls or security devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs)
• WEP deprecation (https://documentation.meraki.com/MR/Encryption_and_Authentication/WEP_Deprecation_on_MRs)

Legacy product notice

• 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
• LAN packet capture fix (MR57, MR52)
• APs stop forwarding RTP traffic (MR45)

Known issues

• Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
• In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled

[NolanHerring]

Am I the only one still running 28.7 that isn't interested in going past that lol. It's stable, that's more important to me than any new features.

[RaphaelL]

Same here. 6K MR33,36 running MR28.7. We can't upgrade until Microsoft fixes the issues about sending 2 PMK. 😥

[NolanHerring]

Do you have a link you can share regarding that Microsoft issue?

[RaphaelL]

I didn't find any official post from microsoft but here is mine : https://community.meraki.com/t5/Wireless-LAN/Wireless-Invalid-MIC-EAPoL-4-way-handshake-is-failling/...

Got confirmation from Microsoft that they have already fixed it , but the KB is not public. ETA 2-8 months.

[Paccers]

Interesting, hadn't checked that thread in a while so good to know at least a root cause has been established. Definitely not linked to Intel driver version as well then?