I have been having great trouble logging to my Raspberry Pi server via ssh via a remote ip address.
Currently I can login to the network via the command $ ssh [email protected]
. Where 192.168.2.25 is the local ip address. However whenever I try to connect to my Raspberry Pi via a remote server with the command $ ssh pi@<external ip address> -p port number
I cannot connect.
Notes
- I have activated port forwarding on my router (Bell Home Hub 2000) ports 22 and 10747. An example of my settings are below (note the external and internal ports are the same).
- I also have the No-Ip DUC installed and running, but I have not been able to login via
$ ssh pi@<hostname.ddns.net> -p port number
either. Also pinging fails asping <hostname.ddns.net>
andping <external ip address>
has 100% packet loss. Note that I have only tried to connect by using the external ip address while still in the home intranet network. - I tried following the instructions here and here. But neither helped me solve my problem.
- Raspberry Pi is connected to the internet (apt-get and web browsers work). Currently my Raspberry Pi acts as a DNS server via Pi-hole but I plan to expand functionality once I can work remotely.
Additional Information
Routing table
$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 202 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
Linux distribution
$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
Ports enabled in /etc/ssh/sshd_config
# What ports, IPs and protocols we listen for
Port 22
Port 10474
Port scan results from Open Port Check Tool:
If there is any other information that is needed just tell me the command to run.
ssh pi@<external ip>
I get the error messagessh: Could not resolve hostname <external ip>: nodename nor servname provided, or not known
ssh: Could not resolve hostname <external ip>
was caused by a misspelled ip address. I figured out that in order to use the external ip login I have to be outside of the local network. Thank you @Sparhawk