dhcpd.conf logical hierachy

Narcis Garcia informatica at actiu.net
Thu Oct 19 07:36:23 UTC 2017


subnet 172.16.0.0 netmask 255.255.0.0 { # For eth0=172.16.20.100
        ...
        pool {
                range 172.16.20.150 172.16.20.189;
                allow unknown-clients;
        }
}
subnet 192.168.2.0 netmask 255.255.255.0 { # For eth0=172.16.20.100
        ...
        pool {
                range 192.168.2.3 192.168.2.199;
                allow unknown-clients;
        }
}
host printer_1 {
        hardware ethernet 00:11:22:33:44:55;
        fixed-address 172.16.20.201;
}
host printer_2 {
        hardware ethernet 22:33:44:55:66:77;
        fixed-address 192.168.2.220;
}


El 19/10/17 a les 09:19, Bill Shirley ha escrit:
> Why do you think you need to link the group to the subnet?  The
> fixed-address
> of printer-1 ties it to the subnet.
> 
> For your 2nd question, add the subnets and hosts to dhcpd.conf. What
> problem
> are you thinking about?
> 
> Bill
> 
> On 10/19/2017 2:52 AM, Narcis Garcia wrote:
>> How do I explicitly link the group MyReservations to that subnet and its
>> options?
>> What if some day I want to setup other subnets and other fixed hosts?
>>
>>
>> El 18/10/17 a les 21:33, Bob Harold ha escrit:
>>> On Wed, Oct 18, 2017 at 3:19 PM, Narcis Garcia <informatica at actiu.net
>>> <mailto: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
>>>
>>>
>>>
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
> 
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users


More information about the dhcp-users mailing list