<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY style="FONT: 10pt Courier New; COLOR: #000000" leftMargin=5 topMargin=5>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>I am currently in the process of setting up a VPN between linux and
win2k.</DIV>
<DIV>After reading many howtos, forums and mailinglists I decided to use
Openswan</DIV>
<DIV>and Debian.</DIV>
<DIV> </DIV>
<DIV>I was told that Kernel 2.4 would be a good idea as Klips is the
better</DIV>
<DIV>known solution and works just fine. I was also told that I don't have</DIV>
<DIV>to touch the Kernel if I use a Debian 2.4.26 as it has native IPSec.</DIV>
<DIV> </DIV>
<DIV>This is where my trouble begins. If 2.4.26 has backported IPSec, I can't
</DIV>
<DIV>use Klips, but have to use Setkey, right?</DIV>
<DIV> </DIV>
<DIV>./ipsec verify returns that Ipsec native is installed and that setkey is
ok.</DIV>
<DIV> </DIV>
<DIV>I tried to follow Nate Carlsons howto, where he says "If you use 2.4.26
</DIV>
<DIV>you don't have to touch the kernel", but from then on he only
describes</DIV>
<DIV>ipsec.conf, which would be the configuration for Klips.... ack.</DIV>
<DIV> </DIV>
<DIV>
<DIV>I would like to use Klips as it is better documented, and because the
Ipsec-Tools</DIV>
<DIV>for Windows use the same syntax for the configuration.</DIV>
<DIV> </DIV></DIV>
<DIV>I hope you can help a rather confused "vpn-newbie"
;)</DIV></BODY></HTML>