[Kea-users] problem in custom option
Tomek Mrugalski
tomasz at isc.org
Thu Mar 30 16:21:30 UTC 2017
On 30/03/17 10:42, Francis Dupont wrote:
> Known and fixed defect:
>
> 1213. [bug] fdupont
> Option string values containing comma can now be specified
> correctly by preceding comma with double backslashes (e.g.
> "foo\\,bar").
> (Trac #5105, git fa79ac2396aa94d7bac91bd12d3593ebaaa9386d)
This code will be released in upcoming Kea 1.2 beta, scheduled for early
April. If you can't wait for it, the unreleased code is already
available on github.
Tomek
More information about the Kea-users
mailing list