client class parameters inside subnet decl?

[Glenn Satchell]

As you've seen, redefining the class doesn't work as you expect. There's a
couple of ways around this.

Either use an if() clause in the initial class definition to have the
different options

Or, better I think, is to override the values in the pool. The permit
means that only members of the class Alcatel-Lucent_IPSip will match, but
you can have another pool in the same subnet with a deny members of
Alcatel-Lucent_IPSip for any other devices if needed. Similarly for the
other subnet.

So your definition below becomes:

   subnet 10.2.44.0 netmask 255.255.255.0 {
           option routers 10.2.44.1;
           pool {
                   range 10.2.44.50 10.2.44.60;
                   allow members of "Alcatel-Lucent_IPSip";
                   next-server 10.2.28.12;
                   option vendor-encapsulated-options 3a:02:00:12:ff;
           }
   }

regards,
-glenn

On Sat, August 20, 2016 8:50 am, Václav Ovsík wrote:
> Hi,
> I have doubts about correctness of the following configuration:
>
>
>   class "Alcatel-Lucent_IPSip" {
>           match if option vendor-class-identifier = "alcatel.ictouch.0"
>                   or  option vendor-class-identifier = "ictouche.class0";
>   }
>
>   subnet 10.2.44.0 netmask 255.255.255.0 {
>           option routers 10.2.44.1;
>           pool {
>                   range 10.2.44.50 10.2.44.60;
>
>                   class "Alcatel-Lucent_IPSip" {
>                           next-server 10.2.28.12;
>                           option vendor-encapsulated-options
> 3a:02:00:12:ff;
>                   }
>           }
>   }
>
>   subnet 10.2.255.0 netmask 255.255.255.0 {
>           option routers 10.2.255.1;
>           pool {
>                   range 10.2.255.50 10.2.255.60;
>
>                   class "Alcatel-Lucent_IPSip" {
>                           next-server 10.2.28.34;
>                           option vendor-encapsulated-options
> 3a:02:00:34:ff;
>                   }
>           }
>   }
>
>
> My idea was to change parameters for IP phones, Wifi AP etc based on
> subnet.
> This is simplified configuration already. Subnet 10.2.255.0/24 is not real
> in
> this test environment. Only DHCP server 10.2.44.8 and one dhclient was
> present
> on subnet 10.2.44.0/24.
>
> The result is:
>
>     TIME: 2016-08-20 00:04:09.032
>       IP: 10.2.44.8 (52:54:0:d4:b1:14) > 10.2.44.50 (52:54:0:fe:1b:2a)
>       OP: 2 (BOOTPREPLY)
>    HTYPE: 1 (Ethernet)
>     HLEN: 6
>     HOPS: 0
>      XID: f8a26116
>     SECS: 0
>    FLAGS: 0
>   CIADDR: 10.2.44.50
>   YIADDR: 10.2.44.50
>   SIADDR: 10.2.28.34
>   GIADDR: 0.0.0.0
>   CHADDR: 52:54:00:fe:1b:2a:00:00:00:00:00:00:00:00:00:00
>    SNAME: .
>    FNAME: .
>   OPTION:  53 (  1) DHCP message type         5 (DHCPACK)
>   OPTION:  54 (  4) Server identifier         10.2.44.8
>   OPTION:  51 (  4) IP address leasetime      600 (10m)
>   OPTION:   1 (  4) Subnet mask               255.255.255.0
>   OPTION:   3 (  4) Routers                   10.2.44.1
>   OPTION:  15 (  8) Domainname                plz.i.cz
>   OPTION:   6 ( 12) DNS server
> 10.2.28.100,10.2.28.101,192.168.24.10
>   OPTION: 119 ( 12) Domain Search             03706c7a01690263 .plz.i.c
>   					      7a00c004         z...
>   OPTION:  44 (  8) NetBIOS name server       10.0.156.141,10.0.156.142
>   OPTION:  42 (  8) NTP servers               10.2.28.110,10.2.28.111
>   OPTION:  43 (  5) Vendor specific info      3a020034ff       :..4.
>   ---------------------------------------------------------------------------
>
> SIADDR (next-server) and option 43 coresspond to subnet 10.2.255.0, but
> dhclient was on 10.2.44.0 :(.
> I hoped it should be 10.2.28.12 and 3a020012ff (voice vlan).
> ISC DHCP is running on Debian stable - 4.3.1-6+deb8u2.
>
> What is the proper way to specify parameters for class members in
> subnet please?
>
> Regards
> --
> Zito
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>