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

32 ServerIron ADX Security Guide
53-1002440-03
Maximum concurrent connection limit per client
1
Maximum concurrent connection limit per client
This feature restricts each client to a specified number of connections, based on the client’s
subnet, to prevent any one client from using all available connections.
Limiting the number of concurrent connections per client
This feature restricts each client to a specified number of concurrent connections, based on the
client’s subnet, to prevent any one client from using all available connections.
You associate a configured client subnet with a maximum permissible connection value. The
association is stored in the ServerIron by means of a Dynamic Prefix (DP) trie. The key stored in the
DP trie is the associated maximum connection value. The choice of the DP trie for storing the client
subnet allows to define different prefix lengths and subnet masks for each client subnet. Since the
DP trie lookup returns the longest prefix match, it is not required that all configured client subnets
should have the same subnet mask.
Configuring the max connection limit per client consists of the following tasks:
• Configure the maximum connections allowed per client address or prefix
• Applying configured number of maximum connections to a specific VIP
Configure the maximum number of connections
1. Begin by creating a policy set or group by entering commands such as the following.
ServerIronADX(config)#client-connection-limit max-conn1
Syntax: [no] client-connection-limit <name>
Enter a name for the policy set or group for <name>.
Use the no form of the command to delete the policy group.
After creating a name, the CLI changes to the config-client-max-conn level.
2. Next, create the policy for maximum number of connections using one of the following
methods.
Create a policy for the maximum number of connections for specific clients
To set a maximum number of connections for a clients in a subnet, enter the a command such as
the following.
ServerIronADX(config)# client-connection-limit max-conn1
ServerIronADX(config-client-max-conn)# max-conn 100.1.1.0 255.255.255.0 10
In the example above, clients with IP addresses in the 100.1.1.0 subnet will be allowed only 10
connections.
Syntax: [no] max-conn [<client-ip-address> <client-subnet-mask> <max-connections>
Enter the clients’ IP address and subnet mask for <client-ip-address> <client-subnet-mask>
Enter a number from 0 to any value for <max-connections>. There is not default for this parameter.
Specifying a maximum number of connections for clients not specified in a policy
You can specify a default maximum number of connections for all clients that are not specified in
any max connection group by entering a command such as the following.










