One problem I have as many iPXE implementations start appearing in vendor firmware is that I can't tell at DHCP transaction time whether the requester has CONFIG_*BLAH* set. For example, I usually have a conditional to say something like 'if not iPXE, chainload iPXE, else http boot', and then a vendor nic has iPXE, but not HTTP enabled. My workaround is basically to have my own build and burn it on adapters as needed with a different vendor id to match on. Any ideas on how iPXE might be able to announce what features it has (kinda like how the banner advertises on-screen, but in DISCOVER in a way that can be examined by dhcpd). I'm thinking a bitfield with each CONFIG option mapped to a bit position.
At that point, I'd just need to see if I can 'and' values against a mask before compare in dhcpd conditionals. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20101115/c2005251/attachment.html>
