История изменений
Исправление Kroz, (текущая версия) :
Нашёлся виновник - это 10.38.100.254, похоже что gateway провайдера. На нём периодически пропадают пакеты.
ping:
C:\Windows\system32>ping -t www.google.com
Pinging www.google.com [172.217.16.4] with 32 bytes of data:
...
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Request timed out.
Request timed out.
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Request timed out.
Request timed out.
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Ping statistics for 172.217.16.4:
Packets: Sent = 25, Received = 21, Lost = 4 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 23ms, Average = 15ms
Control-C
-----------------------------------------------------------
$ ping www.google.com -n -s 24
PING www.google.com (172.217.16.4) 24(52) bytes of data.
32 bytes from 172.217.16.4: icmp_seq=1 ttl=117 time=15.7 ms
32 bytes from 172.217.16.4: icmp_seq=2 ttl=117 time=19.0 ms
32 bytes from 172.217.16.4: icmp_seq=3 ttl=117 time=15.7 ms
32 bytes from 172.217.16.4: icmp_seq=4 ttl=117 time=40.9 ms
32 bytes from 172.217.16.4: icmp_seq=5 ttl=117 time=32.5 ms
^C
--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 15.653/24.748/40.906/10.191 ms
traceroute:
C:\Windows\system32>tracert 172.217.16.4
Tracing route to waw02s13-in-f4.1e100.net [172.217.16.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 2 ms 1 ms 1 ms 10.38.100.254
4 * * 4 ms 10.xxx.xxx.xxx
5 2 ms 2 ms 1 ms 10.xxx.xxx.xxx
6 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
7 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
8 3 ms 2 ms 2 ms xxx.xxx.xxx.xxx
9 17 ms 16 ms 16 ms xxx.xxx.xxx.xxx
10 17 ms 17 ms 16 ms xxx.xxx.xxx.xxx
11 17 ms 16 ms 16 ms xxx.xxx.xxx.xxx
12 15 ms 15 ms 16 ms waw02s13-in-f4.1e100.net [172.217.16.4]
-----------------------------------------------------------
$ traceroute 172.217.16.4 -n
traceroute to 172.217.16.4 (172.217.16.4), 30 hops max, 60 byte packets
1 192.168.0.1 2.919 ms 2.860 ms 2.846 ms
2 * * *
3 10.38.100.254 4.077 ms 4.064 ms 4.051 ms
4 10.xxx.xxx.xxx 6.284 ms 6.270 ms 6.258 ms
5 10.xxx.xxx.xxx 2.907 ms 2.894 ms 2.881 ms
6 xxx.xxx.xxx.xxx 4.955 ms 4.288 ms 4.254 ms
7 xxx.xxx.xxx.xxx 4.243 ms 4.194 ms xxx.xxx.xxx.xxx 6.355 ms
8 xxx.xxx.xxx.xxx 16.482 ms xxx.xxx.xxx.xxx 17.201 ms xxx.xxx.xxx.xxx 17.123 ms
9 xxx.xxx.xxx.xxx 16.266 ms xxx.xxx.xxx.xxx 16.696 ms 18.006 ms
10 xxx.xxx.xxx.xxx 17.956 ms xxx.xxx.xxx.xxx 17.945 ms xxx.xxx.xxx.xxx 17.620 ms
11 xxx.xxx.xxx.xxx 17.587 ms 17.572 ms xxx.xxx.xxx.xxx 17.558 ms
12 172.217.16.4 16.810 ms 15.724 ms 16.833 ms
MTU:
C:\Windows\system32>netsh interface ipv4 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 116090 Loopback Pseudo-Interface 1
1500 1 4662907379 384954954 Wi-Fi
1500 5 0 0 Ethernet
-----------------------------------------------------------
$ ifconfig -a
bond0: flags=5122<BROADCAST,MASTER,MULTICAST> mtu 1500
ether f6:66:0e:bf:a4:18 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
dummy0: flags=130<BROADCAST,NOARP> mtu 1500
ether b6:c2:c3:ff:01:cd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 08:8f:c3:49:8b:27 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 117 bytes 8636 (8.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 117 bytes 8636 (8.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1000 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::5563:afa9:7aba:aeb1 prefixlen 64 scopeid 0x20<link>
ether 14:5b:fa:78:70:a1 txqueuelen 1000 (Ethernet)
RX packets 1064798 bytes 1477582276 (1.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 354493 bytes 32662779 (31.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Исходная версия Kroz, :
Нашёлся виновник - это 10.38.100.254, похоже что gateway провайдера. На нём периодически пропадают пакеты.
ping:
C:\Windows\system32>ping -t www.google.com
Pinging www.google.com [172.217.16.4] with 32 bytes of data:
...
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Request timed out.
Request timed out.
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Request timed out.
Request timed out.
Reply from 172.217.16.4: bytes=32 time=15ms TTL=117
Ping statistics for 172.217.16.4:
Packets: Sent = 25, Received = 21, Lost = 4 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 23ms, Average = 15ms
Control-C
-----------------------------------------------------------
$ ping www.google.com -n -s 24
PING www.google.com (172.217.16.4) 24(52) bytes of data.
32 bytes from 172.217.16.4: icmp_seq=1 ttl=117 time=15.7 ms
32 bytes from 172.217.16.4: icmp_seq=2 ttl=117 time=19.0 ms
32 bytes from 172.217.16.4: icmp_seq=3 ttl=117 time=15.7 ms
32 bytes from 172.217.16.4: icmp_seq=4 ttl=117 time=40.9 ms
32 bytes from 172.217.16.4: icmp_seq=5 ttl=117 time=32.5 ms
^C
--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 15.653/24.748/40.906/10.191 ms
traceroute:
C:\Windows\system32>tracert 172.217.16.4
Tracing route to waw02s13-in-f4.1e100.net [172.217.16.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 2 ms 1 ms 1 ms 10.38.100.254
4 * * 4 ms 10.xxx.xxx.xxx
5 2 ms 2 ms 1 ms 10.xxx.xxx.xxx
6 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
7 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
8 3 ms 2 ms 2 ms xxx.xxx.xxx.xxx
9 17 ms 16 ms 16 ms xxx.xxx.xxx.xxx
10 17 ms 17 ms 16 ms xxx.xxx.xxx.xxx
11 17 ms 16 ms 16 ms xxx.xxx.xxx.xxx
12 15 ms 15 ms 16 ms waw02s13-in-f4.1e100.net [172.217.16.4]
-----------------------------------------------------------
$ traceroute 172.217.16.4 -n
traceroute to 172.217.16.4 (172.217.16.4), 30 hops max, 60 byte packets
1 192.168.0.1 2.919 ms 2.860 ms 2.846 ms
2 * * *
3 10.38.100.254 4.077 ms 4.064 ms 4.051 ms
4 10.xxx.xxx.xxx 6.284 ms 6.270 ms 6.258 ms
5 10.xxx.xxx.xxx 2.907 ms 2.894 ms 2.881 ms
6 xxx.xxx.xxx.xxx 4.955 ms 4.288 ms 4.254 ms
7 xxx.xxx.xxx.xxx 4.243 ms 4.194 ms xxx.xxx.xxx.xxx 6.355 ms
8 xxx.xxx.xxx.xxx 16.482 ms xxx.xxx.xxx.xxx 17.201 ms xxx.xxx.xxx.xxx 17.123 ms
9 xxx.xxx.xxx.xxx 16.266 ms xxx.xxx.xxx.xxx 16.696 ms 18.006 ms
10 xxx.xxx.xxx.xxx 17.956 ms xxx.xxx.xxx.xxx 17.945 ms xxx.xxx.xxx.xxx 17.620 ms
11 xxx.xxx.xxx.xxx 17.587 ms 17.572 ms xxx.xxx.xxx.xxx 17.558 ms
12 172.217.16.4 16.810 ms 15.724 ms 16.833 ms
MTU:
C:\Windows\system32>netsh interface ipv4 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 116090 Loopback Pseudo-Interface 1
1500 1 4662907379 384954954 Wi-Fi
1500 5 0 0 Ethernet