> On 26 Jan 2018, at 18:23, Andreas Krey 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 stat
On Fri, 26 Jan 2018 08:40:46 +, teor wrote:
...
> > Clients address guards by their IP address, and they try hard
> > to only talk to their selected guard. If that guards hops to
> > another address, they have no chance of noticing that and
> > need to select another one.
>
> When the client g
> On 26 Jan 2018, at 05:06, Peter Ott wrote:
>
> Hi,
> it seems that the graph in ATLAS (1 month and 3 months) for my relay isn’t
> updated any longer for the graph ‘read…’ and ‘written bytes per second’ (last
> info was of 2018-01-01). The graph for ‘consensus weight’, ‘middle
> probability’
> On 26 Jan 2018, at 05:18, Andreas Krey wrote:
>
>> On Thu, 25 Jan 2018 19:06:40 +, Peter Ott wrote:
>> ...
>> release upgrade-. A change of the IP-adress seems to be handled fine by TOR.
>
> That is only true for the client side.
Tor relays autodetect changes in their IPv4 address, and p
On Thu, 25 Jan 2018 19:06:40 +, Peter Ott wrote:
...
> release upgrade-. A change of the IP-adress seems to be handled fine by TOR.
That is only true for the client side.
> This change by the ISP occurs at least every 3 days or so).
Clients address guards by their IP address, and they try ha
On 01/25/2018 07:06 PM, Peter Ott wrote:
> A change of the IP-adress seems to be handled fine by TOR. This change
> by the ISP occurs at least every 3 days or so).
?
--
Toralf
PGP C4EACDDE 0076E94E
signature.asc
Description: OpenPGP digital signature
__
Hi,
it seems that the graph in ATLAS (1 month and 3 months) for my relay isn't
updated any longer for the graph 'read.' and 'written bytes per second'
(last info was of 2018-01-01). The graph for 'consensus weight', 'middle
probability' etc. seems to be ok. During startup of TOR (running it on
Win
