From: "Peter Marshall" <peter.marshall@caris.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: to snat or to dnat .. that is the question
Date: Tue, 1 Jun 2004 11:30:06 -0300 [thread overview]
Message-ID: <145d01c447e4$ef8d31a0$49caa8c0@caris.priv> (raw)
Hi again.
I am at a bit of a quandary, and am not sure what to do.
Let the external interface on my firewall be 100.100.100.100
I have an internal box; 192.168.0.20 that needs to connect to an external
box 200.200.200.200 on port 2000.
I want the internal box to connect to hit my firewall on a different port ..
say 15000
so basically
start: .... -s 192.168.0.20 -d 200.200.200.200 --dport 15000
after firewall -s 100.100.100.100 -d 200.200.200.200 --dport 2000
How can I do this ?
I started out with:
$IPT -t nat -A POSTROUTING -d 200.200.200.200 --dport 15000 -p tcp -i eth0 \
-j SNAT --to-source 100.100.100.100
But this does not change the destination port (obviously). I thought about
doing the following
$IPT -t nat -A PREROUTING -d 100.100.100.100 --dport 15000 -p tcp -i eth0 \
-j DNAT --to-destination 200.200.200.200 --dport 2000
However, I don't think that this will change my source address. Also, will
this even forwarded the packets ? They would be coming on the input chain
would they not ?
Thank you for the help.
Peter Marshall
Peter Marshall, BCS
Network Administrator, CARIS
115 Waggoners Lane, Fredericton NB, E3B 2L4 CANADA
Phone: (506) 458-8533 (Reception)
next reply other threads:[~2004-06-01 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 14:30 Peter Marshall [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-01 14:42 to snat or to dnat .. that is the question Piszcz, Justin Michael
2004-06-01 14:51 ` Peter Marshall
2004-06-01 15:16 ` Alistair Tonner
2004-06-01 16:27 ` Peter Marshall
2004-06-01 17:50 ` Alistair Tonner
2004-06-01 17:12 Daniel Chemko
2004-06-01 17:30 ` Peter Marshall
2004-06-01 17:52 ` Alistair Tonner
2004-06-01 17:38 Daniel Chemko
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='145d01c447e4$ef8d31a0$49caa8c0@caris.priv' \
--to=peter.marshall@caris.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