No ProxyDHCP response, retrying...

[bbinet]

I'm running pixiecore in a docker container and when I start a new device from pxe, it first seems to boot correctly, as it is able to enter iPXE 1.0.0+, but then it is stuck in the "Configuring" step, with the "No configuration methods succeeded" "No ProxyDHCP response, retrying (attempt X/10)" error messages.

Here is the log from pixiecore:

sudo docker run --rm --net=host -v $(pwd):/pxe bbinet/pixiecore boot -d /pxe/linux /pxe/initrd.gz --cmdline 'auto=true url={{ ID "/pxe/debian_preseed.cfg" }}'
[Init] Starting Pixiecore goroutines
[DHCP] Got valid request to boot 00:22:15:45:dd:e3 (IA32)
[DHCP] Offering to boot 00:22:15:45:dd:e3
[DHCP] Ignoring packet from 00:22:15:45:dd:e3: packet is DHCPREQUEST, not DHCPDISCOVER
[TFTP] Sent "00:22:15:45:dd:e3/0" to 192.168.0.13:2070
[TFTP] clamping blocksize to "192.168.0.13:2071": 1456 -> 1450
[TFTP] Sent "00:22:15:45:dd:e3/0" to 192.168.0.13:2071
[DHCP] Got valid request to boot 00:22:15:45:dd:e3 (IA32)
[DHCP] Offering to boot 00:22:15:45:dd:e3
[DHCP] Got valid request to boot 00:22:15:45:dd:e3 (IA32)
[DHCP] Offering to boot 00:22:15:45:dd:e3
[DHCP] Got valid request to boot 00:22:15:45:dd:e3 (IA32)
[DHCP] Offering to boot 00:22:15:45:dd:e3
[DHCP] Got valid request to boot 00:22:15:45:dd:e3 (IA32)
[...]

Any idea what I'm doing wrong?

[bbinet]

Note that I have tested with another device, and it is actually working.
So it may be an issue with the network card of my first device. Is there anything special to configure in the BIOS or elsewhere for the network card to properly boot from the pixiecore pxe server?

[danderson]

Hmm, strange. It looks like the first stage worked, and chainloaded to ipxe... And then for some reason it no longer sees the ProxyDHCP responses for the next stage. What is the machine you're trying to boot (manufacturer, model, model of the network card if it's a separate addon, BIOS/EFI version) ?

The next step would be to take a packet capture and see if there's anything wrong with the network traffic. Can you repeat the boot attempt, and at the same time run sudo pixiecore debug tcpdump <your LAN interface name> dump.pcap, and share it with me? You will need to have tcpdump installed on the machine. You can either attach it here, or if you want more privacy, share it to me directly (email/dropbox/whatever) at [email protected] . For best results, please run it outside the docker container, so we can identify if this is a problem with Docker's virtual networking.

The debug command will capture all DHCP/TFTP/PXE traffic that your machine sees.

FWIW, my current theories on what's wrong:

• Another PXE-enabled DHCP server exists on the network, which is confusing iPXE. tcpdump should tell us if that's happening.
• The ProxyDHCP response for 2nd stage loading (via iPXE) is malformed and iPXE ignores it. Need to see the packet capture to A/B compare.
• Pixiecore's iPXE build is somehow not compatible with your hardware, and it's failing to receive the responses correctly. I don't know of an obvious way to debug that, but with more info about your machine I can try to find bug reports or iPXE patches.

[bbinet]

Here is the informations regarding my network cards: my ASUSTek P5Q DELUXE mother board have 2 onboard network interfaces (Note that I had tested to pxe boot from both network cards, and the result was the same).

$ sudo lshw -class network > lshw_network.txt

lshw_network.txt

$ sudo dmidecode > dmidecode.txt

dmidecode.txt

I'll send you soon the pcap file by email soon.

[bbinet]

@danderson Have you received the pcap file, and does it help in investigating the issue here?

[krzysztofantczak]

I'm experiencing the same issue, but i'm trying to boot hyper-v VM. Pixiecore is hosted on another VM (the same hypervisor). Is it possible to make it work?

[Qubasa]

Same issue