Hi,
first, as a very old user of isc dhcp, my compliments on KEA!
our dhcpd.conf is about 32K lines, and after some minor tweaks managed to run
keama
without errors (it seems ISC-DHCP is a bit less strict than keama (strange
since they share code))
these are some of the oddities:
this one seems harmless but …
original isc-dhcp:
subnet 132.65.192.0 netmask 255.255.252.0 {
option domain-name "cs.huji.ac.il <http://cs.huji.ac.il/>";
option domain-name-servers nsa,sa1,shuldig;
option routers 132.65.192.1;
}
becomes:
{
"id": 1,
"subnet": "132.65.233.0/24",
"option-data": [
{
"space": "dhcp4",
"name": "domain-name",
"code": 15,
"data": "cs.huji.ac.il <http://cs.huji.ac.il/>"
},
{
"space": "dhcp4",
"name": "domain-name-servers",
"code": 6,
// "original-data": "nsa,sa1,shuldig”, <- ?????
"data": "nsa, sa1, shuldig” <- ??????
},
{
"space": "dhcp4",
"name": "routers",
"code": 3,
"data": "132.65.224.1"
}
]
},
this one is a bit strange:
original isc-dhcp:
option FBSD.conf-path code 5 = text;
becomes:
"option-def": [
...
{
"space": "FBSD",
"name": "conf-path",
"code": 5,
"type": "string"
},
so far so good, but then
…
{
"space": "FBSD",
"name": "conf-path",
"code": 5,
"csv-format": false,
// "original-data": "fr-06:/vol/system/share/conf",
"data": "66722d30363a2f766f6c2f73797374656d2f73686172652f636f6e66"
},
the string becomes hex?
have some more odd issues, but for later.
thanks
danny
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
