| 1 |
# $Id$ |
| 2 |
|
| 3 |
* Design notes for NCAP filter specifications |
| 4 |
|
| 5 |
Generally, a filter specification is a sequence of filters, each being |
| 6 |
introduced by its family name and containing one or more family-specific |
| 7 |
rules. The point isn't to duplicate what BPF can do, but rather to make |
| 8 |
it unnecessary to think in BPF. NCAP filter specifications are application |
| 9 |
specific, and filter can internally generate BPF to save on context switches. |
| 10 |
|
| 11 |
* Filter Family: "dns" |
| 12 |
|
| 13 |
regex[=#]RE/opts |
| 14 |
regex must match (or not) the presentation form of a message, with |
| 15 |
options like "i" for ignore-case |
| 16 |
|
| 17 |
initiator[=#]address[,...] |
| 18 |
message initiator must be (or not) on this list |
| 19 |
|
| 20 |
target[=#]address[,...] |
| 21 |
message target must be (or not) on this list |
| 22 |
|
| 23 |
flags[=#]tc,aa,ra,rd,qr |
| 24 |
these message flags must be set (or unset) |
| 25 |
|
| 26 |
rcode[=#]noerror,formerr,servfail,nxdomain,notimpl,refused |
| 27 |
these message response codes are wanted (or unwanted) |
| 28 |
(note, they are only checked on responses, not initiations) |
| 29 |
|
| 30 |
opcode[=#]query,update,notify |
| 31 |
these message opcodes are wanted (or unwanted) |
| 32 |
|
| 33 |
qname=name |
| 34 |
query name must match name |
| 35 |
|
| 36 |
qtype=rrtype |
| 37 |
query type must match rrtype |
| 38 |
|
| 39 |
* Filter Family: "icmp" |
| 40 |
|
| 41 |
type[=#]echoreply,unreach,sourcequench,redirect,echorequest,routeradvert |
| 42 |
type[=#]routersolicit,timxceed,paramproblem,tstamprequest,tstampreply, |
| 43 |
type[=#]inforeq,inforeply,maskreq,maskreply,traceroute |
| 44 |
these icmp types are wanted (or unwanted) |
| 45 |
|
| 46 |
type[=#]<type> |
| 47 |
where <type> is an integer in the range 0..255 |
| 48 |
this icmp type is wanted (or unwanted) |
| 49 |
|
| 50 |
code[=#]<code> |
| 51 |
where <code> is an integer in the range 0..255 |
| 52 |
this icmp code is wanted (or unwanted) |