From: Sven Burgener <sburgener@objeng.ch>
To: netfilter@lists.netfilter.org
Subject: Re: iptables abilities
Date: Fri, 23 Jan 2004 11:23:38 +0100 [thread overview]
Message-ID: <4010F62A.7090403@objeng.ch> (raw)
In-Reply-To: <200401230911.08584.Antony@Soft-Solutions.co.uk>
Antony Stone wrote:
> The only reason you can't route private addresses across the Internet is that
> all ISP routers drop packets sent to these address ranges.
Right.
> You would set up your VPN system to forward these packets, just the same as
> you can set up your own firewalls and routers to forward them if you want to.
>
> A VPN with two RFC1918 ranges at each end is a very common setup.
Yes, indeed.
My question, though, is how can a connection be established between two
parties where one of them has a private address (A) and where you want
to connect _to_ the server having the private address (A, see below).
The problem is, you can't establish a connection to the private address
(A), so there has to be a means of 'hijacking' the established session
(from X, see diagram below).
(Internet) (Internet)
A <------------> X <------------> B
A: 192.168.X.X
B: 192.168.X.X
X: public IP address
The end result is to get from B to A, securely.
Cheers
Sven
next prev parent reply other threads:[~2004-01-23 10:23 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
2004-01-23 9:11 ` Antony Stone
2004-01-23 10:23 ` Sven Burgener [this message]
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=4010F62A.7090403@objeng.ch \
--to=sburgener@objeng.ch \
--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