- tor-relays - lists.torproject.org

Added new relays to my family.
by Jochen 03 Oct '19

03 Oct '19

Hi, just letting everyone know that I've added, in total, 6 new relays to my family: https://metrics.torproject.org/rs.html#search/family:94C268630BEDCB64E7F888… During the next few weeks expect around ~1,6Gbit/s total exit capacity. On another note: Is there any update on multithreading for tor relays? I recall sending in a trace to, I think, teor. I know that it's probably not a feature with high priority, just asking if the trace I sent in was useful and if you need anything else ;-) Best Regards, Jochen

3 2

No connections to bridge
by skarz 02 Oct '19

02 Oct '19

I set up a bridge at home on my Raspberry Pi (Raspbian Buster) using [these instructions](https://community.torproject.org/relay/setup/bridge/), and I believe everything is configured correctly... But there is no activity in or out of my bridge. Here's some messages I am seeing: > 16:31:26 [NOTICE] Heartbeat: In the last 6 hours, I have seen 0 unique clients. [2 duplicates hidden] > 16:31:26 [NOTICE] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 6.18 MB and received 25.58 MB. [2 duplicates hidden] > 16:04:28 [NOTICE] Performing bandwidth self-test...done. > 13:10:43 [NOTICE] No circuits are opened. Relaxed timeout for circuit 408 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out I know bridges don't see as much activity but is this abnormal?

3 2

Re: [tor-relays] Bridge - how to configure obfs4 both: on IPv4 AND IPv6?
by Roger Dingledine 29 Sep '19

29 Sep '19

On Sat, Sep 28, 2019 at 08:12:43PM +0200, tschador(a)posteo.de wrote: > But with: > > ServerTransportListenAddr obfs4 <ipv4-addr>:<port> > ServerTransportListenAddr obfs4 [<ipv6-addr>]:<port> > > obfs4proxy is only listening on the IPv4 address! It looks like you are encountering https://bugs.torproject.org/11211 Alas, I suggest sticking to ipv4 for now -- I think if you got ipv6 working on your obfs4, you would next run into the problem that bridgedb doesn't currently give out ipv6 obfs4 addresses. There's a lot of work waiting for somebody who wants to make ipv6 more of a proper citizen in the Tor world. There's a mention by Sarah of a recent funding proposal which could get that restarted again: https://lists.torproject.org/pipermail/tor-project/2019-September/002479.ht… Thanks for running a bridge! --Roger

2 1

Re: [tor-relays] My relay is listed offline, but it isn't!
by niftybunny 26 Sep '19

26 Sep '19

$ traceroute6 2a01:4f8:1c0c:45f7::1 connect: No route to host > On 25. Sep 2019, at 17:24, tschador(a)posteo.de wrote: > > Hi, > > after upgrading to Tor version 0.4.1.6-1~d9.stretch+1 and kernel > 4.9.0-11-amd64 on Debian GNU/Linux 9 my relay ist listed as offline. [1] > > I restarted Tor several times, but no change. The log shows (CEST): > --- > Sep 25 13:10:29.000 [notice] Tor 0.4.1.6 opening log file. > Sep 25 13:10:29.432 [notice] Tor 0.4.1.6 running on Linux with Libevent > 2.0.21-stable, OpenSSL 1.1.0k, Zlib 1.2.8, Liblzma 5.2.2, and Libzstd 1.1.2. > … > Sep 25 13:10:33.000 [notice] Self-testing indicates your ORPort is > reachable from the outside. Excellent. > … > Sep 25 13:11:35.000 [notice] Self-testing indicates your DirPort is > reachable from the outside. Excellent. Publishing server descriptor. > Sep 25 13:11:35.000 [notice] Performing bandwidth self-test...done. > --- > > There are still 150 connects in the moment, slowly decreasing. > > Only two of the authorities show the 'running'-flag for my relay. What's > going on there? > > Regards > > [1] > https://metrics.torproject.org/rs.html#details/6A7551EEE18F78A9813096E82BF8… > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Re: [tor-relays] My relay is listed offline, but it isn't!
by Roger Dingledine 25 Sep '19

25 Sep '19

On Wed, Sep 25, 2019 at 05:24:55PM +0200, tschador(a)posteo.de wrote: > after upgrading to Tor version 0.4.1.6-1~d9.stretch+1 and kernel > 4.9.0-11-amd64 on Debian GNU/Linux 9 my relay ist listed as offline. [1] > > Only two of the authorities show the 'running'-flag for my relay. What's > going on there? > > [1] > https://metrics.torproject.org/rs.html#details/6A7551EEE18F78A9813096E82BF8… My guess is that your ipv4 ORPort is reachable, but that your ipv6 ORPort is not reachable. So you're getting Running votes from the dir auths that don't test ipv6, and the ones that do test ipv6 are declaring you down. For those following at home, if you're in this situation, another useful tool is to go to the search box at the bottom of https://consensus-health.torproject.org/#relayinfo and paste in your fingerprint, to learn more about the individual votes from each directory authority about your relay. Thanks! --Roger

1 0

Measuring the Accuracy of Tor Relays' Advertised Bandwidths
by Rob Jansen 23 Sep '19

23 Sep '19

Hello relay operators! I am planning on performing an experiment on the Tor network to try to gauge the accuracy of the advertised bandwidths that relays report in their server descriptors. Briefly, the experiment involves running a speed test on every relay for a short time (about 20 seconds). Details follow. I plan to run the experiment in about 1 week. Relay operators can opt-out of the speed test by replying on this thread, and we will remove you from the list of relays to scan. Peace, love, and positivity, Rob --- Measuring the Accuracy of Tor Relays' Advertised Bandwidths Motivation ---------- The capacity of Tor relays (maximum available goodput) is an important metric. Combined with mean goodput, it allows us to compute the bandwidth utilization of individual relays as well as the entire network in aggregate. Generally, capacity is used to help balance client load across relays, and relay utilization rates help Tor make informed decisions about how to allocate resources and prioritize performance and scalability improvements. Problem ------- Currently, Tor uses a heuristic measure of unknown accuracy to estimate Tor relay capacity. Each relay keeps track of the maximum goodput it has achieved over any 10 second window in a 24 hour period. This is called the "observed bandwidth". Relays take the minimum of their "observed bandwidth" and their bandwidth rate-limiting configuration and reports the result as the "advertised bandwidth" in their server descriptors. We do not know how well the advertised bandwidth estimates the true relay capacity, but we do know that it represents a lower bound on capacity. Hypothesis ---------- The advertised bandwidth significantly underestimates the true capacity of Tor relays. On average, relays with higher true capacities will be more strongly correlated with capacity underestimation (because it will be less likely that fast relays will have sustained their full capacity over a 10 second period). Experiment ---------- A relay reports its advertised bandwidth in its server descriptor. To test how well these reported numbers represent the true capacity of a relay, we can manually perform a speed test on the relay by initiating the simultaneous download of several large data streams for a period that exceeds 10 seconds. In the report following our test, the relay will report its advertised bandwidth in its server descriptor and the results will be collected and reported by metrics.torproject.org. The experiment involves two steps: running the speed test on a relay under our control, and running the speed test on all relays in Tor network. We will first run the speed test on at least one relay that we control, in order to test that the method is effective and that we can in fact observe a change in the advertised bandwidth reported on metrics.torproject.org. Once we have confidence that our speed test is functioning correctly, and that the metrics pipeline will allow us to gather the results, we will repeat it on all relays in the network. We will conduct the speed tests while minimizing network overhead. We will use a custom client that builds 2-relay circuits. The first relay will be the target relay we are speed testing, and the second relay will be a fast exit relay that we control. We will initiate data streams between a speedtest client and server running on the same machine as our exit relay. The setup will look like: speedtest-client <--> tor-client <--> target-relay <--> exit-relay <--> speedtest-server All components will run on the same machine that we control except for the target-relay, which will rotate as we test different relays in the network. For each target relay, we plan to run the speedtest for 20 seconds in order to increase the probability that the 10 second mean goodput will reach the true capacity. We will measure each relay over a few days to ensure that our speedtest effects are reported by every relay. Although we believe that the overhead of this speed test is in line with regular usage, relay operators can opt-out of the speed test by replying on this thread. Those that opt out will be removed from our list of relays to scan. Analysis -------- Following our speedtest, we will analyze the data collected and reported by Tor metrics. We will compared the advertised bandwidth that each relay reports before our experiment to those reported during our experiment. This will help us test our hypothesis that relays' advertised bandwidth underestimates the true capacity of relays. We will run a statistical correlation analysis on the data to test the strength of the correlation between the previously reported (estimated) relay capacity and relay capacity underestimation. We will report our results to the Tor community. We expect that the results of our experiment will help Tor decide how to allocate resources and will help them plan and prioritize performance improvements. It will also provide insight into the operation of the current load balancing system, which uses advertised bandwidth to produce consensus weights.

12 37

Bridge stats always in multiples of 8
by nottryingtobelame＠protonmail.com 23 Sep '19

23 Sep '19

I'm just curious as to why, in the bridge stats, all the country codes show a multiple of 8. Thanks for your time!

2 1

tor
by armik900＠gmail.com 18 Sep '19

18 Sep '19

hi,what are these relay operators with the same nickname (snap269) but from different countries the vast majority of relays are outdated and do not work С уважением, Станислав

3 2

Sudden bridge activity from Russia and Iran, strange?
by nottryingtobelame＠protonmail.com 18 Sep '19

18 Sep '19

Hello, my new bridge sat for a few weeks with 0 clients. I understand it takes time to begin seeing clients, but all of a sudden within the span of one 6-hour heartbeat period, I picked up 346 clients. Since then, it has been 20-50 every 6 hours. But when I pull the bridge-stats file, it shows 104 from Iran, and 64 from Russia. These two are the overwhelming majority of my clients; all the other countries each have 8. Is this normal, or suspicious?

2 1

SSH scanning on TOR Exit - Nerfing Rules
by AMuse 16 Sep '19

16 Sep '19

Hi all! I'm curious what y'all think of this situation. I have SSH open as an exit port on a TOR exit that my friends and I are maintaining - and of course it's the #1 offender by far in automated abuse notifications we get from our ISP, from peoples' fail2ban servers sending abuse emails. This all seems like a huge waste of time, but that's a separate issue. I'm wondering if nerfing outbound SSH to rate limit will be effective at getting the SSH scanning bots to stop using my exit in their circuit, while leaving SSH open for actual humans who need to SSH while using TOR. I've implemented, as a test, rate limiting outbound on the SSH port. What do you think the impact of this will be? No impact? Losing exit status because connections on SSH die? Something else entirely? Here's the pf rules in question: pass in on $ext_if proto {tcp udp} from any to any port 9000:9150 keep state pass in on $ext_if proto tcp from any to any port 22 keep state pass in on $ext_if proto tcp from any to any port 80 keep state pass out on $ext_if from any to any keep state pass out on $ext_if proto tcp from any to any port 22 keep state (max-src-conn 25, max-src-conn-rate 1/5 )

3 2