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
174 ServerIron ADX Security Guide
53-1002440-03
Configuring Real and Virtual Servers for SSL Termination and Proxy Mode
6
Configuring Real and Virtual Servers for SSL Proxy Mode
Real and Virtual Server configuration is described in detail in the ServerIron ADX Server Load
Balancing Guide. When configuring a Real or Virtual Server for SSL Proxy Mode, you need to do the
following:
• Configure a Real Server with an SSL port
• Configure a Virtual Server with an SSL port
• Enable SSL Proxy and specify an SSL client profile and an SSL server profile on the SSL port of
the Virtual Server
• Bind SSL on the Virtual Server to an SSL port on a Real Server
For IPv4 Real Server to IPv4 Virtual Server
In the example below an IPv4 Real Server and an IPv4 Virtual Server are configured for SSL Proxy
mode with the following details:
• An SSL port is defined on the Real Server: "rs3"
• An SSL port is defined on the Virtual Server: "vip3".
• SSL Proxy is configured and the SSL client profile "IPv4clientprofile" and SSL server profile
"IPv4serverprofile" are specified on the Virtual Server: "vip3".
• A bind is configured between SSL on Virtual Server: "vip3" and SSL on the Real Server: "rs3".
ServerIronADX(config)# server real rs3 10.1.1.1
ServerIronADX(config-rs-rs3)# port ssl
ServerIronADX(config-rs-rs3)# exit
ServerIronADX(config)# server virtual-name-or-ip vip3
ServerIronADX(config-vs-vip3)# port ssl
ServerIronADX(config-vs-vip3)# port ssl ssl-proxy IPv4clientprofile
IPv4serverprofile
ServerIronADX(config-vs-vip3)# bind ssl rs3 ssl
For IPv6 Real Server to IPv6 Virtual Server
In the example below an IPv6 Real Server and an IPv6 Virtual Server are configured for SSL Proxy
mode with the following details:
• An SSL port is defined on the Real Server: "rs4"
• An SSL port is defined on the Virtual Server: "vip4".
• SSL Proxy is configured and the SSL client profile "IPv6clientprofile" and SSL server profile
"IPv6serverprofile" are specified on the Virtual Server: "vip4".
• A bind is configured between SSL on Virtual Server: "vip4" and SSL on the Real Server: "rs4".
ServerIronADX(config)# server real rs4 2000::2
ServerIronADX(config-rs-rs4)# port ssl
ServerIronADX(config-rs-rs4)# exit
ServerIronADX(config)# server virtual-name-or-ip vip4
ServerIronADX(config-vs-vip4)# port ssl
ServerIronADX(config-vs-vip4)# port ssl ssl-proxy IPv6clientprofile
IPv6serverprofile
ServerIronADX(config-vs-vip4)# bind ssl rs4 ssl
Syntax: [no] port ssl ssl-proxy <ssl-profile-name-1> <ssl-profile-name-2>