Posted by: Anonymous Coward
on July 09, 2006 07:03 AM
I had the same problem setting up DG on a dedicated firewall/filter box. DG would hang on startup and spit the error about connecting to parent proxy. The parent proxy is, of course, squid (if you're using squid). Squid is listening (by default) on port 3128. It makes sense that if DG cannot get a tcp connection with squid on port 3128, it will spit this error and quit.
Some ideas as to why this would happen:
1. Squid hasn't started.
#ps aux | grep squid
2. Either squid or DG is misconfigured (DG is talking to or squid is listening to some other port).
In my case, the problem was that my iptables firewall was not allowing the connection. When I made a rule allowing this particular connection from 127.0.0.1 to 127.0.0.1 with --dport 3128, DG started up happily.
Learn about Linux
Download Linux
Get Linux help
Re:Followed proceedure and nothing works
Posted by: Anonymous Coward on July 09, 2006 07:03 AMSome ideas as to why this would happen:
1. Squid hasn't started.
#ps aux | grep squid
2. Either squid or DG is misconfigured (DG is talking to or squid is listening to some other port).
#nano<nobr> <wbr></nobr>/etc/dansguardian/dansguardian.conf
#nano<nobr> <wbr></nobr>/etc/squid/squid.conf
3. Your firewall is not allowing the connection.
In my case, the problem was that my iptables firewall was not allowing the connection. When I made a rule allowing this particular connection from 127.0.0.1 to 127.0.0.1 with --dport 3128, DG started up happily.
#