[Snort-users] Centralized DB Server??

Kris Quinby kquinby at ...2243...
Tue Jun 12 15:28:50 EDT 2001

Are your sensors in different geographic locations?  If not you could have
two network interfaces in each NIDS, one with no IP on the network you are
watching, and one on a "management" network.  Then you could have your MySQL
data base on the management network collecting from all your sensors.


-----Original Message-----
From: Marc Thompson [mailto:Marc.Thompson at ...2101...]
Sent: Monday, June 11, 2001 7:21 AM
To: snort-users at lists.sourceforge.net
Subject: [Snort-users] Centralized DB Server??

I would like to use a IDS architecture using Snort and MySQL 
that utilizes multiple NIDS across many routers and sites, but
only one database to collect alerts.

My question is, wouldn't the action of sending an alert to a
centralized database set off the same rule on a NIDS box sitting
between the alert source and the remote database?

Is the only way to prevent this double-logging of alerts to specify
that the 'in-between' NIDS should ignore traffic from the remote NIDS
to the central database server?  If so, is there a standard way of
specifying this in the Snort configuration file? (ignore traffic
globally to the MySQL TCP port?)

Thank you in advance,
Marc Thompson

Snort-users mailing list
Snort-users at lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
Snort-users list archive:

More information about the Snort-users mailing list