Bird is configured using text configuration file. At startup, bird reads bird.conf (unless -c command line parameter is given). Really simple configuration file might look like this: @@ -68,7 +68,11 @@ protocol rip { two objects in this language: filters and functions. Filters are called by bird core when route is being passed between protocol and main routing table, and filters may call functions. Functions may call other functions but recursion is not allowed. Filter language contains control structures such -as if's and switches, but it allows no loops. Filters are interpretted. +as if's and switches, but it allows no loops. Filters are +interpretted. Filter using many features can be found in filter/test.conf. + +
There's one strange thing with filter language: it does not permit you to create loops. There's +no equivalent of while() or for() command, and recursive functions are not permitted.
You can find sources of filters language in filter/ directory. filter/config.Y contains filter gramar, and basically translates source from user into @@ -145,7 +149,9 @@ booleans (that is to prevent you from shooting in the foot). but you can not modify them. Constant of type set int looks like [ 1, 2, 5..7 ]. As you can see, both simple values and ranges are permitted in sets. Sets of prefixes are special: you can specify which prefixes should match them by - using [ 1.0.0.0/8+, 2.0.0.0/8-, 3.0.0.0/8{5,6} ]. + using [ 1.0.0.0/8+, 2.0.0.0/8-, 3.0.0.0/8{5,6} ]. 3.0.0.0/8{5,6} matches + prefixes 3.X.X.X, whose prefixlength is 5 to 6. 3.0.0.0/8+ is shorthand for 3.0.0.0/{0,8}, + 3.0.0.0/8- is shorthand for 3.0.0.0/{0,7}.
Filter language supports common integer operations (+,-,*,/), parenthesis (a*(b+c)), comparation +(a=b, a!=b, a<b, a>=b). Special operators include ~ for "in" operation. In operation can be +used on element and set of that elements, or on ip and prefix, or on prefix and prefix. Its result +is true if element is in given set or if ip adress is inside given prefix. + +
Bird supports functions, so that you don't have to repeat same blocks of code over and +over. Functions can have zero or more parameters, and can have local variables. Function basically +looks like this: + +
+function name ()
+int local_variable;
+{
+ local_variable = 5;
+}
+
+function with_parameters (int parameter)
+{
+ print parameter;
+}
+
+
+Unlike C, variables are declared after function line but before first {. You can not declare +variables in nested blocks. Functions are called like in C: name(); with_parameters(5);. + +
Filters are declared in similar way to functions, except they can not have explicit +parameters. They get route table entry as implicit parameter. + +
Filters support two control structures: if/then/else and case. Syntax of if/then/else is if expression then command; else command; and you can use {
+command_1; command_2; ... } instead of one or both commands. else clause may be ommited. Case is used like this:
+
+
+ case argument {
+ 2: print "dva"; print "jeste jednou dva";
+ 3 .. 5: print "tri az pet";
+ else: print "neco jineho";
+ }
+
+
+where argument is any argument that can be on the left side of ~ operator, and anything that
+could be member of set is allowed before :. Multiple commands are allowed without {} grouping. If
+argument matches neither of : clauses, else: clause is used. (Case is actually implemented as set
+matching, internally.)
+
Protocols
Rip
diff --git a/filter/config.Y b/filter/config.Y
index c73271ea..05608c95 100644
--- a/filter/config.Y
+++ b/filter/config.Y
@@ -10,6 +10,8 @@
FIXME: create community lists
FIXME: '! =' should not be permitted. Ze `!=' by nemelo byt totez jako `! =' Nadefinujes si pres %token novy token a do cf-lex.l pridas nove pravidlo, ktere jej rozpoznava. Napriklad != return NEQ;
FIXME: IP addresses in ipv6
+
+ FIXME: how can functions return value?
*/
CF_HDR