From owner-freebsd-current@FreeBSD.ORG Mon Sep 27 12:33:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DBF216A4D0 for ; Mon, 27 Sep 2004 12:33:26 +0000 (GMT) Received: from niked.office.suresupport.com (niked.office.suresupport.com [213.145.98.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB96A43D5E for ; Mon, 27 Sep 2004 12:33:25 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from niked.office.suresupport.com (localhost [127.0.0.1]) i8RCZCBw001000 for ; Mon, 27 Sep 2004 15:35:13 +0300 (EEST) (envelope-from nike_d@cytexbg.com) References: <001001c4a305$d003a400$0301a8c0@danielle> <002401c4a45a$642b7cc0$0301a8c0@danielle> <20040927104532.GA20357@mehnert.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Niki Denev To: freebsd-current@freebsd.org Date: Mon, 27 Sep 2004 15:35:12 +0300 Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=_mimegpg-niked.office.suresupport.com-903-1096288512-0001"; micalg=pgp-sha1; protocol="application/pgp-signature" Subject: Re: ipsec and freebsd 5.3-beta X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 27 Sep 2004 12:33:26 -0000 This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet software does not support MIME signed messages. --=_mimegpg-niked.office.suresupport.com-903-1096288512-0001 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hannes Mehnert writes: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > On Mon, Sep 27, 2004 at 08:22:40AM +0200, cell wrote: >> I have always the same problem.I'm on freebsd 5.3-beta 5 and i have put the >> patch for key.c who is in cvweb but i have that : >> .. ENOBUFS ... > > Currently only netipsec/key.c is fixed (which is the FAST_IPSEC > implementation), so if you use FAST_IPSEC it should work, with IPSEC it > shouldn't. > > > Best Regards, > > Hannes Mehnert > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (FreeBSD) > > iD8DBQFBV+9JRcuNlziBjRwRAl1QAJ9bQ7zSaI5IN8IGl7BmEsRE3AM5FACffOwB > 3E1YOvTQaPf19QjG8cRx4w8= > =5rFG The netkey/key.c and netipsec/key.c files are very similar, probably because as far as i remember FAST_IPSEC started as fork from the KAME ipsec implementation.(or at least uses some of the code) I think that the same fix will work both for IPSEC and FAST_IPSEC. e can try to find the key_parse() routine in netkey/key.c and comment the following code : if (m->m_next) { /*XXX*/ m_freem(m); return ENOBUFS; } starting at line 6976. P.S. No guarantees on that, try it at your own risk :) :) --niki --=_mimegpg-niked.office.suresupport.com-903-1096288512-0001 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBWAkAHNAJ/fLbfrkRAl76AJwJ+vWmTAUc3SkPR+v4QcAQJiyUAQCguWb/ 3z+KitNG4aEtLJBicGREWYE= =GGyV -----END PGP SIGNATURE----- --=_mimegpg-niked.office.suresupport.com-903-1096288512-0001--