v1.4.0

Please note: this release changes the default tool used to pull information from IRR, moving from bgpq3 to bgpq4. If you upgrade to this release and you are using bgpq3 to fetch IRR information, you either need to install bgpq4 (instructions here) or be sure that the bgpq3_path line is configured in your arouteserver.yml file and pointed to your bgpq3 binary.

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

  For more details, see the docker directory.

• 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 of the Euro-IX schema.

  See also GitHub #65.

v1.3.0

• 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

v1.2.0

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

v1.1.0

• Improvement: multihop support.

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

  More details on GitHub #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 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.

v1.0.1

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

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

Upgrade notes: after upgrading, run the arouteserver setup-templates command to sync the local templates with those distributed with the new version. More details on the Upgrading section of the documentation.

v1.0.0

No changes, just make it "stable"!

v0.26.0

• New: Add support for OpenBGPD/OpenBSD 6.7 and OpenBGPD Portable 6.7p0, also added to the integration testing suite.

v0.25.1

• Fix: BIRD, use bgp_path.last since it's consistent with RFC 6907 7.1.9-11 (RPKI BOV of routes whose AS_PATH ends with an AS_SET).

  More info: https://www.mail-archive.com/[email protected]/msg05152.html

  Related: PR #56 on GitHub.

v0.25.0

• New feature: tag_and_reject reject policy for BIRD.

  Invalid routes can be tagged with informational BGP communities and then discarded by BIRD.
  With this option, alice-lg reject reasons are supported nicely, whilst keeping show routes all filtered working to keep birdwatcher happy.

  Related: PR #57.

• Improvement: clients-from-euroix command, option --merge-from-custom-file to customise the list of clients generated from an Euro-IX JSON file.

  More details on how to use this option can be found running arouteserver clients-from-euroix --help-merge-from-custom-file.

v0.24.1

• Improvement: add support for bgpq4.

  At least version 0.0.5 is required.

  Related: PR #53 on GitHub.

• Fix: clients-from-euroix command, route server detection on Euro-IX schema versions 0.7 and 1.0.

  In version 0.7 and 1.0 of the Euro-IX member list JSON file the way the route server information are exported changed. The clients-from-euroix command was no longer able to filter out the IP addresses that represent the route server of the same IXP for which the members are processed, basically generating a client entry for the same route server being configured.