Date: Mon, 18 Dec 2006 11:51:22 +0900 From: gnn@freebsd.org To: "Andrew Pantyukhin" <infofarmer@freebsd.org> Cc: David Xu <davidxu@freebsd.org>, current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: vge(4) bad checksum Message-ID: <m2tzzt29xx.wl%gnn@neville-neil.com> In-Reply-To: <cb5206420612171308o4c8f2373g26986c5722e606e1@mail.gmail.com> References: <cb5206420612171246q54ac783h1fd9d420b80ba84c@mail.gmail.com> <20061217205249.GA73132@xor.obsecurity.org> <cb5206420612171308o4c8f2373g26986c5722e606e1@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2tzzt29xx.wl%gnn>