MIT no longer owns 18.0.0.0/8
11–20 of 146 posts
Re: MIT no longer owns 18.0.0.0/8
#12My how things change. At one point in the late 90s, I had an entire MIT Class C subnet at my house. Now, I've got 5 static IPs from Verizon FiOS on some ancient grandfathered plan. Years ago, they "changed" the addresses, prompting me to ask, "what part of 'static' is not clear?"
Re: MIT no longer owns 18.0.0.0/8
#13My how things change. At one point in the late 90s, I had an entire MIT Class C subnet at my house. Now, I've got 5 static IPs from Verizon FiOS on some ancient grandfathered plan. Years ago, they "changed" the addresses, prompting me to ask, "what part of 'static' is not clear?"
Re: MIT no longer owns 18.0.0.0/8
#14Last time I was at the MIT media lab for a conference, I was able to get an unfirewalled external ip address from their wireless network. It was amazing. I briefly streamed live audio of a talk via shoutcast, but of course, nobody uses that stuff anymore. It really makes you ponder what a cloudless internet would be like.
A little over a year ago, my university gave up their generous range of IP addresses. You could plug in ethernet, and not just get an internet routable IP (albeit firewalled from incoming traffic from the internet), you would even be assigned a subdomain off of the school's .edu domain. It was great. Students ran servers in their dorms. Clubs ran servers. Some professors ran servers. Even though you couldn't listen on a socket for incoming traffic from the internet by default, it was unfirewalled internally. I had to briefly live in student housing, and I was able to connect to my server via the school's http proxy via corkscrew. There were so many cool uses for it. Students were encouraged to run web servers if they needed hosting. It was also much faster[1]
I think CMU still provides fairly decent network services.
It was an insanely useful utility provided to students, and any serious engineering school should do it.
Re: MIT no longer owns 18.0.0.0/8
#15Earlier quoted context omitted.
https://whois.arin.net/rest/net/NET-18-0-0-0-1.html So they don't have 18.0.0.0/8, but they do have 18.0.0.0/9?
That's up to 8388608 addresses lost...
Re: MIT no longer owns 18.0.0.0/8
#16My how things change. At one point in the late 90s, I had an entire MIT Class C subnet at my house. Now, I've got 5 static IPs from Verizon FiOS on some ancient grandfathered plan. Years ago, they "changed" the addresses, prompting me to ask, "what part of 'static' is not clear?"
If you can find an ISP that supports IPv6 quite a few of them (maybe all?) support prefix delegation. A /64 isn't uncommon from ISPs in Seattle.
Re: MIT no longer owns 18.0.0.0/8
#17My how things change. At one point in the late 90s, I had an entire MIT Class C subnet at my house. Now, I've got 5 static IPs from Verizon FiOS on some ancient grandfathered plan. Years ago, they "changed" the addresses, prompting me to ask, "what part of 'static' is not clear?"
Just curious, was it a breach of contract or did they have one of those lovely small printed clauses no one ever reads :)
Re: MIT no longer owns 18.0.0.0/8
#18tl;dr MIT is selling off half of 18.0.0.0/8 (8 million IPs)
Re: MIT no longer owns 18.0.0.0/8
#19Earlier quoted context omitted.
That's up to 8388608 addresses lost...
Sold, probably. Looking at https://www.leadertelecom.biz/ips/transfer , that could have brought in a nice sum of money (they ask #unicode code points in dollars per 65,536 addresses)
Could someone explain this? I feel like I'm missing something (not the 2^16 addresses, the "#unicode code points")
Re: MIT no longer owns 18.0.0.0/8
#20Off-offtopic: The cable modem broke down once. We called the guy, he picked it up 20 minutes later, soldered the broken capacitor and we had our internet back in 2 hours. It was on a Saturday.
He didn't have to do any of that, he had monopoly on broadband on the entire area. Small ISPs are the best.