Hi Matthew That did the trick, have accidentally been using an old pre-carp set of firewall rules for the last few days. After your response, I went back and updated to the new rule-set. It's always the simple things.
Thank you, your response was greatly appreciated. Frank > > I have CARP running on a master and a slave server and for some unknown > reason > > the slave continues to classify itself as a master, even though the > advskew is > > higher than on the master. > > It appears that queries sent to the CARP ip address go to the master 50% > of the > > time and the slave 50% of the time when both servers are up. This plays > havoc > > with my databases as I synchronise them asynchronously. > > > > When I take the carp interface down on the slave using 'ifconfig carp0 > down && > > ifconfig carp0 up' it lists it's status as 'backup' for about 10 seconds > and > > then goes back to 'master'. > > Have you by any chance firewalled out the multicast packets that CARP uses > to test for interface death? If either one of a CARP pair can't see CARP > packets > frequently enough it will think the other is down and promote itself to > master. > > If your firewall is blocking, then add a rule like this on both machines: > > pass quick on $ext_if proto carp \ > from $ext_if:network to $carp_mcast keep state > > $carp_mcast is defined as "224.0.0.18" > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > Kent, CT11 9PW > > -------------------------------------------------------------------- Come and visit Web Prophets Website at http://www.webprophets.net.au _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
