3.10 Tunneling, X11 forwarding, SOCKS5 proxy

Defined tunnels

List of defined tunnels. These tunnels are active when Private Shell is connected to the server.

New incoming tunnel...

Once you click this button to create a tunnel, you get the following dialog window:


• Server listens at port - server listens at this port and forwards TCP packets to Private Shell through an established SSH connection
• Host, port - Private Shell forwards received packets to this host and port

Note:
For SSH1 connection you have to re-connect to the server to apply changes.

Important Note:
In incoming tunnel settings localhost alias refers to the IP address of the computer where Private Shell resides.

New outgoing tunnel...

Once you click this button to create a tunnel you get the following dialog window:


• Client listens on port - Private Shell listens at this port and forwards TCP packets to the server through established SSH connection
• Permit connections from local host only - set this option to forbid attempts to connect to the specified port from other computers.
• Host, port - the server forwards received packets to this host and port

Note:
For an SSH1 connection you have to re-connect to the server to apply changes

Important Note:
In outgoing tunnel settings localhost alias refers to the IP address where the SSH server resides.

Edit tunnel...

Edit the selected tunnel preferences.

Note:
For an SSH1 connection you have to re-connect to the server to apply changes.

Remove tunnel

Removes the selected tunnel.

Note:
For an SSH1 connection you have to re-connect to the server to apply changes.

Forward remote X11 connections to local display

Check this box to enable forwarding of the remote X11 connections to the specified local display. Display number can be entered in the field located to the right of the box. In fact, if you select this option, Private Shell creates a tunnel on the port number 6000 + disp_num, where disp_num is the display number that you entered.

Important note for Windows XP Service Pack 2 users

Default behavior of Windows Firewall in Windows XP Service Pack 2 blocks all incoming connections including the LAN (Local Area Network). So if you define an outgoing tunnel and do not check the "Permit only connections from local host" check box, Windows Firewall will give you the next security alert when an attempt to connect to your computer is made:



When this window appears, just click the "Unblock" button and Private Shell will be added to the list of programs which are allowed to communicate through the network without any restrictions.

If you have already clicked the "Keep Blocking" button earlier, you will not be able to use defined tunnels anywhere but from your local machine. To solve this problem, open Windows Control Panel and click the "Windows Firewall" icon. Then select the "Exceptions" tab and check the box corresponding to "Private Shell GUI Client" (or add Private Shell with the "Add Program..." button if it is not already in the list):



Then click the "OK" button to close the window. Now you can use Private Shell without any restrictions.