mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ratheesh k <ratheesh.ksz@gmail.com>
To: 飞颜 <win847@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPv4 NAT UDP Traversal issue
Date: Tue, 20 Apr 2010 08:32:02 +0530	[thread overview]
Message-ID: <j2ocfeab66d1004192002z8fd0b6acx52da44ca3210dc5f@mail.gmail.com> (raw)
In-Reply-To: <k2w363172901004191854t72fa19fahdb93fa498b23fcf6@mail.gmail.com>

2010/4/20 飞颜 <win847@gmail.com>:
> Dear all,
>
>       I have a question about Linux NAT, our Product is ADSL
> Router(Linux Version is 2.6.22.15), and Now our customers requirment
> is below:
>
>       IPv4 Nat: UDP Traversal through NAT, must support STUN
> (RFC3489)  the four ways: Full Cone、Restricted Cone、Port Restricted
> Cone and Symmetric
>
>       As I known, netfilter IPv4 NAT is belonged to Symmetric type.
> and if want UDP Traversal through NAT, NAT Device can not be Port
> Restricted Cone and Symmetric type if the other is Symmetric type.
>
>       So my question is: Can iptable set the UDP NAT converted to
> Full Cone or Restricted Cone type?
>
>       we now set NAT use iptables below:
>
> Chain POSTROUTING (policy ACCEPT)
> target     prot opt source               destination
> MASQUERADE  all  --  anywhere             anywhere
>
>       Thanks very much!
>
> BR,
> win847
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

There is a dedicated mailing list for netfilter .
                      netfilter-users

      reply	other threads:[~2010-04-20  3:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <k2s363172901004182032zea2277b4s40e55ae436d2353e@mail.gmail.com>
2010-04-20  1:54 ` 飞颜
2010-04-20  3:02   ` ratheesh k [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=j2ocfeab66d1004192002z8fd0b6acx52da44ca3210dc5f@mail.gmail.com \
    --to=ratheesh.ksz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=win847@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®