Connecting Non-Meraki peer to multiple MX WAN setup without using Exit Hub

[JordanCN]

I have about a half dozen sites setup with MX 84 devices with AutoVPN setup.  All site can commuicate fine.

Site 1: 172.16.10.x

Site 2: 172.16.20.x

Site 3: 172.16.30.x

etc, etc, etc

We need to connect to a vendor's infrastructure so we setup a Non-Meraki Peer to the Public IP of their appliance and the Local ID is the external IP of the MX at Site 1. I can communicate to the vendor's infrastructure from Site 1, but I need all six sites to traverse the tunnel.

From what I understand I can setup Site1's MX as an Exit Hub so all traffic routes through Site 1, but I really only want the traffic for the vendor's subnets to travel through Site 1. Is this possible or do I have to setup Non-Meraki VPN Peers to each of the external IPs of every MX device with my vendor?

[alemabrahao · Accepted solution]

It is not possible to route the network of Non-Meraki VPN Peers inside the SD-WAN. You need to create a tunnel with each site.

[Aquatera]

I was looking to do the exact same thing, as we have multiple sites that we currently route back over an MPLS network and out via an ASA site-to-site VPN from our DC to a 3rd party monitoring provider, the WAN IP's can float between DC's for resiliency meaning multiple sites only need a single VPN from the DC.  The MPLS is going, and all sites will have MX's installed and was hoping we could do the same thing with them, but looks like it's not possible.

I am hoping a feature request has been put in for this and we will see it one day?