Hi! From the description it seems like the Splash page/Captive portal used to work but suddently stopped. Is this the correct understanding?  Are all clients affected by this?  What happens when you forget the SSID on an affected client and reattempt the connection?  You may find this document useful:  https://documentation.meraki.com/MR/MR_Splash_Page/Splash_Page_Traffic_Flow_and_Troubleshooting ... View more

Is there anything specific you would like to know about Layer 7 firewall rules?  ... View more

Indeed, this was changed as part of the request you made in this community post 🙂  ... View more

/devices/$serial/switchPorts call is for API v0 version  /devices/{serial}/switch/ports is the current one: https://developer.cisco.com/meraki/api-v1/get-device-switch-ports/ ... View more

The troubleshooting guide should be accurate for MX68 security appliance 🙂 ... View more

Hi! This should be achievable by the implementation of https://documentation.meraki.com/MX/Site-to-site_VPN/VPN_Full-Tunnel_Exclusion_(Application_and_IP%2F%2FURL_Based_Local_Internet_Breakout)  and/or firewall rules  https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Firewall_Settings  getting all Spokes into a template https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/MX_Templates_Best_Practices or pushing the settings via API, for example: https://developer.cisco.com/meraki/api-v1/update-network-appliance-firewall-l-7-firewall-rules/  ... View more

For additional reference to the previous replies in the thread see https://documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Different_MX Maybe some guidance there will be helpful!  ... View more

Hi! Thank you for the feedback. I will forward this information to our documentation team so your concern is addressed appropriately 🙂  ... View more

Buongiorno Marcello! Piacere!  ... View more

Would be great if we could have more information regarding your setup as there could be some caveats to it.  For example, adding multiple AP tags in a single VLAN tag could result in the VLAN ID not applying correctly and therefore SSID availability not functioning as expected.  ... View more

If you're looking to know more details on what is/isn't blocked why which specific rule etc, Meraki Support can help finding out. Meraki Support cannot resolve the issue itself. Hope this makes sense 🙂  ... View more

When Custom DNS service is set to some other DNS, for example, 8.8.8.8, do you still encounter this issue? As Blake said, this is likely due to your DNS server's availability.  Also, please note that when connected to an SSID with NAT mode the wireless clients will still be assigned the AP's internal IP 10.128.128.128 as their DNS server IP (this customizes the destination server of the AP's DNS proxy). ... View more

When opening a support case as per @alemabrahao's advice, you may provide a HAR capture so our engineer can look into any potential errors there 🙂 ... View more

Hi! Upon saving this setting again, were you able to proceed with printing?  ... View more

Hi! The ping is sourced from the Meraki Cloud. Please refer to these articles:  https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Ping_Live_Tool#MR.2C_MV_Ping_Tool  https://documentation.meraki.com/MR/Monitoring_and_Reporting/Using_the_MR_Live_Tools#Ping  ... View more

You could test with Group Policy assignments for your AnyConnect users https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance#Group_Policies  ... View more

There is indeed a possibility to Allowlist these in the Dashboard. Did you have a chance to look into our documentation on this? If not, give it a go, I believe it could be helpful 🙂 https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Threat_Protection#Dealing_with_False_Positives ... View more

Hi All! As per what you have seen in the e-mail from Meraki, this is a known and ongoing issue. MaxMind might have published some geoIP updates recently that are causing the unexpected L7 Firewall rule blocks where there weren't any previously. We cannot do anything about this from our end. @BlakeRichardson, we cannot pinpoint a specific country/countries that would have this issue for GeoIP lookups at this moment, the main point here is to be aware of this behaviour if you see anything out of the ordinary that could be related to L7 rules in your networks.  As always, if you encounter issues and need a more detailed look into this, please contact Meraki Support for further assistance, we'll be happy to help 🙂  We hope this will be resolved soon!   ... View more

Seeing ".win" would be likely related to Windows updates, ".win" is often associated with Windows backup files. ... View more

Hi! This Security rule alerts on DNS queries to .win domains - those are commonly used to try and spoof legitimate websites and trick users into thinking they are the original sites. From experience it would likely not be something to worry about but it would highly depend on what is the exact source of this query, if it's internal or external and whether you are able to tell what device is behind the source address.     ... View more

Hi!   Two active uplinks are supported at a time on a primary MX and additional uplinks should be utilized for tertiary failover on the secondary MX. One or two additional uplinks may be configured on the secondary MX and will become active only when all uplinks on the primary MX fail or when a hardware failure occurs on the primary MX (these additional uplinks connected to the secondary MX can be part of a different IP subnet than the uplinks on the primary MX)       ... View more