@himurae, Permission and ownership of config directory and files and fine. If you are still seeing the DHCP leases not being created, something else is probably going on.

Can you please paste the output of ls -ld /config/dhcp and ls -l /config/dhcp. It is possible you might have installed a version _before_ 1.5-rolling-202401030023 and the instance is carrying forward the misconfigured directory/file persmissions.

completed

In T3316#168877, @workingagain wrote:

after manual ownership change dhcp4.leases so the server can start causes this error:

ERROR [kea-dhcp4.dhcpsrv/4006.140169685592512] DHCPSRV_MEMFILE_LFC_LEASE_FILE_RENAME_FAIL failed to rename the current lease file /config/dhcp4.leases to /config/dhcp4.leases.1, reason: Permission denied

https://github.com/vyos/vyos-1x/pull/2686

In T5721#168743, @giuavo wrote:

I have followed your suggestion: a fresh VyOS install in a VM and tried to load the current configuration. Here are the errors I get:

[ service dns dynamic name service-ovh-eth1-11-web web-options url checkip.dyndns.com ]
"checkip.dyndns.com" is not a valid URL


[ service dns dynamic name service-ovh-eth1-11-web web-options url checkip.dyndns.com ]
Invalid HTTP(S) URL format

[[]] failed

configuration for dhcp reservation with just mac address doesn't give configuration exception, but cause an error to kea directly as ERROR [kea-dhcp4.dhcp4/49022.140176366361024] DHCP4_PARSER_FAIL failed to create or run parser for configuration element shared-networks: specified reservation for DUID: hwtype=1 xx:xx:xx:xx:xx:xx must include at least one resource, i.e. hostname, IPv4 address, IPv6 address/prefix, options (/run/kea/kea-dhcp4.conf:59:5)

set service dhcp-server dynamic-dns-update
set service dhcp-server hostfile-update
set service dhcp-server shared-network-name LAN authoritative
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 default-router '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 domain-name 'home'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 name-server '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 start '192.168.1.120'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 stop '192.168.1.230'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 static-mapping ...
...

I also notice that ddclient has a similar problem.

ddclient[1710]: FAILED:   Unable to obtain information for 'pppoe0' -- missing ip or ifconfig command

This might be a problem that's specific to me. I don't know why every systemd start too early.

In T3316#167384, @sdev wrote:

In T3316#167382, @indrajitr wrote:

• with set service dhcp-server hostfile-update the file /etc/hosts doesn't get update with any entry from dhcp at all

Thanks, will investigate this.

@sdev, this will require adjusting on-dhcp-event.sh. I have a hacky local version that writes to /etc/hosts that partially works -- the $domain part is not picked up (which I suspect could be related to how kea-dhcp4.conf is generating the FQDN).

Do you want me to raise a draft PR for you to review?

By all means, thank you!

• with set service dhcp-server hostfile-update the file /etc/hosts doesn't get update with any entry from dhcp at all

Thanks, will investigate this.

https://github.com/vyos/vyos-1x/pull/2617

@Viacheslav, updated PR https://github.com/vyos/vyos-1x/pull/2562

Looks like, we still need to keep /etc/avahi/services because avahi-daemon chroot to that location at startup. This is set up at build time via AVAHI_CONFIG_DIR and there is no way to change it at runtime.

Pretty sure some preceding backports are pending. Please give me a couple of days. I plan to sync up 1.4 with 1.5 and update the docs.