|
On Tue, 2004-05-18 at 13:49, Patrick LeBoutillier wrote:
> Seems like it should work, I will try it out tomorrow.
> Any comments?
Did you look at keepalived Patrick? To give you an idea of how simple,
and how powerful keepalived is, here is a sample configuration provided
with the source which includes interface monitoring and which should be
noted that it will add/remove virtual routes as well:
-- start paste --
global_defs {
lvs_id LVS_DEVEL
}
static_route {
192.168.210.0/24 via 192.168.200.254 dev eth0
192.168.211.0/24 via 192.168.200.254 dev eth0
192.168.212.0/24 dev eth3
192.168.213.0/24 dev eth1
}
vrrp_instance VI_1 {
state MASTER
interface eth0.1 # Vlaned interface
track_interface { # Interface state we monitor
eth0
eth1
}
virtual_router_id 51
priority 100
virtual_ipaddress {
192.168.200.16
192.168.200.17 dev eth1
192.168.200.18 dev eth2
}
virtual_routes {
192.168.110.0/24 via 192.168.200.254 dev eth1
192.168.111.0/24 dev eth2
192.168.112.0/24 via 192.168.100.254
}
}
-- end paste --
When an event happens, you can also have keepalived execute a script of
your choosing relative to the type of event that happened (failure,
recovery etc..)
You should be able to do what you wish using keepalived. As for the
routing functionality of keepalived it is likely relative to how you
have your kernel configured, and possibly the presence of the 'ip' tool
although I doubt it is necessary (but certainly handy to have iproute2
installed on your router/director!)
Cheers,
James
--
James Couzens,
Programmer
-----------------------------------------------------------------
http://libspf.org -- ANSI C Sender Policy Framework library
http://libsrs.org -- ANSI C Sender Rewriting Scehem library
-----------------------------------------------------------------
PGP: http://gpg.mit.edu:11371/pks/lookup?op=get&search=0x6E0396B3
|
