Date: Tue, 28 Aug 2007 16:03:09 +0200 From: "Pawel Worach" <pawel.worach@gmail.com> To: "gnn@freebsd.org" <gnn@freebsd.org> Cc: current@freebsd.org Subject: Re: IPSec panics Message-ID: <d227e09e0708280703t6ef6e399ucbeda48abf7b02e2@mail.gmail.com> In-Reply-To: <m2wsvfu6ne.wl%gnn@neville-neil.com> References: <46D2EB88.7020905@gmail.com> <m2wsvfu6ne.wl%gnn@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/28/07, gnn@freebsd.org <gnn@freebsd.org> wrote: > At Mon, 27 Aug 2007 17:19:36 +0200, > Pawel Worach wrote: > > > > Hi, > > > > While testing IPSec I got this panic on two different -CURRENT systems. > > I think they happened when racoon was updating the SAD. kernel.debug and > > vmcore is still available if more info needed. > > > > Given the backtraces you showed I didnt' see any IPsec related code > being run. Did I miss something? > Come to think of it.. this case was that I had a ssh session to the peer when there was no policy loaded and the peer paniced when setkey -f ipsec.conf was executed so the existing connection now suddenly would require IPSec. Am I making any sense at all ? -- Pawel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d227e09e0708280703t6ef6e399ucbeda48abf7b02e2>