Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Wicked OT: 240.0.0.0/4 netblock
Date: Fri, 19 Oct 2018 14:36:33 -0400	[thread overview]
Message-ID: <A83722D3-AED3-484E-A25C-946C5237B2C5@gmail.com> (raw)

Sorry for distracting you from important things, but I have a question for people more knowledgeable about routing than I am...

There's a person on the OpenWrt forum who is asking about using the 240.0.0.0/4 netblock for some (undefined) purpose. (If you're terminally curious, or need another reason to yell at the monitor, you could look at: https://forum.openwrt.org/t/private-network-using-240-0-0-0-4-netblock/23543/5)

MY QUESTION: I have always believed that this netblock is not routable. Is this true? (A simple yes/no answer would be sufficient.)

Many thanks!

Rich

PS I've seen the IANA advice that those addresses should not be used. (See the final note on the thread.) I'm more interested in whether it would ever work in practice: don't most upstreams block that address?

PPS for all you non-Vermonters, "wicked" in this context means "extremely", often in an interesting way

             reply	other threads:[~2018-10-19 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 18:36 Rich Brown [this message]
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
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=A83722D3-AED3-484E-A25C-946C5237B2C5@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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