+# The user you wish to login as to create tunnels
+# The hostname/IP of the system you wish to create tunnels to
+# Set to some other port, such as 8080, if you wish to setup a SOCKS proxy as
+# well. This would allow you to access the Internet via the remote $HOST.
+# Normal tunnels to establish
+# Normal tunnels allow you to access ports on the remote $HOST by accessing
+# ports on your local system.
+# For example, the following will create a tunnel to $HOST that allows you to
+# access remote port 3389 (RDP) on local port 33890. Likewise, it allows you to
+# access remote port 5900 (VNC) on local port 59000.
+# Reverse tunnels to establish
+# Reverse tunnels allow you to access ports on your local machine by accessing
+# local ports on the remote $HOST when you're logged in on that system. This is
+# a great way to create your own little VPN of sorts.
+# For example, say your local system is PC A and your remote $HOST is PC B.
+# When logged into PC B (either normally or via SSH), the following allows you
+# to SSH into PC A. One would simply run a command like `ssh
+# pc_a_user@localhost -p 2222` on PC B.
+# AutoSSH monitoring port
+# This is used by autossh to make sure the connection is online. It should be
+# different for every configuration you plan to run simultaneously.