v0.14.0

This release breaks backward compatibility (OpenBGPD configs only): for OpenBGPD configurations, starting with this release the Site of Origin Extended BGP communities in the range 65535:* (soo 65535:*) are reserved for internal reasons.

• New feature: use RPKI ROAs as if they were route objects.

  This feature allows to accept those routes whose origin ASN is authorized by a client AS-SET, whose prefix is not but it is covered by a RPKI ROA for the same origin ASN.

  Related: issue #19.

• New feature: automatic checking for new releases.

  This can be disabled by setting check_new_release to False in arouteserver.yml.

• Improvement: routes accepted solely because of a white_list_route entry are now tagged with the route_validated_via_white_list BGP community.

• Fix: on OpenBGPD configurations, in case of duplicate definition of a client's AS-SETs, duplicate BGP informational communities were added after the IRR validation process.

v0.13.0

• New feature: an option to set RFC1997 well-known communities (NO_EXPORT/NO_ADVERTISE) handling policy: pass-through or strict RFC1997 behaviour.

  This breaks backward compatibility: previously, NO_EXPORT/NO_ADVERTISE communities were treated accordingly to the default implementation of the BGP speaker daemon (BIRD, OpenBGPD). Now, ARouteServer's default setting is to treat routes tagged with those communities transparently, that is to announce them to other clients and to pass-through the original RFC1997 communities.

• Improvement: when using PeeringDB records to configure the max-prefix limits, a margin is took into account to accomodate networks that fill the PeeringDB records with their exact route announcement count.

  This breaks backward compatibility: if using max-prefix from PeeringDB, current limits will be raised by the default increment values (+100, +15%): this behaviour can be reverted to the pre-v0.13.0 situation by explicitly setting the max_prefix.peering_db.increment configuration section to 0/0.

  Related: issue #12.

• New feature: client-level white lists for IRRdb-based filters.

  This allows to manually enter routes that must always be accepted by IRRdb-level checks and prefixes and ASNs that must be treated as if they were included within client's AS-SETs.

  Related: issue #16.

v0.12.3

• Improvement: always take the ASn macro into account when building IRRdb-based filters.

  Related: issue #15

v0.12.2

• 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

• Fix an issue that was impacting templates upgrading under certain circumstances.
  Related: issue #10.

v0.12.0

• 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

• 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

• 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

• Fix: OpenBGPD, an issue was causing values > 65535 to be used in standard BGP communities matching.

v0.9.2

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