linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: John Covici <covici@ccs.covici.com>
Subject: Re: 2.4.0 kernels and vpn
Date: Fri, 22 Dec 2000 01:42:41 +0100	[thread overview]
Message-ID: <20001222014241.I7400@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <20001222012105.G7400@garloff.etpnet.phys.tue.nl> <Pine.LNX.4.21.0012211924100.2739-100000@ccs.covici.com>
In-Reply-To: <Pine.LNX.4.21.0012211924100.2739-100000@ccs.covici.com>; from covici@ccs.covici.com on Thu, Dec 21, 2000 at 07:25:18PM -0500

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On Thu, Dec 21, 2000 at 07:25:18PM -0500, John Covici wrote:
> Excuse my ignorance, but what is cipe?

CIPE = Crypto IP Encapsulation.
See
http://sites.inka.de/~W1011/devel/cipe.html

Some version of cipe is in the kerneli patches:
ftp://ftp.YOURCOUNTRY.kernel.org/pub/linux/kernel/people/astor/

I'd recommend using FreeS/WAN, though as it's a standardized solution,
even offering interoperability with other OSes.

> Also, I received a comment that all I had to do was enable gre
> tunneling, is this correct?

This does not give you the P from VPN.

Regards,
-- 
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-12-22  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-21 18:40 2.4.0 kernels and vpn John Covici
2000-12-22  0:21 ` Kurt Garloff
2000-12-22  0:25   ` John Covici
2000-12-22  0:42     ` Kurt Garloff [this message]
2000-12-22  2:42     ` Michael Peddemors
2000-12-23  7:48 Bernd Eckenfels

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001222014241.I7400@garloff.etpnet.phys.tue.nl \
    --to=garloff@suse.de \
    --cc=covici@ccs.covici.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).