From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116
Description of problem:
Installation hangs and NIS does not work when I do this:
- start a fresh install of Fedora 2:
- during pre-install, enable the firewall (by default, no holes)
- during first-boot, select "use network logins", the NIS setup window
opens. enable NIS, set the domain name, press "okey"
- the NIS setup window hangs, the first-boot installation hangs.
(it is possible to recover by hard-killing the NIS setup window)
- enabling the firewall prevents responses from the NIS server from
- during first-boot, the NIS setup window attempts to start "ypbind",
presumably by running "service ypbind start". This hangs forever
because responses from the NIS server are blocked by the firewall.
1) the ypbind startup script should punch a hole in the firewall (as
the ntpd startup script does)
2) the graphical NIS setup window should show the progress of whatever
time consuming things it does, and it should give the user the option
to abort whatever it is doing if things to wrong.
Version-Release number of selected component (if applicable):
There is a general issue with holes in firewalls that needs
addressing. Probably lokkit needs to keep a database of apps and holes
and apps need to add/remove holes neatly - and with user consent - as
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
The problem is still there in FC3. K.O.
This occurs in the Fedora Core 4 release as well. Someone with permission ought
to bump the Version on this bug to fc4.
I'll see if I can replicate this and get a fix so it doesn't happen in FC5.
I am unable to replicate this problem in fc4. Please detail how you see this
Still waiting any further information from reporter. I'm unable to replicate
the problem with my systems.
Upon further research it appears that a firewall rule exists in the default
fedora installation to allow all related connections which allows ypbind udp
traffic to pass back and forth.
If you continue to have problems please re-open this bug.