New MX 18.107.1 stable release candidate patch - fixes MX100 upgrade fail issues

[cmr]

Security appliance firmware versions MX 18.107.1 changelog

Bug fixes

• Resolved an issue that could result in MX100 appliances becoming unresponsive and unable to be recovered with a factory reset after upgrading to MX 17.10.5 or MX 18.1.07 from very old, unsupported firmware versions that reflect as critically out of date from the Organization > Firmware upgrades page in Dashboard.

Legacy products notice

• When configured for this version, Z1 and MX80 devices will run MX 14.56.
• When configured for this version, MX400 and MX600 devices will run MX 16.16.9.

Known issues

• 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.
• Due to an MX 17 regression, RADIUS messages that transit across AutoVPN may fail to be routed correctly.
• There may be an increased risk of encountering device stability and performance issues.

[rhbirkelund]

• Due to an MX 17 regression, RADIUS messages that transit across AutoVPN may fail to be routed correctly.

Hm.. Maybe this is the fix to my current problem with an SSID in tunnel mode, where Radius is being forwarded to Internet instead of obeying the static route on my MX.