Hacker News Reader

Hacker News

Comment by __david__ | Hacker News Reader

Full thread

__david__

I'd throttle the FCC. What is their internal IP block?

View on HN

FCC (NET-165-135-0-0-1) 165.135.0.0 - 165.135.255.255

FCCNET2 (NET-192-133-125-0-1) 192.133.125.0 - 192.133.125.255

FCCNET (NET-192-104-54-0-1) 192.104.54.0 - 192.104.54.255

FCC2-126-30 (NET-4-21-126-0-1) 4.21.126.0 - 4.21.126.255

FCC (NET6-2620-610-1) 2620:0:610:: - 2620:0:610:FFFF:FFFF:FFFF:FFFF:FFFF

SPRINTLINK (NET-208-23-64-0-1) 208.23.64.0 - 208.23.64.127

TBD (NET6-2600-803-230-1) 2600:803:230:: - 2600:803:230:FFFF:FFFF:FFFF:FFFF:FFFF

Q0503-65-125-25-64 (NET-65-125-25-64-1) 65.125.25.64 - 65.125.25.127

This list was more comprehensive than mine. Here's how you can do it on your own server if you're using nginx: https://gist.github.com/kyledrake/e6046644115f185f7af0

Why stop there, throttle the Congress and White House IP's for being complicit. I'd throttle every US government IP block myself.

Let's start getting a list together then.

hows the list going?

Seriously, why doesn't the author release their internal IP block? This could create a valid way of protest against it. Hell, big name tech companies could get in on this.

If some script kiddy on Reddit or Anonymous abuse that information "for the lulz" or "sake of the internetz" with DoS etc., the author would needlessly get into trouble since he got it confidentially.

I'm sure the author could have easily been creative enough to hide that he was his own source. Also are IPs really considered private information? I thought the whole point of IPs was they can be shared.

A simple (probably flawed) example: "Oh hey, I found this pastebin with the FCC's IP block, don't know where it came from"

It's not really secret, you can look it up on ARIN.

EG: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft

It would be hilarious if someone was to try and DoS the FCC network, but were to be foiled by someone in-between them rate-limiting it to 28.8k.

Reply on news.ycombinator.com