Re: Current IPv6 state of US Mobile Phone Carriers
Paul Graydon writes: > That's interesting. I have a Galaxy Nexus on T-Mobile USA and it > doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my > wireless network at home. Doesn't seem to be anything obvious in the > settings to enable or disable that. Same here. IPv6 works fine over my wifi, but doesn't work at all over tmobile. If I play with the cell settings to allow ipv4/ipv6 in APN then all communication stops. TMO might need to go back to those drawing boards. I don't see ipv6 working at all over their network. -wolfgang -- g+: https://plus.google.com/114566345864337108516/about
Re: Current IPv6 state of US Mobile Phone Carriers
Cameron Byrne writes: > On May 22, 2012 7:14 PM, "Wolfgang S. Rupprecht" < > wolfgang.ruppre...@gmail.com> wrote: >> >> >> Cameron Byrne writes: >> >From what you wrote, guess is you are using a phone that does not >> >have IPv6 support (only Nexus phones have support today... Other > phones >> >do not have the correct radio / RIL capabilities) >> >> I'm using the Galaxy Nexus GSM bought directly from google a few weeks >> ago. The firmware is up to date as are the apps. >> >> The instructions mention settings and pages that are slightly wrong >> for this phone. I went to the "Mobile network settings" -> "Access >> Point names" -> "T-Mobile US, epc.tmobile.com" -> "APN Protocol". It >> was "IPv4" and I changed it to "IPv4/IPv6" and then rebooted. There >> was no "save" button or menu item. After reboot the ipv4/ipv6 setting >> was still active (so it was saved), but no connection took place. The >> cell tower I'm using is in Fremont, CA (CID 47052 LAC321). Might it >> not be v6 connected? >> > > For the sake of the archive and documenting the confirmed fix, the correct > APN setting for T-Mobile is "IPv6" not "IPv4 /IPv6" Yup. Thanks Cameron! Chosing IPv6 (-only), does work. I can view IPv6-only websites when on a cell connection. Before that only worked when on wifi. -wolfgang -- g+: https://plus.google.com/114566345864337108516/about
Re: F-ckin Leap Seconds, how do they work?
Steven Bellovin writes: > See > http://landslidecoding.blogspot.com/2012/07/linuxs-leap-second-deadlocks.html Maybe we should stop wrenching the poor system time back and forth. We no longer add or subtract daylight savings time (or timezones) to the kernel time, why do we do it with leapseconds? We should really move the leapseconds correction into the display routines like DST and timezones already are. I believe the Olson time code already has ifdefs for doing this. I wonder why the system's internal time isn't run that way. -wolfgang -- g+: https://plus.google.com/114566345864337108516/about
Re: How to force rapid ipv6 adoption
> (IPv6 ONLY insisting on manufacturers implementing 464XLAT is inferior > in every way to dual stack, There is one way it is superior; it rewards web and other content sites that implement IPv6. Unlike dual stack, it applies pressure where it is needed, on the IPv4-only sites. Grottiness can be a good thing. -wolfgang
