175 karma · joined September 17, 2020
IT Pro & Casual Geek
Youtube has a livestream from NASA: https://www.youtube.com/watch?v=21X5lGlDOfg
https://reactos.org/ implements Windows roughly akin to 2003; dunno if that would be able to re-create this issue, but might be worth trying?
There was a patent lawsuit in the 90s about drive compression software in DOS 6.2. It was yanked in .21, and re-added in .22 with some changes.
I'm glad we agree on NAT sucking. Though given a lot of ISPs are doing DHCPv6 without fixed net-ranges to clients; a work environment does benefit from having ULAs still; sometimes even with NAT66. Performance & security-wise, IPv6 still wins that battle: most routers disable automatic inbound traffic, and you can pinhole traffic directly between hosts.
IPv6 has saved my bacon more times in the past 15 years, than IPv4 has fought with me. No clashing of IPv4 ranges. No fighting with NAT. Ability to easily have concurrent networks, for different purposes. Ability to assign multiple network addresses. Internally, it "just works" on basically anything not an older licensing server, or LAN game. Microsoft is using it internally. Apple has been mandating MacOS and iOS apps to support it for several years now. Usage over the Internet is exceeding 50% in major countries.
Where it falls short... a lot of ISPs use equipment that don't handle it well, and/or don't have the staff to implement it properly; and the ISP buyouts and mergers here in the US of the past 15-20 years REALLY messed up the timeline on adoption. Cloud services, a lot of the stuff Google & Microsoft built up their public offerings on, they were designed largely on older virtualization setups that precluded how IPv6 works, until recently; same goes for Docker & Kubernetes. A lot of VPS hosts support it just fine; but a lot of businesses aren't leveraging those, as they could be. And lastly... a lot of IT guys still don't care for IPv6; as those biases show up in these & on Reddit; so that perpetuates the cycle.