> Using EigerSteinBeta2. I want to add IPSec support, to connect to a
> Cisco Pix firewall. On Charles's IPSec page
> (http://lrp.steinkuehler.net/Packages/ipsec1.5.htm#DOWNLOAD), there are
> 3 IPSec-enabled kernels listed.
>
> 1. I can figure out what a floppy-only, and an IDE-enabled kernel is.
> But what's a "full Eiger"? What does it add, that the others don't?
IDE+ (supports bus-mastering and some other fancy IDE features, rather than
plain vanilla programmed I/O). You don't really need this unless you're
using the IDE drive 'live' in the system (like for web pages or
something)...
I think there are a few other things enabled (like NFS).
Unless you're trying to get something to work and know kernel support for it
is missing, you should be just fine with the floppy-only or IDE kernel.
> 2. Are these kernels different from the ones here?
> http://lrp.steinkuehler.net/files/kernels/2.2.16-1-VPNMasq/
Yes. The previous include KLIPS (Kernel Level IPSec) support, required for
FreeS/WAN (running IPSec on your router/firewall). The VPNMasq kernel
includes support for masquerading IPSec (running IPSec on a machine on your
internal network).
> 3. Do I use the modules from the page above with a kernel from the IPSec
> page?
Use standard Eiger moduels with the IPSec kernels. Use the VPNMasq modules
with the VPNMasq kernel.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
