Hi, the email I received from Meraki regarding the MX 18.105 update also mentioned support for the following: "- Added support for configuring VPN exclusion rules for non-Meraki VPN peers". This is however missing from this post and in the firmware upgrade page on the dashboard.
Could you please elaborate if this support is added or not and preferably some documentation on this new feature?
Is the SGT support also across AutoVPN ? So "true" End-to-End ?
This is what I expected when I saw this new firmware. But the documentation is not yet updated. This would be great although IMO this feature is quite useless with only the MS390 supporting it on the switch side.
Does this also fix the connectivity and resolution issues with slow response times for wireless clients that I've seen reported on 17.x and 18.x firmware?
Edit: Does not seem to have fixed anything compared to previous 18.x and latest 17.x code.
Slow wifi client issues, wifi calling doesn't work, several issues with this code as well. 17.x does the same thing on the latest version too. Issues not present in 16.x codes
I agree. The Wi-fi issue has not been fixed.
I just upgraded one of my client's MX64W to 18.105 to see if it fixes the wifi being trash. Not fixed...
I added an Omada WAP and the wifi works perfectly now. Cisco....................please fix!
Running good so far. Looking forward to playing around with SGT forwarding in the next few days!
Since this just got scheduled for my MX-450 Hub networks, any details on the known issue:
Posting if this helps others, upgrading MX units to 18.105 which only have cellular/4G internet (ie, no ethernet internet connectivity) there appears to be a bug which the unit reports on the dashboard as upgraded to 18.105 however the device goes offline for 15 minutes every 2 hours.
Meraki support engineer confirmed the device was stuck in a upgrade loop and was actually still running 17.10.2 firmware even though the dashboard says its updated.
Telling the MX to reboot via the web dashboard 'fixes' the issue for a few hours before it comes back again. The actual fix is to pull the power out of the MX and reconnect, the hard power off/on appears to force it to update correctly.