Hello Everyone,
When looking at my list on Atlas (21 entries) I'm seeing that some of my relays are getting the Guard flag before they become stable.
https://atlas.torproject.org/#search/quintex
I'm going to make the assumption this is normal behavior but I still find it odd.
I also find it odd that I haven't received the stable flag all of the relays given their uptime. Thoughts, anyone?
Thank you!
John L. Ricketts, PhD Quintex Alliance Consulting john@quintex.commailto:john@quintex.com @aquintex on Twitter
On 2 Nov. 2016, at 23:42, John Ricketts john@quintex.com wrote:
Hello Everyone,
When looking at my list on Atlas (21 entries) I'm seeing that some of my relays are getting the Guard flag before they become stable.
https://atlas.torproject.org/#search/quintex
I'm going to make the assumption this is normal behavior but I still find it odd.
I also find it odd that I haven't received the stable flag all of the relays given their uptime. Thoughts, anyone?
There's a known bug with the Stable flag where downtime has a greater impact the longer the relay has been up. It really should be the other way around.
Ideally, we want any previous uptime to be better than switching relay identities. Otherwise, a new relay is better than one with history. (Which is sometimes how it works at the moment.)
Or, perhaps we want to assume that new relays will have the network average uptime. So any uptime that's better than average should improve your relay's chances of getting the Guard flag.
T
Thanks Tim :)
On Nov 2, 2016, at 16:28, teor teor2345@gmail.com wrote:
On 2 Nov. 2016, at 23:42, John Ricketts john@quintex.com wrote:
Hello Everyone,
When looking at my list on Atlas (21 entries) I'm seeing that some of my relays are getting the Guard flag before they become stable.
https://atlas.torproject.org/#search/quintex
I'm going to make the assumption this is normal behavior but I still find it odd.
I also find it odd that I haven't received the stable flag all of the relays given their uptime. Thoughts, anyone?
There's a known bug with the Stable flag where downtime has a greater impact the longer the relay has been up. It really should be the other way around.
Ideally, we want any previous uptime to be better than switching relay identities. Otherwise, a new relay is better than one with history. (Which is sometimes how it works at the moment.)
Or, perhaps we want to assume that new relays will have the network average uptime. So any uptime that's better than average should improve your relay's chances of getting the Guard flag.
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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Wed, Nov 02, 2016 at 12:42:18PM +0000, John Ricketts wrote:
When looking at my list on Atlas (21 entries) I'm seeing that some of my relays are getting the Guard flag before they become stable.
https://atlas.torproject.org/#search/quintex
I'm going to make the assumption this is normal behavior but I still find it odd.
I agree that this particular behavior is odd. In fact, we put in a fix to prevent it from happening:
https://gitweb.torproject.org/tor.git/tree/ChangeLog?id=tor-0.2.9.4-alpha#n6... https://trac.torproject.org/projects/tor/ticket/18624
But that fix is only in 0.2.9.1-alpha, and 7 of the 8 directory authorities are still on 0.2.8.x. So they'll get it when they upgrade (which will be a ways after 0.2.9.x goes stable probably).
As for why the Stable flag is confusingly assigned, teor's answer is a good one.
--Roger
Thank you Roger.
On Nov 3, 2016, at 01:01, Roger Dingledine arma@mit.edu wrote:
On Wed, Nov 02, 2016 at 12:42:18PM +0000, John Ricketts wrote: When looking at my list on Atlas (21 entries) I'm seeing that some of my relays are getting the Guard flag before they become stable.
https://atlas.torproject.org/#search/quintex
I'm going to make the assumption this is normal behavior but I still find it odd.
I agree that this particular behavior is odd. In fact, we put in a fix to prevent it from happening:
https://gitweb.torproject.org/tor.git/tree/ChangeLog?id=tor-0.2.9.4-alpha#n6... https://trac.torproject.org/projects/tor/ticket/18624
But that fix is only in 0.2.9.1-alpha, and 7 of the 8 directory authorities are still on 0.2.8.x. So they'll get it when they upgrade (which will be a ways after 0.2.9.x goes stable probably).
As for why the Stable flag is confusingly assigned, teor's answer is a good one.
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
John Ricketts -
Roger Dingledine -
teor