February 2019 - tor-relays - lists.torproject.org

Questions to ask exit node providers
by F67 Group 08 Oct '19

08 Oct '19

We are thinking of running a Tor Exit Node. Does anybody have a list of questions to ask before purchasing a VPS or colocation? I came up with some basic questions: - Do you allow a Tor exit node? [with explanation] - What are the policies for handling abuse complaints? - How much uplink bandwidth do you provide? Any other questions one should ask? Thanks.

17 49

Relay without OpenSSL
by Alexander Nasonov 30 Mar '19

30 Mar '19

I recently tried updating one of my relays to Tor 0.4.0.1 compiled with NSS (and without OpenSSL) but it failed to start, see the logs below. I wonder if this configuration is supported at all and whether I should try running a brand new relay instead of updating? Alex [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits [notice] Bootstrapped 90% (ap_handshake_done): Handshake fininshed with a relay to build circuits [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [notice] Bootstrapped 100% (done): Done [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) [warn] Couldn't send authenticate cell [warn] connection_or_compute_authenticate_cell_body(): Bug: TLS key export failed for unknown reason. (on Tor 0.4.0.1-alpha ) -- Alex

3 5

Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".
by technonerd＠fea.st 02 Mar '19

02 Mar '19

I run one relay and another tor instance for hidden services and socksport. Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far. Maybe my configs aren't sane? [err] descriptor at 0x8a0acdb0830 begins with unexpected string "". Is another process running in our data directory? Exiting. First config User tor PIDFile /var/run/tor2/tor2.pid SOCKSPort 9052 ControlPort 9053 Log notice file /var/lib/tor2/notices.log RunAsDaemon 1 DataDirectory /var/lib/tor2/data CookieAuthentication 1 ClientUseIPv6 1 ClientPreferIPv6ORPort 1 ClientPreferIPv6DirPort 1 HiddenServiceDir /var/lib/tor2/ssh/ HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/ssh-new/ HiddenServiceVersion 3 HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/bitcoind/ HiddenServicePort 8333 127.0.0.1:8333 Second config User tor PIDFile /var/run/tor/tor.pid Log notice syslog Log notice file /var/log/tor/debug.log #Log notice debug file /var/lib/tor/data/tor.log DataDirectory /var/lib/tor/data ControlPort 9051 HashedControlPassword CookieAuthentication 1 ORPort 9001 ORPort []:9050 DirPort 9030 BandwidthRate 4 MBytes BandwidthBurst 5 MBytes Nickname PancakeWhore ContactInfo ExitPolicy reject *:* ExitPolicy reject6 *:*

5 8

Debugging ipv6 conenctivity
by Charly Ghislain 25 Feb '19

25 Feb '19

Hi all, My tor relay has got the UnreachableIpv6 flag set once i mentionned an OrPort with my ipv6 address. >From what i can tell, my server is reachable over ipv6, and can contact the directory authorities through ipv6 (following the instructions found there: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Makesurerelaypo… ). The node is behind an haproxy that relays ipv6 traffic to natted ipv4 (with no logging for those concerned). It seems to work fine for web content over ipv6, and traffic on both ips (v4 and v6) goes through this channel. I can successfully telnet my node ORPort using my v6 address. The ports have been defined this way in torrc: ORPort 0.0.0.0:9001 NoAdvertise ORPort 91.121.79.188:9001 NoListen ORPort [2001:41d0:1:84bc::1]:9001 NoListen Is there a way to make a tor client connect to a specific relay to debug this kind of connectivity issues? Or any other mean? In the meantime ive removed the advertized ip6. Regards, Charly

4 6

Regarding linux-tor-prio.sh script
by rl1987＠sdf.lonestar.org 24 Feb '19

24 Feb '19

Hello, Tor repository contains the following script, that has not been updated much in last 10 years or so: https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor… Do people still use? Is it safe to remove it from the repo? Regards

1 0

Memory Used dropped again with 0.3.5.8
by petrarca＠protonmail.ch 24 Feb '19

24 Feb '19

Just an fyi for those who might be interested... With upgrading to 0.3.5.8 the memory usage of my Tor relay dropped again to reasonable levels. It suddenly started to increase end of January causing my relay to crash twice before leveling around 45% (a week before I had an ISP outage). Now it's back to around 25%. The relay bandwidth consumed over all the time was pretty much stable. [Memory Used.png]

1 0

relayor v19.0.0 is released
by nusenu 23 Feb '19

23 Feb '19

Hi, relayor has been made for relay operators to help them install and manage tor relays with minimal effort. https://github.com/nusenu/ansible-relayor Changes since v18.1.1 ------------------------------ - torrc: enable tor's Sandbox feature by default on Ubuntu (where it was previously disabled as a workaround for #160 ) don't set tor RelayBandwidthBurst if the input field is empty - increase tor_alpha_version 0.3.4.x -> 0.4.0.x - increase min ansible version 2.6.2 -> 2.7.8 - add support for OpenBSD 6.4 - add support for FreeBSD 12 (drop 10.x) - README: mark CentOS/Fedora as currently broken due to upstream package issues #185 - test-kitchen: add OpenBSD support add guard-alpha test-suite kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

How To Add Reachable Ports To OBFS4 Bridge
by Keifer Bly 22 Feb '19

22 Feb '19

Hi all, So I am looking to add some reachable ports to my OBFS4 bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E CF14E5B9E9A As this list is public, I guess I should not provide the port numbers that tor and obfs4 are running on. However, would adding reachable ports like 80, 443, 8080 be doable? I know that these ports that might not bind very well as lots of other types of traffic use them, however I saw the ticket at https://trac.torproject.org/projects/tor/ticket/7875 And this raises a concern about bridges being reachable for users who are connecting from behind firewalls, etc (hence the reason why they need to use a bridge), it seems like a good idea to have bridges reachable on ports that aren't likely to be blocked by network administrators or ISPS. Let me know what you think. --Keifer

2 2

Relay operators meetup Lisbon (23.02.2019)
by Vasilis 22 Feb '19

22 Feb '19

Dear Tor friends and relay operators, Tomorrow (23.02.2019) a relay operators meetup will take place at Block cafe, Berlin. When: Saturday, February 23rd, 2019 Time: 15:00 / 3:00 PM Where: Block Cafe, Rua Latino Coelho 63, 1st floor, 1050-133, Lisbon, Portugal Event link: https://privacylx.org/en/events/tormeetup3/ Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Neel Chauhan 19 Feb '19

19 Feb '19

Hi tor-relays@ mailing list, I have a Tor relay "NeelTorRelay2": https://metrics.torproject.org/rs.html#details/D5B8C38539C509380767D4DE20DE… This relay is hosted on a 300 mbps Verizon FiOS (FTTH/GPON) connection. My server is a HPE ProLiant MicroServer Gen10 (quad-core AMD X3421 variant) running FreeBSD, and my router is a Linksys WRT1900AC running OpenWrt. For some reason, the Advertised Bandwidth is not going above ~19.5 MiB/s. If my relay is pushing 10MB/s (80mbps) at a given time, the CPU usage is around 20%, so I don't think its the CPU. My question is that is this lower Advertised Bandwidth speeds normal for a relay hosted on a connection behind a consumer level router and it's NAT table (even despite OpenWrt)? Could it be Verizon's DPI/QoS now that Net Neutrality is repealed? Would using a non-consumer router (like Ubiquiti or pfSense) help? Thank You, Neel Chauhan === https://www.neelc.org/

4 4