[tor-bugs] #33519 [Circumvention/Snowflake]: Support multiple simultaneous SOCKS connections

[Tor Bug Tracker & Wiki]

#33519: Support multiple simultaneous SOCKS connections
-------------------------------------+------------------------
 Reporter:  dcf                      |          Owner:  (none)
     Type:  defect                   |         Status:  new
 Priority:  Medium                   |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:  turbotunnel              |  Actual Points:
Parent ID:  #19001                   |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+------------------------

Comment (by arma):

 Replying to [comment:6 dcf]:
 >  * https://people.torproject.org/~dcf/pt-bundle/tor-browser-snowflake-
 turbotunnel-quic-9.5a8-20200319/

 Good stuff. I've been using this build for the past few days, and it's
 still working. I tried to trip it up a little bit and it recovered after a
 while. So far so good. I'll plan to challenge it more, but first:

 A debugging aid that would be helpful for me, which I realized while
 staring at all these lines:
 {{{
 2020/03/23 08:12:40 Traffic Bytes (in|out): 40 | 0 -- (1 OnMessages, 0
 Sends)
 2020/03/23 08:12:42 Traffic Bytes (in|out): 0 | 575 -- (0 OnMessages, 1
 Sends)
 }}}
 If these log lines could tell me which outgoing connection (aka which
 incoming socks connection) these messages were for (even just saying a
 SocksId number or something), then when I'm watching to see how it
 recovers, it will be easier to tell when snowflake is handling messages
 for the *old* connection, vs when it is using the new connection.

 I think of this because when I failed my outgoing internet for a while and
 then brought it back, and then Tor did the
 {{{
 Mar 20 09:19:49.331 [notice] Our circuit 3155147085 (id: 27) failed to get
 a response from the first hop (0.0.3.0:1). I'm going to try to rotate to a
 better connection.
 }}}
 reaction, I got the impression that a lot of snowflake's alleged sending
 and receiving had to do with the old connection for a good while after Tor
 had given up on that conn. (I was loading a cnn.com page, and snowflake
 sent and received several megabytes and my page still hadn't loaded yet. I
 began to question whether the bytes I was getting were even for the page I
 was loading.)

 It is also definitely possible that I am misunderstanding what's going on,
 and the quic messages at that level are e.g. the aggregate for all
 currently handled connections. If that's the case maybe I want a breakdown
 of how many of them are for which connection.

 Thanks!

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