Score:0

Allow and deny class statements in isc-dhcp-server config

jp flag

When allowing one subnet to use a class, do you have to deny "all other subnets" explicitly. Or is it enough to just to allow the class on the subnets that should use that class, and all other are denied by default?

Explicit pseudo config below:

option space CISCO_PNP;
option CISCO_PNP.pnpserver code 43 = string;

# Bind dhcp subnet
subnet 192.168.1.0 netmask 255.255.255.0{
        range 192.168.1.40 192.168.1.40;
        option routers 192.168.1.1;
}

class "ciscopnp" {
  match if option vendor-class-identifier = "ciscopnp";
  option vendor-class-identifier "ciscopnp";
  vendor-option-space CISCO_PNP;
  option CISCO_PNP.pnpserver "5A1N;B2;I192.168.100.6;J80;K4";
}

# PnP
subnet 192.168.242.0 netmask 255.255.255.0 {
  range 192.168.242.2 192.168.242.30;
  option routers 192.168.242.1;
  allow members of "ciscopnp";
}


# No PnP
subnet 192.168.243.0 netmask 255.255.255.0 {
  range 192.168.243.2 192.168.243.30;
  option routers 192.168.243.1;
  deny members of "ciscopnp";
}

-- Regards Falk

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.