MIT no longer owns 18.0.0.0/8

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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

[ Parent | on HN ]