Feature requests

It can be done that way with GoBGP: gobgp global rib add -a ipv4 123.123.253.0/24 aspath 999999 Then receiving router will see it as: AS9000, AS999999 123.123.253.0/24 It's required in cases when we have RPKI validation and ROA validation on upstream side

We can export per protocol counters to Clickhouse but we do not export them via API: ```JSON_MODE=on sudo -E fcli show network_counters {"success":true,"values":[{"network_name":"1.2.3.4/22","incoming_packets":69471,"outgoing_packets":31680,"incoming_bytes":82167074,"outgoing_bytes":6743429}]}``` We need to add this missing capability.

Redirect action support for BGP Flow spec mode

Customer reported that such long timeout may lead to cases when some traffic triggered bucket capture but then no packets matched this this rule appeared to arrive. It happens when BGP Flow Spec mode enabled with threshold_specific_ban_details enabled. It will lead to 120 seconds without detection. We prefer to avoid exposing it as configuration option as it will add more complexity to our already complex detection engine engine to address it different way

We've implemented schema change in v2.0.358 but some parts are still missing and need testing.

It would be great if we could retrieve stats from InfluxDB by host (and by hostgroup) about the amount of traffic that matches the flowspec rules created by FastNetMon (and which is therefore theoretically dropped). This would make it possible to check very quickly on supervision whether the attack traffic has been identified & matched correctly by FastNetMon, or whether human intervention is required to adapt the filters. Or simply have an option to exclude traffic that matches flowspec rules from traffic statistics sent to InfluxDB.

In some cases it may be useful to add non visible in Full BGP table prefixes for better quality of reports. Or it may be used to override inaccurate data. Starting from FastNetMon 2.0.351 we use JSON format for these files and it can be easily altered: $ head -n 1 /var/cache/fastnetmon/prefix_asn_mapping_ipv4.json {"asn":13335,"prefix":"1.0.0.0/24"} $ head -n 1 /var/cache/fastnetmon/prefix_asn_mapping_ipv6.json {"asn":112,"prefix":"2001:0004:0112::0000/48"}

Our default Top-k dashboad is very CPU intensive and we need to provide better alternative for it. We can pre-calculate top-K hosts (per direction, by bytes/s, packets/s, flow/s) on FastNetMon side and export only them. It will reduce load on Clickhouse and even can be implemented for InfluxDB

The same feature the community edition received here, but for the advanced edition: https://github.com/pavel-odintsov/fastnetmon/commit/f6379e0360667d537874289eacdbca78d79495e9