From: "Fredrik Björk" <Fredrik.Bjork.List@varbergenergi.se>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 150.150. addresses
Date: Thu, 21 Jun 2001 06:42:26 +0000 [thread overview]
Message-ID: <marc-lartc-99310580219876@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99309192123806@msgid-missing>
At 22:24 2001-06-20 -0400, you wrote:
>Are 150.150.*.* adresses private or reserve addresses?
>My friend has a one, and I tried doing an nslookup, ping, and traceroute
>with no luck.
Private address space is defined in RFC1918 (see
http://www.faqs.org/rfcs/rfc1918.html):
3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
That is, all addresses beginning with 10., all beginning with 172.16.
through 172.31. and all beginning with 192.168. are private. You should
NEVER use other addresses in your private LAN since that can cause trouble
for you (and normally only you). A customer of mine had set up a private
LAN with addresses belonging to Pittsburgh board of electricity which would
cause their LAN to believe that requests to Pittsburgh were local so they
couldn't be routed out of their office. Not that a swedish company would
ever be interested in Pittsburgh board of electricity, but you never know
what problems could occur. (Say for instance that Pittsburgh board of
electricity hosts the DNS servers for a company that you really want to
contact...)
On the other hand you should be aware that these addresses won't be routed
on the Internet and can therefore be used alongside with your public IP
addresses for switches or other kinds of equipment that you don't need to
be globally, but only locally available.
/Fredrik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-06-21 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 2:24 [LARTC] 150.150. addresses adelphia
2001-06-21 2:27 ` Tomasz Orzechowski
2001-06-21 6:42 ` Fredrik Björk [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=marc-lartc-99310580219876@msgid-missing \
--to=fredrik.bjork.list@varbergenergi.se \
--cc=lartc@vger.kernel.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