From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: "ext Willy Tarreau" <w@1wt.eu>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] add a sysctl to disable TCP simultaneous connection opening
Date: Fri, 10 Oct 2008 10:59:25 +0300 [thread overview]
Message-ID: <200810101059.25904.rdenis@simphalempin.com> (raw)
In-Reply-To: <20081009214224.GD21013@1wt.eu>
On Friday 10 October 2008 00:42:24 ext Willy Tarreau, you wrote:
> On Thu, Oct 09, 2008 at 07:21:03PM +0300, Rémi Denis-Courmont wrote:
> > Le mercredi 8 octobre 2008 14:54:02 Stephen Hemminger, vous avez écrit :
> > > Does this break NAT traversal via STUNT used by applications like
> > > Skype?
> >
> > This will break the main ICE-TCP mechanism (IETF
> > draft-ietf-mmusic-ice-tcp). I am not aware of any application using this
> > _as_of_now_. Probably too many NAT and firewall implementations will
> > reject it already. And then, some TCP stacks reportedly do not support it
> > (e.g. Windows before Vista).
>
> And opening this through firewalls would be too much dangerous as it would
> allow servers to reconnect outside, pretty much defeating the initial
> purpose of the firewall.
Duh? If you require a SYN from the outside to the server, before you allow the
server to send either SYN or SYN/ACK, I fail to see the problem.
> > On the other hand, if someone were to tunnel/encapsulate TCP over UDP,
> > this could actually be useful - think about peer-to-peer NATted-to-NATted
> > file transfers for instance.
>
> This is already possible using netcat. You can force both ports. It has no
> flow control but would be enough to chat or transfer small config files.
Files transfer over UDP? Come on. I won't restart the UDP sendfile discussion.
--
Rémi Denis-Courmont
next prev parent reply other threads:[~2008-10-10 7:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 8:11 [PATCH] add a sysctl to disable TCP simultaneous connection opening Willy Tarreau
[not found] ` <20081008081109.GA25342-K+wRfnb2/UA@public.gmane.org>
2008-10-08 9:19 ` Michael Kerrisk
2008-10-08 11:54 ` Stephen Hemminger
2008-10-08 12:10 ` Willy Tarreau
2008-10-09 16:21 ` Rémi Denis-Courmont
2008-10-09 21:42 ` Willy Tarreau
2008-10-10 7:59 ` Rémi Denis-Courmont [this message]
2008-10-10 8:10 ` Willy Tarreau
2008-10-10 8:44 ` Rémi Denis-Courmont
2008-10-10 8:57 ` Willy Tarreau
2008-10-08 12:16 ` Pavel Emelyanov
2008-10-08 12:26 ` Willy Tarreau
2008-10-08 12:32 ` Pavel Emelyanov
2008-10-08 12:56 ` Willy Tarreau
2008-10-08 15:50 ` Randy Dunlap
2008-10-08 16:04 ` Willy Tarreau
2008-10-08 16:42 ` David Miller
2008-10-08 17:07 ` Willy Tarreau
2008-10-08 18:21 ` David Miller
2008-10-08 18:24 ` Willy Tarreau
2008-10-09 3:49 ` Andi Kleen
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=200810101059.25904.rdenis@simphalempin.com \
--to=rdenis@simphalempin.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=w@1wt.eu \
/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).