Date: Sat, 15 Jul 2000 01:15:27 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Mark Huizer <freebsd@dohd.cx> Cc: current@freebsd.org Subject: Re: -current, racoon, ipsec Message-ID: <Pine.BSF.4.21.0007150113570.9429-100000@freefall.freebsd.org> In-Reply-To: <20000715100700.A80703@dohd.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Jul 2000, Mark Huizer wrote:
> > > Grr... ok, that might be solved when putting IPSEC in the kernel config,
> > > but the second part still stands, I guess. (Why include libipsec code
> > > when it is in the base tree... they should be compatible)
> > Just use the port. I presume the included copy of ipsec is there for other
> > platforms.
> Which coredumps when there is no matching SPD in the list, but
> well,that's minor. The other thing is that I haven;t gotten a single
> encrypted session to work, but that will wait until after the holiday :)
You should *definitely* talk to the KAME guys with any bugs you find in
racoon. I have a couple of problems I discovered in my testing tonight
prior to the 4.0 merge, and there are still 5 days until the ports freeze
in which to correct them. *Any* help you can give to sumikawa-san will
mean a better IPSEC-enabled 4.1-RELEASE.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007150113570.9429-100000>