Date: Fri, 19 Dec 2003 20:32:02 +1100 From: Rudolph Pereira <memetical@yahoo.com.au> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: current@freebsd.org Subject: Re: Possible IPsec Trouble in 5.2RC? Message-ID: <20031219093202.GB669@starfleet.org.au> In-Reply-To: <Pine.BSF.4.53.0312190745410.49580@e0-0.zab2.int.zabbadoz.net> References: <20031219064932.GA94971@blossom.cjclark.org> <Pine.BSF.4.53.0312190745410.49580@e0-0.zab2.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031219093202.GB669>