A lot of fixes in this one... who's going first?     Security appliance firmware versions MX 18.210 changelog Important notice 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 MX 18.208 regression that resulted in the firewall logging live tool stopping unexpectedly on MX75, MX85, MX95, MX105, MX250, and MX450 appliances. Fixed an MX 18.2 regression that resulted in vMX appliances improperly showing references to a WAN2 interface on the Appliance Status page. Corrected an MX 18.1 regression that could result in MX95, MX105, MX250, and MX450 appliances improperly duplicating multicast packets. Resolved an MX 18.1 regression that resulted in MX95 and MX250 appliances failing to send CDP or LLDP messages. Fixed an MX 18.2 regression that could result in traffic not being properly routed for clients when No-NAT was configured. Corrected a rare issue that could cause Event Log messages to be lost while the MX appliance was applying configuration updates. Corrected a rare issue that could result in MX75, MX85, MX95, MX105, MX250, and MX450 appliances failing to forward traffic from some clients. Fixed an MX 18.2 regression that resulted in MX75, MX85, MX95, MX105, MX250, and MX450 appliances inconsistently forwarding traffic to clients with a 1:1 NAT rule configured. Resolved an MX 18.2 regression that could result in ThousandEye’s Path Visualization failing for traffic routed over AutoVPN on MX75, MX85, MX95, MX105, MX250, and MX450 appliances. Fixed an MX 18.2 regression that resulted in MX appliance improperly dropping traffic from non-Meraki VPN peers when that traffic was received over a PPPoE uplink. Fixed a rare case that could result in non-Meraki VPN tunnels failing to form. Stability improvements for MX75, MX85, MX95, MX105, MX250, and MX450 appliances. Corrected an MX 18.2 regression that caused MX appliances configured in passthrough mode to be unable to establish VPN tunnels to tunneled SSIDs configured on MR devices. Corrected an issue that could result in MX75, MX85, MX95, MX105, MX250, and MX450 appliances configured in VPN concentrator mode failing to forward traffic received from AutoVPN clients. Fixed an issue that could result in MX250 and MX450 appliances improperly forwarding LLDP and BPDU frames from LAN out the WAN interface(s) during the bootup process. Corrected an issue that could result in MX65(W), MX67(C,W), MX68(W,CW), MX75, and MX85 appliances losing static IP configuration after entering into failsafe mode. Resolved a rare issue that could result in HTTP file downloads failing when AMP was enabled. Stability improvements for MX67W and MX68(W,CW) appliances. Corrected an MX 18.1 regression that resulted in VPN status information about WAN2 not being properly reported. This resulted in the information on the VPN status page being incorrect. Corrected an MX 18.107.7 regression that could cause MX appliances that 1) have Mandatory DHCP enabled and 2) are rebooted to encounter severe disruptions to network traffic. Fixed a rare issue that could occur during firmware updates that resulted in MX appliances unexpectedly having configurations that were out of date. Resolved an MX 18.2 regression that resulted in MX appliances not honoring flow preferences for Internet traffic when the preferred uplink was cellular. Devices operating under the SD-WAN+ license were not affected. Stability improvements for MX75, MX85, MX95, MX105, MX250, and MX450 appliances. 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.9. 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 MX appliances that have configured adaptive policy may encounter frequent connectivity state changes for AutoVPN tunnels. Devices manufactured by Ingenico may experience an unstable physical Ethernet connection when directly connected to MX68(W,CW) appliances. Due to rare issues, MX250 and 450 appliances may encounter unexpected device reboots. The Non-Meraki VPN service may fail to properly establish IKEv2 tunnels when the MX appliance is acting as the IKEv2 responder and many allowed subnets are configured. In rare cases, MX67C, MX68CW, and Z3C appliances may fail to enter into a "Ready" state despite being able to register to a cellular network and obtain an IP address for the modem. Due to an issue with no known method of reproduction, the IDS and IPS process may unexpectedly restart. Due to an MX 18.2 regression, MX75, MX85, MX95, MX105, MX250, and MX450 appliances will fail to form AutoVPN tunnels with other MX appliances via their LAN interfaces. Other Added support for reporting CellID on the local status page for Z4C appliances. Added support for configuring PPPoE uplinks without a password on the device local status page. Added improved input validation on the device local status page when configuring the gateway IP address for WAN interfaces. ... View more