Tor blocked? Connection Analysis

This is a quick guide on diagnosing connection problems to the Tor network mirrored from [url=][/url].

These are the quick and dirty steps to producing good, useful logs and traces to help us diagnose fingerprint-based blocking techniques.
1. Start up wireshark sniffing of your connection using these general instructions and/or these OS-specific instructions.
– If you are using a Linux root shell for testing, the command to use instead of wireshark is: “tcpdump -v -i any -s 0 -w bridge_test.cap”
2. Verify the wireshark sniffing is working. Try to access some non-censored websites and see if they show up in the wireshark capture window.
– Avoid sensitive sites sites that you are logged in to, because otherwise your login information will be stored in the capture file.
3. Get a private bridge IP from us (#tor-dev on, the ssl port is 6697). Do not use it yet.
4. Tell the person who gave you the bridge to start up wireshark or tcpdump sniffing the bridge side and enable info level logs on that bridge.
5. Attempt to access the bridge IP in Firefox with Tor still disabled: Enter the bridge IP address and port number into the Firefox URL bar, with an https in front. The URL location bar should look like this: https://bridge.ip:port/
– You should get a certificate warning. Tell us if you do or do not. If you do not get a warning, the bridge is likely blocked by IP. Ask us for a new bridge and try again (but leave the wireshark capture running the whole time).
6. If you do get the warning or you have tested at least 2-3 different private bridge IPs, configure your Tor to connect to the private bridge IP, and to log at info.
7. Let Tor attempt to connect.
8. Tell us the results.
9. Have wireshark save the capture file for this entire process, and send us this file and the Tor client log file.

If you need help and and the IRC server is blocked as well, you can contact me at moritz AT (GPG key, Fingerprint AAA1 4996 0B2B 636B F300 7005 6A5C 4515 6A6D 22E5)