v0.8.0

• New feature: reject policy configuration option, to control how invalid routes must be treated: immediately discarded or kept for troubleshooting purposes, analysis or statistic reporting.

• New tool: invalid routes reporter.

• Fix: the following networks have been removed from the bogons.yml file: 193.239.116.0/22, 80.249.208.0/21, 164.138.24.80/29.

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

v0.6.0

• OpenBGPD 6.1 support: enable large BGP communities support.

• Improvement: the clients-from-peeringdb command now uses the IX-F database to show a list of IXP and their PeeringDB ID.

• Improvement: enable NEXT_HOP rewriting for IPv6 blackhole filtering requests on OpenBGPD after OpenBSD 6.1 fixup.

  Related: issue #3.

• Improvement: BIRD, client-level .local file.

• Improvement: next-hop checks, the authorized_addresses option allows to authorize IP addresses of non-client routers for NEXT_HOP attribute of routes received from a client.

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

• Fix: avoid the use of standard communities in the range 65535:x.

• Improvement: option to set max-prefix restart timer for OpenBGPD.

• Deleted feature: tagging of routes à la RPKI-Light has been removed.

  • The reject_invalid flag, that previously was on general scope only, now can be set on a client-by-client basis.
  • The roa_valid, roa_invalid, and roa_unknown communities no longer exist.

  Related: issue #4

  This breaks backward compatibility.

• New feature: BIRD hooks to add site-specific custom implementations.

• Improvement: BIRD local files.

  This breaks backward compatibility: previously, *.local, *.local4 and *.local6 files that were found in the same directory where the BIRD configuration was stored were automatically included. Now, only the header([4|6]).local and footer([4|6]).local files are included, depending on the values passed to the --use-local-files command line argument.

• Improvement: setup command and program's configuration file.

  The default path of the cache directory (cache_dir option) has changed: it was /var/lib/arouteserver and now it is cache, that is a directory which is relative to the cfg_dir option (by default, the directory where the program's configuration file is stored).

v0.4.0

• OpenBGPD support (some limitations apply).
• Add MD5 password support on clients configuration.
• The build command used to generate route server configurations has been removed in favor of BGP-speaker-specific sub-commands: bird and openbgpd.

To upgrade please follow the instructions.

v0.3.0

New features

• New --test-only flag for builder commands.

• New --clients-from-euroix command to build the clients.yml file on the basis of records from an Euro-IX member list JSON file.

  This also allows the integration with IXP-Manager.

• New BGP communities: add NO_EXPORT and/or NO_ADVERTISE to any client or to specific peers.

• New option (set by default) to automatically add the NO_EXPORT community to blackhole filtering announcements.

To upgrade

To upgrade the program, download the new version...

# if you cloned the repository from GitHub,
# from within the local repository's directory:
git pull origin master

# if you installed it with pip:
pip install --upgrade arouteserver

... then sync the local templates with those distributed in the new version:

arouteserver setup-templates

v0.2.0

New features

• setup-templates command to just sync local templates with those distributed within a new release.

• Multithreading support for tasks that acquire data from external sources (IRRDB info, PeeringDB max-pre
  fix).

  Can be set using the threads option in the arouteserver.yml configuration file.

• New template-context command, useful to dump the list of context variables and data that can be use
  d inside a template.

• New empty AS-SETs handling: if an AS-SET is empty, no errors are given but only a warning is logged and
  the configuration building process goes on.

  Any client with IRRDB enforcing enabled and whose AS-SET is empty will have its routes rejected by the
  route server.

To upgrade

To upgrade the program, download the new version...

# if you cloned the repository from GitHub,
# from within the local repository's directory:
git pull origin master

# if you installed it with pip:
pip install --upgrade arouteserver

... then sync the local templates with those distributed in the new version:

arouteserver setup-templates

v0.1.2

• Fix local files usage among IPv4/IPv6 processes.

  Before of this release, only .local files were included into the route server configuration, for both the IPv4 and IPv6 configurations.
  After this, .local files continue to be used for both the address families but .local4 and .local6 files can also be used to include IP version specific options, depending on the IP version used to build the configuration. Details here.

To upgrade:

# pull from GitHub master branch or use pip:
pip install --upgrade arouteserver

# install the new template files into local system
# (be careful to not overwrite local configuration files
# but only templates)
# TODO: improve the upgrade system
arouteserver setup

v0.1.1

• Add local static files into the route server's configuration.

First beta version

v0.1.0

badges [skip ci]