I have several Suse Linux systems at two different locations (Gilbert and Mesa in the Phoenix metro area) that are having issues picking up a file from dl.google.com via IPv6, the same query via IPv4 works fine. Modems and routers are different at both sites
the IPv4 time to get a reply is .17 seconds versus the IPv6 time of 2 mnutes 7.38 seconds.
Suggestions welcome!
IPv4 query:
dell-3620:/home/data/work #
dell-3620:/home/data/work # time wget -4 https://dl.google.com/linux/linux_signing_key.pub
--2017-08-08 01:53:09-- https://dl.google.com/linux/linux_signing_key.pub
Resolving dl.google.com (dl.google.com)... 172.217.11.78
Connecting to dl.google.com (dl.google.com)|172.217.11.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8038 (7.8K) [application/octet-stream]
Saving to: ‘linux_signing_key.pub.2’
100%[=====================================================================================================>] 8,038 --.-K/s in 0s
2017-08-08 01:53:09 (23.5 MB/s) - ‘linux_signing_key.pub.2’ saved [8038/8038]
real 0m0.170s
user 0m0.042s
sys 0m0.006s
IPv6 query:
dell-3620:/home/data/work # time wget https://dl.google.com/linux/linux_signing_key.pub
--2017-08-08 01:53:23-- https://dl.google.com/linux/linux_signing_key.pub
Resolving dl.google.com (dl.google.com)... 2607:f8b0:4007:802::200e, 172.217.11.78
Connecting to dl.google.com (dl.google.com)|2607:f8b0:4007:802::200e|:443... failed: Connection timed out.
Connecting to dl.google.com (dl.google.com)|172.217.11.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8038 (7.8K) [application/octet-stream]
Saving to: ‘linux_signing_key.pub.3’
100%[=====================================================================================================>] 8,038 --.-K/s in 0.001s
2017-08-08 01:55:30 (11.3 MB/s) - ‘linux_signing_key.pub.3’ saved [8038/8038]
real 2m7.382s
user 0m0.036s
sys 0m0.016s
↧