Dave Anderson

I don't use windows at all, so I don't know what debugger options exist. My strategy would be to add fmt.Println statements in https://github.com/google/netboot/blob/master/pixiecore/pixiecore.go#L185 to trace the initialization. I suspect...

bingo: https://github.com/golang/net/blob/master/ipv4/control_windows.go#L10 Looks like socket control messages are not at all implemented in x/net/ipv4, so the dhcp4 package cannot initialize on windows. If you know how to support this functionality...

The problem pixiecore has is not the same as the stackoverflow question, it's related to how DHCP works. With a normal clientserver communication, when you receive a packet, you have...

+1, this is a problem I had booting illumos as well. The whole file serving logic needs to be redesigned, so it's not a quick fix :(

I don't promise to maintain pixiecore, but as it happens I hit the same boot failure with xyz and would love to fix it :P Sounds like the recipe needs...

Yeah, I've slowly come around to this, because I'd like this feature as well. At some point, when I have some free time, I'll do a fairly large refactor of...

Nope. This project is effectively abandonware. If it's useful, great. Maybe at some point I'll hack on it some more. But don't expect significant changes any time soon.

Hmm, according to the internet, "Operation not supported" means that the iPXE doesn't have HTTP support built in... Which is weird, because I check for exactly that feature when managing...

Sorry for being slow to respond on this. It's something I definitely care about, although at a first glance, there's not much I can do to influence a client if...

@lae Looking at your pcap, I don't see Pixiecore's traffic in there. For each request your PXE client sends, I see two responses coming from 10.11.108.2 and 10.11.108.3. Both of...