From owner-freebsd-current@FreeBSD.ORG Mon Dec 18 07:42:40 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 738BA16A412; Mon, 18 Dec 2006 07:42:40 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id D084743CCC; Mon, 18 Dec 2006 07:42:32 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id kBI7W2qU052085; Sun, 17 Dec 2006 23:32:02 -0800 (PST) Date: Mon, 18 Dec 2006 11:51:22 +0900 Message-ID: From: gnn@freebsd.org To: "Andrew Pantyukhin" In-Reply-To: References: <20061217205249.GA73132@xor.obsecurity.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.90 (i386-apple-darwin8.8.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: David Xu , current@freebsd.org, Kris Kennaway Subject: Re: vge(4) bad checksum X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 07:42:40 -0000 At Mon, 18 Dec 2006 00:08:56 +0300, Andrew Pantyukhin wrote: > I wouldn't even notice the checksum issue if my ipsec > connection to another host hadn't stop working. The > host has ipsec(4) and a re(4) interface. dmesg on the > box showed issues with AH checksums. The problem is > whenever I run tcpdump (promiscuous or not) on re(4), > the box (amd64 current) drops to kernel debugger with > messages like: > panic: mutex Giant not owned at /usr/src/sys/net/bpf.c:1399 > But that's another story. > > So I guess my fast_ipsec/vge/checksum problem is either > fast_ipsec or fast_ipsec+vge bound. Again, there was no > problem with 20061210-current+ipsec+vge (not fast_ipsec). Hi, If you can get tcpdump output on both side of the connection I would appreciate a PR being filed on this and asssigned to me (gnn) since I'm currently in the guts of FAST_IPSEC. Thanks, George