![]() StartingPoints Referenced by
|
Connecting Through Firewalls
Keywords: Software
FIRST DISCLAIMER - Any consequences of applying the following procedures to gain access to the internet go servers from behind a firewall are strictly and solely your own responsibility. In case of doubt, it is best to consult the system or network administrator responsible for the firewall. Sensei's Library does not take responsibility for reprimands, termination of contract or other punishments your boss may inflict on you. SECOND DISCLAIMER - Certainly one and probably both of the below setups will reveal your go server username/password combination to a third party. Think about whether you can live with that and realise that any consequences of the abuse or misuse of your account on the go server are yours and yours only. Method 1 - Socks2HTTP and SockscapStep 1
Install a program called Socks2HTTP on your PC. It will reroute socks protocol calls to the HTTP protocol. Point the rerouted HTTP calls to the HTTP proxy of the firewall. You can download a demo here Step 2
Install a program called Sockscap 32, which 'socksifies' any application. Add a new entry for your go client. Have Sockscap point to localhost and port 1080 as a socks server (where Socks2HTTP will pick it up - you get the picture).(Download here Step 3Launch Socks2HTTP, launch Sockscap, run the entry of your client, and it's as if there's no firewall in your way. Method 2 - cliser
This one is untested, but as the principle is more or less the same, it should work as well. It has the additional advantage of requiring only one piece of software. Download cliser from the author's Method 3 - SSH
This one is known to work with, at least, KGS: it's dependent on your having
Windows users can obtain a suitable SSH client through the Then, enter the following: ssh -l user remote-host -L localport:goserver:goserverport (for example, I use "ssh -l adw27 poseidon -L 2379:kgs.kiseido.com:2379"), and configure your client to connect to localhost:localport instead of the remote server's IP and port. It's worth noting that this will expose your Go server username and password, potentially, to the root user of the system you're forwarding through. However, traffic between your machine and said forwarding box will be encrypted. This is a copy of the living page "Connecting Through Firewalls" at Sensei's Library. ![]() |