2 ms·
In the back of my mind I have a "Days since I solved networking issues by disabling ipv6" calculator. Currently it's at one month, give or take. The host in que
by nikanj 5y ago
In the back of my mind I have a "Days since I solved networking issues by disabling ipv6" calculator. Currently it's at one month, give or take. The host in question was not serving proper ssl certs on ipv6 ports, so connections failed with really scary errors.
I know ipv6 solves a lot of issues for actual networking people, but for the grunts who just want mom's printer to start working, disabling ipv6 still seems to be a silver bullet.
I'm very aware that the latest issue I solved was entirely the fault of the server operator, not of ipv6, but the user experience still was "ipv6 broken, no ipv6, no broken"
- malinens 5y agoOn the other hand I had performance issues when disabling ipv6 on gentoo based system for running docker (containers where starting in 1.5-2 seconds instead of 0.4 seconds). Enabling ipv6 solved those issues.
- belorn 5y agoInteresting that you mention certificates because my counter of Days since I could have solved website issue by disabling https is also about a month or so. Those certificate warnings are really scary for users, but telling them what the certificate error means and how to fix it made for an happy client. Of course they could have solved it by disabling https but then the browser would display this ugly icon and google would not rank their website as good as before, so there is a strong incentive to keep https. The server admins responsible for the site will just have to accept that certificate renewal is part of their responsibility.