I've read this blog, and I know that
1.Non-Meraki VPN routes are not advertised to AutoVPN peers.
2.Remote non-Meraki VPN subnets cannot overlap with any existing Dashboard subnets/routes.
Say I have a topogy like this,
MX (1.1.1.1/16) ( BRANCH) --> AutoVpn -> MX (HUB) --> Non-Meraki peer (2.2.2.2/16)
According to the docs, If I don't do anything, the branch MX, and the Non-Meraki peer won't have reachability to each other.
But what if I just configure a static route on the branch MX (1.1.1.1/16) pointing to Non-Meraki peer (2.2.2.1/16) with a next hop of the Hub MX, and do the reverse on the Non-Meraki peer?
It looks simpler than the solution suggested in the blog.
Will this work or Am I just misunderstanding something here?
Thanks in advance.
