Your bandwidth is too low. Guards must be in the top 25% of the network by bandwidth, and that's currently in the mid 2MBps. Your node is right on that cusp, so it's going to continue to have a flickering guard node flag.
On 23.9.15 5:03, Tim Wilson-Brown - teor wrote:
On 23 Sep 2015, at 18:49, 29230912@tutanota.com mailto:29230912@tutanota.com wrote:
https://atlas.torproject.org/#details/113FCC01A29B4600A8BAA1CB72E6AB1FD899AC...
Any pointers about why my relay is flipping between guard and not guard?
There are 8 authorities, and 4 think your relay should be a guard. Whenever a 5th joins them, your relay is a guard, when it doesn’t, your relay isn’t.
See the entry in https://consensus-health.torproject.org/consensus-health.html
There are a number of factors involved in guard selection:
- Your bandwidth seems to fluctuate, which could cause the guard flag to
fluctuate as well. Unfortunately, the guard flag then causes your bandwidth to fluctuate. So it’s hard to tell what the cause is here, and whether the relay’s Guard flag is in some kind of bandwidth-driven loop. Have you looked at the bwauth votes for your relay?
- Your uptime is ok (for the last month).
- There could be other factors.
Give it a week or so to stabilise, or, alternately, limit the bandwidth to stop it fluctuating so much.
Tim (teor)
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B
teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays