Clearly these variables aren’t “valid IPs” because they have the whitespace in them and text such as “option routers” and “option domain-name-servers” and semicolons and so forth, and would fail the validip function, therefore never getting echo’d to the dhcpd.conf file.

I’ve since fixed the /opt/fog/.fogsettings file so that it’s correct and will work, but that doesn’t mean other people’s are fixed. We need to correct for this.

I don’t know that either of those two items are “crucial”. What about the cases where people don’t want to specify a router’s option (e.g. proxyDHCP setup – I’m pretty sure ISC-DHCP is also capable in a proxy dhcp configuration mode) or a DNS address?

The way this was handled in the past, neither of those existed to begin with if the admin who’s doing the install didn’t want them. It changed the element from:

I am fixing the updater portion to remove all of the match and replacing it with the valid IP in hopes to correct for the .fogsettings file. I’m also going to fix it in an attempt to read the IP out of the line to test it more appropriately.

there wasn’t an error, let alone even a message that there was no router address set in the DHCP config.

I feel very strongly that there should be a message for a DHCP option so critical!
ISC-DHCP gives messages about having other interfaces with other networks available that don’t have declarations. Why not a message for router addresses not being present?

It’s a trivial thing but it would have immensely helped out. I would have at least caught the problem before I left on Friday, because I always check the status of DHCPD after FOG gets done setting it up - because it’s that important.