- Open the SSH Tunnel Manager Preferences window by doubleclicking the icon.
- Click the "+" button to create a new tunnel.
- Enter a name for the tunnel.
- Enter your Login (username only, no "@cotse.net").
- Enter the server you have been assigned in the Host field (The server is listed in the email you received from us.)
- Enter the port to connect to the server on (either 22, 2222, 80, or 443).
You've now completed everything you need to get connected to the Cotse SSH Tunnel server, but you are not yet proxied through our SSH Tunnel server. To accomplish that, you will need to set up some tunnels as described below and in the next column.
Creating an HTTP Tunnel
In the Local redirections box in the Preferences window:
- Enter 8082 (or other local port) in the left column.
- Enter the server you have been assigned in the LAN Host column (ex: tunnel1.cotse.net).
- Enter the server port to use in the right column (8080 for filtered, 8888 for unfiltered).
- Click "Options" and make choices in the window (Auto-Connect and Handle Authentication suggested).
- Check the "Open tunnels list at run time" box at the top of the window.
- Close the Preferences window.
- In the Tunnel Manager menu bar, click "Window", then "Show Tunnels".
- Click the button to open/close the tunnel as desired. This allows HTTP forwarding from your machine, across the SSH Tunnel to our server which is running a web proxy on ports 8080/8888.
Open Safari and edit your proxy connection settings (other browsers have similar setup):
- Check the box beside "Web Proxy".
- Enter localhost for server
- Enter 8082 for (or whatever Source Port field you used in setting up Tunnel Manager, above) for the port
- Repeat above 3 steps for "Secure Web Proxy"
- Enter any URLs you don't want to proxy to in the Bypass box
- Click "Apply Now"
You're all set. Now all you have to do to use your setup is:
- Launch SSH Tunnel Manager.
- Click "Window" and "Show Tunnels".
- Click the button beside your tunnel's name to open the tunnel.
- A window should open, enter your Cotse password at the prompt and wait for the "Connected" dialog.
- Open your browser.
If you would like to check your proxy configuration to make sure that you're connected via tunnel, go to Cotse.com's proxy check and make sure that the IP shows tunnel's IP and not your own IP.
Note that tunnel may disconnect you if you are idle for too many hours and you may need to open a new tunnel session.
|
Listed below you will find an example of how to set up another type of tunnel: a direct forward to a usenet service.
You may use the Cotse SSH Tunnel to tunnel from your machine to a third party usenet client such as Supernews or any other service you have an account with. The following instructions can be used not only for usenet, but for any other type of service (including email):
With SSH Tunnel Manager open:
- Click either "SSH Tunnel Manager / Preferences" in the menu bar, or "Configuration" in the tunnel window.
- In the left window, choose the tunnel you created above.
- In the "Local redirections" window, click the "+" button to create a new tunnel.
- In the left column of the new line, enter an unprotected port number (any port above 1024, because SSH Tunnel Manager will not allow forwarding of protected ports).
- For the LAN Host, enter: your.usenetprovider.net (e.g., supernews.com).
- In the right column, enter 119 (the default usenet port on the host computer).
Close the window. Your Cotse SSH Tunnel Session allowing you to forward from your machine, through the Cotse SSH Tunnel to your.usenet provider, is saved.
You will now need to setup your desktop usenet client to use localhost and the local port assigned above as the "server". This will forward across the SSH Tunnel, through our server to your usenet provider.
This will hide your IP address from your usenet provider and your IP address won't be found in your usenet post headers.
The above session is an example of a general forward and may be used with other services (other than usenet). You may add as many forwards/tunnels as you would like, just make sure to NEVER use the same port, either locally or on the same remote server. You'll break the setup and have trouble.
|
