AW: Problems with Lots of Static DHCP Mappings
André Mamitzsch
a.mamitzsch at ccgmbh.de
Tue Oct 21 13:46:47 UTC 2003
What I can see in your config is that you have declared the range for
the static clients in the range statements. You should remove the
overlaps.=20
Old:
subnet 10.6.8.0 netmask 255.255.252.0 {
range 10.6.9.0 10.6.10.255;
option routers 10.6.8.1;
option broadcast-address 10.6.11.255;
}
New:
subnet 10.6.8.0 netmask 255.255.252.0 {
range 10.6.9.100(or whatever you like) 10.6.10.255;
option routers 10.6.8.1;
option broadcast-address 10.6.11.255;
}
After that, your static leases do not occur in the lease file anymore.
If you are having problems with moving clients from a dynamic (pool) to
a static lease, I recommend the "one-lease-per-client" statement. More
information can be found in man dhcpd.conf or man dhcp-eval.
A pool statement might be helpful as well:
pool
{
deny known clients;
range 10.6.9.1 10.6.9.255;
}
But,be aware: the "deny known clients" statement works globally and is
not bound to a shared network or subnet declaration !=20
Mit freundlichen Gr=FC=DFen,
Best regards,
Andr=E9 Mamitzsch
-----Urspr=FCngliche Nachricht-----
Von: dhcp-hackers-bounce at isc.org [mailto:dhcp-hackers-bounce at isc.org] Im
Auftrag von Neff_Glen at emc.com
Gesendet: Dienstag, 21. Oktober 2003 15:28
An: dhcp-hackers at isc.org; dhcp-server at isc.org
Betreff: RE: Problems with Lots of Static DHCP Mappings
> Seems like a small count to me if you were an ISP or campus assigning=20
> thousands of addresses through some kind of registration system.
Good. . . I'm glad to hear it's not extreme.
> Sounds like some kind of error in the config file is preventing the
statics
> from getting parsed. Are you seeing any errors reported in the log=20
> files?
Well, I provided a link to our config file:
www.trioptimum.com/~crtxreavr/dhcpd.conf
We're seeing no syntax complaints in the logs. In the past when we've
had typos, improperly formatted MAC addresses, and/or open {}s the
daemon immediately errors and terminates. That's not been the case with
our current config.
-G
More information about the dhcp-hackers
mailing list