I would like to play around with a PXE boot server that will be on top of a xubuntu machine. However I read any many websites that it’s essential to run a “full” DHCP server on the host because “regular” DHCP servers don’t understand PXE boot requests.
How about the IPFire DHCP server? Does it work with PXE and if so, how do I confige it to route to the PXE boot server?
Filename is for the name of the pxeimage file that you will be serving.
Have a look in the tftpd addon. It covers doing pxeboot to other machines on your network from a pxe server in IPFire. You will need to change the name of the next-server and the pxeimage filename depending on the specifics of the pxe server you are setting up on your xubuntu machine.
My point was that you could see what entries are used in the dhcp page for a pxe server running on IPFire. Then you could use that info to figure out what you need to use from your xubuntu server in their place.
My interpretation is that you need to put the IP address (not FQDN) of your xubuntu pxe server into the next-server box.
The filename needs to be the xubuntu equivalent of the pxelinux.0 filename used in tftpd for the pxe install of SuSE or the undionly.kpxe filename used for the pxe install of IPFire.
The pxe server on the xubuntu machine must have a pxe filename that defines the install that will be done. You will need to figure out how that file is defined and what filename to give it.
This link looks like it could be of use. Note that it is based on a very old version of Ubuntu but the essence of the steps used and the multiple entries in the default file to allow different OS’s to be installed should be able to be used in your setup work. https://www.howtoforge.com/ubuntu_pxe_install_server
I haven’t had time to play with PXE any further because of playing with proxmox and homematic, but now I’ve found time again and will try PXE with Ubuntu first. If that works I’ll put netboot on my vsphere.
Edit: OK I got your point: netboot.xyz is totally different. It boots a pxe environment and downloads the files for the selected OS which is to be installed.
This article is outdated. That’s what I hate most with linux. Masses of articles produced to the same topic, but most of them useless, because not valid anymore. So here with the netboot files. They point to a Ubuntu version from ~15 years ago that do not exist anymore. Also the netkit-inetd package doesn’t exist. The content/functions moved.
An outdated article has nothing to do with c&p. If I want to invent the wheel again, I don’t need to read any articles at all. Since I couldn’t find netboot installers for newer versions of ubuntu @ archive ubuntu I downloaded the latest LTS and also the directory “installer” is empty, so something totally changed, propably because of uefi.