Folks,
I've made some significant changes to ntop in the main branch. The main ones of
interest to people, I presume, would be:
- Added support for configuring Ntop via the web interface
- Changed the menus to be more coherent & flowing
- The startup page is the Summary->Traffic page. The page which
described ntop is now viewable under About->Ntop. If no capture is
on, the startup page is the "Configure ntop" page.
The GUI configuration can be used to configure all parameters that are
specified via the command line except for the options:
- -P (db-path)
- -u (user)
The configured preferences are saved and reloaded on startup. So, you don't
have to start ntop with all the detailed command line options nor remember the
options anymore. If you have rw access to the default db-path directory, you
can start ntop as "./ntop" (or equivalent on Win*) and when you connect to the
web interface, you'll be automatically taken to the configuration screen to
setup ntop. Save the configuration and restart ntop and you should be good to
go.
Next steps in this direction are:
- Fix the webport/sslPort support to accept addresses instead of
only ports as is the case now
- Allow some options to take effect immediately and color these
options differently so the user can identify them easily.
- Start and stop captures and load different capture files without
having to restart ntop.
- Allow some preliminary skinning
To see any of this, you need to delete the following files from the html
directory and start ntop:
Admin.html All.html About.html FibreChannel.html IP.html Summary.html Local.html
SCSI.html index*.html
I've tested the code on Linux with both FC and IP captures to some extent and
obviously there will be bugs. Please feel free to send feedback to this
list. Enjoy,
Dinesh
--
Empowerment is all about letting go so that others can get going.
- Kenneth Blanchard
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
