Project

General

Profile

Actions
Copy link

Bug #15983

open

Unicode Escaped Characters in Client ID for Kea Cause No Start Condition

Added by Kris Phillips 4 months ago. Updated 4 months ago.

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

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.11
Affected Architecture:

Description

If a dash is present in the Client ID field for a DHCP Reservation, this will cause Kea to fail with the following error:

unsupported unicode escape in "'[Client ID here]'"

There are no logged events under Status --> System Logs --> DHCP. You must run Kea manually and feed it the config file to get this output.

This only happens with a \u2011 unicode hyphen. Using a \u2013 hyphen has no issue.

Actions
Copy link
 #1

Updated by Christopher Cope 4 months ago

  • Subject changed from Dashes in Client ID for Kea Causes No Start Condition to Unicode Escaped Characters in Client ID for Kea Cause No Start Condition
  • Status changed from New to Confirmed

I can confirm and reproduce this issue. As a note the hostname already has entry verification, but it seems the client ID doesn't.

Also of note, placing ‑ (\u2011) directly into the configuration, without the escaped notation, and running kea directly works. This happens with any unicode escaped characters and isn't specific the the non-breaking hyphen that was present in this case. It seems the issue lies in kea not being able to process unicode escaped characters.

Actions
Copy link

Also available in: Atom PDF