Live data from Hacker News

Did AS8003 just disappear?

kentik.com

11–20 of 75 posts

Re: Did AS8003 just disappear?

#12

> Once again as a final note: your corporate network may be using the formerly unused DoD space internally, and if so, there is a risk you could be leaking it out to a party that is actively collecting it. How could you know? Using Kentik’s Data Explorer, you could quickly and easily view the stats of exactly how much data you’re leaking to AS8003 (now AS749). May be worth a check, and if so, start a free trial of Ke…

11.0.0.0/8

Was it ever common to use 11/8 internally? Did people just roll dice because it wasn't being announced? The reference in the post is the first I've heard of people possibly using it.

Re: Did AS8003 just disappear?

#14

Earlier quoted context omitted.

11.0.0.0/8

Was it ever common to use 11/8 internally? Did people just roll dice because it wasn't being announced? The reference in the post is the first I've heard of people possibly using it.

I'm baffled too. This is why there is an RFC 1918 so everyone knows what's public and private.

Re: Did AS8003 just disappear?

#15
post #11

Opened this from RSS feed, because I thought AS8003 is a name of a star or a galaxy.

I figured it was the name of an assembler for a processor called the 8003.

I thought it was a flight number and we were about to be hit with months of world news headlines into the investigations of a flight that simply disappeared.

Re: Did AS8003 just disappear?

#18

Earlier quoted context omitted.

I figured it was the name of an assembler for a processor called the 8003.

I thought it was a flight number and we were about to be hit with months of world news headlines into the investigations of a flight that simply disappeared.

Now it's a twilight zone episode: flight AS8003 disappears over the Atlantic, simultaneously star AS8003 vanishes from the night sky, and every copy of the AS8003 assembler ceases to exist on all media.

Re: Did AS8003 just disappear?

#20
post #14

Earlier quoted context omitted.

Was it ever common to use 11/8 internally? Did people just roll dice because it wasn't being announced? The reference in the post is the first I've heard of people possibly using it.

I'm baffled too. This is why there is an RFC 1918 so everyone knows what's public and private.

There's probably some group of network operators out there who decided amongst themselves that it'd be cheaper and easier to squat the dod ranges when shuffling traffic amongst themselves, than having to wrap each packet with a tunneling header. Or who knows maybe some third world dictator told their isps to use the dod ranges because they mistakenly assumed it would isolate their nation's traffic from the rest of the world. It's a real shame that the linked article doesn't divulge what's actually happening.

The DOD owns all IPs starting with 6, 7, 11, 21, 22, 26, 28, 29, 30, 33, 55, 214, and 215. To a network operator who spends his day filling out forms explaining why he needs each and every /32 I imagine it must make you feel like someone who spends half his income to live in a tiny crumby apartment in a city surrounded by vacant unsecured mansions. The owners of these mansions haven't set foot in them for thirty years. So surely it must be safe to just move in right?

Post reply on HN