From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [Patch 0/2] Avoid direct connections between NATed hosts
Date: Fri, 12 Jan 2007 19:11:45 +0200 [thread overview]
Message-ID: <200701121911.48617@auguste.remlab.net> (raw)
In-Reply-To: <1168621167.28615.14.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Le vendredi 12 janvier 2007 18:59, Eric Leblond a écrit :
> Some algorithms can be used to established direct connections between
> NATed hosts. Skype is one of the programs using this kind of
> "feature".
NAT are not *security* devices; NATs are meant to *improve* IP usability
by allowing as many protocols as possible to operate even though there
are not enough public IP addresses. Making it more difficult for P2P
apps to operate through is hence completely not only non-sensical, but
a plain contradiction.
NATs are sufficiently broken and annoying already to handle for software
development; please do not make them worst. Also, this patch goes
completely against work-in-progress NAT standards.
In this particular case, your approach is a completely associal
short-term solution. In the long run, it will simply cause people with
normal/correct NATs to have to relay even more traffic when they should
not have to, because of people like you. And it certainly won't prevent
Skype from running on your network either.
--
Rémi Denis-Courmont
http://www.remlab.net/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-12 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 16:59 [Patch 0/2] Avoid direct connections between NATed hosts Eric Leblond
2007-01-12 17:02 ` [Patch 1/2] " Eric Leblond
2007-01-12 17:04 ` [Patch 2/2] iptables: add random option to SNAT Eric Leblond
2007-01-12 17:11 ` Rémi Denis-Courmont [this message]
2007-01-12 17:20 ` [Patch 0/2] Avoid direct connections between NATed hosts Patrick McHardy
2007-01-12 17:39 ` Rémi Denis-Courmont
2007-01-17 12:13 ` Patrick McHardy
2007-01-12 22:53 ` Jan Engelhardt
2007-01-13 12:06 ` Resend [Patch 2/2] iptables: add random option to SNAT Eric Leblond
2007-01-13 21:00 ` Resend [Patch 1/2] Avoid direct connections between NATed hosts Eric Leblond
2007-01-17 12:23 ` Patrick McHardy
2007-01-17 15:18 ` Eric Leblond
2007-01-19 15:36 ` Patrick McHardy
2007-01-26 14:00 ` Patrick McHardy
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=200701121911.48617@auguste.remlab.net \
--to=rdenis@simphalempin.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 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).