Tempesta Technologies
  • Home
  • Tempesta FW
    • Features
      • Web acceleration
      • Load balancing
      • Application performance monitoring
    • Performance
    • How it works
    • Deployment
    • Support
    • Knowledge base
  • Services
    • Software development
      • High performance
      • Networking
      • Databases
      • Linux kernel
      • Machine learning
      • How we work
      • Case studies
    • Performance analysis
    • Network security
      • DDoS protection
      • Application security
      • Cryptography
      • Security assessment
      • How we work
      • Case Studies
  • Solutions
    • DDoS Protection
    • Web Acceleration
  • Blog
  • Company
    • Research
    • Careers
    • Contact
Tempesta Technologies

XFW Filtration Rules

Tempesta xFW allows only the IPv4, IPv6, ARP, ICMPv4 and ICMPv6, GRE, TCP and UDP protocols. All other L3 and L4 protocols are blocked. Tempesta xFW also blocks fragmented IPv4 and IPv6 packets as malicious.

RFC 8955 and RFC 8956 Filtering๐Ÿ”—

Most BGP FlowSpec filtering rules specified in RFC 8955 and RFC 8956 can be implemented in Tempesta xFW.

RFC 8955 Section 4.2.2.1 / RFC 8956 Section 3.1: Destination Prefix๐Ÿ”—

Destination Filter applies this rule on a per-IP basis. Netmask (prefix) rules are planned for the 1.2 release.

RFC 8955 Section 4.2.2.2 / RFC 8956 Section 3.2: Source Prefix๐Ÿ”—

Source Filter implements source netmask (prefix) filtering.

RFC 8955 Section 4.2.2.3 / RFC 8956 Section 3.3: IP Protocol๐Ÿ”—

IP Filter filters IP packets by next-level protocol ID.

RFC 8955 Section 4.2.2.4: Port๐Ÿ”—

Source and destination ports must be specified separately in the source and destination filters, respectively.

RFC 8955 Section 4.2.2.5: Destination Port๐Ÿ”—

Destination Filter implements this rule on a per-port and per-address basis.

RFC 8955 Section 4.2.2.6: Source Port๐Ÿ”—

Source Filter implements source-port filtering, which can be specified without IP addresses.

RFC 8955 Section 4.2.2.7 / RFC 8956 Section 3.4: ICMPv4 and ICMPv6 Type๐Ÿ”—

ICMP Filter implements this rule.

RFC 8955 Section 4.2.2.8 / RFC 8956 Section 3.5: ICMPv4 and ICMPv6 Code๐Ÿ”—

This rule is planned for the 1.2 release.

RFC 8955 Section 4.2.2.9: TCP Flags๐Ÿ”—

TCP Anomaly Filter lets you specify prohibited TCP flag combinations.

RFC 8955 Section 4.2.2.10: Packet Length๐Ÿ”—

This rule is planned for the 1.2 release.

RFC 8955 Section 4.2.2.11: DSCP (Differentiated Services Code Point)๐Ÿ”—

Filtering by this field is not currently planned. If you need it, please open a new issue.

RFC 8955 Section 4.2.2.12 / RFC 8956 Section 3.6: Fragment๐Ÿ”—

At the moment, IP Anomaly Filter blocks all IP fragments.

Configurable handling of IP fragments is planned for the 1.2 release.

  • Home
  • XFW
    • Basic Administration
    • Quick start
    • DNS DDoS protection
    • Observability
    • Performance
  • XFW Filtration Rules
    • Chaining
    • Evaluation Mode
    • IP Filter
    • ICMP Filter
    • DNS Filter
    • UDP Anomaly Filter
    • TCP Anomaly Filter
    • TCP Authentication Filter
    • TCP SYN Cookies
    • TCP Flags Filter
    • Destination Filter
    • Source Filter
    • Protected Network Definition
    • Rate Limits
    • Default Rules
  • Manager
    • Management daemon
    • Client library
    • Command line interface
  • DDoS Protection Use Cases
    • DNS server
    • Web server
    • Advanced Protection
  • Troubleshooting
    • Troubleshooting System Description
    • Troubleshooting System Verification Script
    • Troubleshooting Netconsole Configuration
    • Troubleshooting Server
    • Troubleshooting Support Server

Powered by Tempesta FW

Stay up to date with our latest developments

Useful Links

Home
Blog

Tempestaยฎ FW

Features
Performance
Deployment
Support
Knowledge Base

Services

Software Development
Performance analysis
Network Security

Solutions

DDoS Protection

Web Acceleration

Company

Research
Careers
Contact