networking - Ping packet loss 100
2014-04
Alvin Laurentius
I'm using a laptop in a dormitory and I was trying to go to a website, but it only shows texts and white background. When I check another website about the same thing happens, no pics just texts and black background. When I open my twitter I can't see my own profile photo as well as my other friends.
After I do a ping check it shows something like this:
packets transmitted 9
received 0
packet loss 100 %
time 8000 ms
I'm using a direct connection (cable) and no wi-fi router. And I've just pinged google from my command prompt and it doesn't end even after I closed my command prompt. Is something wrong with my connection?
ArcherGodson
You are using tranparent proxy, usually it can transfer HTTP and FTP protocols. It's alright.
If you want to use ping (ICMP protocol) only one way - find your system administrator.
Matt
I've been experiencing some odd behavior. While on a congested wireless network I run
$ ping google.com
I expect one packet to be sent out each second and only some of them to come back with a variety of round trip times, and this is the behavior most of the time. But on this very congested wireless network I see something like this:
PING google.com (74.125.224.228) 56(84) bytes of data.
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=1 ttl=53 time=193 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=2 ttl=53 time=238 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=3 ttl=53 time=96.8 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=4 ttl=53 time=12.9 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=5 ttl=53 time=219 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=9 ttl=53 time=1105 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=8 ttl=53 time=2339 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=17 ttl=53 time=881 ms
64 bytes from lax04s08-in-f4.1e100.net (74.125.224.228): icmp_req=18 ttl=53 time=1200 ms
...
--- google.com ping statistics ---
57 packets transmitted, 41 received, 28% packet loss, time 113307ms
rtt min/avg/max/mdev = 5.773/447.217/2339.271/496.011 ms, pipe 3
The key line is:
57 packets transmitted, 41 received, 28% packet loss, time 113307ms
as you can see the ping ran for about 113 seconds but only sent out 57 packets. I've seen this multiple times:
$ ping google.com
PING google.com (74.125.224.232) 56(84) bytes of data.
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=1 ttl=53 time=6.98 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=2 ttl=53 time=5.71 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=3 ttl=53 time=4.47 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=4 ttl=53 time=5.75 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=5 ttl=53 time=6.94 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=6 ttl=53 time=14.2 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=7 ttl=53 time=6.22 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=8 ttl=53 time=11.8 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=9 ttl=53 time=4.29 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=10 ttl=53 time=5.43 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=11 ttl=53 time=5.02 ms
64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=12 ttl=53 time=4.89 ms
^C64 bytes from lax04s08-in-f8.1e100.net (74.125.224.232): icmp_req=13 ttl=53 time=7.36 ms
--- google.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 60262ms
rtt min/avg/max/mdev = 4.299/6.865/14.258/2.838 ms
This one is even weirder because all the RTTs are reasonable, the packets just aren't getting sent out quickly. Can anyone shed light on this? I'm on debian testing (wheezy), and a few more stats:
$ ping -V
ping utility, iputils-sss20101006
Linux 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 GNU/Linux
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
Kyle Jones
It looks like you have one of the versions of ping that does a DNS lookup for every received packet. Since a DNS UDP packet has to traverse the same congested network as ping packets, the packet may be dropped. With timeouts and retries it can take significant time for a DNS request to return data. The time consumed waiting for a DNS response delays the sending of the next ping packet because your ping is both single-threaded and doesn't use an asynchronous timer to drive each ping.
If my diagnosis is correct, adding -n to ping should get rid of the delays.