You are not logged in.

#1 2010-03-15 09:50:32

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Monitoring traffic between dansguardian and tinyproxy [SOLVED]

I'm trying to find out why firefox -> dansguardian -> tinyproxy doesn't work for some web sites, one of them being www.archlinux.org. The error message is "Content Encoding Error". Interestingly some quite similar setups do work, so this probably isn't a stupid problem:

google.com -> firefox -> dansguardian -> tinyproxy
* -> dillo -> dansguardian -> tinyproxy
* -> * -> dansguardian -> {squid,polipo}
* -> * -> tinyproxy

All of the above work, with * meaning all sites / browsers.

I've tried to use wireshark to monitor the traffic between dansguardian and the proxy server, but no luck: if traffic goes via dansguardian, I can only see traffic on its input port (8080), but not on the listening port of the proxy server (3128). If traffic goes around dansguarding directly to the proxy server, then I can see the proxy server's listening port (3128). But then I don't see the bug, because everything works.

I'm not an expert in that area, so I may be missing something basic. Any ideas / suggestions? Is there another application that I can use to monitor the communication between dansguardian and its proxy server?

Last edited by grey (2010-03-17 15:01:43)


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#2 2010-03-17 05:31:36

Sin.citadel
Member
Registered: 2008-01-22
Posts: 267

Re: Monitoring traffic between dansguardian and tinyproxy [SOLVED]

have you checked /var/log/everything.log for any logs by squid and/or any other proxy. also, dansguardian may be sending its requests to the proxy server using loopback interface, try sniffing that and see if it picks up anything.

Offline

#3 2010-03-17 15:01:30

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: Monitoring traffic between dansguardian and tinyproxy [SOLVED]

@Sin.citadel: I've checked the logs. All these programs have their own log file, they indicate that there is a problem, but they aren't detailed enough. You are right that dansguardian is using lo - that's what I was trying to monitor.
However, it turns out that I hadn't looked closely enough: the traffic is actually there in the wireshark output, for both the browser port and the proxy port. It didn't help me to understand the original problem, but monitoring the traffic actually works.


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

Board footer

Powered by FluxBB