Bug 115333
Summary: | ping flood is hardly a flood | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Andrew Schultz <ajschult784> |
Component: | iputils | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-22 13:51:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Schultz
2004-02-10 22:01:15 UTC
The man page says flood ping does up to 100 packages per second, not more than 100: -f Flood ping. For every ECHO_REQUEST sent a period ââ.ââ is printed, while for ever ECHO_REPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hun- dred times per second, whichever is more. Only the super-user may use this option with zero interval. This new behaviour is wanted as flood ping was know to be used to "shutdown" remote systems by sending as much packages as possible. This is now not possible anymore so easily with ping. Read ya, Phil > The man page says flood ping does up to 100 packages per second, not > more than 100: this is certainly false. The man page says: > outputs packets as fast as they come back or one hundred times per > second, whichever is more. "as fast as they come back" is more than "one hundred times per second" and should be used, according to the man page. Ups, true, but then the manpage needs to be corrected at some point as the code clearly limits to a maximum of 100 packages per second. Read ya, Phil |