Multiple class-matches

[Staffan.Ungsgard at teliasonera.com]

It seems that if a request matches more than one class, capabilities from either class may be honoured.
In the following example a lease limit of 4 is applied to a lease that matches the classes MainClass and AnothetClass1  - eventhough only MainClass is "allowed" in the pool definition.

Is this by design - i.e. is this something that could be considered "good practise" to augment leases ?



class "MainClass" {
match if ( substring (option vendor-class-identifier, 0, 4) = 00:01:02:03);
}

class "AnotherClass1" {
 match if ( substring (option agent.remote-id, 0, 3) = "xyz" );
 spawn with option agent.remote-id;
 lease limit 4;
}

class "AnotherClass2" {
 match if ( substring (option agent.remote-id, 0, 3) = "abc" );
 spawn with option agent.remote-id;
 lease limit 2;
}

....

shared-network xxx {


  subnet 100.64.7.0 netmask 255.255.255.0 {
      pool {
            allow members of "MainClass";
            range 100.64.7.2 100.64.7.254;
            option routers 100.64.7.1;
            option broadcast-address 100.64.7.255;
            option subnet-mask 255.255.255.0;
      }
  }

-- Staffan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20080827/c889796f/attachment.html>