How does DHCPD determine what IP address to assign and...

Ryan McCain Ryan.McCain at dss.state.la.us
Wed Jan 2 20:01:03 UTC 2008


>>> On Sat, Dec 29, 2007 at  9:41 AM, in message
<20071229154059.CTZI3980.fep50.mail.dk at post.tele.dk>, Lars Jacobsen
<lars-jacobsen at newmail.dk> wrote: 
> Well as Simon posted earlier you need af deny statement in every
other
> pool you dont want "DialUp" members to access, like:
> 
> #DSS - Cisco VPN
> deny members of "DialUp";
> subnet 10.116.6.0 netmask 255.255.255.0 {
> range 10.116.6.9 10.116.6.179 ;
> option routers 10.116.6.254;
> }
> 
> 
> And from you lease file i can se there has been no match to class
"DialUp" 
> yet, as its not listed/log*d. 
> So even with the above deny statement it probadly still wont work.
> Class matching can be quite tricky - se my story 
> http://www.strammelse.dk/dhcp/
> 
> 
> Regards
> Lars

I'm back at it again.  The DHCP client connect with Async in the UID
string and was assigned the IP address of 10.116.6.179 which was the
first available address in the subnet I am trying to prevent the client
from grabbing an IP address from.  I'm banging me head against the wall
over here..

-SNIP-

class "DialUp" {
    match if (substring(suffix(dhcp-client-identifier,7),0,5)="Async")

                   or
                 
(substring(suffix(dhcp-client-identifier,6),0,5)="Async") ; 
            log (info, " Matched Dialup Rule");
                        }
}

-SNIP-

#DialUp
subnet 10.116.6.0 netmask 255.255.255.0 {
 pool {
  allow members of "DialUp";
  range 10.116.6.1 10.116.6.8;
  option routers 10.116.6.1;
      }
}

-SNIP-

#VPN 
  subnet 10.116.6.0 netmask 255.255.255.0 {
pool {  
  deny members of "DialUp";  
  range 10.116.6.1 10.116.6.179 ;
  option routers 10.116.6.254 ;
     }
}


... What am I doing wrong?



More information about the dhcp-users mailing list