Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Daniel Miller <dmiller@amfes.com>
To: netfilter@vger.kernel.org
Subject: Perform routing using NAT
Date: Thu, 16 Jan 2014 11:28:09 -0800	[thread overview]
Message-ID: <assp.10936facb6.52D832C9.20409@amfes.com> (raw)

I know there's a basic rule somewhere I'm just not grasping - please 
help me understand.

I have the following topology:
     1.  Windows PC on a LAN - for convenience assume is 192.168.1.x.  
Assume because this is a notebook and can/does connect from different 
points.
     2.  Windows PC has an OpenVPN connection to office Linux server.  
This is a routed connection - PC has address 10.59.97.8, and server is 
at 10.59.97.1.
     3.  There is a second VPN in place for customers.  This is 
172.27.x.x.  The server (same as 10.59.97.1) is at 172.27.0.1.
     4.  Customer has Linux server with VPN address of 172.27.0.10.

I need the Windows PC to reach the 172.27.0.10.  At this time, if I add 
a route to 172.27.0.0/16 via 10.59.97.1 on the Windows PC, and a route 
for 10.59.97.x via 172.27.0.1 on the remote customer's server - I can 
reach the remote server from the PC.  Interestingly - I can't ping the 
PC from the remote server.  I'd like to understand that - but it's not 
necessary communication as long as the PC can reach that remote server.

At this time, no iptables are running on either server.  But I'd like to 
be able to have the PC reach the remote server - without having to 
configure the routes as I've described.  What routing can I eliminate 
using NAT - and what combination of SNAT & DNAT is required?

-- 
Daniel


             reply	other threads:[~2014-01-16 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 19:28 Daniel Miller [this message]
2014-01-16 20:45 ` Perform routing using NAT Neal Murphy

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=assp.10936facb6.52D832C9.20409@amfes.com \
    --to=dmiller@amfes.com \
    --cc=netfilter@vger.kernel.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