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 Thu, 19 Sep 2013 07:45:17 +0200, Konrad Neitzel wrote:
> Hi all!
>
> On Wed, 2013-09-18 at 19:29 -0400, t...@t-3.net wrote:
> > Also. It makes me wonder things when, for example, you say "Think
> > bigger" while pointing to a couple of potential dollars in someone's
> > pocket. Safeguarding
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
Hi Roger,
Thanks for your quick responses, I really appreciate it! Yes, thinking
about it, this does look like an issue with the port forwarding helper. I’ve
filed the following trac issue:
https://trac.torproject.org/projects/tor/ticket/9781. I don’t have
PortForwardingHelper set in th
hehe, thanks :)
I've also checked this but my ip was reachable from my test ips.
I've now checked it with host-tracker dot com and told it my server hoster.
They now have fixed the problem.
- Christian
2013/9/19 Roger Dingledine
> On Wed, Sep 18, 2013 at 06:57:54PM +0200, Christian Dietrich w
Hi all.
Thank you for the quick replies. I understood, that there is no need to
change the node configuration regarding these points.
Even that I am not in focus right now: I am really thinking about
further steps that I would like to do (And at the moment I think about
ways how I could explain e
