From: "Eric Plikuhn" <ericgate@imagestream-is.com>
To: netfilter@lists.samba.org
Subject: Need to NAT incomming packets
Date: Wed, 12 Jun 2002 15:31:57 -0500 [thread overview]
Message-ID: <011e01c21250$32829ee0$cd64a8c0@imagestream.com> (raw)
I trying to determine if the following can be done. I've searched for a
solution but can not find it... because most people are not forced to
attempt this.
Here is the scenario:
Site A 10.0.0.0/8
||
||
Core Router==========Internet
||
||
Site B 10.0.0.0/8
My problem is that the Site A and B router don't/can't do NAT. The second
problem is that they MAY be using the same IP addresses at both sites. Each
site was giving the 10.0.0.0/8 private network to do work with and they have
IP address all over it.
I was hoping have a SNAT rule for each incoming interface in the prerouting
chain on the Core router.... but you can't do SNAT in prerouting with
iptables.
I'm thought of a few possibilities, but so far they all fall short.
Assuming that I can't get new routers at the Site locations and they may be
using the same IP's what can I do?
Eric
next reply other threads:[~2002-06-12 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 20:31 Eric Plikuhn [this message]
2002-06-13 21:38 ` Need to NAT incomming packets Nathan Cassano
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='011e01c21250$32829ee0$cd64a8c0@imagestream.com' \
--to=ericgate@imagestream-is.com \
--cc=netfilter@lists.samba.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