DHCPD classes - How to put unknown devices in a separate class?

[Randall C Grimshaw]

The remaining systems will inherit the defaults from the global scope. Otherwise (Without taking the time to code this) I will just toss out this idea: you might add the recognized devices to a membership as you go - leaving the rest as non members. 

-----Original Message-----
From: dhcp-users-bounces+rgrimsha=syr.edu at lists.isc.org [mailto:dhcp-users-bounces+rgrimsha=syr.edu at lists.isc.org] On Behalf Of Jessica Meyer
Sent: Tuesday, March 23, 2010 4:25 AM
To: Users of ISC DHCP
Subject: DHCPD classes - How to put unknown devices in a separate class?

Hi list

I'm stuck with DHCPD classes. I need to classify all requests
according to the vendor-class-identifier. I have two classes and it
works fine. Now what I need (and haven't found yet) is to put all
_other_ devices in a third class. So, if a device doesn't belong to
class A or B, put it in C. I have played with "match if" statements
but haven't had any success.

My classes are:

class "Devices_A" {
    match if ( substring ( option vendor-class-identifier, 0, 6 ) = "vendor1" );
    log ( info, "Got a packet from a vendor1 device" );
}

class "Devices_B" {
    match if ( substring ( option vendor-class-identifier, 0, 6 ) = "vendor2" );
    log ( info, "Got a packet from a vendor2 device" );
}

Can i somehow test if a request doesn't belong to Devices_A or
Devices_B? Any help is highly appreciated!
Jess
_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users