tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

r-pi tor relay fails after debian stretch update
by jah knee 18 Aug '17

18 Aug '17

hi i am running a relay on a raspberry pi v.1. it ran along just fine until i updated to debian stretch. i have reviewed the config to see what could be wrong, but i cannot find anything. this is what gets put in the logs over and over: Aug 18 09:52:41.000 [notice] Tor 0.2.9.11 (git-572f4570e1771890) opening log file. Aug 18 09:52:41.116 [notice] Tor 0.2.9.11 (git-572f4570e1771890) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0f and Zlib 1.2.8. Aug 18 09:52:41.122 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Aug 18 09:52:41.122 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Aug 18 09:52:41.123 [notice] Read configuration file "/etc/tor/torrc". Aug 18 09:52:41.194 [notice] Opening OR listener on 0.0.0.0:9001 Aug 18 09:52:41.199 [notice] Opening Directory listener on 0.0.0.0:9030 Aug 18 09:52:41.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Aug 18 09:52:44.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Aug 18 09:52:45.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Aug 18 09:52:48.000 [notice] Your Tor server's identity key fingerprint is <X> Aug 18 09:52:48.000 [notice] Bootstrapped 0%: Starting Linux <hostname> 4.9.41+ #1023 Tue Aug 8 15:47:12 BST 2017 armv6l GNU/Linux i've been thinking about moving this node to another machine as i've read on this list how underpowered machines do not really help the network [i can't say i could repeat the details of the arguments, but they made sense to me when i read them]. but i'd still like to contribute ... any help or pointers appreciated. dankon

2 1

blocking >1 connections per ip address onto Tor DirPort
by Felix 17 Aug '17

17 Aug '17

Hi everybody >>> Does a particular Tor server/client will open more than 1 >>> connection at a time from to the DirPort ? >> If you're worried about denial of service issues on the DirPort, >> maybe the simple answer is to turn off the DirPort? I think the >> only real impact might have something to do with whether old >> clients believe that you're a usable guard. > understood - removed those iptables rules Good discussion. My experience is protecting the dirport makes sense to avoid ddos attempts. During my Debian times this rule worked fine for me: /sbin/iptables -A INPUT -p tcp -d $IPEXT --dport 80 -j ACCEPT -m limit --limit 5/s --limit-burst 50 On FreeBSB I go with something like: pass in on $IFEXT inet proto tcp from !<blockDIR> to $IPEXT port 80 flags S/SA keep state (max 150,max-src-states 50,max-src-conn 50, max-src-conn-rate 20/10,overload <blockDIR>) # release the blockDIR after some hours pfctl -t blockDIR -T expire 7200 # hourly cron job -- Cheers, Felix

1 0

Shirts
by Sebastian Urbach 17 Aug '17

17 Aug '17

Good Morning, I was asked recently by friends & family if i could get the traditional Tor shirt for them. I showed them the new Tor shirt and well let's say they really want the traditional shirt. Any chance to get it anywhere ? torservers.net is just offering size M /L and that's not going to work ... Thanks -- Sincerely yours / M.f.G. / Sincères salutations Sebastian Urbach --------------------------------------------------------------------------- Those who surrender freedom for security will not have, nor do they deserve, either one. --------------------------------------------------------------------------- Benjamin Franklin (1706-1790)

2 2

Relay Operators Meetup at BornHack
by Alexander Færøy 16 Aug '17

16 Aug '17

Hello relay operators, DrWhax and I will host a small relay operators meetup at the upcoming BornHack festival in Denmark. If you happen to be around and want to join please keep yourself updated with the event schedule on the BornHack website or track the meetup event directly at https://www.bornhack.dk/bornhack-2017/program/tor-relay-operators-meetup/ :-) All the best, Alex.

1 0

What causes circuits to collapse?
by Igor Mitrofanov 16 Aug '17

16 Aug '17

Hi, I have configured a Tor bridge to go through a particular Tor guard relay (that I also own), as an experiment. Upon initialization I am getting this warning: "Your guard [fingerprint] is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 52/275. Use counts are 67/67. 268 circuits completed, 0 were unusable, 217 collapsed and 1 timed out. For reference, your timeout cutoff is 60 seconds". Both relays are running Tor 3.0.10. I have never received this warning before. How do I interpret the numbers above, and debug the issue? The guard is far from saturating its network bandwidth. It has 98% idle CPU and plenty of free memory. I am not running any attacks against it. It does use a tuned-up sysctl.conf but I have never had any problems with it. "tcpdump icmp" does not show anything interesting. There are no warnings in the guard's log. Thanks, Igor

2 1

Re: [tor-relays] keepyourprivcay: Introducing a new 100 mbit/s relay
by Keepyourprivacy 16 Aug '17

16 Aug '17

Another 100 mbit/s relay has been added, located in sweden. MyFamily entry set in torrc. https://atlas.torproject.org/#details/B92CADBD1E9A2F72E64D7DE5A1BF5B2B30DA7…

2 1

IXPs in the United States
by Christopher 14 Aug '17

14 Aug '17

Hello, Emerald Onion (https://twitter.com/EmeraldOnion) is researching Internet Exchange Points in the United States in order to bolster Tor relay deployments within our legal jurisdiction. We have blogged a list of IXPs we've identified so far: https://emeraldonion.org/internet-exchange-points-in-the-united-states/ Please note that Emerald Onion would not be the org to deploy more relays in other cities. We are interested in helping others in those regions become their own ISP. (See https://emeraldonion.org/development/ for related education.) 1. Are there any Tor routers connected to any United States-based IXPs? If so, which ones and who operates them? We know of at least four: a. Calyx Institute on NYIIX https://www.peeringdb.com/net/4594 b. XMission on Equinix Ashburn, SIX Seattle, and SLIX https://www.peeringdb.com/net/789 c. Riseup Networks on SIX Seattle https://www.peeringdb.com/net/9021 d. Emerald Onion on SIX Seattle https://www.peeringdb.com/net/14010 2. Is this IXP friendly to Tor? 3. What is the organizational structure of this IXP? Such as corporate-run or community-driven, etc. Please let me know if you have any helpful information. I'm also reachable via Signal. https://yawnbox.com/contact/ Cheers, Yawnbox

1 0

Re: [tor-relays] 60 new neu.edu relays in 16 minutes
by privacy＠ccs.neu.edu 12 Aug '17

12 Aug '17

Hello nusenu, DocTor and OrNetRadar detected that someone added 60 tor relays [1] with your email address in the contact info field on 2017-08-08 between 15:45 and 16:01 UTC. [1] https://nusenu.github.io/OrNetRadar/2017/08/08/a7.html <https://nusenu.github.io/OrNetRadar/2017/08/08/a7.html> Since tor relay contact information is not authenticated I was wondering if these are in fact your relays? (I guess they are) Yes indeed they are ours. We started them all at the same time to make it clear that they are all run but one group of researchers. You obviously don't have to answer but if you want to I'm curious: Are these just temporary relays and part of your research or are they here to stay to increase the capacity of the tor network for more than just a few weeks or months? I assume you are not planing to run them for a longer period of time (>6months), but if you do you: Please consider network diversity when adding that amount of tor relay capacity. All your relays are operated in AS "Online S.a.s" - which is already the second biggest AS in terms of tor network capacity. At this stage we are not planning to run it for more than 6 months or so (but this might change). We understand that your concern is primarily about capacity diversity not trust in "Online S.a.s" since anyway it's already the second largest provider for Tor relays. Our experiments are not related to the traffic (and since all our relays are part of the same family at most one of them would be used in any circuit). We are using Online S.a.s because it it is cheap (I guess it's the same reason why others use it). We will check in the next couple of days if there is an alternative low cost provider. We have also limited our bandwidth but can increase it if more people express interest and it can help (we didn’t want to look like we are trying to attract/intercept traffic). +-----------------------------+-------------+ | AS Name | CW Fraction | +-----------------------------+-------------+ | OVH SAS | 15.95 | | Online S.a.s. | 13.41 | | Hetzner Online GmbH | 7.74 | | Digital Ocean, Inc. | 6.65 | | myLoc managed IT AG | 2.63 | +-----------------------------+-------------+ Also the country (FR) is not ideal from a diversity point of view. :) 14 of our relays are in the Netherlands but will make sure to diversify if we have to restart them. thanks for running relays, nusenu Note: There is nothing wrong with adding 60 tor relays, especially with proper MyFamily configuration as you did. Thank you for the positive note and feedback!

2 2

New Here
by Paul Templeton 12 Aug '17

12 Aug '17

Hi all, Have been running a mirror for a couple of years and haven't had much time to dedicate to and exit node but have finally committed to it. Found a provider that doesn't seem to have a cap on data and it will cost me about five euros a month. Question I have is two fold. First I find that atlas.torproject.org sometime says the node is down but its running and connected. Secondly how dose the bandwidth throttling work. I have set it to 300kbits with 500kbit burst but I can see the in/out traffic staying over 1mb for large periods of time and bursting to 7/8mb. Its not a problem just curios. Regards, Paul torproject.coffswifi.net

5 7

keepyourprivcay: Introducing a new 100 mbit/s relay
by Keepyourprivacy 11 Aug '17

11 Aug '17

Hello fellow operators of tor relays out there! :) I'd like to introduce my new relay, it's called keepyourprivacy and hosted in the Netherlands, at a provider which is known for high uptime and great network connectivity. Because it isn't very cheap, it's not very common used for tor relays, so i think it's a good choice for a better network diversity. :) Sure, i liked the idea of running a cheap relay at Kimsufi or something, but there are so many of this relays out there, which isn't good for the basic idea of Tor. It's running on a dedicated server with an dedicated 100 mbit/s full-duplex uplink, which is only used for Tor. So over 60 TB can be pushed each month. In these days Tor needs more help than ever, because VPN bans becoming more and more common - look at China or Russia for example. https://atlas.torproject.org/#details/59633E5F42DDA009798B173944367D7F50B1B… I'm also playing with the idea to change this relay to an exit node, but i'm a little bit worried about possible legal consequences. I would run it with an reduced policy however, but there is still the risk, that someone is doing fraud - or even worse - transmit child pornography over it. And that's nothing i'd like to be involved with it. But i know that it would help the Tor network even more. But for now, i think the middle relay with high uptime, capacity and with a not so common provider like OVH or online.net will still help the community to improve the connectivity. Let me know your thoughts! :)

6 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays