On Mon, Sep 02, 2019 at 12:39:03PM +0200, Christoph Lohmann wrote:
> thank you for noticing me. I have updated the debian on this node. It
> is be the newest of tor in Debian now running there.
Great. It looks like it is running Tor 0.2.9.16 though? That version ("old
LTS") is still technically supported, but it will go out of support in
a few months. It would be much better to move to the deb.torproject.org
repository so you can keep up with the Tor stables better.
> My nodes were running at full speed at the beginning and soon ranked
> very high. The problem is, that when I give a maximum bandwidth, it is
> used all the time. This of course soon takes up the maximum Terabytes I
> have per VPS. My bandwidth is thus calculated to full usage all over
> the whole month.
>
> If anything, like bigger bursts is required, I'd need some way to
> configure when this is needed or maybe some way, to have pauses. I
> haven't looked up since I set up the node, if something was developed
> in tor for this case. I shouldn't be alone there.
Check out the "AccountingMax" option:
https://2019.www.torproject.org/docs/faq#LimitTotalBandwidth
You can set up AccountingMax to give it an overall monthly limit in each
direction, and then throttle the bandwidth so it doesn't use it all too
quickly, but this way you don't need to throttle it so much because it
will turn itself off for the month when it's reached the limit.
--Roger
On Mon, Oct 14, 2019 at 05:05:01PM +0200, gunes acar wrote:
> kulcosictor is upgraded to Tor 0.4.1.6.
> Thanks for the heads up.
Thanks! Your upgraded relay looks good.
I've started the process of unblacklisting the fingerprint. It will
need a threshold of the directory authorities to pull the update, so it
could be a couple of days until it takes effect, but hopefully it will
be relatively soon.
You can go to the bottom of
https://consensus-health.torproject.org/#relayinfo
and paste in your fingerprint or nickname to see progress.
--Roger
Hi Trevor,
Thanks for running a fast relay!
http://rougmnvswfsmd4dq.onion/rs.html#details/7DB8443AE29FBC450D34E55FA914F…
I notice that the server it's on is publishing very fine-grained
bandwidth information though:
https://infinity.rocketnine.space/#menu_system_submenu_network;theme=slate
Do those graphs include the relay traffic? That level of detail can
assist attackers in doing traffic correlation attacks -- for example,
if they know that a given burst of traffic happened somewhere in the
network, they can check your page to see if your relay was involved in it.
Is this level of detail published intentionally? Can we encourage you
to put it behind a login, or otherwise make it less available?
Thanks!
--Roger