I have set up a no-ip account to access my ssh server at home remotely with myserver.ddns.net
, which works well.. from outside only.
From outside:
Remote ping:
$ ping myserver.ddns.net # success
Remote ssh:
$ ssh myserver.ddns.net # success
From local:
Local ping:
$ ping 192.168.2.8 # success
Local ssh:
$ ssh 192.168.2.8 # success
Remote ping:
$ ping myserver.ddns.net # success, resolving to 90.113.108.192
Remote ssh:
$ ssh myserver.ddns.net # loOong time waiting, then..
Connection closed by 90.113.108.192 port 22
Why could it be so?
internal port
andexternal port
which I've both set to 22. I couldn't find any interesting configuration options with the keywords "forward port local".. From my router point of view, what is the difference between forwarding from local and forwarding from outside? – iago-lito Feb 18 '17 at 23:31top
says it's using 0.0% CPU and ~60MB RAM. Arch has a tutorial that might be useful. – Fox Feb 18 '17 at 23:59