Noticed that a couple of my hosts have unlimited leasetime for IPV6 addresses, even though they live in a pool which has 24h lease defined, in fact the IPV4 addresses follow that rule just fine.
config dhcp 'casa'
option interface 'casa'
option limit '100'
option leasetime '24h'
option dhcpv6 'server'
option ra 'server'
option ra_management '1'
option force '1'
option start '11'
list dhcp_option 'option:dns-server,0.0.0.0'
[...]
config host 'shanpu'
option ip 'x.y.z.15'
option mac 'mac1'
option duid '0001something'
option hostid '0015'
option dns '1'
Another host in a 30min pool correctly shows up with a limited lease. Any pointers?
Ok, for the moment it's enough to know about this.
Though the fact that somehow on the guest network the 30min leasetime seems to work is... puzzling.
(edit: this host is now off)
I have tried both ra_useleasetime '1' (which I had for quite some time)
and ra_useleasetime 1
restarting odhcpd in between but the ubus call still reports the client as having unlimited lease.
The fact that one host has a 30m lease instead of unlimited is pretty interesting, though, because all three VLANs have the option set.
yes, as expected rebooting did nothing more than disconnect / reconnect.
it still is listed as "-1" lifetime.
I guess I'll try again when a newer version comes out, thanks.
An active lease unfortunately takes precedence over a configuration for a static lease there (you don't need to delete the whole file, just the offending lease/ line from it is suffucient).
I used this trick too when it was picking up the wrong address but so far the lifetime is stuck at -1.
Maybe I'll try again with a new release, it's pretty pointless to waste time on a minor detail once the correct lease is used.