Bug #3152
closed
Updater should fall back to IPv4 if IPv6 fails
0%
Description
Updater tries to use ipv6 even if ipv6 is disabled.
If ISP connect ipv6 segment to WAN updater uses ipv6 and could not connect to update server and fails.
The updater should check if ipv6 is activated or connection fail and than fall back to ipv4.
Updated by Chris Buechler over 10 years ago
- Target version deleted (
2.1)
if it appears you have v6 connectivity and you actually don't, you need to disable IPv6. Having it disabled on all your interfaces, it won't try to connect via v6.
Not sure there's anything we can do about this (lots of things get broken or flaky if you have seemingly but not functional v6 configured on every OS), but will leave it for future consideration.
Updated by Renato Botelho over 10 years ago
Feature described at #2833 can help on this
Updated by Chris Buechler about 8 years ago
- Subject changed from Updater should fall back to ipv4 to Updater should fall back to IPv4 if IPv6 fails
- Status changed from New to Confirmed
- Affected Version changed from 2.1 to All
Updated by
Updated by Jim Pingle about 8 years ago
Had this happen on a VM with DHCPv6 here. Somehow it lost its WAN IPv6 IP address, when it tried to check for updates, the v6 request went on so long it caused the GUI to hang up, nginx returned a gateway timeout until I reset php-fpm.
Updated by Renato Botelho almost 4 years ago
- Status changed from Confirmed to Closed
Since this bug was opened we moved to a completely different upgrade model using pkg