[tor-bugs] #18688 [Core Tor/Tor]: Relays should disable DirPort if RelayBandwidthRate is less than 50kb/s
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun May 21 06:22:21 UTC 2017
#18688: Relays should disable DirPort if RelayBandwidthRate is less than 50kb/s
---------------------------------------+----------------------------------
Reporter: teor | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-03-unspecified-201612 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------------------+----------------------------------
Comment (by arma):
Oh, I see what's going on here. You're actually fetching the consensus,
and seeing how long it takes, and sad that some relays are slow.
This slowness is unlikely to be because of RelayBandwidthRate. And by
unlikely, I mean it isn't. Specifically, I spot checked all of the relays
you described, and for zero of them it was because of RelayBandwidthRate.
I know this because relays put their bandwidthrates in their descriptors.
So what you really meant here was "relays should disable their dirport if
they're overloaded". But overloaded is relative, and time based, and not
something that relays have a chance to notice right now.
That said, relays do aim to return a 503 in responsive to a consensus
fetch, when they know their rate limits are going to cause them to run out
of bytes in the token bucket.
But probably the really slow relays are the ones who have set their
bandwidthrates too *high*, meaning they are experiencing all sorts of
messy congestion at the network layer because they're trying to talk too
much.
I'm tempted to close this ticket with reason "you misunderstood what
relaybandwidthrate is". Plausible?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18688#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list