[tor-dev] Idle connections in netstat

Angus Gardner angus at auscert.org.au
Thu Dec 20 01:34:59 UTC 2012


Just thought I would follow up on this.

Arm is a neat tool which allows 'top'-like output on a tor relay, current
bandwith, cpu utilization, connections to other relays etc.

This dose require the control-port to be enabled in your torrc file.  eg:

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
ControlPort 9051

And one of:
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#CookieAuthentication 1

Tor will now listen on port 9051 for control information, this includes
instructions to shut down (and stuff which may hurt your install) or even
list connections (which may hurt the anonymity of the Tor network.)

I also have had success in using the following:
Which binds the control port to (localhost) and is thus not
visible to the outside world. 
(Including the people on the internet port scan you just for running a Tor

Once that is set up running arm is a piece of cake.

Hope this helps someone.


-----Original Message-----
From: tor-dev-bounces at lists.torproject.org
[mailto:tor-dev-bounces at lists.torproject.org] On Behalf Of Damian Johnson
Sent: Friday, December 14, 2012 2:59 AM
To: tor-dev at lists.torproject.org
Subject: Re: [tor-dev] Idle connections in netstat

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...

tor-dev mailing list
tor-dev at lists.torproject.org

More information about the tor-dev mailing list