Personally, I think this is a great idea for any interface type. I was pretty surprised when I figured out that the client-id field
was RO in iPXE, since putting the MAC there (in the ethernet case) is only an RFC suggestion, not a requirement. I did actually hack
this up myself, but since I'm C-deficient I only made the client-id be the GUID as RO instead of what I really wanted, which is to
leave it MAC by default but make it overwriteable by an iPXE script. (A build option might be satisfactory as well).
On 04/08/16 15:05, Maule Mark wrote:
Hi:
I have a project where it would be useful for me to set a custom client_id when using dhcp to configure a network interface.
Specifically, in my case I'd like to pass the SMBIOS uuid as the client_id for an infiniband port instead of the port GUID. In
my application, I can guarantee that only one port will be making dhcp requests to the server, and this would allow my node to get
the a consistent ipaddr/hostname from dnsmasq no matter which port the node pxe booted from.
I can hack the code for my own purposes, but was wondering if there might be interest in having this as a general ipxe setting.
I'm willing to do the work and push it if this seems reasonable.
thanks
Mark Maule
Sent from Yahoo Mail. Get it now <https://yho.com/146xkg>
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
