I have an unusual case where I want a new non-meraki S2S VPN peer to be able to talk to another non-meraki S2S VPN peer on our network. For various reasons we are not able to bridge the two non-meraki peers directly and they can only bridge via our network. We basically want to set something like this up - https://community.cisco.com/t5/security-documents/routing-traffic-between-two-site-to-site-vpn-tunnels/ta-p/3145351 I'm trying to figure out how this can be accomplished in the year of 2021. Seems this could go two ways... Bridge inside of MX device - now that Meraki supports IKE2 route-based VPNs (after a FW update...) I am curious if this can be accomplished entirely within the Meraki appliances now. Add an extra device - it seems I could purchase a third device (another Meraki, an EdgeRouter, something), connect one of the S2S VPN to that, and then setup a route between the MX and the 3rd party device to make this happen? Can anybody help me better understand these concepts and how I could possibly accomplish them? I'm a bit out of my depth and on a time crunch, of course. Environment: Two MX100s setup in HA, two dedicated fiber lines, I *may* have spare IPs on each line... let's assume I do for now for option 2. The existing S2S VPN uses IKE1, while the other VPN supports IKE2, it seems they prefer IKE2 route based policy.
... View more