Re: Remote Debugging

From	Paul Rubin <no.email@nospam.invalid>
Newsgroups	comp.arch.embedded
Subject	Re: Remote Debugging
Date	2019-02-27 21:35 -0800
Organization	A noiseless patient Spider
Message-ID	<87bm2wqxu6.fsf@nightsong.com> (permalink)
References	<a1c6fcec-c2a0-409b-8587-3b25038ab183@googlegroups.com>

Show all headers | View raw

gnuarm.deletethisbit@gmail.com writes:
> Essentially I want the serial port on the rPi to become a virtual
> serial port on a PC located anywhere else on the planet.  :)

The main issues here are bypassing your home firewall and the possible
lack of a static IP address on your home internet.

The approach I would suggest is

1) rent a virtual private server (VPS) with a static IP address: this
starts around $15 a year for a dedicated address and I can email you
some recommendations if you want.

2) set up a reverse ssh proxy on your raspberry pi, to connect an
inbound port on the VPS to the login port on the raspberry pi.
See here for how to do this:  https://serverfault.com/a/227268
But you want to forward to port 22 instead of 

3) You will need to set up systemd or some other supervision system on
the rpi to restart the proxy in case of a reboot (power interruption at
home while you are travelling etc.)  What OS distro are you running on
the Pi (Raspian?)  I don't know the exact command for this offhand but
someone else here might, or I can research it a little.

4. You probably want to assign a domain or subdomain name to the VPS.
So you'll run something like

    ssh yourproxy@yourdomain.com:1234

if the proxy port is 1234.  That will then forward to port 22 on your
pi, and you can login to the pi normally and run something like minicom
or whatever other serial comm program you like.

Set your home firewall to block incoming connections (your tunnel works
over an outbound one from the pi) and use public key authentication (if
you can) or strong passwords (if you have to) on both of the ssh ports.
You WILL get bad guys trying to connect to the ports and brute force the
password.  Using the nonstandard port (1234 or whatever; "standard"=22)
will help with this but be careful anyway.

The other approach of simply opening the pi's port 22 to incoming
connections works in principle, but you need a static address, and it's
generally safer to firewall off incoming connections completely rather
than open a way for someone to take over your internal home network
(especially scary if you have windows machines etc. on it).

Back to comp.arch.embedded | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-26 13:42 -0800
  Re: Remote Debugging Theo <theom+news@chiark.greenend.org.uk> - 2019-02-26 22:37 +0000
    Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-26 15:39 -0800
      Re: Remote Debugging Theo <theom+news@chiark.greenend.org.uk> - 2019-02-27 01:32 +0000
    Re: Remote Debugging Jack <jack4747@gmail.com> - 2019-02-26 22:49 -0800
    Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-27 09:08 +0100
      Re: Remote Debugging Grant Edwards <invalid@invalid.invalid> - 2019-02-27 14:49 +0000
      Re: Remote Debugging "A.P.Richelieu" <aprichelieu@gmail.com> - 2019-02-27 18:45 +0100
        Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-27 21:25 +0100
          Re: Remote Debugging "A.P.Richelieu" <aprichelieu@gmail.com> - 2019-02-27 22:12 +0100
            Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-27 23:00 +0100
              Re: Remote Debugging "A.P.Richelieu" <aprichelieu@gmail.com> - 2019-02-27 23:28 +0100
                Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-27 23:50 +0100
  Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-27 15:41 -0800
    Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-28 01:23 +0100
      Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-27 17:41 -0800
      Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-27 17:49 -0800
        Re: Remote Debugging edward.ming.lee@gmail.com - 2019-02-27 18:00 -0800
          Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-27 18:08 -0800
            Re: Remote Debugging Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2019-02-28 11:21 +0200
        Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-02-28 09:09 +0100
          Re: Remote Debugging gnuarm.deletethisbit@gmail.com - 2019-02-28 15:27 -0800
            Re: Remote Debugging David Brown <david.brown@hesbynett.no> - 2019-03-01 10:11 +0100
  Re: Remote Debugging Les Cargill <lcargill99@comcast.com> - 2019-02-27 22:07 -0600
  Re: Remote Debugging Paul Rubin <no.email@nospam.invalid> - 2019-02-27 21:35 -0800

csiph-web