Re: [tor-relays] Relays with broken DirPorts

> On 2 Apr 2016, at 10:44, tor-cont...@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

Re: [tor-relays] Relays with broken DirPorts

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

Re: [tor-relays] Relays with broken DirPorts

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

Re: [tor-relays] Relays with broken DirPorts

> On 31 Mar 2016, at 11:42, Tim Wilson-Brown - teor wrote: > > >> On 31 Mar 2016, at 11:23, Michael McConville > > 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 list

Re: [tor-relays] Relays with broken DirPorts

> On 31 Mar 2016, at 11:23, Michael McConville 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

[tor-relays] Relays with broken DirPorts

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 ch