-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
You only mentioned the 100TB plan limit, this is why I suggested
AccountingMax. I couldn't have guessed you are talking about some
other policy limits.
The consensus weight is your bandwidth measured by the bandwidth
authorities. This is used by clients to calculate your relay's
probability from being chosen in a circuit. If it's big, yes of course
it will attract more clients. If you rate-limit it in torrc, the
bandwidth authorities won't be able to measure more than what you are
offering. Maybe use this:
MaxAdvertisedBandwidth N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits
If set, we will not advertise more than this amount of bandwidth
for our BandwidthRate. Server operators who want to reduce the number
of clients who ask to build circuits through them (since this is
proportional to advertised bandwidth rate) can thus reduce the CPU
demands on their server without impacting network performance.
On 10/1/2015 4:22 PM, Dhalgren Tor wrote:
> On Thu, Oct 1, 2015 at 1:10 PM, Tim Wilson-Brown - teor
> <teor2...@gmail.com> wrote:
>>
>> Can you help me understand what you think the bug is?
>
> Relay is assigned a consensus weight that is too high w/r/t rate
> limit. Excess weight appears to be due to high quality of TCP/IP
> connectivity and low latency of relay. Result is overloaded relay
> and poor end-use latency.
>
>> Is Tor using more bandwidth that the BandwidthRate?
>
> No, but relay is loaded to flat-line maximum and clearly is
> attracting too many circuits.
>
>> If so, this is a bug, and should be reported on the Tor Trac.
>
> Not interested in doing that. Looking for a way to get it work.
>
> If the relay stays overloaded I'll try a packet-dropping IPTABLES
> rule to "dirty-up" the connection.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBCAAGBQJWDTZZAAoJEIN/pSyBJlsRRXkH/2IpuxK6s0KKzq7fEMBJO+/I
/uiL2/6WGcT7L/aaFQqigqjtQ3eQpAXY6CVV9KRqfVukhjjqBTrauZ+WvfYhz0dJ
vWTeyOfpfEwMp8J3XYNrd6noBfgCR9oX3aBE9K+RRPhTGWYLjxnleAOh22t5AeA3
dYG+XoG27bKYnf4sj8y9+kibiId8Guroh54Y6F8QT3lF4j1C2nPb24y1cHn0atEG
ONWFeM8oVNGuliO3T9z5JkIhxBvOiK3DgGDM0jV1+cf8GAUDHGU4xYSX6vBlqrTc
r1aWTDuqVE98tLA38WyjSHc+a3+dfDBiJcpr0h7dFXT1GrjipYkO5VLkBPgsSjI=
=mWbS
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
