dhcpd.conf logical hierachy

[Bob Harold]

On Wed, Oct 18, 2017 at 3:19 PM, Narcis Garcia <informatica at actiu.net>
wrote:

> Any way I define the static pool, error messages occur.
>

Maybe there a confusion in the words "static pool"
"pool" and "range" are used to define dynamic ranges.
"fixed-address" defines a static assignment.


> This is the only configuration I've reached without errors when a known
> host connects, but I might not be defining subnet/interface where static
> cases are attached to:
>
> subnet 172.16.0.0 netmask 255.255.0.0 {
>         option subnet-mask 255.255.0.0;
>         option routers 172.16.20.100;
>         option broadcast-address 172.16.255.255;
>         option domain-name-servers 172.16.21.61;
>         pool {
>                 # IP range to be assigned dynamically
>                 range 172.16.20.150 172.16.20.189;
>                 allow unknown-clients;
>         }
> }
> group MyReservations {
>

These four lines are redundant and should be removed:

>         option subnet-mask 255.255.0.0;
>         option routers 172.16.20.100;
>         option broadcast-address 172.16.255.255;
>         option domain-name-servers 172.16.21.61;
>
Delete the four lines above.


>         host printer_1 {
>                 hardware ethernet 00:11:22:33:44:55;
>                 fixed-address 172.16.20.201;
>         }
> }
>
>
That looks good.  If you need a larger range, just remeber that the dynamic
range and static fixed-addresses should no overlap.  So ranges like:
    range 172.16.20.190 172.16.20.200;
    range 172.16.20.202 172.16.20.255;

As others have said.

-- 
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20171018/1dfa6322/attachment.html>