3 ms·
This is a very old article, but just like even many modern articles, it makes the flawed argument that you can only ever have one network stack: IPv4 or IPv6.
by jeroenhd 5y ago
This is a very old article, but just like even many modern articles, it makes the flawed argument that you can only ever have one network stack: IPv4 or IPv6.
The truth is, dual-stack networking exists and is used all the time. My router is configured to use DHCPv4 and SLAAC and it Just Works, no strange protocol configuration or DHCP flags required. There is no choosing between what sites are on what networks, you always get both. Only IPv6-only networks pose a problem, and that's only a problem for people stuck on IPv4.
You'll have to manually disable IPv4 in your network config to miss out on anything when you enable IPv6. You'll have to do so at every separate client, because some ISPs even run their own complex 6to4 system, transparently encapsulating IPv4 traffic in IPv6 packets in their routers on the consumer side, and then turning those back into IPv4 at their network's edge. The "IPv4" that you get with those ISPs isn't even real IPv4!
Sure, you can't have any incoming connections over IPv4 in dual-stack lite configurations, but normal people don't need incoming connections. If they can reach Facebook, Tiktok and Google then they're all A-OK.
Only the minority with technical requirements for receiving connections need the full dual stack experience anyway. Businesses hosting their own stuff and technies should be able to request a public IP, at a small cost if ISPs are as greedy as ever, but that's it. The rest of the world can live with shitty CG-NAT for websites that haven't made the switch yet, because shitty NAT implementations are the de facto standard when dealing with IPv4.
My prediction for the (far away) future is that directly accessible IPv4 becomes a thing for businesses, cloud hosts and servers, where you're basically paying extra for real network connectivity if you really do need to receive connections from the legacy net. The worldwide transition is slow, but I'm certain that other countries will pick up the pace once big cloud companies start changing their IPv6 assumptions as American ISPs start to transition their last residential customers to cut costs. When your network has trouble reaching Google, no matter if it's your fault or Google's, your customers will blame you.
- midasuni 5y agoDual stack means twice as much to maintain and twice as much to go wrong.
- eqvinox 5y agoIt also means twice as much can go right. I've been able to rescue a broken IPv4 config via IPv6 access several times, and vice versa.
- magicalhippo 5y ago> twice as much to go wrong Actually it's more than that, given that extra services like DNS are pretty much required these days and that DHCP has been replaced with two things, RA and DHCPv6, instead of just one. As a concrete example, I run split-horizon DNS for an internal service I want Let's Encrypt certificates for. This was trivial to set up and worked great from my desktop computer, but for some reason my service didn't work with my phone. Turns out Android refuses to use provided IPv4 DNS addresses if it got allocated an IPv6 address, and reverts to Google's own DNS servers.
- jeroenhd 5y ago> Turns out Android refuses to use provided IPv4 DNS addresses if it got allocated an IPv6 address, and reverts to Google's own DNS servers. That's strange, I haven't seen this happen to my devices at all, and my pihole is IPv4 only for now. From what I can find online, it seems that this happens when Android is configured with an IPv6 address but the provided DNS server won't resolve AAAA queries. Allowing your DNS server to look up AAAA addresses would probably fix your problem?
- magicalhippo 5y ago> Allowing your DNS server to look up AAAA addresses would probably fix your problem? I'm running Pi-Hole as well, and I don't have an issue with AAAA records as far as I can determine. I found several forum posts suggesting I make my router hand out the IPv6 address to my DNS server (also Pi-Hole) and after I did that it started working right away.
- midasuni 5y agoI think the problem is you have www.somesite.com which resolves publicly to an A and AAAA record, and you override its A record with a local DNS entry, but not its AAAA entry? Sounds like an Android bug if you NXdomain the AAAA entry and it still insists on using it (or it overrides your DNS server and goes to a google one)
- wayoutthere 5y agoThe big residential ISPs were some of the first to go IPv6. Consider the issue of how to issue management IP addresses to 30 million cable modems, plus an unknown number of “other” managed devices like set top boxes: the 10. space only has 16 million addresses, so you have to have multiple parallel networks. Managing that is a lot of overhead. The conversion to IPv6 was considered cheaper than the alternative, so the big ones mostly did it 10-15 years ago.