Hacker News Reader

Comment by betaby | Hacker News Reader

I some what skeptical about all those IPv6 launch days. Residential IPSs across the world really do not care. Meanwhile in Canada for example Rogers gives 3G/LTE users IPs from the 25.0.0.0/8 (UK Ministry of Defence) and then NAT them to the pool of the real IPv4 IPs. No IPv6 as you may guess.

View on HN

Comcast is going for a pure IPv6 core network, they are currently at 60% of their customers getting an IPv6 address of some sort (cable modem or even cable box).

T-Mobile's network is IPv6 as well. Especially for customer devices that support 464XLAT: https://sites.google.com/site/tmoipv6/464xlat

There is a LOT of support for IPv6, and many companies like Facebook are finding that IPv6 actually offers better performance end to end for their users.

Take a look at this NANOG presentation: https://www.youtube.com/watch?v=EfjdOc41g0s

To me, enabling IPv6 actually caused some weird issued[0], and had to turn it off... Seems to be more place that can go wrong by just enabling it...

[0] http://forums.xfinity.com/t5/Home-Networking-Router-WiFi/Net...

Kabel Deutschland utilizes DS-Lite, effectively making the network IPv6 native. Comcast has been doing quite a bit of interesting work with going native IPv6 internally.

I am a huge proponent of LISP and this is one of the "coolest" uses of LISP I've seen yet: https://www.nanog.org/sites/default/files//meetings/NANOG64/...

As far as I can tell, T-Mobile in the US provisions handsets with IPv6 by default.

How is your experience? If you tether, do you get IPv6 on your laptop as well? Is IPv4 traffic NATed or not ?

I'm not the OP, but when I tether with my Nexus S (running Cyanogenmod), I get an IPv4 address in RFC 1918 space. T-Mobile gives their handsets only an IPv6 address. They also used to use -I think- NAT64, which meant that direct access to resources by their IPv4 address failed. [0] IIRC, their IPv6->IPv4 bridging method has been changed, so you can access IPv4 resources by their address now.

[0] T-Mo was using -I think- the return of an A record in DNS lookup to establish a NAT mapping, so IP access without the lookup didn't trigger the mapping.

I just got an iPhone 6 Plus from T-Mobile a couple days ago, and I don't seem to be getting an IPv6 address over LTE. Maybe they aren't doing it everywhere yet?

I'm in Western Washington, in the Puget Sound area on the other side of the water from Seattle.

On Android, you can just go to "Settings" -> "Cellular networks" -> "Access point names" and choose whether you want to request an IPv4 or IPv6 address.

As far as I can tell (from looking at https://support.apple.com/en-us/HT201699), iOS doesn't have an equivalent option, so it probably just doesn't support IPv6 over cellular networks yet.

Reply on news.ycombinator.com