Hi,
I'm not able to connect via bridges (obfs4 in particular) without first disabling bridges and connecting directly to the tor network. This is odd. Every time I turn on my laptop and start the tor browser bundle, it fails establishing a route. Setting a new bridge does not help either. But when I disable bridges and connect directly, then I can re enable the same bridges that used to fail and it will connect. Once I restart the tor browser, I can surely confirm that the connection is established via the bridge that used to fail, by looking at the active tcp connections.
This is making Tails impossible to work with bridges. Since Tails requires bridges to be set at logon time, it fails creating a route unless bridges are disabled and in that case it won't let re-enabling them.
What are your thoughts on this? Could this be a security threat? Is the government responsible for this? I live in Iran should you want to know.
ior kov:
Hi,
I'm not able to connect via bridges (obfs4 in particular) without first disabling bridges and connecting directly to the tor network. This is odd. Every time I turn on my laptop and start the tor browser bundle, it fails establishing a route. Setting a new bridge does not help either. But when I disable bridges and connect directly, then I can re enable the same bridges that used to fail and it will connect. Once I restart the tor browser, I can surely confirm that the connection is established via the bridge that used to fail, by looking at the active tcp connections.
This is making Tails impossible to work with bridges. Since Tails requires bridges to be set at logon time, it fails creating a route unless bridges are disabled and in that case it won't let re-enabling them.
What are your thoughts on this? Could this be a security threat? Is the government responsible for this? I live in Iran should you want to know.
Hm. What Tails version is that? (or better what Tor Browser version)? Could you check with the built-in bridges if you get the same error (assuming you did not do that already)? If the error persists, could we get some log output which you get when starting Tor Browser from a terminal like:
cd $path/to/your/tor-browser ./start-tor-browser.desktop --debug
Georg
tor-users@lists.torproject.org