tor-relays October 2017

tor-relays@lists.torproject.org

86 participants
56 discussions

ansible-relayor, how to ?
by Petrusko 01 Apr '18

01 Apr '18

Hey! I'm planning to try the "ansible-relayor" to deploy some Tor relay instances. If I'm not wrong, it's a main goal ? 2 instances / IP... (soooory for being really noob about this!!!) But I'm lost... not found a tutorial, step by step, you know the tutorial so loved by all noobs! For now, on a fresh Debian8 install, there are : - tor 0.2.9.8 (fresh install from depo, client is ok when opening log file) - ansible - ansible-galaxy install nusenu.relayor - git clone https://github.com/nusenu/ansible-relayor (the folder is stored in my /home...) Will it configure (automatically) many torrc file per instance ? +every key files /relay ? (I'm not too much lost!) Do have I to do this install on every server built ? Or relayor can manage few servers on different locations ? Command lines list use this tool if available ? Many thx for help !!! (and hard work for this tool :) -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5

6 9

Decline in relays
by David Goulet 26 Dec '17

26 Dec '17

Hello everyone! Since July 2017, there has been a steady decline in relays from ~7k to now ~6.5k. This is a bit unusual that is we don't see often such a steady behavior of relays going offline (at least that I can remember...). It could certainly be something normal here. However, we shouldn't rule out a bug in tor as well. The steadyness of the decline makes me a bit more worried than usual. You can see the decline has started around July 2017: https://metrics.torproject.org/networksize.html?start=2017-06-01&end=2017-1… What happened around July in terms of tor release: 2017-06-08 09:35:17 -0400 802d30d9b7 (tag: tor-0.3.0.8) 2017-06-08 09:47:44 -0400 e14006a545 (tag: tor-0.2.5.14) 2017-06-08 09:47:58 -0400 aa89500225 (tag: tor-0.2.9.11) 2017-06-08 09:55:28 -0400 f833164576 (tag: tor-0.2.4.29) 2017-06-08 09:55:58 -0400 21a9e5371d (tag: tor-0.2.6.12) 2017-06-08 09:56:15 -0400 3db01d3b56 (tag: tor-0.2.7.8) 2017-06-08 09:58:36 -0400 64ac28ef5d (tag: tor-0.2.8.14) 2017-06-08 10:15:41 -0400 dc47d936d4 (tag: tor-0.3.1.3-alpha) ... 2017-06-29 16:56:13 -0400 fab91a290d (tag: tor-0.3.1.4-alpha) 2017-06-29 17:03:23 -0400 22b3bf094e (tag: tor-0.3.0.9) ... 2017-08-01 11:33:36 -0400 83389502ee (tag: tor-0.3.1.5-alpha) 2017-08-02 11:50:57 -0400 c33db290a9 (tag: tor-0.3.0.10) Note that on August 1st 2017, 0.2.4, 0.2.6 and 0.2.7 went end of life. That being said, I don't have an easy way to list which relays went offline during the decline (since July basically) to see if a common pattern emerges. So few things. First, if anyone on this list noticed that their relay went off the consensus while still having tor running, it is a good time to inform this thread :). Second, anyone could have an idea of what possibly is going on that is have one or more theories. Even better, if you have some tooling to try to list which relays went offline, that would be _awesome_. Third, knowing what was the state of packaging in Debian/Redhat/Ubuntu/... around July could be useful. What if a package in distro X is broken and the update have been killing the relays? Or something like that... Last, looking at the dirauth would be a good idea. Basically, when did the majority switched to 030 and then 031. Starting in July, what was the state of the dirauth version? Any help is very welcome! Again, this decline could be from natural cause but for now I just don't want to rule out an issue in tor or packaging. Cheers! David -- HiTVizeJUSe9JPvs6jBv/6i8YFvEYY/NZmNhD2UixVY=

9 13

ymkeo offline
by René Ladan 28 Nov '17

28 Nov '17

Hi, due to hardware problems my node ymkeo 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D will be offline for an undetermined amount of time. René

1 1

Testers needed for Nyx beta release
by Damian Johnson 07 Nov '17

07 Nov '17

Hi all! After five years Nyx (previously known as arm) is getting a far belated update. Under the covers the whole codebase has been rewritten from scratch, but for users things look much the same. One of those cases where... "When you do things right, people won't be sure you've done anything at all." -Futurama Main changes are... * Python 3.x support. * New website: https://nyx.torproject.org/ * Bandwidth graph now prepopulates when you start up, so you have a graph right away. * Connections are now available without togging DisableDebuggerAttachment in your torrc. * Support for showing IPv6 connections. * Dialog for picking tor events to log, rather than an arcane letter flag input. * Improved efficiency of log deduplication by multiple orders of magnitude. As such verbose logs no longer peg your CPU. * Richer control interpreter, including a python prompt like IDLE. * Removed features that frequently confused users such as the relay setup wizard and torrc validation. * Modernized dependencies. Nyx now uses Stem rather than TorCtl (which was deprecated in 2011). Our ducks should finally be in a row for release, but this being a full rewrite I'd like to start with an open beta to work out anything I might have missed. Would relay operators mind giving Nyx a whirl? To give it a try simply ensure you have a control port available in your torrc... ControlPort 9051 CookieAuthentication 1 ... and run the following... % git clone https://git.torproject.org/stem.git % git clone https://git.torproject.org/nyx.git % cd nyx/ % ln -s ../stem/stem stem % ./run_nyx Thanks! -Damian

17 71

Running both Transmission server and Tor relay
by Ch1keen 06 Nov '17

06 Nov '17

Transmission is the open source torrent application which supports web-based interface. So when users upload torrent files from other computers to that server, it automatically downloads files written in torrent files. I used that at my home server, but I'd like to use my server as Tor relay also. But as many knows, running BitTorrent over Tor is really bad idea. It seriously harms security of Tor network. So I thought about the solution about how to use them simultaneously. 1. One machine, Two services. If that situation not harms the security, I will use them on one machine. 2. Two machines, Two services. Running that services one machine to one service to avoid the crashes between two. 3. Gave up running one service. If really no way to run both, I will gave up running Transmission service. Which could be best solution I will make? Sent from ProtonMail mobile

5 6

Monitoring multiple relays
by Xza 01 Nov '17

01 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I have a couple relays / exits running. Now my question is : how do you manage them is there any dashboard or CLI tools to manage them ( statistics, ect.. ) I know the cli tool specially for Tor "arm" Thanks alot. - -- PGP : 29A4CE52 -----BEGIN PGP SIGNATURE----- iQI4BAEBCgAiGxxEbyA8eWFuZGVyZXNvbkByaXNldXAubmV0PgUCV0SJlwAKCRBI of/XNyszSvv/D/9VtjI+bmiqK53v//StUbmpYjgQjYheYvwktFld+2XDURh52dmU sbk3lab2RS1eQJxjV0BVXMF9O2JUAlp4NA2UMpj8ZJlCk0h1S6p2o4/sAlsrHr8Z nb67HiaRIyEvi9cQiXFtDtK/onAkEuKskolyvh3ysJRRUubHSX1z8WuNJIc4xyGH ZpSLPGUOO6qI7mM8ztS0muEy1khmkHgtlyHi2l4K/NsW3I90cV3w6Db2AEnV6v1c tsfehqLExsHUdEo0U3hHU7yY1p2fzD5Z+C0tgVKTnP5Zus/Vr9OH/zFwxneo0E7a 5FHdnCZnNIG9W32uQgjDdmBEv/YFEd0um/vMWFGUehFANSt+DIps7E+AjwiJwm2i ov97JJurQkrSMX7ZchTEsy720Ju272olp2eDiHaXXTK2TkxcEq+d1gZfj7CXycPW 6mCrj6L6URJAZ34GJQfFFjv8QbFmKkAvGhxl/O8KXRbXxedbLH7PY73jmFjJcmxO +KnSeyqMe1KbzazYyFydP+VmgI2k1IlO89l8Jq1Gq9f2KOPY9UKFZjGDKLS0xGZW EnqU/KUINcrGejYFT8nYNxA+OFTd/ZGIX5qP4Vo5NsZ/pDLZjdxIcvHx1jjZbER+ 5Ku2bihm2KTNAGoYDqB3LGCm+QdEFG/p573xQCcXPk92GyhMJDi9EMPDgA== =mTa0 -----END PGP SIGNATURE-----

8 8

Exit offline
by D.S. Ljungmark 01 Nov '17

01 Nov '17

Sadly, we had some issues and had to take the modio exit offline for a while. We were seeing interesting traffic spikes on ipv6, and the pfsense firewall couldn't handle the traffic properly, so the relay will have to be offline until we got a replacement firewall in place. Try not to miss us too much. Regards, D.S.

1 1

stability of "Sandbox" feature
by fatal 31 Oct '17

31 Oct '17

Hey, the Tor manpage still states, that "the [sandbox] option is currently an experimental feature". How 'experimental' is it with e. g. Debian Stretch and using the torproject repo? Give it a try, or wait some more time? tnx f.

2 1

relayor v0.3.0 is released
by nusenu 31 Oct '17

31 Oct '17

Hi, relayor v0.3.0 has been released. https://github.com/nusenu/ansible-relayor Whether you run a single or many relays, relayor helps you with running relays with minimal effort (automate everything). Introduction to get you started: https://medium.com/@nusenu/deploying-tor-relays-with-ansible-6612593fa34d Main benefits for a tor relay operator ====================================== * automation - no more manual setup tasks * security: offline Ed25519 master keys every tor instance is run with a distinct user * automatically makes use of IPv6 IPs (if available) * automatic tor instance generation (two by default - configurable) * enables tor's Sandbox feature by default on Debian-based systems * easily choose between alpha/non-alpha releases * easily restore a relay setup * easily choose between exit relay/non-exit relay mode * automatic deployment of a tor exit notice html page via tor's DirPort * automatic MyFamily management Supported Operating Systems ---------------------------- Debian 8, 9 and Debian Testing OpenBSD 6.1 FreeBSD 10.3, 11.1 HardenedBSD 11 Ubuntu 16.04 CentOS 7 Fedora 26 Notable changes since v0.2.1: ------------------------------ - enable tor's Sandbox feature by _default_ on Debian based systems - add support for automatic use of OutboundBindAddressExit via simple on/off boolean (opt-in) - add support for HardenedBSD - add support for tor alpha releases on FreeBSD/HardenedBSD - add support for more torrc options - performance improvement due to the use of dynamic includes (ansible) NOTE: The minimal required ansible version has been increased to 2.4.1 due to show-stopper bugs in older versions. regards, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

1 0

Maximum of 2 Tor Instances per IP-Address (?)
by Petrarca 31 Oct '17

31 Oct '17

I read a few times at different places that there is a maximum of two Tor instances that can be run over one public IP address. My questions: 1) Is this statement true? 2) Is there an easy workaround maybe? 3) Just out of curiosity: what is the background for this limitation (if it is true)? Background: I was thinking about running several things on the onion network, e.g. one or more relays (maybe on different platforms?), hidden services (like wordpress, nextcloud), private tor client/access, etc. That would be all running over one internet connection with one WAN IP address with sufficient bandwidths. I probably could set most of it up on one platform/device but I think it might be better to implement them on separated devices rather (even different physical devices). Any comments are welcome - I'm always happy to learn :-) but

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays October 2017