Hi,
Option B: using an SSH client config file
Alternatively I have tried using an implicit jump host through SSH client
config with a slightly different way of setting up the jump host (through
netcat). This results in exactly the same errors.
Host client-machine
ProxyCommand ssh jumphost nc %h %p 2> /dev/null
Host jumphost
Hostname jumphostname
User jumphostuser
using jumphost here for backing up a remote host and it's VMs without
any problems. What BackupPC version do you use?
Doing it like this on Debian 10 buster with BackupPC 3.3.2-2:
:~# su - backuppc
$ ssh target # confirm fingerprint
$ cat ~/.ssh/config
#
Host your-real-host
HostName your-real-ip-here
Port 22 # or whatever you use
ForwardAgent yes
ForwardX11 no
User root
#
Host first-vm-on-real-host
HostName first-vm-ip-here
ForwardAgent no
ForwardX11 no
User root
Port 22
ProxyCommand ssh root@your-real-host nc %h %p
#
Host 2nd-vm-on-real-host
HostName 2nd-vm-ip-here
ForwardAgent no
ForwardX11 no
User root
Port 22
ProxyCommand ssh root@your-real-host nc %h %p
$ ssh-keygen -t rsa -b 4096
$ ssh-copy-id your-real-host
$ ssh-copy-id first-vm-on-real-host
$ ssh-copy-id 2nd-vm-on-real-host
Perhaps you have to adjust /etc/ssh/sshd_config to allow ssh-key only
access.
If you use any backuppc-wrapper-script on the real host, maybe adapt it
to the ssh forwarding.
When trying manually, make sure you do not use your own loaded ssh key
thru ssh-agent, but really use the ssh key of the backuppc user. Prove
that by:
ssh-add -l
HTH
Falko
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
