Title: Message
Nope... ntop doesn't do stuff like that.  It's not an IDS.  If you're looking just to capture a series of packets, it's hard to beat tcpdump.
 
Sticking within ntop, one could easily write a plugin(s) - each plugin can supply a filter and examine only packets that match it... once you have packets, of course, you can code just about anything.
 
-----Burton


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Riccardo Rosso
Sent: Thursday, April 14, 2005 8:00 AM
To: [email protected]
Subject: Re:[Ntop] Usage of the @ CLI option

Thanks Burton.
What I would like to do is for example to write a set of filters to enable various "burglar alarms" (imagine different attack signatures to make ntop work on).
Another example would be to enable simultaneously different simple filters instead of a single complex filter to select different unrelated flows of traffic (example given FTP betwen hosts inside a LAN, outgoing connections twds the Internet from strange ports/hosts,  SSH connection coming from the outside with malformed packet) .
Hoping to have been a little clearer...
Best regards,
  Riccardo

 
Burton Strauss Burton at ntopSupport.com
Thu Apr 14 14:11:21 CEST 2005


Nope.
 
-B "filter" can certainly be in the configuration (@) file, but there is
only a single filter _expression_.  I understand that Dinesh is working on
per-interface _expression_ logic (the complexity is actually how you specify
it - everything else is already present in ntop).  But that will still be a
single _expression_, as that is all that libpcap will accept.
 
Maybe if you explained what you are trying to accomplish?
 
-----Burton
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to