You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to get pingparsing to show the details when a packet times out?
Currently i am only getting statistics for packets that actually gets a reply - but i would LOVE to be able to get stats on exactly when a packets is lost.
Example with a count of 5 packets - 4 will have timeouts. But i will only get details about the packet that actually gets a reply
(this is from my lab where i physically disconnect a device to simulate packet loss)
ping -D -O -c 10 192.168.120.164
PING 192.168.120.164 (192.168.120.164) 56(84) bytes of data.
[1596530210.505053] 64 bytes from 192.168.120.164: icmp_seq=1 ttl=64 time=1.15 ms
[1596530211.506256] 64 bytes from 192.168.120.164: icmp_seq=2 ttl=64 time=1.03 ms
[1596530213.582215] no answer yet for icmp_seq=3
[1596530214.622238] no answer yet for icmp_seq=4
[1596530215.662215] no answer yet for icmp_seq=5
[1596530216.702221] no answer yet for icmp_seq=6
[1596530217.742217] no answer yet for icmp_seq=7
[1596530217.743357] 64 bytes from 192.168.120.164: icmp_seq=8 ttl=64 time=1.02 ms
[1596530218.744564] 64 bytes from 192.168.120.164: icmp_seq=9 ttl=64 time=1.04 ms
[1596530219.745756] 64 bytes from 192.168.120.164: icmp_seq=10 ttl=64 time=1.04 ms
The text was updated successfully, but these errors were encountered:
Hi
Is it possible to get pingparsing to show the details when a packet times out?
Currently i am only getting statistics for packets that actually gets a reply - but i would LOVE to be able to get stats on exactly when a packets is lost.
Example with a count of 5 packets - 4 will have timeouts. But i will only get details about the packet that actually gets a reply
(this is from my lab where i physically disconnect a device to simulate packet loss)
I imagine it would be able to parse this command?
The text was updated successfully, but these errors were encountered: