Log messages

Thu Jan 22 06:12:06 UTC 2015

Hello, Keith.

I saw the same issue, too. It seems that for DHCPINFORM messages dhcpd
does not set leased-address.

I used

if (option dhcp-message-type != 8)

test to avoid DHCPINFORMS in places where I need leased-address.

On 21.01.2015 20:36, Keith wrote:
> As an extra bit of info.
> 
> I just realized that this log message only appears when an INFORM comes in from
> the option 82
> enabled networks:
> 
> Jan 17 06:00:20 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:00:20 netreg1 dhcpd: DHCPINFORM from 69.176.182.54 via 69.176.182.1
> --
> Jan 17 06:01:03 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:01:03 netreg1 dhcpd: DHCPINFORM from 69.176.184.249 via 69.176.184.1
> --
> Jan 17 06:01:07 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:01:07 netreg1 dhcpd: DHCPINFORM from 69.176.183.198 via 69.176.183.1
> --
> Jan 17 06:01:21 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:01:21 netreg1 dhcpd: DHCPINFORM from 69.176.182.54 via 69.176.182.1
> --
> Jan 17 06:02:24 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:02:24 netreg1 dhcpd: DHCPINFORM from 69.176.182.54 via 69.176.182.1
> --
> Jan 17 06:03:26 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:03:26 netreg1 dhcpd: DHCPINFORM from 69.176.182.54 via 69.176.182.1
> --
> Jan 17 06:03:58 netreg1 dhcpd: data: "leased-address" configuration directive:
> there is no lease associated with this client.
> Jan 17 06:03:58 netreg1 dhcpd: DHCPINFORM from 69.176.184.94 via 69.176.184.1
> 
> I'm guessing its harmless, but would like to know if there is something I can do
> to make it go away?
> 
> -> -----Original Message-----
> -> From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-
> -> bounces at lists.isc.org] On Behalf Of Keith
> -> Sent: Wednesday, January 21, 2015 9:30 AM
> -> To: dhcp-users at lists.isc.org
> -> Subject: Log messages
> -> 
> -> We recently started using Option 82 on our dslams.
> -> 
> -> I first turned it on for a few of them the first week of Jan.
> -> 
> -> Using this in the subnet declaration:
> -> 
> -> if exists agent.circuit-id {
> ->         log ( error, concat( "Lease for ", binary-to-ascii (10, 8, ".",
> leased-address), "
> -> is connected to ", option agent.circuit-id));
> ->         }
> -> 
> -> will generate this line in Dhcpd.log:
> -> 
> -> Lease for 69.176.181.162 is connected to
> -> Shelf-14-30:1/1:0.35:VLAN=1:ifIndex=1003001
> -> 
> -> Something I did not notice for some reason until today is a log line that is
> -> appearing:
> -> 
> -> dhcpd: data: "leased-address" configuration directive: there is no lease
> -> associated with this client
> -> 
> -> I can't tell where its coming from.
> -> 
> -> DHCPDISCOVER from 00:16:b6:80:b5:13 (tc-e4f6ed2f5b87) via 69.176.179.1 Jan 21
> -> 09:18:20 netreg1 dhcpd: DHCPOFFER on 69.176.179.166 to 00:16:b6:80:b5:13 via
> -> 69.176.179.1 Jan 21 09:18:20 netreg1 dhcpd: DHCPREQUEST for 69.176.179.166
> -> (209.145.111.37) from 00:16:b6:80:b5:13 via 69.176.179.1 Jan 21 09:18:20
> netreg1
> -> dhcpd: DHCPACK on 69.176.179.166 to 00:16:b6:80:b5:13 via 69.176.179.1 Jan 21
> -> 09:18:33 netreg1 dhcpd: data: "leased-address" configuration directive:
> -> there is no lease associated with this client.
> -> Jan 21 09:18:33 netreg1 dhcpd: DHCPINFORM from 69.176.180.150 via
> -> 69.176.180.1 Jan 21 09:18:33 netreg1 dhcpd: DHCPACK to 69.176.180.150
> -> (e0:69:95:77:5c:98) via
> -> bce0
> -> Jan 21 09:18:42 netreg1 dhcpd: DHCPDISCOVER from 44:6d:57:56:3f:4f (Gerry-
> -> HP) via 69.176.178.1 Jan 21 09:18:43 netreg1 dhcpd: DHCPOFFER on
> 69.176.178.90
> -> to 44:6d:57:56:3f:4f
> -> (Gerry-HP) via 69.176.178.1
> -> 
> -> A little snip of the log file, is this being generated from the
> 69.176.180.150 lease
> -> or the 69.176.179.166 lease?
> -> 
> -> The 69.176.180.0 network has option 82 enabled, but the 69.176.179 network
> -> does not. And looking how the option 82 info comes through this appears to be
> -> from the 69.176.180 network.
> -> 
> -> The "leased-address" log entry has me wondering. It didn't appear before
> -> enabling option 82 as I went back in my logs looking.
> -> 
> -> There is a leased address for both IP addresses in Dhcpd.leases.
> -> 
> -> As far as I can tell dhcp is working ok. Where is this log entry coming from
> and is
> -> this something to be concerned about?
> -> 
> -> Thanks,
> -> Keith
> -> 
> -> _______________________________________________
> -> dhcp-users mailing list
> -> dhcp-users at lists.isc.org
> -> https://lists.isc.org/mailman/listinfo/dhcp-users
> 
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
> 

-- 
Konstantin Stefanov,

Research Computing Center
M.V Lomonosov Moscow State University