From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [Bulk] Re: [gentoo-user] /etc/hosts include file?
Date: Sat, 09 Mar 2013 23:59:17 -0500 [thread overview]
Message-ID: <513C1325.5020504@orlitzky.com> (raw)
In-Reply-To: <20130310014256.GA27509@waltdnes.org>
On 03/09/2013 08:42 PM, Walter Dnes wrote:
> On Fri, Mar 08, 2013 at 07:41:13PM -0500, Michael Mol wrote
>
>> The trouble with NAT is that it destroys peer-to-peer protocols. The
>> first was FTP in Active mode.
>
> In its day, it was OK. Nowadays, we use passive mode. What's the
> problem?
>
It also doesn't work under NAT, it's just broken in the other direction.
>> SIP has been heavily damaged as well. Anyone who's used IRC is
>> familiar with the problems NAT introduces to DCC.
>
> Every ADSL router-modem I've run into recently has port-forwarding.
>
>> Anyone who's ever played video games online,...
>
> A *CLIENT* that can't operate from behind NAT is totally brain-dead.
>
But you must have one non-NATed "server" for anything to work. I assume
that's what was meant by "it destroys peer-to-peer protocols." You have
to draw an arbitrary distinction between machines that work together,
"servers," and ones that don't, "clients."
The problem will become more and more apparent as ipv4 space dries up
and everyone becomes a client. Although ISPs will be more than happy to
sell you a useful connection, for a premium.
Un-NATed addresses are like, type-O blood. Imagine how much better off
we'd be if we could get everyone to switch their blood to type-O. Might
be less painful than the ipv6 transition, too =)
>> or who's tried hosting a Teamspeak or Ventrillo server, has had NAT
>> get in their way as well.
>
> Port-forwarding.
>
Port forwarding can work, but only for one host when the ports are
standardized. You can't forward e.g. port 443 to two hosts, so only one
host behind the NAT can be accessible on 443.
If you're using your NAT as a firewall for one box, then who cares. But
you can't put more than one machine behind it and have everything still
work.
next prev parent reply other threads:[~2013-03-10 5:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 22:24 [gentoo-user] /etc/hosts include file? Alan McKinnon
2013-03-07 23:50 ` Michael Mol
2013-03-08 0:29 ` Michael Mol
2013-03-08 8:32 ` Alan McKinnon
2013-03-08 13:40 ` Michael Mol
2013-03-08 13:54 ` Alan McKinnon
2013-03-08 19:50 ` [Bulk] " Kevin Chadwick
2013-03-08 19:55 ` Michael Mol
2013-03-08 21:49 ` Kevin Chadwick
2013-03-08 22:36 ` Pandu Poluan
2013-03-09 0:50 ` Kevin Chadwick
2013-03-09 3:27 ` Michael Mol
2013-03-09 12:53 ` Kevin Chadwick
2013-03-10 21:28 ` Michael Mol
2013-03-11 23:09 ` Kevin Chadwick
2013-03-12 5:05 ` Michael Mol
2013-03-09 0:13 ` Walter Dnes
2013-03-09 0:41 ` Michael Mol
2013-03-10 1:42 ` Walter Dnes
2013-03-10 4:59 ` Michael Orlitzky [this message]
2013-03-10 21:09 ` Michael Mol
2013-03-10 5:19 ` Alan McKinnon
2013-03-10 21:07 ` Michael Mol
2013-03-10 21:43 ` Alan McKinnon
2013-03-10 22:02 ` Michael Mol
2013-03-11 4:00 ` Walter Dnes
2013-03-11 4:37 ` Michael Mol
2013-03-11 8:22 ` Alan McKinnon
2013-03-11 22:45 ` Walter Dnes
2013-03-11 23:39 ` Kevin Chadwick
2013-03-12 3:58 ` Walter Dnes
2013-03-12 0:25 ` Alan McKinnon
2013-03-12 2:02 ` Michael Mol
2013-03-12 11:29 ` Alan McKinnon
2013-03-13 0:26 ` [Bulk] " Kevin Chadwick
2013-03-11 23:31 ` Kevin Chadwick
2013-03-12 0:37 ` Alan McKinnon
2013-03-09 0:45 ` Kevin Chadwick
2013-03-09 3:21 ` Michael Mol
2013-03-09 12:53 ` Kevin Chadwick
2013-03-10 22:00 ` Michael Mol
2013-03-11 1:56 ` Michael Orlitzky
2013-03-11 2:33 ` Michael Mol
2013-03-11 22:34 ` Kevin Chadwick
2013-03-12 3:36 ` Michael Mol
2013-03-08 15:39 ` Florian Philipp
2013-03-08 4:30 ` Pandu Poluan
2013-03-08 8:23 ` Alan McKinnon
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=513C1325.5020504@orlitzky.com \
--to=michael@orlitzky.com \
--cc=gentoo-user@lists.gentoo.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