[tor-bugs] #6341 [Tor Relay]: connection_or_flush_from_first_active_circuit() does wrong thing when ewma_enabled

[Tor Bug Tracker & Wiki]

#6341: connection_or_flush_from_first_active_circuit() does wrong thing when
ewma_enabled
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  needs_review      
 Priority:  normal     |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:                    
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by robgjansen):

 Replying to [comment:42 arma]:
 > Looks like you're falling victim to bug #6507 (to be fixed in
 0.2.4.1-alpha) -- it interprets an explicit "DirPort 0" as the same as
 "DirPort is enabled". Same with "ORPort 0" I believe. It was introduced in
 0.2.3.3-alpha.
 >
 > Fix is either to upgrade to git master, or stop writing "FooPort 0" in
 your torrcs.

 OK. I wonder if "ClientOnly 1" has precedence since it follows the
 "DirPort 0" and "ORPort 0"?

 Replying to [comment:42 arma]:
 > Wait, is that client torrc for webclient5? It has FetchDirInfoEarly 1 in
 it. If not, can I have the torrc files that go with webclient5 and
 nonexit11? :)

 Yes, client.torrc is used by webclient5 and relay.torrc is used by
 nonexit11. Are you implying that "FetchDirInfoEarly 1" is only for dir
 mirrors? That wasn't clear from  your comment above:[comment:34 arma]:

 > Set "FetchDirInfoEarly 1" in the torrc for each Tor that should fetch
 that way.

 I thought this meant the clients would try to fetch whatever info they
 needed earlier. Are you telling me I should take these lines back out for
 regular clients?

 Replying to [comment:44 arma]:
 > Ok, the problem with nonexit11 is that it failed repeatedly to get a key
 certificate for the authority. Search the info-level log for "certificate
 ":
 [...]
 > I wonder why the requests kept timing out.

 Not sure. I checked my logs, and this was the only node in the entire
 experiment that had problems. I also checked a few other experiments and
 didn't notice those warnings.

 Also, it looks like my cert is not yet expired:
 {{{
 dir-key-certificate-version 3
 fingerprint 919CAD4BB055CE7EC5169F19BCA731F3D60EFB19
 dir-key-published 2011-06-20 16:31:50
 dir-key-expires 2013-06-20 16:31:50
 dir-identity-key
 [...]
 }}}

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6341#comment:45>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online