[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #2001 [Tor Relay]: Reachability test for ORPort doesn't complete with --enable-bufferevents set

#2001: Reachability test for ORPort doesn't complete with --enable-bufferevents
set
-----------------------+----------------------------------------------------
 Reporter:  Sebastian  |       Owner:  nickm   
     Type:  defect     |      Status:  accepted
 Priority:  normal     |   Milestone:          
Component:  Tor Relay  |     Version:          
 Keywords:             |      Parent:          
-----------------------+----------------------------------------------------

Comment(by nickm):

 {{{
 03:46 < Sebastian> So here's my first test, running a private network with
                    relays and authorities configured with
                    --enable-bufferevents, and a client that runs without.
 Both
                    using current master HEAD.
 03:46 < Sebastian> client debug log available here:
                    http://sebastianhahn.net/tor/clientdebug.log, relay
 debug
                    here: http://sebastianhahn.net/tor/relaydebug.log
 03:47 < Sebastian> I used StrictNodes and EntryNodes to make sure this was
 the
                    node that would be used.
 03:47 < Sebastian> 127.0.0.1:5001 is where the relay runs.
 03:50 < Sebastian> It does indeed look like the client fails to
 renegotiate.
 03:51 < Sebastian> nickm: trying your suggestion of old openssl now
 03:52 < Sebastian> nickm: if you look at the relay log, there are weird
 debug
                    log lines too, though. Looks like the bufferevents-
 enabled
                    network itself has issues
 }}}

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2001#comment:12>
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