MR30.5 Changelog changes

RaphaelL
Kind of a big deal
Kind of a big deal

MR30.5 Changelog changes

Hi ,

 

MR30.5 went from beta to stable release candidate. 


The changelog were changed.

 

Old : 

 

Wireless firmware versions MR 30.5 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
  • WPA3 OWE AKM suite missing in beacons
  • Incomplete configurations when using VLAN profiles
  • Intermittent connectivity loss for Windows client devices
  • When using WPN, DHCP requests are missing option 55

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

 

New : 

 

Wireless firmware versions MR 30.5 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
  • When using VLAN profiles, APs may have failed to associate clients (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
  • WPA3 OWE AKM suite information was not included in AP beacons (Wi-Fi 5 Wave 2 APs)
  • When using L2 isolation, Windows clients may have experienced connectivity issues (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
  • When using WPN, DHCP requests did not include option 55 (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
  • In high capacity wireless networks, APs may have experienced instability when the “Band Steering” feature was enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)

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” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)
7 Replies 7
cmr
Kind of a big deal
Kind of a big deal

  • In high capacity wireless networks, APs may have experienced instability when the “Band Steering” feature was enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs)

Yay 🎉🎉😎

Paccers
Getting noticed

Yes I'm keen to see people's feedback on whether there is a noticeable improvement in the stability!

PhilipDAth
Kind of a big deal
Kind of a big deal

This is listed under "Known Issues" - so I would not expect there to be a change.

cmr
Kind of a big deal
Kind of a big deal

@PhilipDAth the instability when band steering is now marked as fixed, whereas instability when client balancing is enabled remains:

 

Screenshot_20231008_202521_Chrome~2.jpg

cmr
Kind of a big deal
Kind of a big deal

And we don't use client balancing 😎

Paccers
Getting noticed

Interesting they still have 3x stable versions with 30.5 moving to RC!

 

 

Paccers
Getting noticed

Noting that this has moved to Stable release for us today!

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels