Hi Ehsan,
Hopefully you remember me from our Mozilla All Hands meeting.
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#search/3C98FA4BA7A0F6082AAC380F5E6E23B...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for many distros / operating systems here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
Hi Roger,
Thanks for your email, and good to hear from you.
I upgraded my node to the latest version, so hopefully that issue should be resolved now. Thanks for your ping!
About the bandwidth, I checked the tor wiki docs and also my linode instance limits again, and I think I could drop the bandwidth rate limits, and just keep a total monthly cap to ensure my account doesn't exceed its monthly quota. Based on my understanding of the documentation this should be a better setup, is that correct?
Here is what my torrc looks like right now:
AccountingMax 3500 GB AccountingStart month 1 00:00
Thanks, Ehsan
On Fri, Oct 4, 2019 at 8:46 PM Roger Dingledine arma@torproject.org wrote:
Hi Ehsan,
Hopefully you remember me from our Mozilla All Hands meeting.
You are running a Tor relay, which is great:
http://rougmnvswfsmd4dq.onion/rs.html#search/3C98FA4BA7A0F6082AAC380F5E6E23B...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for many distros / operating systems here:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
On Sat, Oct 05, 2019 at 06:55:04PM -0400, Ehsan Akhgari wrote:
I upgraded my node to the latest version, so hopefully that issue should be resolved now. Thanks for your ping!
Great. It looks good now.
About the bandwidth, I checked the tor wiki docs and also my linode instance limits again, and I think I could drop the bandwidth rate limits, and just keep a total monthly cap to ensure my account doesn't exceed its monthly quota. Based on my understanding of the documentation this should be a better setup, is that correct?
Here is what my torrc looks like right now:
AccountingMax 3500 GB AccountingStart month 1 00:00
Yes, that will work. But two potential catches to be aware of:
(A) That's 3500 gigabytes in each direction, and some ISPs count a byte in and a byte out as two bytes for your monthly cap.
(B) If I'm doing my math right, 3500 GBytes per month is 1.35 MBytes/s on average. You might watch take a look at it once or twice a month, e.g. on its relay-search page, and see how much of the month it spends hibernating. If it's a lot, you might put in a few additional rules, like RelayBandwidthRate 3 MBytes RelayBandwidthBurst 50 MBytes to limit it to a long-term average of 3MB/s while still giving it a lot of room in the token bucket before the rate limiting kicks in.
See also this original faq entry: https://2019.www.torproject.org/docs/faq#LimitTotalBandwidth
Thanks! --Roger
network-health@lists.torproject.org