From: Razvan Becheriu Date: Thu, 10 Jun 2021 09:38:23 +0000 (+0300) Subject: [#1917] fixed indentation X-Git-Tag: Kea-1.9.9~100 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7a48f301c33785c1484256cf1fc66f2e9922fdff;p=thirdparty%2Fkea.git [#1917] fixed indentation --- diff --git a/src/bin/keactrl/kea-dhcp4.conf.pre b/src/bin/keactrl/kea-dhcp4.conf.pre index fc4a8067c3..95a00798de 100644 --- a/src/bin/keactrl/kea-dhcp4.conf.pre +++ b/src/bin/keactrl/kea-dhcp4.conf.pre @@ -246,35 +246,35 @@ // additional forensic logging capabilities, ability to reserve hosts in // more flexible ways, and even add extra commands. For a list of available // hook libraries, see https://gitlab.isc.org/isc-projects/kea/wikis/Hooks-available. - //"hooks-libraries": [ - // { - // // Forensic Logging library generates forensic type of audit trail - // // of all devices serviced by Kea, including their identifiers - // // (like MAC address), their location in the network, times - // // when they were active etc. - // "library": "@libdir@/kea/hooks/libdhcp_legal_log.so", - // "parameters": { - // "path": "/var/lib/kea", - // "base-name": "kea-forensic4" - // } - // }, - // { - // // Flexible identifier (flex-id). Kea software provides a way to - // // handle host reservations that include addresses, prefixes, - // // options, client classes and other features. The reservation can - // // be based on hardware address, DUID, circuit-id or client-id in - // // DHCPv4 and using hardware address or DUID in DHCPv6. However, - // // there are sometimes scenario where the reservation is more - // // complex, e.g. uses other options that mentioned above, uses part - // // of specific options or perhaps even a combination of several - // // options and fields to uniquely identify a client. Those scenarios - // // are addressed by the Flexible Identifiers hook application. - // "library": "@libdir@/kea/hooks/libdhcp_flex_id.so", - // "parameters": { - // "identifier-expression": "substring(relay4[2].hex)" - // } - // } - //], + // "hooks-libraries": [ + // { + // // Forensic Logging library generates forensic type of audit trail + // // of all devices serviced by Kea, including their identifiers + // // (like MAC address), their location in the network, times + // // when they were active etc. + // "library": "@libdir@/kea/hooks/libdhcp_legal_log.so", + // "parameters": { + // "path": "/var/lib/kea", + // "base-name": "kea-forensic4" + // } + // }, + // { + // // Flexible identifier (flex-id). Kea software provides a way to + // // handle host reservations that include addresses, prefixes, + // // options, client classes and other features. The reservation can + // // be based on hardware address, DUID, circuit-id or client-id in + // // DHCPv4 and using hardware address or DUID in DHCPv6. However, + // // there are sometimes scenario where the reservation is more + // // complex, e.g. uses other options that mentioned above, uses part + // // of specific options or perhaps even a combination of several + // // options and fields to uniquely identify a client. Those scenarios + // // are addressed by the Flexible Identifiers hook application. + // "library": "@libdir@/kea/hooks/libdhcp_flex_id.so", + // "parameters": { + // "identifier-expression": "substring(relay4[2].hex)" + // } + // } + // ], // Below an example of a simple IPv4 subnet declaration. Uncomment to enable // it. This is a list, denoted with [ ], of structures, each denoted with diff --git a/src/bin/keactrl/kea-dhcp6.conf.pre b/src/bin/keactrl/kea-dhcp6.conf.pre index e036b50159..529fa7b8e1 100644 --- a/src/bin/keactrl/kea-dhcp6.conf.pre +++ b/src/bin/keactrl/kea-dhcp6.conf.pre @@ -192,35 +192,35 @@ // additional forensic logging capabilities, ability to reserve hosts in // more flexible ways, and even add extra commands. For a list of available // hook libraries, see https://gitlab.isc.org/isc-projects/kea/wikis/Hooks-available. - //"hooks-libraries": [ - // { - // // Forensic Logging library generates forensic type of audit trail - // // of all devices serviced by Kea, including their identifiers - // // (like MAC address), their location in the network, times - // // when they were active etc. - // "library": "@libdir@/kea/hooks/libdhcp_legal_log.so", - // "parameters": { - // "path": "/var/lib/kea", - // "base-name": "kea-forensic6" - // } - // }, - // { - // // Flexible identifier (flex-id). Kea software provides a way to - // // handle host reservations that include addresses, prefixes, - // // options, client classes and other features. The reservation can - // // be based on hardware address, DUID, circuit-id or client-id in - // // DHCPv4 and using hardware address or DUID in DHCPv6. However, - // // there are sometimes scenario where the reservation is more - // // complex, e.g. uses other options that mentioned above, uses part - // // of specific options or perhaps even a combination of several - // // options and fields to uniquely identify a client. Those scenarios - // // are addressed by the Flexible Identifiers hook application. - // "library": "@libdir@/kea/hooks/libdhcp_flex_id.so", - // "parameters": { - // "identifier-expression": "relay6[0].option[37].hex)" - // } - // } - //], + // "hooks-libraries": [ + // { + // // Forensic Logging library generates forensic type of audit trail + // // of all devices serviced by Kea, including their identifiers + // // (like MAC address), their location in the network, times + // // when they were active etc. + // "library": "@libdir@/kea/hooks/libdhcp_legal_log.so", + // "parameters": { + // "path": "/var/lib/kea", + // "base-name": "kea-forensic6" + // } + // }, + // { + // // Flexible identifier (flex-id). Kea software provides a way to + // // handle host reservations that include addresses, prefixes, + // // options, client classes and other features. The reservation can + // // be based on hardware address, DUID, circuit-id or client-id in + // // DHCPv4 and using hardware address or DUID in DHCPv6. However, + // // there are sometimes scenario where the reservation is more + // // complex, e.g. uses other options that mentioned above, uses part + // // of specific options or perhaps even a combination of several + // // options and fields to uniquely identify a client. Those scenarios + // // are addressed by the Flexible Identifiers hook application. + // "library": "@libdir@/kea/hooks/libdhcp_flex_id.so", + // "parameters": { + // "identifier-expression": "relay6[0].option[37].hex)" + // } + // } + // ], // Below an example of a simple IPv6 subnet declaration. Uncomment to enable // it. This is a list, denoted with [ ], of structures, each denoted with