Re: HTTP response is "Connection: close"
Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > > Like Andrew, I assume the real problem is a malfunctioning > > intercepting proxy on the exit node, so there's little you can do > > about it. > > I would rather blame it on a tor server that crashes or drops the > connection. It's my impression that the OP can detect that and throws a socks error. If, however, there's a broken intercepting proxy it would explain why the OP doesn't notice. > WWIW, if Polipo can detect such a situation (either because we haven't > reached the Content-Length the server declared, or because there was > an unterminated chunk), it will refetch the object. The responses in question are completely empty, there's not a single HTTP header and of course the nothingness isn't chunked either. I get the impression that Polipo forwards them as empty page and puts some headers on top. At least I'm currently running Privoxy->Polipo->Tor as default proxy chain and from time to time I get empty pages that pass Privoxy's trivial no-data check. Refreshing with CTRL+F5 usually results in the real page. I neither verified that it's the same problem, nor did I check how the requests look like before they reach Polipo or after they are processed by it, but the symptoms would fit. Fabian signature.asc Description: PGP signature
Re: stuff making it around the exit policy?
coderman wrote: > On 6/25/07, Whysyn <[EMAIL PROTECTED]> wrote: >> In troubleshooting another problem on my server this morning, I found >> what is apparently traffic that circumvents the ExitPolicy... >> >> netstat output: >> tcp0 0 66.219.161.166:42132131.215.166.198:6882 >> ESTABLISHED 26815/tor > > hi Whysyn, > > this is a connection to another router, not an exit: > router AscendedDaniel 131.215.166.198 6882 ... > > best regards, > Thanks, I always miss the obvious. ~Whysyn
Re: Tor Traffic Problems
coderman schrieb: > hi Andrew, > > please note that 150KBytes/sec == 1.2Mbits/sec. > > if you convert your bandwidth values accordingly you should see better > behavior. > > best regards, I guess that mystery is solved... ;) Thanks a lot.
Re: stuff making it around the exit policy?
On 6/25/07, Whysyn <[EMAIL PROTECTED]> wrote: In troubleshooting another problem on my server this morning, I found what is apparently traffic that circumvents the ExitPolicy... netstat output: tcp0 0 66.219.161.166:42132131.215.166.198:6882 ESTABLISHED 26815/tor hi Whysyn, this is a connection to another router, not an exit: router AscendedDaniel 131.215.166.198 6882 ... best regards,
Re: Tor Traffic Problems
On 6/25/07, Andrew <[EMAIL PROTECTED]> wrote: ... My torrc is as follows: BandwidthRate 110 KB BandwidthBurst 150 KB ... [For those who don't like images: 6h-Average of ingoing traffic 275KB/s, outgoing 384KB/s, maximum of 900KB/s and 700KB/s] hi Andrew, please note that 150KBytes/sec == 1.2Mbits/sec. if you convert your bandwidth values accordingly you should see better behavior. best regards,
stuff making it around the exit policy?
In troubleshooting another problem on my server this morning, I found what is apparently traffic that circumvents the ExitPolicy... netstat output: tcp0 0 66.219.161.166:42132131.215.166.198:6882 ESTABLISHED 26815/tor 66.219.161.166 is a secondary address on my box that does nothing but tor. What gives? Here is a copy of my ExitPolicy from torrc: ExitPolicy reject 0.0.0.0/255.0.0.0:* ExitPolicy reject 169.254.0.0/255.255.0.0:* ExitPolicy reject 127.0.0.0/255.0.0.0:* ExitPolicy reject 192.168.0.0/255.255.0.0:* ExitPolicy reject 10.0.0.0/255.0.0.0:* ExitPolicy reject 172.16.0.0/255.240.0.0:* ExitPolicy accept *:53 # dns ExitPolicy accept *:80 # http ExitPolicy accept *:110 # pop3 ExitPolicy accept *:143 # imap ExitPolicy accept *:443 # https ExitPolicy accept *:993 # imap w/ ssl ExitPolicy accept *:995 # pop3 w/ssl ExitPolicy accept *:1863 # msn im ExitPolicy accept *:5050 # yahoo im ExitPolicy accept *:5101 # yahoo im ExitPolicy accept *:5060 # msn im ExitPolicy accept *:5190 # aolim ExitPolicy reject *:* Thanks guys! ~Whysyn
Tor Traffic Problems
Hi everyone, just as Michael last week, I'm having huge problems with the tor bandwidth usage. It just won't stick to the limits. Background info: I'm running tor 0.1.2.14 on SUSE 9.3; smooth and stable so far. To test it, I turned it up to the default speed last night, reaching the 3 MBit marks in each direction without producing any warnings or errors. My torrc is as follows: BandwidthRate 110 KB BandwidthBurst 150 KB ExitPolicy accept *:80,accept *:443,accept *:6660-6667,reject *:* ExitPolicyRejectPrivate 1 My traffic monitor tells me that traffic is not even close to these values: http://kleinhirn.org/monitor.png & http://kleinhirn.org/monitor2.png [For those who don't like images: 6h-Average of ingoing traffic 275KB/s, outgoing 384KB/s, maximum of 900KB/s and 700KB/s] With virtually all of the traffic being generated by tor (restarted tor at 11.14 this morning according to the log; before there was almost no traffic at all). Now, the question is: what did I do wrong..? Of course I could just use the Accounting options (which worked fine for me last night), but that would disable the directory mirror. Plus, I'd like to know where the mistake is and not just build a work-around ;) I appreciate your help Andrew -- cerebellum - tor 0.1.2.14 on SUSE 9.3
Polipo 1.0.1 Windows binary
A Windows binary for Polipo 1.0.1 is now available on http://www.pps.jussieu.fr/~jch/software/files/polipo/polipo-win32-1.0.1.zip http://www.pps.jussieu.fr/~jch/software/files/polipo/polipo-win32-1.0.1.zip.asc This binary has never seen a Windows machine, so feedback would be appreciated. Juliusz pgpfK7afrY3pG.pgp Description: PGP signature
ANNOUNCE: Polipo 1.0.1
Dear all, I'm pleased to announce the release of Polipo-1.0.1, which you will find on http://www.pps.jussieu.fr/~jch/software/files/polipo/polipo-1.0.1.tar.gz http://www.pps.jussieu.fr/~jch/software/files/polipo/polipo-1.0.1.tar.gz.asc For more information about Polipo, please see http://www.pps.jussieu.fr/~jch/software/polipo/ This version tweaks Polipo's default behaviour with respect to sites hidden behind an HTTP/1.0 front-end proxy (such as Wikipedia) to make it slightly more aggressive. It also adds a number of completely pointless options that were requested by the tor crowd. It fixes a possible crash that happened when using some of the more exotic cache-control options. Finally, it fixes a serious descriptor leak under Windows. Upgrading is not necessary if you're under Unix or using the Cygwin port, but strongly recommended if you're using the native Windows binary. Juliusz 25 June 2007: Polipo 1.0.1: Made Polipo slightly more aggressive when speaking to HTTP/1.0 servers (thanks to Fabian Keil for noticing that). Fixed a crash that would happen when a client used Cache-Control: only-if-cached, and the object was not in cache. (Reported by F. Zappa, A. Patala and V. Ghosal.) Fixed a descriptor leak when running under Windows. Made Polipo optionally drop connections after servicing a number of connections (maxConnectionAge and maxConnectionRequests). pgp2lb9hgkCpz.pgp Description: PGP signature
