From owner-freebsd-current Sat Jul 15 1:15:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CD8B137BC11; Sat, 15 Jul 2000 01:15:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA09549; Sat, 15 Jul 2000 01:15:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 15 Jul 2000 01:15:27 -0700 (PDT) From: Kris Kennaway To: Mark Huizer Cc: current@freebsd.org Subject: Re: -current, racoon, ipsec In-Reply-To: <20000715100700.A80703@dohd.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message