Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello everyone,TL;DR - if you know how to fix IKEv2 traffic selector problems, please help us compile them here so we can start a list!Part of the trends we've been noticing lately with non-Meraki VPN is that a lot of vendors are getting tripped up o...
Seeing this thread again, and specifically @tristan's response, I think perhaps there's some additional details I can provide here, since it sounds like people have expectations on how this works with other vendors and Cisco platforms that don't appl...
vap:4 would be on a Z or wireless MX SSID, specifically the 4th one.Groups have IDs that index from 100, so 104 would be your 5th defined policy - if you go to edit one, you'll see groups/###/edit in the URL, and that corresponds to what it will be l...
Routed tunnel have resolved a lot of the more commons issues we've seen with Azure, for whatever it's worth. They take a bit more effort to set up since you either need a way to monitor tunnel health, or set up BGP, but the actual parameters to set u...
I cannot say when, but yes, this is the plan. IKEv1 is no longer secure enough, as per what the IETF stated a few years back - ref https://datatracker.ietf.org/doc/rfc9395/ - and IKEv2 can handle client addressing natively, so there's no more reason ...