Send dhcp-users mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: DHCPv6 and on_commit etc events (perl-list)
2. [Bug Report] key conflict message for create host by Omapi
(Clodoaldo de Borba Lambiase)
3. Re: [Bug Report] key conflict message for create host by
(Clodoaldo de Borba Lambiase)
4. Re: [Bug Report] key conflict message for create host by
OMAPI (Steve van der Burg)
5. some problems with classes (Andreas Burger)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 Nov 2015 08:51:23 -0500 (EST)
From: perl-list <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCPv6 and on_commit etc events
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=utf-8
Any one know anything about this?
> ISC DHCP version: 4.3.3
> I need some help in finding information about what sort of options are
> available
> in in on_ events in DHCPv6. I can't seem to find any man pages or so on that
> describe what can be logged with these events (on commit, on expiry, on
> release). I have things being logged for DHCPv4 like so:
> on commit {
> log( error,
> concat( "LEASED,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address),",",
> "time,",binary-to-ascii(10,32,"",encode-int (lease-time,32)),",",
> "hardware,",binary-to-ascii(16,8,":",substring(hardware,1,7))
> )
> );
> }
> on expiry {
> log( error,
> concat( "LEASEEXPIRY,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address)
> )
> );
> }
> on release {
> log( error,
> concat( "RELEASED,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address),",",
> "hardware,",binary-to-ascii(16,8,":",substring(hardware,1,7))
> )
> );
> }
> Would like to do something similar in DHCPv6. Have begun testing with on
> commit.
> Apparently the same sorts of data are not available as the same on commit { }
> directive from above produces these log messages:
> Oct 30 13:58:45 DHCPserver dhcpd: data: "leased-address" configuration
> directive: there is no lease associated with this client.
> Oct 30 13:58:45 DHCPserver dhcpd: data: leased_lease: not available
> Oct 30 13:58:45 DHCPserver dhcpd: data: hardware: no raw packet or lease is
> available
> I realize the hardware address is probably not available as these packets are
> being relayed from a router that does not support RFC 6939 (are there any that
> do?).
> Mainly, I'd like to see a man page or some sort of document that describes
> what
> IS available ... or some config I could drop in my dhcpd.conf that would log
> what is available or something... any ideas?
----- Original Message -----
> From: "Darren Ankney" <[email protected]>
> To: "Users of ISC DHCP" <[email protected]>
> Sent: Friday, October 30, 2015 10:15:52 AM
> Subject: DHCPv6 and on_commit etc events
> ISC DHCP version: 4.3.3
> I need some help in finding information about what sort of options are
> available
> in in on_ events in DHCPv6. I can't seem to find any man pages or so on that
> describe what can be logged with these events (on commit, on expiry, on
> release). I have things being logged for DHCPv4 like so:
> on commit {
> log( error,
> concat( "LEASED,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address),",",
> "time,",binary-to-ascii(10,32,"",encode-int (lease-time,32)),",",
> "hardware,",binary-to-ascii(16,8,":",substring(hardware,1,7))
> )
> );
> }
> on expiry {
> log( error,
> concat( "LEASEEXPIRY,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address)
> )
> );
> }
> on release {
> log( error,
> concat( "RELEASED,",
> "ip,", binary-to-ascii (10, 8, ".", leased-address),",",
> "hardware,",binary-to-ascii(16,8,":",substring(hardware,1,7))
> )
> );
> }
> Would like to do something similar in DHCPv6. Have begun testing with on
> commit.
> Apparently the same sorts of data are not available as the same on commit { }
> directive from above produces these log messages:
> Oct 30 13:58:45 DHCPserver dhcpd: data: "leased-address" configuration
> directive: there is no lease associated with this client.
> Oct 30 13:58:45 DHCPserver dhcpd: data: leased_lease: not available
> Oct 30 13:58:45 DHCPserver dhcpd: data: hardware: no raw packet or lease is
> available
> I realize the hardware address is probably not available as these packets are
> being relayed from a router that does not support RFC 6939 (are there any that
> do?).
> Mainly, I'd like to see a man page or some sort of document that describes
> what
> IS available ... or some config I could drop in my dhcpd.conf that would log
> what is available or something... any ideas?
------------------------------
Message: 2
Date: Tue, 3 Nov 2015 19:25:46 +0000
From: Clodoaldo de Borba Lambiase <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Bug Report] key conflict message for create host by Omapi
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi,
I already have tested two differents IP entries for the same MAC address in
dhcpd.conf. It works fine and it proves that ISC DHCP supports this behaviour.
However, two omapi entries with the same MAC address, even if the IPs are in
different networks, doesn't work (like I have described at the first topic).
Main problem is the distinct behaviour applied by ISC-DHCP to 'host' entries by
omapi or by dhcpd.conf. I think the result should be the same for both cases.
------------------------------
Message: 3
Date: Tue, 3 Nov 2015 19:34:09 +0000
From: Clodoaldo de Borba Lambiase <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [Bug Report] key conflict message for create host by
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
The problem addressed is another. We are not expecting different devices in
different subnets that have the same MAC address. What we want to support is
registration of devices, so they can go from a network to another network and
use fixed addresses. So, we need host entries with the same MAC address in
different subnets.
Also, ARP resolution is not a problem, because we use servers with DHCP relay.
The server is not in the same broadcast domain of the client.
------------------------------
Message: 4
Date: Tue, 03 Nov 2015 15:14:07 -0500
From: "Steve van der Burg" <[email protected]>
To: "Users of ISC DHCP" <[email protected]>
Subject: Re: [Bug Report] key conflict message for create host by
OMAPI
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII
Clodoaldo de Borba Lambiase <[email protected]> wrote:
> The problem addressed is another. We are not expecting different devices in
> different subnets that have the same MAC address. What we want to support is
> registration of devices, so they can go from a network to another network and
> use fixed addresses. So, we need host entries with the same MAC address in
> different subnets.
Why are you assuming that this is done by creating multiple host definitions
for the same MAC?
Do you mean that you need to be able to add something like this via OMAPI?
host ec-ff-cc-52-55-f1 {
dynamic;
hardware ethernet ee:ff:cc:52:55:f1;
fixed-address 10.179.48.34,10.179.49.34,10.179.50.34,10.179.51.34;
}
I add, modify and delete host containers on my DHCP servers with omshell and
expect, and a little perl code to control it all. When I first needed to
specify multiple fixed addresses for a MAC, I ran into a limitation of either
omshell or OMAPI. Here's how I solved it:
# Deal with multiple IP addresses for the omshell "set ip-address" command:
#
# Multiple addresses can come in either as an array ref or packed in a string,
separated by commas.
#
# To keep things simple, we treat single addresses as if they were multiple,
and convert them also.
# We convert the addresses to hex, joined with ":", and then pass them back to
the caller.
# This is because omshell can do
# set ip-address=10.11.12.13
# for setting one address in a host container, but needs to do
# set ip-address=0a:0b:70:f0:0a:88:4c:f0
# to set more than one (two here).
#
sub make_ipstr {
my $in = shift;
if ( ref($in) ne 'ARRAY' ) {
my @ipa = split(/,/,$in);
$in = \@ipa;
}
my @ho;
foreach my $ipa ( @$in ) {
my @oc = split(/\./,$ipa);
push @ho,sprintf("%2.2x",$_) foreach @oc;
}
return join(":",@ho);
}
...Steve
--
Steve van der Burg
Information Technology Services
London Health Sciences Centre
& St. Joseph's Health Care London
(519) 685-8500 ext 35559
[email protected]
--------------------------------------------------------------------------------
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.
------------------------------
Message: 5
Date: Wed, 4 Nov 2015 11:03:35 +0100
From: Andreas Burger <[email protected]>
To: "[email protected]" <[email protected]>
Subject: some problems with classes
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
hi there,
i got some good hints to my last questin, but i ran in problems.
what i have:
multiple subnets in more then one logical sets.
clients get ips from dhcp but fixed by mac-address, when they are at the
normal place.
if they show up somewhere else, they should get an ip from a range, but
only if they belong to the same logical set.
so i tried:
(part from dhcpd.conf)
class "agrl" {
}
...
subnet xxxx netmask 2xxx {
option subnet-mask xxx0;
option routers xxx;
option time-servers xxx;
get-lease-hostnames on;
use-host-decl-names on;
pool {
failover peer "hest-dhcp";
allow mebers of "agrl";
deny unknown clients;
range xy xz;
}
}
....
subclass "agrl" 1:10:9a:dd:5a:5d:c4;
host em132-88 { hardware ethernet 10:9a:dd:5a:5d:c4; fixed-address xx;... }
first i had the subclass after the hostdefinition, and that did not
work, as the host-definition fits and the file is not parsed longer.
now i can see, that hosts not part of "agrl" do not get an ip, as wanted.
BUT. it seems, as the hosts became ips from the pool instead of their ip
in the host-statement.
any hints?
regards
andreas
--
________________________________________________
Andreas Burger
Eidgenoessische Technische Hochschule Zuerich
Departement Hest ISG
LFV E31 8092 Zuerich +41 44 632 68 54
[email protected]
_________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3943 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20151104/3ea41014/attachment-0001.bin>
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 85, Issue 2
*****************************************
