- tor-relays - lists.torproject.org

A general question for relay operators
by George 05 Jul '18

05 Jul '18

Greetings relay operators. A question that came up offline for relay operators can be summed up in one sentence, paraphrased from flexlibris: as a relay operator, what "things" do you wish you knew before you started running a relay? I'm really curious, in particular, to hear from those relay operators who are less connected to others, and are maybe more isolated physically from the community. In the long-ago past, many of us ran exit nodes without giving it much thought or preparation leading to ISP issues, but that seems less common today. For others, there might be a learning curve in keeping a network service up with decent uptime, while updating the relevant ports and operating system. There's no irrelevant answers to this, including more boring issues such as paying for the relay, choosing a provider or experiences as a (conscious) exit node operator. Bonus point for showing relation between your total costs per 1Mbps. Not only should this discussion be useful on list, but it might provide more content for the relay operator guide. g -- 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682

9 15

Coordinated raids of Zwiebelfreunde at various locations in Germany
by nusenu 05 Jul '18

05 Jul '18

https://blog.torservers.net/20180704/coordinated-raids-of-zwiebelfreunde-at… https://www.ccc.de/en/updates/2018/hausdurchsuchungen-bei-vereinsvorstanden… "The board members of the association are not considered suspects but witnesses in the ongoing investigation." "Just to recap: The mere presence of an e-mail address at a large free provider on a website has caused law enforcement authorities to deduce that a German association that helps raise funds for this provider must be connected to this website somehow."

5 5

DSL interruption
by Paul 04 Jul '18

04 Jul '18

^ r | rt rt | rt rt | rt rt rt | rt rt rt rt | rt rt rt rt | rt rt rt rt rt | rt rt rt rt rt rt | rt rt rt rt rt rt rt | rt rt rt rt rt rt rt -+---------------------------------------------------------------------------> | 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11 h rx (MiB) tx (MiB) h rx (MiB) tx (MiB) h rx (MiB) tx (MiB) 12 11.14 14.76 20 666.90 679.48 04 11.68 15.05 13 98.65 102.77 21 27.54 29.01 05 22.50 22.41 14 961.83 954.33 22 49.58 51.97 06 14.50 17.09 15 1028.29 1021.80 23 50.87 51.47 07 11.75 15.13 16 1529.16 1520.73 00 28.72 29.68 08 10.71 13.05 17 1779.50 1768.45 01 16.91 19.62 09 32.82 14.84 18 2477.60 2456.01 02 10.76 14.93 10 13.86 15.48 19 2380.83 2358.08 03 10.06 12.70 11 1.57 2.32 From time to time I do get DSL interruptions which look like above on the traffic on one of my smaller relays. This usually last until I restart the machine manually. Anybody having a good quick idea, script to solve this and restart automatically when DSL is up again? Its on Raspian latest.. Thanks and regards Paul

2 1

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