Build a CentOS7 server for: pxe boot, kickstart, reposync, repotrack, nfs, https (STEP 13)

STEP 13 – Provide PXE boot server info to DHCP clients, via VMware Fusion vnet config (not a CentOS DHCP server).

This config is on the VMware host.  In my case, that’s a MacOS Mojave MacBook Pro running VMware Fusion. Any recent VMware hypervisors (Fusion, Workstation ESXi) are capable of providing this. VirtualBox and Parallels can to.  This scope of this guide is staying with VMware Fusion on MacOS.

Fusion doesn’t provide a GUI interface for the DHCP PXE Boot Server option. But it does support a lot of additional features through config files and/or the command line.
For this step, open a MacOS Terminal window, and:
sudo su
nano /Library/Preferences/VMware\ Fusion/vmnet2/dhcpd.conf
Put this after the “DO NOT MODIFY” section of stuff… it’s “reimplementing the subnet”…
note: on the PXE Boot Server, the “pxelinux.0″ file can be put in a subfolder, and then referenced in the DHCP config with this syntax ”  filename “pxelinux/pxelinux.0”;
My PXE server is providing the pxelinux.0 file at the default root of the tftpserver.
           the vnet dhcp config is a little less than obvious…
           the PXE Boot TFTP Server is represented by:  “next-server 10.0.0.11”

subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.128 10.0.0.254;
option broadcast-address 10.0.0.255;
option domain-name-servers 10.0.0.2;
option domain-name localdomain;
default-lease-time 1800;                # default is 30 minutes
max-lease-time 7200;                    # default is 2 hours
option netbios-name-servers 10.0.0.2;
option routers 10.0.0.2;
next-server 10.0.0.11;  
  filename “pxelinux.0”;
}
host vmnet2 {
hardware ethernet 00:55:55:C0:22:22;
fixed-address 10.0.0.1;
option domain-name-servers 0.0.0.0;
option domain-name “”;
option routers 0.0.0.0;
}

* for simplicity, this VMNET config uses an entire class c range (private/non-routable of course), and then allocates the bottom half for static IP and lets the DHCP process serve the top half.


TO RESTART FUSION DHCP SERVICE: without shutting down/restarting VMs/Fusion
(2019-02-22):
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –stop   
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start