Hello, I'm following the bridge setup for windows after not being able to start a tor browser for some reason and having some difficulty with the last step. After running tor.exe -f torrc, there is no notice file appearing where it should be, and Tor still seems to fail to setup. In the torrc.txt file I modified the "ORPort TODO1" and "ServerTransportListenAddr obfs4 0.0.0.0:TODO2" by replacing TODO1 and TODO2 with numbers greater than 1024 and less than 9000. I assume either I messed up modifying the text file or that the obsf4 port I selected is not reachable. Using the provided reachability test I tried ~15 4 digit numbers, using 0.0.0.0 as the IP and a 4 digit number in the appropriate range for the obsf4 port (none reachable). Any suggestions? Thanks!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi!it should work this way: BridgeRelay 1 ContactInfo blah at blubb dot com Nickname MyCoolNodeName ORPort TODO1 ExtORPort auto ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:TODO2 (i think the path to obfs4proxy should be changed, i run it in a linux box) -- tor38 Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ San Shi <substitutiongo@gmail.com> schrieb am Dienstag, 12. Januar 2021 um 21:19:
Hello,
I'm following the bridge setup for windows after not being able to start a tor browser for some reason and having some difficulty with the last step. After running tor.exe -f torrc, there is no notice file appearing where it should be, and Tor still seems to fail to setup.
In the torrc.txt file I modified the "`ORPort TODO1`" and "ServerTransportListenAddr obfs4 0.0.0.0:TODO2" by replacing TODO1 and TODO2 with numbers greater than 1024 and less than 9000.
I assume either I messed up modifying the text file or that the obsf4 port I selected is not reachable. Using the provided reachability test I tried ~15 4 digit numbers, using 0.0.0.0 as the IP and a 4 digit number in the appropriate range for the obsf4 port (none reachable).
Any suggestions? Thanks! -----BEGIN PGP SIGNATURE----- Version: ProtonMail
wsBzBAEBCAAGBQJf/s7AACEJEDUs4U/MtwBvFiEED/I4MJr2ATnk+E6XNSzh T8y3AG92Twf+KfxKZQ6kKXCiJWfXNgxBuU1qkAsYJ9D5aGl1se7R8kOpI2Ww oHcWimIl/m1VNhVkMqlrIuXJfPKFYQacTKdwYGdkVK1xGzkiwXkI7I5IEwKc bDmMwxafVe15kAxGld1JxvjMXo7PIZOeF/TSNPPkEG6ijtsKtXhs+KdDc2fV Q65gZvjUfMxYUMqdfDkzFds2Khx8aBgpMyEuUucb7YIAq3yzagHYTgb62AXH dALIjGoO8pxUDSi4oGF+8X6/omYegAMReJk5qC+WynhUe9x+TpQExS8Edr2h 1d9acbbO6VHYaBm/qI82FkCwbgQOHPxT7qS63EYg3JljFoCnrw17GA== =toqx -----END PGP SIGNATURE-----
On Tue, Jan 12, 2021 at 12:19:28PM -0800, San Shi wrote:
After running tor.exe -f torrc, there is no notice file appearing where it should be, and Tor still seems to fail to setup.
What does your log file say?
I assume either I messed up modifying the text file or that the obsf4 port I selected is not reachable. Using the provided reachability test I tried ~15 4 digit numbers, using 0.0.0.0 as the IP and a 4 digit number in the appropriate range for the obsf4 port (none reachable).
The reachability test at <https://bridges.torproject.org/scan/>? You will have to enter your bridge's IP address. 0.0.0.0 won't work.
participants (3)
-
Philipp Winter -
San Shi -
tor38