netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Tony Wan <visual2me@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: does NAT based on iptables support TCP hole punch?
Date: Wed, 10 Jun 2009 21:57:31 -0700	[thread overview]
Message-ID: <20090610215731.694c3661@nehalam> (raw)
In-Reply-To: <69b8237b0906102042q647797bdl88e16be088af6f45@mail.gmail.com>

On Thu, 11 Jun 2009 11:42:44 +0800
Tony Wan <visual2me@gmail.com> wrote:

> Hi all,
> 
> It's said that TCP hole punch does not work if both endpoints come
> from 2 sub-networks, whose NAT are both implemented by iptables. I
> just want to make sure whether this is true. If so, what type of nat
> can iptables work as? full-cone, restricted, port restricted, or
> symmetric?
> 
> Sorry if it's not appropriate to ask such a question here. Thanks in advance.

You might want to look up STUNT which uses an intermediary to open the NAT tunnel.

      reply	other threads:[~2009-06-11  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  3:42 does NAT based on iptables support TCP hole punch? Tony Wan
2009-06-11  4:57 ` Stephen Hemminger [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=20090610215731.694c3661@nehalam \
    --to=shemminger@vyatta.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=visual2me@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;
as well as URLs for NNTP newsgroup(s).