Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. problem in custom option (Patrice KOCH)
2. Re: problem in custom option (Francis Dupont)
----------------------------------------------------------------------
Message: 1
Date: Thu, 30 Mar 2017 14:50:42 +0200 (CEST)
From: Patrice KOCH <[email protected]>
To: [email protected]
Subject: [kea-dev] problem in custom option
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi everyone,
I try to define a custom dhcp4 option in kea (1.1.0) and I fall face to one
problem
the mistake is probably in the definition of the data section
the definition of my option :
"option-def": [
{
"name": "option-242",
"code": 242,
"space": "dhcp4",
"type": "string",
"record-types": "",
"array": false,
"encapsulate": ""
}
]
the content of my customized option :
{
"name": "option-242",
"code": 242,
"space": "dhcp4",
"csv-format": true,
"data":
"MCIPADD=10.10.10.10,MCPORT=1719,L2Q=1,L2QVLAN=3033,HTTPSRVR=10.10.10.11,HTTPPORT=80,DHCPSTDT=1"
}
to my mind it is correct but in my log debug file only the first part before
the comma is sent to my dhcp client !?
the result in my debug file :
type=242, len=022: "MCIPADD=10.10.10.10" (string)
Could someone give me some help ?
Thanks, pK.
____________________________________________________________________
Patrice KOCH [email protected]
Directeur du CRI
Centre de Ressources Informatiques tel : 03 81 66 61 29
Universite de Franche-Comte fax : 03 81 66 61 77
16, route de GRAY
25030 BESANCON Cedex
____________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/kea-dev/attachments/20170330/2197e489/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 30 Mar 2017 15:39:43 +0000
From: Francis Dupont <[email protected]>
To: Patrice KOCH <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] problem in custom option
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Currently you may not embed commas (,) in a string. It is a known
defect which was fixed by:
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)
Thanks
Francis Dupont <[email protected]>
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 36, Issue 4
**************************************
