From owner-freebsd-net Fri Aug 3 14: 7:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id EBD3937B401 for ; Fri, 3 Aug 2001 14:07:21 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id DFC934B21; Sat, 4 Aug 2001 06:07:20 +0900 (JST) To: Bill Fenner Cc: freebsd-net@freebsd.org In-reply-to: fenner's message of Fri, 03 Aug 2001 14:04:36 MST. <200108032104.OAA22596@windsor.research.att.com> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: kernel upgrade causes truncated IPSEC packets From: itojun@iijlab.net Date: Sat, 04 Aug 2001 06:07:20 +0900 Message-ID: <5032.996872840@itojun.org> 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 . i need to go through the detail, but something equivalent to these functions happen everywhere in ipsec code. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message