 |
 |
|---|
Posted on 01/19/2017 9:06:21 PM PST by dayglored
No pressure, peeps: Techies are awaiting a fix from their Redmond coworkers
A bug in Windows 10 is undermining Microsoft's efforts to roll out an IPv6-only network at its Seattle headquarters.
According to Redmond's principal network engineer Marcus Keane, the software giant is struggling to move over to the decade-old networking technology due to a DHCPv6 bug in Windows 10, which made it "impossible" to expand its planned corporate network. "We have reported it to the product group, and they are duly working on a fix," he revealed today.
The horrible irony of Microsoft waiting on its own team to fix a networking bug aside, the post goes some way to highlighting why it is that IPv6 is still not widely available: because it's a mess.
First up, the existing routers at its Redmond offices didn't support RDNSS. Microsoft was using DHCPv6 to provide IPv6 addresses on its network, but Android doesn't support that.
"As we needed to support Android devices on our guest network, and Android doesn’t support DHCPv6, not having this feature was a problem," said Keane.
So the company went to the router manufacturer and asked them to add RDNSS, which Android can use. In the meantime, they shifted to a different set of routers for the IPv6-only network and used a VPN to connect to the larger network – something that Keane notes "isn't ideal."
Then they hit another Microsoft software problem: network authentication. Employees use the company's own Azure Active Directory cloud-based ID system to log in, but the dynamic system they use to achieve this is – you've guessed it – not supported over IPv6.
Again, Microsoft has gone directly to the vendor to include dynamic ACL-based authorization in its system. "We expect to complete testing of both the wireless controller code and the router code supporting RDNSS in the next month or so, meaning we should be able to roll out IPv6-only to the guest network in our Redmond campus in the next six months," Keane writes.
And once that happens, Keane predicts the real fun will begin: testing whether people's applications will work over IPv6. In the meantime, they're sticking with dual-stack.
You do have to wonder – if even Microsoft can't get IPv6-only working, what chance is there for any other company to? Can someone remind us again why the Internet Engineering Task Force decided not to make this next-gen networking protocol backward-compatible?
[...more at the article link...]
IPv4, with NAT technology, solved the problem of "not enough IP addresses" because not all devices have to have unique public IPs. The push for IPv6 -- at this point in time -- appears to me to be that somebody WANTS every IoT device to have a unique public IP because they want to be able to talk to it directly, to PUSH things to it whether it wants them or not.
My refrigerator? My coffee maker? My pacemaker implant? I DON'T THINK SO.
I'm very happy behind my NAT, thank you.
YMMV.
|
|
|---|
I have been running a dual stack IPv4 and IPv6 stack on my home network. I run IPv4 for the windows machines and IPv6 for my Linux Mint boxes. I have been set up this way for over two years now.
I constantly have problems with the windows machines. I hardly ever have a problem with the Linux boxes.
Some people really like them. Fine, they can have mine.
IPv4 works fine on my local network, and behind a NAT I don't care.
If my survivors put an IPv6 enabled IoT device on my tombstone, that's their business.
From what I’ve heard, Windows 10 is spyware.
> From what I’ve heard, Windows 10 is spyware.
It’s not all spyware, and the part that is intrusive can be controlled to a large degree. But the default settings are pretty egregious, IMO.
I have an Android phone.
On T-Mobile's network, it has an IPv6 address (and a high transfer rate). On my Verizon FiOS LAN, it has an IPv4 address (and a high transfer rate).
Other than battery drain (high on WiFi, low on LTE), I can't tell the difference. ...
Sound like Microsquish needs to get its act together.
Microsoft needs to eat it’s own sludge.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.