From owner-freebsd-pf@FreeBSD.ORG Thu Apr 3 01:47:51 2008 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07AD8106564A for ; Thu, 3 Apr 2008 01:47:51 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id BE0688FC15 for ; Thu, 3 Apr 2008 01:47:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m331lnKG095768; Wed, 2 Apr 2008 21:47:49 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m331lnUX074256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Apr 2008 21:47:49 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200804030147.m331lnUX074256@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 02 Apr 2008 21:45:46 -0400 To: "Bill Marquette" From: Mike Tancsa In-Reply-To: <55e8a96c0804021647sa108cfm56d87884c3a08f5c@mail.gmail.com> References: <200804021259.m32CxI3U071076@lava.sentex.ca> <55e8a96c0804021647sa108cfm56d87884c3a08f5c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-pf@freebsd.org Subject: Re: carp between RELENG_6 and RELENG_7 X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2008 01:47:51 -0000 At 07:47 PM 4/2/2008, Bill Marquette wrote: >I believe the pfsync protocol version (and corresponding struct) >changed between these two releases. If the lack of state >synchronization can be lived with (ie. it's a high availability >address for a service, not a firewall), you should have no other >issues with CARP. Thanks, this is just for an internal router, so no pf rules/states! ---Mike