Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco)
2006-Mar-06 22:49 UTC
Malformed Address and Private IP issue
Hello all, I've run out of of ideas as to why its not working. Below is my configuration for hosts allow. Even when I have 'hosts allow' off, it still doesn't work. Rsync host =========rsync version 2.5.7 protocol version 26 /etc/rsyncd.conf hosts allow = 10.17.44.84 10.17.44.85 localhost.localdomain dev-01.foo.com e-lnx.foo.com Server has 2 IP eth0 = Inet IP eth1 = Private IP Rsync log ========2006/03/06 14:28:28 [28327] malformed address localhost.localdomain 2006/03/06 14:28:28 [28327] malformed address dev-01.foo.com 2006/03/06 14:28:28 [28327] rsync denied on module testdir from stage-02.bar.com (10.17.44.85) Client host -- stage-02.bar.com ==============Error msg: @ERROR: access denied to testdir from stage-02.bar.com (10.17.44.85) rsync: connection unexpectedly closed (92 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) If I connect from other Inet IP, rsync works like a charm. Just that somehow it doesn't work with private IP or I misconfigured somehow. Anyone what the case of my problem is?
On Mon, Mar 06, 2006 at 02:47:48PM -0800, Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco) wrote:> 2006/03/06 14:28:28 [28327] malformed address localhost.localdomain > 2006/03/06 14:28:28 [28327] malformed address dev-01.foo.com > 2006/03/06 14:28:28 [28327] rsync denied on module testdir from stage-02.bar.com (10.17.44.85)I'd suggest upgrading to at least 2.6.6: the error messages that a daemon logs for login failures has improved, which should reveal exactly why the connection is failing to authorize. Also, some bugs have been fixed that should hopefully get rid of the "malformed address" warnings. ..wayne..
Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco)
2006-Mar-07 00:04 UTC
Malformed Address and Private IP issue
I've tried to use all IP for hosts allow and that does not work either. It is so strange. The Malformed address error only happens with private ip and not the INET ip. ==Update ==After further investigation, I've found eth1(private ip) uses the same gateway as eth0(INET ip). The gateway ip is an INET ip which might explain why I am getting malformed address???> -----Original Message----- > From: Wayne Davison [mailto:wayned@samba.org] > Sent: Monday, March 06, 2006 3:22 PM > To: Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco) > Cc: rsync@lists.samba.org > Subject: Re: Malformed Address and Private IP issue > > On Mon, Mar 06, 2006 at 02:47:48PM -0800, Jonathan Chen -X > (jonachen - The Armada Group, Inc. at Cisco) wrote: > > 2006/03/06 14:28:28 [28327] malformed address localhost.localdomain > > 2006/03/06 14:28:28 [28327] malformed address dev-01.foo.com > > 2006/03/06 14:28:28 [28327] rsync denied on module testdir from > > stage-02.bar.com (10.17.44.85) > > I'd suggest upgrading to at least 2.6.6: the error messages > that a daemon logs for login failures has improved, which > should reveal exactly why the connection is failing to > authorize. Also, some bugs have been fixed that should > hopefully get rid of the "malformed address" warnings. > > ..wayne.. >
Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco)
2006-Mar-08 18:55 UTC
Malformed Address and Private IP issue
Yeah heard of it to upgrade. Not sure if possible for me to ask for upgrade on the system I'm working on.> -----Original Message----- > From: John Van Essen [mailto:vanes002@umn.edu] > Sent: Tuesday, March 07, 2006 10:48 PM > To: rsync@lists.samba.org > Subject: RE: Malformed Address and Private IP issue > > On Mon, 6 Mar 2006, Jonathan Chen <jonachen@cisco.com> wrote: > > After further investigation, I've found eth1(private ip) > uses the same > > gateway as eth0(INET ip). The gateway ip is an INET ip which might > > explain why I am getting malformed address??? > > In the OLDNEWS file: > > NEWS for rsync 2.6.0 (1 Jan 2004) > > * Fixed bogus "malformed address {hostname}" message in rsyncd log > when checking IP address against hostnames from "hosts allow" > and "hosts deny" parameters in config file. > > That explains the problem. It's a bug that was fixed in 2.6.0. > > John > > >
Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco)
2006-Mar-08 21:00 UTC
Malformed Address and Private IP issue
How important is it to type "make install" when I don't wish for the compiled program install into its default location. I only want it to be in in the compiled directory and read rsyncd.conf file. So when I ran 2.6.6 under "sudo ./rsync --daemon --config=/etc/rsyncd.conf" under RHEL 3, I basically get the same error message. I got rid of "hosts allow =" line and I still get "malformed address" in the rsync.log file. Then a deny of connection from X private address. sudo ./rsync -e ssh --archive --sparse --compress --update --progress --stats -vv --dry-run jonachen@dev1::testdir . opening connection using --server --sender -vvunlogDtprSz . testdir @ERROR: access denied to testdir from stage02.foo.com (10.10.10.11) rsync error: error starting client-server protocol (code 5) at main.c(1171)> -----Original Message----- > From: Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco) > Sent: Monday, March 06, 2006 4:03 PM > To: 'Wayne Davison' > Cc: rsync@lists.samba.org > Subject: RE: Malformed Address and Private IP issue > > I've tried to use all IP for hosts allow and that does not > work either. It is so strange. The Malformed address error > only happens with private ip and not the INET ip. > > ==> Update > ==> After further investigation, I've found eth1(private ip) uses > the same gateway as eth0(INET ip). The gateway ip is an INET > ip which might explain why I am getting malformed address??? > > > -----Original Message----- > > From: Wayne Davison [mailto:wayned@samba.org] > > Sent: Monday, March 06, 2006 3:22 PM > > To: Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco) > > Cc: rsync@lists.samba.org > > Subject: Re: Malformed Address and Private IP issue > > > > On Mon, Mar 06, 2006 at 02:47:48PM -0800, Jonathan Chen -X > (jonachen - > > The Armada Group, Inc. at Cisco) wrote: > > > 2006/03/06 14:28:28 [28327] malformed address > localhost.localdomain > > > 2006/03/06 14:28:28 [28327] malformed address dev-01.foo.com > > > 2006/03/06 14:28:28 [28327] rsync denied on module testdir from > > > stage-02.bar.com (10.17.44.85) > > > > I'd suggest upgrading to at least 2.6.6: the error messages that a > > daemon logs for login failures has improved, which should reveal > > exactly why the connection is failing to authorize. Also, > some bugs > > have been fixed that should hopefully get rid of the "malformed > > address" warnings. > > > > ..wayne.. > >
Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco)
2006-Mar-08 21:50 UTC
Malformed Address and Private IP issue
> -----Original Message----- > From: Wayne Davison [mailto:wayned@samba.org] > Sent: Wednesday, March 08, 2006 12:28 PM > To: Jonathan Chen -X (jonachen - The Armada Group, Inc. at Cisco) > Cc: rsync@lists.samba.org > Subject: Re: Malformed Address and Private IP issue > > On Wed, Mar 08, 2006 at 10:44:18AM -0800, Jonathan Chen wrote: > > Not sure if possible for me to ask for upgrade on the system I'm > > working on. > > Keep in mind that you don't need to install an upgraded rsync > to be able to use it, since you can run it from any dir. Of > course, if we're talking about upgrading the daemon version, > you'd need appropriate privileges to be able to halt the old > daemon and start a new one, and that might not be permissible for you. >Cool. Did that and it did not work. After I compiled the new version of rsync, I killed the old rsync -daemon and ran the new version. Then I used the new version to get 'testdir' module and still get the access denied error message while the rsync.log complains about... 2006/03/08 11:25:12 [16976] malformed address localhost.localdomain 2006/03/08 11:25:12 [16976] malformed address dev01.foo.com (rsync server name) 2006/03/08 11:25:12 [16976] rsync denied on module testdir from stage02.foo.com (10.10.10.11) "hosts allow" is turned off globably. So I "should" not get a denied message in the rsync.log.> Other suggestions: > > Try adding the hostname for the system you're trying to connect from. > Make sure that the module you're trying to access is using > the "hosts allow" settings you think it is (these settings > can be specified on a per-module basis or globally, and you > didn't supply enough of the rsyncd.conf file for me to check). > > ..wayne.. >