BridgeT produces false negatives

BridgeT produces false negatives. I'm not entirely sure why, but I seem to get less number of false negatives when I reduce the number of concurrent Tor processes.

added component::archived/ooni owner::hellais priority::medium resolution::fixed status::closed type::defect labels

Have you looked at the options available in ooni-probe.conf? I wonder if the option tor_bridges_timeout will help you here.

Have you tried connecting to these bridges manually? Did you notice that the false negative bridges are slower at connecting than the others?

You should probably also try tweaking the bridges timeout inside of the config file as Runa said.

In future to make this behavior more understandable we should start keeping the notice level log of Tor for bridges that fail.

Replying to hellais:

Have you tried connecting to these bridges manually?

Yes

Did you notice that the false negative bridges are slower at connecting than the others?

No

You should probably also try tweaking the bridges timeout inside of the config file as Runa said.

Increasing the timeout and/or decreasing the number of concurrent Tor processes seems to do the trick.

In future to make this behavior more understandable we should start keeping the notice level log of Tor for bridges that fail.

+1 How about storing notice level logs of all the Tor bridges and then grep for the bridge that fails and then discard the rest? Is there a better simpler method you can think of?

Trac:
Cc: N/A to gsathya.ceg@gmail.com

This ticket is related to an old code base. A new ticket should be open if this problem still persists.

Trac:
Status: new to closed
Resolution: N/A to fixed

closed