To add some filter rules in conf file

Ashmath Khan hashmat.email at gmail.com
Tue Oct 20 13:10:37 UTC 2009


Thanks Jeff.

Well, actually I was thinking more along the lines of the following (my
> apologies if I've mangled the syntax, just trying to illustrate a point
> here):
>
> class "red" {
>        match if (option color = "red");
> }
>
> class "fat" {
>        match if (option color != "red") && (option weight = "fat");
> }
>
> class "tall" {
>        match if (option color != "red") && (option weight != "fat") &&
> (option height = "tall");
> }
>
> class "cold" {
>        match if (option color != "red") && (option weight != "fat") &&
> (option height != "tall");
> }
>
>        ...
>        pool {
>                range 10.0.0.1 10.0.0.254;
>                allow members of "red";
>        }
>        pool {
>                range 10.0.1.1 10.0.1.254;
>                allow members of "fat";
>        }
>        pool {
>                range 10.0.2.1 10.0.2.254;
>                allow members of "tall";
>        }
>        pool {
>                range 10.0.3.1 10.0.3.254:
>                allow members of "cold";
>        }
>        ...
>
> No variables required, I think.
>

How do I choose a pool say if option height is absent ? I would have to use
deny etc
I think I can't achieve this because I have to choose pool sometimes when
there is no match(option is absent).  Or sometimes I have to discard a
client if a match is found etc.
Like for example:
rule 1 type dhcp-option
rule 1 dhcp-option 60
rule 1 match-str "*VIP*"
rule 1 match-action discard
rule 1 absent-action continue
rule 2 type dhcp-option
rule 2 dhcp-option 60
rule 2 match-str "*"
rule 2 match-action pass
rule 2 match-pool 192.168.1.100
rule 2 match-option-group ""
rule 2 absent-action continue
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20091020/0fe4c1d4/attachment.html>


More information about the dhcp-users mailing list