From: Jason White <jdw-netfilter@jdwhite.org>
To: netfilter@lists.netfilter.org
Subject: Re: Forcing source port with NAT
Date: Mon, 23 Jun 2003 16:44:22 -0500 [thread overview]
Message-ID: <20030623214422.GC28900@jdwhite.org> (raw)
In-Reply-To: <20030623200247.GB28900@jdwhite.org>
On Mon, Jun 23, 2003 at 03:02PM -0500, Jason White wrote:
[...]
>Basically, I need to ensure that anything coming in on 200.200.200.200:2104
>goes to 10.0.0.2:2104 and anything going out from 10.0.0.2:2104 goes out
>200.200.200.200:2104.
[...]
Answering my own post, the following worked:
iptables -t nat -A POSTROUTING -p udp -s 10.0.0.2 --sport 2104 -j SNAT
--to 200.200.200.200:2104
--
Jason White (jdw-netfilter@jdwhite.org) http://www.jdwhite.org/~jdwhite
Jabber:jdwhite@jabber.org IRC:irc.netbsd.org/{jdwhite,jdw}
AIM:jdwhite90125 Yahoo:jdwhite89 ICQ:9295078 MSN:jdwhite89@hotmail.com
GPG KeyID: 0x74CF850D/1F57 465A 1357 BA39 2BEF 5629 6E1C 2B20 74CF 850D
next prev parent reply other threads:[~2003-06-23 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 20:02 Forcing source port with NAT Jason White
2003-06-23 21:44 ` Jason White [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 19:54 Jason White
2003-06-24 15:37 ` Ramin Dousti
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=20030623214422.GC28900@jdwhite.org \
--to=jdw-netfilter@jdwhite.org \
--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