Cleaned up handling of interface patterns:
o Parsing of interface patterns moved to generic code, introduced this_ipatt which works similarly to this_iface. o Interface patterns now support selection by both interface names and primary IP addresses....
Added PASSIVE option to paswwords.
Change format of passwords (less ;'s) and fix password.h to allowmultiple inclusions.
Skeleton for password handling, currently I only build structures anddo nothing more advanced for them
From now we support multiple tables. The master_table variable isdefinitely gone. Both rte_update() and rte_discard() have an additionalargument telling which table should they modify.
Also, rte_update() no longer walks the whole protocol list -- each table...
Changed syntax of attaching filters to protocols to hopefully the finalversion:
EXPORT <filter-spec> for outbound routes (i.e., those announced by BIRD to the rest of the world). IMPORT <filter-spec> for inbound routes (i.e., those imported by BIRD from the rest of the world)....
After today's lengthy discussions about filter syntax, let's clean upwhitespace/semicolon rules for whole config file:
o All non-zero amounts of whitespace are equivalent to single space (aka `all the whitespace has been born equal' ;-)). o Comments count as whitespace....
Moved to a much more systematic way of configuring kernel protocols.
o Nothing is configured automatically. You need to specify the kernel syncer in config file in order to get it started. o Syncing has been split to route syncer (protocol "Kernel") and...
Allow input and output filters (only accept/reject style as we didn't definemodifying filters yet) to be attached to protocol instances.
Implemented new configuration/reconfiguration interface and defined protocolstate machines. Full explanation will follow soon.
Name cleanups as suggested by Pavel:
- cfg_strcpy() > cfg_strdup() mempool -> linpool, mp_* -> lp_* [to avoid confusion with memblock, mb_*]
Anyway, it might be better to stop ranting about names and do some real work.
Added configuration of the device internal protocol. This is primarilyintended to serve as an example of interface pattern list use. As a sideeffect, you can disable generating of device routes by disablingthis protocol.
Allow setting debug value and `disabled' flag in protocol definition.
Oops, forgot to remove a debugging kludge.
Trivial 15-line bison excercise: Implemented expressions includinguser-defined numeric symbols. Whenever possible, use `expr' insteadof `NUM' to get full express ion power :-)
First attempt at protocol configuration (now done only for RIP).
Parser fragment for the core. Now handles only router ID setting.