All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter@lists.netfilter.org
Subject: Re: VPN over netfilter NAT
Date: Thu, 16 Sep 2004 09:36:05 -0500	[thread overview]
Message-ID: <4149A4D5.2010209@pbl.ca> (raw)
In-Reply-To: <200409161436.26695.apapadop@alumni.carnegiemellon.edu>

Alexandros Papadopoulos wrote:
> I stumbled across 
> http://www.linuxhomenetworking.com/linux-adv/vpn-linux.htm today, which 
> states that "NAT breaks VPNs".
> 
> Is this just an over-simplifying statement that really means "if you're 
> reading this, then don't even try setting up a NAT-traversing VPN"?

Yes and no.  Depends on what you mean by VPN.  VPN can be implemented in 
many different ways.  With IPSec implementation you may run into 
problems (some solvable, some not).  With user space daemon 
implementations such as OpenVPN or VTun, you shouldn't have any 
problems.  Basically it is good idea not to have VPN endpoints behind 
NAT (if possible, of course).

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


  parent reply	other threads:[~2004-09-16 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 11:36 VPN over netfilter NAT Alexandros Papadopoulos
2004-09-16 11:47 ` Brent Clark
2004-09-16 11:49 ` John A. Sullivan III
2004-09-16 12:00 ` OFFTOPIC: " Leonardo Rodrigues Magalhães
2004-09-16 12:30 ` Jason Opperisano
2004-09-16 14:36 ` Aleksandar Milivojevic [this message]
2004-09-16 17:11   ` Les Mikesell
2004-09-17  1:36 ` Kenneth Porter
2004-11-12 13:09 ` Peter Marshall
2004-11-12 13:54   ` Michel van der Klei

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=4149A4D5.2010209@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.