Skip to content
New issue

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

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

Already on GitHub? # to your account

--print-ttl --print-tos doesn't work with -l and -c options #367

Closed
O-ring opened this issue Dec 9, 2024 · 2 comments
Closed

--print-ttl --print-tos doesn't work with -l and -c options #367

O-ring opened this issue Dec 9, 2024 · 2 comments

Comments

@O-ring
Copy link

O-ring commented Dec 9, 2024

Hello everyone,

The --print-ttl --print-tos options do not work when the -c or -l parameters are used.

This is a working example:
fping 10.81.104.126 --print-ttl --print-tos
10.81.104.126 is alive (TOS 72) (TTL 59)

This is a non-working example:
fping 10.81.104.126 --print-ttl --print-tos -c 1
10.81.104.126 : [0], 64 bytes, 20.3 ms (20.3 avg, 0% loss)

Cheers,
Marco

@auerswal
Copy link
Collaborator

auerswal commented Dec 9, 2024

There is another output format that does not print TOS or TTL values: -Q SECS, --squiet SECS.

auerswal added a commit to auerswal/fping that referenced this issue Dec 9, 2024
This addresses GitHub issue schweikert#367, except regarding -QN.
auerswal added a commit to auerswal/fping that referenced this issue Dec 10, 2024
@auerswal
Copy link
Collaborator

There is another output format that does not print TOS or TTL values: -Q SECS, --squiet SECS.

The output of -c N, -C N, and -l is per packet, and can show the packet's TOS and/or TTL, but the -Q SECS output is in general not per packet. Thus I'd say that -Q SECS should print neither TOS nor TTL.

schweikert pushed a commit that referenced this issue Dec 14, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants