How to Read "dhcp.leases"?

How to Read "dhcp.leases"?

Post by Daniel Norto » Sat, 08 Jul 2000 04:00:00



I can't make sense out of this file.  The clients (Windows NT and
Windows 95) currently on the net have fixed addresses, so I don't see
why they would be listed as "abandoned."  Nor do I understand why the
client systems would be assigned other IP addresses.  The "hardware
ethernet" fields don't match the hardware addresses, they're too long
and the first three bytes are all "RAS".

Any clues?

Thanks.
--
Daniel Norton

=====
lease 172.16.0.5 {
        starts 5 2000/07/07 18:03:45;
        ends 6 2000/07/08 18:03:45;
        hardware ethernet 52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:02:00:00:00;
        uid 01:52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:02:00:00:00;
        client-hostname "BIFF";

Quote:}

lease 172.16.0.3 {
        starts 5 2000/07/07 18:00:44;
        ends 6 2000/07/08 18:00:44;
        hardware ethernet 52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:01:00:00:00;
        uid 01:52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:01:00:00:00;
        client-hostname "BIFF";
Quote:}

lease 172.16.0.10 {
        starts 5 2000/07/07 03:04:43;
        ends 6 2000/07/08 03:04:43;
        hardware ethernet 52:41:53:20:c0:8f:86:71:23:e2:bf:01:02:00:00:00;
        uid 01:52:41:53:20:c0:8f:86:71:23:e2:bf:01:02:00:00:00;
        client-hostname "REGIT";
Quote:}

lease 172.16.0.9 {
        starts 5 2000/07/07 03:02:42;
        ends 6 2000/07/08 03:02:42;
        hardware ethernet 52:41:53:20:c0:8f:86:71:23:e2:bf:01:01:00:00:00;
        uid 01:52:41:53:20:c0:8f:86:71:23:e2:bf:01:01:00:00:00;
        client-hostname "REGIT";
Quote:}

lease 172.16.0.1 {
        starts 0 2000/07/02 06:44:54;
        ends 5 2000/07/07 13:49:51;
        abandoned;
        client-hostname "BIFF";
Quote:}

lease 172.16.0.8 {
        starts 6 2000/07/01 08:46:12;
        ends 6 2000/07/01 08:46:12;
        abandoned;
        client-hostname "REGIT";
Quote:}

 
 
 

How to Read "dhcp.leases"?

Post by Ken Johnso » Sat, 08 Jul 2000 04:00:00



> I can't make sense out of this file.  The clients (Windows NT and
> Windows 95) currently on the net have fixed addresses, so I don't see
> why they would be listed as "abandoned."  Nor do I understand why the
> client systems would be assigned other IP addresses.  The "hardware
> ethernet" fields don't match the hardware addresses, they're too long
> and the first three bytes are all "RAS".

> Any clues?

> Thanks.
> --
> Daniel Norton

> =====
> lease 172.16.0.5 {
>         starts 5 2000/07/07 18:03:45;
>         ends 6 2000/07/08 18:03:45;
>         hardware ethernet 52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:02:00:00:00;
>         uid 01:52:41:53:20:60:ee:f3:9c:9e:6b:bf:01:02:00:00:00;
>         client-hostname "BIFF";
> }

See "man dhcpd.leases"

"Abandoned" means from the server's perspective, the server isn't going
to assign that address for a while...  because either (a) the client was
offered the address but said he didn't want it, or (b) the server was
going to offer the address, but checked first, and found that it was
already being used.

You're right that the hardware addresses seem a bit wierd;   normally
they're only six bytes.   I have heard that hardware manufacturers are
going to start assigning longer addresses because they're running low.  
Are these NICs relatively new?

K.

 
 
 

How to Read "dhcp.leases"?

Post by Daniel Norto » Sat, 08 Jul 2000 04:00:00




Quote:>"Abandoned" means from the server's perspective, the server isn't going
>to assign that address for a while...  

Okay, that makes sense now.  Thanks.

Quote:>You're right that the hardware addresses seem a bit wierd;   normally
>they're only six bytes.   I have heard that hardware manufacturers are
>going to start assigning longer addresses because they're running low.  
>Are these NICs relatively new?

The NICs have six-byte addresses.  Since the values start with "RAS", I
surmise that it has something to do with Microsoft's Remote Access
Server.  Why on earth it would taking out leases on IP addresses is
beyond me.

Now that I'm writing this it dawns on me that it probably relays the
DHCP assignments to ports that receive incoming dialups.

--
Daniel Norton