IssueTracker

This explains why IPv6 PDP Context fail. I'll have to wait until this bug is solved I
guess.

A must-have for any current OS.

100% agree.  Android needs fully IPv6 support, not just on WiFi.  Mobile is growing
too fast to lock in on IPv4.  Major mobile carriers in the USA already have IPv6
trials in progress, but only Nokia and MSFT are ready today.

IPV6 was implemented by Nulsoft using Winamp client about 5 years ago.  That's a long
time to wait to see it in mobile, I'm kidding.  Please add.

IPv6 should be considered standard, core capability, a MUST ... not an off-in-the-
future "functionality" add.

"IPv6 should be considered standard, core capability, a MUST" ... While I don't feel
quite as strongly, Mobile is an area where I belive IPv6 adoption will take off, if
handsets support it.

Most mobile operators I've dealt with simply don't have enough IPv4 space for their
customers - resorting to leaving their routable blocks idle while giving out 10.x
range IPs!

IPv6 *can* solve this issue. Lets see Google Android leading the way, Barring a
*major* design flaw (considering this platform was designed over the last few years)
there should be no reason why IPv6 support should take any serious effort to include.

Hello,

Could you please quantify exactly what IPv6 features you're missing in current
(2.0/2.1) Android? All the comments I've seen so far refer to pre-2.0.

I do not believe any branch of Android supports IPv6 on the UMTS / Mobile radio
interface.  This is the critical feature that is required for mobile network
operators to deploy IPv6. So, the ask is that Android support IPv6 PDP in compliance
with 3GPP Release 6 or 7.  If Android supports this, it is relatively easy to a
mobile network opeator like T-Mobile USA to launch an IPv6 service.

Here is conversation on the validity of IPv6 on the mobile interface.
http://www.ietf.org/mail-archive/web/3gv6/current/msg00172.html

Here is a demonstration of what a user can do with IPv6 today in conjunction with
IPv6 to IPv4 NAT http://www.youtube.com/theipv6guy

Well, regardless of support for IPv6 on the UMTS interface (which is dependent on
support in the handset's UMTS radio and firmware, as well as of course the carrier's
network), people should at least be aware that Android from 2.0 on supports IPv6 out
of the box (with userspace application support, including in the browser) on the
802.11 interface.

I can confirm that:

http://twitpic.com/xux1q

Is multicast IPV6 (MLDP) implemented as well?

:O) Mikkle

There is IPv6 multicast in the kernel since you basically need it for IPv6 support
(IPv6 has no broadcast). I'm not immediately familiar with MLDP, though -- what do you
want multicast for? It's not like Android uses IPv4 multicast a lot.

My guess, mLDP --> Multicast Label Distirbution Protocol, something like
http://tools.ietf.org/html/draft-wijnands-mpls-mldp-in-band-signaling-02 ... and if
so, not sure it is relevant as the Android device isn't typically going to be a hop
along a LSP :).

But multicast holds a lot of promise for many areas, not excluding mobile devices.  
The device supporting the rudimentary (NDP stuff) multicast is not the same as
allowing applications to joins channels, and the provider supporting it (over cel).  
As previously noted, Wifi IPv6 support is in place - although I haven't tested the
multicast on that interface ...

Sorry, I meant MLD - the equivalent of IGMP in
IPv4.
I just wanted to be assured that the V6 MC
support isn't hobbled and that it's able to traverse
routers.

What about source-specific MC (MLDv2)?
-  not too important up front,  but still...

Why multicast? I want to code apps using it, such
as upnp media controllers,  mdns clients, etc.
Plus I have an IPv6-  and a multicast fetish.

:O)  Mikkle

Still mcast related, so all good ;)

I disagree that SSM is not important, I'd push for all variants of PIM (SM, SSM, BiDir,
E-RP) to be properly supported ... so MLDv2 fully alive, and the provier'
infrastructure supporting it :).

All IPv6, all the time ... /TJ

Just noticed that the browser does not parse literal IPv6 addresses in URLs.
e.g. http://[2001:0db8:cafe:babe::beef]/ipv6ftw.html
This format is specified in RFC 2732.
While not on the top of my list of important v6 stuff, I belive RFC 2732 should be
supported in browser/webkit for completeness.

:O) Mikkle

Now that the first _partially_ 4G phone has been released the demand for IPv6 is now
even greater. IPv6 is almost a requirement for 4G networks (It actually *is* for
Verizon's).

I'm scheduled to do a presentation on IPv6 deployment on mobile operators at Google IPv6 implementors
conference 2010, but apparently I'll have to use Nokia N52 or N900 to do live demo. I would like to see Androida
based phone to do the v6 PDP, so I can also show that something is working there...

N900 now supports two PDP contexts at the same time, resulting in sort of "dual-stack" like behaviour.

Jan Zorz

Lets get android on the T-Mobile Beta network for IPv6 http://groups.google.com/group/tmoipv6beta

I also miss IPv6 over IPv4 tunneling like Teredo.

lostfreeman, please elaborate. v6-over-v4 tunnelling is old hat, and only serves as an educational or last resort mechanism for IPv6 access. Dual-stack is where it’s at.

FYI, problems around IPV4 should happen sometime between now and next year (see for instance http://ipv6.he.net/statistics/ ).

Android needs a complete support of IPv6 (kernel, libc, java, APIs, browser, etc) ASAP. Googlers has to clarify the situation & future of this issue.

Android also needs to help the mobile providers into deploying IPv6. There, a good solution could be to support the 6rd technology (a 6to4 "extension").

See http://tools.ietf.org/html/rfc5569 and http://tools.ietf.org/html/draft-ietf-softwire-ipv6-6rd-10 for details.

6rd helps to perform rapid IPv6 deployment over a IPv4 ready network. This enables developpers to test and deploy IPv6 ready application and users to enjoy them. Doing so, as soon as your backbone is IPv6 ready you can smoothly migrate to full IPv6 without any impact on the users.

not many Europe & USSR mobile providers offer native IPv6 so I can't, for example, connect by rdp from android phone to my home computer as it has no public ipv4 address. I'm not sure if this is typical

every vista and higher user on internet already has full ipv6 connectivity via teredo. this protocol exists on Linux too as miredo. is it too hard to use in android?

The two previous commenters (and the one before my comment) are conflating two very different issues: IPv6 support, and transitioning to IPv6 over IPv4 infrastructure.

If you want my two cents, frankly, I don't give a damn about IPv6 tunnel support. It's rubbish — throw out 6rd out the door. IPv6-in-IPv4 can be deployed on the ISP's end, sure, but that needs to be exposed to the client as native IPv6.

It's not Android's fault if your mobile provider doesn't support IPv6 yet, and setting up tunnels automatically is going to cause tears on account of performance and privacy. However, Android needs to be ready with *native* IPv6 support (i.e. over 3G) for when your mobile provider does.

6rd is not really relevant to Android or mobile CPE in general. While the 6rd RFC is new, it is an overdue solution to a past problem. It worked for free.fr because it was a custom solution to suit their particular infrastructure needs. That's now past, and is a dead end in terms of progress. The way to move forward is native.

Verizon are already mandating native IPv6 support on their 4G mobile devices. Expecting the mobile device to do IPv4 tunnelling on its end is rather pointless at this point in the game.

Tunnelling is over. Gone to Gowings. Dead, buried, and cremated.

Device: HTC Hero (generic europe version)
Android 2.1 with HTC Sense

I have the impression that DHCPv6 is not working on my device. At home, I have a dual stack network where the IPv6 configuration is as follows:
* address allocation is done through stateless autoconfiguration. Router advertisements are sent by radvd and the AdvOtherConfigFlag is set.
* Stateless DHCPv6 is used for distributing dns servers and search domain.

The dns servers that are advertised using DHCPv6 are the SixXS nscache recursive resolvers that participate in Google over IPv6. Clients that pick up these dns servers should thus connect to gmail (amongst others) over IPv6.

When I connect a windows vista machine to this network it picks up these dns servers and happily connects to gmail over IPv6.

When I connect my HTC Hero to this network, it has a working IPv6 config since it connects to for example www.sixxs.net over IPv6. However, it doesn't seem to pick-up the dns servers from DHCPv6, since it keeps connecting to gmail over IPv4. I have tried to verify this by looking at the dns servers android uses for resolving, but I didn't find a way to do that (I tried cat /etc/resolv.conf, but that didn't work).

Is there anybody who can confirm or deny my observations?

ps: The gmail account activity details aren't IPv6-ready. It reports 'unknown source' instead of an IP address when connecting over IPv6.

there is no /etc/resolv.conf on Android. DNS values are accessed as properties. Something like this will display it:

getprop net.eth0.dns1

and they are set with "setprop". I've not tried setting them to IPv6 servers. I'd be interested to hear if that works.

Note: DNS is a bit different on Android. It's possible to have different DNS servers on different interfaces, It's also supposed to be possible to have different DNS configuration for different processes. I don't recall how to set that up, I've not messed with it in a while.

I expect that no Android release includes DHCPv6 services on any interface at present.

I've looked a bit further into this and these are the properties related to dns on my device:

[net.change]: [net.dnschange]
[net.rmnet0.dns1]: [195.130.131.139]
[net.rmnet0.dns2]: [212.53.4.4]
[net.dns1]: [192.168.2.1]
[net.dns2]: []
[net.dnschange]: [14]
[dhcp.tiwlan0.dns1]: [192.168.2.1]
[dhcp.tiwlan0.dns2]: []
[dhcp.tiwlan0.dns3]: []
[dhcp.tiwlan0.dns4]: []

So it appears that:
* there are indeed different properties for each interface
* the ipv6 dns servers are not picked up (it should be somewhere on tiwlan0)
* the dns config of the active interface is copied to net.dns1 and net.dns2

I have tried to manually set net.dns1 to the IPv6-address of one of the SixXS resolvers and that works. After I did so, my device connected to gmail over IPv6!

This protocol will address security issues majorly,we need a new protocol for streaming GOOGLE tv over 3G enabled mobile networks.
At  TRAQR  we  are trying to create an interface for the same

Support for acquiring DNS servers from RAs via RDNSS (see http://tools.ietf.org/html/rfc5006 ) comes baked into the standard Linux kernel, so it should be fairly painless to add this alongside DHCPv6.

RDNSS is presently the only way to autoconfigure DNS on a network that uses SLAAC, so it's a virtual necessity wherever SLAAC is deployed in a public setting.

On the mobile network, the DNS server is generally pushed in PCO IE
http://www.ietf.org/rfc/rfc4339.txt
 section 5.3.1

I understand the needs on WLAN are different, but 3GPP mobile is covered today.

Cameron

Is IPv6 supported on the mobile interface yet?

I have not seen anything official yet, but i remain optimistic that 3G
support i will be soon.

Some details here http://tinyurl.com/2b4j7uk

Cameron

"RDNSS is presently the only way to autoconfigure DNS on a network that uses SLAAC, so it's a virtual necessity wherever SLAAC is deployed in a public setting."

That's actually not the case -- SLAAC can be in place in combination with stateless DHCP.  Works just fine.

Frank

[Comment deleted]

I bought a HTC Desire HD with Android 2.2 after reading that it would support IPv6 but was surprised/disappointed when I realized there was no support for creating an IPv6 PDP.

Getting IPv6 PDP support is essential to me since I want to start using this right away (my carrier supports it already).

Dual PDP support would be nice as well, but getting IPv6-only support (the carrier supports this together with DNS64/NAT64 for v4 access) is more important to me.

In the event that your "IPv6 ready" switches and routers support
neither RDNSS nor DHCPv6 relaying (shame on you, Extreme Networks),
it's nice to have support for falling back to the "well known"
site-local unicast recursive DNS server addresses:
* fec0:000:0000:ffff::1
* fec0:000:0000:ffff::2
* fec0:000:0000:ffff::3

For what it's worth (not much?), this appears to be implemented in
recent versions of Windows and other operating systems  We are
planning to use this approach at our sites until we can find time to
hack together an embedded DHCPv6 relay agent band-aid device for the
aforementioned defective L3 switches.

See also:
* expired draft:
http://tools.ietf.org/html/draft-ietf-ipv6-dns-discovery-07 (to my
knowledge, never incorporated into any ratified standard)
* http://www.tahi.org/conformance/ct-profile-host/dd/DDWellKnown.html

- Aaron

The fec0::/10 range was deprecated in http://www.ietf.org/rfc/rfc3879.txt - its use by Windows is in violation of that decision by the IETF and is very much non-standard.

[Comment deleted]

Yes, please add IPv6 support to Android OS! Thanks in advance.

IPv6 is a minimum reuirement for every modern OS.

This issue is specially important for a mobile device OS, as more and more mobile devices are taking giant bites from the IPv4 pool.

huh, just found out that IPv6 is supported since 2.1

We are requesting IPv6 support over a PDP, not over WiFi.

See the following video clip of IPv6 over PDP on Android 2.2

http://www.youtube.com/watch?v=WlS6NbEEjZM

> http://www.youtube.com/watch?v=WlS6NbEEjZM
It's an industrial terminal, not real handset!
Show me something like this on an ordinary phone, please.
I cannot believe that only Nokia phones could support IPv6 over a PDP...
My old (from 2004!) Nokia 6630 supports IPv6, but HTC Touch HD (WinMo 6.5) and HTC Desire (Froyo) does not!!!
What is the reason? Radio HW, driver... ?

This is a nice video from the summer, but now it is 6+ months later
and there is still no IPv6 3G support in the Android tree.  2.3
Gingerbread does not have it.  Crossing my fingers for Honeycomb....

Cameron

Surprised me to find that it didn't have it.

Android doesn't support IPv6 networks over WiFi, either. When attempting to connect, it just sits there saying «Obtaining IP address...» for a while, before giving up and trying again in an endless loop. The network in question is using SLAAC with the Recursive DNS Server option present. Android version used is 2.3.2 «Gingerbread», handset HTC Hero GSM.

If IPv4 service (via DHCPv4) is added to the network (i.e. dual-stack), it is able to successfully acquire an IPv6 address as well. However, the value of supporting IPv6 only if IPv4 is available is rather limited, especially post-IPv4 depletion. Android needs to support IPv6-only networks, on WiFi and radio interfaces alike.

Tore

"Android doesn't support IPv6 networks over WiFi, either. When attempting to connect, it just sits there saying «Obtaining IP address...» for a while, before giving up and trying again in an endless loop."

This works for me on gingerbread .. stateless IPv6 over wifi works perfectly.. passes 10/10 tests from http://www.testipv6.com/

"This works for me on gingerbread .. stateless IPv6 over wifi works perfectly.. passes 10/10 tests from http://www.testipv6.com/"

But does it work on a IPv6 only network?

I know that URL can only be accessed via IPv4, you would have needed to go to http://aaaa.test-ipv6.com/

If you can get to www.testipv6.com you have IPv4 - that site is not available over IPv6. You probably have a dual-stacked network, which I did point out that Android supports. Connecting to a IPv6 network (with no IPv4 service), on the other hand, does *not* work.

Tore

> I know that URL can only be accessed via IPv4, you would have needed to go to http://aaaa.test-ipv6.com/

Even that would not be a conclusive test as long as IPv4 is enabled on the local network.

Good catch, Tore. Single-stack IPv6 is overlooked way too often.

support

go to http://aaaa.test-ipv6.com/

local network.

+1 single stack ipv6 should be fixed so that works correctly

CB

We're now talking about 2 different issues, you cant connect to a v6 only network, I can .. But our DNS resolvers listen on IPv4 only .. Static IP was setup after a successful connection...

You dont seem to be able to connect in the first place .. I can, and correctly get an IPv6 address without an IPv4 (verified via `ip addr show` before adding a manual v4 address)

I should add .. I'm running CM7 on a nexus one.. some setup was involved in enabling v6 as CM intentially disables it by default.. cant remember the exact steps, I found the instructions in their commit logs of all places!

If «some setup» is required, it doesn't count. It needs to work out of the box, or it is equivalent to «doesn't work at all» for 99%+ of people.

Tore

The lack of support (in android 2.1) for (stateless) DHCPv6 and/or DNS configuration via RA (RFC 6106) is also problematic in IPv6-only networks. It means there is no support to configure a recursive DNS resolver (except for manual configuration).

Yes, support for RFC 6106 is really really important. Please, consider that if possible.

Apparently, the HTC Thunderbolt supports IPv6 on the radio interface, cf. <http://www.youtube.com/watch?v=GH4KJ-4eM8w>.

Does anyone know whether:

1) It supports IPv6-only cellular networks too, like T-Mobile's?
2) It supports IPv6-only wireless networks too?
3) If the support is in Android proper, or if it is HTC-specific extensions?

By the way: I've been told that the latest iOS version make the iPhone/iPad capable of connecting to IPv6-only wireless networks in a usable fashion (i.e. it is capable of configuring IPv6 DNS resolvers).

Tore

It does not. It only works with LTE.

You mean WiFi?  I am not sure, but my guess is no since this an HTC
specific solution and not part of Android.

HTC specific, since it is not part of the Android code tree.

Okay, it's disappointing to hear that it's HTC-specific support. But I guess the Android developers can no longer blame the lack of IPv6 support in Android on the baseband.

When you say it only works with LTE, does that mean that if the phone is outside LTE coverage it is unable to use IPv6, or that it cannot fall back on 3G connectivity at all?

Wifi is a separate but similar issue: last I checked, Android was completely unable to connect to IPv6 wireless networks. However it is able to use IPv6 on dual-stacked wireless networks, but that's of course inadequate as we really need an IPv4 exit strategy at this point in time.

Tore

* disclaimer ... I do not have any inside knowledge on Android IPv6
support, Verizon IPv6 support, or HTC.  But, i have played with the
Thunderbolt and have made some assumptions based on what i have seen.

Well, this is still a case by case, oem by oem, basis.  Verizon did a
good job of mandating IPv6 for all their LTE products.

That's correct.  The Verizon CDMA network, AFAIK, does not support
IPv6 in any way.  Therefore, IPv6 connectivity is only provided when
on LTE v4v6 connections.  GSM/UMTS/LTE providers have an advantage
here since they have a more common infrastructure pieces between
2G/3G/4G.  AFAIK, the Thunderbold is like the Sprint WiMAX phones.  It
is a normal CDMA 3G phone with a LTE radio strapped on to it.  It is
not a "full native" LTE phone, LTE on this device is like the WiFi
interface ... just a fast interface for data.

Agreed, this is inadequate.  It is not truly supporting IPv6, the IPv6
spec does not have dependencies on IPv4.  My assumption is that the
Thunderbolt has shim layer that makes the LTE interface look like a
normal WiFi interface to the Android OS.

All that said, hats off to VZW, Android, and HTC for making this step
forward.  This is the first IPv6 Phone + service launched in the USA.

EV-DO Rev A has no support for IPv6. UMTS (with HSPA+) does support IPv6, but most HSPA+ deployers aren't enabling it, making this moot. AFAIK, LTE mandates IPv6, which was why Verizon uses it for LTE.

IPv6 has been supported in the standards since the GPRS-era. HSPA+ is not necessary. However it's often disabled in the core equipments, which you can easily understand if devices don't support it.

Although when you test it with working handsets (Symbian), the network part just works. The main innovation in 3GPP Release 8 is the introduction of IPv4v6 type of PDP context, which is dualstack within the same data session. Unfortunately, Release 8 mandates it only for Evolved Packet Core (aka LTE). Support in GPRS/UMTS is in Release 9, and core network support for this will start beeing implemented next year.

Meanwhile there are still IPv6-only data sessions available, à la T-Mobile USA (good job there !).

Can somebody from Google (Steinar ? Lorenzo ?) update the ticket regarding the implementation schedule for v6 on the cellular interface ?

My understanding is that the real work to be done is by the people who write
the radio interface layers, which I think is mostly the same set of folks
who make the devices/chipsets.  Android can work to incorporate such code,
and thereafter test with it.  But I don't think Google Android really writes
this RIL code.

But I may be completely wrong.

Some stuff in the code :

* This one seems to be Google responsibility
http://android.git.kernel.org/?p=platform/hardware/ril.git;a=blob;f=reference-ril/reference-ril.c;h=633ad8b270f391cb4d289cea6befe2886ac93eb3;hb=HEAD#l1038

1038         asprintf(&cmd, "AT+CGDCONT=1,\"IP\",\"%s\",,0,0", apn);


* This one is probably not Google responsibility :
http://android.git.kernel.org/?p=platform/vendor/st-ericsson/u300.git;a=blob;f=u300-ril-pdp.c;h=a045490ea504cc1d523800929eadc97b4b658e4e;hb=HEAD#l419

 419     asprintf(&cmd, "AT+CGDCONT=1,\"ip\",\"%s\",\"\",0,0", (APN ? APN : ""));


In both cases, "IP" as a PDP type is statically defined, that's IPv4-only.

I've seen some reports that Android 2.3.4 for the Google Nexus now has settings that indicate support for IPv6 on the radio interface:

http://twitter.com/#!/jpedrot/status/64292326880710656
http://forum.xda-developers.com/showthread.php?p=13423625

I don't have a Nexus. Can anyone confirm if these settings are indeed there, and more importantly, if they actually work?

Tore

I can confirm, this option exists on GRJ22 (2.3.4) on Nexus One for APN settings. But I can't check it's functionality. Cause my provider (Vodafone DE) only supports IPv4.

Tried the Nexus One using T-Mobile USA's v6 test APN. Only seems to do IPv4 :(

While this is an important step forward, Google needs to release updated
radio firmware to attach to the ipv6 3g network.

Based on android 2.1 or above, We have tried to make some changes to rebuild linux kernel and pppd, then modified pppd-ril.options under /system/etc/ppp/peers/.
We get ipv6 working over 3G(CDMA/EVDO) network in our lab. we also ported these code on android phones, such as XT800, ME811, etc. it's OK.It's so interesting...

I checked on HTC Desire with Oxygen 2.1.1 (Android 2.3.4).
Graphical interface (settings-wireless&networks-Mobile Networks-Access Point Names-My Connection-APN protocol) supports three vaiants:
-IPv4
-IPv6
-IPv4/IPv6

But the result in the network is the same for all of them:
 PDP NUM    : 21h = IPv4 address


It seems to be support for IPv6 in graphical virtual life but not in real life. :(

we also made another changes to let android support dhcpv6 client over 3G(CDMA/EVDO)network, porting it to me811, xt800, android lab box, etc.
SW: android 2.1 or above
HW: QSC6085
Note: QSC6085 itself does not support ipv6/dhcpv6. pdsn sets up dhcpv6 server.

the attached pic is showing dancing turtle on ME811(andorid 2.2).

^_^

Jason
2011-5-4

support

3G(CDMA/EVDO)network, porting it to me811, xt800, android lab box, etc.

server.

Nice. But would be even better if it worked on an ipv6 umts network like
T-Mobile USA :)

For most handsets, radio firmware / RIL is required to use these new
features.

Cb

Cb, do you have any breakdown of which handsets / chipsets have ipv6-capable radio firmware, and which don't?

i can at least confirm that the official 2.3.4 for the nexus one has no new radio firmware (the latest, "5.08.00.04", was shipped with 2.2). i understand this version doesn't support ipv6. odd, since there are gui options for ipv6 apns now.

No, i have no list.  I have asked all the OEMs to support it, they
claimed they needed to wait for these features to appear in android,
so now the finger points to the OEMs.  They have the Android code,
they need to produce the RIL / firmware.... Just like home CPE, they
will likely make you buy a new device to get the new features.

I really hope that Google will bring this IPv6 feature to the Nexus
and Nexus S since these devices are controlled by Google.  Google
controls the hardware and software specification of these phones.  The
Nexus line of phone is for developers, and developers need these
features so that they can ... develop the next generation of Internet.

Cameron

ah, so the ipv6 apn gui features are a political move, so the ball rolls back to the handset makers ;)

i thought the nexus one / s were controlled and developed by htc / samsung. i thought at least that htc (or qualcomm) / samsung would be the ones writing the radio firmwares. are you saying this is actually something google does?

Much of the IPv6 feature evolution is playing whack-a-mole with who to
blame in the complex supply and development chain of the Internet
ecosystem.  If everyone points to the chicken and egg problem.  From a
content side, Google has already broken a substantial part of that log
jam.

Yes, the OEMs write the firmware.

Sorry, for the confusion.  Google owns the business relationship with
the OEMs for the Nexus devices and therefore Google has control over
what the device features and specifications are, this includes IPv6.

Cameron

FWIW, I have access to German SIM cards that will book into the internal IPv6-only test network of a major German UMTS provider. If anyone has hardware they can spare for a week and want tested, this can be arranged. Now, or in the future.

Or you can join the T-Mobile USA open IPv6 Beta

http://forums.t-mobile.com/t5/Nokia/T-Mobile-IPv6-Friendly-User-Trial/m-p/465928/highlight/true#M6881

we did not change RIL and radio firmware, just change sw running on application processor and change modem working mode. I think that this method is now for CDMA/EVDO, not sure if it is for UMTS. Maybe not suitable. We only setup CDMA ipv6 netork environment in our lab. Some OEMs seems to be interested in this method.

kudos@jason

IPv6-capable chipsets should be available soon, support in Android would make testing a lot easier...

Daniel,

Android has had IPv6 GSM data support since version 2.3.4 - so the only thing missing is IPv6-capable chipsets (or more precisely, chipset firmware/RIL). It is rather disappointing that Google, being a IPv6 leader in most other areas, has not been able to release IPv6-capable RIL updates for its Google Nexus phones.

When it comes to WiFi, however, the situation is the other way around; there are no issues with hardware/chipset support here, but the Android OS itself is unable to connect to WiFi networks using IPv6, UNLESS the network in question is also using IPv4 (i.e. dual-stack). IPv6 is a replacement for IPv4, not an extension, so the status quo of having IPv6 depend on IPv4 is missing the entire point.

BTW: Apple iPhone/iPad has no issues with such IPv6-only WiFi networks, so the Android team has some catching up to do...

Tore

Sorry, I missed that. This bug report is a bit too general, I will stop bugging Google and go bug my chipset vendors instead :-)

Any idea on how much of this is going to be addressed in the upcoming Ice Cream Sandwich release? Or will we be left in the dark until the source is released?

I personally want the v6 on wifi issues addressed first (mostly because I have the networks available to test it), but I know there are others needing/wanting the mobile interface issues sorted out first. Does it make sense to split this bug out thusly?

To re-summarize, fixes needed on WiFi:
- Interface should be allowed to come up if v6 only
- Need DHCPv6 client for enterprise networks [http://tools.ietf.org/html/rfc3315]
- RDNSS/DNSSL is a would-be-nice for smaller networks, though most other major OSes (Windows, Mac OS X) do not. [http://tools.ietf.org/html/rfc6106]

This phone from LG is expected to support IPv6 on GSM/UMTS.  Since it has not been launched yet and validated to work out of the box, i cannot promise that it will work, but it should work well with a few caveats.

The phone will ship with a default IPv4 APN, and the user can add an IPv6 APN.  My testing shows that about 10% of network applications (apps) will not work on IPv6, most are peer to peer in nature like Skype or reference hardcoded IPv4 addresses.  

 http://mytouch.t-mobile.com/simple-phones

So what's missing now is 1) proper IPv6 support on WiFi, and 2) more devices that support IPv6 mobile data. Anything else?

With some luck, ICS fixes #1.

With regards to #2, I wonder if there's any hope of getting IPv6 support as a requirement into the Android 4.0 CDD? That ought to ensure that the market gets flooded with IPv6-capable devices quite quickly at least..

Tore

Cameron: good news. Now the question is what exactly is supported? PDPv4, PDPv6. PDPv4v6 ? Can it do PDPv4 and PDPv6 at the same time?

I have devices (not android) that supports PDPv4v6, but currently no mobile operator around with GGSN and SGSN that supports that PDP type.

If LG can do two PDP's that's a win for now, but need to look forward for PDPv4v6.

PDPv6. PDPv4v6 ? Can it do PDPv4 and PDPv6 at the same time?

mobile operator around with GGSN and SGSN that supports that PDP type.

PDPv4v6.

Pdpv4 or pdpv6, not both and not v4v6.

Pdpv6 seems to work well paired with dns64 and nat64

Cb

https://sites.google.com/site/tmoipv6/lg-mytouch

Stock ics android 4.0 on nexus s now supports ipv6 on 3g.

Indeed. But on Android 4 some apps are not working on IPv6-only with NAT64... like Market, Skype (doh...), A-GPS and some other features... need to do a list of all of affected apps. You already started something like this?

NAT64... like Market, Skype (doh...), A-GPS and some other features... need
to do a list of all of affected apps. You already started something like
this?

I have an old list, but let's work together off-list for an update that we
can publish.

Market works fine for me, with nat64/dns64 and white list. I just
downloaded Pandora and angry birds from Android market . Both work fine
v6only (including ads).

Cb

Is there a separate bug report that using the phone as a WiFi access point doesn't work with IPv6?

Ice Cream Sandwich does unfortunately not bring any improvements, at least not in version 4.0.2.

When it attempts to connect to an IPv6 wireless LAN, it will auto-configure an IPv6 address (using SLAAC) and start responding to ICMPv6 echo-requests, however it will after a few seconds bring down the entire interface (when the DHCPv4 request times out). I can not see that it attemps to do information-only DHCPv6 in order to learn the DNS servers, either.

Tore

Yes, ICS didn't bring DHCPv6 support or RFC 6106 support for SLAAC.

This has to be done before 8th of June : http://www.worldipv6day.org/

It is actually June 6th this year.  WorldV6Day was last year.
http://www.worldipv6launch.org/

There appears to be a bug that occurs when the router lifetime expires when the device is sleeping. I often find that my Galaxy Nexus is unable to access anything over IPv6 after being picked up in the morning, after having been left connected to WiFi the night before. The problem is that the IPv6 default route has vanished. Unsolicited RAs on the network does not appear to re-instate it; the only way I've found to get back online is to disconnect and reconnect to the WiFi.

Tore

Regarding comment 97, this is now in violation of RFC behavior.

From RFC 6540, section 2:
   o  New and updated IP networking implementations should support IPv4
      and IPv6 coexistence (dual-stack), but must not require IPv4 for
      proper and complete function.

There appears to be a bug with IPV6 and IPV4V6 PDP types in Android or the Samsung Galaxy Nexus specifically. When roaming, the phone appears to always request IP (i.e. IPv4) PDP context type. This is observed by tracing on the home network's GGSN as the PDP context is being set up. When in the home network, IPv6 PDP type establishes without any problems. Also going from the home network to a roaming network without dropping the PDP context works, but establishing new non-IP PDP contexts when roaming does not.

I have tested this when roaming in Slovenian, Austrian, and Norwegian mobile networks. It's worth noting that the three Slovenian networks I tried support IPV6 PDP type for their own subscribers. Also, establishing IPV6 PDP contexts from a Nokia 21M-02 3G modem stick in the same networks (using the same SIM card) does work perfectly. I therefore find it highly unlikely that the networks I am roaming in is doing PDP type clamping on their SGSNs or something similar; it looks overwhelmingly likely that the bug is in Android or the Galaxy Nexus' RIL.

This is particularly problematic for me. My home network Network Norway only has coverage in and around the major metro areas in Norway. For when their subscribers are outside NwN coverage, they have a national no-extra-cost roaming deal with Telenor. So whenever I am outside of the metro areas, IPv6 mobile broadband no longer works.

I have a completely stock Nordic edition Galaxy Nexus, purchased retail and currently running Android 4.0.2 and RIL version I9250XXKK6.

Anyone else seeing this issue?

Tore

[Comment deleted]

[Comment deleted]

I'm using HTC desire z and Android 2.2
I'm testing in an ipv6 only network with SLAAC.
and have exactly the same issue as comment 50 describes.

On more detailed exploration with tcpdump,
the node does not respond to Router Advertisement messages.
In a dual-stack network the setup works and the node responds to the RA messages with  a Neighbor solicitation msg and its global address. So the issue should be in this step right? However, I have no plan how to proceed any further...

Furthermore, when checking /proc/net/if_inet6, I can see that a link-local layer address (fe80: ..) is set up correctly, so the first part of SLAAC did work, right? (see RFC 4862) However, I'm wondering what needs to be changed to let it obtain a global ip address.

What is the current status on this issue? Have newer versions solved the problem, and if so since which version?

Thanks
Jenny

FYI, since this bug report have become a hodgepodge of various IPv6 related issues (to which no Android developers seem to take an interested), I went ahead and submitted separate and specific bug reports for the IPv6 related problems I personally experience:

Enhancement: Support for DHCPv6 (RFC 3315)
http://code.google.com/p/android/issues/detail?id=32621

Enhancement: Support for Recursive DNS Server Option in ICMPv6 Router Advertisements (RFC 6106)
http://code.google.com/p/android/issues/detail?id=32629

Enhancement: Support connecting to IPv6-only wireless networks
http://code.google.com/p/android/issues/detail?id=32630

Defect: APN Protocol ignored when roaming
http://code.google.com/p/android/issues/detail?id=32631

Enhancement: Automatic fallback from IPv4/IPv6 APN Protocol to parallel IPv4 + IPv6
http://code.google.com/p/android/issues/detail?id=32632

Defect: Frequently ignores ICMPv6 RAs and other multicast traffic
http://code.google.com/p/android/issues/detail?id=32662

Tore

GPS signal takes 15 minutes or so to lock on when utilizing T-Mobile's IPv6 mobile APN. I have heard this is due to a bug in A-GPS when using IPv6.

Hi,

Im working for Slovenian mobile operator Si.mobil and we are starting with tests of 3GPP rel9 IPv4v6. Do you maybe know if Google Nexus 4 have implemented support for PDP type v4v6? Or any other phone if this one doesn`t?

Thanks
Nejc

Hello,

I am looking for a device & SW version (preferably Android) apart from (Nokia USB stick 21M-02) which supports Dual Stack (IPv4v6) in 3G. Could you please let me know?

Regards,
Panos

[Comment deleted]

[Comment deleted]

[Comment deleted]

100% agree

Android One refuses to work ipv6 after 4 hours of Wi-Fi testing on two nokia phones
https://source.android.com/security/bulletin updates don't fix this issue

Eab presence provisioned

Pin please