CIPE requirements
On Wednesday 14 March 2001 10:36, you wrote:
> On Wednesday 14 March 2001 18:15, you wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > A long time ago, in a galaxy far, far way, someone said...
> >
> > > Last question, can I use 2.2.14 kernel or do I need 2.4?
> >
> > Depends on your exact vpn implementation.
> >
> > IPsec won't work with 2.4.
> > Encryption on PPTP won't work with 2.4; unencrypted tunnels work fine
> > though.
> >
> > Both of those vpn mechanisms require some kernel patching, and those
> > patches aren't available for the 2.4.x series.
> >
> > Everyting else will work fine with either 2.2.x or 2.4.x. Hell, one side
> > could be 2.2.x and the other 2.4.x :)
> >
> > Oh, and I strongly recommend that you *not* use 2.2.14 - it has some
> > security holes and (iirc) disk curruption issues. I would also avoid
> > both 2.2.17 and 2.2.18 - 2.2.17 has performance problems, and they both
> > have problems with their VM sybsystems.
> >
> > If you go with 2.2.x, I recommend 2.2.16 or 2.2.19pre17. 2.2.16 has been
> > particularly stable for me.
> >
> > If you go with 2.4.x, you should go with 2.4.2 or 2.4.3 - 2.4.x been
> > particularly well-behaved, especially considering it's still early in the
> > 2.4.x lifecycle; 2.4.0 and 2.4.1 also have problems with disk corruption.
> >
> > - --
> > - ----------------------------------------------------------------------
> > Phil Brutsche pbrutsch@tux.creighton.edu
> >
> > GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC
> > GPG key id: 50DE1CFC
> > GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.4 (GNU/Linux)
> > Comment: For info see http://www.gnupg.org
> >
> > iD8DBQE6sCXM/ZTSZFDeHPwRAndPAJ48Wei/TcufMcVP4L8lk6espuNlYACfdMPK
> > Mvwv00HLaCy+hEewsQfl7wE=
> > =DSSz
> > -----END PGP SIGNATURE-----
>
I have a box w/ 2.2r2 installed w/ stock 2.2.14 kernel. I download the
cipe.tar and unzipped. Ran ./configure and got the message that there is
no suitable configured kernel include tree found.
What does that mean?
Do i need to install a kernel-image from deselect or comiple my own kernel in
/usr/src?
Sorry about the repeated emails. Hard to get support on these issues.
Nick
Reply to: