Kea is an open source DHCPv4/DHCPv6 server being developed by Internet Systems Consortium. Kea is a high-performance, extensible DHCP server engine that is designed to be easily modified and extended with hooks libraries.
DHCP Standardization efforts: ISC participates and actively contributes to evolving Internet standards for the sake of stability and interoperability. The Director of DHCP Engineering at ISC is currently co-chair of the Dynamic Host Configuration working group in the IETF. We are committed to providing a standards-compliant implementation and are closely tracking developments in this working group and evaluating them for inclusion in Kea.
Separate DHCPv4, DHCPv6 and Dynamic DNS servers (run only the applications you are using)
Leases and host reservations can be stored in a local file (default) or optionally in a MySQL, Postgres or Cassandra database
IPv6 prefix delegation
Most popular options supported, including PXE boot
Applications API, with multiple application extensions available from ISC
On-line configuration. It is possible to update the configuration file and tell the servers to reload configuration without restarting the system.
Ample, documented statistics
REST api for remote management
High performance, with up to ~5000 leases per second (default), ~500 leases per second (with optional database backend)
Supported on Linux, BSD and Mac OS X operating systems
Recent Kea News
2018-06-15: Kea 1.4.0 released!
A release of Kea 1.4.0 has been made available. It brings many new features and improves existing ones: high availability, database improvements (better statistics and error handling), expanded client classification (you can now define class restrictions on pool level and use additional operators), much improved Cassandra backend (now with host reservation), RADIUS support and more. For detailed information please check Release Notes.
[Known Issues List - known issues for current release.] (known issues list)
Contact us via the Kea mailing list if you think you might be interested in working on Kea and sharing that work with the community. We are a small team, so please be patient - it may take us a while to code-review unexpected contributions.
The primary things we need are:
Test coverage in different environments, with a variety of clients. We LOVE to hear when things are working well, too!
Applications based on the Kea API, both to validate the API and to demonstrate the potential for DHCP applications.
Detailed, specific requirements for new functionality