Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Sven Burgener <sburgener@objeng.ch>
To: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables abilities
Date: Fri, 23 Jan 2004 09:59:15 +0100	[thread overview]
Message-ID: <4010E263.1080902@objeng.ch> (raw)
In-Reply-To: <1089.12.75.166.13.1074782849.squirrel@nmibwkrf1.nexusmgmt.com>

Dear John

John A. Sullivan III wrote:
> Is there any point at which you could use DNAT/SNAT to change each private
> address to a public address? Alternately, can you build a VPN tunnel
> between the two and tunnel the private addresses through the tunnel?

Perhaps a VPN tunnel would be the best solution. How would such a thing 
be established though, given that both A and B have private addresses?

The two connections between A <--> X and X <--> B need to somehow be 
interconnected. Can this be done with VPN?

>>>>         (Internet)       (Internet)
>>>>     A <------------> X <------------> B
>>>>
>>>>A: 192.168.1.13
>>>>B: 192.168.1.99
>>>>X: public IP address

Cheers
Sven


  reply	other threads:[~2004-01-23  8:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 12:21 iptables abilities Sven Burgener
2004-01-22 12:33 ` Antony Stone
2004-01-22 13:50   ` Sven Burgener
2004-01-22 14:47     ` John A. Sullivan III
2004-01-23  8:59       ` Sven Burgener [this message]
2004-01-23  9:11         ` Antony Stone
2004-01-23 10:23           ` Sven Burgener
2004-01-23 10:38             ` Antony Stone
2004-01-23 13:33             ` John A. Sullivan III
2004-01-23 16:09               ` Antony Stone
2004-01-23 16:39                 ` Sven Burgener
2004-01-23 16:48                   ` Antony Stone
2004-01-22 12:36 ` David Cannings
  -- strict thread matches above, loose matches on Subject: below --
2004-01-23 19:48 bmcdowell
2004-01-23 20:02 ` Antony Stone

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=4010E263.1080902@objeng.ch \
    --to=sburgener@objeng.ch \
    --cc=john.sullivan@nexusmgmt.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