Thanks for the reply.
![:(]( "Sad")
I think I may just switch this to a net-monitor script instead.
The routing table is the only relevant partComplete config required for analysis ( minus router serial number, public WANIP information, keys etc.. )
When WAN1 dies, both routes regardless of distance should be disabled, so distance isn't relevant. But I have changed it, and tested anyway and it still doesn't workFrom the displayed information separate the two dns by distance, so the cloudflar ones should both be disttance=2
I think in my trial and error I added these, have removed.What is vrf-doing on wan interfaces ???
Code:
/ip routeadd comment="TAG: eth1_wan1 ROUTE GOOGLE" disabled=no distance=1 dst-address=0.0.0.0/0 gateway=8.8.4.4 pref-src="" routing-table=main scope=10 suppress-hw-offload=no target-scope=12add comment="TAG: eth1_wan1 PING GOOGLE" disabled=no distance=1 dst-address=8.8.4.4 gateway=82.x.x.x pref-src="" routing-table=main scope=10 suppress-hw-offload=no target-scope=11add comment="TAG: eth1_wan1 ROUTE CLOUDFLARE" disabled=no distance=2 dst-address=0.0.0.0/0 gateway=1.0.0.1 pref-src="" routing-table=main scope=10 suppress-hw-offload=no target-scope=12add comment="TAG: eth1_wan1 PING CLOUDFLARE" disabled=no distance=2 dst-address=1.0.0.1 gateway=82.x.x.x pref-src="" routing-table=main scope=10 suppress-hw-offload=no target-scope=11add comment=ROUTE_WAN2 disabled=no distance=5 dst-address=0.0.0.0/0 gateway=eth2_wan2__pppoe_zen pref-src="" routing-table=main scope=30 suppress-hw-offload=no target-scope=10I think I may just switch this to a net-monitor script instead.
Statistics: Posted by lazynooblet — Sat Mar 23, 2024 10:57 pm