GitLab

name: Client-Classes break KEA Config-Set API Call?
about: Config-Set API call

Describe the bug We've created a client-class for IP-phones in the KEA configuration. Now that we've started automating with the API we discovered an issue with the config-set API call, which reports a bad request.

The configuration is live, and KEA accepts it. However, even when we get the config through the API, and try to set it without changing it, it reports a "bad request".

To Reproduce (Part of the) Config that works:

"shared-networks": [ ],
"client-classes": [
		{
				"name": "Innovaphone"
		}
],
"subnet4": [

(Part of the) Config that doesn't work:

"shared-networks": [ ],
"client-classes": [
		{
				"name": "Innovaphone",
				"test": "option[60].hex == '1.3.6.1.4.1.6666'",
				"option-def": [
						{
								"name": "vendor-encapsulated-options",
								"code": 43,
								"type": "empty",
								"encapsulate": "Innovaphone"
						}
				],
				"option-data": [
						{
								"name": "h323-gatekeeper",
								"code": 200,
								"space": "Innovaphone",
								"data": "10.90.249.1"
						},
						{
								"name": "default-coder",
								"code": 203,
								"space": "Innovaphone",
								"data": "G711A\\,20\\,k4/G711a\\,20\\,k4"
						},
						{
								"name": "language",
								"code": 204,
								"space": "Innovaphone",
								"data": "dut"
						},
						{
								"name": "dialtone-type",
								"code": 210,
								"space": "Innovaphone",
								"data": "0x2C"
						},
						{
								"name": "update-URL",
								"code": 215,
								"space": "Innovaphone",
								"data": "http://10.90.249.1/DRIVE/CF0/update/"
						},
						{
								"name": "vendor-encapsulated-options",
								"code": 43
						}
				]
		}
],
"subnet4": [

Expected behavior Being able to set the exact same config through the API that would work on the CLI.

Environment:

• Kea version: which release? KEA 1.4
• OS:Ubuntu 16.04 x64

Contacting you gitlab / email