Date: Wed, 12 Dec 2007 13:10:01 +0100 From: "Heiko Wundram (Beenic)" <wundram@beenic.net> To: freebsd-questions@freebsd.org Cc: Nikos Vassiliadis <nvass@teledomenet.gr>, Alex Zbyslaw <xfb52@dial.pipex.com> Subject: Re: performance impact of large /etc/hosts files Message-ID: <200712121310.01617.wundram@beenic.net> In-Reply-To: <475FCD8A.5090903@dial.pipex.com> References: <475E0190.7030909@pacific.net.sg> <200712120920.46626.nvass@teledomenet.gr> <475FCD8A.5090903@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mittwoch, 12. Dezember 2007 13:01:14 schrieb Alex Zbyslaw: > <snip explanation> > I don't see how a firewall is appropriate for this (hosts.allow, > likewise). The point of the exercise is to never even contact the ad host. Transparent proxy with squid on the firewall? There's even plugins to manage exactly this kind of ad-blocking with squid; although I don't currently know the extension's name. This is pretty much going to be your only option to do this in a centralized fashion. -- Heiko Wundram Product & Application Development
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200712121310.01617.wundram>