Rsync 2.5.1 on Solaris 8 reverse lookup failures

[Craig Donnelly]

Dave,

I applied your patch for socket.c and recompiled the binary. The logs on the
server now show the following:

2002/01/24 11:30:41 [3132] rsync denied on module etc from unknown
(::ffff:192.168.5.20)
2002/01/24 11:32:12 [3139] reverse+forward lookup for ::ffff:192.168.5.20
(anbk1.andelconsulting.com) mismatched - spoofed address?

And the client returns the  following:

@ERROR: access denied to etc from unknown (::ffff:192.168.5.20)
rsync: connection unexpectedly closed (141 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(139)

I assume this has something to do with IPv4/V6 matching although doing a
"--version" on my rsync mention complied without IPv6.

Regards,

Craig Donnelly
Andel Consulting
10 Fenchurch Avenue
London EC3M 5BN
Tel: 0207 6655055
Fax: 0207 6655060



-----Original Message-----
From: Dave Dykstra [mailto:dwd at bell-labs.com]
Sent: Wednesday, January 23, 2002 4:30 PM
To: Craig Donnelly
Subject: Re: Rsync 2.5.1 on Solaris 8 reverse lookup failures


Ah yes, I think that is caused by the same problem.  Try my patch at
    http://lists.samba.org/pipermail/rsync/2002-January/005791.html

- Dave Dykstra

On Wed, Jan 23, 2002 at 03:33:52PM -0000, Craig Donnelly wrote:
> Dave,
> 
> Thanks for the prompt reply.
> 
> The server side rsyncd.conf file on host cogen1.andelconsulting.com is as
> follows:
> -------------------------------------------------------
> uid = nobody
> gid = nobody
> use chroot = no
> max connections = 4
> syslog facility = local5
> log file = /var/log/rsync.log
> pid file = /var/lock/rsyncd.pid
> motd file = /etc/rsyncd.txt
> 
> [etc]
>         path = /etc
>         comment = config directory
>         auth users = root
>         read only = yes
>         secrets file = /etc/rsyncd.sec
>         strict modes = no
>        hosts allow = 192.168.5.20
>         transfer logging = yes
> ------------------------------------------------------------
> rsync is running as a daemon from inetd and it all works beautifully if I
> comment out the "hosts allow" option.
> 
> If I run the following command I get the motd and available modules
> returned.
> rsync root at cogen1::
> 
> However as soon as I specify a module i.e
> rsync root at cogen1::etc - I get the following errors on the client:
> 
> @ERROR: access denied to etc from unknown (::ffff:192.168.5.20)
> rsync: connection unexpectedly closed (141 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(139)
> 
> and the following is logged on the server side:
> 
> 2002/01/23 15:32:15 [28875] rsync: reverse name lookup mismatch on fd0 -
> spoofed address?
> 2002/01/23 15:32:15 [28875] rsync denied on module etc from unknown
> (::ffff:192.168.5.20)
> 
> Hope this sheds sufficient light?
> 
> 
> Regards
> 
> Craig Donnelly
> Andel Consulting
> 10 Fenchurch Avenue
> London EC3M 5BN
> Tel: 0207 6655055
> Fax: 0207 6655060
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Dave Dykstra [mailto:dwd at bell-labs.com]
> Sent: Wednesday, January 23, 2002 3:20 PM
> To: Craig Donnelly
> Cc: 'rsync at lists.samba.org'
> Subject: Re: Rsync 2.5.1 on Solaris 8 reverse lookup failures
> 
> 
> On Wed, Jan 23, 2002 at 12:36:02PM -0000, Craig Donnelly wrote:
> > I get the following log messages using rsync 2.5.1 compiled on Solaris 8
> > when using the "hosts allow" option in rsyncd.conf:
> > 
> > 2002/01/23 12:09:51 [28276] rsync: reverse name lookup mismatch on fd0 -
> > spoofed address?
> > 2002/01/23 12:10:18 [28276] rsync: connection unexpectedly closed (16
> bytes
> > read so far)
> > 
> > Resolv.conf/DNS are configured and working properly with both A and PTR
> > records available.
> > The problem does not occur on a Solaris 7 machine.
> 
> The first message is a known problem in rsync 2.5.1, but it is usually a
> harmless warning so it is probably not related to the second message which
> can occur from a lot of different causes.  Note also that 27 seconds
> elapses between the two messages.  You'd have to give more details about
> your rsyncd.conf file and your command string in order for us to give you
> any advice about the second message.
> 
> - Dave Dykstra