<div dir="ltr">Hi all,<br>While observing the packet capture comparing the Microsoft DHCP server (the one which is working fine in primary and failover) Vs the ISC DHCP server I have observed the following:<br>In the Microsoft DHCP server, the IP address is bound to the client identifier and IAID, I think this is how it is trying to bond the same IP when pointed to the Microsoft DHCP cluster<br>Command Output:<br>PS C:\Users\Administrator> get-dhcpserverv4lease | select ipaddress, clientid, hostname,addressstate,leaseexpirytime<br>cmdlet Get-DhcpServerv4Lease at command pipeline position 1<br>Supply values for the following parameters:<br>ScopeId: 192.168.0.0<br><br>IPAddress : 192.168.0.152<br>clientid : 9f-6e-85-24-00-02-00-00-ab-11-43-a9-47-2d-16-23-11-5e<br>hostname : <a href="http://test.example.com">test.example.com</a><br>addressstate : Active<br>leaseexpirytime : 6/16/2022 12:13:45 PM<br><br>In the above example(9f-6e-85-24 --> is the client IAID and 43-a9-47-2d-16-23-11-5e is the client identifier and not sure what is the meaning for 00-02-00-00-ab )<br>Does any one has idea if we can use the client identifier value and IAID as the unique element instead of mac address while granting the IP address in ISC DHCP<br>Any help or suggestions is much appreciated<br><br>Thanks in Advance<br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 14, 2022 at 11:36 PM Kraishak Mahtha <<a href="mailto:kraishak.edu@gmail.com">kraishak.edu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi
<i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium">Perl-list,</i><br><div><i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium"><br></i></div><div><i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium">I have been observing some weird behavior on packet capture, I am using the same command "netplan apply" and have been executing in the loop, I am getting the DHCP release packet for some trials only, and for other trials getting the discover packet directly bypassing the release packet I guess, My observation is it is swapping the IP only when we see the release packet.</i></div><div><i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium">If anyone encounters the same behaviors and found a workaround please let me know</i></div><div><i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium"><br></i></div><div><i style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:medium">Thanks in advance</i></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 14, 2022 at 7:10 PM Kraishak Mahtha <<a href="mailto:kraishak.edu@gmail.com" target="_blank">kraishak.edu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi <span style="color:rgb(0,0,0);white-space:pre-wrap">Wayne,</span><div><br></div><div>Thanks for sharing the link,</div><div><br></div><div>I have observed that I am seeing this IP switch only if it is in a primary-failover mode whereas if we run the DHCP server standalone we do not see any issue and the IP is being constant, by any chance did you try this case</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 14, 2022 at 2:56 PM Kraishak Mahtha <<a href="mailto:kraishak.edu@gmail.com" target="_blank">kraishak.edu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">* Observed in the Ubuntu version 20.04</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 14, 2022 at 2:39 PM Kraishak Mahtha <<a href="mailto:kraishak.edu@gmail.com" target="_blank">kraishak.edu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif;font-size:13px">Hi all,<br>We are experiencing weird behavior with ISC's DHCP version 4.4.2. When the Wintel(windows) clients use the ISC DHCP servers that are operating in a primary-failover mode, then reboot or a renewal does not see any address shuffle. When the Ubuntu clients use the ISC DHCP servers, we are observing a periodic IP Address shuffle upon a reboot. This shuffling is not observed when we are using a Microsoft DHCP solution. We are interested to know if this issue is a known issue in the ISC database. If there is a workaround to resolve this issue, please let us know.</span><br><div><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif;font-size:13px"><br></span></div><div><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif;font-size:13px">Thanks in Advance </span></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>