[ previous ] [ next ] [ threads ]
 From:  "Sean Waite" <swaite at sbn dash services dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] IDS
 Date:  Thu, 26 Jan 2006 07:07:34 -0600
Well in that sense you could say that as well regarding VPN, its not part of the firewall's job. But
I would argue that IDS is of more
relevance to a firewall than VPN capability. In fact, the number one request now we have from
clients is IDS, VPN is secondary. 

Although I do understand your point, a web proxy can be run separately, I think a lot of users would
appreciated IDS added to monowall.
At the very least it is one less box to have to muck with.

Sean Waite

-----Original Message-----
From: A dot L dot M dot Buxey at lboro dot ac dot uk
To: BCW <santana110 at telstra dot com>
Cc: m0n0wall at lists dot m0n0 dot ch
Date: Sun, 22 Jan 2006 13:21:32 +0000
Subject: Re: [m0n0wall] IDS

> Hi,
> >  
> > I wonder if there is any consideration for an IDS as part of the next
> > version???
> just like web proxy - this is not part of a firewall job. its trivial 
> to set up a bridge network outside or inside the firewall and run
> snort etc on that - or even connect the LAN port to a hub and just sniff
> that (though a transparent bridge doesnt introduce a collision domain)
> alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch