Page MenuHomeVyOS Platform

DHCP6: no leases are created unless specifying a "interface" on the zone
Needs testing, LowPublic


Doring migration from my trusted old 1.4 snapshot to the newest 1.5-daily, dhcpv6 stopped working
After a hint from simon on slack this was fixed by adding the ìnterface directive inside the shared-network-name.
configuration not working on newest 1.5 rolling:

shared-network-name Inside {
    subnet xxxx:02c8:ab00:0::/64 {
        range 1 {
            start xxxx:aac8:ab00:0::1000
            stop xxxx:aac8:ab00:0::1999
        subnet-id 1

working configuration:

shared-network-name Inside {
    interface eth0
    subnet xxxx:aac8:ab00:0::/64 {
        range 1 {
            start xxxx:aac8:ab00:0::1000
            stop xx:aac8:ab00:0::1999
        subnet-id 1

if this is reproduce able , this is a change of operation since 1.4.
So question is if this is intended or not?
if its intended it is not migrated into, there are also no warnings on change of configuration needed.
so, hopefully this is a bug :)

(dhcpv4 did not need this interface statement)


Difficulty level
Unknown (require assessment)
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

runar created this object in space S1 VyOS Public.
sarthurdev changed the task status from Open to Confirmed.Jan 27 2024, 10:27 PM
sarthurdev claimed this task.

This does seem to be new behaviour introduced with Kea. ISC dhcpd did previously assume local distribution of a subnet based on the interface having an address within the subnet, Kea has changed to require this being explicitly defined.


sarthurdev changed the task status from Confirmed to In progress.Mon, Feb 12, 10:39 PM
sarthurdev moved this task from Need Triage to In Progress on the VyOS 1.4 Sagitta board.