ntop does not integrate nmap any longer - we switched to the passive ettercap OS fingerprint technology, as part of a plan to eliminate external tools with their associated vulnerabilities.
(If you want to run nmap, lsof, go ahead, but ntop will no longer do it for you, the unprivledged user) -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Craig Humphrey > Sent: Tuesday, March 09, 2004 1:48 PM > To: 'Jake Kallman' > Cc: 'Ntop Dev'; 'NMap Dev' > Subject: [Ntop-dev] RE: Nmap-based mapping/monitoring tool > > > Hi Jake, > > you may also want to look at ntop, which monitors a network > through sniffing > (rather than active scanning), but integrates nmap to probe hosts. > > There are a few commercial tools out there that do this kind of thing (or > similar, or sub/supersets). > I've used What's Up Gold quite a bit. > Just did a little google and https://freemap.qualys.com/ looks > interesting, > and being browser based, there's a certain amount of freedom for > the client > end. > > Have fun and keep us in the loop. > > Later'ish > Craig > > > > -----Original Message----- > > From: Jake Kallman [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 09, 2004 9:04 PM > > To: [EMAIL PROTECTED] > > Subject: Nmap-based mapping/monitoring tool > > > > > > I am developing a network monitoring and mapping tool based > > around nmap, > > which will provide a graphical representation of a network > > topology and > > maintain a database of information about computers in that > > network. In > > essence, it will take the output of namp, run at scheduled > > intervals, and > > compare that data against data from previous runs to try and flag > > potential security and infrastructure problems. > > > > The idea, at a high level is fairly simple, and in fact is a > > little more > > complicated than it needs to be since I'm doing this as a project to > > complete my undergraduate degree in CS. I'm writing a driver program, > > which will sit on a network server somewhere, and will run nmap at > > scheduled intervals on all computers in the network (which > > I'm going to > > try and optimize somewhat by allowing for multiple nmapping > > servers in the > > network so as to distribute the work as much as possible). There will > > also be a client application which will allow a user to > > access this data > > remotely (ideally I'm trying to create this client application to > > allow users to log into the server from multiple platforms, > > like PDAs and > > cell phones, which might not be currently available, but when > > I talked to > > some network engineers in my area they said that it would be a great > > feature). The client will access the data from the server program, and > > create a graphical map of the network, showing any potential problem > > areas. Ideally, I want to be able to flag network slowdowns > > and outages, > > newly enabled/disabled ports on machines, newly connected > > machines (with > > an eye toward being able to watch for unauthorized wireless > > connections) > > and things of that nature. > > > > My question is whether or not this seems like a usable idea? > > If not, then > > what seems unfeasible about the design? > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev > _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
