Just for comparison sake, I'm running a relay on the BeagleBone Black,
running Ubuntu (raring), and Tor 0.2.4.17-rc with the following log entries:
Sep 19 16:16:40.000 [notice] Circuit handshake stats since last time:
16771/16781 TAP, 13/13 NTor.
Sep 19 17:16:40.000 [notice] Circuit handshake stat
On Wed, 18 Sep 2013 18:28:18 -0700, Andy Isaacson wrote:
> On Wed, Sep 18, 2013 at 05:43:13PM -0700, Gordon Morehouse wrote:
> > Thanks, Roger. I'm still not sure what finally caused the OOM-killer
> > crash this morning after almost a couple weeks (?) of uptime. I was
> > also seeing additio
On Wed, Sep 18, 2013 at 05:43:13PM -0700, Gordon Morehouse wrote:
> Thanks, Roger. I'm still not sure what finally caused the OOM-killer
> crash this morning after almost a couple weeks (?) of uptime. I was
> also seeing additional clock jump messages but didn't have time to
> diagnose it. The P
On Wed, 18 Sep 2013 13:16:48 -0400, josh wrote:
> You may be able to increase the ip_conntrack_max on your router. I had
I can, and have, but eventually its 16MB of RAM becomes a problem. ;)
The bigger deal, though, is I'm attempting to cobble together a set of scripts
and best practices to
On Wed, 18 Sep 2013 16:43:25 -0400, Roger Dingledine wrote:
> On Wed, Sep 18, 2013 at 06:50:46AM -0700, Gordon Morehouse wrote:
> > The replay has settled into a fairly steady state (after losing its
> > flags except Named) of sending 5-10KB more per sec than it gets. I
> > have a feeling this i
On Wed, Sep 18, 2013 at 06:50:46AM -0700, Gordon Morehouse wrote:
> The replay has settled into a fairly steady state (after losing its
> flags except Named) of sending 5-10KB more per sec than it gets. I
> have a feeling this is literally due to the TAP replies being bigger
> than the TAP request
You may be able to increase the ip_conntrack_max on your router. I had
a terrible verizon dsl router that would have its connection tracking
capacity exhausted by pings to games servers. I was able to partially
resolve the problem my telnetting (yea I know) into the router and
setting the ip_co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Addendum to addendum: the router fail is definitely caused by Tor
connections filling up the router's ip_conntrack table - once it gets
near full, it somehow interferes with a couple other services on my
router (especially DNSmasq) even if there is f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Addendum: restarting tor instantly puts my router into a tailspin this
morning. This is a WRT54G (old school, 3.0 hardware, 200MHz MIPS).
While that's old, there are many, many consumer routers out there with
similar specs and worse firmware. In th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey folks,
Here are my reports. First the good news: it's WAY more stable. Then
the bad news: it still gets OOM-killed once in a while, possibly
preventably.
THE GOOD (notes from September 14):
Here's my Pi relay since compilation of 0.2.4.17-rc
10 matches
Mail list logo
