Security appliance firmware versions MX 16.16.8 changelog
Important notice
- While Meraki appliances have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MX 16 we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that traffic using TCP port 443 between 209.206.48.0/20 is allowed through any firewalls that may be deployed upstream of your Meraki appliances.
- HTTP proxy, which allows default management traffic from MX appliances to be sent through a proxy, is deprecated on MX 16 and higher firmware versions.
Legacy products notice
- When configured for this version, Z1 and MX80 appliances will run MX 14.56.
Bug fixes
- Resolved an issue that could cause small, periodic packet loss on MX100 appliances.
- Fixed an issue that caused packet loss between client devices communicating within the same VLAN when both client devices were connected to ports configured for 802.1X port authentication.
- Resolved a case where the device local status page could still be accessed, even after it had been disabled via the Meraki Dashboard.
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 MX 15 regressions, USB cellular connectivity may be less reliable on some modems
- Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page
- Client traffic will be dropped by MX65(W), MX67(C,W), and MX68(W,CW) appliances if 1) The client is connected to a LAN port with 802.1X authentication enabled and 2) The VLAN ID of the port is configured to 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, or 240.
If my answer solves your problem please click Accept as Solution so others can benefit from it.
