Determining which server, in a partner pair, granted a lease

Daniel Duarte dan.r.duarte at gmail.com
Fri Jul 10 17:44:23 UTC 2009


That is a great solution, unfortunately on my network I can't edit the
configuration, because that's handled by some other guys, I have only
the already available info. So the analysis of the dhcpd.leases is the
only option I have to conclude which server answered a specific
request.

Daniel

2009/7/10 Steve van der Burg <steve.vanderburg at lhsc.on.ca>:
> Thanks for the info.  Knowing about that field led me to set up a little bit of extra logging to catch it:
>
>  if option dhcp-message-type = 3 {
>    log (info, concat("extra: dhcp-server-identifier at REQUEST is ",
>                      binary-to-ascii (10, 8, ".", option dhcp-server-identifier),
>                      " for MAC ",
>                      binary-to-ascii (16, 8, ":", hardware)));
>  }
>
> This seems to work, and now I can scrape the logs to figure out which server gave out a lease (scrape for my "extra:" message, and confirm that the server responded by looking for the DHCPACK back to the same MAC).
>
> ...Steve
>
> loganathan Govindaraj <loganosc at gmail.com> wrote:
>> Based on the sniffer logs from the server , on the server identifier field(
>> offer )  you check which server has offered the ip .
>>
>> Logan
>>
>> On Tue, Jul 7, 2009 at 2:15 AM, Steve van der Burg <
>> steve.vanderburg at lhsc.on.ca> wrote:
>>
>>> Please forgive me if this has been asked and answered before (I searched
>>> the list for at least 30 minutes and couldn't find an answer):
>>>
>>> Is there a way, in 3.x, either by looking at the leases themselves (in
>>> dhcpd.leases) or the log files, or possibly by adding a bit of extra
>>> logging, to tell which of two dhcpd partners granted a lease to a client?
>>>  When I compare lease files and logs on both, it all pretty much looks the
>>> same on both.
>>>
>>> Thanks.
>>>
>>> ...Steve
>>>
>>>
>>>
>>>  --------------------------------------------------------------------------------
>>> This information is directed in confidence solely to the person named above
>>> and may contain confidential and/or privileged material. This information
>>> may not otherwise be distributed, copied or disclosed. If you have received
>>> this e-mail in error, please notify the sender immediately via a return
>>> e-mail and destroy original message. Thank you for your cooperation.
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>
>  --------------------------------------------------------------------------------
> This information is directed in confidence solely to the person named above and may contain confidential and/or privileged material. This information may not otherwise be distributed, copied or disclosed. If you have received this e-mail in error, please notify the sender immediately via a return e-mail and destroy original message. Thank you for your cooperation.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>



More information about the dhcp-users mailing list