Version 2.0.0pre0

[Ondrej Zajicek]

On Wed, Dec 07, 2016 at 08:43:08PM +0100, Ondrej Filip wrote:
> On the other hand, testers are more than welcome. Please use it and
> report (either positive or negative)!
> 
>   Notes:
> 
>   Protocols and tables are now connected using explicit
>   channels, most related protocol options (table, import,
>   export, ...) are now channel options. See
>   doc/bird.conf.example2 for configuration examples.

Hi

As configuration changes are not yet reflected in documentation, here is
a summary for adventurous testers:

0) Most features are presented in doc/bird.conf.example2 :
https://gitlab.labs.nic.cz/labs/bird/blob/int-new/doc/bird.conf.example2

1) There are (currently) 8 network/route classes:
  ipv4, ipv6 - regular IP networks/routes
  vpn4, vpn6 - VPN networks/routes (IP networks with additional VPN distinguisher)
  roa4, roa6 - RPKI ROA records
  flow4, flow6 - BGP Flowspec records

2) Each routing table is defined with class (above) and contains just
routes of that class (instead of 'table xxx;' use e.g. 'ipv4 table xxx;').

3) Two tables are predefined, ipv4 table 'master4' and ipv6 table 'master6'.

4) For each network class, the first defined table of that class is
considered default.

5) Protocols are connected to tables using explicitly configured channels,
each channel connects the protocol to one table. Like tables, channels
has class.

6) Channel is specified by a keyword, which is usually (but not always)
the keyword of channel class (e.g., ipv4, ipv6, ...), and block with
options. These options were moved from protocol to channel: table,
import, export, all limits, preference, import keep filtered.

7) Channel may be specified without options, with expected meaning:
default table (by channel class), import all, export none.

8) Some protocols require one channel of fixed class (e.g. ipv6 for ripng),
Some protocols required one channel of selectable class (e.g. static),
Some protocols may have multiple channels (e.g. BGP).

9) BGP supports these channels (keywords) for these AFI/SAFI pairs:
  ipv4 - AF 1/1
  ipv6 - AF 2/1
  ipv4 multicast - AF 1/2
  ipv6 multicast - AF 2/2
  flow4 - AF 1/133
  flow6 - AF 2/133

  Multicast (SAFI 2) channels connects to regular ipv4/ipv6 tables.

10) BGP channels also have these options (that were moved from BGP
protocol): next hop self, next hop keep, next hop address, missing
lladdr, gateway, secondary, graceful restart, add paths, igp table.

11) As usual, pipe protocol is exception - the syntax is same as in the old
BIRD, two channels (to 'table' and 'peer table') are defined implicitly.

12) Some protocols were splitted and use new keywords: There is rip (for
RIPv2) and ripng (for RIPng), ospf2 (for OSPFv2) and ospf3 (for OSPFv3).
There is no ospf. Note that automatic naming and numbering of multiple
protocols is still shared between these variants.

13) Note that with ospf2, ospf3 keywords collide with automatic names for
second and third OSPF protocol. Use always explicit protocol names in
these case to avoid this issue.


Questions, comments and suggestions are welcome.


-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20161208/74378c0c/attachment.asc>