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
It would be nice to get the TTL of a ping response.
ping www.google.com (173.194.115.84): 56 data bytes
64 bytes from 173.194.115.84: icmp_seq=0 ttl=54 time=52.172 ms
64 bytes from 173.194.115.84: icmp_seq=1 ttl=54 time=34.843 ms
Proposal:
I think it would not be easy or make sense to generate the average of the TTLs if you executed >1 pings.
But the TTL during one ping command would be the same in most cases^, anyway.
So the last (or first) TTL of the output would be sufficient.
Current behavior:
TTL is not returned by the ping plugin.
Desired behavior:
Output the TTL from the ping.
Use case:
When you have a diagram with the TTL to a remote host you can see if and how the routing between local and remote host has changed during the time. Useful for monitoring WAN-Connections.
The text was updated successfully, but these errors were encountered:
Fluctuating TTL in a single ping is not a normal behaviour, unless DHCP server permits two machines with the same ip address. @CWempe What is the use case you are using the plugin for ?
Feature Request
It would be nice to get the TTL of a ping response.
Proposal:
I think it would not be easy or make sense to generate the average of the TTLs if you executed >1 pings.
But the TTL during one ping command would be the same in most cases^, anyway.
So the last (or first) TTL of the output would be sufficient.
Current behavior:
TTL is not returned by the ping plugin.
Desired behavior:
Output the TTL from the ping.
Use case:
When you have a diagram with the TTL to a remote host you can see if and how the routing between local and remote host has changed during the time. Useful for monitoring WAN-Connections.
The text was updated successfully, but these errors were encountered: