[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #12020 [Tor]: Bootstrap gets stuck at 20% when connecting through a bridge.



#12020: Bootstrap gets stuck at 20% when connecting through a bridge.
-------------------------+--------------------------------
     Reporter:  yawning  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  Tor: 0.2.???
    Component:  Tor      |    Version:  Tor: 0.2.5.4-alpha
   Resolution:           |   Keywords:  tor-bridge
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------------

Comment (by s7r):

 This is a strange problem that I faced today as well. Here is some
 information about my setup:
 OpenVZ container with virtual network interface (venet)
 OS: Debian 7 Wheezy
 Network configuration:
 lo (local loopback)
 venet0 - inet addr 127.0.0.2 and inet6 addr <public v6 address>/128 scope
 global
 venet0:0 -inet addr <public v4 address)

 Trying to build a bridge with obfs3 and obfs4 pluggable transports on Tor
 0.2.5.8-rc and obfs4proxy installed from Debian sid repo.

 Wanted the bridge to listen on v4 and v6 too, so I have stated in torrc:
 ORPort [::]:443
 the same for obfs3 and obfs4 listen addr [::]:port
 (this opened ORPort on both versions of IP. Checked via a remote server
 port checker and ports open, everything working fine). OR and obfuscated
 ports open on v4 and v6.

 Trying to connect to the bridge via IPv4, it stucks at loading network
 status. takes forever, does not go on. Tried to connect to it as a normal
 bridge, obfs3 bridge and obfs4 bridge and the same.

 Added "Address <public v4 address>" in torrc. Restarted Tor daemon. The
 same, nothing fixed.

 Finally, I have removed ORPort [::]:443 from torrc and put instead 2
 entries as follows:
 ORPort <public v4 address>:443
 ORPort <public v6 address>:443
 Left the obfuscated listening ports untouched.

 And... it worked. connected to the Tor network just fine. Connected via
 regular bridge, obfs3 and obfs4 - all working fine. Port open on v6 too.

 I might add the fact that these are private bridges configured not to send
 anything to the bridge authorities (maybe this is somehow relevant)
 [PublishServerDescriptor 0]

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12020#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs