Re: [nmap-svn] r6963 - nmap-exp/david/nmap-fixed-rate

[David Fifield <david () bamsoftware com>]

On Sat, Mar 22, 2008 at 12:24:07AM -0500, Kris Katterjohn wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Fyodor wrote:
> | On Sat, Mar 22, 2008 at 12:28:31AM +0000, Brandon Enright wrote:
> |> I look forward to the end-result, sometime sending at N pps is exactly
> |> what I want Nmap to do.
> |
> | Instead of offering just a fixed packet send rate (which I think is
> | what Scanrand and Unicornscan do), I'm starting to think we should
> | allow you to set a minimum and/or maximum packet send rate.  If you
> | are trying to speed Nmap up, you would set a minimum rate which would
> | override Nmap's normal congestion control algorithms if they would
> | otherwise slow Nmap below that rate.  But this would still allow Nmap
> | to ramp up to faster rates if you are scanning an unfirewalled
> | localhost or the like.
> |
>
> I like this minimum rate idea more than the fixed rate.
>
> Also (instead of replying to a different nmap-svn email): I think the
> option would be more flexible if instead of --rate <num> (which is
> per-second) like in r6962 of David's branch, it can be given a modifier
> like "2/s" for 2 per-second, "150/m" for 150 per-minute, etc.  Or maybe
> it should default to per-second.

I'm going to ask for ideas about the command-line interface once the
infrastructure is in place. Another idea I had is specifying a certain
byte or bit rate. So yeah, nobody get too attached to the current
option because I'm just using it for experimentation.

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org