I have a basic setup. 4 x Meraki MX's across 4 sites. All talking to each other via Meraki S-2-S VPN. Under ../manage/configure/vpn_settings I have the networks propagated with the drop down of 'VPN participation' : 'On'... they are two wide /16 networks. One of those four Meraki sites. has an additional peer to a Non-Meraki VPN implementation. I have three new routes (3 x more specific /24's in those greater /16 network's defined above) defined on the MX interfaces so I can also set the 'VPN participation' : 'On' for them too. Set up the peer as per normal. Here's the kicker. The far end implementation is seeing Phase 1 pass no probs, and even Phase 2, but then complaining of propagated proxy id's. It's seeing one of the wide /16 networks. Half understandable.. because.. for some reason.. we can't specify NEAR subnets in the non-meraki VPN peer setup ? Only FAR subnets ? (via the 'private subnets' field) ?! Surely, there's a way to do this...
... View more
