Hacker News Reader

Comment by achernya | Hacker News Reader

Author here -- MIT does not currently have IPv6. Although MIT did receive a /24 IPv6 allocation, https://whois.arin.net/rest/net/NET6-2603-4000-1, it's not routable everywhere on campus yet.

Unfortunately, IPv6 deployment is still below 20% (as measured by Google, https://www.google.com/intl/en/ipv6/statistics.html) so a publically-accessible IPv6 address is not yet sufficient.

View on HN

20% is starting to reach critical mass.

Those are the fast moving and the new parts of the internet. I bet that in a few years IPv6 deployment will slow down as the remaining systems become older, less maintained or even opinionated (like me). For many years to come some kind of IPv4 connectivity will remain a requirement to access all of the internet/web.

I'm not switching my private network. This has nothing to do with wider adoption, nor do I have issues with IPv6 as a protocol.

What's blocking me is router firmware. It can do IPv6, but only as an afterthought. Sadly, no level of adoption is going to fix that, until I buy a new router.

Time for a new router, then, and by "new" I mean any produced in the last ten years. I have several old routers in a junk drawer that only do 10/100 and even they support it.

It supports it, but DHCP and the firewall are much less configurable. Things are exacerbated by my being behind 2 routers.

A router that fixes all this is at least 120. That is too much for me. I tried dd-wrt, but that doesn't fix the first router on the chain.

Reply on news.ycombinator.com