Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Play World of Warcraft via SOCKS or SSH tunnel' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Play World of Warcraft via SOCKS or SSH tunnel
Authored by: sillymrman on May 31, '07 06:41:24PM
It's not working for me. Here's what I did. Punched a whole through the local proxy server using connect.c.

The SSH command is
ssh -v -g -p443 -D 8080 -C -F ~/.ssh/configelem USER@MYHOSTIP -L 6112/*/6112 -L 3724/*/3724
I then call
tsocks ./World\ of\ Warcraft &
(from within the Application's .app folder of course.)

(By the way, DarwinPorts is now MacPorts.)

WoW starts up and seems to connect through the SSH server but gets stuck at login saying "Authenticating".

My SSH output gives me the following
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 10: new [dynamic-tcpip]
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 11: new [dynamic-tcpip]
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 12: new [dynamic-tcpip]
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 13: new [dynamic-tcpip]
debug1: channel 13: cannot handle: socks4 cn 240
debug1: channel 13: free: dynamic-tcpip, nchannels 14
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 13: new [dynamic-tcpip]
channel 13: open failed: connect failed: Connection refused
debug1: channel 13: free: direct-tcpip: listening port 8080 for 0.0.0.0 port 3724, connect from 127.0.0.1 port 49923, nchannels 14
Any ideas?

[ Reply to This | # ]
Play World of Warcraft via SOCKS or SSH tunnel
Authored by: sillymrman on Jun 04, '07 07:53:36PM
Okay, I figured it out. At the bottom of the MacPorts page for tsocks, was the following message:
The tsocks.conf.sample file is in ${prefix}/etc. Rename it to tsocks.conf to use it. You should set tordns_enable to false if you're not using Tor.
I believe that that is a warning it spits out to you upon install now. So, after you install tsocks your tsocks.conf file should look like the following:
server = 127.0.0.1
server_type = 5
server_port = 1080
tordns_enable = false
We're connecting through SSH, not a Tor network so we don't want to do DNS resolution through Tor.

You will also note that I changed server_type to 5. OpenSSH can handle both versions of SOCKS and we might as well use the more recent one. This is not a necessary change.

Further, there is no need to use the -L flag. We are using SOCKS which will handle everything for us. I can connect fine using the following:
ssh -D 1080 USER@HOST
Other useful SSH flags to consider:
  • -v, -vv, or -vvv - There are three levels of debugging available to SSH. -v has the least amount of debugging output, -vvv outputs a ton.
  • -C - This enables compression across the SSH Tunnel. Data from my home server to my client machine is compressed, reducing the amount of information sent over the internet. More information, less size. This uses CPU cycles, though, and may increase your latency.
  • -fN - This will set up the SSH tunnel such that you do not get to execute remote commands (terminal acccess to the server computer) and will put the SSH process into the background. Use this if you want to set up the tunnel and just leave it.
Anyone behind an HTTP/SOCKS proxy should look into using connect.c with SSH to burrow through the proxy. Good stuff!

[ Reply to This | # ]