Control and Monitor Tor
Note: Vidalia has been deprecated and is no longer packaged in Debian.
Arm is recommended. It is already pre-installed on Whonix-Gateway ™. 
To receive a new circuit, press:
To exit arm, press:
|Message / Question||Response|
|arm vs nyx?||The software was previously called arm, but the new name will be nyx. |
|Should any of the following Arm messages concern me?||No; see below for reasons why. See also: "Am I Compromised?" FAQ entry.|
|Am I compromised? Does Arm report leaks?||Arm is conceptually not a tool to discover serious issues such as a possible compromise or leaks. |
|Tor is preventing system utilities like netstat and lsof from working. This means that arm can't provide you with connection information. You can change this by adding 'DisableDebuggerAttachment 0' to your torrc and restarting tor. For more information see... https://trac.torproject.org/3313||If you want to learn about the technical details, read https://trac.torproject.org/3313.|
|DisableDebuggerAttachment even when running as root.||This bug in arm has now been resolved.|
|man page (GENERAL OPTIONS and COMMAND-LINE OPTIONS)||This bug in arm has now been resolved.|
|[WARN] Socks version 71 not recognized. (Tor is not an http proxy.)||
This is caused by the whonixcheck function check_tor_socks_port_reachability. It checks if a Tor SocksPort is reachable by trying to fetch it using curl.  It will not report anything if it works, but will complain if it fails.
|[WARN] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)||This occurs for similar reasons to the entry above.|
|[WARN] Rejecting request for anonymous connection to private address [scrubbed] on a TransPort or NATDPort. Possible loop in your NAT rules?||This happens for example if you run "curl 192.168.0.15". The reason is when you type "curl" in Whonix ™, by default you are not directly using curl, but a uwt-wrapped (stream-isolated) curl instead. It does not try to directly connect to 192.168.0.15, but rather to connect to 192.168.0.15 through Tor, leading to this Tor message. It really means an operation was attempted that will not work in that way. In this instance, deactivate the curl stream isolation wrapper or use the non-wrapped version - see Stream Isolation.|
|[NOTICE] You configured a non-loopback address '10.152.152.10:9179' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. [1 duplicate hidden] (Or another port number or DnsPort or TransPort.)||Tor really listens on that IP/port. It is Whonix-Gateway ™ network interface and is only available to Whonix-Workstation ™s. This restriction is enforced by an internal network with Whonix-Workstation ™(s) and because Whonix-Gateway ™ is firewalled; see /usr/bin/whonix_firewall or the Whonix ™ source code for more information.|
|[NOTICE] New control connection opened. [2 duplicates hidden] (Or more duplicates.)||This is caused by whonixcheck's Tor Bootstrap Status Test, which uses Tor's ControlPort or CPFP.|
|[NOTICE][ARM_WARN] The torrc differ from what tor's using. You can issue a sighup to reload the torrc values by pressing x. Configuration value is missing from the torrc: RunAsDaemon||Arm usability bug.  |
|"192.168.0.1 UNKNOWN 1 / Guard" in circuit information||This indicates that you are connecting to the Tor network with a Tor Bridge.
If you are directly connecting to the public Tor network without a Tor Bridge, the real IP and Nickname of the Guard should be visible instead. 
On Whonix-Gateway ™
tor-ctrl  comes bundled with Whonix ™ by default.
To get a new circuit, run.
tor-ctrl -a /var/run/tor/control.authcookie -c "signal newnym"
tor-ctrl -v -a /var/run/tor/control.authcookie -c "signal newnym"
On Whonix-Workstation ™
Interactive Tor Control Connection
Connect to the Tor control socket.
socat - UNIX-CONNECT:/var/run/tor/control
Run the following command. 
The output should show.
Command Line Tor Control Command
Run the following command. 
cmd="signal NEWNYM" && ( echo "$cmd" && sleep 1 ) | socat - UNIX-CONNECT:/var/run/tor/control
The output should show.
Repeat this command every time a new circuit is desired.
Run tor-ctrl (installed by default) with signal NEWNYM. 
bash -x tor-ctrl -p notrequired -c "signal NEWNYM"
If the following output appears at the bottom.
+ VERSION=v1 + TORCTLIP=127.0.0.1 + TORCTLPORT=9051 + TOR_COOKIE=/var/run/tor/control.authcookie + SLEEP_AFTER_CMD=1 + VERBOSE=0 + getopts :a:c:s:p:P:f:vh Option + case $Option in + PASSWORD=notrequired + getopts :a:c:s:p:P:f:vh Option + case $Option in + CMD='signal NEWNYM' + getopts :a:c:s:p:P:f:vh Option + '[' -e '' ']' + '[' 'signal NEWNYM' '!=' '' ']' + checkprogs + programs=telnet + '[' notrequired = '' ']' + for p in $programs + command -v telnet + '[' 0 '!=' 0 ']' + cmdpipe signal NEWNYM + login + '[' notrequired = '' ']' + sendcmd 'AUTHENTICATE "notrequired"' + echo 'AUTHENTICATE "notrequired"' + sleep 1 + telnet 127.0.0.1 9051 + myecho ++ cat + sendcmd signal NEWNYM + echo signal NEWNYM + sleep 1 + sendcmd QUIT + echo QUIT + sleep 1 + STR='Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '\''^]'\''. 250 OK 250 OK 250 closing connection' + vecho 'Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '\''^]'\''. 250 OK 250 OK 250 closing connection' + '[' 0 -ge 1 ']' + echo 'Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '\''^]'\''. 250 OK 250 OK 250 closing connection' ++ grep -c '^250 ' + '[' 3 = 3 ']' + exit 0
Then the process succeeded. (exit 1 is a bug in tor-ctrl, because it does not understand the double 250 OK.)
Advanced users only.
netcat provides an easy way to send Tor ControlPort protocol commands to Tor's ControlPort. 
Advanced users only.
On Whonix-Gateway ™, run.
Welcome to Stem's interpreter prompt. This provides you with direct access to Tor's control interface. This acts like a standard python interpreter with a Tor connection available via your 'controller' variable... >>> controller.get_info('version') '0.2.5.1-alpha-dev (git-245ecfff36c0cecc)' You can also issue requests directly to Tor... >>> GETINFO version 250-version=0.2.5.1-alpha-dev (git-245ecfff36c0cecc) 250 OK For more information run '/help'. >>>
Vidalia is no longer maintained.
Vidalia is recommended against because development has ceased, leading to it being removed from all Debian variants (stretch, sid etc.) as well as from Tor Browser Bundle v3.5 by The Tor Project.   Vidalia had a number of limitations, such as an inability to fully control Tor -- it could not stop Tor which came with the Debian package because it is started as user "debian-tor". It also could not edit /usr/local/etc/torrc.d/50_user.conf  and did not understand obfuscated bridges. Since Vidalia has been deprecated and provides a pretty bad and confusing user experience, it is simply better to use Arm. 
- Since Vidalia is recommended against.
- Arm works on a different level -- it is a Tor Controller. Arm talks to Tor using Tor's ControlPort and is an interface to show what Tor thinks. Neither Tor nor Arm implement anything like virus detection, compromise detection, leak detection and so on. Arm messages are generally interesting and useful, but there is rarely any cause for concern. For leak testing, see leak tests.
UWT_DEV_PASSTHROUGH=1 curl 10.152.152.10:9100
- The issue was closed as 'not a bug' several years ago.
- No login required due to Control Port Filter Proxy filtered access.
- Or potentially only to Control Port Filter Proxy if this operation is performed in Whonix-Workstation ™.
- This works also on Whonix-Workstation ™, because the anon-ws-disable-stacked-tor package has set up listening for connections on localhost and forwards them to Whonix-Gateway ™, where the Control Port Filter Proxy is listening.
- As noted by Tor developer Roger Dingledine:
Cammy is right -- we've removed the bridge/relay/exit bundles from the download page too, since Vidalia has been unmaintained for years and pointing people to unmaintained software is dangerous. I'd love to have enough developers to do everything at once, but we don't.
- It is unclear whether control commands such as New Identity were correctly processed either.
- Unless the reader is interested in Vidalia's nice network map.
Thanks to torproject.org for the arm screenshot, which is under a Creative Commons Attribution 3.0 United States License.
No user support in comments. See Support.
Comments will be deleted after some time. Specifically after comments have been addressed in form of wiki enhancements. See Wiki Comments Policy.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation.
Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee of the Open Invention Network. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)