From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [Bulk] Re: [gentoo-user] /etc/hosts include file?
Date: Mon, 11 Mar 2013 23:58:24 -0400 [thread overview]
Message-ID: <20130312035824.GA32188@waltdnes.org> (raw)
In-Reply-To: <791427.9528.bm@smtp109.mail.ird.yahoo.com>
On Mon, Mar 11, 2013 at 11:39:35PM +0000, Kevin Chadwick wrote
> > Don't waste time and effort on it. Put your
> > effort into pounding away on a simple issue that people do understand...
> > we're running out of IP addresses.
>
> We have run out of unallocated ones, there are still loads of unused
> ones... and even some being released.
And they'll run out rather quickly at the rate they're being assigned.
There are approximately 3.7 billion usable IPV4 addresses. Soon, that
will be one for every 2 people on this planet. And don't forget the
people who have an account at home, a smartphone with web access, and an
internet-connected desktop at work. Conservation of IP addresses will
buy us a couple more years, but that's it.
> and even more due to global NAT...
In another message you said...
> ...and may I state again also that I have externally facing servers
> and games machines behind NAT.
Yes, that works if *YOU* have at least 1 public IP address and *YOU*
control port-forwarding. But it won't work behind carrier-level NAT.
> It is true eventually it will be an absolute problem but hopefully by
> then we will have a cleaner ipv7.
It won't happen. It's too late to start from scratch, and the IPV6
rollout has already begun.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2013-03-12 3:58 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
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 [this message]
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=20130312035824.GA32188@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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