<html><head></head><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1460469419551_11809" dir="ltr"><span id="yui_3_16_0_ym19_1_1460469419551_11855">But wouldn't that cause issues in the general case? If all of the IB ports will then carry the same client_id, then you can only use dhcp to assign an ipaddr to one of them (in the general case).</span></div><div id="yui_3_16_0_ym19_1_1460469419551_11809" dir="ltr"><span><br></span></div><div id="yui_3_16_0_ym19_1_1460469419551_11809" dir="ltr"><span id="yui_3_16_0_ym19_1_1460469419551_11917">In my application, I can guarantee that only one port on a host will be issuing dhcp discover requests, although the port which does the dhcp discovery for the host may change from boot to boot.</span></div><div id="yui_3_16_0_ym19_1_1460469419551_11810"><br></div><div id="yui_3_16_0_ym19_1_1460469419551_11810">Mark</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1460469419551_11811"><br></div><div class="yahoo_quoted" style="display: block;" id="yui_3_16_0_ym19_1_1460469419551_11956"> <blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;" id="yui_3_16_0_ym19_1_1460469419551_11955"> <div style="font-family: times new roman, new york, times, serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1460469419551_11954"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1460469419551_11953"> <div dir="ltr" id="yui_3_16_0_ym19_1_1460469419551_11952"> <font size="2" face="Arial" id="yui_3_16_0_ym19_1_1460469419551_11957"> <hr size="1" id="yui_3_16_0_ym19_1_1460469419551_11968"> <b><span style="font-weight:bold;">From:</span></b> Michael Brown <mcb30@ipxe.org><br> <b><span style="font-weight: bold;">To:</span></b> Maule Mark <mark_maule@yahoo.com>; "ipxe-devel@lists.ipxe.org" <ipxe-devel@lists.ipxe.org>; Wissam Shoukair <wissams@mellanox.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, April 12, 2016 9:21 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [ipxe-devel] custom dhcp client_id option<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1460469419551_11959"><br>On 12/04/16 15:04, Maule Mark wrote:<br clear="none">> I noticed that. However, dnsmasq only considers client_id (if present)<br clear="none">> followed by hwaddr when looking up configs in its hostsfile. I've tried<br clear="none">> hacking around that in dnsmasq (by trying to match client_uuid if<br clear="none">> present and no client_id match), but the code is pretty tangled and it's<br clear="none">> not clear to me that this would be spec compliant anyway.<br clear="none"><br clear="none">It looks as though our use of the link-layer address as the DHCP client <br clear="none">identifier (option 61) may be obsolete anyway, since IPoIB devices now <br clear="none">use 6-byte eIPoIB LEMACs in ll_addr (rather than the 20-byte IPoIB MAC).<br clear="none"><br clear="none">Wissam: any objections to switching all link layers (including eIPoIB) <br clear="none">to place the client UUID in option 61?<div class="yqt1700392792" id="yqtfd58441"><br clear="none"><br clear="none">Michael<br clear="none"></div><br><br></div> </div> </div> </blockquote> </div><div><br></div><div><br></div><div>Sent from Yahoo Mail. <a href="https://yho.com/146xkg">Get it now</a></div><div class="yahoo_quoted"> <blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: times new roman, new york, times, serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Michael Brown <mcb30@ipxe.org><br> <b><span style="font-weight: bold;">To:</span></b> Maule Mark <mark_maule@yahoo.com>; "ipxe-devel@lists.ipxe.org" <ipxe-devel@lists.ipxe.org>; Wissam Shoukair <wissams@mellanox.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, April 12, 2016 9:21 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [ipxe-devel] custom dhcp client_id option<br> </font> </div> <div class="y_msg_container"><br>On 12/04/16 15:04, Maule Mark wrote:<br clear="none">> I noticed that. However, dnsmasq only considers client_id (if present)<br clear="none">> followed by hwaddr when looking up configs in its hostsfile. I've tried<br clear="none">> hacking around that in dnsmasq (by trying to match client_uuid if<br clear="none">> present and no client_id match), but the code is pretty tangled and it's<br clear="none">> not clear to me that this would be spec compliant anyway.<br clear="none"><br clear="none">It looks as though our use of the link-layer address as the DHCP client <br clear="none">identifier (option 61) may be obsolete anyway, since IPoIB devices now <br clear="none">use 6-byte eIPoIB LEMACs in ll_addr (rather than the 20-byte IPoIB MAC).<br clear="none"><br clear="none">Wissam: any objections to switching all link layers (including eIPoIB) <br clear="none">to place the client UUID in option 61?<div class="yqt1700392792" id="yqtfd58441"><br clear="none"><br clear="none">Michael<br clear="none"></div><br><br></div> </div> </div> </blockquote> </div></div></body></html>