Version 10 (modified by proper, 9 years ago) (diff)

new "Freenet inside the Tor-Workstation"

TorBOX Homepage


TorBOX can work together with any other suited Anonymizing Networks, either in addition, this means the other network will be tunneled through Tor. Also Tor can be completely exchanged with any other suited anonymizing network.

Note that all networks differ in their thread model and security! Research before you start using them.

Rudimentary TorBOX Support for Other Anonymizing Networks

Although the project's name TorBOX does not implicate it, TorBOX is agnostic about which Anonymizing Network is being used. The project name has historical reasons. TorBOX started with Tor as anonymizing network. The idea, that also other anonymizing network could be used, came much later. Can you think of, any better name to describe TorBOX? And even any better name to describe the anonymizing network agnostic?

At the moment TorBOX's support for Other Anonymizing Networks is only rudimentary and not as good as supported like the Tor network. Of course TorBOX developers respect other anonymizing networks, their developers and their users. They are simply more accustomed to the Tor network, which is also a personal preference. It's also very hard to be equally interested, educated and to stay up to date with all other anonymizing networks at the same time.

As soon as a new developer, who actively supports the other anonymizing network, joins the TorBOX project, this particular anonymizing network can be equally supported like the Tor network. For example, there is not much point in separate a 'JonDoBOX', if most of the knowledge and code is shared. Almost anything, even the project name, could be revised.

Using the i2p anonymizing network

Unfortunately it is not possible to reliably replace the Tor network with the i2p network. The i2p network is mainly designed to host all services inside the i2p network. We have to update the Tor-Workstation's operating system and software packages. That is not possible with i2p. Outproxies exist (http, https and socks), but too few of them. And they are not suited for use with TorBOX. They are too unreliable (too often offline). At the moment (March 2012) there are no working https or socks outproxies, which we could use for apt-get. I2p can be used as an addition to TorBOX.

If you simply want to browse eepsites, see Browsing eepsites using i2p inproxies on Tor-Workstation, otherwise you can also install i2p directly inside Tor-Workstation or directly on the Tor-Gateway.

Browsing eepsites using i2p inproxies on Tor-Workstation

There are several i2p inproxies, those are similar to tor2web. Simply use your Tor Browser. For example awxcnx or simply add '.to' after '.i2p'. For example, instant of 'http://forum.i2p' you can use ''. Note that you will loose the end-to-end encryption to the eepsites, which i2p would provide, if you would install it directly inside Tor-Workstation or if you would use it the ordinary way. Depending on if the inproxy uses http (unencrypted), https (or is reachable through a hidden service), also Exit Nodes Eavesdropping applies. In any case, the i2p inproxy admin can see, all your traffic into the i2p network and there is no way to prevent that.

Installing i2p inside Tor-Workstation

It is possible to run i2p inside the Tor-Workstation.

  • Anonymity is provided by Tor.
  • I2p webinterface works normal inside Tor Browser. No need to install a graphical user interface on the Tor-Gateway.
  • Eepsites (.i2p) can be reached directly from Tor Browser.
  • I2p's end-to-end encryption will be used like usual.


  • Adds load to Tor.
  • Adds load to i2p.
  • It's slower than i2p directly on Tor-Gateway or the ordinary usage.
  • Incoming connections are not possible, because TorBOX's Tor Workstation is firewalled. 1
    1 If you know to use a hidden service, please add this information.
  • No contribution (leaching) to the i2p network. 2
    2 Sounds worse than it is. Only very little people are expected to use i2p over Tor. I2p offers those options itself. It's not like a leeching mod.

Recommend settings:

  • Tor Browser
  • Network
    • IP configuration: hidden mode (do not publish IP) (There is no need to publish the exit node's IP address.)
    • UDP-Port: completely disable (Not supported by Tor.)
    • TCP: disable inbound (Firewalled) (Only outgoing TCP supported by TorBOX.)
  • Tunnels
    • length (all tunnels): inbound and outbound: 0 (It's faster and less connection interrupts. Anonymity is already provided by Tor. No need to leech from Tor/i2p.)

Installing i2p on Tor-Gateway

Not written yet.

Using the JonDo anonymizing network

Be aware, that the JonDo network is much smaller than the Tor network. However, JonDo might be faster. Also be aware, that JonDo is less secure than Tor, see law enforcement for details.

JonDo inside Tor-Workstation

You can use JonDo over Tor. This could be useful, to circumvent Tor bans. But note Tor Plus Proxy (it adds a permanent exit node, like explained and the article). Not many changes are required. download and install it as usual. You need 'JonDo – the IP changer', either as the gui or console version. You can decide, if you prefer to use JonDoFox or the Tor Browser. If you want to use the Tor Browser, see their help section on how to point Firefox to JonDo.

JonDo on Tor-Gateway

Not finished yet.

Depending on your thread model, JonDo can be potentially used as a replacement for Tor. Prefer the console version of 'JonDo – the IP changer', otherwise you would have to install a desktop environment, which needs a lot of more RAM, CPU and disc space (not possible on most embedded devices).

For free users

Not finished yet.

Free users can only only use port 80 (http) and 443 (https). Socks is only available for paying premium users. Not researched yet, if it's even possible to tunnel everything thought those ports. Also JonDo does not seem to offer a TransPort or DnsPort. For that reason, something like transproxy could be needed.

For paying premium users

Not written yet. Probable easier, see above. If it's possible for free users, then this topic line will become obsolete.


In fact RetroShare is not an anonymizing network, it is a friend-to-friend (F2F) network, or optionally a darknet. It has a very different audience and thread model. RetroShare does not support using an outproxy yet, for this reason, it can not replace Tor on the Tor-Gateway. It may be used inside the Tor-Gateway. This would enable you to do things, which are normally potentially dangerous, such as adding random people (from a forum) while staying anonymous. (For example, to join a RetroShare forum.)

At the moment it is not possible to connect to the RetroShare network over Tor. RetroShare relies on UDP, which is not supported by Tor. Yet, RetroShare also has no proxy support. Also torsocks does not help. When proxy support gets implemented, it might be possible.


inside the Tor-Workstation

It seems (in classical sense) that this is impossible. (Tested, freenet installs normally, but even with lowest security settings, no connection will be ever established.) There has been a discussion about this topic. Although it's from 2008, it doesn't look like, the situation has changed or will change. The problem is, that Tor does not support UDP.

The only workaround could be using an SSH server. Buy, administrate and connect the SSH server anonymously though your Tor-Workstation. Install freenet on the remote location and connect from your Tor-Workstation (SSL or SSH tunnel). See the freenet wiki for more information.

on the Tor-Gateway

Can be also potentially only be used parallel to Tor. It's impossible to tunnel Freenet through Tor (see above). Also replacing Tor with Freenet is impossible, as freenet is a separated network, not designed to exit the network. Apt-get couldn't work.

Not written yet.