Pig Loves Cow

Just another WordPress weblog

Archive for November, 2008

WoW: WOTLK Collector’s Edition

I got my World of Warcraft: Wrath of the Lich King Collector’s Edition yesterday. Actually it’s still with my friend Richard (who lives in Canada) but he sent me the key already, and I’ll just wait for him to go here to the Phils so I can claim it haha. I spent weeks hunting for it! Thanks for all your kindness richard! Unfortunately, the only in-game benefit of having it is a mini-pet, a baby frost wyrm named Frosty! It’s so blue and cute :)

4 comments

Tunnel WoW using PuTTY and Socks Server

Uncontrollable lag? Sucky ISP? Blocked by firewalls? A solution to these annoyances…TUNNEL!

Okay, so my boyfriend Mark has been having ridiculous pings on his WoW client. We decided to try tunneling it through my PC (which would serve as the socks server) and check if he gets less latency/lag.

All we needed was the following:

  1. My server: A PC that runs ubuntu
    • Socks Server 5 (will discuss later how to install this)
    • A Tunnel Manager (gSTM)
  2. The Client: Mark’s PC
    • WoW client installed (of course!)
    • SockscapV2
    • PuTTY

I used this guide to install Socks Server 5 (SS5) on my Ubuntu machine. gSTM can be installed using Synaptic or Add/Remove Applications. I then had to make sure that my socks port can be accessed from the internet, so I set up the Port Forwarding on my router to direct all 1080 and 1890 ports (1080 is the default port for socks server, but the guide uses 1890 to prevent malicious people for taking advantage of your open port) to my internal IP.

On Mark’s side (client side), he installed SockscapV2to act as a wrapper for Wow’s proxy/socks server, and PuTTY to tunnel the socks requests to my computer via SSH.

PuTTY SSH

Putty Tunnel

Putty Tunnel

We got it working, but unfortunately didn’t fix Mark’s lag that much. It reduced it for a while, but it got higher after an hour. Oh yeah, to check that your tunnel is working, you might want to do a netstat and search for the IP you’re connecting to (or the ports you’re connecting to) — ie in this case 123.123.123.123.
2 comments