Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+--
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by cypherpunks):

 Update: Unfortunately it still happens (used the new domains that dcf made
 in #22782 to get it working),

 {{{
 Apr 21 08:39:23 debian Tor[1274]: Tried for 120 seconds to get a
 connection to [scrubbed]:80. Giving up. (waiting for circuit)
 Apr 21 08:39:23 debian Tor[1274]: Tried for 120 seconds to get a
 connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
 Apr 21 08:39:23 debian Tor[1274]: Tried for 120 seconds to get a
 connection to [scrubbed]:80. Giving up. (waiting for circuit)
 Apr 21 08:39:23 debian Tor[1274]: Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 Apr 21 08:39:25 debian Tor[1274]: Delaying directory fetches: No running
 bridges
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+--
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by cypherpunks):

 * status:  closed => reopened
 * resolution:  not a bug =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 Since #25347 might be related, I'll wait until it's fixed and there's a
 new TB alpha release with it to see if solves the issue.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by cypherpunks):

 * Attachment "newer-snowflake-client-task-manager-test.png" added.


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 Replying to [comment:5 dcf]:
 > I've seen this too, not only with snowflake. I suspect it's actually a
 tor bug. Sometimes a loading tab in Tor Browser will stall, and I'll see
 this message. Then, I open another tab and go to a domain that doesn't
 have an existing circuit, and it will "un-stall" the first tab. It's like
 tor sometimes starts believing that none of its bridges are working, and
 refuses to even try again, until you ask for a new circuit.
 >
 > It may happen more often with snowflake because of #25429 (disconnects
 after 30 s). Some other tor-related tickets are #20379 (fixed in November
 2016) and #24392 (fixed in November 2018). I'm not sure if #24392 is fixed
 in a released Tor Browser yet.

 So I did a methodology to know for sure whether it's due to the switch to
 the newer `snowflake-client` or not (in which case it would primarily be
 an issue with tor, FWIW I'm using 0.3.3.x-a in all of this).

 1. First, I switched everything back to the older `snowflake-client`
 (`sha256sum
 ff94f6ed041263eb4e3bc8c215d9469a3a8cca7957ba4bccea617dc220294a74`),
 including the one in my `/usr/bin`.
 2. I restarted the two instances of `tor` that I had running, and I opened
 the Tor Browser and went to two sites then clicked on New Identity.
 3. I stopped from any activity for 40 minutes.
 4. I went back and first looked at the task manager and saw that the
 receiving/sending rates were varying around `0.9-4KiB/s - 2-5KiB/s` with
 no dips and can go higher than that when snowflake rotates to another
 snowflake proxy (I don't have any other significant application running
 that could affect the network activity). Then, I opened
 check.torproject.org in the Tor Browser, it took a bit of time but it
 eventually worked. I did `apt-get update` (I'm torifying my apt-gets so it
 uses the `debian-tor` service which was setup to use the older `snowflake-
 client`) and it worked as well.

 Afterwards I switched everything back to the newer `snowflake-client`
 (`44ab0a493573b4f95a3b01f7495676cca6cd7ea2ae2afe1b69c4591ae4dbba2a`), and
 I did the same step (2) above.

 1. I stopped from any activity for 30 minutes.
 2. Looking at the task manager one clearly sees that everything stopped
 working, [[Image(newer-snowflake-client-task-manager-test.png)]] And
 looking at wireshark one mostly sees STUN packets with `Binding Request`
 and `Binding Success Response XOR-MAPPED-ADDRESS: ...` Opening the console
 of the Tor Browser one sees `Delaying directory fetches: No running
 bridges` and opening up check.torproject.org eventually times out. Going
 to another site yields another timeout. Same for running `apt-get update`,
 and one sees `Delaying directory fetches: No running bridges` as well in
 the `/var/log/syslog`.

 I hope you can reproduce this so that you can then narrow down the problem
 to a specific commit. (Note that in my testing I had 3 instances of tor
 running in total all of them with snowflake, but the issue may be present
 with just one running it's just that I didn't have time to test)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by dcf):

 Replying to [comment:4 cypherpunks]:
 > I'm definitely noticing that after dozens of minutes of inactivity tor
 eventually hits:
 >
 > {{{
 > Delaying directory fetches: No running bridges
 > Application request when we haven't received a consensus with exits.
 Optimistically trying known bridges again.
 > }}}
 >
 > Restarting the affected program solves the issue. But I'm not sure if
 this is a consequence of the proxy changes that you were mentioning.

 I've seen this too, not only with snowflake. I suspect it's actually a tor
 bug. Sometimes a loading tab in Tor Browser will stall, and I'll see this
 message. Then, I open another tab and go to a domain that doesn't have an
 existing circuit, and it will "un-stall" the first tab. It's like tor
 sometimes starts believing that none of its bridges are working, and
 refuses to even try again, until you ask for a new circuit.

 It may happen more often with snowflake because of #25429 (disconnects
 after 30 s). Some other tor-related tickets are #20379 (fixed in November
 2016) and #24392 (fixed in November 2018). I'm not sure if #24392 is fixed
 in a released Tor Browser yet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 I'm definitely noticing that after dozens of minutes of inactivity tor
 eventually hits:

 {{{
 Delaying directory fetches: No running bridges
 Application request when we haven't received a consensus with exits.
 Optimistically trying known bridges again.
 }}}

 Restarting the affected program solves the issue. But I'm not sure if this
 is a consequence of the proxy changes that you were mentioning.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by cypherpunks):

 * status:  new => closed
 * resolution:   => not a bug


Comment:

 Replying to [comment:2 dcf]:
 > Thanks for this.
 >
 > I tried it, but I wasn't able to reproduce it. On Debian, I used a
 browser from https://people.torproject.org/~dcf/pt-
 bundle/snowflake/20180321-8.0a4-4a5889af2891/ and a command line
 snowflake-client from [https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/log/?id=07291a0136b8a01bd8761a14a51876f08ca0d578
 07291a0136].
 >  1. Started a download of
 
https://mirrors.edge.kernel.org/centos/7.4.1708/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso.
 Was getting about 400 KB/s.
 >  2. In the snowflake/client directory, ran `tor -f torrc SOCKSPort
 1`. It finished bootstrapping and the Browser download was still
 running.
 >  3. Download through the command-line client: `curl -O --proxy
 socks5h://127.0.0.1:1/
 
https://mirrors.edge.kernel.org/centos/7.4.1708/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso`.
 I was getting about 500 KB/s on this download and the browser was still
 about 400 KB/s.
 >
 > Maybe it was a coincidence that one of the clients died when the other
 one started? I'm currently testing some proxy changes from
 comment:63:ticket:21312, and it seems there is still a problem with
 proxies hanging up occasionally. Does it happen for you repeatedly?

 Interesting, I had actually repeated the steps twice at different times (I
 left the download going for quiet some bit at one time, probably 7 min)
 and I always had the same result. I was experiencing repeated shortages
 but I thought that this may have been due to the other snowflake-client
 process that I had running. But the good news is that I can't reproduce it
 now which means you're right :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by dcf):

 Thanks for this.

 I tried it, but I wasn't able to reproduce it. On Debian, I used a browser
 from https://people.torproject.org/~dcf/pt-
 bundle/snowflake/20180321-8.0a4-4a5889af2891/ and a command line
 snowflake-client from [https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/log/?id=07291a0136b8a01bd8761a14a51876f08ca0d578
 07291a0136].
  1. Started a download of
 
https://mirrors.edge.kernel.org/centos/7.4.1708/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso.
 Was getting about 400 KB/s.
  2. In the snowflake/client directory, ran `tor -f torrc SOCKSPort 1`.
 It finished bootstrapping and the Browser download was still running.
  3. Download through the command-line client: `curl -O --proxy
 socks5h://127.0.0.1:1/
 
https://mirrors.edge.kernel.org/centos/7.4.1708/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso`.
 I was getting about 500 KB/s on this download and the browser was still
 about 400 KB/s.

 Maybe it was a coincidence that one of the clients died when the other one
 started? I'm currently testing some proxy changes from
 comment:63:ticket:21312, and it seems there is still a problem with
 proxies hanging up occasionally. Does it happen for you repeatedly?

 Or, there could be some weird interaction, like maybe it only happens when
 both of the clients are using the same proxy instance.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by cypherpunks):

 Some more details: This was tested on Debian. Also the `snowflake-client`
 used for Ricochet is a copy placed in `/usr/bin`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

[Tor Bug Tracker & Wiki]

#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 Steps to reproduce:

 1. Use the fresh testbuilds by dcf `https://people.torproject.org/~dcf/pt-
 bundle/snowflake/20180321-8.0a4-4a5889af2891/`
 2. Start a download
 
`https://mirrors.edge.kernel.org/centos/7.4.1708/isos/x86_64/CentOS-7-x86_64-Everything-1708.iso`
 and watch `about:downloads` or your Task Manager.
 3. Open another instance of `snowflake-client` (for example in Ricochet
 edit the `torrc` in `./local/share/Ricochet/ricochet/tor` with the
 relevant config).
 4. Watch the download failing, or the receiving/s in the Task Manager go
 down to 0.

 Doesn't seem to be reproducible with the earlier version of `snowflake-
 client`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs