Hi, I try to connect to a host that has IPv4 and IPv6, but IPv6 is currently blocked by ACL's. My host also has IPv6 and IPv4. When I pass the -4 or --ipv4 option to rsync, it doesn't pass it to ssh: $ rsync -4 -r -v -v -v -v -l --del . SOMEUSER@SOMEHOST:SOMEPATH cmd= machine=SOMEHOST user=SOMEUSER path=SOMEPATH cmd[0]=ssh cmd[1]=-l cmd[2]=SOMEUSER cmd[3]=SOMEHOST cmd[4]=rsync cmd[5]=--server cmd[6]=-vvvvlr cmd[7]=--delete-during cmd[8]=. cmd[9]=SOMEPATH opening connection using ssh -l SOMEUSER SOMEHOST rsync --server -vvvvlr --delete-during . SOMEPATH <nothing happens> I tried version 2.6.9 (ubuntu) and 3.0.2 (fedora 9), both have the same result. Is it me or is this unwanted behaviour? When I ssh to the machine using -4, I can log in. -- Gijs Molenaar gijs.molenaar@surfnet.nl http://gijs.pythonic.nl fingerprint C660 BABA 4B91 4B5C EB60 7739 4385 8ABA 72EE 99CA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.samba.org/archive/rsync/attachments/20080530/24734425/signature.bin
On Fri, 2008-05-30 at 12:20 +0200, Gijs Molenaar wrote:> I try to connect to a host that has IPv4 and IPv6, but IPv6 is currently > blocked by ACL's. My host also has IPv6 and IPv4. When I pass the -4 or > --ipv4 option to rsync, it doesn't pass it to ssh: [...]Currently, options like -4 only affect network connections made by rsync itself (i.e., directly to a daemon), so you should pass the option to ssh by either passing -e "ssh -4" to rsync or specifying it for the appropriate host in your ~/.ssh/config . Matt -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/rsync/attachments/20080530/a08a3aab/attachment.bin