Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: UDP nat question
Date: Tue, 19 Apr 2005 08:03:15 -0400	[thread overview]
Message-ID: <20050419120315.GA19248@bender.817west.com> (raw)
In-Reply-To: <4263C3A2.70006@inescporto.pt>

On Mon, Apr 18, 2005 at 03:26:42PM +0100, Filipe Abrantes wrote:
> Hi all,
> 
> I have a basic question about iptables UDP NAT.
> 
> Imagine that you have 2 UDP sessions in your private LAN using the same 
> port. How does iptables nat these connections? One of the sessions will 
> get one external port of the NAT machine and the other session will get 
> another one? Does the usual MASQUERADE command suffice to achieve this?

if you're talking about two machines in the inside network making
outbound connections to the same UDP port; for example 53, then (a) it's
highly unlikely that both connections will use the same source port and
(b) yes--each machine gets its srcip:sport re-mapped to the iptables
machine's pubip:mappedsrcport.  remember that connection-tracking uses
four values to match a connection:

  src ip, src port, dst ip, dst port

> iptables MASQUERADE command:
> 
> $IPTABLES -t nat -A POSTROUTING -o $OUTBOUND_IFACE -j MASQUERADE

sure.

> Hope I have made myself clear and,

not really--because i'm guessing your actual question is about something
infinitely more complicated that will come out after much dancing
around...maybe i'm wrong.

-j

--
"Lois: Peter, there's a naked man on this cake.
 Peter: There were only two cakes left, and trust me, you do not want
 the one of Al Roker with the Hershey Kiss nipples."
        --Family Guy


  reply	other threads:[~2005-04-19 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 14:26 UDP nat question Filipe Abrantes
2005-04-19 12:03 ` Jason Opperisano [this message]
2005-04-19 13:31 ` Daniel Lopes
  -- strict thread matches above, loose matches on Subject: below --
2005-04-20 16:11 Filipe Abrantes
2005-04-21 12:17 ` Damjan
2005-04-21 18:02 ` Taylor, Grant

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=20050419120315.GA19248@bender.817west.com \
    --to=opie@817west.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