[network-health] Upgrade your 'eax' Tor relay?

[Ehsan Akhgari]

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 at 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/3C98FA4BA7A0F6082AAC380F5E6E23BFD540B5ED
>
> 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#PlatformspecificInstructions
>
> 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
>
>

-- 
Ehsan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/network-health/attachments/20191005/8c109b1d/attachment.html>