(David, I'm cc-ing you on this since you commented on not receiving a CC previously...if you want to receive updates on a particular bug, directions on subscribing are at http://www.debian.org/Bugs/Developer#subscribe )
I don't know how your setup might have been working "before." If you provide specifics on when it was working the way you expected, when it stopped, and what you changed on your system in between, someone else might be able to help figure it out. Unfortunately I'm not intimately familiar with this package; I only installed it to see if I could reproduce the problems you are having. The steps I listed above got me to an apparently functional filtering setup from a clean testing/squeeze system. You may want to try removing dansguardian and tinyproxy and purging the configuration files, then reinstalling them, just to get a clean slate. The directions I was mostly following are here: http://www.vollmar.ch/dansguardian-e.html ; you can also take a look at http://www.pilpi.net/journal/item-985.php or http://wiki.debian.org/HowTo/dansguardian (if you don't mind switching to squid instead of tinyproxy.) I've seen no indication that DansGuardian is intended to "intercept" the traffic to the proxy or in any way work without having web traffic sent through it, see for example http://dansguardian.org/?page=dgflow . Port 80, not 8080, is the usual (non-proxied) web port, although 8080 is (rarely) used for some sites. If you're having some sites not load, without any block messages, it would be useful to know the URLs so others could verify. The Google blocking may depend somewhat on what language Google is set to. There are some hints on the DansGuardian site for customizing blocklists, see http://dansguardian.org/?page=blacklist and http://dansguardian.org/?page=extras Best of luck getting a configuration that works for you. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
