[Kea-users] NEXT_STEP SKIP and DROP documentation discrepancies

[Igor Smitran]

Hi list,

If i've interpreted documentation correctly then setting th 
NEXT_STEP_DROP in any of the hooks would immediately drop packet and 
stop any further processing of that packet?

     enum CalloutNextStep {
         NEXT_STEP_CONTINUE = 0, ///< continue normally
         NEXT_STEP_SKIP = 1,     ///< skip the next processing step
         NEXT_STEP_DROP = 2      ///< drop the packet
     };

I was planning to drop the packet if there is no option 82 in it. Hook 
position was pkt4_receive:

handle.setStatus(CalloutHandle::NEXT_STEP_DROP);

Kea decided to skip and continue. Computer received an offer.

Then, after few more tests i decided to change to SKIP:

and kea droped the packet immediately:

DHCP4_HOOK_PACKET_RCVD_SKIP [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[no info], 
tid=0xd7a09a5b: packet is dropped, because a callout set the skip flag.

Computer didn't receive an offer.

Is this a bug or i didn't understand the concept?