Re: include in pool

BASSAGET Cédric <[email protected]>
Newsgroups gmane.network.dhcp.isc.dhcp-server
Message-ID <CAN+OZjSRfgSC067tuLM+nqWAu0wyjiTy6PtTjpSetGnyY2H69g@mail.gmail.com>
Hi Simon,
class are already defined, can't change that. but maybe I can create a
"master" class which will group all subclasses ?

all my classes are defined like this :

class "Alcatel-SIP" {
    match if option vendor-class-identifier = "alcatel.sip.0";

    vendor-option-space ALU;
    option ALU.http-server-name = config-option VOIP.http-server-uri;
    log(concat("[", binary-to-ascii(16, 8, ":", hardware), "] ", "BOOT
Alcatel SIP"));
}
Regards
Cédric

Le mar. 9 nov. 2021 à 19:42, Simon Hobson <[email protected]> a écrit :

>
>
> > On 9 Nov 2021, at 08:21, BASSAGET Cédric <[email protected]>
> wrote:
> >
> > 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";
> >        ....
> >      }
> > }
>
> Do you need to define the classes separately ? If not, then you could
> simplify things a lot :
>     pool {
>         range 192.168.2.100 192.168.2.200;
>         allow members of "Aastra";
>         allow members of "Snom";
>        ....
>      }
>
> Simon
>
> _______________________________________________
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.