Dave -
You’d need to ask someone who speaks for the USG to address that question – and
that’s
definitely not my job.
However, I will observe in the time since then, the DoD has taken to
occasionally publicly
routing some of its address blocks, so the probability of inadvertent routing
Excellent summary of the USG position as of 2019. It is, um, nearly 5
years later, has any of these stuff evolved?
On Tue, Feb 13, 2024 at 9:58 PM John Curran wrote:
>
> On Jan 31, 2024, at 12:48 AM, Rubens Kuhl wrote:
>
> DoD's /8s are usually squatted by networks that run out of private IPv4
On Jan 31, 2024, at 12:48 AM, Rubens Kuhl wrote:
DoD's /8s are usually squatted by networks that run out of private IPv4 space.
Even though it is very risky to steal resources from an organization
that can deploy a black helicopter or a nuclear warhead over you, for
some reason like it not
Rubens,
Le 31/01/2024 à 06:48, Rubens Kuhl a écrit :
DoD's /8s are usually squatted by networks that run out of private IPv4 space.
Indeed, most I've seen just came to the conclusion that if there's no
more blocks available in 10/8, just use the next best thing : 11/8.
Best regards,
--
Yes, absolutely. That's part of the technical risk that you take if you
decide to do such things.
If it's a "good" choice or not is entirely situational. Some organizations
are fine with kicking that tech debt down the road, others like to double
down and create a house of cards.
On Thu, Feb 1,
It's unfortunate, but quite common. I've seen similar occurrences in
several companies I worked for previously. For instance, one of my former
employers utilized public IP addresses belonging to others for IPMI server
access, even though it was solely for management purposes and not
communicated
If you are using IPv4 address that belong to someone else internally you really
are in a prime position to use IPv6 only internally and use one of the IPv4AAS
mechanisms to reach the IPv4 internet. After a quarter of a century all your
equipment should be IPv6 capable.
--
Mark Andrews
> On
> On Jan 31, 2024, at 23:19, Frank Habicht wrote:
>
> On 01/02/2024 01:45, Tom Beecher wrote:
>> Seems a bit dramatic. Companies all over the world have been using other
>> people's public IPs internally for decades. I worked at a place 20 odd years
>> ago that had an odd numbering scheme
On 01/02/2024 01:45, Tom Beecher wrote:
Seems a bit dramatic. Companies all over the world have been using other
people's public IPs internally for decades. I worked at a place 20 odd
years ago that had an odd numbering scheme internally, and it was
someone else's public space. When I asked
For many years, a large customer (telco/VOIP/ISP carrier that should have known
better) of a former employer was using 11.0.0.0/8 as an extension of 10.0.0.0/8
and literally forced said employer to carry their routes to those prefixes in
those tables (or lose an extremely lucrative contract).
>
> Even though it is very risky to steal resources from an organization
> that can deploy a black helicopter or a nuclear warhead over you
>
Seems a bit dramatic. Companies all over the world have been using other
people's public IPs internally for decades. I worked at a place 20 odd
years ago
DoD's /8s are usually squatted by networks that run out of private IPv4 space.
Even though it is very risky to steal resources from an organization
that can deploy a black helicopter or a nuclear warhead over you, for
some reason like it not appearing in the DFZ people seem to like it.
Rubens
Seems it disappeared now and we can go back to regular programming.
Thanks to those who did that.
Frank
[frank@fisi ~]$ whois -h rr.level3.com 0.0.0.0/32
[Querying rr.level3.com]
[rr.level3.com]
% No entries found for the selected source(s).
[frank@fisi ~]$
On 30/01/2024 19:37, Job
On Tue, Jan 30, 2024 at 07:28:01PM +0300, Frank Habicht wrote:
> I believe that the entry of
> route: 0.0.0.0/32
>
> does not serve any good purpose?
I don't think so either, I've created an issue to prevent that in future
releases of IRRd v4: https://github.com/irrdnet/irrd/issues/906
That's pretty cool, actually. I keep wondering when someone will offer
up a 0.0.0.0/8...
https://www.ietf.org/archive/id/draft-schoen-intarea-unicast-0-00.html
There must be more people out there than just amazon and google that
ran out of 10/8.
On Tue, Jan 30, 2024 at 11:29 AM Frank Habicht
Hi,
I got 2 bounces for the email addresses seen below for an email similar
to the below...
Anyone want to remove this IRR entry before anyone notices...??? ;-)
Frank
I believe that the entry of
route: 0.0.0.0/32
does not serve any good purpose?
I was surprised to see it in a
16 matches
Mail list logo
