From owner-freebsd-net@FreeBSD.ORG Thu Nov 4 23:29:20 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 622EA1065673 for ; Thu, 4 Nov 2010 23:29:20 +0000 (UTC) (envelope-from ask@develooper.com) Received: from mbox1.develooper.com (mbox1.develooper.com [207.171.7.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2248FC18 for ; Thu, 4 Nov 2010 23:29:19 +0000 (UTC) Received: (qmail 21052 invoked from network); 4 Nov 2010 23:02:38 -0000 Received: from 71-95-204-2.static.mtpk.ca.charter.com (HELO ask-dev.bur.sol) (ask@mail.dev@71.95.204.2) by smtp.develooper.com with ESMTPA; 4 Nov 2010 23:02:38 -0000 From: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 4 Nov 2010 16:02:37 -0700 Message-Id: <17903237-CBF6-4CC3-8CA3-29D9BB65538F@develooper.com> To: freebsd-net@freebsd.org Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Subject: "kernel: carp_input: received len 20 < sizeof(struct carp_header)" messages 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, 04 Nov 2010 23:29:20 -0000 Hi, On a network segment we have both Linux boxes with keepalived (some sort = of vrrp implementation) and FreeBSD boxes with carp enabled. The FreeBSD logs have a gazillion "kernel: carp_input: received len 20 < = sizeof(struct carp_header)" messages. The carp man page makes it seem like we can disable any carp logging = with net.inet.carp.log=3D0; but that doesn't seem to make a difference. The system is running 7.2-RELEASE-p5 (the distribution is pfSense = 1.2.x). Is there another toggle I can use to get rid of the (to us) useless log = messages? I checked that we don't have any overlapping vhid/vrid IDs. Any idea = for how to either just suppress the log message from the kernel or = getting it to log some more details so we can try to make the underlying = problem go away? Thanks! - ask=