Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Victor Julien <victor@nk.nl>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: vpn under linux
Date: Sat, 10 Apr 2004 11:47:02 +0200	[thread overview]
Message-ID: <200404101147.02347.victor@nk.nl> (raw)
In-Reply-To: <200404101018.38664.Antony@Soft-Solutions.co.uk>

On Saturday 10 April 2004 11:18, Antony Stone wrote:
> PPP is Point-to-Point Protocol, and has almost nothing to do with VPNs :)
>
> SSH is Secure Shell, and at least it contains some encryption, but again,
> is almost nothing to do with VPNs (but more on that later).
>
> PPTP is Pretty Poor Tunneling Protocol (oh, no, sorry, it's a Point to
> Point Tunneling Protocol...), and is the way Microsoft systems do VPN.
>
> The "standard" way to do VPN (in other words, the method which is supported
> by most vendors, uses open standards, and also has the best security) is
> IPsec.
>
> The usual way to do IPsec under Linux is to use FreeS/WAN under kernel 2.4,
> or the built-in IPsec under kernel 2.6.
>
> I use FreeS/WAN, I like it, it works well with netfilter (once you've got
> used to the path the packets take at each end), and I'm happy with its
> 3DES/RSA security.
>
> I said I'd mention more about SSH - that also uses good encryption and is
> therefore secure, and once you have an SSH connection between two machines,
> you can "tunnel" almost any network traffic you like between them, and it
> does work, although I wouldn't select this as a first choice for a VPN
> because there's a lot more manual setting up involved.   IPsec is more like
> a network route - you just configure it, and let the two endpoint machines
> get on with negotiating the link, and then computers from whichever network
> ranges you've configured the VPN to support can connect to each other
> transparently through a nice secure tunnel across the Internet.
>

You can also take a look at OpenVPN (http://openvpn.sourceforge.net). It's 
quite easy to set up, is crossplatform and can be made transparant. Also, it 
doesn't require kernel modification.

Regards,
Victor


> Hope this helps,
>
> Regards,
>
> Antony.



  parent reply	other threads:[~2004-04-10  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  9:01 vpn under linux Gianni Pucciani
2004-04-10  9:18 ` Antony Stone
2004-04-10  9:31   ` Gianni Pucciani
2004-04-10  9:44     ` Antony Stone
2004-04-10  9:41   ` Gianni Pucciani
2004-04-10 10:00     ` Antony Stone
2004-04-10 10:15       ` Gianni Pucciani
2004-04-10 23:41       ` Alexander Samad
2004-04-11  0:09         ` Aaron P. Martinez
2004-04-12 12:25         ` Scott MacKay
2004-04-12 16:01           ` John A. Sullivan III
2004-04-12 18:58             ` Dick St.Peters
2004-04-10  9:47   ` Victor Julien [this message]
2004-04-10 12:30 ` John A. Sullivan III
2004-04-10 17:23   ` Tony Earnshaw

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=200404101147.02347.victor@nk.nl \
    --to=victor@nk.nl \
    --cc=netfilter@lists.netfilter.org \
    /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