From: Leandro Melo de Sales <leandroal@gmail.com>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Nat types implemented by IPTABLES - STUN issue
Date: Thu, 6 Jan 2005 03:08:20 -0300 [thread overview]
Message-ID: <5bc4c45705010522084d524973@mail.gmail.com> (raw)
In-Reply-To: <876ef97a05010517193799cae6@mail.gmail.com>
Hi....
So, I can't understand. The STUN RFC says that STUN doesn't support
Symmetric nat. I'm behind a iptables firewall with nat for UDP packets
and I can run some tests successfully. Are you sure that iptables just
cover symmetric nat? If yes, I really need to check that situation.
Leandro.
On Wed, 5 Jan 2005 20:19:43 -0500, Tobias DiPasquale
<codeslinger@gmail.com> wrote:
> On Wed, 5 Jan 2005 16:28:42 -0300, Leandro Melo de Sales
> <leandroal@gmail.com> wrote:
> > I'm using an implementation for STUN (RFC 3489:
> > http://www.faqs.org/rfcs/rfc3489.html) written in JAVA
> > (http://stun4j.dev.java.net/).
> > In this RFC, they describes some nats variations (see STUN RFC
> > chapter 5) some of them supported by STUN specification, like: Full
> > Cone, Restricted Cone, Port Restricted Cone and Symmetric.
> > So, I have a simple question for iptables developers: what types of
> > nat iptables supports?
>
> Symmetric only.
>
> --
> [ Tobias DiPasquale ]
> 0x636f6465736c696e67657240676d61696c2e636f6d
>
prev parent reply other threads:[~2005-01-06 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 19:28 Nat types implemented by IPTABLES - STUN issue Leandro Melo de Sales
2005-01-06 1:19 ` Tobias DiPasquale
2005-01-06 6:08 ` Leandro Melo de Sales [this message]
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=5bc4c45705010522084d524973@mail.gmail.com \
--to=leandroal@gmail.com \
--cc=netfilter-devel@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.