[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] No graph update for my relay in ATLAS

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] No graph update for my relay in ATLAS
From: teor <teor2345@xxxxxxxxx>
Date: Fri, 26 Jan 2018 20:01:06 +1100
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 26 Jan 2018 04:01:27 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=EvFKyGUno1SNSqqPRsCqCVcCsGSBOL0oe5rVaAkRTa4=; b=eeYk36jP59a9oo9CNOYHRmLvG7+mRhI2O/aQAMN2U3iz9vNeEeF4oweJhJ1+L+PF8l 2zD1J5fSQIoaJmvPPsr0kS+7y9xHneL702ApMCmmeTH6o963BqhexFczl9PcZ6cNg1h8 qhK3l21ChESYCMsjsR5DlR2+LP7yx1ZG1jWUs297C30y5yuIon9XXe2bCpk8hcmGP6IM /JeG29ljvsnGfQaxFexPIV5KrgNjOa6oJ0sYWxFQtiHJfzcv9IraM4pq8TG/WjGyLzWD pqrc5bS+A3BRAMQnCDvvW2BZl+iWk/yPQIOUcAlo13cnxn6e1DN+dlKiGXW8FuJYXVqX OcCQ==
In-reply-to: <20180126072339.GL16467@inner.h.apk.li>
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays $exit, non-exit, bridge$" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <00c501d39607$417ced00$c476c700$@df7fe.de> <20180125181853.GJ16467@inner.h.apk.li> <4824669C-A2F6-48BC-8250-108543467871@gmail.com> <20180126072339.GL16467@inner.h.apk.li>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

On 26 Jan 2018, at 18:23, Andreas Krey <a.krey@xxxxxx> wrote:

But mine (5B1F0DAF378A1FAFCFD5FA9CDC66D1023DC0276E) lost guard status
as well in december, and I have no idea as to why either - except
possibly because of running a non-recommended tor version (i.e. too
bleeding edge release branch state). That is fixed since two weeks or so,
and the addresses never changed.

No, the tor version is not used to determine the guard flag.

It's a combination of stability, speed, and age:

https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2444

Your relay may have been unstable with the extra client load in December.

Or its bandwidth might have dropped.

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

References:
- [tor-relays] No graph update for my relay in ATLAS
  - From: Peter Ott
- Re: [tor-relays] No graph update for my relay in ATLAS
  - From: Andreas Krey
- Re: [tor-relays] No graph update for my relay in ATLAS
  - From: teor
- Re: [tor-relays] No graph update for my relay in ATLAS
  - From: Andreas Krey

Prev by Author: Re: [tor-relays] [tor-dev] Marker branch for current tor release(s)
Next by Author: Re: [tor-relays] connlimit: better to use "DROP" or "REJECT --reject-with tcp-reset"?
Previous by thread: Re: [tor-relays] No graph update for my relay in ATLAS
Next by thread: Re: [tor-relays] No graph update for my relay in ATLAS
Index(es):
- Author
- Thread