From: Michael Gale <michael.gale@utilitran.com>
To: Chris Lyon <cslyon@netsvcs.com>, netfilter@lists.netfilter.org
Subject: Re: NAT issues on a VPN tunnel
Date: Wed, 03 Nov 2004 08:06:31 -0700 [thread overview]
Message-ID: <4188F3F7.3020305@utilitran.com> (raw)
In-Reply-To: <CARBON45GHEer27k2Ht000021de@carbon.netsvcs.com>
Hello,
Before you start adding in customer NAT rules are you sure that end
point to end point work ?
If the VPN device is setup on the gw box or the router has a route of
the network on the other side of the VPN you will not need to NAT any
traffic.
We have a VPN device plugged into a production network at a IDC, the
default gw is the firewall, not the VPN device and we did not want to
add a static route on the firewall. So on the VPN device, we SNAT all
packets that leave that machine to it's local IP. That way all
connections that come in from the VPN look like they came from the VPN
device.
Michael.
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
>
>
>
>
>
>
>
--
Michael Gale
Lan Administrator
Utilitran Corp.
We Pledge Allegiance to the Penguin
next prev parent reply other threads:[~2004-11-03 15:06 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
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 [this message]
-- 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=4188F3F7.3020305@utilitran.com \
--to=michael.gale@utilitran.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.