Re: [BackupPC-users] double hop rsync

[gregrwm]

On Tue, Mar 16, 2021 at 10:50 AM Alexander Kobel  wrote:

> Hi Greg,
> On 3/16/21 4:27 PM, gregrwm wrote:
> > On Tue, Mar 16, 2021 at 8:45 AM  backu...@kosowsky.org>> wrote:
> > gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
> >  > i'm trying to use a double hop rsync to backup a server that can
> only be
> >  > reached indirectly.  a simple test of a double hop rsync to the
> target
> >  > server seems to work:
> >  >
> >  >   #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh
> -xq"
> >  > --rsync-path=sudo\ /usr/bin/rsync 192.168.1.243:
> /var/log/BackupPC/.bashrc
> >  > /tmp
> >  > receiving incremental file list
> >  > .bashrc
> >  > 231 100%  225.59kB/s0:00:00 (xfr#1, to-chk=0/1)
> >  >   0#
> >  >
> >  > which demonstrates that the backuppc keys, sudo settings, and
> double hop
> >  > rsync all work.
> >  >
> >  > here's my double hop settings:
> >  > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq
> 192.168.1.243 sudo
> >  > /usr/bin/rsync $argList+';
> >  > $Conf{ClientNameAlias} = '192.168.128.11';
> >
> > Why don't you try using the 'jump' host option on ssh.
> > -J 192.168.128.11
> >
> > seems like a really good idea.  so i tried:
> >
> > $Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 sudo /usr/bin/rsync
> $argList+';
> > $Conf{ClientNameAlias} = '192.168.1.243';
> >
> > and got:
> > Got remote protocol 1851877475
> > Fatal error (bad version): channel 0: open failed: connect failed: Name
> or service not known
> > stdio forwarding failed
> > Can't write 1298 bytes to socket
> > fileListReceive() failed
> >
> > if you've any ideas how to tweak that and try again i'm eager,
>
> any luck with the ProxyJump config option? I use this in my BackupPC
> user's ~/.ssh/config to keep the BackupPC config as clean as possible.
> See, e.g., https://wiki.gentoo.org/wiki/SSH_jump_host#Multiple_jumps
>
> Probably, in your case it would be something like
>
> Host client
> HostName192.168.1.243
> ProxyJump   192.168.1.243
>
> HTH,
> Alex
>

and the winning magic incantation is...
$Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 192.168.1.243  sudo
/usr/bin/rsync $argList+';
$Conf{ClientNameAlias} = '127.0.0.1';

thank you alex and @kosowsky
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Re: [BackupPC-users] double hop rsync

[backuppc]

Alexander Kobel wrote at about 16:50:46 +0100 on Tuesday, March 16, 2021:
 > Hi Greg,
 > 
 > On 3/16/21 4:27 PM, gregrwm wrote:
 > > On Tue, Mar 16, 2021 at 8:45 AM  > > wrote:
 > > 
 > > gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
 > >  > i'm trying to use a double hop rsync to backup a server that can 
 > > only be
 > >  > reached indirectly.  a simple test of a double hop rsync to the 
 > > target
 > >  > server seems to work:
 > >  >
 > >  >   #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
 > >  > --rsync-path=sudo\ /usr/bin/rsync 
 > > 192.168.1.243:/var/log/BackupPC/.bashrc
 > >  > /tmp
 > >  > receiving incremental file list
 > >  > .bashrc
 > >  >             231 100%  225.59kB/s    0:00:00 (xfr#1, to-chk=0/1)
 > >  >   0#
 > >  >
 > >  > which demonstrates that the backuppc keys, sudo settings, and 
 > > double hop
 > >  > rsync all work.
 > >  >
 > >  > here's my double hop settings:
 > >  > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 
 > > 192.168.1.243 sudo
 > >  > /usr/bin/rsync $argList+';
 > >  > $Conf{ClientNameAlias} = '192.168.128.11';
 > > 
 > > Why don't you try using the 'jump' host option on ssh.
 > > -J 192.168.128.11
 > > 
 > > 
 > > seems like a really good idea.  so i tried:
 > > 
 > > $Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 sudo /usr/bin/rsync 
 > > $argList+';
 > > $Conf{ClientNameAlias} = '192.168.1.243';
 > > 
 > > and got:
 > > Got remote protocol 1851877475
 > > Fatal error (bad version): channel 0: open failed: connect failed: Name or 
 > > service not known
 > > stdio forwarding failed
 > > Can't write 1298 bytes to socket
 > > fileListReceive() failed
 > > 
 > > if you've any ideas how to tweak that and try again i'm eager,
 > 
 > any luck with the ProxyJump config option? I use this in my BackupPC user's 
 > ~/.ssh/config to keep the BackupPC config as clean as possible.
 > See, e.g., https://wiki.gentoo.org/wiki/SSH_jump_host#Multiple_jumps
 > 
 > Probably, in your case it would be something like
 > 
 > Host client
 >  HostName192.168.1.243
 >  ProxyJump   192.168.1.243
 > 
 > 
 > HTH,
 > Alex

Of course as per the man page "This [-J] is a shortcut to specify a
ProxyJump configuration directive."

You may need a '-t' to force a pseudo-terminal allocation.
Also, make sure you have access to the right identity file.
Proxy jumps are really powerful... suggest you play with them first
outside of BackupPC and then seek help after you have gotten the hang
of it.


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Re: [BackupPC-users] double hop rsync

[Alexander Kobel]

Hi Greg,

On 3/16/21 4:27 PM, gregrwm wrote:
> On Tue, Mar 16, 2021 at 8:45 AM  > wrote:
> 
> gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
>  > i'm trying to use a double hop rsync to backup a server that can only 
> be
>  > reached indirectly.  a simple test of a double hop rsync to the target
>  > server seems to work:
>  >
>  >   #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
>  > --rsync-path=sudo\ /usr/bin/rsync 
> 192.168.1.243:/var/log/BackupPC/.bashrc
>  > /tmp
>  > receiving incremental file list
>  > .bashrc
>  >             231 100%  225.59kB/s    0:00:00 (xfr#1, to-chk=0/1)
>  >   0#
>  >
>  > which demonstrates that the backuppc keys, sudo settings, and double 
> hop
>  > rsync all work.
>  >
>  > here's my double hop settings:
>  > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 192.168.1.243 
> sudo
>  > /usr/bin/rsync $argList+';
>  > $Conf{ClientNameAlias} = '192.168.128.11';
> 
> Why don't you try using the 'jump' host option on ssh.
> -J 192.168.128.11
> 
> 
> seems like a really good idea.  so i tried:
> 
> $Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 sudo /usr/bin/rsync 
> $argList+';
> $Conf{ClientNameAlias} = '192.168.1.243';
> 
> and got:
> Got remote protocol 1851877475
> Fatal error (bad version): channel 0: open failed: connect failed: Name or 
> service not known
> stdio forwarding failed
> Can't write 1298 bytes to socket
> fileListReceive() failed
> 
> if you've any ideas how to tweak that and try again i'm eager,

any luck with the ProxyJump config option? I use this in my BackupPC user's 
~/.ssh/config to keep the BackupPC config as clean as possible.
See, e.g., https://wiki.gentoo.org/wiki/SSH_jump_host#Multiple_jumps

Probably, in your case it would be something like

Host client
HostName192.168.1.243
ProxyJump   192.168.1.243


HTH,
Alex

> thank you,
> greg
> 
> 
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
> 



smime.p7s
Description: S/MIME Cryptographic Signature
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Re: [BackupPC-users] double hop rsync

[gregrwm]

On Tue, Mar 16, 2021 at 8:45 AM  wrote:

> gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
>  > i'm trying to use a double hop rsync to backup a server that can only be
>  > reached indirectly.  a simple test of a double hop rsync to the target
>  > server seems to work:
>  >
>  >   #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
>  > --rsync-path=sudo\ /usr/bin/rsync 192.168.1.243:
> /var/log/BackupPC/.bashrc
>  > /tmp
>  > receiving incremental file list
>  > .bashrc
>  > 231 100%  225.59kB/s0:00:00 (xfr#1, to-chk=0/1)
>  >   0#
>  >
>  > which demonstrates that the backuppc keys, sudo settings, and double hop
>  > rsync all work.
>  >
>  > here's my double hop settings:
>  > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 192.168.1.243
> sudo
>  > /usr/bin/rsync $argList+';
>  > $Conf{ClientNameAlias} = '192.168.128.11';
>
> Why don't you try using the 'jump' host option on ssh.
> -J 192.168.128.11
>

seems like a really good idea.  so i tried:

$Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 sudo /usr/bin/rsync
$argList+';
$Conf{ClientNameAlias} = '192.168.1.243';

and got:
Got remote protocol 1851877475
Fatal error (bad version): channel 0: open failed: connect failed: Name or
service not known
stdio forwarding failed
Can't write 1298 bytes to socket
fileListReceive() failed

if you've any ideas how to tweak that and try again i'm eager,
thank you,
greg
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Re: [BackupPC-users] double hop rsync

[backuppc]

gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
 > i'm trying to use a double hop rsync to backup a server that can only be
 > reached indirectly.  a simple test of a double hop rsync to the target
 > server seems to work:
 > 
 >   #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
 > --rsync-path=sudo\ /usr/bin/rsync 192.168.1.243:/var/log/BackupPC/.bashrc
 > /tmp
 > receiving incremental file list
 > .bashrc
 > 231 100%  225.59kB/s0:00:00 (xfr#1, to-chk=0/1)
 >   0#
 > 
 > which demonstrates that the backuppc keys, sudo settings, and double hop
 > rsync all work.
 > 
 > here's my double hop settings:
 > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 192.168.1.243 sudo
 > /usr/bin/rsync $argList+';
 > $Conf{ClientNameAlias} = '192.168.128.11';
 > 

Why don't you try using the 'jump' host option on ssh.
-J 192.168.128.11



___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

[BackupPC-users] double hop rsync

[gregrwm]

i'm trying to use a double hop rsync to backup a server that can only be
reached indirectly.  a simple test of a double hop rsync to the target
server seems to work:

  #  sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
--rsync-path=sudo\ /usr/bin/rsync 192.168.1.243:/var/log/BackupPC/.bashrc
/tmp
receiving incremental file list
.bashrc
231 100%  225.59kB/s0:00:00 (xfr#1, to-chk=0/1)
  0#

which demonstrates that the backuppc keys, sudo settings, and double hop
rsync all work.

here's my double hop settings:
$Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 192.168.1.243 sudo
/usr/bin/rsync $argList+';
$Conf{ClientNameAlias} = '192.168.128.11';

fwiw my soon-to-be-decommissioned prior backuppc server is still backing up
the target server without issue.  it's still located where it can reach the
target server directly.  it uses:
$Conf{RsyncClientCmd} = 'ssh -xq $host sudo /usr/bin/rsync $argList+';

but while the new backuppc is working fine for servers it can reach
directly, for the double hop it says:  "fileListReceive failed"

any ideas?
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/