Why is my PXE server not working naymore (Solved)

GKmst

Active Member
Aug 25, 2017
17
1
43
60
Netherlands
I am running a PXE server in a Ubuntu 18.04.6 LXC system on my Proxmox 8.3.5 server.
I am using DNSMASQ to set up a DHCP Proxy.

This is my /etc/dnsmasq.d/pxe-server config file.
Code:
port=0

interface=eth0

bind-dynamic

listen-address=192.168.168.2

dhcp-range=192.168.168.0,proxy

dhcp-boot=pxelinux.0
#dhcp-boot=undionly.kpxe

pxe-service=x86PC,"Network Boot Menu",pxelinux

enable-tftp
tftp-root=/tftpboot

It worked for many years without problems till it stopped working i think after a update or something.

I have bare metal legacy BIOS systems i need to PXE boot to run backup/restore software.
And i also use qemu vm's in Proxmox to boot.

Wen i pxe boot a qemu vm it doesn't boot but i have the ctrl=b option to enter iPXE shell and enter autoboot command after that the VM does boot and my PXE menu appears.
But my bare metal legacy bios systems do not boot at all anymore and do not have this iPXE ctrl=b option like qemu vm's have.

What has happened / changed, why did it stop working? Probably i missed something. I searched up and down last weeks and changed my dnsmasq config numerous times but there is no way to get it to work again.
 
Last edited:
Thank you @MarkusKo

I don't use any eufi systems yet, al my systems are legacy bios still.
The strange thing is it worked flawlessly for years and all of a sudden it stopped working.

I googled up and down to find similar problems but not found any.
I tried a thousand things but i can't get it to work again.

The bare metal systems don't get a IP anymore from the dhcp server in pxe mode it does work if i start windows normally.
For the qemu vm's i need to go into ipxe shell and run autoboot after that my pxe menu shows up it does not boot into the pxe menu right away only after i entered autoboot command.

I will now going to figure out of and how i can install virtio-rng in my lxc pxe system. Hopefully that'll work.
 
OMG i'm such a ...
I found the problem.
I had switched on DHCP snooping.
Once i removed the VLAN from the DHCP snooping settings my bare metal systems booted up right away. With the qemu vm's nothing changed but that is oke.
 
  • Like
Reactions: MarkusKo