From: Mikael Abrahamsson <swmike@swm.pp.se>
To: David Lang <david@lang.hm>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wicked OT: 240.0.0.0/4 netblock
Date: Sun, 21 Oct 2018 18:26:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810211824070.26856@uplift.swm.pp.se> (raw)
In-Reply-To: <alpine.DEB.2.02.1810191115190.4973@nftneq.ynat.uz>
On Fri, 19 Oct 2018, David Lang wrote:
> On Fri, 19 Oct 2018, Mikael Abrahamsson wrote:
>
>> Most host stacks do not handle 240/4 correctly. Getting this working
>> outside of a very closed and controlled network is not feasible.
>>
>> You would need to validate all devices to support this 240/4 block that
>> most IP stacks today will not use.
>
> I think starting down this road with the idea of making it like the 10/8
> block would still be a win. I've seen enough companies running into grief
> with allocation issues in the 10/8 block that the idea of having an
> additional /4 block available, even if only Linux and routers supported it
> would be very useful. (especially with container heavy environments)
As long as you validate everything that is being connected in there and it
never leaks outside (remember, that is hard, for example look at MS
leaking their internal IPs in email headers), you can do whatever you
want.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-10-21 16:26 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
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 [this message]
[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=alpine.DEB.2.20.1810211824070.26856@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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