Verizon IPv6 LTE

* PC

One more tip: IPv6 will work over the legacy 3g network. Don't ask me
much about it, but it "tunnels" it using eHRPD to the same IP/IPv6 headend
to enable seamless EVDO/LTE handover.

Interesting. Does this happens only if you start out in LTE coverage and
then roam onto EV-DO, or does IPv6 work if you connect to the network
outside of LTE coverage too?

I wonder if there will be similar magic provided for UMTS/LTE networks..

I doubt it. The path there should be to upgrade GSM/UMTS network to release 9 and support v4v6 pdp context and then you don't need any magic at all (as far as I can tell).

Justin M. Streiner

> My understanding, and experience (albeit with Android), is that all
VZW LTE
> is IPv6-capable.
>
> I'd love to hear if Apple or VZW is at fault here, or if something
weird is
> happening ...

I don't know about Apple devices on VZW, but my Android phone
definitely
has IPv6 connectivity on VZW 4G LTE in Pittsburgh.

Same in the DC Metro area. My RAZR is all v6 all the time on LTE.

Jamie

"Please don't hack or ddos it :slight_smile: "

Unfortunately, while you do get an ipv6 address, mobile terminated data
doesn't work, so you don't have to worry about this. It is firewalled by
Verizon.

T-Mobile USA allows mobile terminated data on IPv6

http://www.androidpolice.com/2012/01/29/t-mobile-usa-testing-ipv6-on-select-devices-here-is-what-it-all-means-and-yes-no-more-nat/

CB

So I'm back at the office this morning and the iPad is *not* getting an
IPv6 address but is showing LTE service. It did do IPv6 over LTE at home
so it's not a device problem. So I suppose the closest tower to my
office is not IPv6 enabled.

Is this an expected behavior in some areas or something that needs fixing?

~Seth

Quoting Randy Carpenter <rcarpen@network1.net>:

Safari is definitely preferring IPv4.

In a happier note, if you tether a device via hotspot on an IOS6 iPad, the
clients get native IPv6. Strangely, they get addresses out of the same /64 as the iPad's LTE interface. Anyone know how that is working? I would have thought they would use prefix-delegation, and there would be a separate routed /64.

I assume they're doing the same thing I am. The cell network interface is just a p2p interface, and the whole /64 is routed to the phone/tablet. You can configure the p2p interface address as a /128 and configure the /64 on the wifi interface. My understanding of the 3gpp specs is that the cell provider won't have an address in that /64, so you won't conflict with anything upstream of the phone/tablet.

Here's a screenshot of my (wifi-only) tablet getting v6 while tethered through my phone:
http://dan.drown.org/android/clat/IMG_20120425_105124.jpg

Safari on the iPad seems to be preferring A over AAAA if a hostname has
both, though. I can browse to a bracketed IPv6 address so it is working.

I think perhaps it is time to update test-ipv6.com a bit, and have it penalize the first number when IPv4 is used in preference. IPv4 CGN
will make me a sad panda - especially when IPv6 is available but not being used.

I tested today just for giggles, test-ipv6.com shows I have working ipv4
and ipv6 10/10 on both tests. Interestingly enough I was only seeing 3G on
the device at the time.

So I guess its not just on LTE or is it LTE devices ?

I'm running galaxy nexus on vz with stock jelly bean from the recent ota
update

Sadly my iPad stopped getting an IPv6 address anywhere I normally go,
even at home where it was previously working.

~Seth

I tested today just for giggles, test-ipv6.com shows I have working ipv4
and ipv6 10/10 on both tests. Interestingly enough I was only seeing 3G on
the device at the time.

So I guess its not just on LTE or is it LTE devices ?

I'm running galaxy nexus on vz with stock jelly bean from the recent ota
update

See quote from PC below regarding vzw, which matches colloquial evidence I have seen/heard as well. This is also true of T-Mobile's v6 deployment when switching between HSPA+, Edge, 3G, etc (though I do not know if PC's general explanation of "how" is true of TMo)