At the moment you can’t, they’re not supported on Group Policies. See, https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Network_Objects_Configuration_Guide
... View more
Nolan, Will the Network Objects be limited to only Access Rules? I am dying for it to be available in the port forwarding rules section too. Have a large number of inbound client connections that I need to allow ideally based on FQDN. Thanks, Warren
... View more
We use it a lot for client either blaming AMP if they know what it is or saying they can't get to something (Software updates seems to be the most frequent). We use a group policy to turn AMP off and then apply it to their device. If it fixes the issue and is able to be reproduced then we add AMP whitelist to main settings and remove device from that policy.
... View more
Nah, you're fine. Meraki's different. An MX (by default) will automatically pass all traffic it receives from the inside to the outside, as PAT/1:Many. You can restrict that via the L7 and L3 firewall, content filter...
... View more
>Does any on know if is it possible to specify Inbound interface or outbound interface in a layer 3 rule ? What happens is no traffic is allowed inbound by default until you create a NAT rule to allow it. When you create a NAT rule there is a section where you can limit where that NAT can be accessed from.
... View more
The MX is the Security - SD WAN product. While the Z range is the teleworker / remote gateway device. You can see the specs and difference here
... View more
Hey all, I'll just silently leave this here... https://documentation.meraki.com/MX-Z/Deployment_Guides/Datacenter_Redundancy_(DC-DC_Failover)_Deployment_Guide 🙂 Giacomo
... View more
