Among the numerous incompatibilities and troubles we are seeing with the rollout of IPv6 is a new hitch. It seems Microsoft just opened up a ticket with themselves over a problem they are having with their Azure Active Directory cloud-based ID system; it would seem it is incompatible with IPv6. The Register specifies Windows 10 for this issue however it is very likely that previous versions are also going to encounter issues. You can read more about the troubles and attempted solutions here.
"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."
Here is some more Tech News from around the web:
- Windows 10: Microsoft is spamming Chrome users with pop-up adverts @ The Inquirer
- Print Flexible PCBs with a 3D Printer @ Hack a Day
- 3D TV Is Dead @ Slashdot
- Asustek to launch next generation ZenFone 4 smartphones in May, say sources @ DigiTimes
There are two major ISPs in
There are two major ISPs in my city…..one of them still can’t handle ip6
Isn’t the real endeavor of
Isn’t the real endeavor of IPV6 to track individual devices no matter where they reside?
/tinhat
For real though, is there any performance benefit to it?
I would say that there is a
I would say that there is a slight performance decrease because of the larger IP header. Maybe some performance increase in neighbor discovery processing. Why doesn’t MS use autodiscovery? ISC DHCPD works great for IPv6…..
ipv6 is basically just there
ipv6 is basically just there to increase the number of available addresses. There is a shortage of the old v4 ones now.
not really. china went ipv6
not really. china went ipv6 and freed up milions of ipv4 adresses.
Yeah perhaps….but if new
Yeah perhaps….but if new addresses are just freed up like that without redoing the entire system the routing tables are just going to get larger and slower over time. Referring to a previous poster that could be a way that 6 is(will be) effectively faster than 4.
I feel ipv6 will still take
I feel ipv6 will still take quite some time to get working all over just because the adoption rate is painfully slow.
Apps on Android have so many issues working with ipv6, things don’t load or even connect.
Lower end routers can’t handle ipv6, most of the open source router software can’t yet handle it. I believe openwrt and pfsense can but gargoyle, tomato and ddwrt I believe still have issues.
From my experience ipv6 has one major strength which is not having to have port forwarding in the same way ipv4 needs, which is great for stuff like Xbox and PlayStation because having multiple things trying to grab the same port behind an ipv4 Nat is a nightmare.
Correct me if I’m wrong with any of my information, it’s just what I have experienced. So I’d say ipv6 is only good for consumers, anything advanced or business is a mess for ipv6. If you don’t believe me, try using any ftp or game software over a strictly ipv6 connection.
You’re right about the lack
You’re right about the lack of port forwarding being a major benefit. Right now, with NAT, the router has to do stateful packet inspection for all traffic. That means it has to examine the contents of the packet to determine what to do with it and keep a table of port associations. That’s a lot of processing overhead that’s just gone.
It is SOP at work to disable
It is SOP at work to disable IPv6 on all machines. We don’t support nor implement it on anything. At home, only my cable modem uses IPv6 due to Comcast forcing the change. I can call to get an IPv4 address but haven’t bothered. Until it becomes a job requirement I’m not going to bother learning how to implement it.