Has there been any further movement on route summarization from meraki   ... View more

The ability to block statistical P2P (NBAR 1889) as a category was disabled before the Holidays in 2022 as I noted in this response: https://community.meraki.com/t5/Security-SD-WAN/MX-NBAR-blocking-Statistical-Peer-to-peer-traffi/m-p/179500/highlight/true#M42349 This includes removing it from all aggregate or "All X" rules it may have been a part of ... View more

Hello Karsen Thanks, just what i needed! 🙂 ... View more

This as just for my Knowledge purpose 🙂 ... View more

I supose it is or will be part of this https://community.meraki.com/t5/Feature-Announcements/ThousandEyes-Internet-Insights-Integration/ba-p/141403 ... View more

Wo do it the same way. Or we use an existing Meraki switch, configuring an own VLAN to the three ports: ISP, MX1 and MX2, it´s working like an small switch, but the advantage is: it´s managed. ... View more

Hi Mark,   Quick update to my message:   While there is no specific IP range for api.meraki.com, if you have configured a site-to-site VPN as your default route, then the clients' web traffic will transit your VPN automatically. There's no additional configuration needed; you shouldn't have to manually 'include' any traffic in your VPN when you are using a VPN subnet as a default route. Keep in mind there are local Internet breakout rules available, so you can exempt other traffic from transiting the VPN:     If you are not using Meraki MX, and need to manually route some traffic over your VPN, then I'd recommend using a FQDN rule rather than an IP-based rule for that type of PBR.   If you have no other options, then it's also possible to send API traffic to e.g. n101.meraki.com, instead of api.meraki.com. You can find the 'n101' value by logging into the dashboard via browser. That FQDN has a limited number of IP addresses listed under Help > Firewall info. ... View more

Great idea. I will do that.  ... View more

We are on MX15, I see that MX 16 is currently on a release candidate, we will need to wait for it to be an official release before moving to this build.  We are already implementing geo-blocking, however, the providers that we are having issues with are us based ... View more

No we can't add specific permits in front of any layer 7 rules including Geo. I hope everyone who is missing this feature submits a feature request. ... View more

Try a Google search of your mobile phone carrier name plus "SMS gateway email address" Verizon is 4155551212@vtext.com for example.  Then use that email address for the alerts you want to come as texts to your mobile phone. ... View more

Yes you can include the VLAN.   Just change this: f.write(curr_clients[k]['mac']) f.write("\n")   To this: f.write(curr_clients[k]['mac']) f.write(',') f.write(str(curr_clients[k]['vlan'])) f.write("\n")   ... View more