FAQ

This FAQ is related to questions around TorBox. For additional questions and feedback, visit our GitHub page or contact me. For questions relating to Tor or the Tor Browser, check the general FAQ page of the Tor Project or the official Tor support website.

Table of contents
1. Should I change the default passwords? How can I change my passwords?
2. Should I change the name of the wireless network (SSID) of my TorBox? How can I change it?
3. Can I hide the name of the wireless network (SSID) of my TorBox?
4. Which SSH client do you prefer?
5. Do you know some useful browser add-ons to improve anonymity, security and/or usability?
6. Do you know some essential configuration adjustments for Firefox (via about:config) to
    improve anonymity and security?
7. I’m connected to TorBox, and all is working as expected, but I’m not able to download
    something with my BitTorrent client. What’s wrong?
8. Isn’t there a workaround so that I can use TorBox and BitTorrent the same time?
9. I’m connected to TorBox, and all is working as expected, but Firefox, Safari and any iOS device
    don’t display .onion sites. What’s wrong?
10. For starters, do you know some interesting .onion sites?
11. Tor statistics (main menu entry 1) don’t show up — the screen stays black. What can I do?
12. How can I be sure, if my device is using the Tor network?
13. Why do I receive a yellow onion on the Tor Project’s check-site?
14. My client, which is connected to the TorBox, doesn’t receive an IP address.
15. My TorBox doesn’t receive an IP address from the network router.
16. My TorBox receives an IP address (192.168.42.*) from the network router, but it doesn’t work.
17. I’m connected to a public wireless network; everything works as expected. However, every
      x minutes, the connection to the wireless network stops completely, and I have to repeat
      the entire login procedure. What could be the reason?
18. Wicd (the network manager) doesn’t show me all wireless networks! It seems that the ones
      on the 5GHz band are missing. What can I do?
19. Wicd (the network manager) tries to connect a wireless network, but it sticks with “Validating
      authentication”, the program crashes and/or seems to have many bugs. What’s wrong?
20. All about the power supply: “Under-voltage detected!” / Red blinking LED on the Raspberry
      Pi 3 Model B+ / Unusual, strange behaviors – What do these things mean?
21. I can’t get tethering to work. What’s wrong with it?
22. When I’m connected with TorBox and use the Tor Browser on one of the clients, isn’t that
      a risk for my security/anonymity?
23. If I have two or more clients, let’s say device 1 and device 2, connected to the TorBox will it
      intelligently make sure each client has its own tor circuit?

• • •

The Configuration & Update Menu of TorBox v.0.2.5.
The Configuration & Update Menu of TorBox v.0.2.5.
Question #1:
Should I change the default passwords? How can I change my passwords?
Answer:
You should change the default passwords a soon as possible. This is an easy task: login into your TorBox with an SSH client, go to the Configuration & Update Menu (main menu entry 4) and choose the associated menu entries under the section “Configuration” (click on the image on the right side).

Question #2:
Should I change the name of the wireless network (SSID) of my TorBox? How can I change it?
Answer:
This is not mandatory, but you can do it without considerable effort: login into your TorBox with an SSH client, go to the Configuration & Update Menu (main menu entry 4) and choose the associated menu entries under the section “Configuration” (click on the image on the right side above).

Question #3:
Can I hide the name of the wireless network (SSID) of my TorBox?
Answer:
Yes, and it is easy to accomplish: login into your TorBox with an SSH client, go to the Configuration & Update Menu (main menu entry 4) and choose the associated menu entries under the section “Configuration” (click on the image on the right side above).

Question #4:
Which SSH client do you prefer?
Answer:
There is an extensive collection of SSH clients. Usually, it doesn’t matter which one you are using. These are my recommendations:

For a list of other SSH clients, see here.

An iPad connected to TorBox running arm (Tor statistics) in a vSSH terminal.
An iPad connected to TorBox running arm (Tor statistics) in a vSSH terminal.

 
Question #5:
Do you know some useful browser add-ons to improve anonymity, security and/or usability?
Answer:
Yes, but first let me repeat one crucial point: if your well-being depends from your anonymity, then is highly recommended to use the Tor Browser only or even better Tails (read here, here and here why).

In my opinion following browser add-ons are very useful:

  • https-everywhere: Automatically makes websites use a more secure HTTPS connection instead of HTTP if they support it. With HTTPS, even the connection between the Tor exit node and the web server is encrypted. Tor Browser also uses this add-on. (USED BY TOR BROWSER; ESSENTIAL for SECURITY / ANONYMITY; available for Firefox, Firefox for Android, Chrome, and Opera).
  • NoScript: Allows JavaScript, Java, Flash, and other plugins to be executed only by trusted web sites of the users choice. NoScript also provides powerful anti-XSS and anti-Clickjacking protection. Tor Browser also uses this add-on. (USED BY TOR BROWSER; ESSENTIAL for SECURITY / ANONYMITY; available for Firefox and Chrome).
  • First Party Isolation: First Party Isolation, also known as Cross-Origin Identifier Unlinkability, is a concept from the Tor Browser. The idea is to key every source of browser identification with the domain in the URL bar (the first party). This makes all access to identifiers distinct between usage in the website itself and through third-party. Think of it as blocking Third-party cookies, but more exhaustively. (USED BY TOR BROWSER; ESSENTIAL for SECURITY / ANONYMITY; available for Firefox).
  • uBlock Origin: The only real working and independent ad blocker (ESSENTIAL for SECURITY / ANONYMITY / USABILITY; available for Firefox, Chrome, Safari, and Opera).
  • Smart Referer: Prevents Cross Domain Referer Leakage (ESSENTIAL for ANONYMITY; available for Firefox).
  • CanvasBlocker: Allows users to prevent websites from using the Javascript canvas API for fingerprinting them. (ESSENTIAL for ANONYMITY; available for Firefox)
  • Decentraleyes: This browser add-on emulates Content Delivery Networks (CDN) by finding supported resources locally, and injecting them into the environment. All of this happens automatically, so no prior configuration is required. Here is a testing utility to find out if you are properly protected against a CDN vulnerability (ESSENTIAL for ANONYMITY; available for Firefox, Chrome, Opera).
  • Neat URL: Cleans URLs, removing parameters such as Google Analytics’ utm parameters. (ESSENTIAL for ANONYMITY; available for Firefox)
  • Skip Redirect: Some web pages use intermediary pages before redirecting to a final page. This add-on tries to extract the final url from the intermediary url and goes there straight away if successful. (ESSENTIAL for PRIVACY / USABILITY; available for Firefox)
  • Privacy Pass: Allow users to redeem validly signed tokens instead of completing captcha solutions. Clients receive 30 signed tokens for each captcha that is initially solved. Cloudflare currently supports Privacy Pass. (ESSENTIAL for USABILITY; available for Firefox and Chrome).
  • uMatrix: Point and click matrix to filter net requests according to its source, destination, and type (available Firefox, Chrome, and Opera).
  • Privacy Badger: A balanced approach to internet privacy between consumers and content providers by blocking advertisements and tracking cookies that do not respect the Do Not Track setting in a user’s web browser (available for Firefox, Chrome, and Opera).
  • FoxyProxy: FoxyProxy is an advanced proxy management tool (see also here; available for Firefox, Chrome, Safari, Opera, and others).
  • Bypass Paywalls: Let’s say you are a researcher and one of your sources is an article in the Washington Post. Would you subscribe, only for that one article? Yes, we thought so, too 😉 (available for Firefox and Chrome).

Do you have another very useful browser add-on? Let me know in the comment section below!

Question #6:
Do you know some essential configuration adjustments for Firefox (via about:config) to improve anonymity and security?
Answer:
Yes, but first let me repeat one crucial point: if your well-being depends from your anonymity, then is highly recommended to use the Tor Browser only or even better Tails (read here, here and here why).
In my opinion following configuration adjustments for Firefox are very useful:

  • To enable strict First Party Isolation, also known as Cross-Origin Identifier Unlinkability, search for privacy.firstparty.isolate and privacy.firstparty.isolate.restrict_opener_access and set both to true. Alternatively, the browser add-on First Party Isolation does the same (see above). You should really do that!
  • To disable WebRTC (possible IP leak!!), search for media.peerconnection.enabled and double-click on it –> false.
  • To disable face detection using cameras, search for camera.control.face_detection.enabled and double-click on it –> false.
  • To disable geolocation services, search for geo.enabled and double-click on it –> false.
  • To disable the ability to report what plugins are installed, search plugin.scan.plid.all and double-click on it –> false.
  • To disable web speech recognition through the microphone, search media.webspeech.synth.enable and media.webspeech.recognition.enable and double-click on them –> false.
  • To disable all telemetry features, search for “telemetry” and disable all true/false settings related to telemetry by setting them to false.
  • To harden your browser (a little bit) against fingerprinting, search for “privacy.resistFingerprinting” and double-click on them –> true.
  • To enable tracking protection, search for “privacy.trackingprotection.enabled” and double-click on them –> true.

For more information see here or here. Do you have other essential configuration adjustments for Firefox or any other browser? Let me know in the comment section below!

Question #7:
I’m connected to TorBox, and all is working as expected, but I’m not able to download something with my BitTorrent client. What’s wrong?
Answer:
BitTorrent is not working over Tor, because Tor doesn’t support UDP. There are clients with a “Tor-switch” and there are people using the SOCKS v5 feature of the Tor Browser. However, this doesn’t change the fact that UDP is not routed through Tor. If in these configurations BitTorrent works properly, this means that the UDP packages go clear-net, revealing the identity of the client. With TorBox client-devices don’t have direct access to the clear-net. Consequently, UDP packages are dropped and the identity of the client is safeguarded. By the way: due to the high bandwidth usage caused by the BitTorrent protocol, it is considered impolite and inappropriate by Tor community members to use the Tor network for BitTorrent transfers. For that reason, some Tor exit nodes block BitTorrent traffic.

Question #8:
Isn’t there a workaround so that I can use TorBox and BitTorrent the same time?
Answer:
Yes, there is, but it is a little bit complicated and slow. You need a SOCKS v5 proxy server and a BitTorrent client, which works properly with it (for example: Deluge and Vuze). BitTorrent is now tunneled through Tor to the proxy server. Regarding the Socks5 proxy server: we didn’t find any reliable working free public proxy server. The best server we found is coming with costs, even not so much: Private Internet Access (for alternative commercial proxy providers see here). Nevertheless, you should think very carefully about the necessity to use Tor for your BitTorrent traffic, because it is slow and due to the high bandwidth the Tor community doesn’t like it.

BitTorrent tunneled through Tor with a proxy server from “Private Internet Access”. It works, but it is slow. It is probably useful to circumvent censorship but not for daily use. After the screenshot, I canceled the download; no bytes were harmed.

 
Question #9:
I’m connected to TorBox, and all is working as expected, but Firefox, Safari and any iOS device don’t display .onion sites. What’s wrong?
Answer:
As per IETF RFC 7686, “Applications that do not implement the Tor protocol should generate an error upon the use of .onion and should not perform a DNS lookup.” To display a .onion site, you have to use the Tor Browser or the Onion Browser on iOS.

Nevertheless, the display of .onion sites is still possible with certain browsers:
Google Chrome (tested with Version 74) and Chromium (Version 76) resolve .onion addresses by default, without any adjustments.
With Mozilla Firefox you have to use the SOCKS v5 proxy functionality of your TorBox and to configure Firefox accordingly:

  • Under about:preferences, “Network Settings”, click on “Settings…”, choose “Manual proxy configuration”, under “SOCKS Host” enter following IP: 192.168.42.1 / Port: 9050. Toggle on “Proxy DNS when using SOCKS v5”.
  • Under about:config, search for “network.dns.blockDotOnion” and set it to “false”.

The add-on FoxyProxy Standard offers another interesting way to resolve .onion addresses, only using the TorBox SOCKS v5 proxy for that kind of addresses:

  • Install the add-on.
  • Under “Options” add a new proxy, choosing as “Proxy Type” “SOCKS5”, enter IP: 192.168.42.1 / Port: 9050. Toggle on “Send DNS through SOCKS5 proxy?” and save the changes.
  • Under “Patterns” whitelist .onion (see images below).
  • Activate the new proxy settings and activate “Use Enabled Proxies by Patterns and Priority” by clicking on the FoxyProxy icon.
  • Now, all .onion addresses are sent through TorBox’s SOCKS v5; all other addresses are not affected.

• • •

• • •

• • •

 
Question #10:
For starters, do you know some interesting .onion sites?
Answer:
Of course, here is a very short collection: Ahmia Search Engine, OnionDir – Deep Web Link Directory, Deep Web Search Engine, Duck Duck Go Search Engine, BBC News, Facebook, Imperial Library, secMail, The Hidden Wiki, The Pirate Bay, The Tor Project Homepage, TorLinks.

For more sites, see also here (on “clear-web”): Deep Web links, here or here (in German).

Question #11:
Tor statistics (main menu entry 1) don’t show up — the screen stays black. What can I do?
Answer:
The program “Nyx”, which shows the Tor statistics uses the control port of the local Tor installation. If the loading of the Tor process gets stuck or takes a lot of time (possible in case of network connection problems or censorship), “Nyx” doesn’t start either. However, we implemented an alternative way to quickly check the Tor’s log file: go to the countermeasures & troubleshooting menu and chose entry 12. The screen updates automatically when a new entry is written to the log file.

All works just fine....
All works just fine….
Question #12:
How can I be sure, if my device is using the Tor network?
Answer:
Go to https://check.torproject.org/ or http://onionbr5zulufnuj.onion. For more information, you can also use the check site operated by JonDonym. Check with Panopticlick (by the EFF), if your browser is safe against tracking? To check for other browser leaks, go here (an excellent analytic tool!); additionally, you could also test against IP leaks and DNS Nameserver spoofability. You can also monitor your data transfer by using TorBox’s main menu entry 1. On macOS, there is a nice program (IP in Menubar), which permanently displays the IP address of your Tor exit node in the menu bar.

Question #13:
Why do I receive a grey onion on the Tor Project’s check-site?
Answer:
Because the user agent string of your web browser differs from the one from the Tor Browser. The Tor Browser is using following user agent string: “Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0”. You can easily switch your current user agent string with “User Agent Switcher” (for Firefox). However, there are side effects:

  1. Changing the user agent without changing to a similar platform makes your browser nearly unique and allow for fingerprinting your device.
  2. If your string is saying that you are running Windows NT 6.1, most likely a download page automatically offers you a download package for Windows NT, even if you are running OS X. Therefore, a user agent switcher allows you to change the string in one or two clicks if needed.

 
Question #14:
My client, which is connected to the TorBox, doesn’t receive an IP address.
Answer:
Usually, the DHCP-server on TorBox provides your client with all necessary information. If it doesn’t work, and you are sure that your client is configured accordingly, first try to restart TorBox. Shouldn’t that doesn’t work either, then try to configure your client manually:

IPv4-address of your device: 192.168.42.x  (x > 12)
Net Masq: 255.255.255.0
Router / Gateway: 192.168.42.1
DNS: 192.168.42.1 / torbox.ch

 
Question #15:
My TorBox doesn’t receive an IP address from the network router.
Answer:
TorBox is configured as a DHCP client, which means that the router has to give TorBox all necessary network information (usually, the router is configured like that). If that doesn’t work, try to configure TorBox manually according to the data of your provider or an actual client, which works with your router properly:

sudo iptables <interface> <static_IP_address>
sudo route add default gw <gateway_ip>

 
Question #16:
My TorBox receives an IP address (192.168.42.*) from the network router, but it doesn’t work.
Answer:
TorBox in its default configuration occupies the IP-addresses 192.168.42.0 – 192.168.42.255 for its purpose. In the very rare case in which the network router uses the same IP range, you have either to change the IP range of the router or to change the configuration of the TorBox (for example changing all 192.168.42.* to 192.168.43.*. For more information, please contact me.

 
Question #17:
I’m connected to a public wireless network; everything works as expected. However, every x minutes, the connection to the wireless network stops completely, and I have to repeat the entire login procedure. What could be the reason?
Answer:
Certain Internet provider (usually at airports, in hotels, coffee houses, etc.) disconnect the network connection after a particular time of inactivity. In this case, the Tor statistics (main menu entry 1) no longer shows any data transfer and after about 15 seconds, errors in communication with the Tor network will appear. Try to activate in the countermeasures & troubleshooting menu entry 10 “Countermeasure against a disconnection when idle feature”.

A map of Europe, with the corresponding two-letter country codes in place of the full names of countries.
A map of Europe, with the corresponding two-letter country codes in place of the full names of countries.
Question #18:
Wicd (the network manager) doesn’t show me all wireless networks! It seems that the ones on the 5GHz band are missing. What can I do?
Answer:
By default, TorBox WLAN regulatory domain is set to global (or in other words: unset). Usually, this is not a problem for wireless networks on the 2,5 GHz band. However, all usable frequencies in the 5 GHz band have the no-ir (no-initiating-radiation) flag set, which prevents TorBox from using them. To use the 5 GHz band, to see and to connect wireless network on this band, you have to set the country-specific WLAN regulatory domain. The corresponding two-letter country code can be found in this list (for European countries see also the image on the right side). We are looking forward to making this procedure more user-friendly in one of the next TorBox releases.

Question #19:
Wicd (the network manager) tries to connect a wireless network, but it sticks with “Validating authentication”, the program crashes and/or seems to have many bugs. What’s wrong?
Answer:
It is crucial that your TorBox does receive enough power. Generally speaking, you cannot run your TorBox on a USB port of your laptop — this will most likely lead to various unforeseen behaviors. The required power is dependent on which Raspberry Pi variant your TorBox image is running. With a Raspberry Pi 3 Model B+ or a Raspberry Pi 4 Model B, you should use the official power supply or at least one, which provides 5V and 3A (15W). If you need a power bank (for a “TorBox to go” situation), it is recommended to take one with a high capacity (10.000 Ah or more) and an output power capability of at least 15 W (5V x 3A). Even if a Raspberry Pi 3 Model B has a lower network performance, it may run more stable on a power bank due to its lower power consumption (see this Raspberry Pi 3 B+ Review and Performance Comparison and this Power Consumption Benchmarks). The red PWR LED gives you a sense of the stability of your power supply — see the question/answer below.

Question #20:
All about the power supply: “Under-voltage detected!” / Red blinking LED on the Raspberry Pi 3 Model B+ / Unusual, strange behaviors – What do these things mean?

If "pwr" flashes red => Problems are coming ahead!
If “pwr” flashes red => Problems are coming ahead!
Answer:
It is crucial that your TorBox does receive enough power. The red PWR LED on your Raspberry Pi indicates, if it receives enough power. If it fails to light or flashes with a Raspberry Pi 3 B/B+ then most likely the voltage dropped below 4.63V. Additionally, with the Raspberry Pi 3 Model B+, the drop below 4.63V is notified by an “Under-voltage detected!” in the terminal. This doesn’t automatically mean that TorBox won’t work, but it can lead to strange behaviors (for example during the setup process of a connection to a wireless network; see question above), to data losses or even to a corruption of your SD card. If this message regularly arises or/and red PWR LED flashes for a longer time, then you should switch to a more reliable power supply such as the “the official and recommended universal micro USB power supply for Raspberry Pi“. If you like to use another power supply or a power bank (for a “TorBox to go” situation), the following minimum requirements are recommended to ensure a trouble-free operation of your TorBox:

  • Raspberry Pi 3 Model B: 5V / 2.4A / 12W
  • Raspberry Pi 3 Model B+: 5V / 3A / 15W
  • Raspberry Pi 4 Model B: 5V / 3A / 15W

If the “Under-voltage detected!” notification spams your console or your log file, a temporary fix is to ignore it: create /etc/rsyslog.d/ignore-underpowering.conf with :msg, contains, “voltage” ~ and you can enjoy your unstable system.

Three USB WiFi adapters: the one far left needs too much power during boot up. The other two function without any problem. Adapters with long external antennas usually do not work.

The necessary power supply is highly dependent on your peripherals. Even with a reliable power supply, you could run into problems, especially if you are using a “Wireless-internet to wireless-clients” connection. As a rule, simpler, low-powered USB WiFi Adapters lead to fewer problems (see image right). Especially booting up your Raspberry Pi with an already attached USB WiFi adapter could be too much for the power supply of your board. In such a case, try to boot up the Raspberry Pi first and to attach the USB WiFi adapter later when the system is already running. Another solution could be to use a Raspberry Pi 3 Model B instead of a newer more power-hungry variant. Even if it has a lower network performance, it may run more stable, especially on a power bank, due to its lower power consumption (see this Raspberry Pi 3 B+ Review and Performance Comparison and this Power Consumption Benchmarks).

This TorBox (Raspberry Pi 2 Model B) with a TFT display, two wireless network adapter and an RS Pro PB-10400 Power Bank, 5V / 10,4Ah as a power source is connected to a wireless network in a Starbucks Coffee shop. Most likely, this does not work with a Raspberry Pi 3 Model B+ due to its higher power consumption.
This TorBox (Raspberry Pi 2 Model B) with a TFT display, two wireless network adapter, and an RS Pro PB-10400 Power Bank, 5V / 10,4Ah as a power source is connected to a wireless network in a Starbucks Coffee shop. Most likely, this does not work with a Raspberry Pi 3 Model B+ due to its higher power consumption.

Question #21:
I can’t get tethering to work. What’s wrong with it?
Answer:
It is crucial that your TorBox does receive enough power. The tethering option is the last choice which you should use (and probably this option will be removed in the coming up TorBox version). The problem is that the attached smartphone charges its battery as soon as it is connected to the USB port of your Raspberry Pi). This could lead to an underpowered Raspberry Pi, which could lead to various unforeseen behaviors (see the two question/answers above). For that reason it is recommended to charge your smartphone on another power source, to set up a personal hotspot and to use the “Wireless-internet to wireless-clients” or the “Wireless-internet to cable-clients” menu entry.

Whoever wants to give a try: using tethering is simple. For example, in case of an iPhone: unlock your iPhone, but let the personal hotspot disabled for the time being and connect your iPhone with your Raspberry Pi’s USB port. Choose to trust your iPhone (necessary!). Enable personal hotspot on your iPhone (USB only). Finally, in the “TorBox menu”, use entry number 7 or 10, depending on how your client is connected to your TorBox.

Question #22:
When I’m connected with TorBox and use the Tor Browser on one of the clients, isn’t that a risk for my security/anonymity (“Tor over Tor” scenario)?
Answer:
The necessary level of security/anonymity is not for all users the same and highly dependent on your threat model. Do you want to protect yourself from data theft in a public network (e.g., in a hotel), or do you want to avoid government censorship and keep your destination addresses secret, or do you want to remain anonymous to a site operator when accessing the site, possibly even to an international intelligence service? This sentence already contains four different main scenarios! Also, the need for protection and the consequences of revealing identity must be taken into account. This is the reason why we warn on the main page that although security and overcoming censorship are relatively easy, to stay anonymous, however, is difficult. Malware, Cookies, Java, Flash, Javascript, and more will most certainly compromise your anonymity. Even the people from the Tor Project themselves state that “Tor can’t solve all anonymity problems. It focuses only on protecting the transport of data.” Therefore, it is strongly advised not to use TorBox if your well-being depends on your anonymity. In such a situation, it is advisable to use Tails (read here, here and here why).

By default, Tor is using three hops.
By default, Tor is using three hops.
When a user connected to TorBox uses the Tor Browser, the data stream goes through two circuits, which means that you get six hops instead of three. It is not guaranteed that you’ll get three different hops – you could end up with the same hops, maybe in reverse or mixed order. The Tor FAQ discusses the use of more than three hops and states that “without further protections, it seems likely that an adversary can estimate your path length anyway”. This would mean that security would not be compromised in a “Tor over Tor” scenario (the data stream is still encrypted). However, if an adversary could track your data to the Tor network and the data from the Tor network, he might be able to correlate the two data streams and break your anonymity. However, the problem of correlation exists regardless of the number of hops. For an adversary that can monitor and analyze the entire data flow on the internet, the correlation between input and output is a general problem. However, the effort involved should not be underestimated. Usually, it is behavioral errors that lead to a breach of anonymity and not a data correlation. Based on the design of Tor, the file size of a package is always the same because Tor sends data in chunks of 512 bytes. There is no specific signature, which would indicate more encryption layers. As long as the encryption of the layers is not broken, how should an attacker know that there are not three but six hops?

What does that mean? By design, Onion Routing doesn’t care about the content in the data packages – these are chunks of 512 bytes. More hops, in whatever order, don’t break the encryption layers. Traffic correlation, in theory, could be a problem for anonymity, not only in a “Tor over Tor” scenario. However, the amount of work for the adversary should not be underestimated and can probably only be implemented in the case of an internationally operating intelligence service. For these reasons, we believe that “Tor over Tor” does not pose a risk to a user’s security, and the risk of maintaining anonymity is not significantly increased.

Question #23:
If I have two or more clients, let’s say device 1 and device 2, connected to the TorBox will it intelligently make sure each client has its own tor circuit?
Answer:
Yes, each client has its own circuit. However, all applications on the same client use the same circuit. For example: if you open Firefox and Chrome and check your connection, both browsers on the same machine have the same external IP. In contrast, in the Tor Browser, every new domain gets its own circuit — this is an advantage of the Tor Browser. TorBox changes the circuit (middle and exit node) all 10 minutes (that’s the default for Tor).

Leave a Reply