[02] SSH Client Technical Support


For technical or licensing inquiries about Bitvise SSH Client, please open a new support case.

utorrent over SSH

Hi,

I am behind a university firewall that prevents incoming P2P connections.  I have set up Tunnelier as a SOCKS proxy using a remote shell account, and it works fine for browsing etc.

In tunnelier, I set a C2S tunnel with 127.0.0.1 as listen interface, 16612 as the lis. port, 0.0.0.0 as the destination host, and 16612 as the dest port.  It confirms this tunnel is working when I log in.

I then set utorrent to use 16612 as the port 'forwarded from my router" to let P2P traffic connect to utorrent. 

The problem is that this is clearly not working. Utorrent works over the SOCKS proxy, but does not accept incoming requests over 16612.

What did I do wrong?
John Braun
Saturday, August 22, 2009
 
 
The C2S tunnel is worng. Clearly, 0.0.0.0 is an invalid destination host (there is no destination with 0.0.0.0 IP). 0.0.0.0 listening interface, on the other had, refers to all available interfaces (a computer has several IPs assigned to).

SOCKSv5 (maybe also v4) has the ability to accept incoming connections too. The question is if uTorrent bothers to set up that. If it doesn't then uTorrent is most likely switching to passive mode when working through SOCKS.

You could try set it manually with S2C rule (not C2S). ListenInterface:Port=0.0.0.0:16612, DestinationHost:Port=127.0.0.1:16612. You will have to set uTorrent to listen on 16612, that its external IP = external IP of computer running SSH server, and you will have to enable active mode.

If that doesn't work, then you could try out proxifiers.
Andrej Andolsek Send private email
Monday, August 24, 2009
 
 
I am getting a message in the log that the server has allowed a S2C connection on port 16612.  Is there any way to independently test whether that SSH is actually listening on that server port, and forwarding on to my local machine?
John Braun
Tuesday, August 25, 2009
 
 
Open New Terminal Console in Tunnelier, run "netstat -an", and then examine the output. That should work both on Linux and Windows servers.
Andrej Andolsek Send private email
Tuesday, August 25, 2009
 
 
Unfortunately, when I tried this the server denied access.  If the remote server is allowing a S2C tunnel to be established when I log in, does this indicate that the port is available to be listened on?
John Braun
Thursday, August 27, 2009
 
 
If you are connecting to WinSSHD then yes.
Andrej Andolsek Send private email
Thursday, August 27, 2009
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz