Hello, I am wondering, could you please explain exactly what “Consensus Weight” is? I had had a good uptime, about five days, then my darn computer that I run my relay off of froze for about 40 minutes this morning and I had no choice but to reboot the tor software, setting my current uptime back to 0 days. However, it has a consensus weight of 523, is this a good rating? Does this have an effect on things such as what flags a relay has (mine currently being Fast, V2Dir, Running, and Valid)? The relay in question can be found here: https://metrics.torproject.org/rs.html#details/DB1AF6477BB276B6EA5E721326840... I know the stable flag (which I have had on and off since starting my relay, don’t currently have it but relay seems to receive traffic nonetheless) depends on uptime history, not exact current uptime, but am curious, is there an easy to check my current uptime history? Also, I thought I’d share an applescript I wrote to automatically update the tor relay software and homebrew one minute after midnight every day. Here is the source code (written using AppleScript editor) do shell script "$ which brew /usr/local/bin/brew update" do shell script "$ which brew /usr/local/bin/brew upgrade tor" end When it runs, it comes up with this error, saying tor is already up to date. sh: $: command not found Error: tor 0.3.2.10 already installed (1) As this is the only error that appears, I’d take it that the script works It can be scheduled to run automatically at midnight every night via this method I found here: https://apple.stackexchange.com/questions/24862/how-can-i-configure-my-compu... I am curious to know what you all think of this tactic if you will, please let me know as you can give it to others if you wish. Thank you.
Hi,
On 22 Apr 2018, at 08:35, Keifer Bly <keifer.bly@gmail.com> wrote:
Hello,
I am wondering, could you please explain exactly what “Consensus Weight” is? I had had a good uptime, about five days, then my darn computer that I run my relay off of froze for about 40 minutes this morning and I had no choice but to reboot the tor software, setting my current uptime back to 0 days. However, it has a consensus weight of 523, is this a good rating? Does this have an effect on things such as what flags a relay has (mine currently being Fast, V2Dir, Running, and Valid)?
The relay in question can be found here: https://metrics.torproject.org/rs.html#details/DB1AF6477BB276B6EA5E721326840...
Here is the definition of consensus weight: https://metrics.torproject.org/glossary.html#consensus-weight If you still have more questions, search the archives of tor-relays@lists.torproject.org for the words "bandwidth" and "consensus weight": https://lists.torproject.org/pipermail/tor-relays/ Please feel free to ask more specific questions after reading these things.
I know the stable flag (which I have had on and off since starting my relay, don’t currently have it but relay seems to receive traffic nonetheless) depends on uptime history, not exact current uptime, but am curious, is there an easy to check my current uptime history?
As someone said in response to your last email, no, there is not. But you can see your consensus weight and flags history as graphs on:
https://metrics.torproject.org/rs.html#details/DB1AF6477BB276B6EA5E721326840...
You can get an idea of your uptime from these graphs. But please ignore the 1 month bandwidth graph, it might be empty, and it will go away soon. The longer graphs will stay. (Relays recently stopped reporting bandwidth in detail for security reasons. Search the list archives for details.)
Also, I thought I’d share an applescript I wrote to automatically update the tor relay software and homebrew one minute after midnight every day.
It looks like it would work on macOS. Most people use cron for scheduled tasks, because it works on Linux and BSDs as well. T
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? Sorry to keep emailing but trying to keep my relay as useful as possible to the network. Sent from my iPhone
On Apr 21, 2018, at 4:25 PM, teor <teor2345@gmail.com> wrote:
Hi,
On 22 Apr 2018, at 08:35, Keifer Bly <keifer.bly@gmail.com> wrote:
Hello,
I am wondering, could you please explain exactly what “Consensus Weight” is? I had had a good uptime, about five days, then my darn computer that I run my relay off of froze for about 40 minutes this morning and I had no choice but to reboot the tor software, setting my current uptime back to 0 days. However, it has a consensus weight of 523, is this a good rating? Does this have an effect on things such as what flags a relay has (mine currently being Fast, V2Dir, Running, and Valid)?
The relay in question can be found here: https://metrics.torproject.org/rs.html#details/DB1AF6477BB276B6EA5E721326840...
Here is the definition of consensus weight: https://metrics.torproject.org/glossary.html#consensus-weight
If you still have more questions, search the archives of tor-relays@lists.torproject.org for the words "bandwidth" and "consensus weight": https://lists.torproject.org/pipermail/tor-relays/
Please feel free to ask more specific questions after reading these things.
I know the stable flag (which I have had on and off since starting my relay, don’t currently have it but relay seems to receive traffic nonetheless) depends on uptime history, not exact current uptime, but am curious, is there an easy to check my current uptime history?
As someone said in response to your last email, no, there is not.
But you can see your consensus weight and flags history as graphs on:
https://metrics.torproject.org/rs.html#details/DB1AF6477BB276B6EA5E721326840...
You can get an idea of your uptime from these graphs.
But please ignore the 1 month bandwidth graph, it might be empty, and it will go away soon. The longer graphs will stay. (Relays recently stopped reporting bandwidth in detail for security reasons. Search the list archives for details.)
Also, I thought I’d share an applescript I wrote to automatically update the tor relay software and homebrew one minute after midnight every day.
It looks like it would work on macOS.
Most people use cron for scheduled tasks, because it works on Linux and BSDs as well.
T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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@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
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@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@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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 22 Apr 2018, at 12:08, Keifer Bly <keifer.bly@gmail.com> wrote:
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?
It is in seconds:
On 12 Apr 2018, at 08:33, teor <teor2345@gmail.com> wrote:
On 12 Apr 2018, at 01:33, Keifer Bly <keifer.bly@gmail.com> wrote:
Is there a way I can find out what the current weighted mbtf is? Thank you.
The thresholds vary on each directory authority. They are stable-uptime (~15 days) and stable-mtbf (~26 days) in this table: https://consensus-health.torproject.org/#flagthresholds Each figure is in seconds.
T -- teor teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
Thank you. I am just a little confused as I seem to get the stable flag randomly, sometimes after 2 days, sometimes after 4 days, sometimes longer; what I'm saying is it seems completely random. My relay appears to be under " maatuska", despite this I seem to get the stable after various numbers of days and have it suddenly revoked. Thank you very much for your help, I guess all you can do is just let the network do it's thing. It just seems like you'd need to have a wifi network and computer that basically never fail to have the stable flag. On Sat, Apr 21, 2018 at 7:22 PM, teor <teor2345@gmail.com> wrote:
On 22 Apr 2018, at 12:08, Keifer Bly <keifer.bly@gmail.com> wrote:
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?
It is in seconds:
On 12 Apr 2018, at 08:33, teor <teor2345@gmail.com> wrote:
On 12 Apr 2018, at 01:33, Keifer Bly <keifer.bly@gmail.com> wrote:
Is there a way I can find out what the current weighted mbtf is? Thank you.
The thresholds vary on each directory authority. They are stable-uptime (~15 days) and stable-mtbf (~26 days) in this table: https://consensus-health.torproject.org/#flagthresholds Each figure is in seconds.
T
-- teor
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 22 Apr 2018, at 12:40, Keifer Bly <keifer.bly@gmail.com> wrote:
Thank you. I am just a little confused as I seem to get the stable flag randomly, sometimes after 2 days, sometimes after 4 days, sometimes longer; what I'm saying is it seems completely random.
Perhaps your network is unstable. Most people can't run Tor relays a home, their home router doesn't handle the load.
My relay appears to be under " maatuska",
That's the median bandwidth authority, it has nothing to do with the Stable flag.
despite this I seem to get the stable after various numbers of days and have it suddenly revoked. Thank you very much for your help, I guess all you can do is just let the network do it's thing. It just seems like you'd need to have a wifi network and computer that basically never fail to have the stable flag.
Most relay operators run their relays in data centres. T
Maybe that’s it, unfortunately I have nowhere else I can possibly run it. What’s also not helpful is our electrical service isn’t good as it goes out every time there is some bad weather, which does not help. I guess not every relay has the stable flag, would be curious to know what the general percentage is haha.
On Apr 21, 2018, at 11:34 PM, teor <teor2345@gmail.com> wrote:
On 22 Apr 2018, at 12:40, Keifer Bly <keifer.bly@gmail.com> wrote:
Thank you. I am just a little confused as I seem to get the stable flag randomly, sometimes after 2 days, sometimes after 4 days, sometimes longer; what I'm saying is it seems completely random.
Perhaps your network is unstable. Most people can't run Tor relays a home, their home router doesn't handle the load.
My relay appears to be under " maatuska",
That's the median bandwidth authority, it has nothing to do with the Stable flag.
despite this I seem to get the stable after various numbers of days and have it suddenly revoked. Thank you very much for your help, I guess all you can do is just let the network do it's thing. It just seems like you'd need to have a wifi network and computer that basically never fail to have the stable flag.
Most relay operators run their relays in data centres.
T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I guess not every relay has the stable flag, would be curious to know what the general percentage is
You can check with [Tor Metrics][] how many relays have the Running flag and how many have the Stable flag. By looking at the graph I would estimate around 80% of Running relays have the Stable flag right now. [tor metrics]: https://metrics.torproject.org/relayflags.html?start=2018-01-22&end=2018-04-... -- 4096R/A83CE748 Valters Jansons
Thank you. However another thing that is confusing me a little is that based off of my research, relays without the stable flag shouldn’t recurve much traffic; mine says it’s received a few gigabytes since the downtime 1 day ago. Thank you. It is acceptable not to have the stable flag and still be useful to the network correct? Thank you very much. Sent from my iPhone On Apr 22, 2018, at 10:39 AM, Valter Jansons <valter.jansons@gmail.com> wrote:
I guess not every relay has the stable flag, would be curious to know what the general percentage is
You can check with [Tor Metrics][] how many relays have the Running flag and how many have the Stable flag. By looking at the graph I would estimate around 80% of Running relays have the Stable flag right now.
[tor metrics]: https://metrics.torproject.org/relayflags.html?start=2018-01-22&end=2018-04-...
-- 4096R/A83CE748 Valters Jansons _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Dear Keifer, I run a small relay at home as well. (I've never had more than 4,000/4,500 connections, and my home router seems to have had no problem.) However, guessing from the tor docs on my ISP that I should keep my monthly throughput to 1TB or so, I put some daily bandwidth limits on it. Before the dos mitigation came out a couple of months ago, I would hit the limits every other day or so, and my relay would shut down until midnight. So I never had a stable flag for months, and still had plenty of traffic. HTH, --torix Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On April 22, 2018 2:05 PM, Keifer Bly <keifer.bly@gmail.com> wrote:
Thank you. However another thing that is confusing me a little is that based off of my research, relays without the stable flag shouldn’t recurve much traffic; mine says it’s received a few gigabytes since the downtime 1 day ago. Thank you. It is acceptable not to have the stable flag and still be useful to the network correct? Thank you very much.
Sent from my iPhone
On Apr 22, 2018, at 10:39 AM, Valter Jansons valter.jansons@gmail.com wrote:
I guess not every relay has the stable flag, would be curious to know what the general percentage is
You can check with Tor Metrics how many relays have the Running
flag and how many have the Stable flag. By looking at the graph I
would estimate around 80% of Running relays have the Stable flag right
now.
-- 4096R/A83CE748 Valters Jansons
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Torix, thanks you very much. Nice to see someone who has experience with this reaching out. I got a response saying that most relays are run at data centers, not at homes, which allows them to stay stable all the time. It seems like it would be extremely difficult to impossible to maintain the stable flag on a home connection. Good to know I’m not the only one having this trouble, good to contribute nonetheless. For keeping the relay as stable as possible, what would be your recommendations? Would you agree with what I said? I ask this because to me, relay stability seems difficult to calculate. Again thanks very much. From: torix@protonmail.com Sent: Monday, April 23, 2018 5:52 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Consensus Weight Definiton Dear Keifer, I run a small relay at home as well. (I've never had more than 4,000/4,500 connections, and my home router seems to have had no problem.) However, guessing from the tor docs on my ISP that I should keep my monthly throughput to 1TB or so, I put some daily bandwidth limits on it. Before the dos mitigation came out a couple of months ago, I would hit the limits every other day or so, and my relay would shut down until midnight. So I never had a stable flag for months, and still had plenty of traffic. HTH, --torix Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On April 22, 2018 2:05 PM, Keifer Bly <keifer.bly@gmail.com> wrote:
Thank you. However another thing that is confusing me a little is that based off of my research, relays without the stable flag shouldn’t recurve much traffic; mine says it’s received a few gigabytes since the downtime 1 day ago. Thank you. It is acceptable not to have the stable flag and still be useful to the network correct? Thank you very much.
Sent from my iPhone
On Apr 22, 2018, at 10:39 AM, Valter Jansons valter.jansons@gmail.com wrote:
I guess not every relay has the stable flag, would be curious to know what the general percentage is
You can check with Tor Metrics how many relays have the Running
flag and how many have the Stable flag. By looking at the graph I
would estimate around 80% of Running relays have the Stable flag right
now.
-- 4096R/A83CE748 Valters Jansons
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (4)
-
Keifer Bly -
teor -
torix＠protonmail.com -
Valter Jansons