iPXE
Intro
iPXE is open-source boot firmware. It's the "software" binary that is loaded by your network card after DHCP tells it where to look for it and what the name of the files is. I know, you want to just get on with it, but it's vital to know, at least in basics, what the steps are in net boot, so you can debug it when something does not work.
Here is a fancy high-level diagram of how the process is going. I have excluded SAMBA service for now, we will have another graphs for Linux and Windows separately.
Getting iPXE
I don't want to freak you out right now, but we need to compile it from source. "Panic noises...". Do not worry, it will be simple.
Install packages
Install the following packages on your PXE server.
apt install -y make gcc binutils perl mtools mkisofs syslinux liblzma-dev isolinuxClone the iPXE git
Duplicate the latest iPXE repository
cd
git clone git://git.ipxe.org/ipxe.git
cd ~/ipxe/srcEmbedding file into iPXE
This is an important part, that pestered me for a day. When the iPXE loads, it kind of expect a specially formatted DNS reply which tells it what "menu" to load. Under "menu" we can imagine a simple file that tells iPXE what OS to offer you, where are the booting files for that OS and so on. Since I'm using UniFi there is no option to easily tell the build in DHCP server to serve that information which iPXE expect by default.
To go around this, and make life simpler for us, we are going to embed the first "menu" file directly into the binary. All it will tell iPXE is to look locally for another file, that will be our actual menu. We can edit it at will later on, without the need of recompiling the ROM again.
Create file: embed.ipxe
cd ~/ipxe/src
nano embed.ipxeAdd this into it, including the #!ipxe at start !
#!ipxe
dhcp && goto netboot || goto dhcperror
:dhcperror
prompt --key s --timeout 10000 DHCP failed, hit 's' for the iPXE shell; reboot in 10 seconds && shell || reboot
:netboot
chain tftp://${next-server}/main.ipxe ||
prompt --key s --timeout 10000 Chainloading failed, hit 's' for the iPXE shell; reboot in 10 seconds && shell || rebootWhat this does, is to tell iPXE to use DHCP to get IP and then go to option netboot to load main.ipxe file from your TFTP server. The variable ${next-server} is automagically replaced by the IP of server iPXE booted for, so no need to hardcore IP in.
Source of embed.ipxe: Cesetxeberria GitHub
Enable NTFS and PING support
This is optional, but can help in the future. We will enable NTFS support for iPXE, so it can work with NTFS instead of HTTP if needed.
cd ~/ipxe/src
# NTFS support
sed -i 's/#undef\tDOWNLOAD_PROTO_NFS/#define\tDOWNLOAD_PROTO_NFS/' config/general.h
# Ping support
sed -i 's/\/\/#define\ PING_CMD/#define\ PING_CMD/' config/general.h
sed -i 's/\/\/#define\ IPSTAT_CMD/#define\ IPSTAT_CMD/' config/general.h
sed -i 's/\/\/#define\ REBOOT_CMD/#define\ REBOOT_CMD/' config/general.h
sed -i 's/\/\/#define\ POWEROFF/#define\ POWEROFF/' config/general.Source for these changes: Rikka0w0 GitHub
Build the iPXE
Time to compile !
cd ~/ipxe/src
make bin-x86_64-efi/ipxe.efi EMBED=embend.ipxeThis should compile the source code into our ROM file.
Copy ipxe.efi to place
Our main TFTP folder is /pxe-boot remember ? That's the place where the NW card will look for the ipxe.efi. Let's put it there.
cp ~/ipxe/src/bin-x86_64-efi/ipxe.efi /pxe-boot/ipxe.efiCreate your first menu
As you remember, we embedded a file to iPXE that tells it to load main.ipxe so let's create one. Just a basic one, so we can test if everything work.
Create file /pxe-boot/main.ipxe and add this:
#!ipxe
:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item hello Hello world
item shell ipxe shell
choose --default return --timeout 5000 target && goto ${target}
:hello
echo "hello world"
boot ||
goto MENU
:shell
shell ||
goto MENU
autobootDon't worry about the content of the file now, we will change it when we will be adding entries for Windows and Linux. I will explain them then.
Test!
We are at another test stage, you should be now able to do network boot to basic blue menu that look like this:
In your BIOS make sure you set Network Boot, or PXE boot as first booting option and make sure you select UEFI option for it. Do not use secure boot, I think that does not work.
If everything works, let's move on the next step, either Windows or Linux installs.
This was not that hard was it ? Now take a breather, walk for 5 min, get some coffee. Or help me to get some coffee 🙂