[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Open source network scanning / invetory / graphing tool?



Matt Cuttler pisze:
Quoting norbert_schuetz@bigfoot.com from 2/26/09 6:00 PM

Hi folks,

is there any free tool for scanning and graphing (that is, 2D graph) a
LAN that will painfree run or compile under Debian? Or at least build
some sort of ip/device inventory for inital basic network analysis and
documentation? Possibly even with an option to add additional info
(room, hardware details, ...) manually?
For the need of every-now-and-then documenting a new customers network a
closed source windows-only software is not an option and also beyond any
- for the task - resonable price tag.

Any hints appreciated,
Norbert


http://cheops-ng.sourceforge.net/screenshots.php

If you're looking for something which actively probes/scans, try cheops-ng.
If you have the luxury of sitting on a regen tap or SPAN port, you might
wish to try:
-Etherape (available in apt),
-PADS (available in apt), or
-PVS f/k/a NeVO - (commercial from Tenable (from the Nessus fame)), which
can show platform type, browser and mail client versions, etc. And of
course, alert you to said clients/servers which might be vulnerable.

..Or just serially/sequentially scan your network with Nessus and/or nmap
(both available in apt) - to get an idea of the environment you're looking
to tackle. OS Fingerprinting is usually accurate for most widely-used
platforms; it may venture strange guesses on "one-off" platforms, such as
lightweight/embedded IP stacks (such as those found in braindead network
"appliances", storage array management interfaces, etc.).

Not knowing specifics of this environment you might want to skip the
graphics, and simply start with nmap or Nessus to get "the lay of the land".

Just keep in mind that any active scanning might confuse/crash
older/unpatched (and/or) badly-configured devices/appliances.

-Matt Cuttler



Look at http://www.ossim.net/
If I know there is a debian based ossim distro.

--
Thomas.


Reply to: