On 12/04/16 15:04, Maule Mark wrote:
I noticed that. However, dnsmasq only considers client_id (if present) followed by hwaddr when looking up configs in its hostsfile. I've tried hacking around that in dnsmasq (by trying to match client_uuid if present and no client_id match), but the code is pretty tangled and it's not clear to me that this would be spec compliant anyway.
It looks as though our use of the link-layer address as the DHCP client identifier (option 61) may be obsolete anyway, since IPoIB devices now use 6-byte eIPoIB LEMACs in ll_addr (rather than the 20-byte IPoIB MAC).
Wissam: any objections to switching all link layers (including eIPoIB) to place the client UUID in option 61?
Michael _______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
