[tor-bugs] #9601 [BridgeDB]: Cyberoam firewall blocks obfs2/3 bridge addresses

[Tor Bug Tracker & Wiki]

#9601: Cyberoam firewall blocks obfs2/3 bridge addresses
--------------------------+-----------------
     Reporter:  Sherief   |      Owner:
         Type:  task      |     Status:  new
     Priority:  normal    |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+-----------------

Comment (by mrphs):

 A little bit more info could help us figure out how this firewall is
 blocking Tor.

 This is my to-do list when a user struggles with bootstraping Tor:
 ''I've already mentioned this on IRC, going to copy it here for the sake
 of having record...''

  1. Send the "How to get bridge & add it to Vidalia" instruction plus few
 bridges (while I make sure to include bridge with random port) in case
 they failed to get the bridges for any reason.
  1. If the user failed connecting and returned I'd give give him some
 unpublished bridges and ask her/him to turn on debug/info logging,
 increase the message log history to a more reasonable number for debug (at
 least 1000), check the "automatically log message to a file" option, try
 to connect to the network using given bridges and send it back it to us.
  1. I'd send out PT TBB mirrors with few bridges (including at least one
 unpublished bridges) and teach them how to query bridges @ bridges.tpo to
 get obfs3 bundles.
  1. It rarely makes it to this point, but I'd ask them to again turn on
 the debug log on to see what's going on. We usually find interesting bugs
 here.

 it might be a little off-the-topic but hopefully handy for ppl

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9601#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online