Re: Nmap-based mapping/monitoring tool

[Bob McLaren <BobMcLaren () fssi-ca com>]

I appreciate your follow-up.  I'm at a loss, and when I post my problem 
to other newsgroups they all respond blaming it on Nmap.  I'm sure it's 
something stupid having to do with my local setup.  I just don't know 
where to look.

Anyway, regarding your suggestion, yes, I suppose I could manually split 
up the scan.  But I'm not really concerned with how long it takes as 
long as it's within a couple of hours.  I was hoping to start the scan, 
and then go about my business for the afternoon until it was done.  
Instead, because of the 15 and 60 second pauses, it would have taken at 
least the whole day.

Bottom line, to handle my immediate task at hand, I may have to split up 
the scan in to multiple processes.  But I hate "admitting defeat" and 
finding a workaround when I know what the tool is capable of.

Thanks again, and if you or anybody else on this list have any ideas 
about how I can tackle this, I would appreciate ANY input.

-Bob

MadHat wrote:

> On Mar 9, 2004, at 10:57 AM, Bob McLaren wrote:
>
> > Sounds like a fun project to me!
> >
> > The only thing I would be concerned about is trying to monitor an 
> > enterprise-sized network using this approach.
> > If you were going to monitor a small and specific range of addresses, 
> > you would probably be fine.  However, if you intend to scan an entire 
> > Class A or even Class B network several times a day, you will end up 
> > generating a whole heck of a lot of traffic.  Or worse yet, you could 
> > run into my problem (see my earlier post), in that my box seems to 
> > run out of buffer space whenever I try to scan too many hosts in a 
> > network at once.
>
>
> The problems I ran into were that of not completing in a timely manner.
> Bob, have you tried splitting up the /16 into multiple sections to 
> scan and see if that worked?
>
> There are several things around people have used to split up and 
> parallelize scans.  This may speed up scanning and get you past the 
> issue you are seeing.
>
> I had glanced at that thread, but did not follow it, sorry.
>
>
> ---------------------------------------------------------------------
> For help using this (nmap-dev) mailing list, send a blank email to 
> nmap-dev-help () insecure org . List archive: http://seclists.org


---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List archive: http://seclists.org