[Kea-users] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: the interface br0 is not running

2022-01-11 Thread Michael Agbaglo
Why is kea complaining while ISC dhcpd is working? 2022-01-12 07:28:32.200 WARN [kea-dhcp4.dhcpsrv/111933.140670479808384] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: the interface br0 is not running 2022-01-12 07:28:32.200 WARN [kea-dhcp4.dhcpsrv/111933.140670479808384] DHCPSRV_OPEN_SOC

Re: [Kea-users] HA setup in kubernetes, hostnames in the configuration fail to resolve

2022-01-11 Thread Yordanov, Damyan via Kea-users
Thanks for the reply. I can unterstand that the feature lacked priority, back then. That said, the problems below seem pretty much trivially solvable for me, if not solved already. They are not Kea-related anyway. In fact, the ISC DHCPD does support hostnames (https://kb.isc.org/v1/docs/isc-dh

Re: [Kea-users] KEA support for option 150 (tftp-server-ip)

2022-01-11 Thread Maria Hrabosova
Hi, I don't fully agree that option 150 can be anything. It is a standard DHCP option defined in https://www.rfc-editor.org/rfc/rfc5859.html and, as Veronique said, it's also recognized by ISC DHCP (https://kb.isc.org/v1/docs/isc-dhcp-44-manual-pages-dhcp-options#standard-dhcpv4-options). Tha

Re: [Kea-users] KEA support for option 150 (tftp-server-ip)

2022-01-11 Thread Gordon Ross
Option 150 can be anything so you have to define it yourself. //Define some custom options "option-def": [ //Option for Cisco IP Phones to find CUCM. { "name": "cisco-cucm-servers", "code": 150, "type": "ipv4-address", "array": true } ] From: Kea-u

[Kea-users] KEA support for option 150 (tftp-server-ip)

2022-01-11 Thread Veronique Lefebure
Hello, In ISC DHCP v4.4.2 we have (https://downloads.isc.org/isc/dhcp/4.4.2/dhcp-4.4.2-RELNOTES) : Support for sending and receiving additional DHCP4 options has been added to both the dhcpd and dhclient. Specifically: option codes 93,94, and 97 (RFC 4578); code 150 (RFC 5859); and codes 209,2