From owner-freebsd-net Fri Aug 3 14: 4:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 7AB9037B407 for ; Fri, 3 Aug 2001 14:04:38 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id C49DB4CE80; Fri, 3 Aug 2001 17:04:37 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA21481; Fri, 3 Aug 2001 17:04:37 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id OAA22596; Fri, 3 Aug 2001 14:04:37 -0700 (PDT) Message-Id: <200108032104.OAA22596@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: itojun@iijlab.net Subject: Re: kernel upgrade causes truncated IPSEC packets Cc: freebsd-net@freebsd.org Date: Fri, 3 Aug 2001 14:04:36 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > [0-length mbuf in the chain] is perfectly legal, and can happen > by result of m_cat()/m_split() calls from ipsec code. I don't see any m_cat() or m_split() happening on output; they're all in ah_input.c and esp_input.c . A 0-length mbuf in the chain is at best useless and perhaps fairly unexpected (thus the bug in if_tun.c lasting for 6.5 years before being found). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message