Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. RE: Ubuntu update to isc-dhcp-server seems to have broken
      config file processing (bls s)
   2. DHCP server offers same lease regardless of changed option
      (Klemen Sladic)


----------------------------------------------------------------------

Message: 1
Date: Mon, 7 Jun 2021 13:52:46 +0000
From: bls s <bls3...@outlook.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: RE: Ubuntu update to isc-dhcp-server seems to have broken
        config file processing
Message-ID:
        
<mwhpr02mb259154712f025d358a5db6afa3...@mwhpr02mb2591.namprd02.prod.outlook.com>
        
Content-Type: text/plain; charset="us-ascii"

Response from Ubuntu on Launchpad (https://bugs.launchpad.net/bugs/1930917):

I can confirm the update introduced a regression on Hirsute (and Impish I 
presume). Focal and Groovy work properly. Unfortunately, it's not related to 
the security patch, but it stems from the package being rebuilt with the newer 
toolchain in Hirsute, so removing the patch won't fix the issue.

I am currently investigating how to fix this.

** Also affects: isc-dhcp (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: isc-dhcp (Ubuntu Impish)
   Importance: Undecided
       Status: Confirmed

** Changed in: isc-dhcp (Ubuntu Hirsute)
       Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Hirsute)
     Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: isc-dhcp (Ubuntu Impish)
     Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: isc-dhcp (Ubuntu Hirsute)
   Importance: Undecided => Critical

** Changed in: isc-dhcp (Ubuntu Impish)
   Importance: Undecided => Critical

-----Original Message-----
From: dhcp-users <dhcp-users-boun...@lists.isc.org> On Behalf Of bls s
Sent: Friday, June 4, 2021 7:02 AM
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: RE: Ubuntu update to isc-dhcp-server seems to have broken config file 
processing

Thanks, Simon for confirming my understanding.

Yes, have backed off to the previous version and it works, so there's a 
workaround.

I'm off to sort out how to file an actual bug report on Ubuntu in the hope that 
they revert the change (whatever it is!).

Benn

-----Original Message-----
From: dhcp-users <dhcp-users-boun...@lists.isc.org> On Behalf Of Simon Hobson
Sent: Friday, June 4, 2021 5:03 AM
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Ubuntu update to isc-dhcp-server seems to have broken config file 
processing

bls s <bls3...@outlook.com> wrote:

> I'm using isc-dhcp-server 4.4.1-2 on RasPiOS Buster, and it's working fine 
> with the following subnet declaration:
>  
> subnet 192.168.92.0 netmask 255.255.255.0 {
>     option domain-search "foo.com", "dyn.foo.com";
>     option broadcast-address 192.168.92.255;
>     allow duplicates;
>     ddns-updates off;
>     pool {
>         ddns-updates on;
>         allow unknown-clients;
>         option domain-name "dyn.foo.com";
>         ddns-rev-domainname "dhcp";
>         default-lease-time 86400;
>         max-lease-time 86400;
>         range 192.168.92.101 192.168.92.127;
>     }
> }

That looks fine

> This same subnet config worked on Ubuntu 21.04 a couple of weeks ago, with 
> isc-dhcp-server V4.4.1-2.2-ubuntu6 on it. Today I updated on Ubuntu, got 
> isc-dhcp-server V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server complains about 
> "Can't clone pool group".
>  
> I found that I can put the pool declaration outside of the subnet declaration 
> on Ubuntu, and it works correctly. Unfortunately, doing this on RasPiOS fails!

Having a pool outside of a subnet isn't a valid config. It may appear to work, 
as do some other config errors, but may cause some really "interesting" issues.

> Am I totally using subnet and pool incorrectly, or is this an incompatible 
> change in isc-dhcp-server? And, is it an intended change coming to mainline 
> isc-dhcp-server or did Ubuntu bork it?

I'd be thinking that there's something changed in the Ubuntu version. Can you 
roll-back to the earlier version and try it again ?

Simon

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

Message: 2
Date: Tue, 8 Jun 2021 15:47:28 +1200
From: Klemen Sladic <gostur...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: DHCP server offers same lease regardless of changed option
Message-ID:
        <CAN6eUaHLN1ALt0KkHa7Whzdo=+tv0ucle0vynhe6a_op9kg...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi.

I have a question regarding valid leases.
Let's say DHCP server is configured with a host entry using a custom DHCP
option with some predefined value, like:

host host1 {
   hardware ethernet 00:01:02:03:04:05;
   option my-net-opt "host1_net_opt"; }

After host1 gets this lease and recognizes the option the lease is valid
for (let's say) 10 days.

Now I reconfigure DHCP server by changing option value for that host, like:

host host1 {
   hardware ethernet 00:01:02:03:04:05;
   option my-net-opt "host1_net_opt_new"; }

and restart the DHCP server.

What I am experiencing is that if host1 requests a new lease (after restart
or renew) while the old one is still valid, it gets the same old lease with
the old option value.

My questions are:
1. Is this expected behaviour or am I doing something wrong?
2. If this is how it works is there a way to somehow invalidate that old
lease to force the server to create a new one with a new option value?

Thank you very much.
Any help would be highly appreciated.

RegK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210608/c8957d54/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 152, Issue 4
******************************************

Reply via email to