Skip to content

Releases: pierky/arouteserver

v0.12.3

15 Oct 13:45
Compare
Choose a tag to compare
  • Improvement: always take the ASn macro into account when building IRRdb-based filters.

    Related: issue #15

v0.12.2

14 Oct 13:43
Compare
Choose a tag to compare
  • Fix: an issue on OpenBGPD builder class was preventing features offered via large BGP communities only from being actually implemented into the final configuration.
    Related: #11

v0.12.1

12 Oct 20:15
Compare
Choose a tag to compare
  • Fix an issue that was impacting templates upgrading under certain circumstances.
    Related: issue #10.

v0.12.0

12 Oct 16:34
Compare
Choose a tag to compare
  • OpenBGPD 6.2 support.

  • New feature: Graceful BGP session shutdown support, to honor GRACEFUL_SHUTDOWN communities received from clients and also to perform graceful shutdown of the route server itself (--perform-graceful-shutdown command line argument).

v0.11.0

04 Oct 17:17
Compare
Choose a tag to compare
  • Python 3.4 support.

  • Improvement: GT registry removed from the sources used to gather info from IRRDB.

    Related: PR #8.

  • Improvement: multiple AS-SETs used for the same client are now grouped together and queried at one time.
    This allows to leverage bgpq3's ability and speed to aggregate results in order to have smaller configuration files.

v0.10.0

07 Sep 17:08
Compare
Choose a tag to compare
  • New feature: when IRRDB-based filters are enabled and no AS-SETs are configured for a client, if the cfg.filtering.irrdb.peering_db option is set ARouteServer tries to fetch their values from the client's ASN record on PeeringDB.

    Related: issue #7

  • Improvement: config building process performances,

    • reduced memory consumption by moving IRRDB information from memory to temporary files;

    • responses for empty/missing resources are also cached;

    • fix a wrong behaviour that led to multiple PeeringDB requests for the same ASN.

  • Improvement: clients-from-euroix command, the new --merge-from-peeringdb option can be used to integrate missing information into the output clients list by fetching AS-SETs and max-prefix limit from PeeringDB.

Moreover, new realistic scenarios have been tested by feeding ARouteServer with lists of clients pulled from actual IXPs' members lists and making it generate feature-rich configurations, that have been finally loaded into BIRD and OpenBGPD to verify their validity. More details here.

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.

v0.9.3

06 Sep 17:38
Compare
Choose a tag to compare
  • Fix: OpenBGPD, an issue was causing values > 65535 to be used in standard BGP communities matching.

v0.9.2

30 Aug 16:41
Compare
Choose a tag to compare
  • Fix: remove quotes from clients description.

  • Fix: OpenBGPD, syntax error for prefix lists with 'range X - X' format.

  • Fix: clients-from-euroix command, members with multiple vlan objects with the same vlan_id were not properly listed in the output, only the first object was used.

v0.9.1

23 Aug 17:17
Compare
Choose a tag to compare
  • Improvement: BIRD, new default debug options (states, routes, filters, interfaces, events, was all).

    If needed, they can be overwritten using the header custom .local file.

  • Fix: enrichers errors handling reported a generic message with no further details.

  • Fix: HTTP 404 error handling for "Entity not found" error from PeeringDB.

  • Fix: OpenBGPD, large prefix lists were causing a "string too long" error.

  • Fix: OpenBGPD, clients descriptions longer than 31 characters were not properly truncated.

v0.9.0

20 Jul 17:08
Compare
Choose a tag to compare
  • New feature: RTT-based communities to control propagation of routes on the basis of peers round trip time.

  • Improvement: in conjunction with the "tag" reject policy, the rejected_route_announced_by BGP community can be used to track the ASN of the client that announced an invalid route to the server.

  • Fix: when the "tag" reject policy is used, verify that the reject_cause BGP community is also set.