December 2016 - tor-relays - lists.torproject.org

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

snaptor relays: MyFamily update required
by nusenu 08 Apr '17

08 Apr '17

Hi snaptorg, thanks for adding new relays, please do not forget to update your MyFamily. +---------------------+-----------------+---------------+------+ | first_seen | IP | MyFamilyCount | exit | +---------------------+-----------------+---------------+------+ | 2016-11-12 00:00:00 | 213.32.66.192 | 9.0000 | 0 | | 2016-11-26 23:00:00 | 193.70.90.199 | 9.0000 | 0 | | 2016-11-26 23:00:00 | 128.199.108.14 | 9.0000 | 0 | | 2016-11-27 00:00:00 | 139.59.46.211 | 9.0000 | 0 | | 2016-11-28 11:00:00 | 94.156.77.41 | 8.0000 | 1 | | 2016-11-28 14:00:00 | 142.4.206.241 | 9.0000 | 1 | | 2016-11-29 00:00:00 | 185.103.110.210 | 9.0000 | 1 | | 2016-12-03 23:00:00 | 144.217.90.138 | 9.0000 | 0 | | 2016-12-16 15:00:00 | 176.123.26.27 | 8.0000 | 1 | | 2016-12-16 23:00:00 | 193.70.22.86 | NULL | 0 | +---------------------+-----------------+---------------+------+ https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… regards, nusenu -- https://github.com/nusenu/ansible-relayor

3 9

Please enable IPv6 on your relay!
by Moritz Bartl 28 Jan '17

28 Jan '17

Hi! We still have a depressingly low number of relays that support IPv6 (currently only ~120 of ~1900 relays). If your host supports IPv6, please enable it, especially if you run an exit! This has to be done explicitly. https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto In short, you add: ORPort [IPv6::address]:port IPv6Exit 1 ExitPolicy reject6 *:* (or a more open exit policy respectively) Thanks! -- Moritz Bartl https://www.torservers.net/

30 42

Some problems with new Exit Node
by Alan 18 Jan '17

18 Jan '17

So I bit the bullet and started running an Exit Node (Andromeda), still early days with a few problems, namely:- # It hasn't been given a Stable flag yet. # Some problem with dns resulting in [WARN] eventdns: All nameservers have failed - i've switched the dns to 8.8.8.8, only seen that error once since # The Consensus Weight was gaining nicely and reached over 7,000 but now has dive bombed to just 20, with that the speed dropped from ~50mbps to ~5mbps https://atlas.torproject.org/#details/FDB4FC238F13E7FEC99D025DB8B89A636EFC1… Is this all normal or something i've overlooked? Alan

4 4

torworld relays in entry and exit position
by nusenu 15 Jan '17

15 Jan '17

Hi torworld, thanks for joining the tor network with your relays! You are operating entry and exit relays without proper 'MyFamily' configuration, this can be dangerous for tor clients because they might choose you as entry _and_ exit relay, please help protect tor clients by properly specifying the MyFamily configuration in your torrc files. If you need any help please let us know. https://www.torworld.org/ https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… https://lists.riseup.net/www/arc/ornetradar/2016-10/msg00101.html kind regards, nusenu https://github.com/nusenu/ansible-relayor

1 1

All I want for Chrismas is a bloody t-shirt
by I 11 Jan '17

11 Jan '17

9 19

Re: [tor-relays] What's a "useful" relay?
by Rana 11 Jan '17

11 Jan '17

@Ivan >Some best practices definitely would be awesome to have about running on common (embedded) hardware. Clear notification like "your Commodore 64 is to slow to be a good relay" would also be useful. I agree about the need for guidelines but I disagree about the content of the guidelines that are needed. The data I see so far, including your report of a Pi with 7000 connections, is a clear indication that minimal hardware capabilities are NOT the guidelines that are needed (unless a relay with 7000 connections is still considered "harmful" or "useless"). My own Pi-based relay https://atlas.torproject.org/#details/707A9A3358E0D8653089AF32A097570A96400… has just reached 1300 connections; CPU utilization: practically zero; memory utilization: 14.5%. The increase from 500 to 1300 connections required memory utilization increase of just 2%, from 12.5% to 14.5%. Clearly, hardware of the $35 Pi has absolutely nothing to do with residential relays being useful or not, save the (recently reported here) anomaly of an operator who has symmetric BW of 160 mbps to the home. So guidelines on hardware are evidently not needed for "normal" residential ISP bandwidth: it has been amply demonstrated that even a dirt cheap Pi is not the bottleneck, no need to spend further effort on this until the REAL bottleneck is resolved: the network. To continue the story, the above relay of mine with 1300 connections has consensus BW rating of 38 (thirty eight). Why? Who knows. I get zero feedback on the reason for this. To further continue the story, my 2nd relay https://atlas.torproject.org/#details/31B8C4C4F1C78F923BD906769297B15A428C4… that currently has about the same Atlas-measured BW as the first relay (132 vs 153 KB/s) and is based on exactly the same hardware and software, is clinically dead with almost no connections and BW rating of 13. Why? Who knows. What is needed is a standardized feedback on WHY the relay has such a low rating. This could cause at least part of the operators to take care of the bottleneck (eg moving the relay to another location, or abandoning the home relay and replacing it with a hosted one). And if the home relay is indeed as harmful as some people here think, the recommendation should be issued to shut it down, instead of leaving it hanging there doing nothing or even harming Tor. Such feedback could significantly improve the quality and effectiveness of Tor. Based on the discussion here, the people who run Dirauths and bwauths know very well (or at least can easily find out) the reasons for relays getting low rating - why not automate the communication of the reasons to relay operators in clear, unequivocal and actionable terms? I get the feeling that people are trying to be "politically correct" here and it's a pity (although they DO respond fully and frankly when asked a direct question). Rana

2 3

Disparity between download and upload traffic
by Gage Parrott 10 Jan '17

10 Jan '17

Morning, everyone, I recently migrated my bridge relay over to a VM and everything seems to be working fine except for one oddity. I consistently see lines like this in tor's log file on the new machine: Dec 25 23:48:14.000 [notice] Heartbeat: Tor's uptime is 4 days 5:59 hours, with 43 circuits open. I've sent 1.78 GB and received 28.37 GB. Dec 25 23:48:14.000 [notice] Heartbeat: In the last 6 hours, I have seen 2 unique clients. Dec 26 05:48:14.000 [notice] Heartbeat: Tor's uptime is 4 days 11:59 hours, with 105 circuits open. I've sent 1.87 GB and received 29.24 GB. Dec 26 05:48:14.000 [notice] Heartbeat: In the last 6 hours, I have seen 2 unique clients. Notice the amount of data sent and received. Can anyone think of why there would be such a large discrepancy between the amount of traffic downloaded versus uploaded? This behavior persists after reboots, as well. I thought maybe it was downloading a ton of directory data, but is there really a GB's worth of directory data to download every six hours?? Also, the logs on my old machine (pre-migration, one line pasted below for reference) indicated that nearly the same amount of data was being sent as was being received. Any ideas on why would this have changed? Dec 07 06:02:03.000 [notice] Heartbeat: Tor's uptime is 4 days 6:12 hours, with 78 circuits open. I've sent 33.71 GB and received 33.47 GB. Any help is greatly appreciated. Thanks a bunch and merry Christmas! gp

2 3

zwiebeln@online.de relays: MyFamily update required (was: [OrNetRadar] Contact: "<zwiebeln at online de>")
by nusenu 05 Jan '17

05 Jan '17

Hi zwiebeln, thanks for running so many tor exit instances and adding so many yesterday. Please do not forget to add your new relays to your MyFamily, your "old" relays had a proper MyFamily configuration. thanks, nusenu https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… +---------------------+-----------------+---------------+------+ | first_seen | IP | MyFamilyCount | exit | +---------------------+-----------------+---------------+------+ | 2016-04-11 21:00:00 | 178.17.170.179 | 25.0000 | 1 | | 2016-05-14 15:00:00 | 195.123.209.184 | 25.0000 | 1 | | 2016-07-03 15:00:00 | 178.17.170.179 | 25.0000 | 1 | | 2016-08-28 12:00:00 | 37.157.193.161 | 25.0000 | 1 | | 2016-09-10 14:00:00 | 37.157.193.161 | 25.0000 | 1 | | 2016-09-16 21:00:00 | 89.221.209.100 | 25.0000 | 1 | | 2016-09-18 12:00:00 | 37.157.196.97 | 25.0000 | 1 | | 2016-09-27 10:00:00 | 37.157.196.97 | 25.0000 | 1 | | 2016-09-27 10:00:00 | 89.221.209.100 | 25.0000 | 1 | | 2016-11-12 21:00:00 | 144.217.60.211 | 25.0000 | 1 | | 2016-11-12 23:00:00 | 213.32.55.239 | 25.0000 | 1 | | 2016-11-14 12:00:00 | 149.202.238.204 | 25.0000 | 1 | | 2016-11-15 15:00:00 | 144.217.60.239 | 25.0000 | 1 | | 2016-11-15 15:00:00 | 158.58.170.150 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.212 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.27 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.212 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.27 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 51.15.53.83 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 46.182.18.29 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 51.15.53.83 | 25.0000 | 1 | | 2016-12-05 17:00:00 | 46.182.18.29 | 25.0000 | 1 | | 2016-12-05 17:00:00 | 46.182.18.214 | NULL | 1 | | 2016-12-16 20:00:00 | 88.151.99.224 | NULL | 1 | | 2016-12-18 18:00:00 | 185.14.29.129 | NULL | 0 | | 2016-12-18 22:00:00 | 149.202.238.204 | NULL | 0 | | 2016-12-18 22:00:00 | 144.217.60.239 | NULL | 0 | | 2016-12-18 22:00:00 | 144.217.60.211 | NULL | 0 | | 2016-12-18 22:00:00 | 213.32.55.239 | NULL | 0 | | 2016-12-18 23:00:00 | 158.58.170.150 | NULL | 0 | +---------------------+-----------------+---------------+------+ ornetradar(a)riseup.net: > 2016-12-18 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | AS | CC | ORp | Dirp | OS | Version | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 | 21:41:51 | 149.202.238.204 | OVH SAS | fr | 444 | 81 | Linux | 0.2.8.11 | alsaceonionb | 1 > 1 | 0 | 21:26:02 | 144.217.60.239 | OVH SAS | ca | 444 | 81 | Linux | 0.2.8.11 | quebeconionb | 1 > 1 | 0 | 21:31:09 | 144.217.60.211 | OVH SAS | ca | 444 | 81 | Linux | 0.2.8.11 | montrealonionb | 1 > 1 | 0 | 21:36:53 | 213.32.55.239 | OVH SAS | fr | 444 | 81 | Linux | 0.2.8.11 | strasbourgonionb | 1 > 1 | 0 | 22:24:55 | 158.58.170.150 | Seflow S.N.C. D | it | 444 | 81 | Linux | 0.2.8.11 | milanoonionb | 1 > 1 | 0 | 17:42:44 | 185.14.29.129 | Serverius Holdi | nl | 9001 | 9030 | FreeBSD | 0.2.8.11 | humboldt | 1

2 5

Speed up of reconnections after IP Address change
by balbea16 03 Jan '17

03 Jan '17

Hi There,I only have a dynamic IP address and my ISP changes it almost every time after 24 hours. It is somehow sad to see 1.400 connections drop to almost none. After the change it takes 20 minutes until my OR notices this (our IP Address has changed from ...). It than takes another hour until the connections start to actualy rebuild. This means it takes more than an hour (every per day) to reach the normal operating Mode. Is there any way to speed up this process? Could adjust the torrc script for instance? TNX Mike

4 3