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

100 ServerIron ADX Security Guide
53-1002440-03
Configuring NAT
4
Dynamic NAT configuration example 1
This section describes the Dynamic NAT configuration shown in Figure 6.
FIGURE 6 Minimum required commands
Figure 6 shows an example of a network using dynamic NAT on a ServerIron ADX ADX. The device is
acting as a gateway to connect a private network to the Internet. The private network, which can
also be considered as the inside network, is using IP addresses in the range of 10.10.1.2 -
10.10.1.254 with a 24-bit subnet mask.
The ServerIron ADX is connected to the Internet through a router. The outside interface of the
ServerIron ADX has a global IP address of 209.157.1.1. The ServerIron ADX also has a pool of
global IP addresses, which are used to map internal IP addresses.
Minimum required commands for dynamic NAT configuration.
1. Identify an internal and external interface on the ServerIron ADX. In this example, Ethernet 1/2
and 1/1 are used.
int eth 1/2
int eth 1/1
2. Assign IP addresses to the interfaces and define the outside and inside boundaries of the NAT
mechanism.
ServerIronADX(config)# int eth 1/2
ServerIronADX(config-if-1/2)# ip address 209.157.1.1/24
ServerIronADX(config-if-1/2)# ip nat outside
ServerIronADX(config-if-1/2)# int eth 1/1
ServerIronADX(config-if-1/1)# ip address 10.10.10.1/24
ServerIronADX(config-if-1/1)# ip nat inside
On Switch (S) code, enable NAT globally.
ServerIronADX(config)# ip nat inside
On Router (R) code, enable NAT on interfaces (both ip nat inside and outside should be
enabled). The interfaces can also be physical interfaces (not necessarily virtual interfaces).
Remote Server
63.253.63.50
Gateway
VE: 10.10.1/24 (Primary)
209.157.1.1/24 (Secondary)
ServerIron ADX
10.10.1.2
NAT pool IP:
209.157.1.2–209.157.1.30
PC
10.10.1.100
PC
10.10.1.101
Server
10.10.1.102
Server
10.10.1.103
Internet
ip nat inside source list 10 pool out_pool
ip nat pool out_pool 209.157.1.2 209.157.1.30 prefix-len
!
interface ethernet 2
SI ADX
ip address 10.10.1.2 255.255.255.0
ip default-gateway 10.10.1.1
ip nat inside
port-name To-gateway-router
!
interface ethernet 1
port-name Inside-Network
!
access-list 10 permit 10.10.1.0 0.0.0.255
!










