OK I think we should all clear something up here. A firewall is *NOT* a IDS system. A IDS system (now this is just my view on it) should not be running on the same machine as a firewall. The best setup for a firewall plus a IDS system would be a IDS machine outside of the firewall and one inside....
hmm its early so I hope I've made some sence [:)] later
I agree you when you say that a Firewall is not a IDS. My English is not very good. So let me explain again what I need.
I need a Intrusion Detect that could de integrated with the Firewall. They won´t be in the same machine, but I need that the IDS re-configure the Firewall automatically, when it detects a threat.
Having an IDS that updates the IPTables filters on the firewall is not a good idea.
The filter table would become enormous in the case of worm attacks such as code red. Also, this creates a trivial denial-of-service vulnerability.
Also, by the time the IDS told the firewall to block the attacker, the worm would already have infected the server.
Instead, you need a filtering firewall. Look at Hogwash (it's a modified Snort). It can be run on a separate machine, or possibly, within ASL hooked into IPTables. I've been trying to install it within Astaro, but I would need the Astaro kernel source and configuration.
Having an IDS that updates the IPTables filters on the firewall is not a good idea.
The filter table would become enormous in the case of worm attacks such as code red. Also, this creates a trivial denial-of-service vulnerability.
Also, by the time the IDS told the firewall to block the attacker, the worm would already have infected the server.
Instead, you need a filtering firewall. Look at Hogwash (it's a modified Snort). It can be run on a separate machine, or possibly, within ASL hooked into IPTables. I've been trying to install it within Astaro, but I would need the Astaro kernel source and configuration.