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: dhcpd does not answer DHCPDISCOVER from systemd-networkd
      (Frederik Himpe)
   2. Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
      (glenn.satch...@uniq.com.au)
   3. Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
      (Pavel Zhukov)
   4. Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
      (Simon Hobson)
   5. Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
      (Bill Shirley)


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

Message: 1
Date: Wed, 26 Feb 2020 13:54:41 +0100
From: Frederik Himpe <frede...@frehi.be>
To: dhcp-users@lists.isc.org
Subject: Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
Message-ID: <11f94a94fb3cdd1b48ec6b4ab93b6f83d4930d91.ca...@frehi.be>
Content-Type: text/plain; charset="UTF-8"

On Tue, 2020-02-25 at 20:31 +0000, Simon Hobson wrote:
> Frederik Himpe <frede...@frehi.be> wrote:
> 
> > I have a Debian Buster server running dhcpd version 4.4.1-2 an a
> > client
> > with Ubuntu 18.04. When I use systemd-netword to get an IP using
> > DHCP,
> > the server does not answer the DHCPDISCOVER. However, when I run
> > dhclient instead, dhcpd does answer the DHCPDISCOVER. Also PXE
> > booting
> > works.
> > 
> > 
> 
> > subclass "AI" 1:04:0e:3c:a3:b2:79;
> 
> So where is group AI defined ? How is it defined ?

Right, I had forgotten about that. It's defined like this, at the top
level in the hierarchy in dhcpd.conf:

class "AI" {
        match pick-first-value (option dhcp-client-identifier, hardware);
}

And there we have the problem...

> One really obvious difference there is that dhclient is not sending
> Option 61, while systemd-networkd is sending a 19 byte Option 61.

So this option 61 is the dhcp-client-identifier I'm using in the class
definition. Thanks for the pointing me in the right direction! With
just match hardware it's now working as I want.

Regards,

-- 
Frederik Himpe <frede...@frehi.be>



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

Message: 2
Date: Thu, 27 Feb 2020 00:28:56 +1100
From: glenn.satch...@uniq.com.au
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
Message-ID: <653b3caf18894f0e9090e8640f88c...@uniq.com.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On 2020-02-26 23:54, Frederik Himpe wrote:
> On Tue, 2020-02-25 at 20:31 +0000, Simon Hobson wrote:
>> Frederik Himpe <frede...@frehi.be> wrote:
>> 
>> > I have a Debian Buster server running dhcpd version 4.4.1-2 an a
>> > client
>> > with Ubuntu 18.04. When I use systemd-netword to get an IP using
>> > DHCP,
>> > the server does not answer the DHCPDISCOVER. However, when I run
>> > dhclient instead, dhcpd does answer the DHCPDISCOVER. Also PXE
>> > booting
>> > works.
>> >
>> >
>> 
>> > subclass "AI" 1:04:0e:3c:a3:b2:79;
>> 
>> So where is group AI defined ? How is it defined ?
> 
> Right, I had forgotten about that. It's defined like this, at the top
> level in the hierarchy in dhcpd.conf:
> 
> class "AI" {
>         match pick-first-value (option dhcp-client-identifier, 
> hardware);
> }
> 
> And there we have the problem...
> 
>> One really obvious difference there is that dhclient is not sending
>> Option 61, while systemd-networkd is sending a 19 byte Option 61.
> 
> So this option 61 is the dhcp-client-identifier I'm using in the class
> definition. Thanks for the pointing me in the right direction! With
> just match hardware it's now working as I want.
> 
> Regards,

Hi Frederik

The value of the dhcp-client-identifier, as shown in the packet dump, is 
b6:22:0f:eb:00:02:00:00:ab:11:f0:a4:5a:73:5e:e8:d2:07

and that doesn't match the sub-class value, so you can see why the 
client doesn't match class AI, and hence "no free leases" :)

Potentially you could have added another value to the sub-class with 
that identifier.

subclass "AI" b6:22:0f:eb:00:02:00:00:ab:11:f0:a4:5a:73:5e:e8:d2:07;

The other points are valid though, the whole group statement should be 
moved outside the shared-network block.

regards,
-glenn


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

Message: 3
Date: Wed, 26 Feb 2020 16:32:15 +0100
From: Pavel Zhukov <pzhu...@redhat.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
Message-ID: <87a755tlds....@pzhukov-workstation.usersys.redhat.com>
Content-Type: text/plain

glenn.satch...@uniq.com.au writes:

> On 2020-02-26 23:54, Frederik Himpe wrote:
[ ... ]
>>
>> class "AI" {
>>         match pick-first-value (option dhcp-client-identifier,
>> hardware);
>> }
>>
>> And there we have the problem...
>>
[ ... ]

> Potentially you could have added another value to the sub-class with
> that identifier.
Or change pick-first-value order to match hardware first?
>
> subclass "AI" b6:22:0f:eb:00:02:00:00:ab:11:f0:a4:5a:73:5e:e8:d2:07;
>
> The other points are valid though, the whole group statement should be
> moved outside the shared-network block.
>
> regards,
> -glenn
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

-- 
PAVEL ZHUKOV

 



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

Message: 4
Date: Wed, 26 Feb 2020 15:57:46 +0000
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
Message-ID: <dc0a1064-7464-438a-8322-3e6961ebf...@thehobsons.co.uk>
Content-Type: text/plain; charset=utf-8

Pavel Zhukov <pzhu...@redhat.com> wrote:

>Or change pick-first-value order to match hardware first?

That would make pick-first-value a null operation. Hardware is always present.

Simon


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

Message: 5
Date: Wed, 26 Feb 2020 18:51:55 -0500
From: Bill Shirley <b...@c3po.polymerindustries.biz>
To: dhcp-users@lists.isc.org
Subject: Re: dhcpd does not answer DHCPDISCOVER from systemd-networkd
Message-ID:
        <82868422-d299-55d3-4fb4-62c4ebe9e...@c3po.polymerindustries.biz>
Content-Type: text/plain; charset=utf-8; format=flowed

Hardware is always present

Except for IPv6.? This is a real irritation to me about IPv6 along with the 
fact that
most devices (except Windows) do not send their hostname (or FQDN).? The
whole "I want to hide on your LAN and use your internet service" idea is crazy.

Bill

On 2/26/2020 10:57 AM, Simon Hobson wrote:
> Pavel Zhukov <pzhu...@redhat.com> wrote:
>
>> Or change pick-first-value order to match hardware first?
> That would make pick-first-value a null operation. Hardware is always present.
>
> Simon
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users


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

Subject: Digest Footer

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


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

End of dhcp-users Digest, Vol 136, Issue 12
*******************************************

Reply via email to