Project

General

Profile

Actions

Feature #15321

open

Feature #15650: Kea Feature Integration for parity with ISC DHCP

Kea DHCP Custom Options Support (IPv4 and IPv6)

Added by Alhusein Zawi 9 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

adding customs options to KEA DHCP


Files

sample-kea-option-def.json (344 Bytes) sample-kea-option-def.json Dale Harron, 10/03/2024 07:41 PM

Related issues

Has duplicate Feature #13422: Add a 'type' field to the DHCPv6 server Additional BOOTP/DHCP Options Duplicate

Actions
Actions #1

Updated by Lev Prokofev 6 months ago

Below is an example of possible options with the right syntax:

https://github.com/isc-projects/kea/blob/master/doc/examples/kea4/all-options.json

Actions #2

Updated by Jim Pingle 4 months ago

  • Subject changed from KEA DHCP custom options to Kea DHCP Custom Options Support (IPv4 and IPv6)
  • Parent task set to #15650
Actions #3

Updated by Marcos M about 2 months ago

I'm providing a patch here to experiment with custom options for DHCP4; no support will be provided for this. Show

Apply it with the System Patches package, then go to Services > DHCP Server > Settings, enter the JSON-formatted custom option data, then Save/Apply.

The custom option needs to be defined once and applied per interface. Here's an example that adds a vendor option (43) to the opt1 interface (get the name from Status > Interfaces): Show

Actions #4

Updated by Dale Harron about 2 months ago

After a lot of experimentation and help from Marcos, I discovered it is important to know if the option is already defined or not. For that go to https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html#known-rfc-violations.
Look up the option and if it is already defined do not include the option-def portion because it is already defined.
"option-def": [ {
"space": "dhcp4",
"name": "custom-option-vendor",
"code": 43,
"type": "string"
}
],

If you wish to define the same option on multiple interfaces, simply cascade them with a comma, so the JSON sample now becomes (option 114 as an example): {
"option-data": {
"opt4": [ {
"name": "v4-captive-portal",
"data": “https://sub4.domain.com:8007/rfc8910.php?zone=vlan30”
}
],
"opt5": [ {
"name": "v4-captive-portal",
"data": “https://sub5.domain.com:8009/rfc8910.php?zone=vlan40”
}
]
}
}

Actions #5

Updated by Jim Pingle about 1 month ago

  • Has duplicate Feature #13422: Add a 'type' field to the DHCPv6 server Additional BOOTP/DHCP Options added
Actions

Also available in: Atom PDF