29. Reports » Tools » Routing

Reports » Tools displays the number of BGP announcements that are active. The number is red when there is at least one announcement sent through a BGP Connector configured for mitigation, or blue when all announcements were sent through BGP Connectors configured for traffic diversion.

The Routing tab displays all BGP announcements sent by Wanguard and provides a way for Console users to send BGP routing updates manually. The tab contains 3 sub-tabs, located at the lower left side of the window:

29.1. Active BGP Announcements

It displays all active BGP announcements sent by Sensors, Filters, Console users.

Console users can send or withdraw BGP announcements manually. To send an announcement, click the [Create Blackhole] or the [Divert Traffic] button and select a previously configured BGP Connector (see Configuration » Components » BGP Connector) for mitigation or diversion.

[Batch Actions] - [Clear] marks all failed or orphaned announcements as finished.

[Batch Actions] - [Resend] resends all active announcements. Useful when ExaBGP loses its configuration.

[Batch Actions] - [Reset] marks all announcements as finished by manipulating the database directly, without actually using the BGP Connector.

When there is at least one active BGP announcement, the following information is displayed:

BGP Connector

BGP Connector used for the routing update. When Grouping is set to “BGP Connector”, clicking it allows you to delete all announcements that used it, with a single click


Role configured for the BGP Connector. Can be Unset, Mitigation or Diversion


The prefix contained in the BGP routing update. When Grouping is set to “IP/Mask”, clicking it allows you to delete all announcements for that prefix, with a single click


A green check mark indicates that announcement was sent successfully. A red “X” icon indicates an error. Most errors are listed in the BGP Events (see Configuration » Schedulers » Event Reporting) grid. A warning sign indicates that the anomaly that triggered the announcement is no longer active, but the announcement still is. In this case you should remove the announcement manually and investigate the cause


Indicates the username of the Console user that sent the announcement, or the anomaly for which the announcement was generated. To avoid the overlapping of announcements, only a single announcement is sent to BGPd when there are multiple anomalies for the same prefix and BGP Connector


Time when the BGP announcement was sent


Time when the BGP announcement will be withdrawn


Contains details about BGP Flowspec rules


Contains user comments about the BGP announcement


It contains a button for manual removal and a button for adding/modifying user comments. The column is hidden for guest accounts without proper permissions

29.2. BGP Announcement Archive

Lists all BGP announcements sent by Sensors, Filters and Console users. By clicking the down arrow of any column header, you can apply row filters, change sorting direction and toggle the visibility of columns. All columns are explained in the previous section, except for the Originating User column (hidden by default) that shows the Console user that sent and withdrew the announcement.

You can modify the status of announcements manually by double-clicking rows. The modification is applied only to the database, not to the Quagga BGPd/ExaBGP configuration.

29.3. BGP Connector Events

Lists events generated by BGP Connectors for the selected time range. Events are explained in the Configuration » Schedulers » Event Reporting chapter.