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. Different Failover Interfaces than DHCP interfaces
(ift...@skynet.be)
2. Re: Log Statement: How to log offered Lease Time? (Bill Shirley)
3. Re: Log Statement: How to log offered Lease Time? (Bob Harold)
4. Re: Log Statement: How to log offered Lease Time? (Bob Harold)
5. RE: [EXT] Re: Why is dhcpd not matching the MAC address as it
should (Andrew Falanga (afalanga))
----------------------------------------------------------------------
Message: 1
Date: Mon, 22 Jan 2018 13:28:59 +0100 (CET)
From: ift...@skynet.be
To: dhcp-users@lists.isc.org
Subject: Different Failover Interfaces than DHCP interfaces
Message-ID:
<1895321737.68979.1516624139...@webmail.appsuite-ad.proximus.be>
Content-Type: text/plain; charset="utf-8"
Hello,
In the failover configuration can we use different IP address than the server
IP address itself so that Failover traffic is out-of-band
Example:
Both servers of a pair would have 10.0.0.1&10.0.0.2 as IP address for the real
DHCP traffic interface
While in the failover config primary and secondary IP would be
10.1.1.1&10.1.1.2 for failover link to work on a dedicated interface ?
Thanks
yves
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180122/446f4cd7/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 22 Jan 2018 09:17:29 -0500
From: Bill Shirley <b...@c3po.polymerindustries.biz>
To: dhcp-users@lists.isc.org
Subject: Re: Log Statement: How to log offered Lease Time?
Message-ID:
<1d3e067e-61bd-408d-f536-25183270f...@c3po.polymerindustries.biz>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
I use:
on commit {
? log (info, concat (
? ...
??? ,"? LeaseTime:", pick-first-value(binary-to-ascii(10, 32, "",
encode-int(lease-time, 32)), "(none)")
Bill
On 1/22/2018 6:14 AM, ift...@skynet.be wrote:
> Hello,
>
> I can see Discover,Offer,Request,Ack in my log
> What i am referring to is the detailed logging options that you can collect
> by using log statement
> ex: log ( info, concat( "MSGTYPE", binary-to-ascii (16,8,"^", option
> dhcp-message-type)));
>
> those seems only to work on Incoming DHCP messages (Discover, Request)
> but not on Outgoing Offer and Ack
>
> thanks
> yves
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180122/6ac976ab/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 22 Jan 2018 09:50:15 -0500
From: Bob Harold <rharo...@umich.edu>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Log Statement: How to log offered Lease Time?
Message-ID:
<ca+nkc8azny0hb8zjhp5mtt+ftm1bz5ajhjacnfqy6ksmwb4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Mon, Jan 22, 2018 at 9:17 AM, Bill Shirley <
b...@c3po.polymerindustries.biz> wrote:
> I use:
> on commit {
> log (info, concat (
> ...
> ," LeaseTime:", pick-first-value(binary-to-ascii(10, 32, "",
> encode-int(lease-time, 32)), "(none)")
>
> Bill
>
>
> On 1/22/2018 6:14 AM, ift...@skynet.be wrote:
>
> Hello,
>
> I can see Discover,Offer,Request,Ack in my log
> What i am referring to is the detailed logging options that you can collect
> by using log statement
> ex: log ( info, concat( "MSGTYPE", binary-to-ascii (16,8,"^", option
> dhcp-message-type)));
>
> those seems only to work on Incoming DHCP messages (Discover, Request)
> but not on Outgoing Offer and Ack
>
> thanks
> yves
>
>
In my experience that logs the "normal" lease time, not the actual lease
time, which can be lower due to failover MCLT settings or other
situations. There is no way to get the actual lease time that is being
sent, as far as I can tell. I would love for that to be fixed.
--
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180122/43fd6ab6/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 22 Jan 2018 09:55:02 -0500
From: Bob Harold <rharo...@umich.edu>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Log Statement: How to log offered Lease Time?
Message-ID:
<ca+nkc8bain2nbk+p_sqm+o2wbjj50tqfz7mgo-nzzpcldav...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Jan 22, 2018 9:50 AM, "Bob Harold" <rharo...@umich.edu> wrote:
On Mon, Jan 22, 2018 at 9:17 AM, Bill Shirley <bill@c3po.polymerindustries.b
iz> wrote:
> I use:
> on commit {
> log (info, concat (
> ...
> ," LeaseTime:", pick-first-value(binary-to-ascii(10, 32, "",
> encode-int(lease-time, 32)), "(none)")
>
> Bill
>
>
> On 1/22/2018 6:14 AM, ift...@skynet.be wrote:
>
> Hello,
>
> I can see Discover,Offer,Request,Ack in my log
> What i am referring to is the detailed logging options that you can collect
> by using log statement
> ex: log ( info, concat( "MSGTYPE", binary-to-ascii (16,8,"^", option
> dhcp-message-type)));
>
> those seems only to work on Incoming DHCP messages (Discover, Request)
> but not on Outgoing Offer and Ack
>
> thanks
> yves
>
>
In my experience that logs the "normal" lease time, not the actual lease
time, which can be lower due to failover MCLT settings or other
situations. There is no way to get the actual lease time that is being
sent, as far as I can tell. I would love for that to be fixed.
--
Bob Harold
Someday I hope to try this solution:
https://lists.isc.org/pipermail/dhcp-users/2007-May/003684.html
--
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180122/bce7dc55/attachment-0001.html>
------------------------------
Message: 5
Date: Mon, 22 Jan 2018 19:34:30 +0000
From: "Andrew Falanga (afalanga)" <afala...@micron.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: RE: [EXT] Re: Why is dhcpd not matching the MAC address as it
should
Message-ID: <d2a4f83bdcb142b292a976ad5778d...@bowex17f.micron.com>
Content-Type: text/plain; charset="us-ascii"
> -----Original Message-----
> From: dhcp-users [mailto:dhcp-users-boun...@lists.isc.org] On Behalf Of
> Simon Hobson
> Sent: Wednesday, January 17, 2018 2:35 PM
> To: Users of ISC DHCP <dhcp-users@lists.isc.org>
> Subject: [EXT] Re: Why is dhcpd not matching the MAC address as it should
>
> Andrew Falanga (afalanga) <afala...@micron.com> wrote:
>
> > class "controller" {
> > # tried matching based on two different styles I've seen on the net
> > #match if substring(hardware, 1, 3) = 00:a0:45;
> > match if (binary-to-ascii(16, 8, ":", substring(hardware, 0, 4)) =
> > "1:00:a0:45");
>
> This won't match, the string "1" (that you've used) will not match the string
> "01" (what binary-to-ascii will generate). Also you are comparing FIVE bytes
> from the MAC address to FOUR bytes in the string. What you should do is
> simply compare the binary values :
> match if substring(hardware, 0, 3) = 1:00:a0:45; or match if
> substring(hardware, 1, 3) = 00:a0:45; (as you've shown as an alternative
> above)
>
> Note: the leading "1" is the hardware type, 1 indicating Ethernet.
>
Simon (and others),
Thank you for the insights. I have at last figured out the recipe. I had to
change my pool declaration/definition to be
pool {
allow dynamic bootp clients;
allow members of "controller";
range dynamic-bootp 192.168.1.240;
}
I don't quite understand the reason why the server didn't figure out to allow
them when the range had the "optional" modifier "dynamic-bootp" but with adding
"allow dynamic bootp clients" to the pool definition, everything worked as it
should.
Thanks for the help and the insights. Especially, thank you for the
clarification that the binary-to-ascii function does return "both" 0's or
leading 0's.
Andy
------------------------------
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 111, Issue 27
*******************************************
