7156 Uefi pxe DHCP error

[dureal99d]

@george1421 this what I get when I try to restart the service

sudo service dnsmasq restart
Failed to restart dnsmasq.service: Unit dnsmasq.service not found.

yet when I run this command ““dnsmasq -v”” I get this

Dnsmasq version 2.76  Copyright (c) 2000-2016 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.

[george1421]

@dureal99d Did you remember to install your distribution’s dnsmasq package first? If so the service name may not be called dnsmasq since it appears that Ubuntu 16 looks like its systemd based. A quick check is to just reboot the computer. Once its back up then key in ps aux|grep dnsmasq to see if the dnsmasq service is running in memory. I need to figure out what the proper systemd restart command is.

[Edit] According to this github page: https://gist.github.com/magnetikonline/6236150

# for Ubuntu 16.04LTS
$ sudo systemctl restart NetworkManager

# for Ubuntu 14.04LTS
$ sudo restart network-manager

[dureal99d]

@george1421 I did not install dnsmasq. I will redo all the steps from scratch. I will install my distros dnsmasq first, then I will do the steps and get back to you.

[george1421]

@dureal99d OK just install your distro’s dnsmasq version then just pop back to the directory where you built dnsmasq and just key in sudo make install and it should see that the binary has already been created and just copy over the compiled version. But did the compile right since it was installed and reported the right version when the command was run.

[dureal99d]

@george1421 ok I’m waiting on my machine to boot.

[dureal99d]

@george1421

make[1]: Entering directory '/home/dureal99d/dnsmasq-2.76/src'
make[1]: 'dnsmasq' is up to date.
make[1]: Leaving directory '/home/dureal99d/dnsmasq-2.76/src'
install -d /usr/sbin -d /usr/share/man/man8
install -m 644 man/dnsmasq.8 /usr/share/man/man8 
install -m 755 src/dnsmasq /usr/sbin

[george1421]

@dureal99d Yes, that is expected. It says the binary you complied is up to date and just recopied the files to their destination location. So dnsmasq -v should show that 2.76 is installed (hope).

[dureal99d]

@george1421

the result of running command ps aux|grep dnsmasq

nobody    1467  0.0  0.0  47864  3728 ?        S    07:51   0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
dureal9+  5503  0.0  0.0  14224   972 pts/5    S+   08:00   0:00 grep --color=auto dnsmasq

[dureal99d]

@george1421 yes the command shows

Dnsmasq version 2.76  Copyright (c) 2000-2016 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.```

[dureal99d]

@george1421 to edit this file what do I type

[george1421]

@dureal99d OK then issue the network manager restart that is below. Then (at least on my Pi) inspect the /var/log/syslog file way at the bottom. You should see the startup of the dnsmasq service. Confirm the version number there is showing 2.76. If that is the case then you have successfully updated your dnsmasq to 2.76.

[george1421]

@dureal99d said in 7156 Uefi pxe DHCP error:

@george1421 to edit this file what do I type

?? File you need to edit ??

[dureal99d]

@george1421 I just thought I would have to edit this, dnsmasq file.

[george1421]

@dureal99d Ah ok to add uefi support? I am working on another tutorial that covers that. https://forums.fogproject.org/topic/8726/advanced-dnsmasq-techniques

I think the bits you need are on the third post. Below is that config file. The 192.168.112.24 is MY FOG/dnsmaq server. This is the simple way to add uefi support. I’m working on a more complex way that opens up new options. But if you want to get uefi/bios working this should get you going.

# 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

# 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

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

# 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, ARM_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.

# PXEClient:Arch:00000
pxe-service=X86PC, "Boot BIOS PXE", undionly.kpxe

# PXEClient:Arch:00007
pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe.efi

# PXEClient:Arch:00009
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", ipxe.efi

dhcp-range=192.168.112.24,proxy

[dureal99d]

@george1421 cool. and I see a whole bunch of data popped into the syslog once I ran that network command sudo systemctl restart NetworkManager.

[dureal99d]

@george1421 I still need the command to edit ltsb.conf file

[dureal99d]

@george1421 ok, let me try this another way. is this ltsb file one I should crate myself? and if so where do I place it after I’m done?

[george1421]

@dureal99d Yes it is a file you create. Typically we call this ltsp.conf and it goes in /etc/dnsmasq.d directory. You will need to use your favorite text editor. I use vi (because I’m old). You need to be sure to launch your text editor either as administrator if doing via the gui or as sudo if launching it by command line. If you use vi then the command would be sudo vi /etc/dnsmasq.d/ltsp.conf If you have never used vi before, don’t! All of the text editor commands are cryptic and will drive you nuts to learn.

[dureal99d]

@george1421 said in 7156 Uefi pxe DHCP error:

LOL, no vi for me then. good ol gedit it is.

[dureal99d]

@george1421 said in 7156 Uefi pxe DHCP error:

@dureal99d Ah ok to add uefi support? I am working on another tutorial that covers that. https://forums.fogproject.org/topic/8726/advanced-dnsmasq-techniques

I think the bits you need are on the third post. Below is that config file. The 192.168.112.24 is MY FOG/dnsmaq server. This is the simple way to add uefi support. I’m working on a more complex way that opens up new options. But if you want to get uefi/bios working this should get you going.

# 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

# 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

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

# 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, ARM_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.

# PXEClient:Arch:00000
pxe-service=X86PC, "Boot BIOS PXE", undionly.kpxe

# PXEClient:Arch:00007
pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe.efi

# PXEClient:Arch:00009
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", ipxe.efi

dhcp-range=192.168.112.24,proxy

so how do you get this file to interact with the router?