Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not parsing ping timeouts, including timestamps #37

Closed
banananananananana opened this issue Aug 4, 2020 · 2 comments
Closed

Not parsing ping timeouts, including timestamps #37

banananananananana opened this issue Aug 4, 2020 · 2 comments
Assignees

Comments

@banananananananana
Copy link

banananananananana commented Aug 4, 2020

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)

pingparsing 192.168.120.164 --icmp-replies -c 5 --timestamp datetime
{
"192.168.120.164": {
"icmp_replies": [
{
"ttl": 64,
"timestamp": "2020-08-04T10:21:10.529026",
"duplicate": false,
"time": 1.03,
"icmp_seq": 1
}
],
"packet_loss_count": 4,
"packet_receive": 1,
"packet_loss_rate": 80.0,
"rtt_avg": 1.031,
"destination": "192.168.120.164",
"packet_transmit": 5,
"packet_duplicate_rate": 0.0,
"rtt_min": 1.031,
"rtt_max": 1.031,
"packet_duplicate_count": 0,
"rtt_mdev": 0.0
}
}

I imagine it would be able to parse this command?

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

@thombashi
Copy link
Owner

Hi,

Unfortunately, that is not possible for now.
To make it possible, need some enhancements.

@thombashi
Copy link
Owner

You can now parse the ping output with pingparsing 1.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants