A. Dumas  wrote:
> On 27-10-2020 13:34, Chris Green wrote:
> > My Beaglebone Black (the system like a Pi) is on a boat in France
> > behind a commercial WiFi system, so I run the following on it:-
> >
> >      ssh -nNT -R 51236:localhost:22 chris@
> >
> > This connects port 22 (the sshd server port) on the Beaglebone to port
> > 51236 on myhost.  Then all you need to do is connect to port 51236 on
> > myhost and you actually connect to the Beaglebone.
>
> Ah yes, I always wanted to look into this for a Raspberry Pi I have
> somewhere else behind double NAT (carrier grade NAT). Thanks!
>
> So you  should always be up, right? Or is this robust enough to
> reconnect within reasonable time of  is down for a while?

If you use autossh it will cope with a 'not always there' myhost.
However in my case I have an intermediate 'ssh bridge' system which is
a virtual host on a commercial hosting provide so it is always there.

The 'ssh bridge' is to protect my home system from incessant ssh
attacks, my home system's firewall allows connections only from two or
three IPs, one of which is the ssh bridge.

--
Chris Green
·

--- SoupGate-Win32 v1.05