Thanks for the replies guys - I've not has a storm in the last few days,
but if/when my Pi gets knocked offline again, I'll dig into those
mitigation strategies. Think in the meantime I need to do a bit more
reading about how the network maintains stability etc
Best,
Chris
On 20 October 2013 19
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Chris Whittleston:
> Do you think it might help to restart tor every 24 hours or so
> using cron Dan - or would that adversely affect the network too
> much/not actually help?
Generally restarting a Tor relay is something you want to do as little
as
Gordon has pre-built packages[1], but I just downloaded the source and
built it myself: https://www.torproject.org/download/download.html.en
(unstable/alpha version).
-Dan
[1]
https://github.com/gordon-morehouse/cipollini/tree/master/raspbian_packages
On 10/20/2013 01:49 PM, Jochen Fahrner wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.10.2013 17:25, schrieb Dan Staples:
> I recently upgraded my Pi to
> Tor v0.2.4,
How did you do that? Is there some deb package for the Pi available?
- --
Mit besten Grüßen
Jochen Fahrner
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dan Staples:
> Thanks Gordon, I've been following your posts about the
> circuit-creation storms with interest. I recently upgraded my Pi
> to Tor v0.2.4, and haven't witnessed a storm yet (they are
> relatively rare for me). But I am certainly inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks Gordon, I've been following your posts about the
circuit-creation storms with interest. I recently upgraded my Pi to
Tor v0.2.4, and haven't witnessed a storm yet (they are relatively
rare for me). But I am certainly interested in trying out y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dan Staples:
> In my experience, setting the bandwidth advertising options does
> nothing to stop the "storms" of circuit creation requests.
This is absolutely correct, and I've been working on this problem with
the Pi for months now.
> It *will*
I run a few Rasp PI relays. If you use Tor 2.3.5 you need to limit
bandwidth to 100KB or less and make sure the CPU is not overclocked to
avoid heating issues unless you stick it in the fridge or something.
2.4.17 is much better at dealing with circuit storms, i can push 3Mbps
upstream with no iss
I don't think it would make a difference. When my relay is experiencing
a circuit-creation storm, I've restarted Tor, and even stopped it for a
few minutes, but as soon as it comes back online, it gets slammed
again. Only leaving it offline for an hour or so and then turning it
back on seems to
Do you think it might help to restart tor every 24 hours or so using cron
Dan - or would that adversely affect the network too much/not actually help?
On 14 Oct 2013 22:32, "Dan Staples" wrote:
> In my experience, setting the bandwidth advertising options does
> nothing to stop the "storms" of ci
In my experience, setting the bandwidth advertising options does
nothing to stop the "storms" of circuit creation requests. It *will*
affect the *average* bandwidth used by your relay, but every once in a
while, I'll still get circuit-creation storms that completely overwhelm
my RPi and knock i
Ok - I have 0.2.4.17-rc built and running on the Pi - I'll give it 24-48
hours to see if the same problem with sudden increases in the number of
circuits happens again, then try the MaxAdvertisedBandwidth setting in case
it helps.
Will drop feedback here in a couple of days - thanks for the help a
Thanks Logforme - yeah I was trying that before I sent the first email in
this chain, but maybe I didn't go low enough with the advertised bandwidth.
When the 0.2.4 compilation is done (it's still chugging along) I'll try
going lower and see if it helps.
Chris
On 14 October 2013 21:38, Logforme
On 2013-10-14 22:01, Chris Whittleston wrote:
> I see - so I'll probably still see the problem with a huge number of
> circuits being created after I've finished building 0.2.4. Is there
> any way to limit this, I'm guessing reducing the bandwidth wouldn't
> actually help? I guess I'll look into ho
On Mon, Oct 14, 2013 at 08:36:58PM +0100, Chris Whittleston wrote:
> Aha - makes sense, I'll just build it myself. Thanks for the quick response.
>
> So - the new handshake in 0.2.4.x doesn't help with the ongoing issues? On
> that page I linked it was suggested it might...
It would help except t
I see - so I'll probably still see the problem with a huge number of
circuits being created after I've finished building 0.2.4. Is there any way
to limit this, I'm guessing reducing the bandwidth wouldn't actually help?
I guess I'll look into how much further I can overclock the CPU...
Chris
On
On Mon, Oct 14, 2013 at 08:36:58PM +0100, Chris Whittleston wrote:
> Aha - makes sense, I'll just build it myself. Thanks for the quick response.
>
> So - the new handshake in 0.2.4.x doesn't help with the ongoing issues? On
> that page I linked it was suggested it might...
It does help! It helps
Aha - makes sense, I'll just build it myself. Thanks for the quick response.
So - the new handshake in 0.2.4.x doesn't help with the ongoing issues? On
that page I linked it was suggested it might...
Chris
On 14 October 2013 20:33, Roger Dingledine wrote:
> On Mon, Oct 14, 2013 at 08:26:52PM
Hey guys,
So I just started running a non-exit relay on a Raspberry Pi, and have hit
a problem where it seems huge numbers of circuits are being created which
overwhelms the system and can cause tor to crash. I read here (
https://blog.torproject.org/blog/how-to-handle-millions-new-tor-clients)
th
On Mon, Oct 14, 2013 at 08:26:52PM +0100, Chris Whittleston wrote:
> So I just started running a non-exit relay on a Raspberry Pi, and have hit
> a problem where it seems huge numbers of circuits are being created which
> overwhelms the system and can cause tor to crash. I read here (
> https://blo
20 matches
Mail list logo
