A new beta appliance firmware version is available. Firmware MX 18.207 was just released on 2023-12-14 and has been in this firmware category since 2023-12-13.
USB modems with MX/Z series devices running firmware MX 18 or newer will be limited to best effort support and will not be receiving any future firmware fixes or improvements.
Bug fixes
Resolved an issue that resulted in Z4(C) appliances incorrectly advertising SSIDs that were configured as hidden.
Corrected a rare issue that could result in RADIUS authentication requests for AnyConnected VPN clients to fail after a long timeout occurs.
Fixed a data validation issue with PPPoE authentication on the device local status page that could result in devices getting into an invalid config state when invalid data was entered for the PPPoE username.
Fixed an MX 18.2 regression that resulted in control traffic generated by MX75, MX250, and MX450 appliances not being routed correctly when the destination was on the MX LAN.
Fixed an issue that would result in MX appliances indiscriminately responding to DNS requests received over AutoVPN and addressed to its management IP.
Resolved an issue that resulted in client VPN clients being unable to communicate properly if they were connected to an MX appliance configured to operate in passthrough mode.
Fixed a race condition that could result in the integrated cellular modem on Z3C, MX67C, and MX68CW devices getting stuck being unable to detect the SIM card.
Various cellular fixes to increase the reliability of integrated cellular modems.
Expanded the range of conditions that Z3C, MX67C, and MX68CW appliances can automatically recover from the integrated modem becoming unresponsive.
Corrected an issue that could result in MX appliances not failing over to a backup cellular connection after the WAN interfaces had been disabled from Dashboard.
Fixed an issue that resulted in some MX67(C,W) and MX68(W,CW) appliances experiencing difficulty upgrading to MX 18.2 from their factory default firmware.
Corrected an issue that prevented MX appliances from sending IPv6 traffic over Non-Meraki VPN tunnels.
Resolved a rare issue that could result in unexpected VRRP transitions when MX appliances were configured in high availability (HA) and content filtering was enabled.
Fixed an issue that could result in a device reboot when content filtering was enabled.
Corrected an MX 18.2 regression that could result in MX appliances running in passthrough mode and configured in high availability (HA) to crash.
Resolved an issue that resulted in active-mode FTP connections failing on MX75, MX250, and MX450 appliances.
Fixed an issue that could result in AnyConnect VPN clients not receiving DNS responses on MX75, MX250, and MX450 appliances when Umbrella integration was configured.
Corrected an MX 18.2 regression that could result in worse AutoVPN scalability with AutoVPN peers running MX 17 or older firmware versions.
Corrected a case that could result in the AnyConnect process crashing.
Resolved an MX 18.2 regression that caused MX75, MX85, MX95, and MX105 appliances to have significantly increased device utilization.
Fixed an issue that resulted in the AnyConnect VPN client appearing to hang for 2 minutes if the user hit cancel on the login page of the client.
Resolved an issue that resulted in uplink shaping not limiting traffic speeds on MX250, MX450, and MX75 appliances.
Corrected an issue that could result in devices connected to MX68(W,CW) and MX85 appliances being unable to negotiate 802.3at power levels from PoE.
Fixed an issue that could result in pings to fail using the cellular interface when WAN1 was the active uplink.
Corrected an issue that caused mandatory DHCP to not function correctly on MX250, MX450, and MX75 appliances.
Resolved an issue that resulted in MX250, MX450, and MX75 appliances not relaying DHCP traffic.
Fixed an issue that could result in IP addresses not being freed and returned to the lease pool when IPSec client VPN connections were terminated.
Fixed an issue that resulted in the AnyConnect VPN and IPSec client VPN services restarting when an MX appliance had a change to IPv6 uplink information, even when these services were not using or providing any IPv6 functionality.
Legacy products notice
When configured for this version, Z1 devices will run MX 14.56.
When configured for this version, MX400 and MX600 devices will run MX 16.16.9.
When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.6.
Known issues status
This list is being reviewed and updated. Many existing issue reports have not been confirmed to affect MX 18.2XX firmware versions.
Known issues
Due to an MX 18.2 regression, MX appliances summarize AutoVPN routes advertised through BGP without being configured to do so.
Due to issues under investigation, MX95 and MX105 appliances may see performance reductions ranging from 10-20% when compared to MX 18.205.
There is an increased risk of encountering device stability and performance issues on all platforms and across all configurations.
Other
Added support for configuring 10 Gbps full duplex from the local status page for WAN interfaces on MX85, MX95, and MX105 appliances.
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.
