Hi, I have a non-exit relay running Tor 0.2.25 on a Pi. Consensus weight 37. exit-policy: reject *:* Now Iḿ back from vacation and my relay has 1600 incoming conncts and arm warns me that my bandwidth is too small to support so many incomers. Would I kindly restrict my reject policy or limit my MaxAdvertiseBandwidth. Which I believe is no longer supported(?). Can anyone help me cut down on the traffic and the notices? J. Chase
On 04/30/2014 08:42 PM, jchase wrote:
Hi, I have a non-exit relay running Tor 0.2.25 on a Pi. Consensus weight 37. exit-policy: reject *:* Now Iḿ back from vacation and my relay has 1600 incoming conncts and arm warns me that my bandwidth is too small to support so many incomers. Would I kindly restrict my reject policy or limit my MaxAdvertiseBandwidth. Which I believe is no longer supported(?). Can anyone help me cut down on the traffic and the notices?
Use RelayBandwidthRate to limit the throughput. Other than upgrading your hardware, there's not much you can optimize.
jchase jchase@riseup.net wrote:
I have a non-exit relay running Tor 0.2.25 on a Pi. Consensus weight 37. exit-policy: reject *:* Now I? back from vacation and my relay has 1600 incoming conncts and arm warns me that my bandwidth is too small to support so many incomers. Would I kindly restrict my reject policy or limit my MaxAdvertiseBandwidth. Which I believe is no longer supported(?). Can anyone help me cut down on the traffic and the notices?
Looks a lot like the relay mobbing problem again. Try adding
HidServDirectoryV2 0
to your torrc file. That appears to make the problem stop or at least become very infrequent with far fewer inbound connections. The cause of the problem really needs to be tracked down, probably by someone very familiar with the hidden services code in tor. Otherwise most of the HSDir relays may eventually disappear as more and more people are forced to turn off the hidden services directory mirror function.
Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *or* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************
On Wed, Apr 30, 2014 at 06:42:27PM +0000, jchase wrote:
Hi, I have a non-exit relay running Tor 0.2.25 on a Pi. Consensus weight 37. exit-policy: reject *:* Now I??? back from vacation and my relay has 1600 incoming conncts and arm warns me that my bandwidth is too small to support so many incomers. Would I kindly restrict my reject policy or limit my MaxAdvertiseBandwidth. Which I believe is no longer supported(?). Can anyone help me cut down on the traffic and the notices? J. Chase
First, there is no Tor 0.2.25 version.
But second, assuming you mean some old version, you should upgrade.
Depending on which relay you are (I think you didn't say?), this might have happened because you got the Guard flag: https://blog.torproject.org/blog/lifecycle-of-a-new-relay
I'm pretty much convinced at this point that trying to run a Tor relay on tiny hardware like this is not a workable idea. You could be a bridge: https://www.torproject.org/docs/faq#RelayOrBridge but I agree that's less fun.
--Roger
tor-relays@lists.torproject.org