> I also have had success in using the following:
> ControlListenAddress 127.0.0.1:9051
> Which binds the control port to 127.0.0.1 (localhost) and is thus not
> visible to the outside world.
> (Including the people on the internet port scan you just for running a Tor
> node.)
Or set 'ControlPort
ce of cake.
Hope this helps someone.
Cheers,
Gus
-Original Message-
From: tor-dev-boun...@lists.torproject.org
[mailto:tor-dev-boun...@lists.torproject.org] On Behalf Of Damian Johnson
Sent: Friday, December 14, 2012 2:59 AM
To: tor-dev@lists.torproject.org
Subject: Re: [tor-dev] Idle conn
Hi Gus. If you're trying to make sense of tor's netstat output then
you might find arm to be useful. Its connection panel was made for
that...
http://www.atagar.com/arm/
http://www.atagar.com/arm/images/screenshot_page2_full.png
___
tor-dev mailing list
On Thu, 13 Dec 2012 16:22:09 +, Angus Gardner wrote:
...
> Recently I have been noticing, in netstat output, a high level of
> established but idle TCP connections to other tor-hosts.
>
> (Out of 96 ESTABLISHED connections there are 90 with Recv-Q & Send-Q of 0.)
That pretty normal. Recv-Q ge
Hi,
I am fairly new to Tor and have been running a relay for a couple of weeks.
I have configured a RelayBandwithRate of only 100 KB and so only see a few
active connections at any one time.
Recently I have been noticing, in netstat output, a high level of
established but idle TCP connecti
