On Mon, Mar 24, 2008 at 11:39:28AM -0400, Brian J. Murrell wrote: > > No idea if it makes any sense with one box (insofar as that makes any > > sense at all) - I'd never try, a second box is the cheapest element of > > the setup. > > But you first have to solve my basic problem: adjusting to Internet > connections going up and down on a single box before you can start to > roll that out to multiple boxes -- to deal with hardware failures.
In a full heartbeat-managed system you can just use pingd or something similar, and treat the internet connections like extra resources to be monitored, like you would any network-attached storage device. Then it's just a matter of setting up rules to kick shorewall at the appropriate moments. (I don't actually do it that way, my systems are rigged to feed link state into quagga and run OSPF, which is a whole different beast. Heartbeat probably isn't suitable for a single host setup either) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
