>> While it works, this setup has a drawback: the ping IP can't be >> reached when a link goes down. > > What do you mean by 'link goes down'? Do you mean that a 'shorewall > disable' has been done for the link?
No, I mean that shorewall can't reach the IP (the adsl link goes down, the ISP has routing problems). >> - no static routes >> - lsm interface option select link for pings > > Is this depending on route rules that direct traffic with a source IP > address of a provider interface out of that interface? Yes. # ip ru | grep wifi 10001: from all fwmark 0x20000/0xf0000 lookup wifi 20000: from x.x.130.33 lookup wifi # ip ro sh table wifi x.x.128.7 dev ppp0 scope link src x.x.130.33 default via x.x.128.7 dev ppp0 src x.x.130.33 lsm binds to x.x.130.33 thanks to the device=ppp0 option. If I use shorewall disable wifi, both ip rules and the full wifi routing table go away. I'd like to remove only the fwmark (maybe optionally), so that if I forced some traffic through wifi it could go out via the other link. > The generated script already has 'up' and 'down' commands that do > something else. We could consider a new option in shorewall.conf that > alters the behavior of 'disable' and 'enable'. Got it. I'm not good with names, something like: RESTORE_RT_RULES=Yes/No (default Yes) If Yes shorewall enable will adjust routing rules (like now). If No, shorewall will only adjust the default gateway in the balance table. -- Ciao, Filippo ------------------------------------------------------------------------------ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
