Summary: | Strange dansguardian behaviour: it works only through google | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | andrea ferraris <andrea_ferraris> |
Component: | [OLD] Server | Assignee: | Gentoo Network Proxy Developers (OBSOLETE) <net-proxy+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
andrea ferraris
2005-04-04 04:41:27 UTC
I know that maybe I'd like to try with the oops mailing lists (I did with the englih one) and mantainers, but I'm not really fluent in russian ;-) first of all, I am not an oops user - I maintain it only because no one else offered to do it. quick hints: - check permissions on /var/lib/oops and /var/cache/oops - use tcpdump/ethereal to see if the request is carried out by the oops server if you have any suggestions/improvements/fixups regarding this ebuild, please don't hesitate to post 'em here. Sincerely thx for your support. I'll try to help to solve this issue and to find more info before saying that I loose. In any case I think that's inappropriate that such package, www-proxy/oops-1.5.23 is marked as stable, because there are no evidence that any Gentoo user uses it (nobody in forums, neither citations) and I think that a piece of software that is not used, can't be marked as stable, because that's misleading. If I'm wrong, let me know. If I'm right, please, mark it at least as masked if not hard masked. I've marked stable because the old stable version was broken. Unfortunately we need to make compromises - gentooers expects from stable ebuilds to be at least compilable. Anyway, given the oldness of the last release, it should be stable as a mountain :) Do you suggest to downgrade my Gentoo to version 1.0, with kernel 2.0 or 2.2? ;-) Once upon a time there was an oops www-proxy server stable on Linux (also if it seems that was really better on Solaris with its threads), once upon a time. Now, if I'm the only Gentoo oops user and if I have trouble with it, I think that maybe could be better to mark oops on x86 as testing (~x86). In my last message I was wrong when I wrote "masked or hard masked", I have had been say "testing or masked". The problem is that I have problems not only with the russian, but also with english. Now (local time 23:40) I can't try, because I don't have the server here. Tomorrow will be a better day. I would mark it as testing/masked if I have some hard evidence that the basic functionality is broken. Until now I failed in this quest. I've tested the default oops installation accessing www.google.com, www.comune.cossato.bi.it and many other urls without a single positive results (read as failed to reproduce). This reply is posted using oops as proxy! IT WORKS!!!! IT WORKS!!!! It was enough to install on GeNToo ;-) I started from the default oops installation. It is, I dropped my config file and used one only with essential and minimal modifications to work (try to work), as pointed out in the few and thin docs. The issue is the same (really a bit worse, because I saw that from my client with Firefox 1.0.2 on WXPSP1 I can get replies from many sites, instead with IE6 on WXPSP2 I can't go anywere). The directories and files have the right permissions, it is they are writable by squid and oops runs a squid user. I looked at packets with tethereal and there are some strange things. Essentially my request packets arrive from my PC to the eth0 of the server, then there are (ACK), (ACK, SYN), (ACK), but there are no requests from oops in internet. Tomorrow I'll continue, because now I realized that I have had to monitor also the loopback (127.0.0.1), because dansguardian ask oops there at port 8080. Or maybe I can enlarge the network at which oops hear from 127.0.0.0/30 to include also the PCs of my private network to test if they can use oops on 8080 without pass through dansguardian and without trouble. why not keeping simple? take dansguardian out of the equation... Before reading your right hint, due the disperation, I did it. I configured oops to listen on port 8080 to all requests from my intranets (192.168/16), I configured IE on one of my clients to go to such port of the proxy server and, miracle, it works. Don't close the bug, because before it would be better to understand if it's dansguardian's or oops's fault (dansguardian+squid work fine) and, for me, oops alone, is almost useless because I need to deny access to a lot of external sites and dansguardian is essential in such task. Do you know if there are some other filtering program in Gentoo that can work with oops? In dansguardian docs you could read that it should work (not tested) also with oops, instead, b.e., in squidguard docs I couldn't find something like that. sorry but I don't know how to help you. have you considered the posibility that maybe dansguardian is the program which filters your requests? Thx. Of course, I'll work on that, it is on the dansguardian configuration. Maybe some parameters that dont't bother squid are annoying for oops. Sorry if I didn't let you know more, but the problem is that I can work on this host only from monday to wednsday, so next week I hope to have better news. try to monitor communication between dansguardian and oops using ethereal this issue is either a misconfiguration or dansguardian's problem. Sorry for the delay. I checked the dansguardian configuratione and it seems OK. The oops cfg seems OK too, because if I use oops directly it works. In the next days I'll try to see what happens between the two with ethereal. any news? btw, a new version of oops is available in portage. Yes. Now also dansguardian+squid have problems with WindowsXP clients's windowsupdate. The true problem is that I work there 18 hours a week and I have to do help desk to 80 users and in the last weeks I got 20 news PC to install and yesterday also a new server. So I hope to do something but I can't guarantee when. it's official then...this is dansguardian's problem. could it be that it has problems with persistent HTTP connections? try it with a browser that could disable those. also, you should try disabling HTTP 1.1 protocol in browser's settings. any progress on this one? I hate to see bugs just lying there for ages. this should be closed with one resolution or the other. Sorry me, you're right. I thought that was closed. You could close it because I had some other weird problems with dansguardian and squid, that I solved dirty and quickly reinstalling the software, but I hadn't the time to test further with oops and I'll don't have it in the next weeks, so if I have any more trouble I'll open a new bug. Thanks. bug closed |