Components » Filter Cluster

The functionality of Wanguard Filter is described in the Choosing a Method of DDoS Mitigation chapter. Filter Cluster receives aggregated traffic information from Packet Filter(s) and/or from Flow Filter(s).

To add a Filter Cluster, click the [+] button found in the title bar of the Configuration » Components panel. To configure an existing Filter Cluster, go to Configuration » Components and click its name.

Filter Cluster Configuration parameters:

● Filter Name – A short name to help you identify the Filter Cluster

● Filter Color – The color used in graphs for the Filter Cluster. The default color is a random one. You can change it from the drop-down menu

● Filter Visibility – Toggles the listing inside the Reports » Devices panel

● Device Group – Enter a description if you wish to organize components (e.g. by location, characteristics) or to permit fine-grained access for roles

● Filter Server – Select a server that fulfills the minimum system requirements for running the Filter Cluster

● Apply Rules By – Select where to apply the filtering rules detected by the Filter Cluster:

▪ Associated Filters – Filtering rules are applied on each server running an associated Filter

▪ Filter Cluster – Filtering rules are applied only on the server running the Filter Cluster

● Filtering Interface – Select where to apply the filtering rules:

▪ None – Filter Cluster detects and reports filtering rules, but it doesn’t apply them to a firewalled interface

▪ Inbound interface – Filter Cluster applies the filtering rules on the inbound interface, which is defined below

▪ Outbound interface – Filter Cluster applies the filtering rules on the outbound interface, which is defined below

● Traffic Diversion – Provides a selection of BGP Connectors that can be used for traffic diversion. If the server is deployed inline, or if you do not plan to deploy the server in a Side Filtering topology, leave this parameter set to Off

● Inbound Interface – Enter the interface that receives the incoming/ingress traffic. This parameter can be omitted if the Filtering Interface is the same as the Outbound Interface. Bridged interfaces should have the string “physdev:” prepended in front of the interface’s name

● Outbound Interface – The cleaned traffic is sent to the downstream router/switch via the outbound interface, which should hold the route to the default gateway. This parameter can be omitted if the Filtering Interface is the same as the Inbound Interface. Bridged interfaces should have the string “physdev:” prepended in front of the interface’s name

● Associated Filters – Select the Packet Filter(s) and/or Flow Filter(s) that should provide aggregated traffic information to the Filter Cluster. The associated Filters are launched automatically by the Filter Cluster instance

● BGP Flowspec – Select which policy to apply when the Response is configured to send BGP Flowspec announcements for filtering rules. The rate-limit policy works only for bits/s anomalies; anomalies detected for pkts/s will have the traffic matched by the filtering rule fully discarded

● Netfilter Firewall – Filter Cluster can leverage the Netfilter framework included in the Linux kernel to perform software-based packet filtering and packet rate limiting. Netfilter is very flexible, and because Filter Cluster does not make any use of the connection tracking mechanism specific to stateful firewalls, it is also very fast

▪ Disabled – Filter Cluster detects and reports filtering rules, but the Netfilter firewall API is not used

▪ Filtering rules drop matched traffic. Valid traffic is accepted – Filter Cluster detects, reports, and applies filtering rules using the Netfilter firewall. If the filtering rule is not whitelisted, then the traffic matched by it is blocked, and the remaining traffic is allowed to pass

▪ Filtering rules drop matched traffic. Valid traffic is rate-limited – Filter Cluster detects, reports, and applies filtering rules, and rate-limits the remaining traffic. If the filtering rule is not whitelisted, the traffic matched by it is blocked. The traffic that exceeds the packets/second threshold value is not allowed to pass. Netfilter supports rate-limiting only for packets/s thresholds, not for bits/s thresholds. Note that some kernel versions will fail to rate-limit traffic above 10000 pkts/s and will block all traffic instead

▪ Filtering rules rate-limit matched traffic. Valid traffic is accepted – Filter Cluster detects and reports filtering rules and rate-limits matched traffic to the threshold value. Netfilter supports rate-limiting only for packets/s thresholds, not for bits/s thresholds. Note that some kernel versions will fail to rate-limit traffic above 10000 pkts/s and will block all traffic instead

▪ Apply the default Netfilter chain policy – Filter Cluster detects and reports filtering rules and applies them to the firewall using the default Netfilter chain policy. The Netfilter framework is still being used, but all rules have the RETURN target. This option is used exclusively for testing purposes

When using the Netfilter Firewall, the following options become available:

• Execution – Filtering rules can be applied automatically without end-user intervention, or manually by a user that clicks the Netfilter icon in Reports » Tools » Anomalies

• Netfilter Table – The raw option requires both Inbound and Outbound interfaces to be set, and it may not work for virtual interfaces. It provides a better packet filtering performance compared to the filter option

• Netfilter Chain – Set to FORWARD if the server forwards traffic, or INPUT if it does not

• Operating Layer – Set to OSI Layer 2 if the server is configured as a bridge, or OSI Layer 3 otherwise

● Dataplane Firewall – This parameter sets the filtering policy of the Dataplane Firewall, a built-in software-based firewall that uses DPDK. It is better performing than Netfilter but less flexible and harder to configure

• Execution – Filtering rules can be applied automatically without end-user intervention, or manually by a user that clicks the Dataplane icon in Reports » Tools » Anomalies

● Hardware Offload – Select the appropriate option if you have a NIC that provides hardware filters. Since hardware filters do not consume CPU cycles, use this feature to complement the Netfilter Firewall and Dataplane Firewall

▪ Disabled – Hardware filters are not applied

▪ Chelsio T5+ 10/40/100 Gigabit adapter with LE-TCAM filters – Filter Cluster uses the cxgbtool utility to apply up to 487 filtering rules that may contain any combination of source/destination IPv4/IPv6 addresses, source/destination UDP/TCP port, and IP protocol. This utility is installed by the Chelsio Unified Wire driver. Drop traffic counters are available for packets, not for bytes

▪ Mellanox ConnectX NIC with OFED driver – Filter Cluster uses the /opt/mellanox/ethtool/sbin/ethtool utility to apply up to 924 filtering rules that may contain any combination of source/destination IPv4/IPv6 addresses, source/destination UDP/TCP port, and IP protocol. The ethtool utility is installed in the specified path by the OFED driver from Mellanox. Drop traffic counters are not available

▪ Intel x520+ 1/10/40 Gigabit adapter configured to block IPv4 sources – Filter Cluster programs the Intel chipset to drop IPv4 addresses from the filtering rules that contain source IPs. Up to 4086 hardware filters can be used. Drop traffic counters are not available

▪ Intel x520+ 1/10/40 Gigabit adapter configured to block IPv4 destinations – Filter Cluster programs the Intel chipset to drop IPv4 addresses from the filtering rules that contain destination IPs. Up to 4086 hardware filters can be used. Drop traffic counters are not available

When using Hardware Offload, the following option becomes available:

• Execution – Filtering rules can be applied automatically without end-user intervention, or manually by a user that clicks the NIC chipset icon in Reports » Tools » Anomalies

● Whitelist – It contains a collection of rules created to prevent the blocking of critical traffic, see the dedicated Whitelist Template chapter for details

● Comments – Comments about the Filter Cluster can be saved here. These observations are not visible elsewhere

Enable the Filter Cluster by clicking the small on/off button displayed next to its name in the Configuration » Components panel. When a traffic anomaly triggers the Response action “Detect filtering rules and mitigate the attack with Wanguard Filter”, a Filter Cluster instance will be launched automatically. If no traffic anomaly requires the running of a Filter instance, Reports » Devices » Overview will show the message “No active instance”.