News for hackers. Stuff that matters.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @04:14PM (#14151343)
That's too bad. I think universities should make these resources that they've been granted available to students and researchers.

Last 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.

[1] http://www.speedtest.net/result/4339921583.png

Re:MIT no longer owns 18.0.0.0/8 by dangero on Wednesday April 19, 2017 @04:32PM (#14151486)
IPV6 solves this, plus even without you don't need anything close to this amount of IPs to do what you're describing. It's a fairly niche case to need that many public IPs and it seems a little crazy to hold that many just in case some researcher might want to use them.

Even your comment about streaming, seems like mainly nostalgia vs reality as you kind of admit. Any modern streaming infrastructure works from behind a NAT since most people are behind one these days.

Re:MIT no longer owns 18.0.0.0/8 by mickrussom on Wednesday April 19, 2017 @05:44PM (#14152073)
IPv6 solves mAAAAny issues. DNS issues causes MAAAAny more. I dAAAAbble in v6 here AAAAnd there AAAAnd the situAAAAtion is still pretty dire.
Re:MIT no longer owns 18.0.0.0/8 by bb88 on Wednesday April 19, 2017 @05:49PM (#14152115)
The question is, will people get the joke?
Re:MIT no longer owns 18.0.0.0/8 by natermer on Wednesday April 19, 2017 @06:16PM (#14152311)
Only people that could have anything approaching a opinion about ipv6 worth listening to.
Re:MIT no longer owns 18.0.0.0/8 by runjake on Wednesday April 19, 2017 @05:48PM (#14152108)
Guy who manages a two-dozen site v6 network with tens of thousands of clients here. What issues are you referring to?
Re:MIT no longer owns 18.0.0.0/8 by tarboreus on Wednesday April 19, 2017 @06:22PM (#14152344)
Yeah if you want to make a cname for yourself in this field you'll have to bring your AAA game.
Re:MIT no longer owns 18.0.0.0/8 by niij on Wednesday April 19, 2017 @10:14PM (#14153436)
*AAAA
Re:MIT no longer owns 18.0.0.0/8 by knd775 on Wednesday April 19, 2017 @05:57PM (#14152182)
They answered that question 6 times in their comment.
Re:MIT no longer owns 18.0.0.0/8 by mortehu on Wednesday April 19, 2017 @06:36PM (#14152420)
If you can't access IPv6 enabled sites, you can't access Google, Facebook, Wikipedia, or Netflix, who all enabled IPv6 permanently in 2012[1]. According to [2], around a third of US has IPv6 connectivity. If AAAA records constitute some big problem, it's not well known.

1. http://www.worldipv6launch.org/participants/?q=1

2. https://www.google.com/intl/en/ipv6/statistics.html#tab=per-...

Re:MIT no longer owns 18.0.0.0/8 by throwaway2048 on Wednesday April 19, 2017 @06:40PM (#14152439)
Thats not how it works, if you only have IPv4, AAAA records have no effect. Google et all continue to work via IPv4.
Re:MIT no longer owns 18.0.0.0/8 by mortehu on Wednesday April 19, 2017 @06:56PM (#14152516)
I'm not sure what you're referring to when you say "Thats not how it works".

I was referring to people with broken IPv6 setups, mostly Teredo and 6to4 (old Mac OS X versions), for whom IPv4 worked but IPv6 was not actually routable. At the time, publishing AAAA records would lock out all of those users.

Re:MIT no longer owns 18.0.0.0/8 by mirashii on Wednesday April 19, 2017 @07:24PM (#14152684)
> If you can't access IPv6 enabled sites, you can't access Google

He was referring to your lack of qualification in the above. An IPv4 user can indeed access Google, which is an IPv6 enabled site.

Re:MIT no longer owns 18.0.0.0/8 by mortehu on Wednesday April 19, 2017 @11:21PM (#14153664)
Oh, I see now. You're reading "Having IPv6 access is a necessary for accessing Google". What I meant was "If the presence of AAAA records means you can't access a site, then you can't access Google".

A user who only has IPv4 connectivity relies on their software recognizing this when accessing an IPv6 enabled site. Software's failure to do so is one of the main reasons for the slow rollout of IPv6.

Re:MIT no longer owns 18.0.0.0/8 by taf2 on Wednesday April 19, 2017 @06:30PM (#14152388)
Very hAAAArd to rAAAed - even having troubling remembering whAAAt you just sAAAAid...
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @06:12PM (#14152291)
IPV6 is all well and good, but I am not optimistic about it. Why should a university deploy it, and introduce all sorts of new problems? Mine hasn't. And I don't blame them.

No, I think that our future is isolated carrier-grade NAT, connecting to cloud services exclusively. And that makes me sad.

I had to disable ipv6 on my Linode, because Clouldflare, Google, and Facebook do not seem to trust any ipv6 traffic coming from Linode. Only using ipv4 has fixed everything.

And, as for ip4 blocks being obsolete, I still think it's wrong to sell them off. Universities were endowed with these. If they don't have a use for them, they should make them available for someone who does. Not just sell them to be used for some corporation's infrastructure.

I hate how so many people on hackernews seem to think that not selling these ipv4 addresses is a "waste". People are only looking at this in purely financial terms. I consider it to be wasteful to sell them to Microsoft or Amazon or whatever. No matter how much money they offer. Universities are supposed to use the gifts they are given to try to better society.

Aren't these ip addresses going to just be used for things like NAT traversal? Why doesn't MIT make them available for some non profit to offer that service as a public utility?

If a flight school has an operating runway and hanger, should they just make all their students use flight simulators and demolish their runway? Should an agricultural school sell off their farmland to real estate developers? If their students really weren't benefiting from their property, then they should donate it to some organization that could carry on the spirit of what they were supposed to be doing with it.

Re:MIT no longer owns 18.0.0.0/8 by zkms on Wednesday April 19, 2017 @07:44PM (#14152793)
> Why should a university deploy it, and introduce all sorts of new problems? Mine hasn't. And I don't blame them.

If your university doesn't have a lot more demand for IP addresses then yeah -- it makes sense that they'd just hold on to their network space, continue to NAT their DHCP pools and keep doing what they're doing. That's not an indictment of IPv6, it just means that the work to deploy IPv6 doesn't provide any benefits to them. However, newcomers and networks that foresee expansion can't just "stay the course" -- there just isn't enough IPv4 for them -- and do need to bite the IPv6 bullet.

Deploying IPv6 does indeed require work in terms of management (all tools that assume the length/format of an IP address need to be updated, netadmins need to learn and deploy RA guard and friends) and your network silicon needs to do IPv6 in the fastpath -- but even with all these pain points, carrier-grade NAT'ing IPv4 is nevertheless more painful, expensive, and slow.

Forward-thinking network operators have been taking advantage of the LTE and DOCSIS 3 transitions to enable native IPv6 everywhere, and Facebook is moving to IPv6-only infrastructure -- and it's paid off! About 80% of network traffic (to Akamai) from T-Mobile and Verizon is IPv6 (from Comcast it's lower -- around 50%): https://www.akamai.com/uk/en/our-thinking/state-of-the-inter...

The future is IPv6 -- it's just not quite equally distributed yet.

Re:MIT no longer owns 18.0.0.0/8 by ghaff on Wednesday April 19, 2017 @07:51PM (#14152828)
>If they don't have a use for them, they should make them available for someone who does. Not just sell them to be used for some corporation's infrastructure.

Isn't selling them off to someone who will pay money for them pretty much the definition of making them available for someone who has a use for them?

It's not like you can't buy an IPv4 address if you want one because Amazon and Google own them all.

We just have this situation where a few universities, the US DoD, and a handful of corporations own a disproportionate number of IP addresses because they were early to the game. They all got cheap IPv4 addresses. So HP owns two /8 addresses while Google does not.

I'm not seeing a situation where donating millions of IPv4 addresses to someone is going to improve society relative to Amazon forking over a bunch of dollars to a university.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Thursday April 20, 2017 @01:28AM (#14154201)
I guess it's a matter of opinion. If a university had some prime real estate, they could sell it to the highest bidder so that they could build a shopping mall, or they could donate it to a non-profit that would improve society in some way, thereby fulfilling their mission, to improve society. Or they could just cash out and getting more money could arguably improve society in a less tangible, less measurable way.

Universities are uniquely positioned to not be constrained by market forces. Part of the reason that universities get privileged access to things, is because they are seen as working in the public interest. Government and business and wealthy donors throw money at universities, because they want to see innovation and public good come from it.

Maybe that's idealistic of me, and universities are just a kind of business, and only that. MIT already gives the public free hosting, with an externally routable, unfirewalled ip4 or ip6 address, to anyone who comes on campus. I don't think any other universities in the world do that. And MIT does this at great expense. (this is how Aaron Schwarz was able to download so much of JSTOR)

It makes no financial sense for MIT to be doing this. Perhaps they should lock down their network as much as possible, and probably outsource it's management.

Re:MIT no longer owns 18.0.0.0/8 by ShirleyMarquez on Friday April 21, 2017 @11:30PM (#14170979)
That hasn't been completely true for a few years. If you just walk onto campus with a wireless device and use the public network (the one that doesn't require authentication) you get a 10.x.x.x address behind a NAT and it has some firewall restrictions. (They're pretty light; it's mostly to keep out some network attacks.) I think you do still get a public address if you plug into an Ethernet port, and you may get one if you use the MIT SECURE wireless network.

MIT's network policies are not purely about what makes financial sense. The Institute was one of the birthplaces of the internet, and they see the ongoing development of it as one of their core missions. MIT has a close relationship with W3C, which is located a stone's throw away. Their network is multi-homed to the max; I think they peer with ALL the backbone providers that operate in the US. The school has ludicrous amounts of internet bandwidth; I think it's now measured in terabits per second. After all, they have to be able to cope with thousands of students watching Netflix along with all the research!

And just in case there is a REAL internet collapse... they have an emergency info site at mit.NET that is hosted far away from the campus. That would let them get some information out even if Cambridge were wiped off the map and all the name servers for .edu were to fail.

Re:MIT no longer owns 18.0.0.0/8 by flyinghamster on Wednesday April 19, 2017 @07:02PM (#14152558)
On Linode, were you using the default single IPv6 address, or did you request a prefix? I found that the default address was in a blacklisted /64, and couldn't send email without it getting bounced or blackholed. Once I got my own /64, the problems went away (but DKIM+SPF was also mandatory).
Re:MIT no longer owns 18.0.0.0/8 by lamontcg on Wednesday April 19, 2017 @06:41PM (#14152445)
We really need to just pick a date and turn off ipv4 because its the only way to make this guy change.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @06:57PM (#14152520)
It's not me that's fixated on ipv4. I would love ipv6. But why aren't ISPs providing it? Why aren't universities and other large organizations switching to it by default?

ISPs don't care. They would rather everyone just use carrier-grade NAT.

Re:MIT no longer owns 18.0.0.0/8 by lamontcg on Wednesday April 19, 2017 @07:56PM (#14152862)
Because someone works at those universities or ISPs who is making the same argument you're making. If enough of you all throw your hands in the air and say 'not enough people are doing it' then there will never be enough people doing it. At some point someone needs to point a (metaphorical) gun at your heads and make you all do it or else.

In the meantime, you should feel bad every time you make this argument because you're helping to make the world worse and enabling everyone else to just kick the can down the road.

Re:MIT no longer owns 18.0.0.0/8 by flyinghamster on Wednesday April 19, 2017 @04:55PM (#14151677)
I've tried to run IPv6 on my Comcast connection. Unsurprisingly, Comcast doesn't get the point of IPv6. They allocate one single IPv6 address to my router. That's right, ONE. LOUSY. ADDRESS.

This seems to be a "feature" of owning your own modem rather than renting one of theirs. I hesitate to even try to get this fixed via their tech support.

I guess if I want IPv6 connectivity, I'm either going to have to get a tunnel from Hurricane Electric (SIXXS is shutting down), or carve out some IPv6 space from my Linode and tunnel it to my home network.

Re:MIT no longer owns 18.0.0.0/8 by ajross on Wednesday April 19, 2017 @06:03PM (#14152234)
Actually, Comcast supports DHCP prefix delegation (I'm led to believe everywhere, but it works at my home anyway), which is pretty much the Right Thing in this space. Your default DHCPv6 request is from a single client and it returns a single IP, as expected. And you can then do NAT across that if you want, which is what their default routers do.

But if you want a subnet, you can make a second DHCPv6 request with prefix delegation metadata, and the server will establish a route for a full /64 subnet to your existing IP and return it to you. Then you can hand these out however you want (though they won't give you bigger than a /64 so you can do internal subnet routing).

The only annoyance is that none of the existing Linux distros support this yet as part of their network client integration, so you have to script it yourself around dhclient (see the -P argument), which is a little hairy if you want to get the hooks right (I punted and just did it once manually and left dhclient running).

Re:MIT no longer owns 18.0.0.0/8 by flyinghamster on Wednesday April 19, 2017 @09:10PM (#14153200)
UPDATE: I now have IPv6 connectivity via my shiny new EdgeRouter POE. Now I just have to poke a few holes in the firewall where appropriate (now that I've set drop-by-default rules).

Getting it to work with the ER-POE was non-intuitive but not as bad as I was expecting. I'm even getting a /60...

Re:MIT no longer owns 18.0.0.0/8 by kiallmacinnes on Thursday April 20, 2017 @05:31AM (#14155185)
I suspect most people don't use a Linux box as their router (with the obvious exception of router distros and embedded Linux on routers).

Most people will read this, I think, and think a Linux client won't accept a V6 from a router that has obtained it's delegation via DHCP-PD..

Re:MIT no longer owns 18.0.0.0/8 by pedrocr on Wednesday April 19, 2017 @06:44PM (#14152456)
>The only annoyance is that none of the existing Linux distros support this yet as part of their network client integration, so you have to script it yourself around dhclient (see the -P argument), which is a little hairy if you want to get the hooks right (I punted and just did it once manually and left dhclient running).

I think OpenWRT has all you need for this. At least I think that's exactly what I did with my ISP config on my own router just with the LuCi web interface.

Re:MIT no longer owns 18.0.0.0/8 by ihattendorf on Wednesday April 19, 2017 @06:47PM (#14152478)
Yep, same with Cox in my area. I'm running Sophos UTM Home which supports prefix delegation, I'm sure there are others that are plug and play as well.
Re:MIT no longer owns 18.0.0.0/8 by sethj on Thursday April 20, 2017 @12:16AM (#14153904)
Linux doesn't support it? My Comcast router has a /64 given to it by Comcast and all my linux boxes connected to it work like a charm.. although I haven't been able to get my dd-wrt router to pass them on yet.
Re:MIT no longer owns 18.0.0.0/8 by ajross on Thursday April 20, 2017 @12:28AM (#14153971)
Linux supports it just fine, you have to do the integration on your own. If you want to use the distro-provided DHCP setup, you need to work out the NetworkManager hooks on your own to add the PD client at the right spots.
Re:MIT no longer owns 18.0.0.0/8 by virtuallynathan on Wednesday April 19, 2017 @08:47PM (#14153091)
Comcast will give out up to a /60 for residential if you hint for it in DHCPv6-PD.
Re:MIT no longer owns 18.0.0.0/8 by buzer on Wednesday April 19, 2017 @05:08PM (#14151786)
That doesn't sound correct. Are you absolutely sure you aren't also getting a prefix delegation thru DHCPv6? That's currently the common way to provide IPv6 connectivity currently for residential users.

From what I remember hearing, Comcast was giving /60s thru PD.

Re:MIT no longer owns 18.0.0.0/8 by flyinghamster on Wednesday April 19, 2017 @05:27PM (#14151954)
No, I don't get a prefix. No /60, no /64, not even a /120, just one single address. A /128. Maybe I should jump on their forums and raise a fuss. I'm not at all confident that calling tech support would get me to someone who even had a clue what IPv6 is.
Re:MIT no longer owns 18.0.0.0/8 by kiallmacinnes on Wednesday April 19, 2017 @06:02PM (#14152228)
Just to be sure, with a routed network being aimed at your house, you'll actually receive two subnets (well, a single address in one subnet, and a whole second subnet). You need to use DHCP-PD or similar to make use of it.

The /128 sounds perfectly normal, and is used as a "point to point" link between the ISP and your modem. Over this, DHCP prefix delegation typically gives you a whole second subnet of /60 or so. If your modem isn't handling DHCP-PD, then all your see is 1 measly address even though they've likely allocated and pushed 295,147,905,179,352,825,856 addresses to you.

Re:MIT no longer owns 18.0.0.0/8 by flyinghamster on Wednesday April 19, 2017 @07:06PM (#14152578)
Hmmm, maybe I should revisit this. I first tried it a year or so ago with pfSense on a virtual machine. Between the IPv6 issues and generally poor performance (long story), I went back to my IPv4-only configuration with DD-WRT on a D-Link DIR-825.

I'm now using a Ubiquiti EdgeRouter POE, and maybe I should give it another shot. I'm not convinced I'll actually get a prefix from Comcast, though.

Re:MIT no longer owns 18.0.0.0/8 by mjcl on Wednesday April 19, 2017 @08:34PM (#14153022)
It may differ by region, but in the SF Bay Area I've been getting a /60 from Comcast residential for a few years now using a MikroTik router. See here: http://i.imgur.com/2mrRk01.png
Re:MIT no longer owns 18.0.0.0/8 by kiallmacinnes on Thursday April 20, 2017 @03:56AM (#14154756)
The edge router can do DHCP-PD, but it needs some configuration for it to do it, there's lots of info on the Ubuiquiti forums about it. Good luck!
Re:MIT no longer owns 18.0.0.0/8 by syncsynchalt on Wednesday April 19, 2017 @07:26PM (#14152694)
Comcast has a decent ipv6 technology group (by necessity - they were an early adopter/innovator of carrier-grade v6 as they have more CPE to address than can be fit into 10/8). If you ever become interested in resolving this you may want to dig through http://www.comcast6.net and see if you can find a direct contact to work with.

I don't have any contacts myself, I'm just a customer and interested observer.

Re:MIT no longer owns 18.0.0.0/8 by Niten on Wednesday April 19, 2017 @11:22PM (#14153669)
I can confirm that, my home network is currently routing a /60 from Comcast.
Re:MIT no longer owns 18.0.0.0/8 by __jal on Wednesday April 19, 2017 @06:42PM (#14152447)
FTR, I don't get a prefix from them, either.

I tunnel all traffic through Comcast via a VPN, though, because I consider them a hostile network, so I don't especially care.

Re:MIT no longer owns 18.0.0.0/8 by apaprocki on Wednesday April 19, 2017 @05:25PM (#14151942)
Not necessarily your situation -- but I noticed this from Time Warner as well and it turned out to be my old Airport Extreme hardware. Even with the latest firmware it wouldn't receive the delegated range. As soon as I upgraded to the latest model, it properly received a delegated range from TWC without me doing anything else. Just saying, there is a lot of reason to hate cable companies, but it's not always their fault :)
Re:MIT no longer owns 18.0.0.0/8 by syncsynchalt on Wednesday April 19, 2017 @07:20PM (#14152660)
That's surprising, in Denver Comcast gives my Time Capsule a /64 (and has for years, we were one of the earlier areas to get v6 service from them). Doubly surprising since the v6 RFCs all but forbid giving out less than a /64, and Comcast is a leader rather than follower of v6 technology. I wonder if the modem manufacturer is at fault instead.

I regularly ssh straight into to my suspended WoL Macbook over v6, and never went out of my way to set up a single bit of it. A half dozen new technologies working perfectly out of the box!

Re:MIT no longer owns 18.0.0.0/8 by VLM on Wednesday April 19, 2017 @05:47PM (#14152102)
"carve out some IPv6 space from my Linode and tunnel it to my home network."

I'm planning on doing exactly this using openvpn as my transport (because I already have an extensive ipv4 openvpn system). Has anyone tried it? I'm not interested so much in how to do it, which I think I know, but in anecdotes along the lines of "it makes openvpn crash" or "linode told me I was being abusive and cut me off" or whatever.

I've had ipv6 for decades I guess. I even got one of the Hurricane Electric "sage" tee shirts last decade. But when sixxs goes down I lose ipv6 connectivity for the first time since the DSL days at the turn of the century.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @06:01PM (#14152210)
I tunnel all of my traffic through my Linode. I had to disable ipv6, because I was getting constant captcha checks from facebook, cloudflare, and google. No matter how many different ipv6 addresses I tried, traffic is always marked as suspicious. As soon as I disabled ipv6, everything went smoothly.
Re:MIT no longer owns 18.0.0.0/8 by kiallmacinnes on Wednesday April 19, 2017 @06:26PM (#14152363)
This sounds like CloudFlare etc have just blacklisted hosting provider IPv6 blocks, as there a real easy way to get millions of "clean" IPs priced by the hour.

CloudFlare etc certainly dont do this with SiXXS IPv6 addresses, or any traditional residential provider I'm aware of.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @07:09PM (#14152596)
Well, I'd love to use ipv6. In fact, I can't wait. But, what am I supposed to do?

  * T-mobile: ipv4  
  * Office: ipv4  
  * Verizon: ipv4  
  * University: ipv4
  * Linode: ipv6 (but flagged as hostile)
Google will not just show me captchas, but will deactivate accounts if I use some of their apis. I had to reverify several accounts when I've tried using ipv6.

I'm not being backward about ipv4, I'm really not. But we're in denial about the fact that we still live in an ipv4 world. And I don't like seeing the last vestiges of non-profit ipv4 address space being liquidated.

Re:MIT no longer owns 18.0.0.0/8 by virtuallynathan on Wednesday April 19, 2017 @08:48PM (#14153095)
T-Mobile stopped handing out IPv4 addresses to handsets on iOS 10 -- IPv6 Only.
Re:MIT no longer owns 18.0.0.0/8 by crisopolis on Wednesday April 19, 2017 @10:27PM (#14153486)
Yeah, T-Mo is IPv6 on smartphones such as Android/iPhone.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Thursday April 20, 2017 @10:22AM (#14156870)
I route all of my mobile traffic through an older Android device that only connects to their 3G network. Maybe that's why...
Re:MIT no longer owns 18.0.0.0/8 by geraldcombs on Wednesday April 19, 2017 @05:11PM (#14151816)
You should be able to get a /56 or /60 from them using DHCPV6-PD.
Re:MIT no longer owns 18.0.0.0/8 by eximius on Wednesday April 19, 2017 @06:32PM (#14152397)
I have Comcast and get a range. It may be a regional thing or your setup is just wonky.

Granted, I have business class so that I don't violate their ToS by hosting stuff and to get a dedicated IP.

Re:MIT no longer owns 18.0.0.0/8 by jagger27 on Wednesday April 19, 2017 @05:07PM (#14151779)
Rogers in Canada gives /64, which is lovely.
Re:MIT no longer owns 18.0.0.0/8 by lokedhs on Wednesday April 19, 2017 @09:32PM (#14153274)
My old ISP gave me a /64 and it was anything but lovely. It's too small to break up into subnets, and they were unable to give anything larger.

This caused me to switch ISP's and now I have a static /48. That's much nicer.

Re:MIT no longer owns 18.0.0.0/8 by scott00 on Wednesday April 19, 2017 @06:56PM (#14152519)
I get a /60 from Comcast in Chicago.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @07:33PM (#14152720)
> Even your comment about streaming, seems like mainly nostalgia vs reality as you kind of admit. Any modern streaming infrastructure works from behind a NAT since most people are behind one these days.

If I tried streaming a conference on youtube, facebook, or periscope, my stream could be muted or stopped because someone plays copyrighted music or something.

Re:MIT no longer owns 18.0.0.0/8 by cperciva on Wednesday April 19, 2017 @04:35PM (#14151507)
That's too bad. I think universities should make these resources that they've been granted available to students and researchers.

They are... indirectly. MIT can do far more to assist students and researchers using the money they raise by selling off IP addresses than they can by holding on to the addresses in case 16 million students all decide that they want to host their own podcasts.

Re:MIT no longer owns 18.0.0.0/8 by ShirleyMarquez on Friday April 21, 2017 @11:32PM (#14170984)
16 million students!! The school only has a bit over 11,000 students, and just over 12,000 faculty and staff. In other words, they had about 700 addresses per person. After the sale they will only have 350.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @05:59PM (#14152200)
I don't think MIT needs any more money. Universities are often endowed with special assets that others organizations are not.

Yes, universities should dole out as many IP addresses as students want. Where else will students get an opportunity to build something with that infrastructure?

Maybe the university could use their infrastructure to create a non-profit ISP that serves some underutilized market.

If I were endowing land to a university, I would want them to use it, or make it available for the public good. Not just sell it off.

Re:MIT no longer owns 18.0.0.0/8 by klodolph on Wednesday April 19, 2017 @06:55PM (#14152510)
How many IP addresses do the roughly 12,000 students, 1,000 faculty, and 8,600 staff at MIT use? Do they use an average of 800 publicly-routable IPv4 addresses per person? Do they need that many? Do they want that many? Do they have projects that would actually use those IP addresses?

Mind you, an /8 block might sell for maybe $3-$7 per address, or $50M on the conservative side.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @07:01PM (#14152548)
If the ip addresses really aren't useful to them, they can provide them to someone who could carry on their spirit of improving society.

How about providing services to the general public in some way, then? Transfer them to a non-profit trust that will allocate them to anyone who would do something important with them.

If a university had extra land, I would argue that they provide it to someone who could give it back to the public in some way.

It is because universities are supposed to do this in the first place, that they are endowed with things.

Re:MIT no longer owns 18.0.0.0/8 by klodolph on Wednesday April 19, 2017 @07:08PM (#14152584)
I don't think we agree on what the purpose of a university is. I'd say the purposes of a University are research and post-secondary education. MIT is not some kind of general-purpose charity with the vague goal of improving society. It sounds like they decided that $50M is more useful than an /8 block for achieving their mission.

All I'm hearing in response is the unjustified assertion that the IPv4 addresses are more useful somehow. I'd like to hear why the IPv4 addresses are so useful, and why you need 17M of them, and how they'll improve society more than $50M of research or education would.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @07:23PM (#14152678)
Obviously IPv4 addresses are useful, because people are offering money for them. My understanding of what they are used for, is to support clients behind NAT. But there could be some further application that I am not aware of.

If IPv4 addresses are useful to Microsoft or Amazon, then perhaps they can be useful to the general public, in some way. Indeed, MIT already provides IPv4 hosting to anyone who physically shows up at their campus. Maybe MIT could grant their IP addresses to a non-profit that would find a way to improve society.

It's debatable what universities should be doing. I've talked about this with several people who work in grant writing, and administration of well respected universities. What I have been told, is that it is generally the job of universities to educate certain people, with the end goal of improving society, and the world. And that is what justifies universities hand picking who they educate; affirmative action. So, picking out students from poor and marginalized communities, and targeting them for education, would arguably do more good for society as a whole. Universities played a part in ending slavery, by demonstrating that black people could indeed compete with white people intellectually. And that this mission is explicitly laid out in the charters of many universities.

But, I'm aware of how indirect that is. Not everyone will agree. And certainly not all, if not most universities are like this. I think a lot of universities are just educational and research facilities.

Re:MIT no longer owns 18.0.0.0/8 by klodolph on Thursday April 20, 2017 @04:05PM (#14160335)
This answer is profoundly unsatisfying.

It sounds like the argument is that IPv4 addresses are useful to ISPs and cloud providers, therefore they must be useful to MIT. Somehow. The question of why IPv4 addresses would be useful to MIT is completely dodged.

I am also reading the comment about what universities should be doing and it sounds contradictory. You say the job of a university is to "educate certain people", but then complain that some universities are "just educational and research facilities". It feels like complaining that a bakery is "merely a provider of baked goods".

Education and research are part of the university's mission. Making the world a better place isn't the mission, it's the desired outcome of education and research. So giving grants to students so they can attend classes furthers the university's mission, and giving grants to faculty so they can do research furthers the university's mission, but providing IPv4 addresses to some vague hypothetical project is not part of MIT's mission.

Re:MIT no longer owns 18.0.0.0/8 by johncolanduoni on Wednesday April 19, 2017 @06:24PM (#14152356)
MIT may not need more money, but I guarantee you there are people there who could do something productive with a grant. Many more than can do something productive with 1000 public IP addresses anyway.
Re:MIT no longer owns 18.0.0.0/8 by corford on Wednesday April 19, 2017 @05:55PM (#14152161)
Given ipv4 exhaustion I'm not sure the pros outweigh the cons but your post just triggered some happy long forgotten memories.

Manchester Uni (circa ~2001) as part of JANET (https://en.wikipedia.org/wiki/JANET) had unmetered, unfiltered 100Mbit ethernet ports straight into all the dorm rooms, each with a dynamic public IP on the end. A publicly routable 100MBit line back then was a big deal (the fastest connection I could get at my parents was a bonded ISDN line).

It was thanks to that that I first started playing around with linux (RedHat 5 or 6 back then iirc). I remember assembling a server box with cheap PC parts, hosting an FTP (...posting the Dyn domain for it to alt.2600 and later getting in trouble after the uni received a letter from Universal :), running audiogalaxy satellite 24/7, setting up an IRC server for me and my friends to co-ordinate Quake 2 games (or counter strike - can't remember), trying (and failing) to do my own email with qmail and all sorts of other fun stuff I've forgotten. Good times.

Re:MIT no longer owns 18.0.0.0/8 by drzaiusapelord on Wednesday April 19, 2017 @04:43PM (#14151590)
>I think universities should make these resources that they've been granted available to students and researchers.

MIT student body size: ~11,200

Unique IPs on this block: ~16.7 MILLION.

That's ~1500 unique IPs per student.[1]

>Students ran servers in their dorms. Clubs ran servers. Some professors ran servers.

Well, they're still keeping a whole boatload and IPv6 is here, so you're lamenting a scenario that isn't actually happening. MIT students will not have a shortage of IPs for such activities.

Sorry, but we're way past the point of any rational argument to reserve 16 million ipv4 IPs for such a tiny student body. IPv4 hoarding is counter-productive. It keeps organizations from moving to v6 in a timely fashion and over-powers organizations that ran quickly during the IP goldrush way back when. Its not merit based and its just dirty politics as far as I'm concerned. We have v6 now and setting up v6 to v4 gateways is trivial for v4-only destinations. If anything if you love hacking around and setting up boxen then you should be thrilled at what v6 is offering and the amount of addresses you can trivially get, not the opposite. Its legitimately democratizing due to the lack of scarcity while v4 allocation is nothing but representative of the dirty politics and dirty economics of scarcity.

I doubt Vint Cerf is crying in his cornflakes about MIT giving up v4 addresses, and I would assume he's thrilled to hear about v6 getting more traction:

Some researchers wanted a 128-bit space for the binary address, Cerf (recalled) ... But others said, "That's crazy," because it's far larger than necessary, and they suggested a much smaller space. Cerf finally settled on a 32-bit space that was incorporated into IPv4 and provided a respectable 4.3 billion separate addresses.

"It's enough to do an experiment," he said. "The problem is the experiment never ended."

http://www.networkworld.com/article/2227543/software/softwar...

[1] MIT is only giving up half of this mother lode, so each student merely is allocated ~700 each. MIT also claims 14m of those IPs have never been used in internet history.

https://gist.github.com/simonster/e22e50cd52b7dffcf5a4db2b8e...

Re:MIT no longer owns 18.0.0.0/8 by gpvos on Wednesday April 19, 2017 @05:25PM (#14151943)
MIT keeping their /8 would actually make IPv4 addresses more scarce and thus encourage other organizations to migrate to IPv6 faster. But on the other hand, they would be crazy not to do anything with that money.
Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @05:55PM (#14152160)
> MIT is only giving up half of this mother lode, so each student merely is allocated ~700 each. MIT also claims 14m of those IPs have never been used in internet history.

Good. I didn't realize how many ip addresses they have. I think that universities are endowed with finite resources like land or ip addresses have a responsibility to make them available to students and fellows, and by extension, improve society.

Selling everything to the highest bidder isn't something I want to see done.

Re:MIT no longer owns 18.0.0.0/8 by ShirleyMarquez on Friday April 21, 2017 @11:17PM (#14170948)
MIT had about 700 IPv4 addresses for every human being involved with the Institute - students, faculty, and staff. They're only putting half of them on the market, so they will still have 350 per person. I don't think it's going to compromise the quality of their network services or the availability of IP addresses for people who want them.

Like most large institutions, MIT doesn't give public IP addresses to most client devices (desktops, laptops, phones, and tablets); they get DHCP address in the 10.x.x.x range behind a NAT because it's a bit easier to firewall them that way. But real IP addresses are available if you need them to run services.

Re:MIT no longer owns 18.0.0.0/8 by apostacy on Wednesday April 19, 2017 @04:34PM (#14151505)
A student ran an IRC server (necromancy.poly.edu) that anyone could connect to from outside the network, if they used their student VPN. I love that that was possible.

There were so many cool projects that their network facilitated. I went to this exhibition, after the network "upgrade", and spoke to a student who's wearable device gets sensor readings from itself using HTTP to a node.js server hosted on a VPS. He was having latency issues.

Re:MIT no longer owns 18.0.0.0/8 by rlyshw on Thursday April 20, 2017 @08:58AM (#14156219)
I'm the VP of the Linux users group at the University of Delaware and we have several servers in the central data center connected to the university's subnet(128.4.0.0/16) with unfettered access to the general internet. No NAT, and limited firewall.

Our Webserver is on a subdomain of the .edu(lug.udel.edu) and is totally accessible from the internet. It even listens for incoming connections. We run a mail server, a mirror, and an IRC server on there. It's great because even alumni can connect from wherever. I think there is a central firewall for every connection coming in, but I haven't run into problems for my uses.

In fact, every system registered for an IP on the UD intranet is assigned a public, world-accessible IP on the 128.4.0.0/16 subnet and can listen for incoming connections. Even wireless devices.

Re:MIT no longer owns 18.0.0.0/8 by tanderson92 on Wednesday April 19, 2017 @05:52PM (#14152140)
Many universities still own generous blocks, though historically there were possibly many more[1]. My university, Caltech, still has the 131.215.0.0 - 131.215.255.255 block and has student dorms, graduate student housing, and office buildings wired up exactly as you describe. They also happen to own the 134.4.0.0 - 134.4.255.255 block, though I have never seen an actual server used there linked externally or internally.

[1] http://answers.google.com/answers/threadview?id=339445

Re:MIT no longer owns 18.0.0.0/8 by notyourwork on Wednesday April 19, 2017 @05:59PM (#14152201)
131.215.0.0/16

134.4.0.0/16

Re:MIT no longer owns 18.0.0.0/8 by tanderson92 on Wednesday April 19, 2017 @06:43PM (#14152453)
I don't follow.
Re:MIT no longer owns 18.0.0.0/8 by p4lindromica on Wednesday April 19, 2017 @06:59PM (#14152533)
contiguous IP blocks are typically denoted in CIDR notation
Re:MIT no longer owns 18.0.0.0/8 by RyJones on Wednesday April 19, 2017 @06:57PM (#14152522)
More compact notation for the address blocks
Re:MIT no longer owns 18.0.0.0/8 by sallyfour on Wednesday April 19, 2017 @05:24PM (#14151936)
CMU does still provide a public ip over wifi. You can even specify if you want a static one for a given mac address.
Re:MIT no longer owns 18.0.0.0/8 by driverdan on Wednesday April 19, 2017 @06:01PM (#14152217)
Are there schools that NAT student computers? That would be pretty shitty.