From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Chris Lyon <cslyon@netsvcs.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: NAT issues on a VPN tunnel
Date: Tue, 02 Nov 2004 11:09:04 -0500 [thread overview]
Message-ID: <1099411744.2031.10.camel@localhost> (raw)
In-Reply-To: <CARBON45GHEer27k2Ht000021de@carbon.netsvcs.com>
On Tue, 2004-11-02 at 10:40, Chris Lyon wrote:
> So, I am trying to use NAT to solve the problem below because of an IP
> addressing conflict issue but I am not having much luck. Basically all of
> the Site A needs to get to only a few devices at each site B&C so I am
> trying to do PREROUTING NAT on the far end systems. I have the tunnels up
> and I can see the traffic getting to the remote side on ipsec0 but I just
> can't get it to NAT from the 1.1.1.1 to the real 10.10.1.1.
>
> Command that I think should work
> iptables -t nat -A PREROUTING -i ipsec0 -d 1.1.1.1 -j DNAT --to 10.10.10.10
> iptables -t nat -A POSTROUTING -o ipsec0 -s 10.10.10.10 -j SNAT --to 1.1.1.1
>
>
> Any ideas? Layout and configs are below.
>
>
> Site A eth0 - 192.168.254.0/24--Internet--Site B eth0 - 10.10.0.0/16
> \ NAT FROM 1.1.1.1 10.10.1.1
> example
> \--Internet--Site C eth0 -
> 10.10.0.0/16
> NAT FROM 1.1.2.1 10.10.1.1
> example
>
>
> So here is the openswan configurations for your reference:
>
> Site A
>
> conn site_a-to-site_b
> #---------(local side is left side)
> left=<public site a>
> leftsubnet=192.168.254.0/24
> leftnexthop=%defaultroute
> #---------(remote side is right side)
> right=<public site b>
> rightsubnet=1.1.0.0/16
> #---------Auto Key Stuff
> pfs=yes
> auth=esp
> authby=secret
> esp=3des-md5-96
> keylife=8h
> keyingtries=0
>
>
> Site B
>
> conn site_b-to-site_a
> #---------(local side is left side)
> left=<public site b>
> leftsubnet=1.1.0.0/16
> leftnexthop=%defaultroute
> #---------(remote side is right side)
> right=<public site a>
> rightsubnet=192.168.254.0/24
> #---------Auto Key Stuff
> pfs=yes
> auth=esp
> authby=secret
> esp=3des-md5-96
> keylife=8h
> keyingtries=0
This looks terribly familiar. Is this an old post come back to life or
was it on one of the *swan lists? I thought we left off with some
discussion of where to do the NAT and that the basic set up described
should work but were unsure about how you knew the packets were not
being NATd correctly. I don't recall a reply after that. Take care -
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-11-02 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 15:40 NAT issues on a VPN tunnel Chris Lyon
2004-11-02 16:09 ` John A. Sullivan III [this message]
2004-11-02 17:02 ` Chris Lyon
2004-11-02 18:49 ` John A. Sullivan III
2004-11-02 20:05 ` Chris Lyon
2004-11-03 0:27 ` John A. Sullivan III
2004-11-03 0:24 ` Jason Opperisano
2004-11-03 15:06 ` Michael Gale
-- strict thread matches above, loose matches on Subject: below --
2004-11-03 0:35 Christopher Lyon
2004-11-03 2:43 ` Jason Opperisano
2004-11-03 10:48 ` John A. Sullivan III
[not found] ` <CARBONunxtkVO4alvoN00002350@carbon.netsvcs.com>
2004-11-03 15:49 ` Jason Opperisano
2004-11-05 6:42 ` Chris Lyon
2004-11-05 10:40 ` John A. Sullivan III
2004-11-05 16:44 ` Chris Lyon
2004-11-05 16:57 ` 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=1099411744.2031.10.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=cslyon@netsvcs.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 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.