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

Get TTL from ping #5537

Closed
CWempe opened this issue Mar 6, 2019 · 5 comments
Closed

Get TTL from ping #5537

CWempe opened this issue Mar 6, 2019 · 5 comments
Labels
feature request Requests for new plugin and for new features to existing plugins
Milestone

Comments

@CWempe
Copy link

CWempe commented Mar 6, 2019

Feature Request

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.

@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Mar 6, 2019
@dheerajdwivedi
Copy link
Contributor

I am picking this up.
Any suggestions on what should be the TTL value

  1. First TTL
  2. Last TTL
  3. List of unique TTL

@CWempe
Copy link
Author

CWempe commented Mar 8, 2019

More suggestions:

  1. Min TTL
  2. Max TTL
  3. Most occurred TTL

Maybe all options (4-6) and the user can decide.

Sorry, I am not helping to find a decision. 🙈

@dheerajdwivedi
Copy link
Contributor

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 ?

@CWempe
Copy link
Author

CWempe commented Mar 8, 2019

Use case is monitoring WAN connections to other branches and see if there is any strange behavior.

But you are right. One value should be enough

@danielnelson
Copy link
Contributor

Closed in #5556

@danielnelson danielnelson added this to the 1.11.0 milestone Mar 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

No branches or pull requests

3 participants