#33336: Trial deployment of Snowflake with Turbo Tunnel -------------------------------------+-------------------------- Reporter: dcf | Owner: dcf Type: task | Status: accepted Priority: Medium | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: turbotunnel | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------+--------------------------
Comment (by arma): Running dcf's https://people.torproject.org/~dcf/pt-bundle/tor-browser- snowflake-turbotunnel-quic-9.5a5-20200223/ tor-browser-linux64-9.5a5_en- US.tar.xz I replaced tor-browser_en-US/Browser/TorBrowser/Tor/tor with the tor binary made from my Tor git branch {{{debug33336}}} and in tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults I commented out dcf's new lines LearnCircuitBuildTimeout, CircuitBuildTimeout, CircuitStreamTimeout, and added these three of my own: {{{ log info file /tmp/tor-info-log logtimegranularity 1 safelogging 0 }}} Then I started my tor browser using snowflake: {{{ [...] Feb 25 14:25:27.557 [notice] Definitely works: recorded success for primary confirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) Feb 25 14:25:27.929 [notice] Bootstrapped 100% (done): Done }}} I browsed for a while. It worked fine. I disabled my wireless on the laptop, and clicked on a few more things. {{{ Feb 25 14:31:01.385 [notice] We tried for 15 seconds to connect to 'www.gstatic.com' using exit $81B75D534F91BFB7C57AB67DA10BCEF622582AE8~hviv104 at 192.42.116.16. Retrying on a new circuit. [...] Feb 25 14:31:25.438 [notice] We tried for 15 seconds to connect to 'pagead2.googlesyndication.com' using exit $578E007E5E4535FBFEF7758D8587B07B4C8C5D06~marylou1 at 89.234.157.254. Retrying on a new circuit. Feb 25 14:31:25.438 [notice] Our circuit 3717720358 (id: 24) 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. Feb 25 14:31:25.438 [notice] Marking guard down: Recorded failure for primary confirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) Feb 25 14:31:26.436 [notice] Delaying directory fetches: No running bridges Feb 25 14:31:27.437 [notice] We tried for 15 seconds to connect to 'px.moatads.com' using exit $578E007E5E4535FBFEF7758D8587B07B4C8C5D06~marylou1 at 89.234.157.254. Retrying on a new circuit. Feb 25 14:31:27.438 [notice] Considering retry for primary confirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) Feb 25 14:31:27.438 [notice] Application request when we haven't received a consensus with exits. Optimistically trying known bridges again. [...] Feb 25 14:33:31.503 [notice] Closing OR conn. Considering blaming guard. Feb 25 14:33:31.503 [notice] Our circuit 0 (id: 30) died before the first hop with no connection Feb 25 14:33:31.504 [notice] Marking guard down: Recorded failure for primary confirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) }}} around here I turned the wifi back on, and clicked on a few more things in tor browser. It thrashed for a while more, with things like {{{ Feb 25 14:35:31.846 [notice] Our circuit 0 (id: 49) died before the first hop wi th no connection Feb 25 14:35:31.846 [notice] Marking guard down: Recorded failure for primary co nfirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC4 0DDCC8824814F80A72) Feb 25 14:35:32.075 [notice] Delaying directory fetches: No running bridges Feb 25 14:35:58.268 [notice] Considering retry for primary confirmed guard $2B28 0B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) Feb 25 14:35:58.268 [notice] Application request when we haven't received a cons ensus with exits. Optimistically trying known bridges again. Feb 25 14:36:24.457 [notice] Closing OR conn. Considering blaming guard. Feb 25 14:36:24.457 [notice] Our circuit 0 (id: 50) died before the first hop wi th no connection Feb 25 14:36:24.457 [notice] Marking guard down: Recorded failure for primary co nfirmed guard $2B280B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC4 0DDCC8824814F80A72) }}} and then came the exciting part: {{{ Feb 25 14:36:24.458 [warn] Pluggable Transport process terminated with status code 512 Feb 25 14:36:25.307 [notice] Delaying directory fetches: No running bridges Feb 25 14:36:44.753 [notice] Considering retry for primary confirmed guard $2B28 0B23E1107BB62ABFC40DDCC8824814F80A72 ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) Feb 25 14:36:44.753 [notice] Application request when we haven't received a cons ensus with exits. Optimistically trying known bridges again. Feb 25 14:36:44.825 [warn] The connection to the SOCKS5 proxy server at 127.0.0.1:45527 just failed. Make sure that the proxy server is up and running. Feb 25 14:36:44.825 [notice] Closing OR conn. Considering blaming guard. }}} My snowflake client is dead? But Tor just keeps on trying to use it, warning quietly to itself every couple of minutes about how the connection to the socks5 proxy server just failed? I will set up logging on the snowflake client side too, and see if I can reproduce. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33336#comment:20> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs