AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Autossh reverse tunnel raspberry pi10/11/2023 The remoteFW has no issues with outbound connections. The usual way to get around the firewall access issue is to have the remoteRPI create the connection back to the local network. ![]() Gaining access and doing it yourself is equally impossible. Having the ‘customer’ create the hole is probably impossible. Putting holes in ‘customer’ firewalls is a difficult proposition, at best. A hole is going to be needed in the firewall. There is no direct access of remoteRPI due to the remote firewall, remoteFW. First, remoteRPI will most probably be assigned a private IP address by DHCP. There are a couple of problems with this solution. But just adding remoteRPI doesn’t make either accessible. I then wish to use putty and VNC to access remoteRPI to finally access the Arduino. I propose using a Raspberry Pi for this purpose since they are cheap. The first step to accessing the remote Arduino is to connect it serially to a networked computer. On the far right of the diagram is an Arduino ‘in the field’ and I want to access it from a local PC which is on the far left. ![]() (Jump down to the Dec 2016 Update for Notes about the Duplicity Service that will easily and quickly allow remote access to an RPI) I'd really like to make autossh work (I know I could find a workaround, like some crontab automatically relaunching my manual SSH tunnel but that'd probably be more brittle than making autossh work).This post covers how to remotely monitor / upgrade an Arduino or other MCU behind a firewall. Note that I don't think it's a firewalling issue as the "non autossh" method works fine (but then I don't get the automatic "always up" / reconnect feature). What am I not understanding here or doing wrong? It's not asking for password, it's not showing any terminal/prompt. OpenSSH_6.7p1 Debian-5+deb8u1, OpenSSL 1.0.1k ĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: /etc/ssh/ssh_config line 19: Applying options for *ĭebug1: Connecting to localhost port 20000.ĭebug1: key_load_public: No such file or directoryĭebug1: identity file /home/ksproxy/.ssh/id_rsa type -1ĭebug1: identity file /home/ksproxy/.ssh/id_rsa-cert type -1ĭebug1: Enabling compatibility mode for protocol 2.0ĭebug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u1 Here's a the -vvv output ssh -vvv -t -p 20000 If I try the correct port (20000) but this time with the -t param, same thing: it "works" but I don't get no terminal/prompt. Ssh: connect to host localhost port 1234: Connection refused If I try another port, it fails: ssh -p 1234 I tried to "-vvv" the output of the ssh commands but it just shows that nothing is going on. This "works" but it's just stuck there, doing nothing. Now I try the same but this time with autossh: $ autossh -M 20000 -N -i /home/rspi/.ssh/id_rsa ssh -p 20000 I can even access the Raspberry Pi from my desktop (by first going through the server), doing: ssh -t "ssh -p first ask for the server's password, then for the Pi's password and everything is fine. So everything works fine: I enter the password and I get a terminal/prompt. On the Rpi: $ ssh -N -R 20000:localhost:22 the server (the one with the static IP): ssh -t -p $ ![]() (I've changed the real IP here in this question to 37. to not post the server's actual IP) Now I'm trying to make autossh (from Debian / Raspbian package autossh) to work too but I'm not succeeding. The user account I'm using on the server is called "ksproxy" (it's not really a "proxy" but whatever). I managed to create a reverse SSH tunnel between a Raspberry Pi 2 and a server of mine (server which has a static IP) and it works fine. (just asked this on SO but was adviced to take it here)
0 Comments
Read More
Leave a Reply. |