Wireless firmware versions MR 29.1 changelog Important note Meraki APs use UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications when running MR 27 and older firmware. When running MR 28+ firmware, Meraki APs will now use TCP port 443 as the primary means for cloud connectivity. In order to maintain connectivity to the Meraki cloud on MR 28+ ensure that TCP port 443 is allowed to communicate with 209.206.48.0/20 on firewalls that are deployed upstream of your Meraki APs. (Wi-Fi 6 and Wi-Fi 6E APs) 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. New Wi-Fi Personal Network (WPN) support - https://documentation.meraki.com/MR/Encryption_and_Authentication/Wi-Fi_Personal_Network_(WPN) (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) Band Steering Enhancements - https://documentation.meraki.com/MR/Radio_Settings/Band_Steering (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) Client Balancing Enhancements - https://documentation.meraClient Balancing - Cisco Merakiki.com/MR/Other_Topics/Client_Balancing (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) Mesh Enhancements - https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Wireless_Mesh_Networking (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) IPv6 Enhancements - https://documentation.meraki.com/MR/Other_Topics/MR_29.X_Firmware_Release_-_Supported_IPv6_Features (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) Bug fixes General stability and performance improvements (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E MRs) AP intermittently stops redirecting HTTP Traffic to the Splash page prior to Splash page login (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) Enabling FIPS may cause issues with RADIUS authentication (Wi-Fi 6 APs) AP may stop publishing MQTT updates until rebooted (Wi-Fi 5 Wave 2 APs) When an Apple client enters an incorrect PSK the AP responds with a disassociation response instead of deauthentication response, resulting in multiple failed connection attempts from the client (Wi-Fi 5 Wave 2 APs) AP may experience DHCP failures on 2.4 GHz WPA2 Enterprise SSIDs (MR42) AP may not sync PMKs on WPA3 Enterprise SSIDs configured with OKC (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs) Client average latency values may be missing for some clients (Wi-Fi 6 APs) Meraki Auth does not work when an SSID is configured to Tunnel data to a concentrator (Wi-Fi 6 APs) AP configured with an iPSK and 802.11r SSID, without RADIUS, fails to apply policies when a client roams to a new AP (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) AP may reboot when detecting a very high number of DFS events (Wi-Fi 6 APs) Client capability may be incorrectly reported as 2.4 GHz only (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) Channel and channels widths not available in Indonesia regulatory domain (Wi-Fi 6 APs) Under certain conditions an AP may not respond to ICMP requests (pings) destined for its Management IP (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) AP may reboot when configured with more than 50 iPSK SSIDs (Wi-Fi 5 Wave 2 APs) AP running in dark mode may still have the ethernet port LED light on (Wi-Fi 6 APs) AP may not show all SSID spoof events in Dashboard (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) Multicast traffic received on wired interface may Not be forwarded to clients on LAN (MR30H) AP on channel 100/104 may show high channel utilization with no clients connected (Wi-Fi 5 Wave 2) MT sensors unable to connect to MR42E and MR53E Enable MT14 TVOC data to be sent via MQTT Known issues Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) No DHCP response error is seen after a client performs a successful L3 roam (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) AP performance may degrade over time (Wi-Fi 6 APs) AP may stop broadcasting beacons on WPA2 configured SSID (MR53E) AP may loose Cloud connectivity for an interval of time (Wi-Fi 6 APs) SES-imagotag ESL status may display as gray even when ESL is functioning normally (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
... View more