Content filtering on pfSense is still a work in progress. There has
been a lot of work done on a port of SquidGuard, but I haven't used it
so I don't know how functional it is yet. There will be a more robust
content filtering component coming later this year as part of Centipede
Networks' contribution to pfSense, but that piece is still a ways off.
-Gary
Richard Sperry wrote:
I have a client that needs to play god over their employees. I need to create
a 6 site IPSEC mesh and I need Content filtering along with IM filtering.
IPSec seemed to have an issue on my test, but I think that may be the server
itself. As the carp failover peer went offline. I would like to limit upstream
content to SMB/CIFS/DNS/HTTP/etc/ I can only figure how to block on the
receiving end, and could cause me to have a large bandwidth cost as I am billed
per what goes up the pipe, not what I accept.
The issue on content filtering was that the upstream provider has latency
issues and squid returned a basic 404 instead of trying a few times like IE or
FF.
Also IMspector had no log and throws an err of missing mysql. Even thou I want
it locally for now. ( a central point like OSSIM.net would kick arse.
Any thoughts?
--Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
