I'm looking for some information on the four largest US mobile phone
carriers and the current state of their IPv6 infrastructure. Specifically,
we are trying to figure out:
1. How much of the carrier core and edge for AT&T, Verizon. T-Mobile, and
Sprint are on IPv6 now?
2. If, and how, are they handling NAT64 for native IPv6 edge devices?
3. What is the percentage of breakdown for users on native IPv6? Dual
stacked?
GREE is a mobile social gaming company and we're trying to better
understand what lies between our customer's smart phones and our servers.
My next step will be to reach out to the carriers themselves, but I figured
many of their Network Engineers are probably on the NANOG mailing list and
this would be a great place to start.
I'm looking for some information on the four largest US mobile phone
carriers and the current state of their IPv6 infrastructure. Specifically,
we are trying to figure out:
1. How much of the carrier core and edge for AT&T, Verizon. T-Mobile, and
Sprint are on IPv6 now?
Hi,
T-Mobile USA has native ipv6 to all subscribers in all of it's coverage
area. But, less than 1% of subscribers use IPv6 because they do not have an
IPv6 capable phone. The Nexus S and Galaxy Nexus work well.
This device challenge will improve in time. Samsung is doing a good job of
bringing IPv6 to Android devices. More info here
2. If, and how, are they handling NAT64 for native IPv6 edge devices?
Yes, NAT64 / DNS64 is used in the case of reaching ipv4-only nodes. If you
are concerned about middleboxs, you should deploy IPv6.
3. What is the percentage of breakdown for users on native IPv6? Dual
stacked?
Small today. As IPv6 becomes the default setting, that will change.
CB
GREE is a mobile social gaming company and we're trying to better
understand what lies between our customer's smart phones and our servers.
My next step will be to reach out to the carriers themselves, but I
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.
IPV6 is present, to my knowledge, on all devices on the Verizon IPV6
LTE network. I noticed its using it to communicate to Google for many
of it's services when I ran a netstat. I believe they mandated
support for it from any certified device.
Cameron contacted me off list and pointed out the steps. Works a treat, NAT64 is handling the IPv4 traffic without any obvious problems, along with IPv6. Smooth and simple. Shame it has to be switched on through some manual steps, but I guess that's understandable for now given it's technically in Beta stage.
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.
Paul Graydon <paul@paulgraydon.co.uk> 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.
Please read and follow the instructions here on how to setup
Feel free to ping me off-list if you see any issues.
From what you wrote, my 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)
Not only does Verizon *not* have IPv6 on their LTE network, they also do *not* have IPv4, except for double-NATed rfc1918 crap that changes your IP address every couple minutes. The only way to get a stable connection is to pay them $500 to get a static public IP address.
I suppose they are selectively letting certain devices in some areas. I get "der duh, what?" when I ask about it.
It certainly does not work on the iPad "3" in Ohio. Not only that, but I can't even pay them to give me a stable IPv4 address, because if you get a static IP, it disables the hotspot functionality. Head-->Wall.
I suppose they are selectively letting certain devices in some areas. I get "der duh, what?" when I ask about it.
uhm... you asked someone at their kiosks/stores about ipv<anything>??
you are a very, very brave man.
It certainly does not work on the iPad "3" in Ohio. Not only that, but I can't even pay them to give me a stable IPv4 address, because if you get a static IP, it disables the hotspot functionality. Head-->Wall.
good times!! mobile carriers live in what seems like a very different
world from the one the rest of the internet lives in
(cameron's folk aside, where there are still some oddities, at least
you can get working ipv6, and mostly working v4... or working enough
that I can tether my phone and vpn over that connection when
necessary)
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"
> I suppose they are selectively letting certain devices in some
> areas. I get "der duh, what?" when I ask about it.
>
uhm... you asked someone at their kiosks/stores about ipv<anything>??
you are a very, very brave man.
No... the Business technical support via telephone. They knew what I was talking about, but no idea about what VZW's plans are for it.
> It certainly does not work on the iPad "3" in Ohio. Not only that,
> but I can't even pay them to give me a stable IPv4 address,
> because if you get a static IP, it disables the hotspot
> functionality. Head-->Wall.
>
good times!! mobile carriers live in what seems like a very different
world from the one the rest of the internet lives in
Tell me about it. I would settle for a stable IPv4 address (dynamic is fine, but a "lease" time of something closer to an hour, rather than 2 minutes)
> I suppose they are selectively letting certain devices in some
> areas. I get "der duh, what?" when I ask about it.
>
uhm... you asked someone at their kiosks/stores about ipv<anything>??
you are a very, very brave man.
No... the Business technical support via telephone. They knew what I was talking about, but no idea about what VZW's plans are for it.
yea... so keep in mind that vzw and set(vzb(former mci/uunet) / vzt
(the phone company that owns the copper AND also deployed FIOS)) are
very, very different things.
I think inside vzb/vzt there's some oddness in their planning process
for v6, it's completely divorced from the vzw planning. If you want
answers about your vzw mifi/phone/tablet you can only ask vzw
kiosk/etc people
> It certainly does not work on the iPad "3" in Ohio. Not only that,
> but I can't even pay them to give me a stable IPv4 address,
> because if you get a static IP, it disables the hotspot
> functionality. Head-->Wall.
>
good times!! mobile carriers live in what seems like a very different
world from the one the rest of the internet lives in
Tell me about it. I would settle for a stable IPv4 address (dynamic is fine, but a "lease" time of something closer to an hour, rather than 2 minutes)
maybe they already did the CGN thing to their network, lots and lots
of single IP sharing by port number! look, it's the future!
From: Christopher Morrow [mailto:morrowc.lists@gmail.com]
>
> Not only does Verizon *not* have IPv6 on their LTE network, they also
do *not* have IPv4, except for double-NATed rfc1918 crap that changes
your IP address every couple minutes. The only way to get a stable
connection is to pay them $500 to get a static public IP address.
>
wierd, I could swear someone in my office with a galaxy-nexus-on-vzw
was able to browse some ipv6-only sites.
My Moto Droid RAZR is most definitely IPv6 over LTE.
