A lot of fixes in this one... who's going first?
Me of course! Just applied it to a Z3 that was running 18.208.1...
Months and months after the release of MX18 and cellular is still broken...
Upgrading our test MX75 with this version to see how it fares.
Just pushed this to an MX75 and setting up an upgrade to MX68 for later tonight.
Just went through the upgrade. No issues until now!
Can you elaborate more?
Only issue here so far is one site with a HA pair of MX105's where they cant seem to upgrade correctly.
All other sites , 20 - 30 with different MX models seems just fine.
The issue with the MX105s we can clearly see on the "connection" graph. Every two hours "red", for a short while. - And of course loss of connection for users.
Support says that maybe some files on the MX are not being purged.
Suggested we try to upgrade to latest 18.1 and then to this 18.2, else reset devices for a proper "clean up". (I dont know when we can have the next service-window on that site, but I will try to update this when that happens)
We have loaded this on our DEV firewall and a couple sites as of yesterday. We are waiting to perform on the larger MX450 series in HA pair that has been painful for a long time on that series. Would like to know if anyone else loaded it on their bigger series yet and any issues reported. NAT rules failing were a big one for us.
I'm fighting NAT 1:1 rule failure on a an MX250 right now, and 18.210 didn't seem to help any over any older firmware.
Our problem:
public IPs (not actual, but close representation)
WAN1
10.0.0.1/28 gateway
10.0.0.2 main IP
10.0.0.3 secondary IP for certain traffic NATed to 192.168.0.11 (this works perfectly on legacy non Meraki router)
WAN2
11.0.0.2 main IP
- 1:1 NAT setup for LAN IP 192.168.0.11 to 10.0.0.3 port forwarding port 80 for non-secure informational data.
- of course normal port forward doesn't do anything since the traffic is not incoming on 10.0.0.2
- zero traffic allowed to or from 192.168.0.11 with 1:1 NAT turned on for 10.0.0.3
- outbound only traffic is good from 192.168.0.11 with no NAT or 1:MANY NAT (tried 1:MANY just for fun.) but still no incoming traffic allowed.
- Contacted ISP to clear ARP tables, still no traffic incoming.
With input from Meraki Support, we tried a number of scenarios, including messing with traffic shaping, and flow preferences. Very confusing as to why with NAT there is no incoming traffic allowed no matter what inbound ports are defined to allow traffic from a non-primary IP that still within the subnet. Seems like a serious Meraki bug that needs attention.
I may have found out something about the 1:1 NAT. Apparently the 1:1 NAT will not even try to work if the destination is not in the ARP table of the Meraki. And, in my case the destination device didn't seem to fill the ARP table in my short testing window. After trying another destination device, it started working about 24 hours where it did not initially upon setup. Very strange it takes so long to update the ARP table.
We just upgraded from 18.107.2 to 18.210 on our MX75 and immediately noticed that the IPv6 uplink is no longer working. I can get our static IPv4 address on the same uplink, but v6 is stuck in 'Failed' state.
It's not urgent as we don't use it, and I can't say if it's our ISP or not. It just started happening after the update.