tor-relays

tor-relays@lists.torproject.org

38 participants
4819 discussions

Start a nNew thread

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 22
by daniel boone 08 Sep '16

08 Sep '16

3 2

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 21
by daniel boone 07 Sep '16

07 Sep '16

3 2

write-history for exit relays only?
by Philipp Winter 07 Sep '16

07 Sep '16

I want to learn how many bytes exit relays forwarded. I assume that the write-history that is published in a relay's extra-info document includes bytes that were relayed as part of the exit's guard and middle role? If so, is there a way to learn how many bytes were written by the relay in its exit role only? I suspect that one could approximate this number by accounting for the probability of all exits being selected as guard, middle, and exit, but I would prefer a simpler and more reliable approach.

3 3

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 16
by daniel boone 06 Sep '16

06 Sep '16

1 0

Tor bridge and obfs4proxy
by Arisbe 05 Sep '16

05 Sep '16

I need someone's bridge experience. I had an HD crash and lost one of my Tor bridges. So, I'm rebuilding on a leased VPS. First I tried with Debian 8 and then with ubuntu 16.04 when Debian didn't work. With both operating systems I get a warning message when I start Tor. Tor is the latest version as is obfs4proxy: Sep 04 13:39:41.641 [warn] Strange ServerTransportPlugin type 'obfs4' Sep 04 13:39:41.641 [warn] Failed to parse/validate config: Invalid server transport line. See logs for details. There are no log entries. Apparently Tor starts without the proxy. I have configured torrc as follows: ServerTransportPlugin obfs3 obfs4 exec /usr/bin/obfs4proxy ExtORPort auto /usr/bin/ does contain the obfs4proxy file. Does anyone know my problem? Is there a 'tell-all' explanation of obfs4proxy? Thanks, Arisbe

2 2

Useful metrics for relay operators
by Alison 05 Sep '16

05 Sep '16

Hello all, After Roger's recent checkin emails to this list, some of the folks from the community and metrics teams have started to brainstorm ways that we could use Onionoo data [1] to give better support and recognition to the relay operators. For example, a weekly mail of all the relays that just passed the "earned a tshirt" threshold, or some other threshold about how much bandwidth they've pushed over a period of time. The community team would then contact the operator(s) and congratulate them, thank them for their service, see if we can offer them help in any other ways, and so forth. I'd like to hear directly from relay operators about what kinds of metrics they might like to see involved in a project like this. Have you achieved milestones with your relays that you wished Tor Project would have given you some recognition for? Have there been specific times you'd wished for a checkin email, like the one Roger sent (eg 3 months after starting a new relay)? Anything else that you think Onionoo could measure that would be valuable for you as an operator? Thank you so much for running relays! Looking forward to hearing from you. Alison [1] https://onionoo.torproject.org/

8 9

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 12
by daniel boone 05 Sep '16

05 Sep '16

4 4

Guard vs Exit Bandwidth
by Tristan 05 Sep '16

05 Sep '16

Looking at the advertised bandwidth vs bandwidth history from Tor Metrics[1], it appears that guard relays see much more traffic than exit relays. I think it might be partially because guard-only, guard-middle and guard-exits aren't separated, but would it really skew the numbers that much? [1]http://rougmnvswfsmd4dq.onion/bandwidth-flags.html -- Finding information, passing it along. ～SuperSluether

3 3

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 14
by daniel boone 04 Sep '16

04 Sep '16

2 1

Re: [tor-relays] tor-relays Digest, Vol 68, Issue 15
by daniel boone 04 Sep '16

04 Sep '16

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays