So, I have a lot of experience in setting up and administering servers, but the only part I don't have that much experience with is port forwarding and other networking aspects of server administration. Never needed to until now.
I recently set up a port forward with my laptop (wireless) at home specifically for an ssh connection so I could use it as a socks proxy at work (it's not frowned on or anything illegal, but I still don't like rubbing things like gaming in my employer's face.) But then I also realized I could theoretically play with my own local server and not just log on to multiplayer ones on the internet (and this works just fine for me, by the way.)
The scenario is this: I just moved into this house so I don't have network cable run throughout, yet. So, what I've done is connect my desktop to my laptop physically. At this time, I can ssh into my laptop and then from the laptop's terminal, ssh into my desktop.
What I can't do, is to connect my proxied minecraft client to the local server being run on the desktop.
To diagram it, this is what I'd like to happen: [proxied minecraft client at work] --> [ssh tunnel] --> [laptop at home] --> [local minecraft server on desktop]
What's actually happening: [proxied minecraft client at work] --> [ssh tunnel] --> [laptop at home] -X-> [local minecraft server on desktop]
It also seems worth mentioning that 1) when I'm SSH'd in, I can pull up my router's admin page on my browser at work and 2) I tried running a local server instance on the laptop and the client still couldn't connect.
Based on the details, I assume that perhaps I also need to port forward the local server's port, but I also suspect that it may not be that simple. Has anyone else here done something similar or at least more versed in networking than I am that can help me figure this out? Many thanks in advance.
disclaimer: please forgive me if I'm breaking the rules with this post. I looked for a sticky for guidelines on posting in the server support forum and didn't find one.
Have you tried the same setup with 1.6? I use a similar setup and since upgrading to 1.7 the multiplayer connection piece seems to not respect the socks proxy settings any more. I think it may be a bug, but was going to do more testing myself before I report it.
The other option of course is to use individual port forwards instead of socks proxy, but it's more cumbersome as each server you want to reach would have to be forwarded manually. Not necessarily an issue for your situation, but for me it is.
More info: I am now convinced that this is a regression in the Minecraft 1.7.2 client. My data:
-> Tunneling through an SSH-based socks proxy from 1.6 client to 1.6 server -> Works
-> Tunneling through the same proxy from 1.6 client to 1.7 server -> Server shows up the server list as a 1.7.2 server
-> Tunneling through the same proxy from 1.7 client to 1.7 server -> Server shows up as
Furthermore, if I turn on debugging in the SSH session itself, I see a bunch of messages like "debug1: Connection to port 9999 forwarding to socks port 0 requested" when the 1.6 client loads the server list, but I see no such messages at all when the 1.7 client loads the server list.
And I'm pretty sure it's not a problem with the Java proxy settings, since both the 1.6 and 1.7 clients both assert "Client> Picked up _JAVA_OPTIONS: -DsocksProxyHost=127.0.0.1 -DsocksProxyPort=9999". There must be some new quirk in the 1.7 multiplayer engine that ignores these Java settings.