Date: Wed, 02 Mar 2005 17:19:38 -0600 From: Matthew Grooms <mgrooms@seton.org> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: freebsd-pf@FreeBSD.org Subject: Re: Fwd: pf + pfsync + carp testing ... Message-ID: <42264A0A.1090301@seton.org> In-Reply-To: <20050302191656.GA93112@cell.sick.ru> References: <200502282232.17646.max@love2party.net> <4223931C.9000607@seton.org> <200502282326.41760.max@love2party.net> <4224B078.9020301@seton.org> <20050301185431.GA81982@cell.sick.ru> <4225174C.801@seton.org> <20050302081051.GB87159@cell.sick.ru> <422600A2.2080907@seton.org> <20050302191656.GA93112@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Gleb & Max,
Fantastic! The carp interfaces work like a champ now on RELENG_5.
I have been testing the fail over for about half an hour and the MASTER
/ BACKUP state changes have worked 100% of the time. I really appreciate
both of you taking the time to get this stuff into FreeBSD.
On a slightly more depressing note, I don't think that state via
pfsync seems to be working right between the two firewalls. Sometimes (
maybe every 1 out of 4 tries ) when the interfaces fail over, the
traffic flow stops. The reason why I believe it is a state sync issue is
that new connections can always be opened even while the previously
opened connections are stalled. This doesn't always happen when an
interface is going down either. It happens just as often when an
interface is coming back up and reclaims a MASTER state. Any ideas?
Matthew
Gleb Smirnoff wrote:
> Matthew,
>
> Yes. There was an error in there. Frank Volf has already showed me it in private
> mail. Sorry for this. I'm working in HEAD now, where miibus and em does not need
> this hacks.
>
> Fixed patch available at the same place:
>
> http://people.freebsd.org/~glebius/totest/carp-RELENG_5-patch
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42264A0A.1090301>