3 ms·
I once ticked "IPv6" when ordering a Debian VPS. It was super-slow and I didn't know IPv6 was the cause. Basically the system always tries IPv6 first, times out
by tajen 9y ago
I once ticked "IPv6" when ordering a Debian VPS. It was super-slow and I didn't know IPv6 was the cause. Basically the system always tries IPv6 first, times out at 30s, then tries IPv4. I never completed an `apt-get update` and I assumed my provider had sold me crap. Years later, I discovered that disabling IPv6 did the trick.
So, my noob advice: If you ask for a guide about IPv6, it's not for you yet.
- zAy0LfpBZLC8mAC 9y agoActually, your provider did sell you crap. IPv6 will only be tried if your host has configured IPv6 connectivity and the destination host has IPv6 DNS entries. Debian mirrors generally support IPv6, so apt-get hanging probably means that the IPv6 connectivity of your provider was broken.
- BenjiWiebe 9y agoThat was my thought too. IPv6 shouldn't cause hangs if it is configured correctly.
- deathanatos 9y agoI just want to emphasize this a bit: IPv6 won't cause hangs even if the connection is IPv4 only if things are configured correctly. (That said, I've seen incorrect configurations: Comcast, at one point, assigned me an IPv6 address (automatically) and led the system to believe that their was a valid IPv6 route, but proceeded to drop all IPv6 packets. This same scenario can happen on IPv4, too, and the resolution is the same: worm your way through the bowels of support until you reach someone competent.)