Hey folks
The mobile Internet in Iran is only-Iran access these days, but the servers in data-centers have access to the Internet; albeit they are restricted too and can not connect directly to TOR.
First thing I tried was to setup a TOR connection via a bridge on a server which was fine and working. But when I tried to turn that to a bridge it-self, I found that it’s not possible (or I didn’t find a way). The second thing I tried was to run tor over a local socks proxy.
This is my torrc file:
Socks5Proxy 127.0.0.1
ORPort auto
BridgeRelay 1
PublishServerDescriptor 0
Exitpolicy reject *:*
Nickname [myname]
ContactInfo [my mail]
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
ServerTransportOptions obfs4 iat-mode=2
ExtORPort auto
When I run tor, I get this log:
[n] Tor 0.4.6.10 opening log file.
[n] We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These two versions should be binary compatible.
[n] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
[n] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
[n] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
[n] Read configuration file "/etc/tor/torrc".
[n] Based on detected system memory, MaxMemInQueues is set to 1420 MB. You can override this by setting MaxMemInQueues by hand.
[n] Opening Socks listener on 127.0.0.1:9050
[n] Opened Socks listener connection (ready) on 127.0.0.1:9050
[n] Opening OR listener on 0.0.0.0:0
[n] OR listener listening on port 40785.
[n] Opened OR listener connection (ready) on 0.0.0.0:40785
[n] Opening OR listener on [::]:0
[n] OR listener listening on port 35951.
[n] Opened OR listener connection (ready) on [::]:35951
[n] Opening Extended OR listener on 127.0.0.1:0
[n] Extended OR listener listening on port 43267.
[n] Opened Extended OR listener connection (ready) on 127.0.0.1:43267
[n] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
[n] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
[n] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
[n] Your Tor server's identity key fingerprint is [fp]
[n] Your Tor bridge's hashed identity key fingerprint is [fp]
[n] Your Tor server's identity key [ik] fingerprint is '[fp]'
[n] You can check the status of your bridge relay at https://bridges.torproject.org/status?id=[fp]
[n] Bootstrapped 0% (starting): Starting
[n] Starting with guard context "default"
[n] Signaled readiness to systemd
[w] Managed proxy '/usr/bin/obfs4proxy' did not configure the specified outgoing proxy and will be terminated.
[w] Pluggable Transport process terminated with status code 0
[n] Bootstrapped 3% (conn_proxy): Connecting to proxy
[n] Opening Socks listener on /run/tor/socks
[n] Opened Socks listener connection (ready) on /run/tor/socks
[n] Opening Control listener on /run/tor/control
[n] Opened Control listener connection (ready) on /run/tor/control
[n] Bootstrapped 4% (conn_done_proxy): Connected to proxy
[n] Bootstrapped 10% (conn_done): Connected to a relay
[n] Bootstrapped 14% (handshake): Handshaking with a relay
[n] Bootstrapped 15% (handshake_done): Handshake with a relay done
[n] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
[n] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
[n] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
[n] Bootstrapped 100% (done): Done
[n] Now checking whether IPv4 ORPort [ip]:40785 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
and after a long time, I get something like this:
Your server has not managed to confirm reachability for its ORPort(s) at [ip]:40785. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
But I can manually telnet and connect to the port on the IP from everywhere.
One time I get something like this:
[n] Self-testing indicates your ORPort [ip]:8080 is reachable from the outside. Excellent.
[n] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 127 buildtimes.
[n] No circuits are opened. Relaxed timeout for circuit 168 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
[n] No circuits are opened. Relaxed timeout for circuit 195 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [23 similar message(s) suppressed in last 4500 seconds]
[n] No circuits are opened. Relaxed timeout for circuit 203 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [7 similar message(s) suppressed in last 5280 seconds]
[n] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 117 buildtimes.
[n] No circuits are opened. Relaxed timeout for circuit 358 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [9 similar message(s) suppressed in last 3660 seconds]
[n] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.91 MB and received 7.74 MB. I've received 51 connections on IPv4 and 0 on IPv6. I've made 21 connections with IPv4 and 0 with IPv6.
[n] While not bootstrapping, fetched this many bytes: 5704117 (server descriptor fetch); 483366 (consensus network-status fetch); 35954 (microdescriptor fetch)
[n] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[n] No circuits are opened. Relaxed timeout for circuit 360 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 5400 seconds]
[n] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 117 buildtimes.
But I never get the port for obfs4 bridge anyway