>Web filtering - supported yes but limited cannot do custom profiles etc that i am aware off.   You can create group policies with content filtering and layer 7 rules, and apply them to specific machines or VLAN interfaces.  This needs an Advanced Security licence. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies   >WIDS (wireless intrusion detection) supported?   You really want to use a Meraki MR axxess point if you want strong features in this area.  They support Air Marshall. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal   The WiFi built into the MX models is very basic.     ps. The MX68 has two PoE LAN ports - so you can plug an MR directly into one of the PoE ports to power it. ... View more

Latest rc is MX 18.211.0.1   ... View more

Thanks Shaun. yeah did the ICMP in the end.. very limited on the meraki unfortunately. Also trying to have meraki send alerts to our soar automation using playbooks to ingest tickets into our backend ticketing system.. but unable to separate security events from the WAN appliance with normal switch/wireless events on meraki side, which means more playbook customization 😞 ... View more

You can't do this ntively.  There are third-party solutions like Boundless Digital that offer granular role-based access control. https://www.boundlessdigital.com/network-management/meraki-automation/role-based-access-control/  ... View more

Individual Meraki devices can also be polled locally. In this scenario, the SNMP traffic would stay within the local network and each device would need to be polled from the network management system. These settings can be found under Network-wide > Configure > General > Reporting:   https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_Configuration ... View more

@LeAnts if you are moving it into a combined network you can simply split the combined network into its components and then join together the bits you want.   For example:   Existing network A consists of Switch Network A, Appliance Network A and Wireless Network A, but you want to get the MX that is in Appliance Network B   Split network A Combine Switch Network A, Appliance Network B and Wireless Network A into new Network A   TaDa! ... View more

Correct - as per this document, source based default routing (chosen per-VLAN) only allows two types of next-hop: An IP directly attached via a local VLAN A remote MX, to which the MX in question is linked via an AutoVPN tunnel.   To specify a different WAN link for each VLAN, you need to use the subnet in use on each VLAN, in the way you describe, within the SD-WAN config. https://documentation.meraki.com/MX/Networks_and_Routing/Source_Based_Default_Routing ... View more

You don't have any direct interfaces on the LAN side of an MX.  However defining a VLAN and having that VLAN on an access port on the firewall or as native and only VLAN on a port is basically the same as defining an "interface" on the other types of firewalls.   Do mind that indeed some needed features are missing like the spanning-tree support and port-channel/LACP support as alemabrahao mentioned. ... View more

ah!  Thought we were going to see another new train of MX's 🙂 ... View more