Unknown client alerts and clients not getting IP addresses

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Unknown client alerts and clients not getting IP addresses

Fleming, Tony

Good afternoon folks!

We ran into a problem today and it has me completely dumfounded

Background:

                We create a host record for each device that connects to our network

                Over the years our dhcpd.conf file has grown due to little purging (yeah – I know we should be purging the data)

Symptom:

                Suddenly today, we began getting reports users are unable to get an IP address.

                The clients vary from iphones, to OS X and PC laptops

                                The issue doesn’t seem to be OS or hardware dependent

                My logs are alerting:

                                dhcpd: DHCPDISCOVER FROM xx:xx:xx:xx:xx:xx via x.x.x.x: uknown client

In my dhcpd file there is a “host” record for each device – so I am scratching my head to why the device isn’t getting an IP address.

                Not all devices are having trouble getting IP leases

Workaround:

                We have removed the directive in dhcpd.conf to “deny unknown clients”

                Now all of our devices are getting IP addresses.

 

Questions:

                Has anyone experienced a problem like this?

                                If so, what did you find to be the root cause?

                Is it possible my 300k line dhcpd.conf file is causing this behavior?

                                Could there be a programmatic time-out searching through host records in memory that is causing the host lookup to fail?

 

Thank you.

 


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: Unknown client alerts and clients not getting IP addresses

Simon Hobson
"Fleming, Tony" <[hidden email]> wrote:

> Background:
>                 We create a host record for each device that connects to our network
>                 Over the years our dhcpd.conf file has grown due to little purging (yeah – I know we should be purging the data)
> Symptom:
>                 Suddenly today, we began getting reports users are unable to get an IP address.
>                 The clients vary from iphones, to OS X and PC laptops
>                                 The issue doesn’t seem to be OS or hardware dependent
>                 My logs are alerting:
>                                 dhcpd: DHCPDISCOVER FROM xx:xx:xx:xx:xx:xx via x.x.x.x: uknown client
> In my dhcpd file there is a “host” record for each device – so I am scratching my head to why the device isn’t getting an IP address.
>                 Not all devices are having trouble getting IP leases
> Workaround:
>                 We have removed the directive in dhcpd.conf to “deny unknown clients”
>                 Now all of our devices are getting IP addresses.

Post your config - not all of it ;-)
But when you trim it, be very very careful that you don't alter the structure at all.
Include a problem client - both it's config and the log entries for it.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

RE: Unknown client alerts and clients not getting IP addresses

Fleming, Tony

Thank you.

Please let me know if you would like to see more of the configuration, but for now I am including one subnet and client configuration block.

 

class "Wired" {

        match hardware;

}

class "Wireless" {

        match hardware;

}

 

shared-network "STUWIRELESS-XXX" {

        authoritative;

        subnet 10.31.0.0 netmask 255.255.240.0 {

                pool {

                        allow members of "Wireless";

                        default-lease-time 3600; #1 hour

                        max-lease-time 3600;

                        option ntp-servers X.X.X.X, X.X.X.Y;

                        option domain-name-servers X.X.X.X, X.X.X.Y;

                        one-lease-per-client true;

                        option routers 10.31.0.1;

                        deny unknown-clients;

                        range 10.31.0.20 10.31.15.254;

                }

        }

}

 

subclass "Wireless" 44:85:00:2F:81:86;

host XXXX.STUDENT.XXX.XXX {

hardware ethernet 44:85:00:2F:81:86;

}

 

 

Here is the logged output:

Aug 23 07:52:56 srvr04 dhcpd: DHCPDISCOVER from 44:85:00:2f:81:86 via 10.31.0.1: network STUWIRELESS-XXX: no free leases

Aug 23 07:53:00 srvr04 dhcpd: DHCPDISCOVER from 44:85:00:2f:81:86 via 10.31.0.1: network STUWIRELESS-XXX: no free leases

Aug 23 07:53:09 srvr04 dhcpd: DHCPDISCOVER from 44:85:00:2f:81:86 via 10.31.0.1: network STUWIRELESS-XXX: no free leases

 

Here is the lease status:

Ranges:

shared net name        first ip                   last ip                    max      cur      percent  touch   t+c  t+c perc

STUWIRELESS-XXX    10.31.0.20       - 10.31.15.254      4075   436     10.699   3639  4075   100.000

 

It appears I have plenty of IP addresses in this pool. It appears the look-up to match a known client is failing for some reason.

 

BTW,

I did clean-up a lot of dead host entries (cut the file size into 2/3rds of its original size), but still having the trouble.

 

Any help is appreciated.

Thank you.

 

-----Original Message-----
From: dhcp-users [mailto:[hidden email]] On Behalf Of Simon Hobson
Sent: Tuesday, August 23, 2016 2:29 AM
To: Users of ISC DHCP <[hidden email]>
Subject: Re: Unknown client alerts and clients not getting IP addresses

 

"Fleming, Tony" <[hidden email]> wrote:

 

> Background:

>                 We create a host record for each device that connects to our network

>                 Over the years our dhcpd.conf file has grown due to

> little purging (yeah – I know we should be purging the data)

> Symptom:

>                 Suddenly today, we began getting reports users are unable to get an IP address.

>                 The clients vary from iphones, to OS X and PC laptops

>                                 The issue doesn’t seem to be OS or hardware dependent

>                 My logs are alerting:

>                                 dhcpd: DHCPDISCOVER FROM

> xx:xx:xx:xx:xx:xx via x.x.x.x: uknown client In my dhcpd file there is a “host” record for each device – so I am scratching my head to why the device isn’t getting an IP address.

>                 Not all devices are having trouble getting IP leases

> Workaround:

>                 We have removed the directive in dhcpd.conf to “deny unknown clients”

>                 Now all of our devices are getting IP addresses.

 

Post your config - not all of it ;-)

But when you trim it, be very very careful that you don't alter the structure at all.

Include a problem client - both it's config and the log entries for it.

 

_______________________________________________

dhcp-users mailing list

[hidden email]

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


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: Unknown client alerts and clients not getting IP addresses

Niall O'Reilly
On 23 Aug 2016, at 14:08, Fleming, Tony wrote:

> class "Wireless" {
>         match hardware;
> }
 [...]
> subclass "Wireless" 44:85:00:2F:81:86;

  IIRC, when matching on hardware, the htype byte (01 for Ethernet)
  must be prefixed to the MAC address.  If I'm not mistaken or
  distracted, you'll need to specify

subclass "Wireless" 01:44:85:00:2F:81:86;

  I hope this helps.

  Niall O'Reilly
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: Unknown client alerts and clients not getting IP addresses

Simon Hobson
In reply to this post by Fleming, Tony
"Fleming, Tony" <[hidden email]> wrote:

> class "Wired" {
>         match hardware;
> }
> class "Wireless" {
>         match hardware;
> }
>  
> shared-network "STUWIRELESS-XXX" {
>         authoritative;
>         subnet 10.31.0.0 netmask 255.255.240.0 {
>                 pool {
>                         allow members of "Wireless";
>                         default-lease-time 3600; #1 hour
>                         max-lease-time 3600;
>                         option ntp-servers X.X.X.X, X.X.X.Y;
>                         option domain-name-servers X.X.X.X, X.X.X.Y;
>                         one-lease-per-client true;
>                         option routers 10.31.0.1;
>                         deny unknown-clients;
>                         range 10.31.0.20 10.31.15.254;
>                 }
>         }
> }
>  
> subclass "Wireless" 44:85:00:2F:81:86;
> host XXXX.STUDENT.XXX.XXX {
> hardware ethernet 44:85:00:2F:81:86;
> }

First, as Niall points out, for your subclass declarations, you need to include the hardware type, so that should be :
subclass "Wireless" 1:44:85:00:2F:81:86;

This is shown in the man page examples for subclass.

Secondly, do you need both the subclass and host declarations ?
I'm not sure whether it includes known|unknown-clients, but general advice is to never mix allow and deny in a pool as the way the mix works isn't intuitive (and I can never remember how it goes !). Certainly, the "allow members of ..." will imply "deny anything not in ..."
If you don't need the host declarations, then it would save a considerable amount of maintenance.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

RE: Unknown client alerts and clients not getting IP addresses

Fleming, Tony
Thank you. I will make the changes and see if that fixes the problem.

Tony

-----Original Message-----
From: dhcp-users [mailto:[hidden email]] On Behalf Of Simon Hobson
Sent: Tuesday, August 23, 2016 9:11 AM
To: Users of ISC DHCP <[hidden email]>
Subject: Re: Unknown client alerts and clients not getting IP addresses

"Fleming, Tony" <[hidden email]> wrote:

> class "Wired" {
>         match hardware;
> }
> class "Wireless" {
>         match hardware;
> }
>  
> shared-network "STUWIRELESS-XXX" {
>         authoritative;
>         subnet 10.31.0.0 netmask 255.255.240.0 {
>                 pool {
>                         allow members of "Wireless";
>                         default-lease-time 3600; #1 hour
>                         max-lease-time 3600;
>                         option ntp-servers X.X.X.X, X.X.X.Y;
>                         option domain-name-servers X.X.X.X, X.X.X.Y;
>                         one-lease-per-client true;
>                         option routers 10.31.0.1;
>                         deny unknown-clients;
>                         range 10.31.0.20 10.31.15.254;
>                 }
>         }
> }
>  
> subclass "Wireless" 44:85:00:2F:81:86; host XXXX.STUDENT.XXX.XXX {
> hardware ethernet 44:85:00:2F:81:86; }

First, as Niall points out, for your subclass declarations, you need to include the hardware type, so that should be :
subclass "Wireless" 1:44:85:00:2F:81:86;

This is shown in the man page examples for subclass.

Secondly, do you need both the subclass and host declarations ?
I'm not sure whether it includes known|unknown-clients, but general advice is to never mix allow and deny in a pool as the way the mix works isn't intuitive (and I can never remember how it goes !). Certainly, the "allow members of ..." will imply "deny anything not in ..."
If you don't need the host declarations, then it would save a considerable amount of maintenance.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users