Forum Discussion
Stefan_Klotz
Cumulonimbus
Cumulonimbusping output shows truncated entry from not pinged address
I noticed following strange output when pinging a node:
[prompt] # ping x.x.x.x
PING x.x.x.x (x.x.x.x) 56 (84) bytes of data.
64 bytes from x.x.x.x: icmp_seq=1 ttl=61 time=xx ms
64 bytes from x.x.x.x: icmp_seq=2 ttl=61 time=xx ms
64 bytes from x.x.x.x: icmp_seq=3 ttl=61 time=xx ms
64 bytes from x.x.x.x: icmp_seq=4 ttl=61 time=xx ms
64 bytes from x.x.x.x: icmp_seq=5 ttl=61 time=xx ms
...
32 bytes from y.y.y.y: icmp_seq=26978 ttl=61 (truncated)
64 bytes from x.x.x.x: icmp_seq=54 ttl=61 time=xx ms
64 bytes from x.x.x.x: icmp_seq=55 ttl=61 time=xx ms
When stopping the ping I see in the statistics one more packet received than transmitted.
Where does this comes from? Has this any special meaning? Is this indicating any strange behavior or misconfiuration in the network?
Thanks for any helpful ideas or information to further investigate this!
Regards,
Stefan 🙂
Hello Stefan,
Your capture is expressed all in one line and is confusing to be interpreted
Anyway, take into account that when you press "CTRL+C", you are interrupting the process unexpectedly and one packet could be lost in the wire (packet sent without response).
Try this instead (to control how many packets you are sending)
ping -c10 x.x.x.x
ConfigTerminalNimbostratus
Hi Stefan, did you ever figure out what the cause was? I'm experiencing something identical to what you posted about all these years ago.
