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

[Tor Bug Tracker & Wiki]

#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):

 Yes! I can confirm that the clients never logs the message "%d: end cell
 (%s) for stream %d. Removing stream." in this case.  So for whatever
 reason, either no END cell is generated, or it isn't delivered to the
 client, or the client doesn't notice it.  I am guessing that it is the
 former, based on how this appears in my testing net but not when using a
 client with the public net.

 --

 Also, it seems that when we re-create a new bufferevent_openssl object
 callback, we don't properly set its inbuf/outbuf callbacks to inform us
 when stuff is successfully flushed, so we never update lastwritten on an
 OR connection.

 Good thing _that_ one didn't make it into production!  Fixed it in 5710d99

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