16 Jul
2019
16 Jul
'19
10:58 a.m.
On Tue, Jul 16, 2019 at 11:38:00AM -0400, Bryan Fields wrote:
On 7/16/19 11:28 AM, Holger Baust via 44Net wrote:
Yes, one should consider announcing 44.128.0.0/20. They are squatting on
space which is not theirs to squat on.
In addition to announcing 44.128.0.0/20, it may be good to ensure all of
44.0.0.0/8 is visible in the default-free zone and drop any packets
received for unused IP addresses within 44.0.0.0/8 on the floor.
The Internet default-free zone at times seems to adhere to a "use it or
lose it" mantra, and while this is unfortunate; announcing the 44net to
the internet at large will send a clear message that the space is
actually in use and should not be squatted on.
To completely cover the 44net block from a BGP perspective, in addition
to the existing 44.0.0.0/9 and 44.128.0.0/10 announcement, 44.192.0.0/10
should also be announced (and nullrouted) from some vantage point.
I'm happy to do so if the community accepts my help in this regard. I
have facilities to announce the prefix and ignore any traffic received
for it.
Kind regards,
Job Snijders
My company plans to use DC/OS from Mesosphere and
DC/OS is using
44.128.0.0/20 per default for overlay networking. This seems to
have no impact since this overlay nets are only used in DC/OS
clusters and not routed to the Internet, but might lead to problems
in some cases...
Their documentation with this informations can be found at:
https://docs.mesosphere.com/1.10/networking/virtual-networks/ip-per-contain…
You're posting using quoted printable, don't do that. I've fixed your link.
Is this already known?
News to me, and a really poor idea. There's other networks which could
be used for this, without stepping on allocated space. 44.128.0.0/20
isn't used now, but neither was 1/8 or 5/8. I kinda want to announce
44.128.0.0/20 just to mess with them, might freak out if there's a
route to that :)