All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Olivier GRALL <olivier.grall@neotip.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [IPTABLES] Symmetric NAT?
Date: Sun, 16 Oct 2005 16:33:52 +0200	[thread overview]
Message-ID: <20051016143351.GC17257@rama.0sec> (raw)
In-Reply-To: <434FA046.8050708@neotip.com>

On Fri, Oct 14, 2005 at 02:10:46PM +0200, Olivier GRALL wrote:
> Hi,
> 
> I was making some tests with STUN when I realize that my NAT box was a simple Linux Box with an IPTABLES 
> rule with a MASQ target. What seemed strange to me was that the STUN result was "Port restricted cone ".
> 
> I made a new with NATcheck.exe... same result.
> http://midcom-p2p.sourceforge.net/
> 
> I was sure IPTABLES NAT was Symmetric and not Port restricted cone. What about it ?
> In the "Procceding of NetFilter Developer WorkShop 2004",  Harald Welte reported "
> 
> netfilter however implements (SNAT and MASQ) as ssymmetric.
> "

iptable_nat implements a fully symmetric port-overloading NAT.

-- 
- Harald Welte <laforge@netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

  reply	other threads:[~2005-10-16 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 12:10 [IPTABLES] Symmetric NAT? Olivier GRALL
2005-10-16 14:33 ` Harald Welte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-18  7:07 [IPTABLES] Symmetric NAT ? Olivier GRALL

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=20051016143351.GC17257@rama.0sec \
    --to=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=olivier.grall@neotip.com \
    /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.