v0.7.0
-
New feature: custom BGP communities can be configured on a client-by-client basis to tag routes entering the route server (for example, for informative purposes).
-
Fix: validation of BGP communities configuration for OpenBGPD.
Error is given if a peer-AS-specific BGP community overlaps with another community, even if the last part of the latter is a private/reserved ASN.
-
Improvement: the custom
!include <filepath>
statement can be used now in YAML configuration files to include other files.More details here.
-
Improvement: IRRDB-based filters can be configured to allow more specific prefixes (
allow_longer_prefixes
option).