[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4013 [Tor Client]: Tor 0.2.3.x client can't use 0.2.2.x bridge
#4013: Tor 0.2.3.x client can't use 0.2.2.x bridge
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: major | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by dcf):
Replying to [ticket:4013 arma]:
> My 0.2.3.3-alpha client, when configured to use a bridge, asks the
bridge for /tor/status-vote/current/consensus-microdesc.z. But 0.2.2.x
bridges don't know how to answer this question (they return a 404), so my
client can't bootstrap from them.
I saw this on my 0.2.2.34 bridge with a 0.2.3.7-alpha client. It was the
reason for c1f7a98d (UseMicrodescriptors 0) in flashproxy.git.
I want to add that just upgrading the bridge to 0.2.3 didn't seem to cause
it to start serving microdescriptors. (I continued to get 404s.) On CentOS
5, I changed from the centos5 to the centos5-experimental repository and
did a yum upgrade, which installed 0.2.3.6-alpha. But the bridge reported
{{{
Nov 15 16:50:59.000 [warn] Please upgrade! This version of Tor
(0.2.3.6-alpha) is not recommended, according to the directory
authorities. R
ecommended versions are: 0.2.1.31,0.2.2.34,0.2.3.7-alpha
Nov 15 16:50:59.000 [notice] Reloaded microdescriptor cache. Found 0
descriptors.
}}}
And the client continued to say.
{{{
Nov 15 14:10:09.000 [warn] Received http status code 404 ("Not found")
from server 'scrubbed' while fetching consensus directory.
}}}
I deleted the files {{{/var/lib/tor/{cached-certs,cached-consensus,cached-
descriptors,cached-descriptors.new,lock,state} }}}. {{{cached-microdesc-
consensus}}} and {{{cached-microdescs.new}}} didn't exist. I restarted the
bridge and the deleted files reappeared along with {{{cached-microdesc-
consensus}}} and {{{cached-microdescs.new}}}. The bridge log said
{{{
Nov 15 17:12:02.000 [notice] Reloaded microdescriptor cache. Found 0
descriptors.
}}}
After that the client was able to connect. Restarting the bridge once more
says
{{{
Nov 15 17:35:49.000 [notice] Reloaded microdescriptor cache. Found 2449
descriptors.
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4013#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs