- tor-relays - lists.torproject.org

Relay request
by runner7272 05 Apr '16

05 Apr '16

Sent from my Sprint Phone.

2 1

Re: [tor-relays] tor-relays Digest, Vol 63, Issue 5
by d3part3d＠tuta.io 04 Apr '16

04 Apr '16

? -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 4. Apr 2016 15:31 by tor-relays-request(a)lists.torproject.org: > Send tor-relays mailing list submissions to > > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Tor Weather has been discontinued (Karsten Loesing) > 2. Re: Tor Weather has been discontinued (Eran Sandler) > 3. Re: Tor Weather has been discontinued (Eran Sandler) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Apr 2016 16:48:39 +0200 > From: Karsten Loesing <> karsten(a)torproject.org> > > To: > tor-relays(a)lists.torproject.org > Subject: [tor-relays] Tor Weather has been discontinued > Message-ID: <> 57027EC7.9010802(a)torproject.org> > > Content-Type: text/plain; charset=utf-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dear relay operators, > > as of April 4, 2016, Tor Weather has been discontinued. > > Tor Weather [0] provided an email notification service to any user who > wanted to monitor the status of a Tor node. Upon subscribing, they > could specify what types of alerts they would like to receive. The > main purpose of Tor Weather was to notify node operators via email if > their node was down for longer than a specified period, but other > notification types were available, including one where operators would > be informed when their node was around long enough to qualify for a > t-shirt. > > The main reason for discontinuing Tor Weather is the fact that > software requires maintenance, and Tor Weather is no exception. Tor > Weather was promising t-shirts for relays that have not been around > long enough or that provided too little bandwidth to be useful to the > network, and it was almost impossible to deny a t-shirt after Tor > Weather has promised it. Apart from that, Tor Weather was likely not > offering t-shirts to people who have long earned it, thereby confusing > them. An unreliable notification system is worse than not having a > system at all. Relay operators shouldn't rely on Tor Weather to > notify them when their relay fails. They should rather set up their > own system instead. > > We have tried to find a new maintainer for Tor Weather for years, but > without success. We started rewriting Tor Weather [1] using Onionoo > [2] as data back-end in 2014, and even though that project didn't > produce working code, somebody could pick up this efforts and finish > the rewrite. The Roster developers said that they're planning to > include an email notification function in Roster [3]. And we > developed a simple Python script that provides information about a > relay operator's eligibility for acquiring a t-shirt [4]. None of > these alternatives is a full replacement of Weather, though. > > We encourage you, the community of Tor relay operators, to step up to > start your own notification systems and to share designs and code. > Tor Weather is still a good idea, it just needs somebody to implement it. > > Tor Weather is discontinued in two steps. For now, new subscriptions > are disabled, new welcome messages are not sent out anymore, and > existing subscriptions continue working until June 30, 2016. From > July 1, 2016 on, Tor Weather will not be sending out any emails. > > Sorry for any inconvenience caused by this. > > All the best, > Karsten > > > [0] > https://weather.torproject.org > > [1] > https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 > > [2] > https://onionoo.torproject.org > > [3] > http://www.tor-roster.org > > [4] > https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py > > -----BEGIN PGP SIGNATURE----- > Comment: GPGTools - > http://gpgtools.org > > iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 > WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF > xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE > ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i > gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER > VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= > =LVj8 > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 2 > Date: Mon, 04 Apr 2016 14:58:20 +0000 > From: Eran Sandler <> eran(a)sandler.co.il> > > To: > tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Tor Weather has been discontinued > Message-ID: > <> CALR3k-G0DoeRB-baVw+uvGUeMdDRVMORwEgAjDgCg6kE3n1cGQ(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > I have played quite a bit with onionoo and wrote a wrapper in Go for it. > > I am willing to rewrite Tor Weather using Go (or python if you like). > > I'll go over the old code and this email again to make sure I understand > the full scope of the project. > > As an operator I have relied on the Tor Weather alerts to know if one if my > nodes were down and while it's wasn't quick enough in sending alerts it was > a good tool. > > I have some ideas about the t-shirts alerts so that we won't miss sending > to those that need it and wouldnt send to those that don't need it. > > Eran > > On Mon, Apr 4, 2016, 17:49 Karsten Loesing <> karsten(a)torproject.org> > > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Dear relay operators, >> >> as of April 4, 2016, Tor Weather has been discontinued. >> >> Tor Weather [0] provided an email notification service to any user who >> wanted to monitor the status of a Tor node. Upon subscribing, they >> could specify what types of alerts they would like to receive. The >> main purpose of Tor Weather was to notify node operators via email if >> their node was down for longer than a specified period, but other >> notification types were available, including one where operators would >> be informed when their node was around long enough to qualify for a >> t-shirt. >> >> The main reason for discontinuing Tor Weather is the fact that >> software requires maintenance, and Tor Weather is no exception. Tor >> Weather was promising t-shirts for relays that have not been around >> long enough or that provided too little bandwidth to be useful to the >> network, and it was almost impossible to deny a t-shirt after Tor >> Weather has promised it. Apart from that, Tor Weather was likely not >> offering t-shirts to people who have long earned it, thereby confusing >> them. An unreliable notification system is worse than not having a >> system at all. Relay operators shouldn't rely on Tor Weather to >> notify them when their relay fails. They should rather set up their >> own system instead. >> >> We have tried to find a new maintainer for Tor Weather for years, but >> without success. We started rewriting Tor Weather [1] using Onionoo >> [2] as data back-end in 2014, and even though that project didn't >> produce working code, somebody could pick up this efforts and finish >> the rewrite. The Roster developers said that they're planning to >> include an email notification function in Roster [3]. And we >> developed a simple Python script that provides information about a >> relay operator's eligibility for acquiring a t-shirt [4]. None of >> these alternatives is a full replacement of Weather, though. >> >> We encourage you, the community of Tor relay operators, to step up to >> start your own notification systems and to share designs and code. >> Tor Weather is still a good idea, it just needs somebody to implement it. >> >> Tor Weather is discontinued in two steps. For now, new subscriptions >> are disabled, new welcome messages are not sent out anymore, and >> existing subscriptions continue working until June 30, 2016. From >> July 1, 2016 on, Tor Weather will not be sending out any emails. >> >> Sorry for any inconvenience caused by this. >> >> All the best, >> Karsten >> >> >> [0] >> https://weather.torproject.org >> >> [1] >> https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 >> >> [2] >> https://onionoo.torproject.org >> >> [3] >> http://www.tor-roster.org >> >> [4] >> https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py >> >> -----BEGIN PGP SIGNATURE----- >> Comment: GPGTools - >> http://gpgtools.org >> >> iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 >> WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF >> xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE >> ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i >> gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER >> VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= >> =LVj8 >> -----END PGP SIGNATURE----- >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >

1 0

I would like to help.
by Generalgrievous 03 Apr '16

03 Apr '16

I have a Banana Pi that I would like to use to help the TOR network. I have installed Debian-Jessie and started researching the process for setting up relay, even an exit. I am a total noob, but willing to learn. If someone is willing to help me step by step, I would be excited to help. I've tested my internet speed, Download average 60 mbps, Upload avreage 6 mbps, If I would be more of a hindrance than a benefit, please say so, no hard feelings. Located Central CA. General G. Sent from [ProtonMail](https://protonmail.com), encrypted email based in Switzerland.

6 6

Earned T-shirt and no email response for months
by Dimitar Milkov 02 Apr '16

02 Apr '16

Hello, My relay earned me a Tor T-shirt a couple of months ago. I emailed the team responsible for them on the email given in the T-shirt descriprion page (https://www.torproject.org/getinvolved/tshirt.html) with size, shipping address and everything, and the notification email from Tor Weather also included. However, there is still no response. I asked in IRC after the first month or so and some people said that they are overloaded with work because of some campaign/conference sort of thing. How long it usually takes for a T-shirt request to be processed? What is your experience?

4 4

Re: [tor-relays] Relays with broken DirPorts
by starlight.2016q1＠binnacle.cx 02 Apr '16

02 Apr '16

These relays all appear at least somewhat overrated by BWauths and are not rate-limiting with BandwidthRate. DirPort performance is bad due to a saturated physical link or 'tc' bandwidth limit, so TCP congestion back-off kicks in. If BandwidthRate were the limiting factor DirPort would return a 503 (busy) error. Reason for the overrating is a serious bug in Torflow resulting in relays going unmeasured for extended periods, possibly more than 30 days at which time a BWauth will cease listing an affected relay. I'm planning to work on fixing this, but have not had the time and presently don't see getting to it before early summer. >Dear Relay Operators, > >Also while working on #17158, I found some relays whose DirPort >responses made my python script hang. It wouldn't even respond >to ^C, but that might just be an OS X thing, or a stem thing. > >I'm not sure what to do about these relays. I'd like to do a >tcpdump / Wireshark check, but I don't have time at the moment. >Would anyone like to follow this up? > >This is an incomplete list of broken relay IPs and DirPorts, >starting with those with the highest consensus weight: >217.23.14.190:1194 >151.80.164.147:80 >148.251.255.92:80 >78.142.19.59:80 > >Thanks > >Tim > >Tim Wilson-Brown (teor)

3 2

Relays with very slow DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

Dear Relay Operators, While I was checking fallback directory mirrors for #17158, I encountered some relays that took more than a minute to serve a consensus. Most took 150 seconds, which could be caused by a RelayBandwidthRate of 10 kilobytes a second. One solution to this issue is to disable the DirPort on relays with a RelayBandwidthRate less than 50 kilobytes a second, or more than 30s to serve a consensus. https://trac.torproject.org/projects/tor/ticket/18688 (This ticket also contains the python / stem code that I'm using to check the consensus download speed.) But I don't actually know if it's the relays' torrc configuration that's causing the issue, or if their provider is limiting their speeds, or if there's some other issue. If you're the operator of one of the relays listed below, can you let me know? And if someone wants to investigate further, or contact these operators on their ContactInfo, that would be great. (I don't have time right now, I'm trying to pull together a list of fallback directories before the 0.2.8-rc.) This is an incomplete list of slow relay IPs and DirPorts, starting with those with the highest consensus weight: 217.198.117.122:80 212.47.250.44:80 158.69.112.86:80 50.7.178.34:80 191.101.251.172:80 51.254.249.177:80 188.165.232.40:80 104.236.38.231:8080 89.163.225.184:9030 185.31.230.69:9030 81.7.14.227:9030 62.210.238.33:9030 164.132.56.137:9030 212.107.149.145:9030 94.23.165.33:9031 Thanks Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 1

Re: [tor-relays] Relays with broken DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

> On 31 Mar 2016, at 11:23, Michael McConville <mmcco(a)mykolab.com> wrote: > > You'll probably get through to more people if you include nicknames with > IP addresses, and if you send an email to the operators who listed their > address in ContactInfo. I was actually hoping that someone else would do that for me, I'm a little snowed under at the moment. Tim > > Thanks for this, > Mike > > Tim Wilson-Brown - teor wrote: >> Dear Relay Operators, >> >> Also while working on #17158, I found some relays whose DirPort responses made my python script hang. It wouldn't even respond to ^C, but that might just be an OS X thing, or a stem thing. >> >> I'm not sure what to do about these relays. I'd like to do a tcpdump / Wireshark check, but I don't have time at the moment. >> Would anyone like to follow this up? >> >> This is an incomplete list of broken relay IPs and DirPorts, starting with those with the highest consensus weight: >> 217.23.14.190:1194 >> 151.80.164.147:80 >> 148.251.255.92:80 >> 78.142.19.59:80 >> >> Thanks >> >> Tim >> >> Tim Wilson-Brown (teor) >> >> teor2345 at gmail dot com >> PGP 968F094B >> >> teor at blah dot im >> OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F >> > > > >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 1

Relays with broken DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

Dear Relay Operators, Also while working on #17158, I found some relays whose DirPort responses made my python script hang. It wouldn't even respond to ^C, but that might just be an OS X thing, or a stem thing. I'm not sure what to do about these relays. I'd like to do a tcpdump / Wireshark check, but I don't have time at the moment. Would anyone like to follow this up? This is an incomplete list of broken relay IPs and DirPorts, starting with those with the highest consensus weight: 217.23.14.190:1194 151.80.164.147:80 148.251.255.92:80 78.142.19.59:80 Thanks Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 0

Tor Exclude Nodes Misbehaving
by stealth＠nym.mixmin.net 30 Mar '16

30 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have edited my torrc file on my Tor Client to exclude several countries, but I keep getting the United Kingdom in my pathway. My torrc file is below: DataDirectory C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor GeoIPFile C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip GeoIPv6File C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip6 ExitNodes {PL}, {RO}, {LU}, {DK}, {CH}, {NO}, {AN}, {LI}, {IS}, {FI}, {NL}, {HU}, {BG} ExcludeNodes {US}, {CN}, {FR}, {UK}, {ES}, {IT}, {AU}, {HK}, {RU}, {PT}, {IL}, {IE}, {DE}, {CA}, {BE}, {NZ}, {PR}, {MX}, {KP}, {KR}, {GR}, {DJ}, {JP} StrictExitNodes 1 When I click on the green onion after selecting a web site, I keep getting the United Kingdom as one of my nodes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW9eAMAAoJEH1gNwhiMDZusekP/jXnkAkTIHEvytXkoRsPKvYv NY9DG0eX/n6nE4ufBAczoRgaZMCwF5BPlBio9CyiSlL4qiI0xZ9zqY1vV5+kIrYS cewQH62JvS2rj3DRykVytyHXrdRE+zvnhqqY0fqD/7+WehXkG9dQmu5TT8qfmS35 bw12EpVs6yyAR7Rfhnaha0D1fqK1ekOFkpi+bo6j7X6LMW6zPnWhzROZeqEakFtP slcGJlF+OIk2f2pTkYzhq5MHwollZ+bUqkljFLzvzl1HvK2lHMtLLSgnLcU/88hC 7bhJiOfkh7+jmpi+GMzoCRFGWLq75bufJ34acxap3P4bRnYduJ72RvUQ40+LITcj dNmtFTC/+psrdvjHBJP9XDO8FPhmVIOlEr588tjgOPQwDNHbe5t7TMEYk/8S5EzH +7ahYd9MbT03oNnVrQKbSut66LmuukDyIuvR8gP9UU2+VNmKubxVcsRlOQvDmIDR /zqT6nYrc7uCimE37Ny0K8v2R0NSwE/rVPZeP2i0dzgyHOkSPLitRDvkyLgDI+kr Wwn0cAkdzjs4428PdOnEyu+b2vLtXDcV3Q1aH32wQbMXR/o2uaY4VB6iVTjU6tlb bexKHehLYmaK0c0LKLb91mxjequDe4QEdJBUQg/vVvmwPzcvVBHXJgPmPf9uJ9W/ Szr3idQyUm4QZ6WvCAvD =FURP -----END PGP SIGNATURE-----

5 4

Who operates the bridge with nickname antirio?
by Karsten Loesing 27 Mar '16

27 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, does anybody here know who operates the bridge with nickname antirio? https://atlas.torproject.org/#details/16609212922F6F1077A1BBA299709E19F9A3F… I'm asking, because that bridge has a nice distribution of IPv4 and IPv6 clients: bridge-ip-versions v4=48,v6=64 bridge-ip-versions v4=56,v6=72 We have a bug where IPv6 addresses are included in bridge-ip-versions statistics but where consensus downloads via IPv6 addresses are not counted. It would be very valuable to test the patch for this bug on the antirio bridge or on another bridge with at least 1/2 of clients connecting via IPv6. (When looking yesterday I didn't find another bridge with that property.) The patch is commit b79d859 in my task-18460-2 branch: https://gitweb.torproject.org/karsten/tor.git/log/?h=task-18460-2 In theory it should be sufficient to cherry-pick that commit from any other recent tor branch. It just changes three lines of code. More details on the ticket: https://trac.torproject.org/projects/tor/ticket/18460 Thanks! All the best, Karsten -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJW94evAAoJEC3ESO/4X7XBs5UH/jTAcsuOl6sCJO21WuOLcMmI csq/b1IPsBvoh6YT8HBh4h07+mJSwMuWXcm3nReJsmdvjlDP4watlsEbqMgX+oxo 6GSSOX4ySS4C5bscywxXWvZIDFWPC6rToYcyfyFDmP5I+nkPNyVqsc9fBXjGJvpN uJ15bixc0iZaespKG6mQwgX8ZHi9Hf+s089voQyMEe09SscKqXHe3/50ZrLHmLPl d8BJ8Ij6WxD9ndG6FOVAUOoTunsWL8NbVSHSCJf93LOUsM6XmPjIPERyvcvnL54M uvg3kqIFTdngvLwFqzB4cETREnJtXuPIPMt8eAMLsDGtcDAuSZiqKhs1dEpJLQE= =7cQU -----END PGP SIGNATURE-----

2 2