Nmap Development mailing list archives
Re: Desired --max-rate behavior: exceed the maximum to keep up the average?
From: Brandon Enright <bmenrigh () ucsd edu>
Date: Mon, 4 Aug 2008 22:39:55 +0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 4 Aug 2008 15:19:26 -0600 David Fifield <david () bamsoftware com> wrote:
What do you think is the right behavior? Should --max-rate be strict or lenient? David
I think in the networking world most people treat a "rate" as an average over time -- often 1 or 5 seconds. When specifically referring to a short time-slice people call that the "burst-rate". Perhaps - --max-rate can average and if we want to enforce a minimum packet delay we can add an option like --disallow-bursting Or perhaps rather than have a --max-rate option we have a - --min-interpacket-delay to enforce such things? - --min-interpacket-delay could take a raw number (mili or micro seconds) or perhaps even the suffice like pps (ex: 2000pps) and do the math for people to figure out how many microseconds that is. Having --max-rate severely kill performance because packets missed their timeslice will confuse many people and make the option quite a bit less useful. Brandon -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiXhTwACgkQqaGPzAsl94LPqQCfRCM30WoA4zgc5spftEP9jXe1 qNUAn0A1pSFt48oo75gCcCtmaTlW8gK7 =Gvvg -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Desired --max-rate behavior: exceed the maximum to keep up the average? David Fifield (Aug 04)
- Re: Desired --max-rate behavior: exceed the maximum to keep up the average? Brandon Enright (Aug 04)