- tor-relays - lists.torproject.org

killall -hup command
by Keifer Bly 04 Jul '18

04 Jul '18

Hello, So recently I rebooted my relay using the killall tor -hup command (while I was trying to mae some changes to my torrc file). My relays uptime was not changed at all by this, having a current uptime of about 6 days. However, I noticed today at http://torstatus.blutmagie.de/router_detail.php?FP=db1af6477bb276b6ea5e7213… My relay lost the stable flag (which it had had for the last about two months). I know not to worry about exactly what flags I have all the time, but it raises the question of what eactly the killall -hup command does? Thanks.

4 5

Turning down my relay from DigitalOcean
by Guillermo Narvaez 03 Jul '18

03 Jul '18

Hello everyone, Sadly I'm stoping the tor daemon in my relay due high cost of bandwidth ($100), in the meantime I start to search an optional hosting. My apologies! -Guillermo

10 11

Contact info obfscation
by Keifer Bly 02 Jul '18

02 Jul '18

Hello, I am aware that email addresses used in the “ContactInfo: “ in a relay operator’s torrc file is publicly listed on the tor relay. However, what I am wondering, is there a way to obfuscate the email address on http://torstatus.blutmagie.de/router_detail.php?FP=db1af6477bb276b6ea5e7213… to appear as “k—f---b--(a)g-ail.xn--com-9o0a or something of the sorts, while keeping the real email address readable for tor cloud to send mail to? It seems like obfuscating the email address in the torrc file would cause it to become unreadable to the tor project as well. Thank you.

10 23

Problem implementing IPv6 and NYX info
by arisbe 02 Jul '18

02 Jul '18

This year I've modified most of my exit relays to function as IPv6 in/out. The process was easy with the exception of two [0], [1]. I requested and received an IPv6 address, netmask and gateway from these ISPs. I then modified my /etc/network/interfaces file as follows leaving the IPv4 lines in tack: iface eth0 IPv6 static address 2a06:1700:0:1b:: netmask 64 gateway 2a06:1700:0:1b::1 ip addr shows the IPv6 address as global. I added a single line to torrc following the IPv4 line: ORPort 9001 ORPort [2a06:1700:0:1b::1]:9001 After a restart, both relays ramped up to a volume of connections where I was comfortable that the changes were good. Visiting them 12 hours later I find connections in the few hundred and no flags. About half of the connections were from non-Tor servers. The Tor daemon was running and had a PID. Logs showed the relay operational and nothing peculiar. Tor metrics shows the relay as down. I've commented out the IPv6 ORPort line to get both of these exits going again. The procedure I outlined has worked four other times for me. So what gives? Can anyone steer me toward the problem? And, finally, a quick question: Does NYX display incoming and outgoing IPv6 relay information? I assume ARM does not. Arisbe [0] [4061C553CA88021B8302F0814365070AAE617270] [1] [9B31F1F1C1554F9FFB3455911F82E818EF7C7883]

5 5

relayor v0.4.0 is released
by nusenu 01 Jul '18

01 Jul '18

Hi, relayor v0.4.0 is released. relayor helps you with running relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor This release contains important changes for exit operators that define their own exit policy, please _do_ read the changelog if you are an exit operator using relayor _before_ upgrading since it requires a minor configuration adjustment. If you do not change the default value for tor_ExitPolicy no configuration change is required. Changes since v0.3.3: ------------------------------ - major: change the format of tor_ExitPolicy (single-line to multi-line) previously it you defined the exit policy like: tor_ExitPolicy: "accept *:80, accept *:443, accept *:22" now you define your exit policy like this: tor_ExitPolicy: - accept *:80 - accept *:443 - accept *:22 - support multiple IP addresses for OutboundBindAddressExit - add support for OpenBSD 6.3 (drop 6.2) - add support for Ubuntu 18.04 (drop 16.04) - add support for Fedora 28 (drop 27) - drop support for Debian 8 and HBSD - increase min. tor version to 0.2.9.x - increase min. ansible verstion to 0.2.5.3 - add support for custom addition to MyFamily members - switch tor_alpha_version from 0.3.3.x to 0.3.4.x - Debian: switch to HTTPS (from HTTP) for repository traffic - reorder some torrc items 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 9 and Debian Testing OpenBSD 6.3 FreeBSD 10.4, 11.1 Ubuntu 18.04 CentOS 7 Fedora 28 regards, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

1 1

fix this please
by I 30 Jun '18

30 Jun '18

3 5

Gentoo's Github hacked
by I 29 Jun '18

29 Jun '18

1 0

Tor Exit Node Winter Shutdown
by Jason Odoom 29 Jun '18

29 Jun '18

Hello relay operators, I regret to inform you all that I will be shutting down my Tor Exit node - Winter [0] after more than five years. Digital Ocean's new bandwidth policy has made it incredibly expensive to keep this online. I incurred almost $200 of usage. I was lucky enough to have received a deduction off of my bill. I also believe that in this case asking for donations will do little to help. I did not host this Exit node for accolade but because I truly believe in what the Tor project is doing. I will allocate my budget for the Exit node towards monthly contributions to Tor as an alternative. Hopefully in the future I will be able to return. It's been fun. 0: https://metrics.torproject.org/rs.html#details/9EC5E097663862DF861A18C32B37… Best, Jason - Jason Odoom GPG 9031B50D

2 2

A general question for relay operators
by arisbe 29 Jun '18

29 Jun '18

Hello George and all, When I was learning to implement Tor I had difficulty wading through the web pages for information. Some pages were obsolete, some poorly maintained (think Tor flow or good/bad hosting companies). The Tor manual is just a huge list of Tor terminology with no aids to help find things. The Tor project site has no site map. I still occasionally have the same problems when I try to find something. I found this very discouraging as I tried to grow my first Tor node without a live person to help me. I can imagine how daunting this would be to someone also trying to learn linux. Hey, thanks so much for asking. I appreciate your interest.

3 3

No IPv6 bridges from bridges.torproject.org
by Roman Mamedov 28 Jun '18

28 Jun '18

Hello, If you select "Do you need IPv6 addresses - Yes", it always results in an error "There aren't any bridges available". No matter if choosing obfs4 or none for the pluggable transport. Is that thing working? There should be at least one available (with obfs4, too), or at least I was under impression that I run one. As a side note, that page always loads in my native language with no way to switch to English -- pages which do this are the worst. In this case it means I can't usefully copy-paste you the exact error messages that I get. -- With respect, Roman

2 1