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 99
53-1002440-03
Configuring NAT
4
Configuring an address pool
Use the ip nat pool command to configure the address pool. For an example, refer to “Dynamic NAT
configuration example 1” on page 100.
Syntax: [no] ip nat pool <pool-name> <start-ip> <end-ip> netmask <ip-mask> | prefix-length
<length> | port-pool-range <priority-value>
The <pool-name> parameter specifies the name assigned to the pool. It can be up to 255
characters long and can contain special characters and internal blanks. If you use internal blanks,
you must use quotation marks around the entire name.
The <start-ip> parameter specifies the IP address at the beginning of the pool range. Specify the
lowest-numbered IP address in the range.
The <end-ip> parameter specifies the IP address at the end of the pool range. Specify the
highest-numbered IP address in the range.
NOTE
The address range cannot contain any gaps. Make sure you own all the IP addresses in the range.
If the range contains gaps, you must create separate pools containing only the addresses you own.
The netmask <ip-mask> | prefix-length <length> parameter specifies a classical sub-net mask
(example: netmask 255.255.255.0) or the length of a CIDR prefix (example: prefix-length 24). The
ServerIron ADX supports up to 255 global IP addresses.
The port-pool-range <priority-value> parameter enables dynamic NAT redundancy, where the
<priority-value> can be 1 or 2. A range value of 2 indicates higher priority for the NAT IP. A 2 value
also means the source ports allocated for the NAT IP are from the higher range.
Associating a range of private addresses with a pool and enabling PAT
Use ip nat inside source list to associate a private address range with a pool of Internet addresses
and enable PAT. For an example, refer to “Dynamic NAT configuration example 1” on page 100.
Syntax: [no] ip nat inside source list <acl-id> pool <pool-name>
The inside source keyword specifies that the translation applies to private addresses sending
traffic to the Internet (inside source).
The list <acl-id> parameter specifies a standard or extended ACL. Named ACLS are not supported
with NAT. You must use a numbered ACL.
The pool <pool-name> parameter specifies the pool name. You must create the pool before you
can use it with this command.
NAT configuration examples
The following sections provide both Dynamic and Static NAT configuration examples.
NOTE
A ServerIron ADX can have a maximum of 255 global IP addresses, in a single pool or multiple pools.