3 ms·
Setting up IPv6 on my home network was fun and exciting now it's just boring. The only time I've noticed it was was once when IPv4 broke (dhcp server issue) an
by hackeraccount 3y ago
Setting up IPv6 on my home network was fun and exciting now it's just boring. The only time I've noticed it was was once when IPv4 broke (dhcp server issue) and another time when IPv6 itself broke (radvd issue).
All that said I do sort of wonder when or if we'll ever move off dual stack. I think there's a strong argument that running two protocols at once is riskier then the combined risks of the two.
- DrThunder 3y agoI can't imagine too many businesses will be switching to it internally unless forced to. ISP's and mobile carriers are one thing.
- LinuxBender 3y agoAnd even then they can just have a small number of IPv6 terminate on some load balancers and small SNAT groups. Almost everything inside the data-centers will likely remain IPv4 for quite a while.
- Volundr 3y agoAnecdote: a company I used to work for was growing rapidly by acquisition, which ended up being the motivation to go ipv6 internally. With IPv4 every new company was basically guaranteed to have an internal network that conflicted with one of our existing subnets, so we either had to re-ip them, which was brutal or put crazy NATs on our VPNs alongside dns insanity. Going IPv6 meant that getting them on our mesh was simple. Just enable IPv6 on their network (which was far easier than most network admins fear it will be), then join their IPv6 network to the mesh, let their IPv4 be whatever it was. Update all DNS servers to have AAAA records. No more conflicts!