From owner-freebsd-current@FreeBSD.ORG Fri Dec 19 01:32:06 2003 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 15D3E16A4CE; Fri, 19 Dec 2003 01:32:06 -0800 (PST) Received: from snoopy.pacific.net.au (snoopy.pacific.net.au [61.8.0.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D5243D3F; Fri, 19 Dec 2003 01:32:04 -0800 (PST) (envelope-from memetical@yahoo.com.au) Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) hBJ9W3no004006; Fri, 19 Dec 2003 20:32:03 +1100 Received: from zhadum.dnsalias.net (dyn153.syd7.homedsl.pacific.net.au [202.7.78.153])hBJ9W3xs001546; Fri, 19 Dec 2003 20:32:03 +1100 Received: from psi.starfleet.org.au (psi.starfleet.org.au [172.16.0.3]) by arthur.starfleet.org.au (Postfix) with ESMTP id CEBF29434; Fri, 19 Dec 2003 20:32:02 +1100 (EST) Received: by psi.starfleet.org.au (Postfix, from userid 1000) id A41FC6D457; Fri, 19 Dec 2003 20:32:02 +1100 (EST) Date: Fri, 19 Dec 2003 20:32:02 +1100 From: Rudolph Pereira To: "Bjoern A. Zeeb" Message-ID: <20031219093202.GB669@starfleet.org.au> References: <20031219064932.GA94971@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Possible IPsec Trouble in 5.2RC? 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: Fri, 19 Dec 2003 09:32:06 -0000 On Fri, Dec 19, 2003 at 07:58:06AM +0000, Bjoern A. Zeeb wrote: > On Thu, 18 Dec 2003, Crist J. Clark wrote: > > Hi, > > > I just upgraded a ThinkPad 600E from RELENG_5_1 to RELENG_5_2. I seem > > to be having trouble with my IKE deamon, racoon(8), but I don't think > > the problem is with racoon(8), but it may be the FreeBSD KAME IPsec > > implementation. > .... > > Anyone else seeing this? > > I am seeing a lot of other trouble with IPSEC implementation at the > moment. Multiple 0xdeadc0de accesses and I have successfully been able > to panic my router test box by at least 3 different ways. Again, I can only concur. My -current-running laptop has never been so unstable as when I've been trying to setup ipsec. I've had random panics when doing even the most basic diagnosis; unfortunately X freezes and the laptop reboots without giving me a change to do much. > In the meantime there are two things you can do: > > a) if you do not need IPv6 you may use FAST_IPSEC which worked for me > b) re-enable all debugging and perhaps let me know if you can see > messages like: > Invalid policy for PCB -559038242 (0xdeadc0de) I've seen this on bootup