On 04/07/17 18:00, Patrick O'Callaghan wrote:
I'm wondering if this could be related to MTU issues, which in
the past
have sometimes caused very mysterious behaviour. Not sure how to check
though. Maybe use tracepath (not traceroute), or ping with different
size packets might show something.
I do not know.... But another possibility (thinking about another
thread)....
[root@meimei enp2s0]# host
docs.python.org
docs.python.org is an alias for
python.map.fastly.net.
python.map.fastly.net has address 151.101.0.223
python.map.fastly.net has address 151.101.192.223
python.map.fastly.net has address 151.101.64.223
python.map.fastly.net has address 151.101.128.223
python.map.fastly.net has IPv6 address 2a04:4e42::223
python.map.fastly.net has IPv6 address 2a04:4e42:200::223
python.map.fastly.net has IPv6 address 2a04:4e42:400::223
python.map.fastly.net has IPv6 address 2a04:4e42:600::223
So that host has 4 IPv4 and 4 IPv6 addresses.
Probably a long shot, but if the system isn't configured properly for
IPv6 it may explain why it works sometimes and not others.
In looking at wireshark earlier trying to see what a re-transmitted
packet would be displayed I found my system seems to prefer IPv6 for
that particular host. :-)
Not sure what good tracepath would be since....
[root@meimei enp2s0]# tracepath -n 151.101.192.223
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 0.577ms
1: 192.168.1.1 0.560ms
2: 211.75.128.254 9.495ms
3: 168.95.229.46 9.464ms
4: 220.128.4.102 10.177ms asymm 6
5: 220.128.1.182 16.220ms asymm 6
6: 220.128.4.21 31.501ms
7: 211.22.33.53 34.772ms asymm 9
8: 61.14.157.82 38.363ms asymm 9
9: 61.14.157.78 74.545ms asymm 13
10: 61.14.158.41 70.767ms asymm 12
11: 61.14.158.41 66.320ms asymm 12
12: no reply
13: no reply
14: no reply
--
Fedora Users List - The place to go to get others to do the work for you