Bug 619043

Summary:	ypbind fails to bind to domain with "broadcast"
Product:	Red Hat Enterprise Linux 6	Reporter:	Rik van Riel <riel>
Component:	ypbind	Assignee:	Karel Klíč <kklic>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	rvokal
Target Milestone:	rc	Keywords:	RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-28 14:59:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rik van Riel 2010-07-28 12:45:07 UTC

Description of problem:

# cat /etc/yp.conf 
# /etc/yp.conf - ypbind configuration file
# Valid entries are
...
domain surriel.com broadcast

The above yp.conf works fine for RHEL5 and Fedora 12, on the same network with the same NIS server.  However, RHEL6 ypbind fails to bind to the domain.

# service ypbind start
Starting NIS service:                                      [  OK  ]
Binding NIS service: ......................                [FAILED]
Shutting down NIS service:                                 [  OK  ]

Version-Release number of selected component (if applicable):

ypbind-1.20.4-29.el6.x86_64

How reproducible:

Have "broadcast" as the server.  Try to start ypbind and watch it fail.

Comment 2 RHEL Program Management 2010-07-28 13:17:45 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Karel Klíč 2010-07-28 13:58:10 UTC

Hello,

it works well here, so I need more information about what is happening on your computer.

Please try to run ypbind manually in the debug mode:

$ sudo service ypbind stop
$ sudo ypbind -d

and attach its output to this bug. Make sure that both SELinux and firewall are turned off (something like 'setenforce 0; service iptables stop') during this test.

If you have access to the yp server, please run the ypserv manually in the debug mode and consider attaching its output to this bug:

$ sudo service ypserv stop
$ sudo ypserv -d

Thank you.

Comment 4 RHEL Program Management 2010-07-28 14:17:42 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 5 Rik van Riel 2010-07-28 14:59:02 UTC

Looks like iptables is indeed the problem.  Without broadcast things work fine with iptables.  With iptables on, broadcast never gets an answer from the server. With iptables off, broadcast NIS works.

For some reason, the INPUT rules did not show up in "iptables -L" after the kvm iptables rules were added?

Anyway, this is not a ypbind bug.