On 12. des. 2005, at 21.22, Peter Hessler wrote:

This is with -current dhcpd within the last month.

On Mon, 12 Dec 2005 12:15:37 -0800
Peter Hessler <[EMAIL PROTECTED]> wrote:

: I have a dhcp'd network, with static entries for a ton of machines.
: The problem is that the range is for .10 - .254, and the static
: entries are scattered throughout.  When a random client requests an
: address, dhcpd will give out a staticly defined entry.  So when the
: static entry machine comes back, the two machines fight each other
: for the address.
:
: Moving the static entries to outside the range is unfeasable right
: now. And it doesn't address the issue of 'machine was on a different
: dhcp network with an address that happens to be staticly defined on
: ours'.
:
: Why does dhcpd give out addresses that are currently in use, and why
: does it give out staticly defined addresses? Shouldn't it remove the
: static entries from the dynamic pool?
:
:
: Sanitized portions of config:
:
: shared-network LOCAL-NET {
:         option  domain-name "example.com";
:         option  domain-name-servers 10.0.0.1;
:
:         option  nis-domain "example.nis";
:         option  nis-servers nis.example.com;
:         option  ntp-servers ntp.example.com;
:         option  time-offset -28800;     # PST
:
:         subnet 10.0.0.0 netmask 255.255.255.0 {
:                 option routers 10.0.0.1;
:
:                 range 10.0.0.10 10.0.0.254;
:         }
:
:         group {
:           use-host-decl-names on;
:          # host1.example.com 10.0.0.15
:            host host1.example.com { hardware ethernet \
:              00:0f:1f:f7:7d:64; fixed-address host1.example.com; }
:          # host2.example.com 10.0.0.20
:           host host2.example.com { hardware ethernet \
:              02:A0:98:01:F5:B4; fixed-address host2.example.com; }
:          # host3.example.com 10.0.0.29
:           host host3.example.com { hardware ethernet \
:              00:0F:1F:F7:78:B6; fixed- address host3.example.com; }
:        }
: }
:


I believe OpenBSD's dhcpd is based on ISC's implementation, in which case: static entries are in the global scope and independent of any pool declaration. The error is one of configuration: you've defined static entries and dynamic pool overlapping = you've told it to use the IP addresses twice. At a pinch, the option ping-check, might help you out if your address space utilisation is not too large.

/Pete

Reply via email to