Re: include in pool

Hello,
Any idea / tip ?
Regards

Le mer. 10 nov. 2021 à 14:37, BASSAGET Cédric <[email protected]>
a écrit :

> Too be more clear, here's my dhcpd.conf file and includes :
>
> FILE dhcpd.conf :
> include "/etc/dhcp/dhcpd_voip.conf";
> subnet 192.168.2.0 netmask 255.255.255.0 {
>     option routers 192.168.2.1;
>     pool {
>         range 192.168.2.100 192.168.2.200;
>         include "allowed-members.include";
>     }
> }
>
> ################
> FILE allowed-members.include :
> .....
> allow members of "Aastra6730i";
> allow members of "Aastra6731i";
> allow members of "Aastra6739i";
> allow members of "Aastra6751i";
> .....
> ################
> FILE dhcpd_voip.conf :
> contains include of classes :
> include "/etc/dhcp/dhcpd_voip/aastra.conf"
> ....
> ################
> FILE /etc/dhcp/dhcpd_voip/aastra.conf :
> .....
> class "Aastra6730i" {
>     match if option vendor-class-identifier = "AastraIPPhone6730i";
>     log(concat("[", binary-to-ascii(16, 8, ":", hardware), "] ", "BOOT
> Aastra 6730i"));
>     option tftp-server-name = concat(config-option VOIP.http-server-uri,
> "/tftpboot/");
> }
> class "Aastra6757i" {
>      ...
> }
> .....
> ################
>
> The error I get with this config is :
>
> allowed-members.include line 6: expecting allow/deny key
> allow members
>        ^
> allowed-members.include line 6: expecting a parameter or declaration
> allow members of "Aastra6731i";
>                               ^
> allowed-members.include line 8: expecting allow/deny key
> allow members
>        ^
> allowed-members.include line 8: expecting a parameter or declaration
> allow members of "Aastra6751i";
>                               ^
>
>
> I get one error per class
> Regards,
> Cédric
>
>
>
> Le mer. 10 nov. 2021 à 14:23, BASSAGET Cédric <
> [email protected]> a écrit :
>
>> Hi Peter,
>> the include line in your example is commented. I think you will get an
>> error if you un-comment it :)
>> Regards
>> Cédric
>>
>> Le mar. 9 nov. 2021 à 15:36, Peter Davies <
>> [email protected]> a écrit :
>>
>>> Hi Cèdric,
>>>    Have you tried having each shared-network/subnet in its own include
>>> file.
>>> Then include a file with "members of" statements within that?
>>> ie:
>>> dhcpd.conf:
>>>          class "allocation-class-1" {
>>>          match pick-first-value (option dhcp-client-identifier, hardware)
>>> ;
>>>        }
>>>
>>>        class "allocation-class-2" {
>>>          match pick-first-value (option dhcp-client-identifier, hardware)
>>> ;
>>>        }
>>>
>>>         allow members of "allocation-class-1";
>>>         allow members of "allocation-class-1";
>>>
>>>        class "allocation-class-1" {
>>>          match pick-first-value (option dhcp-client-identifier, hardware)
>>> ;
>>>        }
>>>
>>>        class "allocation-class-2" {
>>>          match pick-first-value (option dhcp-client-identifier, hardware)
>>> ;
>>>        }
>>>        subclass "allocation-class-1" 1:8:0:2b:4c:39:ad;
>>>        subclass "allocation-class-2" 1:8:0:2b:a9:cc:e3;
>>>        subclass "allocation-class-1" 1:0:0:c4:aa:29:44;
>>>
>>>       include "subnet-1.include";
>>> ...
>>>
>>> subnet-1.include:
>>> shared-network "SN1" {
>>>   subnet 10.0.0.0 netmask 255.255.255.0 {
>>>     option routers 10.0.0.1;
>>>     pool {
>>>            #include "access-1.include";
>>>            range 10.0.0.10 10.0.0.254; } }
>>> }
>>>
>>> access-2.include:
>>> allow members of "allocation-class-1";
>>> allow members of "allocation-class-2";
>>>
>>> This appears to work
>>>
>>> Kind Regards Peter
>>>
>>>
>>> ------------------------------
>>> *From:* dhcp-users <[email protected]> on behalf of
>>> BASSAGET Cédric <[email protected]>
>>> *Sent:* 09 November 2021 09:21
>>> *To:* [email protected] <[email protected]>
>>> *Subject:* include in pool
>>>
>>> Hello.
>>> I have to configure a dhcp server wich will act as master for dozens of
>>> relays.
>>> My basic pool config includes a lot of "allow members of" statements,
>>> like this :
>>>
>>>
>>> subnet 192.168.2.0 netmask 255.255.255.0 {
>>>     option routers 192.168.2.1;
>>>     #option domain-name-servers 192.168.2.1;
>>>     #option bootfile-name = "snom821.htm";
>>>     pool {
>>>         range 192.168.2.100 192.168.2.200;
>>>         ### Assign who is going to use this pool
>>>         allow members of "voip-mac-address-prefix";
>>>         # allow localhost for NRPE
>>>         # allow members of "localhost";
>>>         # Aastra
>>>         allow members of "Aastra6730i";
>>>         allow members of "Aastra6731i";
>>>         allow members of "Aastra6739i";
>>>         allow members of "Aastra6751i";
>>>         allow members of "Aastra6753i";
>>>         allow members of "Aastra6755i";
>>>         allow members of "Aastra6757i";
>>>         # Snom
>>>         allow members of "Snom300";
>>>         allow members of "Snom320";
>>>         allow members of "Snom360";
>>>         allow members of "Snom370";
>>>         allow members of "Snom820";
>>>        ....
>>>      }
>>> }
>>>
>>> As I have to create dozens of pools, I tried to put all these "allow
>>> members of ..." in a file called "allowed_members.include", and replace my
>>> pool def by :
>>>
>>> subnet 192.168.2.0 netmask 255.255.255.0 {
>>>     option routers 192.168.2.1;
>>>     pool {
>>>         include "path/to/allowed_members.include";
>>>     }
>>> }
>>>
>>>
>>> but it does not work, it throws a config error when testing config.
>>>
>>> So my questions are :
>>> - is there a way to do an "include" inside a pool ?
>>> - is there another way to declare multiple pools for each relay ? (all
>>> relays will have the same config)
>>>
>>> The aim of this is to have a small and comprehensible dhcpd.conf file.
>>>
>>>
>>> Regards,
>>> Cédric
>>>
>>> _______________________________________________
>>> ISC funds the development of this software with paid support
>>> subscriptions. Contact us at https://www.isc.org/contact/ for more
>>> information.
>>>
>>> dhcp-users mailing list
>>> [email protected]
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>>

_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users