- tor-relays - lists.torproject.org

handling of MyFamily for an outdated relay
by Toralf Förster 04 Nov '17

04 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Looking at his : I do wonder how to deal with deleting all /var/lib/tor/data2/* files of a Tor relay and running a new one with the same config (but now different key/fingerprint). I added the new fingerprint to the config, which now has 3 entries (the middle is 1 outdated): MyFamily 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA,6EABEBF38CE7E3DF672C4DB01383606FE3EB2215,D11D11877769B9E617537B4B46BFB92B443DE33D Is this the right way ? I'm asking b/c I do see now "Alleged Family Members" here: https://atlas.torproject.org/#details/D11D11877769B9E617537B4B46BFB92B443DE… - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWf3YchccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTuLJAQCAmqnYRI5y4NpShgQp7kcdSTC2 MfrsfHkH3aObifTJ1wD9ERBkJN6zAIY7usN6sPy4VfHzAjkGaMTDLoBlYRA2f1w= =EQTO -----END PGP SIGNATURE-----

2 3

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

Thank you to directory operators
by Tor Node Admin ＠ SechsNullDrei.org 31 Oct '17

31 Oct '17

Good morning, Relay operators often receive gratitude on this list for running relays, but let's not forget the directory operators - those individuals/organizations who are more central to The Tor Network and run their directory servers at a higher personal risk level than the relay operators. Sincerely, Isaac, <mailto:Tor@SechsNullDrei.org> Tor(a)SechsNullDrei.org

3 2

UbuntuCore
by Paul Templeton 30 Oct '17

30 Oct '17

These nodes are popping up everywhere - is this some sort of malware being deployed on systems around the globe? Paul

5 4

Relay flag set counts
by grarpamp 30 Oct '17

30 Oct '17

1 s Authority Fast HSDir Running Stable V2Dir Valid 2 s Authority Fast Running Stable V2Dir Valid 7 s Authority Running Stable V2Dir Valid 270 s Exit Fast Guard HSDir Running Stable V2Dir Valid 58 s Exit Fast Guard Running Stable V2Dir Valid 25 s Exit Fast Guard Running Stable Valid 168 s Exit Fast HSDir Running Stable V2Dir Valid 71 s Exit Fast Running Stable V2Dir Valid 45 s Exit Fast Running Stable Valid 149 s Exit Fast Running V2Dir Valid 15 s Exit Fast Running Valid 7 s Exit Running Stable V2Dir Valid 10 s Exit Running Stable Valid 3 s Exit Running V2Dir Valid 2 s Exit Running Valid 1293 s Fast Guard HSDir Running Stable V2Dir Valid 311 s Fast Guard Running Stable V2Dir Valid 167 s Fast Guard Running Stable Valid 1721 s Fast HSDir Running Stable V2Dir Valid 513 s Fast Running Stable V2Dir Valid 469 s Fast Running Stable Valid 754 s Fast Running V2Dir Valid 200 s Fast Running Valid 96 s Running Stable V2Dir Valid 41 s Running Stable Valid 95 s Running V2Dir Valid 27 s Running Valid

1 0

"Fast" flag definition
by Igor Mitrofanov 30 Oct '17

30 Oct '17

Hi, It looks like 94.7% of all Running relays have the "Fast" flag now. If that percentage becomes 100%, the flag will become meaningless. What were the reasons behind the current definition of "Fast", and are those still valid? If not, should "Fast" become self-adjusting ("faster than 2 Mbps or 70% of all Guard relays, whichever is greater")? Thanks!

3 3