From: Dave Taht <dave.taht@gmail.com>
To: "Richard E. Brown" <richb.hanover@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Wicked OT: 240.0.0.0/4 netblock
Date: Fri, 19 Oct 2018 11:53:21 -0700 [thread overview]
Message-ID: <CAA93jw5ENCorW_CUqA3-0tUEqa6RmPcpFstUkEGmyufFZJYsng@mail.gmail.com> (raw)
In-Reply-To: <A83722D3-AED3-484E-A25C-946C5237B2C5@gmail.com>
On Fri, Oct 19, 2018 at 11:36 AM Rich Brown <richb.hanover@gmail.com> wrote:
>
> 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.)
240 is routable if you don't use a standard martians list.
http://www.radb.net/query/?keywords=fltr-martian
blocks 224/3.
It may not be routable on older versions of windows.
It may not even be assignable on some OSes and tools, currently.
It's certainly blocked on many a bogon filter and in our bcp38 package
An attempt to make "E" useful died a decade ago:
https://tools.ietf.org/html/draft-fuller-240space-02
Still, it would be a better world with 268m more routable ips in it,
wouldn't it?
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2018-10-19 18:53 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 [this message]
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=CAA93jw5ENCorW_CUqA3-0tUEqa6RmPcpFstUkEGmyufFZJYsng@mail.gmail.com \
--to=dave.taht@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