"If the MX is configured as a Hub, it will build VPN tunnels to all other Hub MXs in the Auto VPN domain (in the same same dashboard organization). It will also build VPN tunnels to all Spoke MXs in the Auto VPN domain that have this MX configured as a hub. If all MXs in the Auto VPN domain are configured as Hub then the Auto VPN has a full mesh topology." That reads a lot better! It's a 128-bit AES cipher. I added that it's an AES cipher to the "How Auto VPN Works" section under #3, it's in the image that you mentioned was grayed out, and it's in the "Auto VPN vs Non-Meraki Site-to-Site VPN" section. I am personally always negotiating with our internal teams to find a balance of detail we can share, and I appreciate the feedback around why this information is helpful. I understand why missing those details is frustrating, and I'm always pushing for more. This is good, but I would suggest that it states AES128 plainly. We see this question every now and then here in the community, and it's still a requirement for audit purposes for many organizations to be able to state what level of encryption is being used on their IPesc tunnels. I totally get the way Meraki operates and how you control what information you share, but in my mind this sort of thing should be stated clearly, and plainly for all to see. It's not part of any secret sauce. Thanks @CameronMoody. Great work here!
... View more