Changes between Version 20 and Version 21 of Hooks


Ignore:
Timestamp:
Jun 11, 2018, 9:49:39 AM (16 months ago)
Author:
tomek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Hooks

    v20 v21  
    4242|| 11. || radius || EULA || ISC || http://isc.org/kea || Integration with RADIUS for access control and accounting are supported. Kea is able to send Access-Request messages and alter its behavior depending on the responses. Specific IP addresses may be assigned (if Framed-IP-Address or Framed-IPv6-Address is received), client can be assigned to specific pool (if Framed-Pool or Framed-IPv6-Pool is received) or denied service altogether (if Access-Reject is received). Kea can also send accounting messages to RADIUS accounting servers. As with other features, this supports both IPv4 and IPv6. [[https://kea.isc.org/docs/kea-guide.html#hooks-radius | Documentation]]
    4343|| 12. || host_cache || EULA || ISC || http://isc.org/kea || Some of the optional backends may be slow to respond. The host caching library creates a local cache on the Kea server of host reservations on the backend to improve performance. [[https://kea.isc.org/docs/kea-guide.html#hooks-host-cache | Documentation]]
    44 || 13. || high_availability || EULA || ISC || http://isc.org/kea || Two Kea instances can now be configured to run as a pair to provide higher availability. Two modes are supported. In hot standby mode there is a primary instance handling all traffic and sending updates to its secondary partner. The secondary monitors the health of the primary and is able to take over automatically in case the primary fails. In load balancing mode both partners are active and are handling approximately half of the traffic traffic. In case of a failure of either server, the partner is able to take over responding to all traffic directed to both servers. Support for additional backup servers is implemented. The solution supports both IPv4 and IPv6 and can work with any backend, including memfile. Note that this is NOT an implementation of the IETF standard DHCPv4 failover (which does not support DHCPv6).[[https://kea.isc.org/docs/kea-guide.html#hooks-high-availability | Documentation]]
     44|| 13. || high_availability || MPL 2.0 || ISC || http://isc.org/kea || Two Kea instances can now be configured to run as a pair to provide higher availability. Two modes are supported. In hot standby mode there is a primary instance handling all traffic and sending updates to its secondary partner. The secondary monitors the health of the primary and is able to take over automatically in case the primary fails. In load balancing mode both partners are active and are handling approximately half of the traffic traffic. In case of a failure of either server, the partner is able to take over responding to all traffic directed to both servers. Support for additional backup servers is implemented. The solution supports both IPv4 and IPv6 and can work with any backend, including memfile. Note that this is NOT an implementation of the IETF standard DHCPv4 failover (which does not support DHCPv6).[[https://kea.isc.org/docs/kea-guide.html#hooks-high-availability | Documentation]]
    4545
    4646