SshTunnel
From MLDonkey
Contents |
Using Ssh Tunnel to remote control mldonkey
Assume your mldonkey runs on a secured box listening only on localhost for gui connections (port 4001). If the box allows ssh connections and port-forwarding, simply connect from your client workstation (e.g. on work) with an ssh terminal.
ssh -L4001:127.0.0.1:4001 youruser@yourbox.dyndns.org
This sets up a tunnel from your client to yourbox. All communications will be encrypted. Now simply connect your mldonkey gui to localhost using the default settings.
This works also for Cygwin using openssh.
Using Putty to tunnel
Putty is a small and handy telnet/ssh application for windows. It does not require an install. (I never leave home without a floppy disc with putty =). Get it from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
- Fill in the fields for a normal ssh connection to your remote machine.
- Add, in the "Tunnels" section, source port 4001 and destination 127.0.0.1:4001. Ensure that "Local" is selected and press add. (For telnet replace 4001 with 4000 and for the webinterface replace 4001 with 4080.)
- Open the session and log in as usual.
- Now you can connect your local gui to localhost:4001.
More
- Of course the web interface (4080) and the telnet (4000) connection can be tunneled as well.
- If you have an IPv6-enabled system (like OpenBSD) you should start the ssh-server with "sshd -4" or else the tunneling won't work
- You can bind mldonkey gui/http/telnet to your internal network adress (e.g. 192.168.0.1) to allow unencrypted traffic from your lan, while ssh-ing from the outside. (just replace 127.0.0.1 in the above, and change your bind addresses)
- If you're on a slow connection, compression can help; add "-C" to the command line.
See also
- ApacheRedirection
- Secure_web_access_via_ssl_of_your_mldonkey_client
- AuthenticateWebInterfaceUsingApache
Languages: English