We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running fping with a packet size of over 4096 bytes, it doesn't correctly display the size and always defaults to displaying 4096.
So when I run fping -c 10 -M -b 9000, to check jumbo frames. [0], 4090 bytes, 0.03 ms (0.03 avg, 0% loss)
fping -c 10 -M -b 9000
[0], 4090 bytes, 0.03 ms (0.03 avg, 0% loss)
However if I run a tcpdump I do see that the package size does go over 4096 bytes. ICMP echo request, id 11483, seq 0, length 9008
ICMP echo request, id 11483, seq 0, length 9008
The text was updated successfully, but these errors were encountered:
fixed in a136764 (to be released with fping 5.0)
Sorry, something went wrong.
No branches or pull requests
When running fping with a packet size of over 4096 bytes, it doesn't
correctly display the size and always defaults to displaying 4096.
So when I run
fping -c 10 -M -b 9000
, to check jumbo frames.[0], 4090 bytes, 0.03 ms (0.03 avg, 0% loss)
However if I run a tcpdump I do see that the package size does go over 4096 bytes.
ICMP echo request, id 11483, seq 0, length 9008
The text was updated successfully, but these errors were encountered: