In your case it's simpler just use two /32 static routes
We need to make two new terms which are the gateways for WANs
WAN y.y.y.y gateway is y.y.y.gw
WAN z.z.z.z gateway is z.z.z.gw
So simply specify a /32 route for the EOIP tunnel trafficThe basics here are that only the tunnel traffic itself actually goes to the remote public IP. All the site to site traffic is going thru the tunnel which does not involve the public IP. Your tunnel traffic itself now has no option but to leave via WAN you specified.
It's a trick you often use when you want to form a tunnel and have the default route go thru the tunnel when you would do something like thisEverything in the above goes thru the tunnel except the tunnel communication traffic itself.
We need to make two new terms which are the gateways for WANs
WAN y.y.y.y gateway is y.y.y.gw
WAN z.z.z.z gateway is z.z.z.gw
So simply specify a /32 route for the EOIP tunnel traffic
Code:
/ip routeadd dst-address a.a.a.a/32 gateway=y.y.y.gwadd dst-address b.b.b.bv/32 gateway=z.z.z.gwIt's a trick you often use when you want to form a tunnel and have the default route go thru the tunnel when you would do something like this
Code:
/ip routeadd dst-address 0.0.0.0/0 gateway=tunnel.gw add dst-address a.a.a.a/32 gateway=y.y.y.gwStatistics: Posted by LdB — Sat Dec 09, 2023 10:24 am