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
ServerIron ADX Security Guide 17
53-1002440-03
HTTP TRL
1
Example
To configure the ServerIron to refuse connections from 192.168.9.210 for 20 minutes, enter.
ServerIronADX(config)# security hold-source-ip 192.168.9.210 20
To display the IP addresses from which connections are currently being refused.
The IP addresses for which connections are being refused are displayed in the source column.
HTTP TRL
This section describes how to use the HTTP Transaction Rate Limiting (TRL) feature with ServerIron
devices.
Overview of HTTP TRL
HTTP TRL provides HTTP transaction rate limiting for SSL and HTTP traffic, based on a customer ID.
Existing ServerIron TRL features, which are based on source IP addresses, are inadequate in
environments where a client is identified by an application user ID. HTTP TRL allows you to prevent
per-client over subscription by allowing you to configure features, such as transaction and
connection rate limiting, based on customer IDs.
With HTTP TRL, the rate limit configuration for each customer is grouped into a set. Each of these
groups can be applied to multiple VIPs. A counter is maintained on per-VIP basis. When a client
request is received, the client customer ID is extracted and decoded. A table lookup is performed
on the customer ID and, if the client is subjected to a rate limit, a session lookup is done to locate
the current connection information.
For each BP, the current counter is checked against the configuration. If the limit is exceeded, the
configured action occurs.
HTTP TRL features
Before you configure HTTP TRL, you should be aware of the following benefits and restrictions for
this feature:
• The customer ID is contained within the HTTP header, is alphanumeric, and can be up to 101
characters in length.
• Maximum customer ID entries is 35K.
• Customer ID entries can be manually configured or have dynamic upload support.
• All customer connections are supported on a single VIP with support for up to 10K
connections.
• Customer report response times can run up to 120 seconds before they timeout at the
gateway tier.
ServerIronADX# rconsole 2 1
ServerIronADX2/1 # show security holddown
source destination vers attempt start last HD time
192.168.2.30 Any tcp 0 000ab6ae 00000000 Y 9
192.168.2.40 Any tcp 0 000ab6ea 00000000 Y 9