This question came from our site for professional and enthusiast programmers.

1

Even with a dynamic IP, my server (in another country) tends to change IP so infrequently that the host often times out on no-ip.com. The bigger problem is that "apartment building's network" suggests you're behind a NAT, so simply knowing your IP-address-du-jour may not be enough.
–
tc.May 25 '10 at 1:37

Thanks for the referral. My problem is that I don't really have an external IP address. The building's router does some fancy pants stuff (as @tc suggested, a NAT) so that I don't have a single IP address. Help?
–
Steven XuMay 25 '10 at 1:43

@Steven: So your problem is not the absence of a static IP address, your problem is the absence of any public IP address. I think the wording of your question is confusing some people.
–
David ZMay 25 '10 at 6:03

Within your LAN, set your router to forward the required ports to your local computer's IP/host. Then get the DynDNS service to acquire a hostname for your router. If the router's external IP is dynamic, use ddclient to auto-update when new addresses are assigned.

You're unable to get to your computer because you're behind a NAT'ing system of some sort. In other words, your computer is on a private, internal network and being NAT'd via the building's NAT device, under their control so there is no easy way to get back in, in this sense.

One way would be to create a reverse SSH tunnel initiated from your workstation, outbound over the Internet, destined to an ssh daemon that you can connect to from home.

Once this is established, then you can ssh to localhost that you set up the reverse tunnel on (which would be redirected, via the reverse tunnel) to your system, from the ssh host that you connected to, via the reverse tunnel.

Hope this helps?

Afterwards, you may want to look into writing a small script for a cronjob to keep this connection alive, reconnect on disconnect, etc. and use ssh-agent properly, for passwordless connections - if set up properly, the passphrase would only need to be set once (if that).

This will allow you to access SSH using from Google Talk Client Apps anywhere.

There is no need for a public IP address or special setting.

I'ts Free and Open Source, Not Paying any application services anymore.

No need to open SSH port (keep your computer save)

No need to open any tunneling (e.g. VPN or somethink like that)

I made a script (tested on my raspbian OS in Raspberry Pi) so u can easily install robotito on Raspberry Pi, Debian or Ubuntu Box(debian package distribution).
this is the steps to get your linux box remotable:

Open Shell Command or u can call it Terminal, go to your home folder, Download installer script by command :

$wget https://opengateway.googlecode.com/files/robotito

after that running the script by entering command :

$sudo ./robotito

and then you can edit file credentials.rb from config folder if robotito using your gtalk account and save it by pressing ctrl+x and y . Default is using nano editor.

running the robotito from robotito folder by command

$cd robotito

$./jabbershd start

Now that this is done you can use ssh from any google talk client, don't forget to add the robotito gtalk account to your google talk account and test it with chatting each other before using the account.