Slashdot Mirror
IT Pros Blast Google Over Android's Refusal To Play Nice With IPv6
alphadogg writes: The widespread popularity of Android devices and the general move to IPv6 has put some businesses in a tough position, thanks to Android's lack of support for a central component in the newer standard. DHCPv6 is an outgrowth of the DHCP protocol used in the older IPv4 standard – it's an acronym for 'dynamic host configuration protocol,' and is a key building block of network management. Nevertheless, Google's wildly popular Android devices – which accounted for 78% of all smartphones shipped worldwide in the first quarter of this year – don't support DHCPv6 for address assignment.
Obviously at this point it isn't a bug, its a "feature." The only question is why did Google decide to push this negative feature?
much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
DHCP in IPv6 isn't really needed because devices can derive their own addresses and the network will automatically handle collisions.
IPv6 is great for the Internet, but your local network doesn't need it.
Google's IPv6 support for mail is what annoys me. I have a static non-tunneled IPv6 address for my server, have reverse DNS set up for it that resolves properly, have SPF and DKIM records set up properly, and they still refuse to accept mail from the server, even though they accept my IPv4 mail just fine. Lots of other folks have been having the same problem, and it really makes me wonder why Google's even bothering with IPv6 SMTP when they're refusing mail from so many legitimate (i.e. non-spam) hosts.
Isn't half the point of IPv6 that we can just give EVERYTHING a static IP? Who needs dynamic assignment?
I use router advertisement on my home network. All the other devices, except Android-powered devices play nicely with router advertisements. The Android devices lose the IPv6 address when they go to sleep, and do not re-obtain the IPv6 address when they wake up. The Android devices are the only devices with this problem on my home network.
All this talk of v4 address space about to expire for the last 2 years... Are they holding back an ipv6 flavor for some reason?
Shipped doesn't mean sold. And of course it's wildly popular, the bottom-of-the-barrel, can-barely-run-the-OS, weak low-end devices are either free with a contract or under $100.
That doesn't mean it's superior in any way.
RDNSS is the way, fuck this ipv4 relic.
> it's an acronym for 'dynamic host configuration protocol,' and is a key building block of network management.
The above explanation is a clear proof that Slashdot is not a "news for nerds" site anymore.
-Yenya
--
While Linux is larger than Emacs, at least Linux has the excuse that it has to be. --Linus
The black box behind the number of posts hides the title.
DHCPv6 is a bad bolt-on, IPV6 always had superior solutions designed since the 90s (when it had another name)
Because it uses IPv6 stateless auto-config like it's supposed to.
Mod parent up!
--- Often in error; never in doubt!
I work for a (smallish) ISP so let me tell you why you will simply not get any IPv6 service without DHCPv6 on our network.
It has nothing at all to do with being IPv4 old-timers. That is just you not understanding the complexity of the world out there. Our network was build from the start with the idea that IPv6 is the future.
We use DHCPv6 to provide every user with his own /48 prefix. Yes you said that DHCPv6 is a great solution for prefixes. But we also use it to deliver a /128 to go with that prefix. We need this to have a stable and predictable address that we can use as next hob for your shiny new prefix.
We had this very same debate on the NANOG mailing list. Some people there asked why does your routers not sniff the DHCPv6 packet and add the route dynamically? Two reasons. One, that is not in any standard, so our vendor did not implement it. Two, it does not work if you have router redundancy (how would the backup router know the route?).
There are more reasons an ISP would not want to use SLAAC. It exposes 2**64 addresses to the ISP network access routers. This can harm the network in many different ways and you simply do not want your ND caches to be full of that crap. You want to use as few slots in the shared ND cache per user. Therefore you are going to disable SLAAC on the customer edge and use some other mechanism. One guy suggested not using GUA on the customer links and only use link local addressing here. We choose to use /128 DHCPv6 assigned addresses. In either case, GUA-SLAAC is a fail in the provider network.
SLAAC is great inside the household of our customers. But we leave that decision to the customer and his choice of CPE-router.
The problem with Android is that it should really be able to act like a CPE for tethering purposes. Therefore is should be able to accept our CPE configuration. Android should also be able to ask for a prefix to be sub-delegated from the house CPE and it should accept that this might come with extra addresses that will be used for routing or for other purposes.
It's an abbreviation.
An acronym is a special case of an abbreviation, that is pronounced like a word. A classic example is ASCII. Most people don't say each letter, they say ASCII as a two-syllable word.
I would suspect that stateless Auto configuration works on the phones. As long as it was passed along by the routers it would work just fine.
However that being said ARIN is at 0.07% left of IPv4 space as of a few days ago and likely less after this week. Estimates in July the ARIN free pool will be empty and you'll be leasing IPv4 ip's for a lot more and not own your IP's for quite awhile so it is in everyone's interests to push adoption of IPv6. Google's decision to make sure the phones are compatible as much as possible shoots this into the foot.
However Verizon and AT&T and others are not getting more IPv4 ip's so they'll make sure IPv6 works on the phones.
14.04 LTS has dhcpv6 so broken up t might as well not even be there.... Which is pretty sad.
Im trying to recall the feature. Something about discovering routers for network address and using the mac address as the unique component.
I recall that dhcp is irrelevant for ipv6
I went out the other day and bought a new router for home after my WRT54G that had been doing the job for years started to show its age.
I decided to buy a PROPER router, with multiple gigabit, multi-connection failover, IPv6, VLAN, VoIP, VPN, LDAP, QoS, wireless access point management, all the trimmings.
The IPv6 config has a myriad of options. I got bored looking into all of them. 6rd, 6in4, DHCPv6, TSPC, AICCU, RADVD, god knows what.
Fact was, I got bored of trying to figure out which/how to use. Some required sign-ups and were basically IPv6 VPN's with all kinds of monitoring and restrictions, most needed ISP support to provide details, IP ranges, or some catch-all IP, and none were offering anything different to my eyes. In the end, it was all moot - my ISP offered no support for IPv6 at all (probably because of several competing and basically identical-to-the-end-user standards), and the other stuff requires me to sign up with a third party that will then take all my IP traffic and subject it to god-knows-what-jurisdiction.
The problem with IPv6 is not that it doesn't work. It's that it's not plug-and-play for whatever setup you have (transit over IPv4 or IPv6 native, for example).
If I get bored working out what to choose, I'm sure everyone else will not bother to support them until we choose just one either.
Some operator-based prefix, plus the phone's IMEI or the SIM card's IMSI. Or perhaps just the phone number in the international format. There. Unique and permanent addresses for everyone.
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
now we need to go OSS in diesel cars
http://developer.samsung.com/forum/board/thread/view.do?boardName=General&messageId=239890
"I just reply to you when I see you spamming Slashdot with your nonsense"- by dave420 (699308) on Friday June 19, 2015 @10:31AM (#49945047)
Why'd you agree w/ my points on hosts then? Quoting you here:
"I'm not denying all those things" - by dave420 (699308) on Wednesday September 17, 2014 @11:39AM (#47927435) FROM -> http://yro.slashdot.org/commen...
Of course you're not: It's impossible to dispute FACT on HOSTS FILES superiority to other methods!
Since my points of fact in favor of hosts SINGLE FILE native kernelmode faster part show hosts doing more, with less, vs. so-called 'competitors' many part messagepassing + other overheads laden slower usermode FAR MORE COMPLEX 'solutions' doing less than hosts do for more security, speed, reliability, + anonymity online!
I make creating a superior more efficient solution EASIER!
(Which is more than a mere trolling stalking harassing "ne'er-do-well" like yourself could *EVER* manage).
---
"I'm simply pointing out that it takes an AdBlocker to block your spamming"- by dave420 (699308) on Friday June 19, 2015 @10:31AM (#49945047)
Then WHY DON'T YOU DO THAT & use 'em? Answer that!
(You stalk/harass me instead!)
I bother you? Use them!
OBVIOUSLY, you don't & you're just a "ne'er-do-well" troll, OR you have "other motivations" (see next):
* DO YOU WORK FOR AN ADVERTISING FIRM, or ARE YOU A WEBMASTER/WEBCODER, or ARE YOU A MALWARE MAKER, or ARE YOU AFFILIATED WITH 1 OF MY COMPETITORS?
Answer that! No, instead as per your usual, you'll avoid every question, or lie!
(You must be involved with 1 of those above, especially since you can't EVER "get the best of me" & you know it, witness the above - & their "so-called 'solutions' are INFERIOR TO MINE on TONS of levels, OR YOU'D USE THEM, merely evidencing their stupidity in & of itself via inferior designwork!)
APK
P.S.=> SEE Dave420 SQUIRM - evasions galore from him will ensue, guaranteed... apk
They managed to screw up DHCPv4 as well: https://code.google.com/p/android/issues/detail?id=6111
Somehow, for every OS on the planet you can give it a meaningful hostname either manually or via DHCP, except for android where that can be achieved only via rooting and adb-shell. Ever wondered why your networked devices are called android-deadbeefdec0dedfadedcaca? It's because they still haven't fixed this bug in 5 major releases. It's not that iOS has this, even Windows NT has this. Yes, on most android devices you can't set the bloody hostname and ironically they call it a networked OS.
10x more important than IPv6. My router can handle that. My phone company can handle that. My device itself, doesn't need to handle that.
Who really has non-NAT access on their phone.
Article. Is. Dumb.