MR unable to properly detect Meraki Smart Antennas (MR46E)
DFS radar detection was overly sensitive (MR30H/MR33/MR70/MR74)
MR would not send traffic to a client that did not first send a packet after receiving an IP address (MR36/MR46/MR46E/MR56/MR76/MR86)
VLAN tag received via RADIUS response was not being correctly applied. (MR36/46/56)
WPA3 transition mode SSID did not allow for client to associate if the client did not support PMF (MR36/MR46/MR56)
MR may get into a state where it broadcasts a "meraki-<MAC ADDR>" SSID rather than the configured SSID, despite having connectivity to Gateway and Dashboard (MR45/MR55)
RADIUS test on Dashboard would fail due to invalid internal parameters on the MR (MR36/MR46/MR56)
Upon receiving an ARP broadcast on the wire, the MR would eventually transmit an ARP with the destination MAC matching that of the client that originally sent the ARP broadcast. This would result in some clients detecting duplicate IP addresses, requesting new addresses, and potentially exhausting DHCP scopes. (MR45/55)
MR would send control frames at OFDM rates to clients that did not support OFDM rates (All MRs)
MR was sending HTTP Redirect packets over the wired interface, rather than back to the wireless client, when layer 7 firewall rules and VLAN tagging were enabled on the SSID. (All MRs)
Scanning radio was not properly parsing DFS channels, resulting in adverse AutoRF behavior (MR36/MR46/MR56)
Meshed MR’s encountered issues with Block ACK negotiation, leading to reduced throughput (802.11ac Wave 2 MRs)
MR would get into a state where it would cease being able to TX frames reliably in environments with sustained high channel utilization (802.11ac Wave 2 MRs)
RSSI value for SSIDs seen by the MR was invalid (MR45/MR55)
General stability and security improvements
Known issues
Downstream VOIP RTP Packet Loss (MR42/MR42E/MR52/MR53/MR53E/MR84)
Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (All MRs)
Reduced aggregate upload throughput on 2.4GHz radio for Windows clients (802.11ax MRs)
EAPOL Key 3 is not sent from AP in the CE regulatory domain to 802.11b/g clients on PSK SSIDs (802.11ax MRs)
If my answer solves your problem please click Accept as Solution so others can benefit from it.
