v1.15.1

• 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.

• 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.

• 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.

v1.15.0

• 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 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 section of the documentation.

  See also GitHub PR #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.

• 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.

v1.14.1

• 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 105

v1.14.0

• New: Add support for BIRD 2.0.9 (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 and #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.

v1.13.1

• Fix: avoid running bgpq4 using the -3 option.

  It seems that the -3 CLI option has been dropped in bgpq4 and is no longer supported (it was added as a way to not break compatibility with bgpq3 syntax).

  See also GitHub issue #95.

• Fix (OpenBGPD): syntax error when prepend functionalities were configured with 'std' communities only and 32bit ASN clients were present.

  See also GitHub issue #98.

• Improvement: better explaination of when error messages can be ignored.

  See also GitHub issue #96.

v1.13.0

• New (OpenBGPD): use the expires attribute of ROAs from rpki-client format.

  In OpenBGPD configurations (starting with 7.2), the expires attribute of ROAs gathered from JSON feeds that contain it is passed on into the configuration of the roa-set.

  See also GitHub issue #92.

v1.12.0

• New: add the --merge-file option to the ixf-member-export command, to include user-created content into the IX-F Member Export JSON file.

  For more details on how it works please check the documentation.

  See also GitHub issue #89.

• Improvement: in the ixf-member-export command, the value of IXP ID can now be set via the --ixp-id in addition to the existing --ixp_id option.

  In the future, the --ixp_id version of the option will be dropped. A warning message will be shown when the deprecated version of that command line argument is used.

• Improvement: ask for 16bit placeholder ASN in configure when the route-server is on a 32bit ASN.

  When the configure command is used to generate the policy for a route-server running on a 32bit ASN, a prompt asks the operator which 16bit placeholder ASN should be used to setup the BGP communities. So far, the fixed value 65534 was used.

  See also GitHub issue #88.

• Improvement (OpenBGPD): use as-set to configure the list of "never via route server" ASNs.

  This change reduces the size of the configuration and hopefully makes the filter processing faster.

  See also GitHub issue #90.

• Fix: when the route-server ASN was a 32bit value, the Euro-IX Large BGP Communities automatically configured via configure were using the 16bit placeholder ASN.

  When the configure command was used to build the genera.yml policy for route-servers running on 32bit ASNs, the Large BGP Communities used to map route reject causes to Euro-IX codes were using the 16bit placeholder ASN instead of the actual route-server's 32bit ASN.

v1.11.1

• Fix: better error handling for clients configured with no IP address.

  When a client was mistakenly configured with no IP addresses, the program raised an unhandled exception, instead of providing a good feedback to the user.

  See also GitHub issue #87.

v1.11.0

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

• Improvement: better handling of IRRd query failures.

  Multiple hosts can now be configured as servers used for the IRR queries performed via bgpq3/bgpq4. In case of timeout or failure, the next host in the list is used.
  A timeout of 2 minutes is used by default. These settings can be modified in the arouteserver.yml file.

  See also GitHub issue #85

v1.10.1

• Fix: the HTML representation of RPKI validation custom communities was broken.

  After adding custom RPKI validation communities implemented as part of v1.10.0 the route server configuration textual representation file hada small cosmetic problem.

  See also GitHub issue #83.