- tor-relays - lists.torproject.org

The Onion Box v3.0: Web Interface for your Tor relay
by Ralph Wetzel 04 Oct '16

04 Oct '16

5 10

Question about relay speed
by Sheesh 03 Oct '16

03 Oct '16

Hello! I'm running a non-exit relay on my VPS with small amount of traffic/month. That means my advertised bandwidth is ~500 KB/s. I got a new VPS where I want to let a relay run with several MB/s - My question now is: should I let the slower relay run (aka do 500 KB/s positively contribute to the TOR network?) or move my relay key to the new server and run this one only? Thanks in advance!

7 13

Re: [tor-relays] help #3
by teor 02 Oct '16

02 Oct '16

> On 30 Sep 2016, at 14:37, Markus Koch <niftybunny(a)googlemail.com> wrote: > > Installed with apt-get and started simply as a demon aka service tor start > Thank you for helping Have you tried: >>> sudo su debian-tor --shell /bin/bash --command "ulimit -Sn" >>> sudo su debian-tor --shell /bin/bash --command "ulimit -Hn" What are the file descriptor limits set to? How much RAM does the system have? What are the TCP buffer limits in the kernel? Here's some background: In Tor, there are the 4 C/Linux error return values that can trigger that message: EMFILE ENFILE ENOBUFS ENOMEM On my system, "man 2 intro" lists them as: Too many open files...the limit on the number of open files per process... Too many open files in system. Maximum number of file descrip- tors allowable on the system has been reached... No buffer space available. An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full. Cannot allocate memory. The new process image required more memory than was allowed by the hardware or by system-imposed mem- ory management constraints… T > > Markus > > > > > > > 2016-09-30 23:33 GMT+02:00 teor <teor2345(a)gmail.com>: >> >>> On 30 Sep 2016, at 14:01, Green Dream <greendream848(a)gmail.com> wrote: >>> >>> Have you double-checked the ulimit was applied correctly? Including >>> making sure it's applied to the user account running Tor? Here's how I >>> do that on Ubuntu/Debian, assuming the user account is "debian-tor": >>> >>> sudo su debian-tor --shell /bin/bash --command "ulimit -Sn" >>> sudo su debian-tor --shell /bin/bash --command "ulimit -Hn" >>> >>> Those should return the actual hard and soft limits being applied to >>> the debian-tor user. In my case it returns 64000, but you'll just want >>> to make sure it's what you're expecting. >>> >>>> nothing works and now I am running out of ideas >>> >>> It would be easier for people to help if you elaborate a bit -- >>> perhaps the exact commands you've already tried and the log messages >>> (if there are any other error or warning messages besides the one you >>> already listed). >> >> The debian packages should set the appropriate file descriptors for you. >> How are you launching your tor services? >> >> T >> >> -- >> Tim Wilson-Brown (teor) >> >> teor2345 at gmail dot com >> PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B >> ricochet:ekmygaiu4rzgsk6n >> xmpp: teor at torproject dot org >> >> >> >> >> >> >> T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org

2 1

Help configuring a relay on OS X
by Surf Norway 01 Oct '16

01 Oct '16

A few years ago I tried setting up a relay as a way to contribute back to the community, I have fast symmetrical fiber and a Mac mini running as a light file server. I never was able to get it to work and gave up. I recently bumped up the RAM to max and put an SSD drive in, upgraded to 10.11 and thought I'd give another go at setting up a relay. I've installed Xcode and the command line tools, installed MacPorts and used that to install Tor. I configured the torrc file as best I could and expect that's probably the problem with my setup. When I start Tor (v0.2.8.8) it identifies the OS, reads the torrc file and grabs a chunk of memory for MaxMemInQueues. Then it opens OR listener but on an invalid IP (0.0.0.0), complains that it can't write to the log file (permission denied), and closes partially-constructed OR & directory options. Before I go and change the log file permissions, what user should I be running as when I start Tor as a relay? Ideally I want it to start with the system and run by default in the background and uncommented "RunAsDaemon 1" in the torrc file. The mini sits and serves files normally and isn't usually in use as a normal computer/console. When I run Tor myself it's from a different machine in order to use the Tor browser. All I want the mini to do is act as a relay, nothing more. Thanks for any help. Sorry for the newbie question, but guess what... Surf

2 1

help #3
by Markus Koch 30 Sep '16

30 Sep '16

me again ... I need the knowledge of the almighty tor operators. I set up three new and shiny tor exists and got a not so shiny error message: [WARN]Failing because we have 4063 connections already. Please read doc/TUNING for guidance It was already in this mailing list: http://archives.seul.org/tor/relays/Feb-2016/msg00060.html I "tuned" it with ulimit https://gitweb.torproject.org/tor.git/tree/doc/TUNING/ and nothing works and now I am running out of ideas and getting pissed. They exits are running a Debian 7 x64 minimal install with the newest tor version. Any ideas how to fix it? Markus

4 4

How to get rid of 'Family' entries?
by theonionbox＠gmx.com 30 Sep '16

30 Sep '16

2 1

Request for Tor abuse complaints
by Sadia Afroz 29 Sep '16

29 Sep '16

Dear exit operators, Can you please share the abuse complaints you received while running an exit? We are researchers from Univ. of California, Berkeley and Univ. of Massachusetts Amherst are interested in understanding what kind of abuse happens through Tor. Thanks to Moritz Bartl from Torservers.net <http://torservers.net/> we analyzed over 1GB of complaints received over 6 years. Here is our preliminary analysis of the complaints: http://www1.icsi.berkeley.edu/~sadia/tor_abuse_complaints.pdf <http://www1.icsi.berkeley.edu/~sadia/tor_abuse_complaints.pdf> We will appreciate if you can share the abuse complaints you received. It will be valuable for us to better understand the abuse of Tor and to find solutions to reduce abuse. Best, Sadia

9 17

Hide TOR exit on my external IP?
by Volker Mink 29 Sep '16

29 Sep '16

2 2

"Potentially dangerous relay groups"
by nusenu 28 Sep '16

28 Sep '16

pa011(a)web.de wrote: > there is that list of "potentially_dangerous_relaygroups" you published. > Could yo please emphasize a bit more on what brings a relay on that list, apart from incorrect given MyFamily which doesnt seem to be always the case. > I mean I see quite a few well respected names on that list ? to quote from https://github.com/ornetstats/stats (1) "dangerous" in the sense that a tor client might has a chance to use more than one of these relays in a single circuit (2) these relays are aggregated based on contact information (3) if their groupsize is bigger than their effective family size and they are operated in more than one /16 network block they are listed (4) this list might contain false-positives (contact information is not authenticated) Does that answer your question? I probably should also filter entries where two out of guard_prob, middle_prob and exit_prob are 0 since that means that (1) is never the case - iff onionoo is right about these probabilities.

12 23

log message: [WARN] Failing because we have X connections already.
by David S 27 Sep '16

27 Sep '16

greetings! i setup a new tor exit server and am seeing this in the log messages: 18:25:01 [WARN] Failing because we have 1352 connections already. Please read doc/TUNING for guidance. [11430 similar message(s) suppressed in last 21600 seconds] any ideas why? this is happening on a shared VPS, running ubuntu 16.04 and tor v0.2.8.8. i'm starting to think it's some limitation by the VPS provider. uname -a shows a old kernel (possibly centos 6): Linux km14133-25 2.6.32-042stab113.21 #1 SMP Wed Mar 23 11:05:25 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux i've made sure tor has enough "max open files" available via limits.conf: # cat /proc/$(pgrep tor)/limits|grep "open files" Max open files 65536 65536 files i'm starting to scratch my head. maybe i should do some intense debugging on this box.. cheers, david

3 3