Note The NAT Exemption resource does not support disabling the TCP sequence number randomization feature:ASA2(config)# nat (dmz) 0 access-list NONAT norandomseqWARNING: norandomseq is not allowed with NAT 0.Tip The possibility of using the norandomseq option is one of the reasons for preferringthe Identity Static address publishing method over NAT Exemption. (Refer to Examples 8-17 and 8-19).Defining Connection Limits with NAT RulesThe ASA algorithm supports the definition of acceptable connection limits withinaddress translation statements. One key usage of this feature is the contention of Denialof Service (DoS) attacks to specific hosts (typically servers). DoS mitigation for clientside addresses is analyzed in Chapter 11, “Additional Protection Mechanisms.”Example 8-27 demonstrates how a limit for the number of simultaneous UDP connections can be defined for a host whose IP is being published with the static command. Theexample emphasizes that, after the configured number of 25 connections is reached, ASAstops accepting new requests.
đang được dịch, vui lòng đợi..
