These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

EVE through SSH

First post
Author
Previous Topic Next Topic
Nag'o
Sebiestor Tribe
Minmatar Republic
#1 - 2013-10-08 14:51:56 UTC  |  Edited by: Nag'o
Hi there.
A week ago I set up a nice SSH tunnel to play EVE through my network router without having to fiddle with the proxy server settings.

Here's what I did:
- Stablished SSH connection with my server
- Added a tunnel to route the eve IP through port 26000
- Launched EVE client through exefile.exe with "/server:127.0.0.1:26000" as starting parameter (so my local SSH client can route the packets)

I managed to play a couple of times without problems last week but today when trying to launch the EVE client I got an "incompatible protocol" message.
Did anything changed on the EVE connection protocol from last week?
Do I have to add another port to the tunnel or route an IP other than 86.237.38.200?

Thanks.

EDIT: Poking around the forums I found out this may be related to an incompatible version. I couldn't manage to run EVE from the launcher through SSH. That's because the launcher uses other IPs and ports than the main EVE server IP (86.237.38.200:26000). I am not sure if that is what is causing the problem, but if it is, is there a way for me to patch the client through SSH without having to tunnel a thousand of different connections? If there is no other way, what are the IPs and ports the launcher has to connect to for patching the client?

Brain hackz0r. Execute schizophrenia virus. Hyper-phishing activated. Downloading reality.
CCP Aporia
C C P
C C P Alliance
#2 - 2013-10-13 13:48:08 UTC
The "Incompatible Protocol" message usually shows up when your client needs to be updated.

The launcher needs to be able to establish a SSL connection between the machine it is running on and https://client.eveonline.com, and if you have network logging enabled in the launcher settings it also requires to be able to contact https://clientlogger.eveonline.com.

Friend of walking avatars, currently hibernating until he gets to open that door.
CCP Atropos
C C P
C C P Alliance
#3 - 2013-10-14 10:33:59 UTC
It also needs access to the content delivery network that's hosted at content.eveonline.com. The final IP you will end up with differs though, since it gets load balanced to the nearest edge server to you.
MailDeadDrop
Archon Industries
#4 - 2013-10-14 14:11:01 UTC
Nag'o wrote:
A week ago I set up a nice SSH tunnel to play EVE through my network router without having to fiddle with the proxy server settings.

What is your motivation for doing this? Does your router not handle NAT well?

MDD
Vincent Athena
Photosynth
#5 - 2013-10-14 15:21:21 UTC
Nag'o wrote:
Hi there.
A week ago I set up a nice SSH tunnel to play EVE through my network router without having to fiddle with the proxy server settings.

Here's what I did:
- Stablished SSH connection with my server
- Added a tunnel to route the eve IP through port 26000
- Launched EVE client through exefile.exe with "/server:127.0.0.1:26000" as starting parameter (so my local SSH client can route the packets)

I managed to play a couple of times without problems last week but today when trying to launch the EVE client I got an "incompatible protocol" message.
Did anything changed on the EVE connection protocol from last week?
Do I have to add another port to the tunnel or route an IP other than 86.237.38.200?

Thanks.

EDIT: Poking around the forums I found out this may be related to an incompatible version. I couldn't manage to run EVE from the launcher through SSH. That's because the launcher uses other IPs and ports than the main EVE server IP (86.237.38.200:26000). I am not sure if that is what is causing the problem, but if it is, is there a way for me to patch the client through SSH without having to tunnel a thousand of different connections? If there is no other way, what are the IPs and ports the launcher has to connect to for patching the client?


Its because you are running via the .exe file and CCP did an update. When that happens you got to run the launcher and let it update the client. Then you can go back to running the .exe file.

Know a Frozen fan? Check this out

Frozen fanfiction
Chi Quan
Bibkor Enterprises
#6 - 2013-10-15 17:28:26 UTC
MailDeadDrop wrote:
What is your motivation for doing this? Does your router not handle NAT well?
MDD

Playing eve at work most likely. Note that this is dangerous, Admins may be looking for SSH tunnels, even if they don't know what's inside, if it runs through their router, they may detect it and still have your ass for "inappropriate and dangerous manipulation of the corporate IT infrastructure".

-- Please like me, I'm an attention w*ore.
Nag'o
Sebiestor Tribe
Minmatar Republic
#7 - 2013-10-16 01:09:30 UTC
Yes, updating solved the problem. I had to do it manually because of the launcher though. Now that I know the domains I have to route I won't have this problem again. Thanks a lot!

I'm a dev in my company. I set up an SSH tunnel because I didn't wanted to fiddle with the proxy server settings. The SSH server is in the network gateway wich I have full acess to. The firewall on the router blocks any connections from outside the network so I guess it's safe. Well, it's never perfectly safe but since there are no top secret projects here (I work in a small transportation company) there isn't much to worry about.

Brain hackz0r. Execute schizophrenia virus. Hyper-phishing activated. Downloading reality.
Neng-Fa Zhou
Ministry of War
Amarr Empire
#8 - 2013-12-06 12:03:53 UTC
Nag'o wrote:
Hi there.


Here's what I did:
- Stablished SSH connection with my server
- Added a tunnel to route the eve IP through port 26000
- Launched EVE client through exefile.exe with "/server:127.0.0.1:26000" as starting parameter (so my local SSH client can route the packets)


Hey that is awesome but....

1. What method did you use to establish SSH connection? Putty? some other method details please.
2. What steps did you take to add a tunnel?
3. I understand your third step, it is similar to setting up for the test server.
Nag'o
Sebiestor Tribe
Minmatar Republic
#9 - 2013-12-06 12:22:09 UTC  |  Edited by: Nag'o
Neng-Fa Zhou wrote:
Nag'o wrote:
Hi there.


Here's what I did:
- Stablished SSH connection with my server
- Added a tunnel to route the eve IP through port 26000
- Launched EVE client through exefile.exe with "/server:127.0.0.1:26000" as starting parameter (so my local SSH client can route the packets)


Hey that is awesome but....

1. What method did you use to establish SSH connection? Putty? some other method details please.
2. What steps did you take to add a tunnel?
3. I understand your third step, it is similar to setting up for the test server.


Any SSH client will do as long as you know how to set up the tunnel.
The gateway machine in my network has direct acess to the internet and a proxy installed. Any other machine on the network needs to go through the proxy for internet acess and that proxy blocks all ports except the ones for web browsing. What I did was just tunnel the EVE related packets from my machine to the gateway machine for direct internet acess. I'm basically acessing the internet through the gateway's own connection instead of the proxy.
It's nothing hacky because I need an admin password for acessing the gateway machine and stabilishing the tunnel.

Brain hackz0r. Execute schizophrenia virus. Hyper-phishing activated. Downloading reality.
Neng-Fa Zhou
Ministry of War
Amarr Empire
#10 - 2013-12-06 13:26:33 UTC
hey dude I appreciate your reponse, how did you manage the ip / load balancing issue ccp atropos mentioned?
Nag'o
Sebiestor Tribe
Minmatar Republic
#11 - 2013-12-06 13:50:23 UTC
I have a dynamic tunnel for port 443 for the SSL but I realized my proxy server, although much slower, does not block the launcher content, so I have no idea if that tunnel is being used (or if the port used by the launcher SSL packets is indeed 443).

Back then I just downloaded the expansion from home and now I do the small patches through the launcher whenever I get an "incompatible protocol" message again.

Brain hackz0r. Execute schizophrenia virus. Hyper-phishing activated. Downloading reality.