Home Theater Server User Manual
Table Of Contents
- Contents
- About This Document
- Network Security
- TCP SYN attacks
- IP TCP syn-proxy
- Granular application of syn-proxy feature
- Syn-def
- No response to non-SYN first packet of a TCP flow
- Prioritizing management traffic
- Peak BP utilization with TRAP
- Transaction Rate Limit (TRL)
- Understanding transaction rate limit
- Configuring transaction rate limit
- Configuring the maximum number of rules
- Saving a TRL configuration
- Transaction rate limit command reference
- Global TRL
- TRL plus security ACL-ID
- security acl-id
- Transaction rate limit hold-down value
- Displaying TRL rules statistics
- Displaying TRL rules in a policy
- Displaying IP address with held down traffic
- Refusing new connections from a specified IP address
- HTTP TRL
- Overview of HTTP TRL
- Configuring HTTP TRL
- Displaying HTTP TRL
- Display all HTTP TRL policies
- Display HTTP TRL policy from index
- Display HTTP TRL policy client
- Display HTTP TRL policy starting from index
- Display HTTP TRL policy matching a regular expression
- Display HTTP TRL policy client index (MP)
- Display HTTP TRL policy client index (BP)
- Display HTTP TRL policy for all client entries (BP)
- Downloading an HTTP TRL policy through TFTP
- HTTP TRL policy commands
- Logging for DoS Attacks
- Maximum connections
- clear statistics dos-attack
- Maximum concurrent connection limit per client
- Firewall load balancing enhancements
- Syn-cookie threshhold trap
- Service port attack protection in hardware
- Traffic segmentation
- DNS attack protection
- Access Control List
- How ServerIron processes ACLs
- Default ACL action
- Types of IP ACLs
- ACL IDs and entries
- ACL entries and the Layer 4 CAM
- Configuring numbered and named ACLs
- Modifying ACLs
- Displaying a list of ACL entries
- Applying an ACLs to interfaces
- ACL logging
- Dropping all fragments that exactly match a flow-based ACL
- Enabling ACL filtering of fragmented packets
- Enabling hardware filtering for packets denied by flow-based ACLs
- Enabling strict TCP or UDP mode for flow-based ACLs
- ACLs and ICMP
- Using ACLs and NAT on the same interface (flow-based ACLs)
- Displaying ACL bindings
- Troubleshooting rule-based ACLs
- IPv6 Access Control Lists
- Network Address Translation
- Syn-Proxy and DoS Protection
- Understanding Syn-Proxy
- Configuring Syn-Proxy
- DDoS protection
- Configuring a security filter
- Configuring a Generic Rule
- Configuring a rule for common attack types
- Configuring a rule for ip-option attack types
- Configuring a rule for icmp-type options
- Configuring a rule for IPv6 ICMP types
- Configuring a rule for IPv6 ext header types
- Binding the filter to an interface
- Clearing DOS attack statistics
- Clearing all DDOS Filter & Attack Counters
- Logging for DoS attacks
- Displaying security filter statistics
- Address-sweep and port-scan logging
- Secure Socket Layer (SSL) Acceleration
- SSL overview
- SSL acceleration on the ServerIron ADX
- Configuring SSL on a ServerIron ADX
- Basic SSL profile configuration
- Advanced SSL profile configuration
- Configuring Real and Virtual Servers for SSL Termination and Proxy Mode
- Configuration Examples for SSL Termination and Proxy Modes
- SSL debug and troubleshooting commands
- Displaying socket information
124 ServerIron ADX Security Guide
53-1002440-03
DDoS protection
5
TABLE 11 Output Descriptions for show server syn-cookie
DDoS protection
A Distributed Denial of Service (DDoS) attack is employed to cause a denial of service to legitimate
users by consuming all or most of the CPU and memory resources on a ServerIron ADX or on real
servers. The ServerIron ADX provides protection and prevents well-known DDoS attacks such as
Xmas-tree attack, syn fragment, address sweep and others. The ServerIron ADX prevents these
attacks by defining filters for each type of attack coupled with a drop or log action. These filters are
then bound to an interface. All packets that match the filter on the bound interface are dropped or
logged as defined in the configuration. Filters can be defined according to a generic rule as shown
in “Configuring a Generic Rule” on page 125 or applied from built-in rules as described in Table 13,
Table 15, Table 16 and Table 17. Filters are applied to IPv4 and IPv6 traffic where appropriate.
The following sections describe how to configure a security filter, define rules within a security filter
and bind a security filter to an interface.
• “Configuring a security filter” on page 125
• “Configuring a Generic Rule” on page 125
• “Configuring a rule for common attack types” on page 127
• “Configuring a rule for ip-option attack types” on page 129
• “Configuring a rule for icmp-type options” on page 130
• “Configuring a rule for IPv6 ICMP types” on page 131
• “Configuring a rule for IPv6 ext header types” on page 132
• “Binding the filter to an interface” on page 133
Field Description
CPU SYNs rcvd
AXP SYNs rcvd Number of SYNs received on ServerIron ADX ports that have the Syn-Proxy feature
enabled.
CPU SYN-ACKs sent
AXP SYN-ACKs sent Number of SYN ACKs sent from the ServerIron ADX to the client
CPU Valid ACKs rcvd
AXP Valid ACKs rcvd Number of valid ACKs received from the client.
Invalid ACKs rcvd Number or invalid ACKs received from the client.
ACL passed Number of ACL lookups that the ServerIron ADX passed.
ACL failed Number of ACL lookups that the ServerIron ADX denied.
Frags allowed Number of fragmented packets allowed.
Frags dropped Number of fragmented packets dropped.
ACK without datp dro:
Invalid vport