3 ms·

> The problem is either in your ISP, your network or client configuration. Thank you for telling me that it's broken. That's kinda my point. Again, I don't h

by clarry 7y ago

> The problem is either in your ISP, your network or client configuration. Thank you for telling me that it's broken. That's kinda my point. Again, I don't have IPv6 connectivity to the world, at all. Random applications trying to enable and use it per default is bound to fail.

Jonnax 7y ago
You linked to a bug in Firefox Nightly. That's hardly indicative of there being widespread issues. Also that bug seems to occur when IPv6 is disabled in the kernel. Random applications should be fine with trying the IPv6 address, and if it fails using the IPv4 address. That should happen transparently. There are millions of Linux deployments that don't require manually disabling IPv6. You not having an IPv6 address is a separate issue.
Dagger2 7y ago
If you don't have v6 connectivity, then by default DNS lookups will be sorted so that v4 addresses are first. I don't know what went wrong in your case, but I don't think it had anything to do with IPv6. `getent hosts` returns v6 addresses (only, no v4) if any exist on the hostname you give it, and thus its output is useless for debugging here. You need to check `getent ahosts <hostname>`, which uses the same getaddrinfo() call that most software (including Firefox) uses for DNS lookup. If you have no v6 connectivity then the v4 addresses should be sorted first in the output of that, and v4 will be tried first by your software. Another good test is `wget <url>` which prints the IPs in sorted order (limited to the first 3 though), tries to connect to them one by one and prints any errors it encounters. If `getent ahosts` is showing v6 addresses sorted first, I'd be happy to take a look at your config -- if you pastebin the output of `ifconfig` and /etc/gai.conf then I should be able to tell you what's up. Either you'll have a v6 address you didn't notice or you've somehow configured your system to sort them first even when you only have v4. For some reason, there's a "I saw a colon somewhere, therefore it's IPv6's fault" trap that people keep falling into. Your posts look like an example of that.
umanwizard 7y ago
Can you explain what exactly is the behavior when you forget to disable IPv6 on a new install? My ISP offers IPv4 only. I've used Windows, various flavors of Linux, macOS, iOS, FreeBSD, Playstation 4, Apple TV, and Android, and they have all "just worked" flawlessly without me ever having to manually tune anything. I'm curious what issues you are running into.

by clarry 7y ago

Jonnax 7y ago

You linked to a bug in Firefox Nightly. That's hardly indicative of there being widespread issues. Also that bug seems to occur when IPv6 is disabled in the kernel. Random applications should be fine with trying the IPv6 address, and if it fails using the IPv4 address. That should happen transparently. There are millions of Linux deployments that don't require manually disabling IPv6. You not having an IPv6 address is a separate issue.

Dagger2 7y ago

If you don't have v6 connectivity, then by default DNS lookups will be sorted so that v4 addresses are first. I don't know what went wrong in your case, but I don't think it had anything to do with IPv6. `getent hosts` returns v6 addresses (only, no v4) if any exist on the hostname you give it, and thus its output is useless for debugging here. You need to check `getent ahosts <hostname>`, which uses the same getaddrinfo() call that most software (including Firefox) uses for DNS lookup. If you have no v6 connectivity then the v4 addresses should be sorted first in the output of that, and v4 will be tried first by your software. Another good test is `wget <url>` which prints the IPs in sorted order (limited to the first 3 though), tries to connect to them one by one and prints any errors it encounters. If `getent ahosts` is showing v6 addresses sorted first, I'd be happy to take a look at your config -- if you pastebin the output of `ifconfig` and /etc/gai.conf then I should be able to tell you what's up. Either you'll have a v6 address you didn't notice or you've somehow configured your system to sort them first even when you only have v4. For some reason, there's a "I saw a colon somewhere, therefore it's IPv6's fault" trap that people keep falling into. Your posts look like an example of that.

umanwizard 7y ago

Can you explain what exactly is the behavior when you forget to disable IPv6 on a new install? My ISP offers IPv4 only. I've used Windows, various flavors of Linux, macOS, iOS, FreeBSD, Playstation 4, Apple TV, and Android, and they have all "just worked" flawlessly without me ever having to manually tune anything. I'm curious what issues you are running into.