dhcpd - range parameter

UNIX for Advanced & Expert Users
1

Hi All,

I'm curious about what this community would think about this portion of a dhcpd.conf file:

subnet 192.168.1.0 netmask 255.255.255.0 {
...
...other parameters/options...
...
range 192.168.1.3 192.168.1.253
range 172.16.0.2 172.16.0.50
}

I tested this and dhcpd did not barf when I put it in. It seems odd that it would allow a range outside of the subnet scope. Anyone use this technique or have experience with it?

Thanks

2

(post deleted, srry)

3

There is nothing wrong with dhcp accepting it, you can use it in conjunction with some allow/disallow classes settings ie:

class "allowed-LAN"  { match hardware; }
subclass "allowed-LAN" 1:00:14:BF:E8:75:EE; 
subclass "allowed-LAN"  1:00:30:E2:29:E7:DB;
subnet 192.168.1.0 netmask 255.255.255.0 {
  option routers 192.168.1.1;
  option subnet-mask 255.255.255.0;
  pool {
    range 192.168.1.2 192.168.1.10;
    option domain-name-servers 62.157.101.211, 217.146.139.5, 208.67.222.222, 2
08.67.220.220;  # orsn.net / OpenDNS.com
    option domain-name "allowed-lan";
    ddns-domainname "allowed-lan";
    default-lease-time 345600;
    max-lease-time 691200;
    allow members of "allowed-LAN";
  }
  pool {
    range 172.16.0.12 172.16.0.32;
    option domain-name-servers 192.168.1.1;
    option domain-name "denied-lan";
    ddns-domainname "denied-lan";
    deny members of "allowed-LAN";
    default-lease-time 600;
    max-lease-time 7200;
  }
}

So you're capable of controling whatever others that are not allowed in your net of how they get routed without making alot of jumps through hoops.