On Sunday, December 17, 2017 at 8:12:19 AM UTC-5, Jens-Jørgen Kjærgaard wrote: > > > But I will try to implement your suggestions - being a little difficult, > as the rpi is on a remote location in my hut, with only intermittent power > in our dark midwinter, and I can't ssh into it, as it is on a mobile > network, changing ip with every reboot (you wouldn't have any suggestions > to solve this? Googled some answers, but it seems rather complicated). >
the standard way of dealing with this is to use dyndns. you can do it all on the pi, or you can do it on the router. usually easier to do it on the router. the router tells the dyndns service what its public-facing IP address is, then you can connect to your router using a name of your choice, no matter what the IP address is. 1) set up a dyndns account at any dyndns service. i like freedns, but many are available. choose a hostname that you can remember, e.g., yourname.mooo.com. http://freedns.afraid.org/ 2) configure your router to talk to the dyndns service you set up. 3) configure your router to forward port 22 to the rpi. this will be called 'port forwarding' in the router configuration. forward port 22 on the WAN of the router to port 22 at the LAN ip address of the rpi. 4) be sure that sshd is enabled on the rpi 5) connect to your pi with 'ssh [email protected]` you should also ensure that root is not allowed to remotely access the pi, and you should ensure that the password for the pi account is secure and not trivial. for additional security, use only PKI certificates to connect to the pi - no passwords. m -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
