Bug 18179
Summary: | kickstart not seeing next server (again) - using different DHCPD | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | tek |
Component: | anaconda | Assignee: | Erik Troan <ewt> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dr, mangrich |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-10-03 19:41:10 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
tek
2000-10-03 05:02:33 UTC
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. -Thom 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. |