21

The issue The packages we build for deb.tpo are compiled for various Debian and Ubuntu architectures. These currently are amd64, i386 (x86-64 and x86), and two arm ports: armel and armhf. Arm CPUs come in different versions, and newer versions generally have more features. The arm ports of Debian differ in what kind of CPU they need as a minimum. In ...


5

Raspberry Pi is good for this. Add the repository, install Tor and configure. You can clone the memory-card and put it in a new one for easy setup of multiple Raspberry Pi's. For updates just make a cron job that updates packages every X day. Then the Pi will pull the latest updates without the user having to do anything.


5

Linostar's answer is on the right track, but missed the Tor version you specified. You should update to at least the 0.2.5.x series for Tor to try and detect out of memory situations and handle them smartly. I'd suggest upgrading to either 0.2.5.x or even 0.2.6.x if you don't mind an alpha to se what happens.


4

I've built meek-client for RPi and RPi 2 at here, and I altered the provided install script a bit at here to automatically install meek-client and use meek-amazon. Install via curl -fsSL https://raw.github.com/bbs4us/onion_pi/master/setup.sh | sudo bash


3

This info seems obsolete. On the 'Pi: sudo apt-get install tor ...now results in a working install. (Of course, you must appropriately edit torrc and then restart the service.)


3

It would depend on what distro you are using. I have Tor running pretty well on ARCH on my PI, there are good instructions here. I did have an issue with "Problem with user value" but that is also detailed on the how to Other than that it seems just the same as any other Linux OS, so you can follow the usual instructions


3

The error message says: Alternatively, to build without manpages, use the --disable-asciidoc argument when calling configure. When you use debuild you can't just enter configure --disable-asciidoc. You'll have to edit the file debian/rules. On line 22 of the file there is a section which deals with configure options: override_dh_auto_configure: ! [...


3

It installs with no issue, enable SSH, login as root, and type apt-get install tor As for memory usage, many people run it on routers, which have only 32MB of memory. There is no GUI for setting it up AFAIK, and will require the usual command line tinkering – if you are comfortable with that. Warning: I've not personally tried using it, only installing ...


2

Internet traffic (HTTP) is transmitted via port 80. Tor and Apache (or another web server) do not share ports well, because of problems with intercepting each others traffic, etc. You can either change the port of your web server, which I don't recommend, or change the port of Tor.


2

You set values for RelayBandwidthRate and RelayBandwidthBurst in your torrc. RelayBandwidthRate is set to 500 KB. This translates to 500 kilo Bytes per second, which is 500*8=4000 Kilo Bits per second. arm somehow rounds this number down to 3.9 Mb/s. On your screenshot that shows the torrc inside arm you changed the number to 250 KB and arm shows 2 Mb/s. ...


2

Found a solution! I Formatted the SD card using SDFormatter, and reburn Raspabian using Win32DiskImager - in other words, reinstalled Raspabian. And then: sudo apt-get update install tor just installed tor with the full torrc file. I guess that it's a good solution for most of you with this problem, but because i used my Pi as a Tor Hotspot, it wasnt ...


2

Despite setting the SOCKS5 proxy in Firefox, I could not view web pages blocked in my country because Firefox was still doing DNS lookup out of my router, rather than through Tor. Asking on the tor-relays mailing list, I learned this solution. Type "about:config" in the address bar, and hit enter. Search for the item "network.proxy.socks_remote_dns" and set ...


2

The guide makes Apache run as system user debian-tor: export APACHE_RUN_USER=debian-tor export APACHE_RUN_GROUP=debian-tor but the permissions on /var/www doesn't get set to debian-tor as well so probably it's a permission problem. BUT BESIDES THAT: You shouldn't follow that guide. He configures the HiddenServiceDir to be /var/www which is also ...


2

I've been running a Tor relay and hidden service website for over a year on a Pi. one thing I recommend is that you buy an SD card twice the size you need for the Pi image. The empty space is used for wear leveling of the flash memory.


2

If you are using Raspbian/Debian, you may want to investigate the cron-apt package, instead of making a custom cron job for updates.


2

I've found a simple solution - it seems this problem only appears on 0.2.3.x. After upgrading to 0.2.4.x, the problem went away completely. Incidentally, the CPU usage efficiency seems to have been drastically improved in the new version. This is still somewhat problematic, as Tor in the standard Raspbian repos is still at 0.2.3.25. Fortunately, it's ...


2

The occurences in torrc are to : Bind SOCKS listener to port 9100 on address 192.168.0.1 via SOCKSPort 192.168.0.1:9100 directive Allow connections from 192.168.0.0/16 subnet to the SOCKS proxy via SOCKSPolicy accept 192.168.0.0/16 The problem you're experiencing is that INSIDE a Wi-Fi network devices can't talk to the Raspberry Pi, i.e. the apps running ...


2

Do you see a message in the Tor notices log that says the ORPort and/or DirPort are confirmed as working? It should log "Self-testing indicates your ORPort is reachable. Excellent." Check your port forwarding first. If that appears to be setup correctly then it could be due to a similar situation I was in. I had needed a Dynamic DNS before my ORPort/DirPort ...


2

Tor usually writes data into the DataDirectory. This includes information about the network, status information about your relay and other information. Those files are regularly updated. You can move the DataDirectory to some directory outside of your SD card if possible. Another way is to set AvoidDiskWrites 1 in your torrc. If set Tor will try to write ...


2

RPi{1,2,3} are ARM architecture SoCs, Tor Browser is currently only available for x86 (i386) or x86_64 (AMD64) on Linux, there is no Tor Browser for any ARM platforms. As such you won't be able run Tor Browser natively on the RPi. If you want to follow the progress or contribute to the porting of Tor Browser to ARM see #12631 and similarly see #10972 for ...


2

There may be several error due to the configuration. 1) run tor in terminal. Check the output. If it says cannot bind tor, there may be another instance of tor is running. try stop the tor service by: sudo service stop tor 2) After running tor successfully, check what configuration file is read by tor. Maybe you have edited the wrong configuration file. ...


1

No problem! Doing it myself regulary! You need a gcc and g++ and the next libraries, compiled in the order of listing here : Zlib. You need it to compile OpenSSL with compression support OpenSSL. Take a stable source if you're not PRO with source building Libevent. Take a 2.0 current version and go on In configure I strongly recommend you to install in a ...


1

Tor over Tor is always worse, rule of thumb: mo' hops, mo' problems. Instead of using your RPi as a "Force Everything Through Tor" transproxy box, you should use it as an isolating proxy. Your laptop/desktop connects to the Pi over Ethernet (this is important!). Then, your Pi connects to some wifi network with internet access and runs an instance of Tor. ...


1

First check if the binary is executing - through ssh try running : /usr/local/bin/meek-client --help You should see something like Usage of /usr/local/bin/meek-client: -front="": front domain name if no front= SOCKS arg -helper="": address of HTTP helper (browser extension) -log="": name of log file -proxy="": proxy URL -url="": URL to ...


1

There is no problem as you are not a exit node. Tor will check if your DNS server was hijacking DNS failures, through looking up random domain names and see if it always gets the same address (generally an error page), even if you are not an exit node. Also Tor will correct DNS hijackings itself, so nothing needs to be done. Not about raspberry-pi either.


1

You can start by looking at OnionPI, that is a way to set up such a access point. https://learn.adafruit.com/onion-pi/overview Also, you do have routers with built in tor capabilities for wifi. I have one of these, and that's the 'Netgear WNR3500L v2' which I flashed with Tomato USB - http://tomatousb.org/ That let's me set up a wifi which is ...


1

It may or may not be an attack, but my personal opinion is that Tor isn't guessing the right values for some parameters like MaxMemInQueues (like it was setting them too high, then too low later). Try setting the 2 parameters MaxOnionQueueDelay and MaxMemInQueues yourself and see if the performacnce becomes more stable. It may help also to limit the bandwith ...


1

Although the answer has been accepted, I have some sort of update: While everything "weasel" said is true, we now have the Raspberry 2, that works perfectly as it features an ARMv7 CPU. In other words: Go ahead and add the Debian armhf repo of the Tor project and it will result in an up-to-date setup that's working like a charm (as long as you use a ...


1

I found a complete tutorial for Raspbian with prebuilt binaries for the latest version. Also, full instructions for building from source are provided. You can catch them here: http://unsuspectingbit.com/tutorial-private-anonymizing-proxy-raspberry-pi-tor-based/ [on Saturday11April2015 Seems to be a dead link: If anyone has a more current link or if the new ...


Only top voted, non community-wiki answers of a minimum length are eligible