New install of Ubuntu 14.04.2 and Fog 1.20 on a Dell Optiplex 745 (192.168.1.20) using dnsmasq.
Finally got the host (192.168.1.128) to load the undionly.0 link as described in the dnsmasq instructions. But then it times out when loading default.ipxe.
As you can see below, Wireshark shows that the TFTP host successfully downloads undionly.kpxe from 192.168.1.20, but then it tries to TFTP to 192.168.1.1 (the default gateway).
Why is it doing that?
That’s right, it’s a consumer-grade router–Asus RT-N66U. That is why I am using dnsmasq, because I lack the ability to configure its DHCP correctly.
Here is my ltsp.conf file:
# Don't function as a DNS server:
port=0
# Log lots of extra information about DHCP transactions.
log-dhcp
# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp
# Set the root directory for files available via FTP.
tftp-root=/tftpboot
# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,192.168.1.20
# rootpath option, for NFS
#dhcp-option=17,/images
# kill multicast
#dhcp-option=vendor:PXEClient,6,2b
# 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
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3
# 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 from network", undionly
# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
#pxe-service=X86PC, "Boot from local hard disk", 0
# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1
# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses. Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.1.20,proxy
# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h
# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite
@cml Thanks, I will try it out!
EDIT: TOTALLY WORKED!
OK, so for my own education, can you explain where that “next-server” setting is? What would I have to change in order for the default undionly.kpxe to work correctly?
@cml 's file works great, but I shouldn’t have to request a unique binary every time I reconfigure the network.
@Wayne-Workman said:
Just to make it clear, Secure Boot is currently required to be OFF to network boot with FOG. Can you provide us with a screen shot of the error ? You might need to take a video to capture the error, often times the errors are only displayed for fractions of a second. What happens if you try to boot using ipxe.efi ??
At first, I didn’t know what you were talking about–the only efi file in my /tftpboot folder was snponly.efi. But then I read another suggestion from you elsewhere that maybe upgrading to trunk might help, so I tried that.
And, lo, my /tftpboot doth overflow with efi files! So I tried ipxe.efi, and it WORKS.
Also - see my old post below on the subject of using a USB dongle.
That looks like really useful info once I get this host registered. Amazing.
As you requested elsewhere, I will experiment with co-existing EFI and BIOS hosts using DD-WRT and see if I can’t contribute to the Wiki to pay it forward.