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

nping: rate > 1000 equals 0 delay #1751

Open
jomo opened this issue Sep 20, 2019 · 0 comments

Comments

@jomo
Copy link

commented Sep 20, 2019

nping converts the --rate option to millisecond delay using 1000 / rate, which means that a rate over 1000 equals a delay of 0.
As only millisecond delay is supported, a --delay less than 0.001 seconds also equals a delay of 0.

This behavior doesn't seem to be documented and the result can be an order of magnitudes higher packet rate:

nping -H -N -c 10000 --rate 1000 127.0.0.1

Starting Nping 0.7.80 ( https://nmap.org/nping )

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 10000 (280.000KB) | Rcvd: 0 (0B) | Lost: 10000 (100.00%)
Nping done: 1 IP address pinged in 12.00 seconds
nping -H -N -c 10000 --rate 1001 127.0.0.1

Starting Nping 0.7.80 ( https://nmap.org/nping )
 
Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 10000 (280.000KB) | Rcvd: 0 (0B) | Lost: 10000 (100.00%)
Nping done: 1 IP address pinged in 0.09 seconds

In my opinion, nping should exit with an error message if the rate is 0 without --rate 0 being explicitly requested.

Other than that, it would be nice if nping could support delays < 1ms. Is this feasible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.