Bug 1312621

Summary: dhcpd instructions are unclear for PXE boot
Product: [Fedora] Fedora Documentation Reporter: Dan Mossor [danofsatx] <danofsatx>
Component: install-guideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:21:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Mossor [danofsatx] 2016-02-28 02:31:17 UTC
Section 10.2 of the Installation Guide gives the example setup for dhcpd to enable a PXE boot / network installation. The example is unclear between paragraphs 2 and 4 in that the text in paragraph 4 does not match up with the text in paragraph 2, and there are no clear instructions as to where it goes in the example file. 

After trial and error and comparing with the F20 instructions, I was able to get dhcpd started again. I suggest modifying paragraph 4 to include the whole file as such:

option arch code 93 = unsigned integer 16;
subnet 192.168.1.0 netmask 255.255.255.0 {
        option domain-name-servers 192.168.1.1;
        option routers 192.168.1.1;
        range 192.168.1.11 192.168.1.50;
        authoritative;
        default-lease-time 600;
        max-lease-time 7200;
        ddns-update-style none;
        if option arch = 00:07 {
                filename "uefi/shim.efi";
                } else {
                filename "pxelinux.0";
                }
        next-server 192.168.1.2;
}

Comment 2 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.