Red Hat Bugzilla – Bug 18179
kickstart not seeing next server (again) - using different DHCPD
Last modified: 2008-05-01 11:37:59 EDT
Basically same problem as I saw in Red Hat 6.1. I set my 'next server' to
be a certain IP address, the DHCP server tells the client to use that
address, but kickstart will still just see 0.0.0.0 as the next server.
This is with 7.0.
Well, I was able to get around this. We are currently using the CMU DHCP/BOOTP
server with Princeton patches (http://wwwnet.princeton.edu/software/dhcpd/).
We had to specify the 'nr' option to the server which basically says "give the
client all the info I have whether or not it asked for it specifically". So
I'm guessing the install is assuming that the server will just give out all its
information without even asking for it.
I just tested this w/ Red Hat 7.0, and it works fine here. If you're using the
ISC dhcpd server use the next-server directive.