-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1712191133230.31253@Telcontar.valinor> On Tuesday, 2017-12-19 at 11:04 +0100, Knurpht - Gertjan Lettink wrote:
Op dinsdag 19 december 2017 10:29:20 CET schreef Bob Williams:
On Tue, 19 Dec 2017 09:16:04 +0100
Knurpht - Gertjan Lettink <knurpht@opensuse.org> wrote:
Op dinsdag 19 december 2017 08:53:26 CET schreef Bob Williams:
On Mon, 18 Dec 2017 17:18:12 +0000
Wol's lists <antlists@youngman.org.uk> wrote:
provide yourself with ssh to that box
How? Both my box and mum's box are behind TWO levels of NAT, as far as I can tell. I haven't got round to working out how to get IPv6 working at home, and mum is with a different ISP so getting it working at her end will be even more of a problem.
Do you have your own user on her machine? If so, do this, on your own (local) machine. You may have already done step 1, creating your own key pair, in which case proceed to step 2:
ssh-keygen creates the public and private keys. ssh-copy-id copies the local-host’s public key to the remote-host’s authorized_keys file. ssh-copy-id also assigns proper permission to the remote-host’s home, ~/.ssh, and ~/.ssh/authorized_keys.
Step 1: Create public and private keys using ssh-key-gen on local-host jsmith@local-host$ [Note: You are on local-host here]
jsmith@local-host$ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/home/jsmith/.ssh/id_rsa):[Enter key] Enter passphrase (empty for no passphrase): [Press enter key] Enter same passphrase again: [Press enter key] Your identification has been saved in /home/jsmith/.ssh/id_rsa. Your public key has been saved in /home/jsmith/.ssh/id_rsa.pub. The key fingerprint is: 33:b3:fe:af:95:95:18:11:31:d5:de:96:2f:f2:35:f9 jsmith@local-host
Step 2: Copy the public key to remote-host using ssh-copy-id jsmith@local-host$ ssh-copy-id -i ~/.ssh/id_rsa.pub remote-host jsmith@remote-host's password: Now try logging into the machine, with "ssh 'remote-host'", and check in:
.ssh/authorized_keys
to make sure we haven't added extra keys that you weren't expecting. Note: ssh-copy-id appends the keys to the remote-host’s .ssh/authorized_keys.
Step 3: Login to remote-host without entering the password jsmith@local-host$ ssh remote-host Last login: Sun Nov 16 17:22:33 2008 from 192.168.1.2 [Note: SSH did not ask for password.]
jsmith@remote-host$ [Note: You are on remote-host here]
The above 3 simple steps should get the job done in most cases.
Bob
The machines aren't in the same networks, and both are behind a router. You forget that on "mum's" side a port has to be forwarded on the router to her own local IP address. This will only work if "mum" gets the same external IP address from her ISP all the time. ( And I do know of situations where customers get a different IP address every other day ).
One can tackle that issue by making the remote mail it's external IP address on a regular basis ( f.e. daily ).
Or use a service like dyndns? That breaks a.s.a. the ISP brings in a new IP address.
You are both forgetting that both the OP and him mom router's external addresses are on a 10.*.*.* IP range, and probably a different one each. A service like dyndns works even if the IP changes, but not in this case, because the routers do not have routable public addreses. The can't even ping one another. Unless they are both on the same ISP, and it uses the same 10.*.*.* network for all the clients. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo47EwACgkQtTMYHG2NR9XN8ACfU18zGEnsC6AbCUBkdlGxcg4U obAAnivjLX/AsqntfABU3x9mmvX/w682 =Mjv7 -----END PGP SIGNATURE-----