Changes between Initial Version and Version 8 of Ticket #30350


Ignore:
Timestamp:
May 2, 2019, 6:34:13 AM (7 months ago)
Author:
dcf
Comment:

Replying to cohosh:

I started running a new proxy-go instance on a different server. It took me a few tries in order to get it as a snowflake from the VPS, but when I eventually did, the connection was successful.

I'm going to say that this a proxy blocking problem and what we need is:

  1. New, unblocked proxies
  2. Something better on the client side than the 30 second timeout to figure out that the connection has been blocked we need a different proxy (I'll add these notes to #25429).
  3. Some way at the broker to hand out proxies in a smarter way so that we aren't repeatedly giving clients snowflakes that are blocked in their region

Thanks for running these tests so quickly.

Blocking the single IP address of the current fallback proxies is what I would have expected to happen first, and it looks like that's what happened in this case. Anyway, a blocking reaction by the GFW is a milestone for us. (It took at least 19 months of the proxies running at a static IP for even this small blocking event to happen.) I honestly thought that Snowflake didn't work in China anyway because of our use of a Google STUN server, but I guess I was wrong.

I'm not sure item 3, tracking where proxies are blocked, is necessarily a priority. Round-the-clock proxy-go was never meant to be a permanent thing, only a stopgap until we have actual organic proxies (#20813). The idea is that eventually we don't rely on long-lived proxies running at static IP addresses, because if we do that we're playing the bridge distribution game, and doing it worse than BridgeDB does. IMO the browser extension (#23888) is the priority for getting actually diverse snowflakes.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30350

    • Property Status changed from new to accepted
    • Property Owner set to cohosh
    • Property Cc mcs gk added
  • Ticket #30350 – Description

    initial v8  
    33Below is Tor log messages.
    44
    5 
     5{{{
    665/1/19, 05:10:31.667 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
    775/1/19, 05:10:37.818 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
     
    19195/1/19, 05:11:51.702 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
    20205/1/19, 05:11:51.702 [WARN] Pluggable Transport process terminated with status code 0
    21 
     21}}}
    2222
    2323Could you please solve this problem? Thank you very much for your help. I really appreciate it.