Version 12 (modified by marcin, 6 years ago) (diff)


Known DHCP Issues in Kea

The version of Kea DHCP included in BIND 1.1.0 is an engineering snapshot and intended for experimental use only (the alpha release of BIND 10 DHCP is currently anticipated in 2014). The current list of known defects in Kea can be found here.

Significant known issues with the DHCP servers in this release are:

  • The DHCP servers do not yet use the "socket creator" to bind to privileged ports. As a result, to use Kea DHCP, BIND 10 must be started by root (or via "sudo").
  • Support for directly connected DHCPv4 clients has been added, but was not tested yet (besides unit-tests).
  • Support for remote DHCPv6 clients connected via relays has been added, but was not tested yet (besides unit-tests).

We would appreciate feedback on usability and reports of any DHCP bugs. Please contribute your experiences to the Kea users mailing list:

  • BIND 10 configuration mechanism doesn't handle partial configuration of map elements. When the new value is being set for one of the elements of the map, the existing values for other elements of this map are lost. This means, that the user must always configure all elements of the map. Some maps for which this issue can be observed: Dhcp4/lease-database, Dhcp6/lease-database and maps in DhcpDdns module.
  • Memfile lease database backend doesn't yet differentiate between different lease types, e.g. IA_NA and IA_PD. When a client requests both assignment of a non temporary address and a prefix, and the IA_NA and IA_PD options sent by the client happen to have the same IAID, one of the two: address or prefix returned will be invalid.

Attachments (1)

Download all attachments as: .zip