From owner-freebsd-chat Mon Sep 11 12:50:35 2000 Delivered-To: freebsd-chat@freebsd.org Received: from enterprise.sd73.bc.ca (enterprise.sd73.bc.ca [207.23.161.2]) by hub.freebsd.org (Postfix) with ESMTP id BD10337B424 for ; Mon, 11 Sep 2000 12:50:31 -0700 (PDT) Received: from DarkSide ([207.23.161.75]) by enterprise.sd73.bc.ca (8.9.3/8.9.3) with ESMTP id MAA19559; Tue, 12 Sep 2000 12:51:22 -0700 From: "Freddie Cash" To: "Jason C. Wells" , freebsd-chat@freebsd.org Date: Mon, 11 Sep 2000 12:43:56 -0700 Subject: Re: Anti-pr0n or censored proxy for school district Reply-To: fcash@bigfoot.com Message-ID: <39BCD38C.6471.101F1013@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can you folks help me search out a "content control" mechanism for a > school computer lab? > I was considering simple filters. The problem is collecting a rule set. > I was hoping to avoid a commerical client side solution like net-nanny. > A choke point solution would be better. > I am inclined to think that such a thing is a hopless endeavour. Have > any of you had to do this? What were the results? The school district here, unfortunately, uses IBM's NetVista server running on NT4 to provide proxying, content control, LAN-mail, and the like. Works ok, but it requires lots of HP on the backend, and the newer versions require a fair bit of HP on the client-side now too. Since we're in the process of putting in new FreeBSD-based firewalls, I am attempting to come up with a plan to move away from NetVista and more towards an ipfw-type solution. If I come up with any great solutions, I'll pass them on (or vice versa, I hope). Freddie Cash fcash@bigfoot.com ----------------- Windows 98: noun Updated 32-bit extensions to a 16-bit graphical shell for an 8-bit operating system, originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand 1-bit of competition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message