I'm using ipv6 and I find that Android's implementation makes it very hard to identify my android devices in my netflow data (SLAAC coupled with use of temp addresses / privacy extensions yields long, unwieldy and ever-changing addresses). On my Windows and Linux boxes, I tend to use a combination of DHCPv6 and SLAAC coupled with an explicit ip token that allows me to give my devices IPv6 addresses where the suffix corresponds to the last octet of the IPv4 address. This makes tracking and identifying my devices a little easier. For example, a device with an IPv4 of 192.168.1.76 would get an IPv6 of fd42:2181:64f5::76/48.
Needless to say, on current versions of Marshmallow and Lollipop, this is currently impossible in an out-of the-box environment as Android doesn't support DHCPv6 and neither does the cut down ip binary provide the ip token functionality. Accordingly I cloned the latest version of the iproute2 source and compiled it for Android. Now my devices can use SLAAC with an ip token, get assigned the prefix by the router and generate their own suffix according to my desired paradigm.
In the hope that someone else might find it useful, I've uploaded armeabi-v7a and aarch64 binaries for both sdk22 and sdk23. Just use the appropriate binary to replace your existing one.
Download: iproute2
Needless to say, on current versions of Marshmallow and Lollipop, this is currently impossible in an out-of the-box environment as Android doesn't support DHCPv6 and neither does the cut down ip binary provide the ip token functionality. Accordingly I cloned the latest version of the iproute2 source and compiled it for Android. Now my devices can use SLAAC with an ip token, get assigned the prefix by the router and generate their own suffix according to my desired paradigm.
In the hope that someone else might find it useful, I've uploaded armeabi-v7a and aarch64 binaries for both sdk22 and sdk23. Just use the appropriate binary to replace your existing one.
Download: iproute2
