From: Jonathan Morton <chromatix99@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wicked OT: 240.0.0.0/4 netblock
Date: Fri, 19 Oct 2018 21:54:00 +0300 [thread overview]
Message-ID: <24F1ED34-4C97-4534-93C5-7C88660D4B1D@gmail.com> (raw)
In-Reply-To: <A83722D3-AED3-484E-A25C-946C5237B2C5@gmail.com>
> On 19 Oct, 2018, at 9:36 pm, Rich Brown <richb.hanover@gmail.com> wrote:
>
> MY QUESTION: I have always believed that this netblock is not routable. Is this true? (A simple yes/no answer would be sufficient.)
According to https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml the 240/4 netblock is:
NOT valid as a source or destination address for packets between devices.
NOT forwardable.
NOT globally reachable.
IS "reserved by protocol":
o Reserved-by-Protocol - A boolean value indicating whether the
special-purpose address block is reserved by IP, itself. This
value is "TRUE" if the RFC that created the special-purpose
address block requires all compliant IP implementations to behave
in a special way when processing packets either to or from
addresses contained by the address block.
I'm sure you could use those addresses in a closed, controlled laboratory network - but not in anything you plan to deploy commercially or publicly. It would be better to use IPv6, IMHO.
- Jonathan Morton
next prev parent reply other threads:[~2018-10-19 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 18:36 Rich Brown
2018-10-19 18:53 ` Dave Taht
2018-10-19 19:09 ` valdis.kletnieks
2018-10-19 19:13 ` Dave Taht
2018-10-19 18:54 ` Jonathan Morton [this message]
2018-10-19 19:04 ` Mikael Abrahamsson
[not found] ` <alpine.DEB.2.02.1810191115190.4973@nftneq.ynat.uz>
2018-10-21 16:26 ` Mikael Abrahamsson
[not found] ` <nycvar.QRO.7.76.6.1810211541180.4351@qynat-yncgbc>
2018-10-22 9:05 ` Mikael Abrahamsson
2018-11-15 3:28 ` Stephen Hemminger
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24F1ED34-4C97-4534-93C5-7C88660D4B1D@gmail.com \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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