I think Quazz is right. I was trying “sudo dnsmasq” to troubleshoot. Sorry - am very new to Linux. I think this issue is resolved, though PXE is not working, but I’ll ask about that in a new thread. For anyone reading about this issue, the steps in here will help set up dnsmasq, and answered my question.

stew@stew-Satellite-C600:~$ ls -la /etc/dnsmasq.d
total 24
drwxr-xr-x   2 root root  4096 May 19 10:30 .
drwxr-xr-x 144 root root 12288 May 19 09:39 ..
-rw-r--r--   1 root root  1419 May 19 10:27 ltsp.conf
-rw-r--r--   1 root root   211 Mar 27 20:22 README

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,10.0.1.9

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,10.0.1.9
dhcp-boot=net:UEFI,ipxe.efi,,10.0.1.9
dhcp-boot=net:UEFI64,ipxe.efi,,10.0.1.9

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=10.0.1.9,proxy

Thanks George. dnsmasq now active. However I still get the error “dnsmasq: failed to create listening socket for port 53: Address already in use” when I try “sudo dnsmasq”. I have already removed the line “dns=dnsmasq” from NetworkManager.conf. Is this a problem?

Thanks George. You were right about the network stack, I found that easily and enabled it. Now I have options to boot in Onboard NIC!

I updated dnsmasq to 2.76 by following this guide. The problem I have now is that I get this error message on dnsmasq restart:

“Job for dnsmasq.service failed because the control process exited with error code. See “systemctl status dnsmasq.service” and “journalctl -xe” for details.”

I looked up this error message online and in the forum, but couldn’t find a resolution. I followed the advice here, and have added/removed the dns=dnsmasq multiple times, but same error. Any ideas?

“journalctl -xe” is very long, but I can post here if needed. “systemctl status dnsmasq.service” returns:

~/dnsmasq-2.76$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
           └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
   Active: failed (Result: exit-code) since Wed 2017-05-17 16:27:52 EDT; 15min ago
  Process: 15049 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=1/FAILURE)
  Process: 15047 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)

May 17 16:27:51 stew-Satellite-C600 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
May 17 16:27:51 stew-Satellite-C600 dnsmasq[15047]: dnsmasq: syntax check OK.
May 17 16:27:52 stew-Satellite-C600 dnsmasq[15049]: dnsmasq: bad option at line 1 of /etc/dnsmasq.d/issue.pcap
May 17 16:27:52 stew-Satellite-C600 systemd[1]: dnsmasq.service: Control process exited, code=exited status=1
May 17 16:27:52 stew-Satellite-C600 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 17 16:27:52 stew-Satellite-C600 systemd[1]: dnsmasq.service: Unit entered failed state.
May 17 16:27:52 stew-Satellite-C600 systemd[1]: dnsmasq.service: Failed with result 'exit-code'.

Server

• FOG Version: 1.4.0
• OS: Ubuntu 16.04 LTS

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

Linux novice here, trying to implement Fog at our institution. I believe there may be multiple issues going on, and will try to list them systematically.

The problem is that Fog appears to be set up correctly, but when I try to capture an image, the host PC doesn’t have an option to network boot, and I don’t see any indication of Fog during startup.

• Fog is installed successfully on Ubuntu, not as a DHCP server. We are running SonicWall Firewall, so I followed this guide for setting up Fog without a DHCP server, since I couldn’t find the equivalent 066/067 configs in SonicWall. The steps seemed to work fine.
• I’m attempting to capture an image of a Dell Latitude 3560. I have installed the default Fog client on this Windows 10 machine. The wired network adapter is a Realtek PCIe GBE Family Controller. I understand that this may not work with “undionly.kpxe”, and may need to be switched to “ipxe.pxe”, but I don’t know for sure if that’s the problem.
• The Dell doesn’t have an option in boot for “network adapter” or equivalent, and I confirmed that PXE is enabled in “integrated NIC” in BIOS.

Let me know if you need any more info/logs/etc. Appreciate any help.