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)
Hello,
I'm the operator of one of the mentioned relays (81.7.14.227). Thanks, Tim, for pointing this issue out to me. I'll try to help with this as much as I can.
So far, I have not been able to reproduce this issue. With the python script from #18688, I am getting results of approx. 0.20s.
On 01.04.2016 19:11, starlight.2016q1@binnacle.cx wrote:
These relays all appear at least somewhat overrated by BWauths and are not rate-limiting with BandwidthRate.
My server has a 100 Mbit/s interface and the options 'RelayBandwidthRate' and 'RelayBandwidthBurst' are set to 40 Mbit/s. I've reduced it to 30 Mbit/s for the time being.
DirPort performance is bad due to a saturated physical link or 'tc' bandwidth limit, so TCP congestion back-off kicks in.
I will try to do some testing next week, to see how fast/stable my network connection actually is.
On 2 Apr 2016, at 10:44, tor-contact@posteo.de wrote:
Hello,
I'm the operator of one of the mentioned relays (81.7.14.227). Thanks, Tim, for pointing this issue out to me. I'll try to help with this as much as I can.
So far, I have not been able to reproduce this issue. With the python script from #18688, I am getting results of approx. 0.20s.
It is possible that I was measuring slowdowns on my own connection, and not on the relay's connection. That's why I asked others to help me verify the issue, and work out what was going on.
That said, the list of relays in "Relays with broken DirPorts" consistently failed over repeated attempts. (The relays in "Relays with very slow DirPorts" might have been slow on my end, and might just have been slow once.)
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@lists.torproject.org
-
starlight.2016q1＠binnacle.cx -
Tim Wilson-Brown - teor -
tor-contact＠posteo.de