On 9/12/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > On 12-Sep-07, at 4:30 PM, Sjon Wijnolst wrote: > > > Which tools can be used to monitor connections (up-down, IP) and act > > uppon changes? Any experience? I've been looking into Paul Gear's > > article but that doesn't really implement what I want. I understood > > shorewall can be loaded with a different set of configuration > > files, so > > I could create files for every scenario and load them with appropriate > > command lines. > > the config files are not a problem - the problem is, how do you > detect when the ISP goes down, or, more important, when i comes up > again? I have been struggling with this for some time. When one ISP > goes down, things get messed up until we notice and change the > configuration - then we have to watch to see when it comes up. >
I have two DSL lines, each of them is rather unreliable, going down and up frequently. My solution is to arping the gateways for the two lines every 5 seconds or so, and if a line is not responding, then add an ip rule to direct all traffic via another line. Then when the line is back, this ip rule is deleted. The actual script is very simple and it works well. This way shorewall doesn't have to be restarted, and tc rules are also not affected. Regards, Gregory ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
