help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using tramp to connect to a remote emacs session


From: Michael Albinus
Subject: Re: Using tramp to connect to a remote emacs session
Date: Fri, 04 Sep 2009 13:37:53 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> Hi Michael,

Hi,

> The host name for my localhost is limited to the local network. The 
> Siemens router from my ISP (Telus) probably implements some kind of NAT 
> (I'm not sure). So the outgoing connection worked, whereas the incoming 
> connection failed.

When you have connected to the remote host, call "who":

slbpky:~> who 
albinus  tty7         2009-09-02 16:19 (:0)
albinus  pts/0        2009-09-02 16:19 (localhost:10.0)
albinus  pts/1        2009-09-04 08:29 (100.200.100.200)
albinus  pts/2        2009-09-04 08:31 (localhost:12.0)

The string "100.200.100.200" I have used instead of my real values ...
This is the IP address your router is visible in the net. You can try to
reach it from your remote host via "ping 100.200.100.200".

If you have enabled NAT forwarding of port 22 in our router (Siemens
router shall allow this), you can even try "ssh user@100.200.100.200".
You shall reach your local host from the remote one.

> I don't have a static IP, moreover from the outside I can only see my 
> ISP's servers not my home machine. Hence I can't login from the outside.

I hope you see at least your router as described above.

>> The more simple solution is to register your local machine with dynamic
>> DNS. Let's say you have registered it at http://www.dyndns.com/, under
>> the name "suvayu.homelinux.org" (just as example). Then you could
>> connect via
>>
>>    emacsclient /ssh:user@suvayu.homelinux.org:/file/to/edit
>
> This is very interesting. I had no idea such a service existed! I will 
> definitely look into this.

You shall register your router as dynamic DNS client (most routers offer
this), because this device is visible from outside, and not your local
host. And via NAT forwarding you reach the sshd daemon on your local
host.

> Thanks for your patience. :)

Best regards, Michael.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]