Arouteserver

------

- New: Add support for `BIRD 2.0.8 <https://www.mail-archive.com/bird-usersnetwork.cz/msg05937.html>`_ (also included into the integration testing suite).

------

- New: Docker image to easily build route-server configurations.

For more details, see the `docker directory <https://github.com/pierky/arouteserver/tree/master/docker>`_.

- Improvement: change the default value of ``bgpq3_path`` to ``bgpq4``.

The ``bgpq4`` tool is now referenced as the default one in the ``bgpq3_path`` configuration line of arouteserver.yml.

**Please note**: operators who are using the tool and who left the ``bgpq3_path`` configuration line unset will now need to either explicitly configure that line to point to their ``bgpq3`` binary or to make sure ``bgpq4`` is available on their system.

- Fix: the ``ixf-member-export`` command now produces a JSON file compliant with `version 1.0 <https://github.com/euro-ix/json-schemas/blob/master/versions/ixp-member-list-1.0.schema.json>`_ of the `Euro-IX schema <https://github.com/euro-ix/json-schemas>`_.

See also `GitHub PR65 <https://github.com/pierky/arouteserver/pull/65>`_.

------

- New: ``irr-as-set`` command, to build the route server AS-SET object for IRR databases.

This new command can be used to build the AS-SET RPSL object that describes the ASes and AS-SETs of route server clients. Details and usage: https://arouteserver.readthedocs.io/en/latest/USAGE.html#irr-as-set

Related: `issue 49 on GitHub <https://github.com/pierky/arouteserver/issues/49>`_.

------

- Improvement (BIRD only): ``tag_and_reject`` is now the default reject policy set by the ``configure`` command.

When the ``configure`` command is initially used to setup ARouteServer and to generate the ``general.yml`` file, the `reject policy <https://arouteserver.readthedocs.io/en/latest/CONFIG.html#reject-policy-and-invalid-routes-tracking>`__ that it configures is ``tag_and_reject`` if BIRD is specified as the route server daemon.

- Fix: ``setup-templates`` was not generating the correct backup of customized templates.

The bug only affected the upgrade procedure of deployments where the Jinja2 templates were locally customized. More details on the comments of commit `2ea6df69106d473f9f4170c65f929bab4a0d7676 <https://github.com/pierky/arouteserver/commit/2ea6df69106d473f9f4170c65f929bab4a0d7676>`_.

------

- Improvement: multihop support.

For BIRD, this option can be configured only when path-hiding mitigation is turned off.

More details on `GitHub PR61 <https://github.com/pierky/arouteserver/pull/61>`_.

- Improvement (BIRD only): allow ``count_rejected_routes: True`` in BIRD 2.0.7 when the patch is used.

A `patch for BIRD 2.0.7 <https://www.mail-archive.com/bird-usersnetwork.cz/msg05638.html>`_ was released to address the bug that leads the daemon to crash when a configuration is built using ``count_rejected_routes: True``. This release adds a new locally meaningful fictitious version of BIRD that can be used to overcome the limitation enforced in ARouteServer 1.0.1, by signalling to the tool the usage of a patched version of BIRD (``--target-version 2.0.7+b962967e``).

See the notes for the 1.0.1 release for more details.

- New: Add support for OpenBGPD/OpenBSD 6.8 and OpenBGPD Portable 6.8p1, also added to the integration testing suite.

------

- Fix (BIRD only): change default behaviour to count rejected routes towards the max-prefix limit threshold.

So far, routes received by the route server and rejected as a result of ingress filtering were not counted towards the max-prefix limit threshold; **this release changes the default behaviour** in a way that they are now taken into account.

Example: a peer is configured with max-prefix limit 10 and action 'shutdown'. It announces 15 routes, 5 of which are rejected due to inbound filters.
BIRD route servers configured using previous releases will not perform any action on that peer, while a configuration generated with this release will lead to the shutdown of the BGP session with that peer.

In case the previous implementation of the max-prefix limit is the desired one, it can be restored by setting the new configuration statement that has been introduced with this release, ``count_rejected_routes``, to ``False``. More details in the `general.yml file <https://github.com/pierky/arouteserver/blob/master/config.d/general.yml>`_.

**BIRD 2.0.7 users, please note**: if you are using ARouteServer to configure route servers which are based on BIRD 2.0.7, you'll get an error message at configuration build time. This is due to the fact that in BIRD 2.0.7 there is `a bug <https://www.mail-archive.com/bird-usersnetwork.cz/msg05597.html>`_ that affects configurations generated using the statement that implements the new default behaviour for max-prefix limit handling. The error message will show you the options to unblock the config generation, but in any case it will not be possible to implement this new way of handling the max-prefix limit.