wkrp
commented
2 years ago Custom snowflake bridge lines to test. Custom snowflake bridge lines do not yet work in Orbot.
- Alternate broker domain front. Go to where Tor Browser lets you enter a bridge address. (Settings → Connection → Bridges in Tor Browser desktop.) Copy and paste the following bridge line, the whole thing:
snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://snowflake-broker.azureedge.net/ front=ajax.aspnetcdn.com ice=stun:stun.voip.blackberry.com:3478,stun:stun.altar.com.pl:3478,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.sonetel.net:3478,stun:stun.stunprotocol.org:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478The difference from usual is the url and front parameters. - AMP cache rendezvous. Snowflake in Orbot for Android or iOS has a built-in AMP cache rendezvous setting, but you can enable it in desktop Tor Browser by manually entering a bridge address. Go to where Tor Browser lets you enter a bridge address. (Settings → Connection → Bridges.) Copy and paste the following bridge line, the whole thing:
snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://snowflake-broker.torproject.net/ ampcache=https://cdn.ampproject.org/ front=cdn.ampproject.org ice=stun:stun.voip.blackberry.com:3478,stun:stun.altar.com.pl:3478,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.sonetel.net:3478,stun:stun.stunprotocol.org:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478The difference from usual is the url, ampcache, and front parameters. You can experiment with different Google domains for the front parameter.
EDIT 2022-10-07: Removed the QR codes as they do not work in Orbot.
quartermarsh
SaSyda
free-the-internet
gusgustavo
pitasia
gaukas
hexrot
mehdifirefox
Since the beginning of protests and shutdowns in Iran, we have been applying numerous performance optimizations to the Snowflake bridge. As a result, peak bandwidth has risen from 1 Gbps to 4 Gbps and the estimated number of simultaneous users has grown from 20,000 to 100,000. But about two days ago, at 2022-10-04 17:15, usage dropped suddenly and drastically. Likely related, users reported failed Snowflake connection from Iran starting 2022-10-05. We have been investigating, but the exact cause is not clear. We would like help, especially logs from failed Snowflake connections.
You can see the sudden drop in client polls at the Snowflake broker:
It was accompanied by a simultaneous drop in bandwidth at the bridge:
The most likely explanation for a pattern like this is censorship of the broker, probably in Iran. Clients cannot reach the broker, therefore they do not get proxy service, therefore they do not use bridge bandwidth. But the evidence is somewhat ambiguous, and anyway we need to understand how the broker is being blocked, if indeed that is what's happening.
Some of the evidence:
There are various possible explanations. For example, connectivity to the broker domain front may be blocked only for certain TLS fingerprints. Perhaps OONI coverage is lacking in the networks most affected. For this we would like help.
How you can help
and add this to the end of the line:
Then, when you restart Tor Browser, you will find the log at: