Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix kea-dhcp4.conf.pre #144

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions src/bin/keactrl/kea-dhcp4.conf.pre
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
// Depending on how Kea was compiled, it may also support SQL databases
// (MySQL and/or PostgreSQL). Those database backends require more
// parameters, like name, host and possibly user and password.
// There are dedicated examples for each backend. See Section 7.2.2 "Lease
// There are dedicated examples for each backend. See Section 8.2.2 "Lease
// Storage" for details.
"lease-database": {
// Memfile is the simplest and easiest backend to use. It's an in-memory
Expand All @@ -77,7 +77,7 @@
// "host": "localhost",
// "port": 3306
// },
// See Section 7.2.3 "Hosts storage" for details.
// See Section 8.2.3 "Hosts storage" for details.

// Setup reclamation of the expired leases and leases affinity.
// Expired leases will be reclaimed every 10 seconds. Every 25
Expand Down Expand Up @@ -127,9 +127,9 @@
// are actually useful in your network.
//
// For a complete list of options currently supported by Kea, see
// Section 7.2.8 "Standard DHCPv4 Options". Kea also supports
// vendor options (see Section 7.2.10) and allows users to define their
// own custom options (see Section 7.2.9).
// Section 8.2.10 "Standard DHCPv4 Options". Kea also supports
// vendor options (see Section 8.2.13) and allows users to define their
// own custom options (see Section 8.2.11).
"option-data": [
// When specifying options, you typically need to specify
// one of (name or code) and data. The full option specification
Expand Down Expand Up @@ -226,9 +226,9 @@
// This is a test. It is an expression that is being evaluated on
// each incoming packet. It is supposed to evaluate to either
// true or false. If it's true, the packet is added to specified
// class. See Section 12 for a list of available expressions. There
// are several dozens. Section 8.2.14 for more details for DHCPv4
// classification and Section 9.2.19 for DHCPv6.
// class. See Section 15 for a list of available expressions. There
// are several dozens. Section 8.2.18 for more details for DHCPv4
// classification and Section 9.2.23 for DHCPv6.
"test": "substring(option[60].hex,0,6) == 'Aastra'",

// If a client belongs to this class, you can define extra behavior.
Expand Down