Arouteserver

------

- New: add support for OpenBGPD 7.4, also added to the integration testing suite (portable edition only).

- Fix: pin down `urllib3` version to avoid issues on upgrade.

See also `GitHub issue 110 <https://github.com/pierky/arouteserver/issues/110>`__.

- Fix: the `playground <https://github.com/pierky/arouteserver/tree/master/tools/playground>`__ Docker image was not building anymore.

Go and AliceLG birdwatcher versions have been bumped to the latest available.

------

- Improvement: use bulk queries to get clients' records from PeeringDB.

Clients' details (such as IRR records and max-prefix limits) are now retrieved from PeeringDB using *bulk* API queries, where multiple ASNs are checked at once.

This speeds up the configuration building process and reduces the number of queries to PeeringDB, reducing the risk of hitting the API rate limit.

See also `GitHub issue 107 <https://github.com/pierky/arouteserver/issues/107>`__.

------

- Fix: update the requirements.

The min. version of Jinja2 reported in the requirements file was not enough to satisfy the needs of the templates.

See also `GitHub issue 106 <https://github.com/pierky/arouteserver/issues/106>`__.

- Fix: allow setting PeeringDB API key to mitigate anonymous API throttling mechanism.

ARouteServer can now be instructed to use an API key to perform authentication against the PeeringDB API server. This can be done by setting the environment variable ``SECRET_PEERINGDB_API_KEY`` or by storing the same key inside one of the following well-known files: ``~/.arouteserver/peeringdb_api.key``, ``~/.peeringdb_api.key``.

This should mitigate the effects of the anonymous API throttling mechanism introduced on PeeringDB.

See also `GitHub issue 107 <https://github.com/pierky/arouteserver/issues/107>`__.

- Improvement: retry on PeeringDB API failure or rate-limit.

In case of failure or rate-limit of the PeeringDB API the tool now retries the same query multiple times.

See also `GitHub issue 107 <https://github.com/pierky/arouteserver/issues/107>`__.

------

- New: add support for OpenBGPD 7.3, also added to the integration testing suite (portable edition only).

- New: ``md`` command, to build a textual representation in Markdown format.

This command works like the ``html`` command and can be used to build a textual representation of the route server's configuration policy in Markdown format.

For more details see the `Textual representation <https://arouteserver.readthedocs.io/en/latest/USAGE.html#textual-representation>`__ section of the documentation.

- New: add ``custom_options`` to the clients definition file.

This new section can be used to add BGP-speaker-specific arbitrary lines of configuration to the file generated by ARouteServer.

For more details see the `Client custom options <https://arouteserver.readthedocs.io/en/latest/CONFIG.html#custom_options>`_.>`__ section of the documentation.

See also `GitHub PR 104 <https://github.com/pierky/arouteserver/pull/104>`__.

- Improvement (BIRD): skip NEXT_HOP check for IPv6 link-local clients.

Due to a limitation of BIRD, it is not possible to verify the NEXT_HOP attribute of routes announced by IPv6 clients configured using link-local addresses.
The configurations generated using this release skip that check (upon operator's approval if such clients are present).

See also `GitHub PR 104 <https://github.com/pierky/arouteserver/pull/104>`__.

- Fix: detect infeasible extended BGP communities when a 32bit ASN is used for the route server.

When the route server uses a 32bit ASN, certain extended BGP communities may end being configured to match multiple 32bit values, which is not possible because the way they are encoded.

This release detects similar situations in advance and aborts the configuration building process.

See also `GitHub PR 104 <https://github.com/pierky/arouteserver/pull/104>`__.

------

- Fix: import limit is not set if PeeringDB records are not found.

For clients not configured with a specific max-prefix value, when a PeeringDB record was not found the value from the general limit was not used to build the import limit configuration. The tool was expected to fallback to the ``general_limit_ipv4`` value instead.

See also `GitHub issue 105 <https://github.com/pierky/arouteserver/issues/105>`_.

------

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

- Improvement (OpenBGPD): improve readability of the configurations.

A better formatting of the output configuration allows a better readability. Also, wherever possible, extended communities are removed using wildcard matching, allowing a more compact configuration.

See also `GitHub issue 97 <https://github.com/pierky/arouteserver/issues/97>`_ and `99 <https://github.com/pierky/arouteserver/issues/99>`_.

- Improvement (Docker image): use ``bgpq4`` version 1.4.

The Docker image was using version 1.2.

- Improvement (Docker image): PyPy3-based image added.

The Docker images based on PyPy3 will have tags in the form ``latest-pypy3`` and ``<version>-pypy3`` (like ``1.14.0-pypy3``).

- Improvements: drop dependencies on libraries needed for Python 2 compatibility.

Also, tests are now performed using Python 3.6, 3.8 and 3.9 too.