Can confirm this with DHCP instead of BOOTP as well:
Apr 19 17:51:48 curacao dhcpd[18031]: reuse_lease: lease age 671 (secs) under
25% threshold, reply with unaltered, existing lease
Apr 19 17:51:48 curacao dhcpd[18031]: DHCPDISCOVER from 08:00:27:44:28:00 via
eth0
Apr 19 17:51:49 curacao
I have tried this, too. I added the option "ignore-client-uids on;" and deleted
the lease file.
After restarting the server I could boot several targets. I also don't know if
this is a bug or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I dug a little deeper and could see that in our case the devices all use the
same uid in the boot request, thus receiving the same ip address via dhcp.
I guess the failing bootreply comes from the still memorized mac address of the
device before.
To get it working I used the option
I can confirm the bug description.
Ubuntu 16.04.2 LTS
isc-dhcp-server 4.3.3-5ubuntu12.6
dhcpd.conf used:
subnet 192.168.255.0 netmask 255.255.255.0
{
range dynamic-bootp 192.168.255.2 192.168.255.99;
allow bootp;
if substring (option vendor-class-identifier, 0, 10) = "AM335x ROM"
{
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665264
Title:
