<div dir="ltr"><div dir="ltr"><div>Let me clarify this issue</div><div><br></div><div>Firstly, when I'm on the 3rd floor.</div><div>My windows Laptop can get the ip address with the relay agent ip: 10.122.23.1</div><div><b>#more kea-leases4.csv</b></div><div>10.122.23.11,0c:d2:92:a5:41:91,01:0c:d2:92:a5:41:91,3600,1537763173,12223,0,0,DESKTOP-24SJKAU.,0</div><div><br></div><div>Then, I move to 1st floor. It cannot obtain new ip address with the relay agent: 10.122.7.1</div><div><br></div><div><b>+ Observed behavior in kea log.</b></div><div> </div><div>2018-09-24 09:42:04.938 DEBUG [kea-dhcp4.bad-packets/8257] DHCP4_NO_LEASE_INIT_REBOOT [hwtype=1 0c:d2:92:a5:41:91], cid=[01:0c:d2:92:a5:41:91], tid=0x89222cbf: no lease for address 10.122.23.11 requested by INIT-REBOOT client</div><div><br></div><div>2018-09-24 09:42:50.435 DEBUG [kea-dhcp4.bad-packets/8257] DHCP4_NO_LEASE_INIT_REBOOT [hwtype=1 0c:d2:92:a5:41:91], cid=[01:0c:d2:92:a5:41:91], tid=0x6a8468f1: no lease for address 10.122.23.11 requested by INIT-REBOOT client</div><div><br></div><div><br></div><div>"DHCP Request" packets are received from kea with the following information:</div><div>_client ip address (ciaddr): 0.0.0.0</div><div>_requested IP address (opt50): 10.122.23.11</div><div>_relay agent IP address (giaddr): 10.122.7.1</div><div>_No server identifier </div><div><br></div><div>As you know. RFC2131: DHCPREQUEST generated during INIT-REBOOT state</div><div>If requested IP address is different with relay agent IP address in this case. the server SHOULD send a DHCPNAK. </div><div><br></div><div>captured file from kea server.</div><div><a href="https://drive.google.com/file/d/1bE1P_KE3hFE9LvqqneocKSWc-7JDIfq-/">https://drive.google.com/file/d/1bE1P_KE3hFE9LvqqneocKSWc-7JDIfq-/</a></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 9, 2018 at 6:10 PM Marcin Siodelski <<a href="mailto:marcin@isc.org">marcin@isc.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The difficulty with this particular situation is that the capture<br>
doesn't really help determining what happened before the NAK and no<br>
response to Windows client.<br>
<br>
The INIT-REBOOT client is the one that remembers its previously assigned<br>
address. If the server doesn't know this lease it can't respond to the<br>
client because it is possible that it was assigned by a different<br>
server. But, this situation should get resolved on its own, because the<br>
client that didn't get a response should eventually try DORA (4-way<br>
exhange) and get the lease.<br>
<br>
It seems that the iOS client gets the NAK because the lease he is asking<br>
for is not a valid lease for this client because the client has a lease<br>
for a different address.<br>
<br>
So, I presume that the server has a lease for iOS client for some other<br>
address than he is asking and has no lease for the Windows client so it<br>
ignores his request, which all seem to be a valid behavior. But to be<br>
sure we'd need to know what is in the lease database and also how the<br>
clients ended up in the INIT-REBOOT state.<br>
<br>
Marcin Siodelski<br>
ISC Engineering<br>
<br>
<br>
<br>
On 04.07.2018 13:08, Hieu Nguyen wrote:<br>
> Please help me<br>
> <br>
> 2018-07-01 16:08 GMT+07:00 Hieu Nguyen <<a href="mailto:hieu.ntrong@gmail.com" target="_blank">hieu.ntrong@gmail.com</a><br>
> <mailto:<a href="mailto:hieu.ntrong@gmail.com" target="_blank">hieu.ntrong@gmail.com</a>>>:<br>
> <br>
> 2 client (Windows and iOS) in "INIT-REBOOT" state sends a DHCP<br>
> Request to KEA through a relay.<br>
> Requested address (option 50) is its old address. This subnet isn't<br>
> configured in KEA server.<br>
> <br>
> Kea don't know of this client.<br>
> <br>
> *+ Observed behavior:*<br>
> iOS:<br>
> 2018-07-01 15:26:34.892 DEBUG [kea-dhcp4.bad-packets/1553]<br>
> DHCP4_PACKET_NAK_0002 [hwtype=1 6c:4d:73:f3:d4:19],<br>
> cid=[01:6c:4d:73:f3:d4:19], tid=0xb858b700: invalid address<br>
> 10.122.23.24 requested by INIT-REBOOT<br>
> <br>
> Windows:<br>
> 2018-07-01 15:28:00.290 DEBUG [kea-dhcp4.bad-packets/1553]<br>
> DHCP4_NO_LEASE_INIT_REBOOT [hwtype=1 f0:42:1c:e5:f3:5d],<br>
> cid=[01:f0:42:1c:e5:f3:5d], tid=0x954bf4ee: no lease for address<br>
> 10.122.13.204 requested by INIT-REBOOT client<br>
> <br>
> Window client must use the command " ipconfig /release and ipconfig<br>
> /renew " to obtain new ip address.<br>
> <br>
> *+ Expected behavior:*<br>
> Kea returns a NAK to Windows like iOS. <br>
> <br>
> After that I set up other DHCP Server from Microsoft. It properly<br>
> returns DHCP NAK to 2 clients.<br>
> <br>
> I also attached the capture from kea server. help me this case,plz<br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Kea-users mailing list<br>
> <a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
> <br>
<br>
</blockquote></div>