Send dhcp-users mailing list submissions to
[email protected]
Advertising
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. ISC-DHCPD in a OmniOS zone (Michael Mounteney)
2. Peer holds all free leases on two subnets (Patrick Trapp)
----------------------------------------------------------------------
Message: 1
Date: Mon, 12 Oct 2015 18:18:48 +1000
From: Michael Mounteney <[email protected]>
To: [email protected]
Subject: ISC-DHCPD in a OmniOS zone
Message-ID: <20151012181848.5a417e6e@coomera>
Content-Type: text/plain; charset=US-ASCII
From: Michael Mounteney <[email protected]>
To: [email protected]
Subject: ISC-DHCPD in a OmniOS zone
Date: Sun, 11 Oct 2015 09:59:15 +1000
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; i686-pc-linux-gnu)
Organization: disorganisation
Hello, as per subject line, I'm trying to set up DHCPD within a zone,
which is somewhat like a BSD jail -- a shared-kernel isolated chrooted
execution environment.
The environment has three interfaces which it inherits from the 'real'
running OS environment:
root@diener:/root# ifconfig -a
lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
e1000g1:2: flags=1100943<UP,BROADCAST,RUNNING,PROMISC,MULTICAST,ROUTER,IPv4>
mtu 1500 index 2
inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
lo0:2: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
When I attempt to start isc-dhcpd:
root@diener:/root# /usr/sbin/dhcpd -cf /etc/dhcpd.conf -lf /var/db/dhcpd.leases
-f -d -p 67 -s 255.255.255.255 e1000g1:2 e1000g1
binding to user-specified port 67
Internet Systems Consortium DHCP Server 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Config file: /etc/dhcpd.conf
Database file: /var/db/dhcpd.leases
PID file: /var/run/dhcpd.pid
irs_resconf_load failed: 59.
Unable to set resolver from resolv.conf; startup continuing but DDNS support
may be affected
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 0 leases to leases file.
Error getting interface flags for 'lo0:2'; No such device or address
Error getting interface information.
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging..
exiting.
Obviously that third interface, the lo0:2 ipv6, is the problem but I
don't want the serve dhcpd on that interface anyway. As my dhcpd
command line indicates, I'm specifying the interface on which I want
dhcpd to listen, but it doesn't make any difference --- dhcpd still
attempts to look at the lo0 interface, fails, and bombs.
It doesn't matter what interfaces are given on the command line
(including none); the error is always the same.
Any ideas? Really it seems to be necessary to stop isc-dhcpd from
looking at that lo0 interface at all.
______________
Michael Mounteney
--
______________
Michael Mounteney
Landcroft Computing
------------------------------
Message: 2
Date: Mon, 12 Oct 2015 11:38:41 +0000
From: Patrick Trapp <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Peer holds all free leases on two subnets
Message-ID:
<1d507d610594d14f86d40d77c17e9e66263eb...@exchangedsb.ruralnex.com>
Content-Type: text/plain; charset="iso-8859-1"
OK, first of all, I'm sure I caused this one. (Usually, I don't realize it so
quickly, so that's progress, I guess.) I just don't know why it's happening.
Short form: I attempted to copy an include file to a new name to match our
standard naming convention. Since that point, the include in question fails to
work, returning "peer holds all free leases" from both servers of the failover
pair.
Long form: Our dhcp 'domain' includes a fairly high number of subnets spread
over a wide geographic area, so to make it relatively manageable, we use a lot
of include files - in most cases, each shared network has its own include to
make it easier for me to locate them and not have a huge conf file to wade
through. Some larger communities have multiple shared networks and I combine
them into a single include.
Last week, I was tasked with creating new dhcp scopes for a town with an
existing network. To be consistent with my other configurations, this requires
a new include file. Creating this file was no problem and (as far as I know)
all is fine - testing may not have started on it, though.
However, in the process of looking over the status quo to create that new file,
I realized that the include file for the existing network didn't meet our
naming standards and sought to remedy that fact. I didn't want to change the
existing file in case I needed to roll back, so I copied it to a new include
file and went into the dhcpd.conf where I added the new file and commented out
the old one. Ever since that time, the devices that should be served by the new
include are triggering "peer holds all free leases" errors on both servers. All
other pools are operating normally, as far as I can tell (the log is so full of
"peer holds" messages that is it hard to be certain). We have rolled back the
changes to the prior configuration without helping the situation. We have
restarted the service a number of times and rebooted both dhcp servers
completely once. I have stopped the secondary server and put the primary server
in partner-down in hopes that it would take over the entire
pool, but that doesn't appear to have made much difference.
I don't know why this caused this issue and more importantly, I don't know how
to recover. Ideas, suggestions, and criticism welcome. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20151012/48cd3937/attachment-0001.html>
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 84, Issue 6
*****************************************
