From owner-freebsd-questions@FreeBSD.ORG Wed Dec 14 19:47:01 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5D081065673 for ; Wed, 14 Dec 2011 19:47:01 +0000 (UTC) (envelope-from mokomull@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5E76E8FC08 for ; Wed, 14 Dec 2011 19:47:00 +0000 (UTC) Received: by faaf16 with SMTP id f16so2324772faa.13 for ; Wed, 14 Dec 2011 11:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RhRM7C7wmHQ2gxBC18G7Q2zrY1hl0h9cMMSLAPvun2Y=; b=FbmiEGVrihoeWArdhCupmO+DeuqquO61bdYUrgpBOjxxc1LNYZU1WbMaARbfUGiV/J VqPzBbqyC3SXy/n/wiBJ+RXC0UqVLfBi/viKqsjcaRE2WiTkGcyqae45/1KhxANAt9uC I39wMut0hV89XX0j9NWisAFvzWz01ipSEKVbw= MIME-Version: 1.0 Received: by 10.180.90.234 with SMTP id bz10mr7674557wib.46.1323892020116; Wed, 14 Dec 2011 11:47:00 -0800 (PST) Received: by 10.223.154.135 with HTTP; Wed, 14 Dec 2011 11:47:00 -0800 (PST) In-Reply-To: <20111214092557.GB38586@admin.sibptus.tomsk.ru> References: <20111214050959.GA34547@admin.sibptus.tomsk.ru> <4EE857D3.2060504@gmail.com> <20111214092557.GB38586@admin.sibptus.tomsk.ru> Date: Wed, 14 Dec 2011 11:47:00 -0800 Message-ID: From: Matt Mullins To: Victor Sudakov Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Subject: Re: carp(4) on FreeBSD 8.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2011 19:47:01 -0000 I've used carp very successfully in the past, both in the standard mode and ARP load-balancing mode, to build fail-over sets of firewalls. It worked well enough that one of our firewalls was down for a week before we noticed (and none of our clients did). I just did a mock-up of your scenario on a system at home (using the GENERIC kernel), and it seemed to work for me. I see you have a managed switch; you might see if some features like port security are disabled for that port. > What is even more strange, tcpdump on le0 does not even see ICMP echo > requests addressed to 10.14.134.99. That is strange. You might try "tcpdump -nevvv -i host 10.14.134.99" on the sending system and see if it's even sending the packets at all. If there's a remote chance that something else is using carp or VRRP on that network, you might try using a different VHID. Hope I can help, Matt Mullins