All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason White <jdwhite@jdwhite.org>
To: netfilter@lists.netfilter.org
Subject: Forcing source port with NAT
Date: Mon, 23 Jun 2003 14:54:59 -0500	[thread overview]
Message-ID: <20030623195459.GA28900@jdwhite.org> (raw)

Greetings,
  I have an application, Zephyr Messaging Service, which uses a client
application that sends out UDP packets on port 2104.  The Zephyr server
will refuse packets from the client if the source address is not 2104.
I want to run this application behind a NAT on one given machine.  I
need a way to ensure that packets from this one machine with a source
address of 2104 go through the NAT that they emerge on port 2104 of the
external ip address.  To diagram a packet:

[Intenal machine-10.0.0.2:2104] --> [NAT internal: 10.0.0.1] -->
  [NAT external: 200.200.200.200: 2104] --> ///internet/// ...

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.

I know how to map the external to internal, but internal to external
isn't immediately obvious

Thanks,
-Jason

-- 
Jason White (jdwhite@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


             reply	other threads:[~2003-06-23 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 19:54 Jason White [this message]
2003-06-24 15:37 ` Forcing source port with NAT Ramin Dousti
  -- strict thread matches above, loose matches on Subject: below --
2003-06-23 20:02 Jason White
2003-06-23 21:44 ` Jason White

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=20030623195459.GA28900@jdwhite.org \
    --to=jdwhite@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.