On 12-12-09 12:00 PM, Jo-Philipp Wich wrote: > I fail to see how that requires changes to shorewall, it would continue > doing whatever it does (routes added without explicit metric get > automatically metric 0).
Because shorewall builds a routing system that looks like this:
root@OpenWrt:~# ip rule ls
0: from all lookup local
...
32766: from all lookup main
32767: from all lookup default
root@OpenWrt:~# ip route ls table main
default via <gw_primary_isp> dev eth0.1
...
10.75.22.0/24 dev br-lan proto kernel scope link src 10.75.22.195
root@OpenWrt:~# ip route ls table default
default via {gw_fallback_isp> dev pppoe-wan1 src 1.5.3.5 metric 2
So that when the primary ISP goes AWOL it's default route disappears
from the "main" routing table and default routing falls through to the
"default" table.
If I were to add both ISP's gateways into the "main" routing table,
albeit with lower metrics, they would still be used in preference to
falling through to the "default" routing table.
Cheers,
b.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
