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.
Stability improvements for MX75 appliances.
Corrected an issue that could result in AnyConnect client VPN clients from being unable to ping hosts on the MX WAN if the MX was configured in passthrough mode.
Fixed an issue that resulted in some AutoVPN subnets becoming unreachable when there were more than 4093 AutoVPN peers configured.
Resolved an issue that resulted in performance probes used for measuring AutoVPN path performance being sent too frequently.
Corrected an issue that resulted in wireless broadcast traffic being improperly routed on MX64W and MX65W appliances.
Fixed an issue that could result in CPU time being spent on wireless processes when no SSIDs were enabled on MX64W and MX65W appliances.
Resolved an issue that resulted in MX appliances configured in high availability using their WAN interface IP address for establishing EBGP sessions when a VIP was configured.
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.
Corrected an issue that resulted in MX95, MX105, MX250, and MX450 appliances not dropping untagged traffic when configured to do so.
Resolved an MX 18.1XX regression that resulted in peripheral devices, such as the USB port, not receiving the correct amount of power on MX65(W) 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.
After making some configuration changes on MX84 appliances, a brief period of packet loss may occur. This will affect all MX84 appliances on all MX firmware versions
Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page
MX appliances will now properly validate that DBD packets conform to the appropriate MTU size. If the MX's OSPF peer has an improper MTU configured, it may cause the OSPF adjacency to fail to properly form. The updated behavior properly conforms to RFC. Please ensure these settings are properly configured on any MX's OSPF peers to avoid disruption after upgrading to MX 18.1.X.
All MX 18.X firmware changelogs have been updated.
What is "new" :
AutoVPN tunnels may briefly drop and re-establish after configuration or WAN connectivity changes if 1) the MX is configured in high availability (HA) mode and 2) both AutoVPN peers are running MX 18. This issue is actively being investigated.
AutoVPN transmissions between peers which are running firmware versions 18.1 and later will consume an additional 4 bytes of overhead, totaling up to 68 bytes.
@cmr Do you know the folks that manage the firmware bot ? That would be nice to have notifications when the changelog are magically edited and new bugs are displayed!