[tor-relays] Consensus Weight Definiton

[Keifer Bly]

My apologies if I seem worried, I am not trying to sound that way at all,
just trying to understand how all of this works.

On https://consensus-health.torproject.org/, I found this information. I am
curious, where it says  stable-uptime=, the following number is in minutes
correct?

Thank you.

Known flags <https://consensus-health.torproject.org/#knownflags>
maatuska known-flags Authority BadExit Exit Fast Guard HSDir Running Stable
V2Dir Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
tor26 known-flags Authority BadExit Exit Fast Guard HSDir Running Stable
V2Dir Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
longclaw known-flags Authority BadExit Exit Fast Guard HSDir Running Stable
V2Dir Valid FallbackDir Unmeasured DescriptorMismatch
dizum known-flags Authority Exit Fast Guard HSDir Running Stable V2Dir
Valid FallbackDir Unmeasured DescriptorMismatch
bastet known-flags Authority Exit Fast Guard HSDir Running Stable V2Dir
Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
gabelmoo known-flags Authority BadExit Exit Fast Guard HSDir Running Stable
V2Dir Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
moria1 known-flags Authority BadExit Exit Fast Guard HSDir Running Stable
V2Dir Valid FallbackDir Unmeasured DescriptorMismatch
dannenberg known-flags Authority Exit Fast Guard HSDir Running Stable V2Dir
Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
faravahar known-flags Authority BadExit Exit Fast Guard HSDir Running
Stable V2Dir Valid ReachableIPv6 NoIPv6Consensus FallbackDir Unmeasured
DescriptorMismatch
consensus known-flags Authority BadExit Exit Fast Guard HSDir NoEdConsensus
Running Stable V2Dir Valid ReachableIPv6 NoIPv6Consensus FallbackDir
Unmeasured DescriptorMismatch
Flag Thresholds <https://consensus-health.torproject.org/#flagthresholds>
maatuska flag-thresholds guard-bw-exc-exits=8390000
guard-bw-inc-exits=9970000 guard-tk=691200 stable-uptime=1508364
enough-mtbf=1 fast-speed=72000 guard-wfu=0.98 stable-mtbf=2727600
ignoring-advertised-bws=1
tor26 flag-thresholds guard-bw-exc-exits=5422000 guard-bw-inc-exits=6576000
guard-tk=691200 stable-uptime=1497887 enough-mtbf=1 fast-speed=102000
guard-wfu=0.98 stable-mtbf=2015184 ignoring-advertised-bws=0
longclaw flag-thresholds guard-bw-exc-exits=5242000
guard-bw-inc-exits=6400000 guard-tk=691200 stable-uptime=1454621
enough-mtbf=1 fast-speed=102000 guard-wfu=0.98 stable-mtbf=2850956
ignoring-advertised-bws=0
dizum flag-thresholds guard-bw-exc-exits=5242000 guard-bw-inc-exits=6424000
guard-tk=691200 stable-uptime=1464944 enough-mtbf=1 fast-speed=102000
guard-wfu=0.98 stable-mtbf=2783063 ignoring-advertised-bws=0
bastet flag-thresholds guard-bw-exc-exits=7450000
guard-bw-inc-exits=9060000 guard-tk=691200 stable-uptime=1497887
enough-mtbf=1 fast-speed=75000 guard-wfu=0.98 stable-mtbf=2619896
ignoring-advertised-bws=1
gabelmoo flag-thresholds guard-bw-exc-exits=5242000
guard-bw-inc-exits=6436000 guard-tk=691200 stable-uptime=1458892
enough-mtbf=1 fast-speed=102000 guard-wfu=0.98 stable-mtbf=2801856
ignoring-advertised-bws=0
moria1 flag-thresholds guard-bw-exc-exits=5242000
guard-bw-inc-exits=6422000 guard-tk=691200 stable-uptime=1444475
enough-mtbf=1 fast-speed=102000 guard-wfu=0.98 stable-mtbf=2750090
ignoring-advertised-bws=0
dannenberg flag-thresholds guard-bw-exc-exits=5327000
guard-bw-inc-exits=6553000 guard-tk=691200 stable-uptime=1455937
enough-mtbf=1 fast-speed=102000 guard-wfu=0.98 stable-mtbf=2162701
ignoring-advertised-bws=0
faravahar flag-thresholds guard-bw-exc-exits=7270000
guard-bw-inc-exits=8470000 guard-tk=691200 stable-uptime=1510855
enough-mtbf=1 fast-speed=101000 guard-wfu=0.98 stable-mtbf=2578082
ignoring-advertised-bws=1


On Sat, Apr 21, 2018 at 6:40 PM, teor <teor2345 at gmail.com> wrote:

> Hi,
>
> You talked about using homebrew to automatically update tor.
> How do you launch tor?
> Des homebrew restart tor when it is updated?
>
> Because tor doesn't update to the new version until you restart it.
>
> On 22 Apr 2018, at 11:06, Keifer Bly <keifer.bly at gmail.com> wrote:
>
> Thank you. And I’m not asking for a for sure response, just generally what
> you think, would an about 40 minute downtime (what I had this morning)
> majorly effect my time between failures after about 106 hours of solid
> uptime?
>
>
> If your relay fails after 106 hours, the average time before failure will
> get closer to 106 hours.
>
> If you want to know how this might affect the stable flag, you can
> find the thresholds on consensus-health, and check if they are more
> or less than 106 hours. Read people's previous responses to your
> emails for details.
>
> Sorry to keep emailing but trying to keep my relay as useful as possible
> to the network.
>
>
> The tor network has significant redundancy.
> There are thousands of relays.
> Clients adapt to changes and just use another relay.
>
> You seem really worried, so I'm going to repeat some advice from
> an earlier email:
>
> Do your best to run a relay.
> Keep it updated.
> Stop worrying.
> Just relax.
>
> T
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180421/c84a6ee4/attachment-0001.html>