There are many such solutions in the market today - AWS IoT, MS Azure IoT, and many others for large scale industries and enterprises.

Private methods to access your remote devices using authentication tokens/passwords.

No open public Ports/IP in the internet to access your remote device.

Reverse proxy tunnels with encryption technology - SSL/TLS.

So an all-round secure solution for remote device access should have the following: Anyone could still access your RPi from the internet. If they do so, it is almost similar to the port-forwarding problem. Secondly, any such reverse proxy tunneling service shouldn't create an open-ended public IP and public TCP port for you to access your device from remote locations. So you might ask, what is the right approach then?Ī better alternative and secure solution to port-forwarding is to use a Secure Reverse Proxy tunnel service (that creates SSL/TLS tunnels, preferably) that encrypts the data sent over the internet. Though this is easy, cheap and a quick hack solution, it is not a secure approach to solve your remote connectivity problem. Opening up ports in your router/firewall for all inbound traffic is similar to leaving your home or office door unsecured. My question to you is would leave your door open when you go out of our office or home so that anyone can gain access to your home or office ? If the answer is no, then why would you leave the door in your home/office router alone open to anyone in the internet to sneak in ?

I understand that you want to access your RPi while you are out of your home or office(where the RPi is located). # and ChallengeResponseAuthentication to 'no'. # PAM authentication, then enable this but set PasswordAuthentication # If you just want the PAM account and session checks to run without # the setting of 'PermitRootLogin without-password'. # PAM authentication via ChallengeResponseAuthentication may bypass # be allowed through the ChallengeResponseAuthentication and If this is enabled, PAM authentication will # Set this to 'yes' to enable PAM authentication, account processing, Subsystem sftp /usr/lib/openssh/sftp-server # Allow client to pass locale environment variables # Change to no to disable tunnelled clear text passwords # Change to yes to enable challenge-response passwords (beware issues with # To enable empty passwords, change to yes (NOT RECOMMENDED) # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication # For this to work you will also need host keys in /etc/ssh_known_hosts # Don't read the user's ~/.rhosts and ~/.shosts files #AuthorizedKeysFile %h/.ssh/authorized_keys

# Lifetime and size of ephemeral version 1 server key #Privilege Separation is turned on for security

# Use these options to restrict which interfaces/protocols sshd will bind to # What ports, IPs and protocols we listen for # See the sshd_config(5) manpage for details My ssh_config may also be useful, so here is that, in full: # Package generated configuration file I don't know what information might be helpful to provide, but looking around some similar questions 'netstat -tlpn' is usually useful: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name I get: ssh: connect to host port 22: Connection refused

I've tried forwarding port 22 on my router, but when trying: ssh I'll be moving in a few days, and the Pi isn't going with me, so I need to be able to access the Pi from a remote network, over the internet. So, I've been using SSH from an Ubuntu desktop to access my Raspberry Pi over the LAN using the command: ssh 192.168.1.185

Where dose neorouter get installed