[Kea-users] issue with INIT-REBOOT

[Hieu Nguyen]

Let me clarify this issue

Firstly, when I'm on the 3rd floor.
My windows Laptop can get the ip address with the relay agent ip:
10.122.23.1
*#more kea-leases4.csv*
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

Then, I move to 1st floor. It cannot obtain new ip address with the relay
agent: 10.122.7.1

*+ Observed behavior in kea log.*

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

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


"DHCP Request" packets are received from kea with the following information:
_client ip address (ciaddr): 0.0.0.0
_requested IP address (opt50): 10.122.23.11
_relay agent IP address (giaddr): 10.122.7.1
_No server identifier

As you know. RFC2131:  DHCPREQUEST generated during INIT-REBOOT state
If  requested IP address is different with relay agent IP address in this
case. the server SHOULD send a DHCPNAK.

captured file from kea server.
https://drive.google.com/file/d/1bE1P_KE3hFE9LvqqneocKSWc-7JDIfq-/


On Mon, Jul 9, 2018 at 6:10 PM Marcin Siodelski <marcin at isc.org> wrote:

> The difficulty with this particular situation is that the capture
> doesn't really help determining what happened before the NAK and no
> response to Windows client.
>
> The INIT-REBOOT client is the one that remembers its previously assigned
> address. If the server doesn't know this lease it can't respond to the
> client because it is possible that it was assigned by a different
> server. But, this situation should get resolved on its own, because the
> client that didn't get a response should eventually try DORA (4-way
> exhange) and get the lease.
>
> It seems that the iOS client gets the NAK because the lease he is asking
> for is not a valid lease for this client because the client has a lease
> for a different address.
>
> So, I presume that the server has a lease for iOS client for some other
> address than he is asking and has no lease for the Windows client so it
> ignores his request, which all seem to be a valid behavior. But to be
> sure we'd need to know what is in the lease database and also how the
> clients ended up in the INIT-REBOOT state.
>
> Marcin Siodelski
> ISC Engineering
>
>
>
> On 04.07.2018 13:08, Hieu Nguyen wrote:
> > Please help me
> >
> > 2018-07-01 16:08 GMT+07:00 Hieu Nguyen <hieu.ntrong at gmail.com
> > <mailto:hieu.ntrong at gmail.com>>:
> >
> >     2 client (Windows and iOS) in "INIT-REBOOT" state sends a DHCP
> >     Request to KEA through a relay.
> >     Requested address (option 50) is its old address. This subnet isn't
> >     configured in KEA server.
> >
> >     Kea don't know of this client.
> >
> >     *+ Observed behavior:*
> >      iOS:
> >     2018-07-01 15:26:34.892 DEBUG [kea-dhcp4.bad-packets/1553]
> >     DHCP4_PACKET_NAK_0002 [hwtype=1 6c:4d:73:f3:d4:19],
> >     cid=[01:6c:4d:73:f3:d4:19], tid=0xb858b700: invalid address
> >     10.122.23.24 requested by INIT-REBOOT
> >
> >     Windows:
> >     2018-07-01 15:28:00.290 DEBUG [kea-dhcp4.bad-packets/1553]
> >     DHCP4_NO_LEASE_INIT_REBOOT [hwtype=1 f0:42:1c:e5:f3:5d],
> >     cid=[01:f0:42:1c:e5:f3:5d], tid=0x954bf4ee: no lease for address
> >     10.122.13.204 requested by INIT-REBOOT client
> >
> >     Window  client must use the command " ipconfig /release and ipconfig
> >     /renew " to obtain new ip address.
> >
> >     *+ Expected behavior:*
> >     Kea returns a NAK to Windows like iOS.
> >
> >     After that I set up other DHCP Server from Microsoft. It properly
> >     returns DHCP NAK to 2 clients.
> >
> >     I also attached the capture from kea server. help me this case,plz
> >
> >
> >
> >
> > _______________________________________________
> > Kea-users mailing list
> > Kea-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/kea-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20180924/b4a22be2/attachment.htm>