Hi,
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. #HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C or #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: 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.)
Once that is set up running arm is a piece of cake.
Hope this helps someone.
Cheers, Gus
-----Original Message----- From: tor-dev-bounces@lists.torproject.org [mailto:tor-dev-bounces@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 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...
http://www.atagar.com/arm/ http://www.atagar.com/arm/images/screenshot_page2_full.png _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev