Android ICS and IPv6 over WiFi

While I’m not on a carrier that hands out IPv6 over the radio (4g/LTE/etc), at least the WiFi support for IPv6 remains working 🙂

7 thoughts on “Android ICS and IPv6 over WiFi

  1. yes, ipv6 work in Android. I have do ipv6 in wifi and router. but Android system still not very good support ipv6. we have talk about this in pfsense forum. 🙂

  2. I can get an autoconf IPv6 address over wifi also with ICS on the Galaxy S3, but can’t seem to connect anything via v6. Can’t yet tell what this issue is.

      • Yes, I can ping its global and link local addresses on the same subnet.

        Subnet is dual stack and has a router with RA and DHCPv6 enabled for global /64 autoconf and IPv6 DNS server, all other hosts are fine.

        Android phone is getting a global on the same /64, and also appears to be able to do AAAA lookups. Trying to verify if it is installing/using the IPv6 default route learned by the RA, as it cannot seem to reach anything beyond the /64 it is in.

  3. Confirmed with a tcpdump, the DNS queries going out are only for A records, never AAAA. This is both from a web browser and from a ping6 on the command line.

    Also ICS does not appear to be using the default route learned from the RA. It sees the RA and configured a global address, but does not have a route for anything outside of its configured /64.

    For hosts on the same /64 I see normal neighbor solicitations and ICMPv6 echo requests and replies.

    • 1|root@android:/ # ping6 fe80::223:6cff:fe7f:b18d%wlan0
      PING fe80::223:6cff:fe7f:b18d%wlan0 (fe80::223:6cff:fe7f:b18d): 56 data bytes
      64 bytes from fe80::223:6cff:fe7f:b18d: seq=0 ttl=64 time=294.399 ms
      64 bytes from fe80::223:6cff:fe7f:b18d: seq=1 ttl=64 time=223.897 ms
      64 bytes from fe80::223:6cff:fe7f:b18d: seq=2 ttl=64 time=145.155 ms
      64 bytes from fe80::223:6cff:fe7f:b18d: seq=3 ttl=64 time=49.046 ms
      — fe80::223:6cff:fe7f:b18d%wlan0 ping statistics —
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 49.046/178.124/294.399 ms

      root@android:/ # ping6 2607:f8b0:400b:801::1013
      PING 2607:f8b0:400b:801::1013 (2607:f8b0:400b:801::1013): 56 data bytes
      ping6: sendto: Network is unreachable

  4. I have the same problem.

    /data/data/berserker.android.apps.sshdroidpro/home # ping 2001:470:b:6ab:f0a4:a6
    a0:557f:d99
    PING 2001:470:b:6ab:f0a4:a6a0:557f:d99 (2001:470:b:6ab:f0a4:a6a0:557f:d99): 56 data bytes
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=0 ttl=64 time=93.872 ms
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=1 ttl=64 time=17.944 ms
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=2 ttl=64 time=17.120 ms
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=3 ttl=64 time=16.663 ms
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=4 ttl=64 time=15.533 ms
    64 bytes from 2001:470:b:6ab:f0a4:a6a0:557f:d99: seq=5 ttl=64 time=14.863 ms
    ^C
    — 2001:470:b:6ab:f0a4:a6a0:557f:d99 ping statistics —
    6 packets transmitted, 6 packets received, 0% packet loss
    round-trip min/avg/max = 14.863/29.332/93.872 ms
    /data/data/berserker.android.apps.sshdroidpro/home # ping http://www.google.com -6
    PING http://www.google.com (2404:6800:8005::68): 56 data bytes
    ping: sendto: Network is unreachable

    2001:470:b:6ab:f0a4:a6a0:557f:d99 is my laptop.

Leave a Reply