[Openswan Users] Debian 2.4.26 and Openswan 2.1.3

[David Clymer]

Thus quoth t.henneberger at hcs-computer.de:
> To: users at lists.openswan.org
> From: t.henneberger at hcs-computer.de
> Subject: Re: [Openswan Users] Debian 2.4.26 and Openswan 2.1.3
> 
> >> T. Henneberger and 
> > D. Clyme wrote:
> 
> > > This is where my trouble begins. If 2.4.26 has backported IPSec, I can't 
> > > use Klips, but have to use Setkey, right?
> > 
> > Dont worry about setkey. Just use openswan in the normal fashion.
> > 
> > > 
> > > /ipsec verify returns that Ipsec native is installed and that setkey is ok.
> > > 
> > > I tried to follow Nate Carlsons howto, where he says "If you use 2.4.26 
> > > you don't have to touch the kernel", but from then on he only describes
> > > ipsec.conf, which would be the configuration for Klips.... ack.
> > > 
> > 
> > You configure openswan for klips and native the same way, except you
> > dont need to define virtual interface mappings for native ipsec
> > (for example: interfaces="ipsec0=eth0 ipsec1=eth1" or whatever the
> > syntax is). 
> > -davidc
> 
> Hello David
> 
> I don't think I can follow you there ;) You mean I can use my 2.4.26 Kernel 
> and just configure my ipsec.conf and ipsec.secrets as described for Klips?

Yes. Configuration of openswan is pretty much the same regardless of
whether you use KLIPS or native.

-davidc