From owner-freebsd-net@FreeBSD.ORG Tue Jan 2 11:26:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4442116A403 for ; Tue, 2 Jan 2007 11:26:41 +0000 (UTC) (envelope-from ashoke@rocketmail.com) Received: from web51909.mail.yahoo.com (web51909.mail.yahoo.com [206.190.48.72]) by mx1.freebsd.org (Postfix) with SMTP id D764413C428 for ; Tue, 2 Jan 2007 11:26:40 +0000 (UTC) (envelope-from ashoke@rocketmail.com) Received: (qmail 94229 invoked by uid 60001); 2 Jan 2007 10:59:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rocketmail.com; h=Message-ID:X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=EHLnYOmnBdU33d9TN0/7StQ25eyZ0yT4yxZBt6mL2s4YqyHDD2O9phAaGEBQn6vC+OZ18JCru/eqCpA3ZKVTyW2FQCp+pPZfwSsYFhbUIj4G49vqVhkMF9hKQ2LEJBE9hvZpthwXcHLEPtU7lgLUHEUXfFWkO75isM+JkVo3x8Q= ; Message-ID: <20070102105959.94227.qmail@web51909.mail.yahoo.com> X-YMail-OSG: zWzSraoVM1nJhnKYGOZmFPgZLHaqZOXimj1TJr0RGsPmNB7vrxYTjdl2ZrXEokIuJWOhSziHgvvEv7Q0hUW5sFFTOk0ofy4QRFnOTLocsfoatIlwWtp6ZA-- Received: from [164.164.171.199] by web51909.mail.yahoo.com via HTTP; Tue, 02 Jan 2007 02:59:59 PST Date: Tue, 2 Jan 2007 02:59:59 -0800 (PST) From: ashoke saha To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: NAT Taversal bug in kernel patch ? 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: Tue, 02 Jan 2007 11:26:41 -0000 Hi , just joined the mailibng list. I was implementing NAT traversal based on the patch and my kernel was panicking because of wrong ipsec config, which it should not whatever be the config. Looks like there is a small issue in the code http://ipsec-tools.sourceforge.net/freebsd6-natt.diff which might already be fixed. Look at the call of the function udp4_espinudp () in udp append. Now under certain circumstances it is possible that udp4_espinudp () calls m_pullup() and it would add a new pkt header to the mbuf chain. But udp_append() is still holding the old head, whose PKTHDR flag is now off. It then sends the pkt further up and kernel does as panic as it does not see PKTHDR flag. ashoke. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com