Description of problem: If a user attempts to run anaconda to install RHEL 5 on a client, it can sometimes take Anaconda over a half hour to get a dynamic IP address through its ethernet interface from a DHCP server. Version-Release number of selected component (if applicable): RHEL 5 Gold How reproducible: Always (at least when I try it) Steps to Reproduce: 1. Start a RHEL 5 installation via CD or a kickstart on a machine 2. Wait until anaconda attempts to get a dynamic IP 3. Continue waiting Actual results: Anaconda finds an IP, but it takes over a half hour for it to do such. Expected results: Anaconda finds an IP within 5 minutes or so. Additional info: The test plan was run on a VMware box, and the RHEL 5 Gold installation was initiated through an RHN Satellite-based kickstart.
Adding 'noipv6' to your kernel command line will make things faster if you don't have IPv6 set up on your network
Need more details about your network. Half an hour seems a bit long. I would believe 10 minutes, which is the RFC required timeout. There seems to be something unique about your network setup. You also had the bug report about noipv6 causing a SIGSEGV. Either you have an old release of RHEL-5 or your network contains things that we are not accounting for correctly. Make sure you are using RHEL-5 GOLD.
*** This bug has been marked as a duplicate of 231645 ***