A new stable appliance firmware is now available on Wed, 26 Jul 2023

FirmwareBot
New here
A new stable appliance firmware version is available. Firmware MX 18.107.3 was just released on 2023-07-26 and has been in this firmware category since 2023-07-26.
1 Comment
cmr
Kind of a big deal
Kind of a big deal

Security appliance firmware versions MX 18.107.3 changelog

Bug fixes

  • Resolved an MX 17.10.4 regression that could result in the WAN 2 port being set as disabled when making changes via the device local status page.
  • Corrected an issue that could result in an unexpected device reboot when FIPS mode was enabled.
  • Resolved an issue that resulted in MX appliances generating syslog flow messages for internal traffic processing steps.
  • Fixed an issue that could result in the default AnyConnect group policy not being applied consistently, depending on the username’s case/capitalization.
  • Corrected an issue that could result in configuration changes to the Layer 3 firewall rules not taking effect when the MX was configured in passthrough mode and only AnyConnect client VPN was configured.
  • Resolved an issue that resulted in routes learned via IBGP being reported as “external” routes on the Route table page in Dashboard.

IPv6

  • Corrected a rare issue that could result in IBGP instability when two AutoVPN peers established their IBGP session using IPv6.
  • Fixed an issue that could result in AutoVPN IPv6 routes not being preferred over non-Meraki VPN peer IPv6 routes.
  • Resolved an issue that could result in traffic being incorrectly dropped when being routed across an IPv6 route learned via EBGP.
  • Corrected an issue that could result in IPv6 traffic received over VPN not being correctly routed to destinations reachable through other types of VPN. For example, AnyConnect client VPN to non-Meraki site-to-site VPN peers.

MX95/105

  • Fixed an issue that resulted in MX95 and MX105 appliances incorrectly forwarding CDP traffic.

MX67/68

  • Resolved a rare issue that could result in device reboots for MX67(C,W) and MX68(W,CW) appliances.

Z4

  • Fixed an issue that resulted in clients not receiving DHCP IP addresses if 1) clients were connected to Z4 appliances, 2) the Z4 was originally configured in NAT mode, 3) the client received an IP address from the Z4 while it was in NAT mode, and 4) the Z4 was reconfigured to operate in passthrough mode.

Z3

  • Resolved an issue that resulted in the LED activity lights for LAN ports not functioning correctly on Z3(C) appliances.

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.

Other

  • Updated APN mappings for the Orange and EE carriers.
  • Content filtering URL lookups to the Talos backend will no longer follow routes configured for client traffic. These lookups should now always egress a WAN interface.
  • Improved support for reporting when 2.5Gbps and 5Gbps link speeds were in use.
  • Added support for automatic detection of AIF Telecom cellular connections using the “datapro” APN.