From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: netfilter@lists.netfilter.org
Subject: Re: Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel
Date: Tue, 24 Aug 2004 13:46:45 +0800 [thread overview]
Message-ID: <012801c4899d$bd5e9660$0100a8c0@newlife> (raw)
In-Reply-To: 09D3F703EF3B0A4CBE28449EA9F3D32069F456@nicta-atp-mail.in.nicta.com.au
>
> I am trying to set up multiple ipsec VPN clients working behind a Linux
> router with NAT/PAT, based on a 2.4.20 (can be 2.4.22) kernel. I would
> like to be able to connect a number of Windows (2k or XP) machines to an
> existing Cisco VPN server.
>
> client 1 (ipsec) ---> | router |
> client 2 (ipsec) ---> | NAT/ |
> . PAT | -> ipsec VPN server (Cisco)
> . | |
> client 10 (ipsec) --->| |
>
Instead of making your VPN clients tunnel thru' Linux NAT router,
it would be better if you make the Linux NAT router perform
IPSEC VPN client functions with the Cisco ipsec VPN server
In the configuration I mention, you are effectively putting IPSEC
behind NAT, whereas to have IPSEC before NAT, that's a lot
more problematic.
next prev parent reply other threads:[~2004-08-24 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 5:11 Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel Roksana Boreli
2004-08-24 5:46 ` Ming-Ching Tiew [this message]
2004-08-24 7:32 ` Payal Rathod
2004-08-24 7:50 ` Ming-Ching Tiew
2004-08-24 8:53 ` bridge + transparent proxy ArioS
2004-08-24 9:31 ` Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel John A. Sullivan III
2004-08-26 9:13 ` Thomas Kirk
2004-08-26 10:39 ` John A. Sullivan III
2004-08-26 14:14 ` Tom Eastep
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 11:56 Jason Opperisano
2004-08-25 7:24 Roksana Boreli
2004-08-25 11:29 ` John A. Sullivan III
2004-08-25 11:44 Jason Opperisano
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='012801c4899d$bd5e9660$0100a8c0@newlife' \
--to=mingching.tiew@redtone.com \
--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