warning message question
Saturday morning, I got the following message. Jul 25 09:33:57.004 [warn] Received http status code 502 (Proxy Error) from server '80.190.246.100:80' while fetching consensus directory. Can anyone explain the situation(s) that can result in such a message? Thanks in advance! Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * **
Re: warning message question
On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote: Saturday morning, I got the following message. Jul 25 09:33:57.004 [warn] Received http status code 502 (Proxy Error) from server '80.190.246.100:80' while fetching consensus directory. Can anyone explain the situation(s) that can result in such a message? 80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities. So your relay was trying to get an updated version of the v3 consensus from gabelmoo. It looks like the way gabelmoo is listening on port 80 is by proxypassing it through apache. You can read more about that approach in this poorly organized faq entry: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients and at that particular moment, for some reason apache decided that sending back a 502 proxy error was better than passing your request on. For example, I bet this could happen if the gabelmoo relay was down at the time. --Roger
Re: warning message question
Scott Bennett wrote: Saturday morning, I got the following message. Jul 25 09:33:57.004 [warn] Received http status code 502 (Proxy Error) from server '80.190.246.100:80' while fetching consensus directory. I've got similar messages too, always in conjunction with 'Got a bad signature on a networkstatus vote' (Tor v0.2.1.17): Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.918 [warn] Got a bad signature on a networkstatus vote Jul 25 01:33:13.918 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no signature, 4 required Jul 25 01:33:13.918 [warn] Not enough good signatures on networkstatus consensus Jul 25 01:33:13.918 [warn] Unable to load consensus directory downloaded from server '137.56.75.117:11375'. I'll try again soon. Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.792 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.792 [warn] Got a bad signature on a networkstatus vote Jul 25 01:34:16.792 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no signature, 4 required Jul 25 01:34:16.792 [warn] Not enough good signatures on networkstatus consensus Jul 25 01:34:16.792 [warn] Unable to load consensus directory downloaded from server '216.146.46.30:9001'. I'll try again soon. Jul 25 01:44:24.800 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.800 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote Jul 25 01:44:24.801 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no signature, 4 required Jul 25 01:44:24.801 [warn] Not enough good signatures on networkstatus consensus Jul 25 01:44:24.801 [warn] Unable to load consensus directory downloaded from server '91.143.93.213:9002'. I'll try again soon. Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote Jul 25 02:18:58.903 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no signature, 4 required Jul 25 02:18:58.903 [warn] Not enough good signatures on networkstatus consensus Jul 25 02:18:58.904 [warn] Unable to load consensus directory downloaded from server '88.159.81.251:110'. I'll try again soon.
Torbutton for Mozilla Thunderbird
How can I get the Torbutton for the Mozilla Thunderbird? I used it under Windows (but very old version, about 1,5 - 2 years) but I cannot find it now for my new Linux system.
Re: warning message question
On Sun, 26 Jul 2009 03:52:38 -0400 Roger Dingledine a...@mit.edu wrote: On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote: Saturday morning, I got the following message. Jul 25 09:33:57.004 [warn] Received http status code 502 (Proxy Error) from server '80.190.246.100:80' while fetching consensus directory. Can anyone explain the situation(s) that can result in such a message? 80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities. So your relay was trying to get an updated version of the v3 consensus from gabelmoo. It looks like the way gabelmoo is listening on port 80 is by proxypassing it through apache. You can read more about that approach in this poorly organized faq entry: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients Eeeeuww! That's hideous. Why would someone configure a mess like that when they could just as easily use an RDR rule? and at that particular moment, for some reason apache decided that sending back a 502 proxy error was better than passing your request on. How would a typical user know that the proxy in question was an apache server on the other end? Ugh. For example, I bet this could happen if the gabelmoo relay was down at the time. Bummer. Thanks for the explanation, Roger. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * **
Re: warning message question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/26/2009 09:52 AM, Roger Dingledine wrote: On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote: Saturday morning, I got the following message. Jul 25 09:33:57.004 [warn] Received http status code 502 (Proxy Error) from server '80.190.246.100:80' while fetching consensus directory. Can anyone explain the situation(s) that can result in such a message? 80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities. So your relay was trying to get an updated version of the v3 consensus from gabelmoo. It looks like the way gabelmoo is listening on port 80 is by proxypassing it through apache. You can read more about that approach in this poorly organized faq entry: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients and at that particular moment, for some reason apache decided that sending back a 502 proxy error was better than passing your request on. FYI, gabelmoo is passing directory requests through Apache for two reasons: First, I have been using Apache as a first attempt to measure how long clients take to download network statuses in order to derive how fast clients are; this functionality is now in 0.2.2.0-alpha-dev, so that Apache is not required anymore for this: http://archives.seul.org/or/cvs/Jul-2009/msg00244.html Second, I'm using port 80 both for serving the Tor directory and for serving files for performance measurements: http://freehaven.net/~karsten/volatile/torperf-2009-07-01.pdf For example, I bet this could happen if the gabelmoo relay was down at the time. It's back online now. - --Karsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpsMc8ACgkQ0M+WPffBEmWTTQCdFth19N02fKpJc7vAJE+pSMOW +3sAoLGWwxPlkCXmSLD/BHldeeqGdpTU =FvlG -END PGP SIGNATURE-
What is the new records in my new tor?
Yesterday I installed new version the Tor for Debian Lenny. Now I see the log of the Tor and find there the next: Jul 26 19:44:44.388 [notice] Tor 0.2.1.18 opening log file. Jul 26 19:44:44.466 [notice] Parsing GEOIP file. Jul 26 19:44:47.070 [notice] We now have enough directory information to build circuits. Jul 26 19:44:47.070 [notice] Bootstrapped 80%: Connecting to the Tor network. Jul 26 19:44:47.143 [notice] Bootstrapped 85%: Finishing handshake with first hop. Jul 26 19:44:50.060 [notice] Bootstrapped 90%: Establishing a Tor circuit. There were no such records in the logs of the old version of the Tor (excepting the first of courser :-) ) What do they mean?
Re: Best practice for DNS through tor
Jim McClanahan wrote: 3) I tried redirection with iptables on the local host but I can't get that to work --- I'm not sure its possible. ... I would think that should work. (I've done similar DNATing -- with DNS even! :-) Something like: iptables -t nat -A OUTPUT -p udp --dport 53 \ -j DNAT --to-destination $router_ip:5300 Thanks that did it. I was using PREROUTING which is for packets routed through the box, not packets originating from the box. I've been caught by this before but it just didn't click. -- Anthony G. Basile, Ph.D. Chair of Information Technology D'Youville College Buffalo, NY 14201 USA (716) 829-8197 signature.asc Description: OpenPGP digital signature
RE: Tor packages for OS X powerpc and 10.3.9 uploaded
Thank you Andrew and the anonymous donor! I regret to report that this still crashes on 10.3.9 without 'export EVENT_NOKQUEUE=1' in the starting script. I didn't have to wait long today; just half an hour. GD Date: Fri, 24 Jul 2009 01:38:00 -0400 From: and...@torproject.org To: or-talk@freehaven.net Subject: Tor packages for OS X powerpc and 10.3.9 uploaded Thanks to an anonymous donor for the working powerpc hardware, I was able to make packages on OS X 10.3.9 (Panther) this evening. They are available in the usual places, such as https://torproject.org/download Thanks for your patience. -- Andrew Lewman The Tor Project pgp 0x31B0974B Website: https://torproject.org/ Blog: https://blog.torproject.org/ Identica/Twitter: torproject _ Windows Live™ Hotmail®: Celebrate the moment with your favorite sports pics. Check it out. http://www.windowslive.com/Online/Hotmail/Campaign/QuickAdd?ocid=TXT_TAGLM_WL_QA_HM_sports_photos_072009cat=sports
Re: Tor packages for OS X powerpc and 10.3.9 uploaded
On 07/26/2009 02:07 PM, downie - wrote: Thank you Andrew and the anonymous donor! I regret to report that this still crashes on 10.3.9 without 'export EVENT_NOKQUEUE=1' in the starting script. I didn't have to wait long today; just half an hour. Do you get a crashlog you could upload to bugs.torproject.org? I ran a client for a day without an issue. I had curl pull a file over tor repeatedly without issue. -- Andrew Lewman The Tor Project pgp 0x31B0974B Website: https://torproject.org/ Blog: https://blog.torproject.org/ Identica/Twitter: torproject
RE: Tor packages for OS X powerpc and 10.3.9 uploaded
Date: Sun, 26 Jul 2009 20:39:36 -0400 From: and...@torproject.org To: or-talk@freehaven.net Subject: Re: Tor packages for OS X powerpc and 10.3.9 uploaded Do you get a crashlog you could upload to bugs.torproject.org? I ran a client for a day without an issue. I had curl pull a file over tor repeatedly without issue. yes, it seems to be a relay issue only. I have an entry in panic.log which I will add to Flyspray. GD _ Windows Live™ Hotmail®: Search, add, and share the web’s latest sports videos. Check it out. http://www.windowslive.com/Online/Hotmail/Campaign/QuickAdd?ocid=TXT_TAGLM_WL_QA_HM_sports_videos_072009cat=sports
