This option specifies that Tor will use the bridges specified with the bridge configuration variable to be used as entry points to the Tor network. Let’s describe those configuration variables a little bit – summarized from : What if we want to configure the use of bridges manually? We can do that by editing /etc/tor/torrc configuration file and adding the following configuration variables: The first bridge is named derby, while the second one is Unnamed, but both are working just fine. We can see that Tor successfully learned the fingerprint of both bridges. Looks like client functionality is working. We now have enough directory information to build circuits. In the Message Log we can see logging information presented below: The configuration settings can be seen in the picture below: Let’s add the first two bridges in the Vidalia and click Ok. This will open “Bridge Settings” where we can add the bridges. To use those IP addresses we can open up Vidalia and go to Network and check “My ISP blocks connections to the Tor network”. Soon after the message will be sent, we’ll receive the IP of one of the available bridges. We can get a list of bridges by sending an email message from a Google or Yahoo account to and setting the Subject and Body of an email message to “get bridges”.

The second option is not hard to guess, since the previous picture mentions it.We can see that we got two bridge relays, one on port 80 and the other on port 443: Find a Tor bridge by visiting the Tor Bridges in a web browser, which should give us two bridge relays as shown in the picture below:.There are two ways of finding the Tor bridge IP addresses and they are described below: First we need to find Tor bridges in order to get the IP address to which we’ll connect. If our ISP is blocking access to the Tor network, we can still bypass ISP’s filters by using a Tor bridge.

Bridges tor project