[tor-relays] Unwarranted discrimination of relays with dynamic IP

[teor]

> On 28 Dec 2016, at 02:50, Rana <ranaventures at gmail.com> wrote:
> 
> Speaking of guards, could someone come with a theory pf what happened here? The IP is static, the relay exists for 18 days and has Stable flag since maybe 2 weeks, the measured bandwidth -153 KB/s - exactly equals the bandwidth limit in torrc for 2 weeks now. What could explan the sudden catastrophic drop in bandwidth after linear if not exponential growth? This articledescribes exactly this pattern but the drop occurs when a Guard flag is awarded. In this case, no guard fag. Any ideas?

When your relay reaches its bandwidth rate, it has no spare capacity.
Therefore, the bandwidth authority measurements (and consensus
weight) are lower.

Since the consensus weight is lower, clients use the relay less.
The relay has spare capacity, and the bandwidth authority measurements
(and consensus weight) are higher.

This feedback process continues until the relay utilisation and
consensus weight stabilise.

(Large page)
https://consensus-health.torproject.org/consensus-health-2017-01-03-02-00.html#707A9A3358E0D8653089AF32A097570A96400CC6

In this particular case, the changes are large.
This might be because:
* the bandwidth rate is low,
* the connection speed is high compared to the bandwidth rate,
* the IP address changes, or
* the relay restarts, or
* perhaps some other reason.

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20170103/32fb61b1/attachment.sig>