Packet loss

musthafa786 · ‎03-07-2013

Hi,

I am getting packet loss when I do continuous ping to below two destination,

Could anyone help me on this ? thanks.

dest 1:

-----------------------------------------------------------------------------------------------

64 bytes from 100.50.23.140: icmp_seq=115 ttl=61 time=4.742 ms

64 bytes from 100.50.23.140: icmp_seq=116 ttl=61 time=3.879 ms

64 bytes from 100.50.23.140: icmp_seq=117 ttl=61 time=3.625 ms

64 bytes from 100.50.23.140: icmp_seq=118 ttl=61 time=3.648 ms

64 bytes from 100.50.23.140: icmp_seq=119 ttl=61 time=3.856 ms

64 bytes from 100.50.23.140: icmp_seq=120 ttl=61 time=3.791 ms

Request timeout for icmp_seq 121

64 bytes from 100.50.23.140: icmp_seq=122 ttl=61 time=3.595 ms

64 bytes from 100.50.23.140: icmp_seq=123 ttl=61 time=3.717 ms

64 bytes from 100.50.23.140: icmp_seq=124 ttl=61 time=3.568 ms

64 bytes from 100.50.23.140: icmp_seq=152 ttl=61 time=3.711 ms

64 bytes from 100.50.23.140: icmp_seq=153 ttl=61 time=3.819 ms

64 bytes from 100.50.23.140: icmp_seq=154 ttl=61 time=3.484 ms

64 bytes from 100.50.23.140: icmp_seq=155 ttl=61 time=3.766 ms

64 bytes from 100.50.23.140: icmp_seq=156 ttl=61 time=3.797 ms

64 bytes from 100.50.23.140: icmp_seq=157 ttl=61 time=3.799 ms

64 bytes from 100.50.23.140: icmp_seq=158 ttl=61 time=3.828 ms

64 bytes from 100.50.23.140: icmp_seq=159 ttl=61 time=3.754 ms

64 bytes from 100.50.23.140: icmp_seq=160 ttl=61 time=3.711 ms

64 bytes from 100.50.23.140: icmp_seq=153 ttl=61 time=8003.554 ms (DUP!)

Request timeout for icmp_seq 161

64 bytes from 100.50.23.140: icmp_seq=162 ttl=61 time=3.836 ms

dest 2:

------------------------------------------------------------------------------------------------

64 bytes from 100.50.33.10: icmp_seq=756 ttl=61 time=3.672 ms

64 bytes from 100.50.33.10: icmp_seq=757 ttl=61 time=2146293.864 ms

wrong data byte #8 should be 0x8 but was 0x55

cp:51 38 58 b5 80 18 16 a0

55 ac 0 0 1 1 8 a 0 0 fd 90 14 15 16 17

28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37

dp:51 37 58 b5 0 5 e1 3e

8 9 a b c d e f 10 11 12 13 14 15 16 17

18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27

28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37

64 bytes from 100.50.33.10: icmp_seq=758 ttl=61 time=3.774 ms

64 bytes from 100.50.33.10: icmp_seq=759 ttl=61 time=3.797 ms

64 bytes from 100.50.33.10: icmp_seq=760 ttl=61 time=3.726 ms

64 bytes from 100.50.33.10: icmp_seq=761 ttl=61 time=2.932 ms

Regards,

Musthafa

cflory · ‎03-07-2013

Are you taking errors on your circuit or is there an issue at your provider?

-Chris

jawad-mukhtar · ‎03-07-2013

The "DUP" means that "ping" received two replies to one enquiry - the

icmp_sequence number is duplicated.ing will report duplicate and damaged packets. Duplicate packets

should never occur, and seem to be caused by inappropriate link-level

retransmissions. Duplicates may occur in many situations and are

rarely (if ever) a good sign, although the presence of low levels of

duplicates may not always be cause for alarm.

Damaged packets are obviously serious cause for alarm and often indi-

cate broken hardware somewhere in the ping packet’s path (in the net-

work or in the hosts).

Jawad