From owner-freebsd-net@FreeBSD.ORG Thu May 25 19:05:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A5816B679 for ; Thu, 25 May 2006 19:05:48 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 873AC43D55 for ; Thu, 25 May 2006 19:05:45 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by py-out-1112.google.com with SMTP id s49so3178473pyc for ; Thu, 25 May 2006 12:05:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NfpXkj6C10NSecVcwEjyiDMQrzH4Dlo2xxv/9maASyg7JEHDeJ0yyqaL4IxaYBF3ua1zNE1/To0IFHhc1PatDWTfD1pQ6s2wDeznxdcTaSl5mUs6yUYGnaNhhWzwKMg8BSVjRGRH4cJXY5/gjVUYi71JGCfXayk2d/Rw0TyXM0w= Received: by 10.35.8.1 with SMTP id l1mr1095647pyi; Thu, 25 May 2006 12:05:44 -0700 (PDT) Received: by 10.35.94.6 with HTTP; Thu, 25 May 2006 12:05:44 -0700 (PDT) Message-ID: Date: Thu, 25 May 2006 15:05:44 -0400 From: "Scott Ullrich" To: dima <_pppp@mail.ru> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-net@freebsd.org, Marko Lerota Subject: Re: Re[2]: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 19:06:03 -0000 On 5/25/06, dima <_pppp@mail.ru> wrote: > That's not true. I have several CARP deployments on 5.x. None of them eit= her adds this route or writes anything to logs. I cannot speak for 5.X. I speak only for RELENG_6_X. Looking back I cannot recall if this was the behavior that I saw when we where on 5.X. Either way it happens on 6.X in a lot of (search for "bad gateway" on http://forum.pfsense.com) pfSense installs and has became a FAQ rather quickly. Scott