failover with conntrackd
(Sorry for the delayed response. I've been on vacation. I'm quoting extensively to provide context.)
Quoted 3 lines · At 2007-10-10 09:55:57 -0500, [email protected] wrote:
Quoted 3 lines
Is anyone using conntrack-tools to implement gateway failover on a network with windows clients? [...]
To recap: I have two gateway machines that share two virtual addresses (one on eth0, connected to the internal network and the other on eth1, connected to the outside world).
Quoted 3 lines
Um, why are you not using the same MAC address for the gateway and having the systems decide who is actively using the MAC at any given time?
Mostly because neither ucarp nor keepalived seem to support changing the MAC address... and besides, everything I read seems to suggest that just gratuitous ARP should be sufficient.
Quoted 3 lines
There is a very simple VRRP daemon (vrrpd) for Linux / Unix that will achieve this. To my knowledge it works by creating a new MAC address that is used for the VRRP router.
I did not realise that vrrpd supports it.
My problem with ucarp (which, like vrrpd, also uses a single daemon per interface/shared IP) is that the pair of daemons on eth0 were not always perfectly synchronised with the pair on eth1. As a result, failover time was unpredictable. That's why I switched to keepalived, so as to manage both interfaces with a single process.
But I'll try vrrpd anyway, thanks.
Quoted 2 lines
The two or more VRRP routers will heart beat each other (I think by multicast (?))
Yes, through multicast; and if the primary goes down, the remaining nodes elect a new primary.
I'll try it and report.
-- ams
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Quoted 2 lines · At 2007-10-23 11:38:00 +0530, [email protected] wrote:
But I'll try vrrpd anyway, thanks.
Ah, no. vrrpd is a non-starter, because it provides no notification when a machine switches between primary and secondary mode. Unfortunately, I can't use any of the three failover programs I've tried so far.
1. keepalived
- Provides notifications.
- Uses a single process for multiple interfaces, so no synchronisation problems.
- Doesn't support MAC address takeover.
2. vrrpd
- Supports MAC address takeover.
- Uses one process per interface, but supports synchronisation through signalling the other process when state the changes.
- Doesn't provide notifications (although Jerome Etienne's OLS presentation suggests that he meant to implement this).
- Not very nice code; authentication partly implemented, but with bugs and without sufficient testing.
3. ucarp
- Provides notifications.
- Reasonably nice code.
- Uses one process per interface, and provides no synchronisation support at all.
- Does not support MAC address takeover.
I'm going to modify ucarp to change the MAC address with the state, and to switch state on signal, so that two processes can be synchronised.
This is a lot more painful than I thought it would be.
-- ams
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc