Stories
Slash Boxes
Comments

SoylentNews is people

Android's Lack of DHCPv6 Support Frustrates Enterprise Network Admins

posted by martyb on Wednesday November 07 2018, @03:12AM   Printer-friendly
from the BAD-design-(Broken-As-Designed) dept.

jas writes:

In June 2012, an owner of a Samsung Galaxy Nexus running Android 4.0.2 opened a case in Google's Issue Tracker requesting support for Dynamic Host Configuration Protocol for IPv6, otherwise known as DHCPv6, or RFC 3315, which allows for stateful address and connection configuration on devices joining an IPv6 network. DHCPv6, like DHCPv4, is commonly used in enterprise networks for connecting devices.

For the last six years — including through five new major versions of Android — that request has languished, when this week it was marked as "Won't Fix (Intended Behavior)" by Google engineer Lorenzo Colitti. Android is effectively the only platform which lacks support for DHCPv6, making the IPv6 implementation on Android incomplete.

https://www.techrepublic.com/article/androids-lack-of-dhcpv6-support-frustrates-enterprise-network-admins/

Original Submission

 
This discussion has been archived. No new comments can be posted.
Android's Lack of DHCPv6 Support Frustrates Enterprise Network Admins | Log In/Create an Account | Top | 17 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by Rosco P. Coltrane on Wednesday November 07 2018, @05:58AM (2 children)

    by Rosco P. Coltrane (4757) on Wednesday November 07 2018, @05:58AM (#758850)

    It makes them much easier to track.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 5, Insightful) by coolgopher on Wednesday November 07 2018, @07:18AM

    by coolgopher (1157) on Wednesday November 07 2018, @07:18AM (#758865)

    Then they'd be better off on IPv6, where you don't end up with infernal aliasing of internal addresses all the !&#^ time due to NAT.

  • (Score: 5, Interesting) by Anonymous Coward on Wednesday November 07 2018, @07:28AM

    by Anonymous Coward on Wednesday November 07 2018, @07:28AM (#758868)

    My understanding of it is that Google knew how ephemeral IP numbers would be as Android mobile devices transit across multiple networks, during the course of a day/week/month they knew they'll change them multiple times and that they'd probably be NAT'ed (and my mobiles always seem to get IPv4 addresses in the 10.x.x.x range from the phone company, so we're looking at CGNAT there).

    So, to track you, they use the play store and associated software garbage to track your (ab)usage by your google account, no google account? no problem...it's amazing how 'chatty' the average Android phone is out of the box (especially some of the Chinese ones)....why, hello there Mr IMSI, what are *you* doing lurking there in that datastream? (fuck knows what else is lurking in the encrypted ones...)

    Put a firewall on your phone, set it to block all traffic by default, watch what happens in the logs....(though to be more thorough here, you also need to monitor the phones connection via an external device to catch 'OOB' stuff, rule 1: never trust *any* software running on *any* phone)

    Fixed IP?, they don't need *no* steenkin' IP numbers (v4 or v6, fixed or otherwise) to track you, they're well beyond that.

    I'll just rearrange my tinfoil hat...