unclebob
19-09-2010, 21:20
The packet loss has stopped
Thanks OVH
Thanks OVH
debian:~# ping google.com
PING google.com (66.249.92.104) 56(84) bytes of data.
64 bytes from par03s01-in-f104.1e100.net (66.249.92.104): icmp_req=1 ttl=58 time=8.43 ms
^C
--- google.com ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28034ms
rtt min/avg/max/mdev = 8.310/8.476/9.383/0.204 ms
debian:~# ping 173.194.37.104
PING 173.194.37.104 (173.194.37.104) 56(84) bytes of data.
64 bytes from 173.194.37.104: icmp_req=2 ttl=59 time=4.52 ms
^C
--- 173.194.37.104 ping statistics ---
33 packets transmitted, 8 received, 75% packet loss, time 32143ms
rtt min/avg/max/mdev = 4.501/4.556/4.661/0.047 ms
debian:~# traceroute 66.249.92.104
traceroute to 66.249.92.104 (66.249.92.104), 30 hops max, 60 byte packets
1 vss-1-6k.fr.eu (94.23.1.254) 0.423 ms * *
2 ldn-1-6k.uk.eu (94.23.122.65) 114.344 ms * *
3 195.66.224.125 (195.66.224.125) 4.058 ms 4.102 ms 4.095 ms
4 64.233.175.25 (64.233.175.25) 4.265 ms 4.387 ms 4.395 ms
5 72.14.232.95 (72.14.232.95) 8.243 ms 8.236 ms 8.073 ms
6 64.233.175.115 (64.233.175.115) 8.587 ms 8.475 ms 8.498 ms
7 par03s01-in-f104.1e100.net (66.249.92.104) 8.316 ms 8.362 ms 8.415 ms
debian:~# traceroute 173.194.37.104
traceroute to 173.194.37.104 (173.194.37.104), 30 hops max, 60 byte packets
1 vss-1-6k.fr.eu (94.23.1.254) 40.786 ms * *
2 * * *
3 195.66.224.125 (195.66.224.125) 4.053 ms 4.067 ms 4.052 ms
4 64.233.175.27 (64.233.175.27) 4.243 ms 4.312 ms 4.308 ms
5 209.85.251.202 (209.85.251.202) 4.762 ms 4.827 ms 4.889 ms
6 lhr14s02-in-f104.1e100.net (173.194.37.104) 4.442 ms * *
Pinging google.com [173.194.36.104] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 173.194.36.104:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging google.co.uk [173.194.36.104] with 32 bytes of data:
Reply from 173.194.36.104: bytes=32 time=4ms TTL=58
Request timed out.
Reply from 173.194.36.104: bytes=32 time=4ms TTL=58
Request timed out.
Ping statistics for 173.194.36.104:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms
server:~# ping google.com PING google.com (173.194.37.104) 56(84) bytes of data. ... 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=111 ttl=58 time=4.48 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=113 ttl=58 time=4.43 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=120 ttl=58 time=4.43 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=121 ttl=58 time=4.41 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=123 ttl=58 time=4.41 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=124 ttl=58 time=4.45 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=125 ttl=58 time=4.45 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=126 ttl=58 time=4.43 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=128 ttl=58 time=4.47 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=129 ttl=58 time=4.56 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=130 ttl=58 time=4.47 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=131 ttl=58 time=7.79 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=134 ttl=58 time=4.45 ms 64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_seq=135 ttl=58 time=4.40 ms ^C --- google.com ping statistics --- 135 packets transmitted, 69 received, 48% packet loss, time 134410ms rtt min/avg/max/mdev = 4.371/4.540/7.797/0.495 ms