I know that some of you lost faith, but it's real! We are releasing BIRD version 3.0.0. After more than 5 years of sustained development, we came to conclusion that it's stable enough to be released. The feature list is the same as BIRD 2.16.

But this version is multithreaded. By default, it spins one worker thread for BGP, BMP, RPKI and Pipe, another one for BFD, and the rest stays in the main thread.

To enable this, we had to do a huge amount of internal reworks, so the table and channel implementation is very much different now. The protocols stayed almost the same.

There are some minor breaking changes in config and CLI, most notably unified route attribute names to the filter variant. We are expecting to add a compatibility mode for the CLI. Anyway, it should be possible to reuse most of the configs and CLI scriptings from BIRD 2.

The memory consumption has gone up significantly. We are still working on reducing the memory footprint and the next versions should be better in that.

There is some documentation about what has changed between BIRD 2 and BIRD 3 from the users' perspective in doc/migration-bird3.md. if you find anything missing in that file, please send a patch, it would be deeply appreciated.

We are expecting to keep developing BIRD 2 and BIRD 3 side by side for some more time as there are some old branches rooted in BIRD 2. New projects and contributions should primarily target BIRD 3 though.

Thank you for running BIRD and testing the alpha versions. Your feedback and contributions have been instrumental in reaching this milestone. We look forward to hearing your experience with BIRD 3.

As always, the tarball is available at https://bird.network.cz/download/bird-3.0.0.tar.gz and you can also setup our BIRD 3 repositories for Debian and Ubuntu: 
https://pkg.labs.nic.cz/doc/?project=bird

Let me thank the whole BIRD team and specifically Maria as the team leader! Thank you so much guys!

Merry routing!

On behalf of the BIRD team
Ondrej

We support:
- Collecting network packets passing through nftables rules marked as 'nftrace set 1'.
- Storing collected traces in the Clickhouse database.
- Providing access to stored traces and flexible analytics.

Visor includes following utilities:
- pkt-tracer - daemon for collecting network packets that pass through nftables rules marked as 'nftrace set 1', and forward them to a server for storage.
- trace-hub - server that implements an API for receiving and storing traces in a database and providing access to them via an API.
- visor-cli - command-line network traffic analyzer for fetching and analyzing traces by applied filters.
- visor-ui - terminal user interface tier of visor-cli.