[Openswan Users]
Paul Wouters
paul at xelerance.com
Mon Feb 28 19:28:38 CET 2005
On Mon, 28 Feb 2005, panos wrote:
> To use KLIPS wouldn't we have to build a new kernel without the IPSEC
> stuff built in.
You can build both as modules, so you can use the same kernel image.
> What is NETKEY?...
CONFIG_NETKEY is the option for the included IPsec stack in 2.6. CONFIG_KLIPS
is the option for the openswan IPsec stack for 2.4 and 2.6
Paul
> -----Original Message-----
> From: Marcus Leech [mailto:mleech at nortel.com]
> Sent: Monday, February 28, 2005 10:14 AM
> To: Paul Wouters
> Cc: panos; users at openswan.org
> Subject: Re: [Openswan Users]
>
> I'm using FC3 with 2.6.10-1.766 kernel. I couldn't get KLIPS to work
> beyond the most superficial definition of "work". I had to revert to
> NETKEY, which has its own problems--like you can only do one
> cycle of connection up/down, between restarts of OpenSwan. [The EAGAIN
> problem we were discussing].
>
> Paul Wouters wrote:
>
> > On Mon, 28 Feb 2005, panos wrote:
> >
> >> Basically I am trying to setup a simple tunnel in manual mode. This
> >> worked on 2.4 kernel (RH9) and openswan-2.2.0. I am now trying the
> same
> >> config under FC3 openswan-2.3.0 and its not working.
> >
> >
> > Manual keying is very likely broken with Openswan when using NETKEY.
> The
> > most sensible thing is not to use manual keying, but automatic keying.
> If
> > you really insist on manual keying despite the strong recommendation
> to
> > switch, try using KLIPS instead of NETKEY.
> >
> > Paul
> > _______________________________________________
> > Users mailing list
> > Users at openswan.org
> > http://lists.openswan.org/mailman/listinfo/users
> >
> >
>
More information about the Users
mailing list