From: "Emiel Mols" <emiel@fulgor-hosting.nl>
To: "'John A. Sullivan III'" <john.sullivan@nexusmgmt.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: RE: IPSEC and NAT
Date: Sat, 16 Oct 2004 00:03:44 +0200 [thread overview]
Message-ID: <E1CIaAp-0006Vi-00@deer.gmane.org> (raw)
In-Reply-To: <1097877726.2771.47.camel@localhost>
Well, I only control one end of the link :). This one ip address is assigned
to me and I have to find a way to NAT it :(.
netfilter-devel@lists.netfilter.org
-----Original Message-----
From: John A. Sullivan III [mailto:john.sullivan@nexusmgmt.com]
Sent: zaterdag 16 oktober 2004 0:02
To: Emiel Mols
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: IPSEC and NAT
On Fri, 2004-10-15 at 14:00, Emiel Mols wrote:
> Hi,
>
>
>
> I've managed to setup a host-to-net ipsec connection with a remote network
> on a linux router using (ported) isakmpd and kernel 2.6.8.1. However, I
want
> to be able to 'share' this ipsec connection with the rest of the network,
> but since no ipsecn virtual interface is created in the 2.6 kernels I
can't
> use ordinary SNAT/MASQUERADE targets in iptables: ipsec packets get
> encrypted before entering the POSTROUTING table :(, so the source address
of
> the encapsulated packet can't be changed anymore. I've read
>
http://lists.netfilter.org/pipermail/netfilter-devel/2004-January/thread.htm
> l#13879, but the supplied patch doesn't work very well.
>
>
>
> Does anyone have any suggestions on how to get this working?
<snip>
I may be a bit tired at the end of a long week and have thus missed your
point . . . but why not set it up as a net-to-net connection? - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-10-15 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410151800.i9FI09Mc018462@nmibwkms1.nexusmgmt.com>
2004-10-15 22:02 ` IPSEC and NAT John A. Sullivan III
2004-10-15 22:03 ` Emiel Mols [this message]
2004-10-16 1:18 ` Alexander Samad
[not found] <200410160653.i9G6rmMc025506@nmibwkms1.nexusmgmt.com>
2004-10-16 14:59 ` John A. Sullivan III
[not found] <200410152203.i9FM3kMc029703@nmibwkms1.nexusmgmt.com>
2004-10-16 2:09 ` John A. Sullivan III
2004-10-16 6:53 ` Emiel Mols
2004-10-15 18:00 Emiel Mols
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=E1CIaAp-0006Vi-00@deer.gmane.org \
--to=emiel@fulgor-hosting.nl \
--cc=john.sullivan@nexusmgmt.com \
--cc=netfilter-devel@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.