NONAT has to be turned on first in Organization > Early Access. Docs are here: https://documentation.meraki.com/MX/Networks_and_Routing/NAT_Exceptions-No_NAT_on_MX_Security_Appliances    And I was wrong, BGP route exchange is available on NONAT routed mode - but only on firmware 18.207 or above:   https://documentation.meraki.com/MX/Networks_and_Routing/Border_Gateway_Protocol_(BGP)   ... View more

You could deploy in routed mode, if you enable NONAT on the WAN interface connected to your MPLS. You'll be able to route in and out of the MPLS and apply L3 firewall rules to the traffic flow.   This is only If you dont mind enabling opt-in "beta" functionality, which NONAT is labelled as. But we've been successfully using it in production as a stop gap until we move everything behind Meraki AutoVPN and NAT.   You'll also not get BGP route exchange, and the MPLS will be treated as an external network, so advertising status routes from the hub might be required depending on your topology and needs. ... View more

I think the auto-reboot function would be great providing: * You can turn the functionality off in the dashboard with a tickbox per network. * The reboot reason and crash data is uploaded to the cloud once connectivity is restored. ... View more

Source NAT would be a super handy feature we could use. Hopefully it's still on the dev todo list. ... View more

On Saturday, during the early hours , we had two MS130-48 in different Orgs with 16.8 and 16.9 firmware both stop forwarding DNS but still allowing TCP/ICMP packets to pass. Looking into 17.1.2 as a fix. ... View more

Upgrading our test MX75 with this version to see how it fares. ... View more