Re: [Kea-users] ignore the broadcast flag in a discover and response with unicast

It requires to write code but it does not strictly require C++ code even it this case it will be simpler than to master interfaces between C++ and "external" languages as Python, OCaml, Lua or V8 cf. the fdxhook branch available on github where I describe such experiment. Regards Francis Dupont

Re: [Kea-users] ignore the broadcast flag in a discover and response with unicast

Hello Marcin, thx for pointing me into that direction. i'll have a closer look into it. wkr rene On Mon, Nov 13, 2017 at 1:21 PM, Marcin Siodelski wrote: > Hello, > Any non-standard behavior like this can be implemented using hooks. You'd > need to create a simple hook library

Re: [Kea-users] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT - conflicting reservation for address

We narrowed down the problem and it turned out to be caused by an ARP probe from the device tracking feature on the Cisco switches. Adding the following switch config resolved the issue: ip device tracking ip device tracking probe use-svi ip device tracking probe auto-source fallback 0.0.0.0

Re: [Kea-users] subnet scope DHCPv4 options in database?

On Sat, 11 Nov 2017, Tomek Mrugalski wrote: W dniu 10.11.2017 o 16:27, Owen Dunn pisze: However, it seems that subnet-scope options in the dhcp4_options table are not processed. Not supported yet. This is currently planned for 1.5. Currently (1.3) you can store options associated with host

Re: [Kea-users] ignore the broadcast flag in a discover and response with unicast

Hello, Any non-standard behavior like this can be implemented using hooks. You'd need to create a simple hook library which implements pkt4_send callout. See: -https://jenkins.isc.org/job/Kea_doc/doxygen/index.html#hooksFramework