From owner-freebsd-isp Sat Dec 26 14:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07954 for freebsd-isp-outgoing; Sat, 26 Dec 1998 14:07:42 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07944; Sat, 26 Dec 1998 14:07:38 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id QAA05123; Sat, 26 Dec 1998 16:07:16 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Sat, 26 Dec 1998 16:07:16 -0600 (CST) From: Phillip Salzman To: Gary Palmer cc: Casper , freebsd-isp@FreeBSD.ORG Subject: Re: BESS internet filtering In-Reply-To: <50518.914709562@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The only *real* way to totally filter content is to use `allow' lists, > rather than exclude lists. I personally don't think that content > filtering is the job of the ISP, with or without disclaimers. > I agree entirely. But several customers have requested it, and work we are doing with an upstart ISP called Family Internet Services (http://www.familyinet.net/) has raised the issue. They wish to provide filtering. What we are going to do is go in half with them on the BESS system, pipe all of their traffic through it, and setup certain user accounts to go through it also. Those accounts will be extra ones requested by parents for their children. No other accounts will be filtered in any way. Phillip Salzman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message