Dansguardian and Squid

yeeha! · 08-19-2006, 04:04 AM

I have squid running on my proxy. I tried to change it to listen on port 4112. Well, it works.

Now, my Dansguardian won't work. I'd changed the filter port to 8080 and proxy port to 4112. The problem is, where it goes wrong? Is it because the firewall setting?

Tnax in advanced.

win32sux · 08-19-2006, 10:22 PM

Quote:

Originally Posted by yeeha!

I have squid running on my proxy. I tried to change it to listen on port 4112. Well, it works.

Now, my Dansguardian won't work. I'd changed the filter port to 8080 and proxy port to 4112. The problem is, where it goes wrong? Is it because the firewall setting?

Tnax in advanced.

yes, it could be the firewall settings... post the output of these commands (with squid and dansguardian running):

Code:

netstat -an | grep "LISTEN "

Code:

iptables -v -n -L

notice there is a space between LISTEN and the last quotation mark...

yeeha! · 08-20-2006, 09:17 PM

Quote:

Originally Posted by win32sux

yes, it could be the firewall settings... post the output of these commands (with squid and dansguardian running):

Thanks.
I've to change back squid to listen on port 8080 and dansguardian's filter port to 3128 to make DG running. If not, it won't start. So here's how it goes:

Code:

netstat -an | grep "LISTEN "

with this command, I get:

Code:

tcp        0      0 0.0.0.0:32768           0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:32769         0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:6000            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:10000           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:3128            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN

Code:

iptables -v -n -L

and the outpuit of this command is too long to post here. And it takes me several minutes to realize there's no "attach button" here

. Pardon me a n00b from n00bland...

win32sux · 08-20-2006, 09:28 PM

you should be able to make squid and dansguardian run on pretty much any port you want... the typical ports are 3128 for squid and 8080 for dansguardian... squid doesn't need to be told about dansguardian, but dansguardian has a configuration file where you tell it which port squid is listening on - it should say 3128... without seeing your firewall rules, there's no way to say whether it's a firewall issue... if you firewall is logging, then check your syslog...

yeeha! · 08-21-2006, 01:22 AM

Ya, I've changed the DG's config file to the port that squid listening on.(i.e: 4112. That's the port that 'd changed in the squid config). Then I changed the filter port to 8080. With this configuration, DG won't start at all.

How can I attach the output(in a form of file) here as it's rather long to be put in a code tag.
I use Shorewall and had tried to changed the rule with this:

Code:

REDIRECT	loc	4112	tcp	www

but with no luck.