Login
- Table of Contents
-
- 16-Security Command Reference
- 00-Preface
- 01-ACL commands
- 02-Time range commands
- 03-User profile commands
- 04-Password control commands
- 05-Public key management commands
- 06-PKI commands
- 07-IPsec commands
- 08-SSH commands
- 09-SSL commands
- 10-SSL VPN commands
- 11-Session management commands
- 12-Connection limit commands
- 13-Attack detection and prevention commands
- 14-IP source guard commands
- 15-ARP attack protection commands
- 16-ND attack defense commands
- 17-ASPF commands
- 18-Protocol packet rate limit commands
- 19-Crypto engine commands
- 20-Security policy commands
- 21-Object group commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 13-Attack detection and prevention commands | 566.85 KB |
Attack detection and prevention commands
attack-defense local apply policy
attack-defense login reauthentication-delay
attack-defense signature log non-aggregate
attack-defense tcp fragment enable
attack-defense top-attack-statistics enable
display attack-defense flood statistics ip
display attack-defense flood statistics ipv6
display attack-defense http-slow-attack statistics ip
display attack-defense http-slow-attack statistics ipv6
display attack-defense policy ip
display attack-defense policy ipv6
display attack-defense scan attacker ip
display attack-defense scan attacker ipv6
display attack-defense statistics interface
display attack-defense statistics local
display attack-defense top-attack-statistics
dns-reply-flood detect non-specific
dns-reply-flood source-threshold
http-flood detect non-specific
http-slow-attack detect non-specific
https-flood detect non-specific
icmp-flood detect non-specific
icmpv6-flood detect non-specific
reset attack-defense policy flood
reset attack-defense statistics interface
reset attack-defense statistics local
reset attack-defense top-attack-statistics
signature { large-icmp | large-icmpv6 } max-length
syn-ack-flood detect non-specific
syn-ack-flood source-threshold
threshold-learn auto-apply enable
threshold-learn tolerance-value
Attack detection and prevention commands
ack-flood action
Use ack-flood action to specify global actions against ACK flood attacks.
Use undo ack-flood action to restore the default.
Syntax
ack-flood action { drop | logging } *
undo ack-flood action
Default
No global action is specified for ACK flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent ACK packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent ACK packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for ACK flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log ACK flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ACK flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ACK flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against ACK flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] ack-flood action drop
Related commands
ack-flood detect
ack-flood detect non-specific
ack-flood source-threshold
ack-flood threshold
ack-flood detect
Use ack-flood detect to configure IP address-specific ACK flood attack detection.
Use undo ack-flood detect to remove IP address-specific ACK flood attack detection configuration.
Syntax
ack-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo ack-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific ACK flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for ACK packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected ACK flood attack. If no action is specified, the global actions set by the ack-flood action command apply.
drop: Drops subsequent ACK packets destined for the protected IP address.
logging: Enables logging for ACK flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With ACK flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of ACK packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure ACK flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log ACK flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ACK flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ACK flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure ACK flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] ack-flood detect ip 192.168.1.2 threshold 2000
Related commands
ack-flood action
ack-flood detect non-specific
ack-flood threshold
ack-flood detect non-specific
Use ack-flood detect non-specific to enable global ACK flood attack detection.
Use undo ack-flood detect non-specific to disable global ACK flood attack detection.
Syntax
ack-flood detect non-specific
undo ack-flood detect non-specific
Default
Global ACK flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following ACK flood attack prevention types:
· Source-based ACK flood attack prevention—Monitors the receiving rate of ACK packets on a per-source IP basis.
· Destination-based ACK flood attack prevention—Monitors the receiving rate of ACK packets on a per-destination IP basis.
The global ACK flood attack detection applies to all IP addresses except those specified by the ack-flood detect command. The global detection uses the global trigger threshold set by the ack-flood threshold or ack-flood source-threshold command and global actions specified by the ack-flood action command.
Examples
# Enable global ACK flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] ack-flood detect non-specific
Related commands
ack-flood action
ack-flood detect
ack-flood source-threshold
ack-flood threshold
ack-flood threshold
Use ack-flood threshold to set the global threshold for triggering destination-based ACK flood attack prevention.
Use undo ack-flood threshold to restore the default.
Syntax
ack-flood threshold threshold-value
undo ack-flood threshold
Default
The global threshold is 40000 for triggering destination-based ACK flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ACK packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based ACK flood attack prevention is disabled.
Usage guidelines
With global ACK flood attack detection configured, the device is in attack detection state. When the receiving rate of ACK packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global ACK flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of ACK packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based ACK flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] ack-flood threshold 100
Related commands
ack-flood action
ack-flood detect
ack-flood detect non-specific
ack-flood source-threshold
Use ack-flood source-threshold to set the global threshold for triggering source-based ACK flood attack prevention.
Use undo ack-flood source-threshold to restore the default.
Syntax
ack-flood source-threshold threshold-value
undo ack-flood source-threshold
Default
The global threshold is 40000 for triggering source-based ACK flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ACK packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based ACK flood attack prevention is disabled.
Usage guidelines
With global ACK flood attack detection configured, the device is in attack detection state. When the receiving rate of ACK packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based ACK flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] ack-flood source-threshold 100
Related commands
ack-flood action
ack-flood detect
ack-flood detect non-specific
attack-defense apply policy
Use attack-defense apply policy to apply an attack defense policy to an interface.
Use undo attack-defense apply policy to restore the default.
Syntax
attack-defense apply policy policy-name
undo attack-defense apply policy
Default
No attack defense policy is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
Usage guidelines
An interface can have only one attack defense policy applied. If you execute this command multiple times, the most recent configuration takes effect.
An attack defense policy can be applied to multiple interfaces.
Examples
# Apply attack defense policy atk-policy-1 to VLAN-interface 100.
<Sysname> system-view
[Sysname] interface vlan-interface 100
[Sysname-Vlan-interface100] attack-defense apply policy atk-policy-1
Related commands
attack-defense policy
display attack-defense policy
attack-defense local apply policy
Use attack-defense local apply policy to apply an attack defense policy to the device.
Use undo attack-defense local apply policy to restore the default.
Syntax
attack-defense local apply policy policy-name
undo attack-defense local apply policy
Default
No attack defense policy is applied to the device.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
Usage guidelines
An attack defense policy applied to the device itself detects packets destined for the device and prevents attacks targeted at the device.
Applying an attack defense policy to the device can improve the efficiency of processing attack packets destined for the device.
Each device can have only one attack defense policy applied. If you execute this command multiple times, the most recent configuration takes effect.
An attack defense policy can be applied to the device itself and to multiple interfaces.
If a device and its interfaces have attack defense policies applied, a packet destined for the device is processed as follows:
1. The policy applied to the receiving interface processes the packet.
2. If the packet is not dropped by the receiving interface, the policy applied to the device processes the packet.
Examples
# Apply attack defense policy atk-policy-1 to the device.
<Sysname> system-view
[Sysname] attack-defense local apply policy atk-policy-1
Related commands
attack-defense policy
display attack-defense policy
attack-defense login reauthentication-delay
Use attack-defense login reauthentication-delay to enable the login delay feature and set the delay period.
Use undo attack-defense login reauthentication-delay to restore the default.
Syntax
attack-defense login reauthentication-delay seconds
undo attack-defense login reauthentication-delay
Default
The login delay feature is disabled. The device does not delay accepting a login request from a user who has failed a login attempt.
Views
System view
Predefined user roles
network-admin
Parameters
seconds: Specifies the delay period in seconds, in the range of 4 to 60.
Usage guidelines
The login delay feature delays the device to accept a login request from a user after the user fails a login attempt. This feature can slow down login dictionary attacks.
The login delay feature is independent of the login attack prevention feature.
Examples
# Enable the login delay feature and set the delay period to 5 seconds.
[Sysname] attack-defense login reauthentication-delay 5
attack-defense policy
Use attack-defense policy to create an attack defense policy and enter its view, or enter the view of an existing attack defense policy.
Use undo attack-defense policy to delete an attack defense policy.
Syntax
attack-defense policy policy-name
undo attack-defense policy policy-name
Default
No attack defense policies exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Assigns a name to the attack defense policy. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
Usage guidelines
|
|
CAUTION: The default thresholds for triggering attack prevention might not be appropriate for your network. Set appropriate thresholds according to the actual application scenarios. Small thresholds might affect the Internet or webpage access speed. Large thresholds might make your network vulnerable to attacks. |
Examples
# Create attack defense policy atk-policy-1 and enter its view.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1]
Related commands
attack-defense apply policy
display attack-defense policy
attack-defense signature log non-aggregate
Use attack-defense signature log non-aggregate to enable log non-aggregation for single-packet attack events.
Use undo attack-defense signature log non-aggregate to restore the default.
Syntax
attack-defense signature log non-aggregate
undo attack-defense signature log non-aggregate
Default
Log non-aggregation is disabled for single-packet attack events.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Log aggregation aggregates multiple logs generated during a period of time and sends one log. Logs that are aggregated must have the following attributes in common:
· Location where the attacks are detected: device or interface.
· Attack type.
· Attack prevention action.
· Source and destination IP addresses.
As a best practice, do not disable log aggregation. A large number of logs will consume the display resources of the console.
Examples
# Enable log non-aggregation for single-packet attack events.
<Sysname> system-view
[Sysname] attack-defense signature log non-aggregate
Related commands
signature detect
attack-defense tcp fragment enable
Use attack-defense tcp fragment enable to enable TCP fragment attack prevention.
Use undo attack-defense tcp fragment enable to disable TCP fragment attack prevention.
Syntax
attack-defense tcp fragment enable
undo attack-defense tcp fragment enable
Default
TCP fragment attack prevention is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command enables the device to drop attack TCP fragments to prevent TCP fragment attacks that the packet filter cannot detect. As defined in RFC 1858, attack TCP fragments refer to the following TCP fragments:
· First fragments in which the TCP header is smaller than 20 bytes.
· Non-first fragments with a fragment offset of 8 bytes (FO=1).
TCP fragment attack prevention takes precedence over single-packet attack prevention. When both are used, incoming TCP packets are processed first by TCP fragment attack prevention and then by the single-packet attack defense policy.
Examples
# Enable TCP fragment attack prevention.
<Sysname> System-view
[Sysname] attack-defense tcp fragment enable
attack-defense top-attack-statistics enable
Use attack-defense top-attack-statistics enable to enable the top attack statistics ranking feature.
Use undo attack-defense top-attack-statistics enable to disable the top attack statistics ranking feature.
Syntax
attack-defense top-attack-statistics enable
undo attack-defense top-attack-statistics enable
Default
The top attack statistics ranking feature is disabled.
Views
System view.
Predefined user roles
network-admin
Usage guidelines
This feature collects statistics about number of dropped attack packets based on attacker, victim, and attack type and ranks the statistics by attacker and victim.
To display the top attack statistics, use the display attack-defense top-attack-statistics command.
Examples
# Enable the top attack statistics ranking feature.
<Sysname> system-view
[Sysname] attack-defense top-attack-statistics enable
Related commands
display attack-defense top-attack-statistics
display attack-defense flood statistics ip
Use display attack-defense flood statistics ip to display IPv4 flood attack detection and prevention statistics.
Syntax
display attack-defense { ack-flood | dns-flood | dns-reply-flood | fin-flood | flood | http-flood | https-flood | icmp-flood | rst-flood | sip-flood | syn-ack-flood | syn-flood | udp-flood } statistics ip [ ip-address ] [ interface interface-type interface-number | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ack-flood: Specifies ACK flood attack.
dns-flood: Specifies DNS flood attack.
dns-reply-flood: Specifies DNS response flood attack.
fin-flood: Specifies FIN flood attack.
flood: Specifies all IPv4 flood attacks.
http-flood: Specifies HTTP flood attack.
https-flood: Specifies HTTPS flood attack.
icmp-flood: Specifies ICMP flood attack.
rst-flood: Specifies RST flood attack.
sip-flood: Specifies SIP flood attack.
syn-ack-flood: Specifies SYN-ACK flood attack.
syn-flood: Specifies SYN flood attack.
udp-flood: Specifies UDP flood attack.
ip-address: Specifies a protected IPv4 address. If you do not specify an IPv4 address, this command displays flood attack detection and prevention statistics for all protected IPv4 addresses.
interface interface-type interface-number: Specifies an interface by its type and number.
local: Specifies the local device.
count: Displays the number of flood attack prevention entries.
Usage guidelines
The device collects statistics about protected IP addresses for flood attack detection and prevention. The attackers' IP addresses are not recorded.
If you do not specify the interface or local parameter, this command displays IPv4 flood attack detection and prevention statistics for all interfaces and the local device.
Examples
# Display all IPv4 flood attack detection and prevention statistics.
<Sysname> display attack-defense flood statistics ip
Dest IP VPN Detected on Detect type State PPS Dropped
201.55.7.45 -- GE1/0/1 SYN-ACK-FLOOD Normal 1000 111111111
192.168.11.5 -- GE1/0/2 ACK-FLOOD Normal 1000 222222222
Src IP VPN Detected on Detect type State PPS Dropped
201.55.7.44 -- Local DNS-FLOOD Normal 1000 111111111
192.168.11.4 -- Local ACK-FLOOD Normal 1000 22222222
192.168.8.41 -- Local SIP-FLOOD Normal 1000 125623489
# Display the number of flood attack prevention entries.
<Sysname> display attack-defense flood statistics ip count
Totally 2 flood destination entries.
Totally 3 flood source entries.
Table 1 Command output
|
Field |
Description |
|
Dest IP |
Destination IPv4 address in attack packets. |
|
Src IP |
Source IPv4 address in attack packets. |
|
VPN |
This field is not supported in the current software version. MPLS L3VPN instance to which the protected IPv4 address belongs. If the protected IPv4 address is on the public network, this field displays hyphens (--). |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
Detect type |
Type of the detected flood attack: · ACK flood. · DNS flood. · DNS reply flood. · FIN flood. · ICMP flood. · ICMPv6 flood. · SYN flood. · SYN-ACK flood. · UDP flood. · RST flood. · HTTP flood. · SIP flood. · HTTPS flood. |
|
State |
Whether the interface or device is attacked: · Attacked—It is being attacked. · Normal—It is not attacked. |
|
PPS |
Number of packets sent to the IPv4 address per second. |
|
Dropped |
Number of attack packets dropped by the interface or the device. |
|
Totally 2 flood destination entries |
Total number of IPv4 destination-based flood attack prevention entries. |
|
Totally 2 flood source entries |
Total number of IPv4 source-based flood attack prevention entries. |
display attack-defense flood statistics ipv6
Use display attack-defense flood statistics ipv6 to display IPv6 flood attack detection and prevention statistics.
Syntax
display attack-defense { ack-flood | dns-flood | dns-reply-flood | fin-flood | flood | http-flood | https-flood | icmpv6-flood | rst-flood | sip-flood | syn-ack-flood | syn-flood | udp-flood } statistics ipv6 [ ipv6-address ] [ interface interface-type interface-number | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ack-flood: Specifies ACK flood attack.
dns-flood: Specifies DNS flood attack.
dns-reply-flood: Specifies DNS response flood attack.
fin-flood: Specifies FIN flood attack.
flood: Specifies all IPv6 flood attacks.
http-flood: Specifies HTTP flood attack.
https-flood: Specifies HTTPS flood attack.
icmpv6-flood: Specifies ICMPv6 flood attack.
rst-flood: Specifies RST flood attack.
sip-flood: Specifies SIP flood attack.
syn-ack-flood: Specifies SYN-ACK flood attack.
syn-flood: Specifies SYN flood attack.
udp-flood: Specifies UDP flood attack.
ipv6-address: Specifies a protected IPv6 address. If you do not specify an IPv6 address, this command displays flood attack detection and prevention statistics for all protected IPv6 addresses.
interface interface-type interface-number: Specifies an interface by its type and number.
local: Specifies the local device.
count: Displays the number of flood attack prevention entries.
Usage guidelines
The device collects statistics about protected IP addresses for flood attack detection and prevention. The attackers' IP addresses are not recorded.
If you do not specify the interface or local parameter, this command displays IPv6 flood attack detection and prevention statistics for all interfaces and the local device.
Examples
# Display all IPv6 flood attack detection and prevention statistics.
<Sysname> display attack-defense flood statistics ipv6
Dest IPv6 VPN Detected on Detect type State PPS Dropped
1::2 -- GE1/0/1 DNS-FLOOD Normal 1000 111111111
1::3 -- GE1/0/2 SYN-ACK-FLOOD Normal 1000 222222222
Src IPv6 VPN Detected on Detect type State PPS Dropped
1::4 -- Local ACK-FLOOD Normal 1000 111111111
1::5 -- Local SYN-FLOOD Normal 1000 22222222
17::14 -- Local SIP-FLOOD Normal 1000 264549789
# Display the number of flood attack prevention entries.
<Sysname> display attack-defense flood statistics ipv6 count
Totally 2 flood destination entries.
Totally 3 flood source entries.
Table 2 Command output
|
Field |
Description |
|
Dest IPv6 |
Destination IPv6 address in attack packets. |
|
Src IPv6 |
Source IPv6 address in attack packets. |
|
VPN |
This field is not supported in the current software version. MPLS L3VPN instance to which the protected IPv6 address belongs. If the protected IPv6 address is on the public network, this field displays hyphens (--). |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
Detect type |
Type of the detected flood attack: · ACK flood. · DNS flood. · DNS reply flood. · FIN flood. · ICMPv6 flood. · SYN flood. · SYN-ACK flood. · UDP flood. · RST flood. · HTTP flood. · SIP flood. · HTTPS flood. |
|
State |
Whether the interface or device is attacked: · Attacked—It is being attacked. · Normal—It is not attacked. |
|
PPS |
Number of packets sent to the IPv6 address per second. |
|
Dropped |
Number of attack packets dropped by the interface or the device. |
|
Totally 4 flood destination entries |
Total number of IPv6 destination-based flood attack prevention entries. |
|
Totally 2 flood source entries |
Total number of IPv6 source-based flood attack prevention entries. |
display attack-defense http-slow-attack statistics ip
Use display attack-defense http-slow-attack statistics ip to display statistics about IPv4 HTTP slow attack detection and prevention.
Syntax
display attack-defense http-slow-attack statistics ip [ ip-address ] [ interface { interface-type interface-number | interface-name } | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ip-address: Specifies a destination IPv4 address.
interface { interface-type interface-number | interface-name }: Specifies an interface. The interface-type argument specifies the interface type. The interface-number argument specifies the interface number, and the interface-name argument specifies the interface name.
local: Specifies the local device.
count: Displays the number of IPv4 HTTP slow attack prevention entries for matching protected IPv4 addresses.
Usage guidelines
If you do not specify the interface or local parameter, this command displays statistics about IPv4 HTTP slow attack detection and prevention for all interfaces and the local device.
Examples
# Display statistics about IPv4 HTTP slow attack detection and prevention.
<Sysname> display attack-defense http-slow-attack statistics ip
IP address VPN Detected on State
192.168.11.4 asd Local Normal
201.55.7.44 -- GE1/0/2 Normal
# Display the number of IPv4 HTTP slow attack prevention entries for protected IPv4 addresses.
<Sysname> display attack-defense http-slow-attack statistics ip count
Totally 2 HTTP slow attack entries.
Table 3 Command output
|
Field |
Description |
|
IP address |
Destination IPv4 address. |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
State |
Whether the interface or device is attacked: · Attacked—It is being attacked. · Normal—It is not attacked. |
|
Totally 2 http slow attack entries |
Total number of IPv4 HTTP slow attack prevention entries. |
display attack-defense http-slow-attack statistics ipv6
Use display attack-defense http-slow-attack statistics ipv6 to display statistics about IPv6 HTTP slow attack detection and prevention.
Syntax
display attack-defense http-slow-attack statistics ipv6 [ ipv6-address ] [ interface { interface-type interface-number | interface-name } | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6-address: Specifies a destination IPv6 address.
interface { interface-type interface-number | interface-name }: Specifies an interface. The interface-type argument specifies the interface type. The interface-number argument specifies the interface number, and the interface-name argument specifies the interface name.
local: Specifies the local device.
count: Displays the number of IPv6 HTTP slow attack prevention entries for matching protected IPv6 addresses.
Usage guidelines
If you do not specify the interface or local parameter, this command displays statistics about IPv6 HTTP slow attack detection and prevention for all interfaces and the local device.
Examples
# Display statistics about IPv6 HTTP slow attack detection and prevention.
<Sysname> display attack-defense http-slow-attack statistics ipv6
IPv6 address VPN Detected on State
1::5 asd Local Normal
17::14 -- GE1/0/2 Normal
# Display the number of IPv6 HTTP slow attack prevention entries for protected IPv6 addresses.
<Sysname> display attack-defense http-slow-attack statistics ipv6 count
Totally 5 HTTP slow attack entries.
Table 4 Command output
|
Field |
Description |
|
IPv6 address |
Destination IPv6 address. |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
State |
Whether the interface or local device is attacked: · Attacked—It is being attacked. · Normal—It is not attacked. |
|
Totally 2 HTTP slow attack entries |
Total number of IPv6 HTTP slow attack prevention entries. |
display attack-defense policy
Use display attack-defense policy to display attack defense policy configuration.
Syntax
display attack-defense policy [ policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-). If no attack defense policy is specified, this command displays brief information about all attack defense policies.
Usage guidelines
This command output includes the following configuration information about an attack defense policy:
· Whether attack detection is enabled.
· Attack prevention actions.
· Attack prevention trigger thresholds.
Examples
# Display the configuration of attack defense policy abc.
<Sysname> display attack-defense policy abc
Attack-defense Policy Information
--------------------------------------------------------------------------
Policy name : abc
Applied list : Local
GE1/0/1
Vlan1
--------------------------------------------------------------------------
Exempt IPv4 ACL: : Not configured
Exempt IPv6 ACL: : vip
--------------------------------------------------------------------------
Actions: CV-Client verify BS-Block source L-Logging D-Drop N-None
Signature attack defense configuration:
Signature name Defense Level Actions
Fragment Enabled Info L
Impossible Enabled Info L
Teardrop Disabled Info L
Tiny fragment Disabled Info L
IP option abnormal Disabled Info L
Smurf Disabled Info N
Traceroute Disabled Medium L,D
Ping of death Disabled Low L
Large ICMP Disabled Medium L,D
Max length 4000 bytes
Large ICMPv6 Disabled Low L
Max length 4000 bytes
TCP invalid flags Disabled medium L,D
TCP null flag Disabled Low L
TCP all flags Enabled Info L
TCP SYN-FIN flags Disabled Info L
TCP FIN only flag Enabled Info L
TCP Land Disabled Info L
Winnuke Disabled Info L
UDP Bomb Disabled Info L
UDP Snork Disabled Info L
UDP Fraggle Enabled Info L
IP option record route Disabled Info L
IP option internet timestamp Enabled Info L
IP option security Disabled Info L
IP option loose source routing Enabled Info L
IP option stream ID Disabled Info L
IP option strict source routing Disabled Info L
IP option route alert Disabled Info L
ICMP echo request Disabled Info L
ICMP echo reply Disabled Info L
ICMP source quench Disabled Info L
ICMP destination unreachable Enabled Info L
ICMP redirect Enabled Info L
ICMP time exceeded Enabled Info L
ICMP parameter problem Disabled Info L
ICMP timestamp request Disabled Info L
ICMP timestamp reply Disabled Info L
ICMP information request Disabled Info L
ICMP information reply Disabled Medium L,D
ICMP address mask request Disabled Medium L,D
ICMP address mask reply Disabled Medium L,D
ICMPv6 echo request Enabled Medium L,D
ICMPv6 echo reply Disabled Medium L,D
ICMPv6 group membership query Disabled Medium L,D
ICMPv6 group membership report Disabled Medium L,D
ICMPv6 group membership reduction Disabled Medium L,D
ICMPv6 destination unreachable Enabled Medium L,D
ICMPv6 time exceeded Enabled Medium L,D
ICMPv6 parameter problem Disabled Medium L,D
ICMPv6 packet too big Disabled Medium L,D
IPv6 extension header abnormal Disabled Info L
IPv6 extension header exceeded Disabled Info L
Limit 7
Scan attack defense configuration:
Preset defense:
Defense: Disabled
User-defined defense:
Port scan defense: Enabled
Port scan defense threshold: 5000 packets
IP sweep defense: Enabled
IP sweep defense threshold: 8000 packets
Period: 100s
Actions: L
Flood type Global dest/src thres(pps) Global actions Service ports Non-specific
DNS flood 1000/1000 - 53 Disabled
DNS reply flood 1000/1000 - - Disabled
HTTP flood 1000/1000 80 - Disabled
SIP flood 1000/1000 50 - Enabled
HTTPS flood 1000/1000 - 443 Disabled
SYN flood 1000/1000 - - Disabled
ACK flood 1000/1000 - - Disabled
SYN-ACK flood 1000/1000 - - Disabled
RST flood 1000/1000 - - Disabled
FIN flood 1000/1000 - - Disabled
UDP flood 1000/1000 - - Disabled
ICMP flood 1000/1000 - - Disabled
ICMPv6 flood 1000/1000 - - Enabled
Flood attack defense for protected IP addresses:
Address VPN instance Flood type Thres(pps) Actions Ports
1::1 -- FIN-FLOOD 10 L,D -
192.168.1.1 -- SYN-ACK-FLOOD 10 - -
1::1 -- FIN-FLOOD - L -
HTTP slow attack defense configuration:
Non-specific: Enabled
Global threshold:
Alert-number: 1200000
Content-length: 100000000
Payload-length: 1000
Packet-number: 1000
Global period: 1200 seconds
Global action: L, BS (1000)
Ports: 80, 8000 to 8001
Threshold: AN-Alert number, CL-Content length, PL-Payload length, PN-Packet number
HTTP slow attack defense configuration for protected IP addresses:
Address VPN instance Threshold (AN/CL/PL/PN) Period Actions Ports
1111:2222:3333:4 abcdefghigkl 1200000,100000000,1000,1000 1000 L,BS(10) 80
444::8888 mnopqrstuvwx
yz
Table 5 Command output
|
Field |
Description |
|
Policy name |
Name of the attack defense policy. |
|
Applied list |
Locations to which the attack defense policy is applied: interfaces and Local (Local indicates that the policy is applied to the device). |
|
Exempt IPv4 ACL |
IPv4 ACL used for attack detection exemption. |
|
Exempt IPv6 ACL |
IPv6 ACL used for attack detection exemption. |
|
Actions |
Attack prevention actions: · CV—Client verification. This field is not supported in the current software version. · BS—Blocking sources. This field is not supported in the current software version. · L—Logging. · D—Dropping packets. · N—No action. |
|
Signature attack defense configuration |
Configuration information about single-packet attack detection and prevention. |
|
Signature name |
Type of the single-packet attack. |
|
Defense |
Whether attack detection is enabled. |
|
Level |
Level of the single-packet attack, info, low, medium, or high. Currently, no high-level single-packet attacks exist. |
|
Actions |
Prevention actions against the scanning attack: · L—Logging. · D—Dropping packets. · N—No action. |
|
Large ICMPv6 |
Large ICMPv6 attack. |
|
ICMPv6 echo request |
ICMPv6 echo request attack. |
|
ICMPv6 echo reply |
ICMPv6 echo reply attack. |
|
ICMPv6 group membership query |
ICMPv6 group membership query attack. |
|
ICMPv6 group membership report |
ICMPv6 group membership report attack. |
|
ICMPv6 group membership reduction |
ICMPv6 group membership reduction attack. |
|
ICMPv6 destination unreachable |
ICMPv6 destination unreachable attack. |
|
ICMPv6 time exceeded |
ICMPv6 time exceeded attack. |
|
ICMPv6 parameter problem |
ICMPv6 parameter problem attack. |
|
ICMPv6 packet too big |
ICMPv6 packet too big attack. |
|
IPv6 extension header abnormal |
Abnormal IPv6 extension header attack. |
|
Limit |
Upper limit of IPv6 extension headers. |
|
Scan attack defense configuration |
Configuration information about scanning attack detection and prevention. |
|
Preset defense |
Configuration information about predefined scanning attack detection and prevention. |
|
Defense |
Whether scanning attack detection is enabled. |
|
Level |
Level of the scanning attack detection, low, medium, or high. |
|
User-defined defense |
Configuration information about user-defined scanning attack detection and prevention. |
|
Port scan defense |
Status of port scan attack prevention, which can be Enabled or Disabled. |
|
Port scan defense threshold |
Threshold for triggering port scan attack prevention. |
|
IP sweep defense |
Status of IP sweep attack prevention, which can be Enabled or Disabled. |
|
IP sweep defense threshold |
Threshold for triggering IP sweep attack prevention. |
|
Period |
Scanning attack detection cycle in seconds. |
|
Actions |
Scanning attack prevention actions: · BS—Blocking sources. This field is not supported in the current software version. · D—Dropping packets. · L—Logging. |
|
Flood attack defense configuration |
Configuration information about flood attack detection and prevention. |
|
Flood type |
Type of the flood attack: · ACK flood. · DNS flood. · DNS reply flood. · FIN flood. · ICMP flood. · ICMPv6 flood. · SYN flood. · SYN-ACK flood. · UDP flood. · RST flood. · HTTP flood. · SIP flood. · HTTPS flood. |
|
Global dest/src thres(pps) |
Global thresholds for triggering the destination-based and source-based flood attack prevention. The default is 1000 pps. |
|
Global actions |
Global prevention actions against the flood attack: · D—Dropping packets. · L—Logging. · CV—Client verification. This field is not supported in the current software version. If no actions are configured, this field displays a hyphen (-). |
|
Service ports |
Ports that are protected against the flood attack. This field displays port numbers only for the DNS and HTTP flood attacks. For other flood attacks, this field displays a hyphen (-). |
|
Non-specific |
Whether the global flood attack detection is enabled. |
|
Flood attack defense for protected IP addresses |
Configuration of the IP address-specific flood attack detection and prevention. |
|
Address |
Protected IP address. |
|
VPN instance |
This field is not supported in the current software version. MPLS L3VPN instance to which the protected IP address belongs. If no MPLS L3VPN instance is specified, this field is not displayed. |
|
Thres(pps) |
Threshold for triggering the flood attack prevention, in units of packets sent to the IP address per second. If no threshold is specified, this field displays 1000. |
|
Actions |
Flood attack prevention actions: · CV—Client verification. This field is not supported in the current software version. · BS—Blocking sources. This field is not supported in the current software version. · D—Dropping packets. · L—Logging. · N—No action. |
|
Ports |
Ports that are protected against the flood attack. This field displays port numbers only for the DNS and HTTP flood attacks. For other flood attacks, this field displays a hyphen (-). |
|
HTTP slow attack defense configuration |
Configuration information about the global HTTP slow attack detection and prevention. |
|
Non-specific |
Whether global HTTP slow attack detection is enabled. |
|
Global threshold |
Global threshold settings: · Alert-number—HTTP concurrent connection threshold. If this threshold is not specified, the field displays 5000. · Content-length—Threshold for the Content-Length field value. If this threshold is not specified, the field displays 10000. · Payload-length—Payload size threshold. If this threshold is not specified, the field displays 50. · Packet-number—Threshold of abnormal packets. If this threshold is not specified, the field displays 10. |
|
Global period |
Global HTTP slow attack detection period. |
|
Global action |
Global HTTP slow attack prevention actions: · BS—Blocking sources. This value is not supported in the current software version. · L—Logging. |
|
Ports |
Ports protected by the global HTTP slow attack prevention. If protected no ports are specified, the field displays 80. |
|
HTTP slow attack defense configuration for protected IP addresses |
Configuration of the IP address-specific HTTP slow attack detection and prevention. |
|
Address |
Protected IP address. |
|
VPN instance |
This field is not supported in the current software version. VPN instance to which the protected IP address belongs. If no VPN instance is specified, this field is not displayed. |
|
Threshold (AN/CL/PL/PN) |
Threshold parameter settings for IP address-specific HTTP slow attack detection. Full spellings for threshold parameters are as follows: · AN—Alert number. · CL—Content length. · PL—Payload length. · PN—Packet number. If a parameter threshold is not specified, the global threshold for this parameter is displayed. |
|
Period |
IP address-specific HTTP slow attack detection period. If this period is not specified, the field displays the global detection period. |
|
Actions |
IP address-specific HTTP slow attack prevention actions: · BS—Blocking sources. · L—Logging. If no actions are specified, this field displays the global prevention actions. |
|
Ports |
Ports protected by the IP address-specific HTTP slow attack prevention. If no ports are specified, the field displays ports protected by the global HTTP slow attack prevention. |
# Display brief information about all attack defense policies.
<Sysname> display attack-defense policy
Attack-defense Policy Brief Information
------------------------------------------------------------
Policy Name Applied list
Atk-policy-1 GigabitEthernet1/0/1
GigabitEthernet1/0/2
P123 GigabitEthernet1/0/2
p1 Local
p12 Local
Table 6 Command output
|
Field |
Description |
|
Policy name |
Name of the attack defense policy. |
|
Applied list |
Locations to which the attack defense policy is applied: interfaces and Local (Local indicates that the policy is applied to the device). |
Related commands
attack-defense policy
display attack-defense policy ip
Use display attack-defense policy ip to display information about IPv4 addresses protected by flood attack detection and prevention.
Syntax
display attack-defense policy policy-name { ack-flood | dns-flood | dns-reply-flood | fin-flood | flood | http-flood | https-flood | icmp-flood | rst-flood | sip-flood | syn-ack-flood | syn-flood | udp-flood } ip [ ip-address ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
ack-flood: Specifies ACK flood attack.
dns-flood: Specifies DNS flood attack.
dns-reply-flood: Specifies DNS response flood attack.
fin-flood: Specifies FIN flood attack.
flood: Specifies all IPv4 flood attacks.
http-flood: Specifies HTTP flood attack.
https-flood: Specifies HTTPS flood attack.
icmp-flood: Specifies ICMP flood attack.
rst-flood: Specifies RST flood attack.
sip-flood: Specifies SIP flood attack.
syn-ack-flood: Specifies SYN-ACK flood attack.
syn-flood: Specifies SYN flood attack.
udp-flood: Specifies UDP flood attack.
ip-address: Specifies a protected IPv4 address. If you do not specify an IPv4 address, this command displays information about all protected IPv4 addresses.
count: Displays the number of matching IPv4 addresses protected by flood attack detection and prevention.
Examples
# Display information about all IPv4 addresses protected by flood attack detection and prevention in attack defense policy abc.
<Sysname> display attack-defense policy abc flood ip
IP address VPN instance Type Rate threshold(PPS) Dropped
123.123.123.123 -- SYN-ACK-FLOOD 100 4294967295
201.55.7.45 -- ICMP-FLOOD 100 10
192.168.11.5 -- DNS-FLOOD 23 100
10.168.200.5 -- SIP-FLOOD 100 102556
# Display the number of IPv4 addresses protected by flood attack detection and prevention in attack defense policy abc.
<Sysname> display attack-defense policy abc flood ip count
Totally 3 flood protected IP addresses.
Table 7 Command output
|
Field |
Description |
|
Totally 3 flood protected IP addresses |
Total number of the IPv4 addresses protected by flood attack detection and prevention. |
|
IP address |
Protected IPv4 address. |
|
VPN instance |
This field is not supported in the current software version. MPLS L3VPN instance to which the protected IPv4 address belongs. If the protected IPv4 address is on the public network, this field is not displayed. |
|
Type |
Type of the flood attack. |
|
Rate threshold(PPS) |
Threshold for triggering the flood attack prevention, in units of packets sent to the IP address per second. If no rate threshold is set, this field displays 1000. |
|
Dropped |
Number of dropped attack packets. If the prevention action is logging, this field displays 0. |
display attack-defense policy ipv6
Use display attack-defense policy ipv6 to display information about IPv6 addresses protected by flood attack detection and prevention.
Syntax
display attack-defense policy policy-name { ack-flood | dns-flood | dns-reply-flood | fin-flood | flood | http-flood | https-flood | icmpv6-flood | rst-flood | sip-flood | syn-ack-flood | syn-flood | udp-flood } ipv6 [ ipv6-address ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
ack-flood: Specifies ACK flood attack.
dns-flood: Specifies DNS flood attack.
dns-reply-flood: Specifies DNS response flood attack.
fin-flood: Specifies FIN flood attack.
flood: Specifies all IPv6 flood attacks.
http-flood: Specifies HTTP flood attack.
https-flood: Specifies HTTPS flood attack.
icmpv6-flood: Specifies ICMPv6 flood attack.
rst-flood: Specifies RST flood attack.
sip-flood: Specifies SIP flood attack.
syn-ack-flood: Specifies SYN-ACK flood attack.
syn-flood: Specifies SYN flood attack.
udp-flood: Specifies UDP flood attack.
ipv6-address: Specifies a protected IPv6 address. If you do not specify an IPv6 address, this command displays information about all protected IPv6 addresses.
count: Displays the number of matching IPv6 addresses protected by flood attack detection and prevention.
Examples
# Display information about all IPv6 addresses protected by flood attack detection and prevention in attack defense policy abc.
<Sysname> display attack-defense policy abc flood ipv6
IPv6 address VPN instance Type Rate threshold(PPS) Dropped
2013::127f -- SYN-ACK-FLOOD 100 4294967295
2::5 -- ACK-FLOOD 100 10
1::5 -- ACK-FLOOD 100 23
10::15 -- SIP-FLOOD 100 1002
# Display the number of IPv6 addresses protected by flood attack detection and prevention in attack defense policy abc.
<Sysname> display attack-defense policy abc flood ipv6 count
Totally 3 flood protected IP addresses.
Table 8 Command output
|
Field |
Description |
|
Totally 3 flood protected IP addresses |
Total number of the IPv6 addresses protected by flood attack detection and prevention. |
|
IPv6 address |
Protected IPv6 address. |
|
VPN instance |
This field is not supported in the current software version. MPLS L3VPN instance to which the protected IPv6 address belongs. If the protected IPv6 address is on the public network, this field is not displayed. |
|
Type |
Type of the flood attack. |
|
Rate threshold(PPS) |
Threshold for triggering the flood attack prevention, in units of packets sent to the IPv6 address per second. If no rate threshold is set, this field displays 1000. |
|
Dropped |
Number of dropped attack packets. If the prevention action is logging, this field displays 0. |
display attack-defense scan attacker ip
Use display attack-defense scan attacker ip to display information about IPv4 scanning attackers.
Syntax
display attack-defense scan attacker ip [ interface interface-type interface-number | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number.
local: Specifies the local device.
count: Displays the number of matching IPv4 scanning attackers.
Usage guidelines
If you do not specify any parameters, this command displays information about all IPv4 scanning attackers.
Examples
# Display information about all IPv4 scanning attackers.
<Sysname> display attack-defense scan attacker ip
IP addr(DslitePeer) VPN instance Protocol Detected on Duration(min)
192.168.31.2(--) -- TCP GE1/0/2 1284
2.2.2.3(--) -- UDP GE1/0/2 23
192.68.11.2(--) -- TCP Local 782
2.2.2.1(--) -- UDP Local 23
# Display the number of IPv4 scanning attackers.
<Sysname> display attack-defense scan attacker ip count
Totally 3 attackers.
Table 9 Command output
|
Field |
Description |
|
Totally 3 attackers |
Total number of IPv4 scanning attackers. |
|
IP addr(DslitePeer) |
The IP addr field displays the IPv4 address of the attacker. The DslitePeer field displays the DS-Lite tunnel source IPv6 address of the attacker in a DS-Lite network. In other situations, this field displays hyphens (--). |
|
VPN instance |
This field is not supported in the current software version. MPLS L3VPN instance to which the attacker's IPv4 address belongs. If the IPv4 address is on the public network, this field is not displayed. |
|
Protocol |
Name of the protocol. |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
Duration(min) |
The amount of time the attack lasts, in minutes. |
Related commands
scan detect
display attack-defense scan attacker ipv6
Use display attack-defense scan attacker ipv6 to display information about IPv6 scanning attackers.
Syntax
display attack-defense scan attacker ipv6 [ interface interface-type interface-number | local ] [ count ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number.
local: Specifies the local device.
count: Displays the number of matching IPv6 scanning attackers.
Usage guidelines
If you do not specify any parameters, this command displays information about all IPv6 scanning attackers.
Examples
# Display information about all IPv6 scanning attackers.
<Sysname> display attack-defense scan attacker ipv6
IPv6 address VPN instance Protocol Detected on Duration(min)
2013::2 -- TCP GE1/0/1 1234
1230::22 -- UDP GE1/0/2 10
1002::20 -- TCP Local 782
1230::1 -- UDP Local 10
# Display the number of IPv6 scanning attackers.
<Sysname> display attack-defense scan attacker ipv6 count
Totally 3 attackers.
Table 10 Command output
|
Field |
Description |
|
Totally 3 attackers |
Total number of IPv6 scanning attackers. |
|
IPv6 address |
IPv6 address of the attacker. |
|
VPN instance |
This field is not supported in the current software version. MPLS L3VPN instance to which the attacker IPv6 address belongs. If the attacker IPv6 address is on the public network, this field is not displayed. |
|
Protocol |
Name of the protocol. |
|
Detected on |
Where the attack is detected: the device (Local) or an interface. |
|
Duration(min) |
The amount of time the attack lasts, in minutes. |
Related commands
scan detect
display attack-defense statistics interface
Use display attack-defense statistics interface to display attack detection and prevention statistics on an interface.
Syntax
display attack-defense statistics interface interface-type interface-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Examples
# Display attack detection and prevention statistics on GigabitEthernet 1/0/1.
<Sysname> display attack-defense statistics interface gigabitethernet 1/0/1
Attack policy name: abc
Scan attack defense statistics:
AttackType AttackTimes Dropped
Port scan 2 23
IP sweep 3 33
Distribute port scan 1 10
Flood attack defense statistics:
AttackType AttackTimes Dropped
SYN flood 1 0
ACK flood 1 0
SYN-ACK flood 3 5000
RST flood 2 0
FIN flood 2 0
UDP flood 1 0
ICMP flood 1 0
ICMPv6 flood 1 0
DNS flood 1 0
DNS reply flood 1 0
HTTP flood 1 0
SIP flood 1 1000
HTTPS flood 1 0
HTTP slow attack defense statistics:
AttackType AttackTimes
HTTP slow attack 1
Signature attack defense statistics:
AttackType AttackTimes Dropped
IP option record route 1 100
IP option security 2 0
IP option stream ID 3 0
IP option internet timestamp 4 1
IP option loose source routing 5 0
IP option strict source routing 6 0
IP option route alert 3 0
Fragment 1 0
Impossible 1 1
Teardrop 1 1
Tiny fragment 1 0
IP options abnormal 3 0
Smurf 1 0
Ping of death 1 0
Traceroute 1 0
Large ICMP 1 0
TCP NULL flag 1 0
TCP all flags 1 0
TCP SYN-FIN flags 1 0
TCP FIN only flag 1 0
TCP invalid flag 1 0
TCP Land 1 0
Winnuke 1 0
UDP Bomb 1 0
Snork 1 0
Fraggle 1 0
Large ICMPv6 1 0
ICMP echo request 1 0
ICMP echo reply 1 0
ICMP source quench 1 0
ICMP destination unreachable 1 0
ICMP redirect 2 0
ICMP time exceeded 3 0
ICMP parameter problem 4 0
ICMP timestamp request 5 0
ICMP timestamp reply 6 0
ICMP information request 7 0
ICMP information reply 4 0
ICMP address mask request 2 0
ICMP address mask reply 1 0
ICMPv6 echo request 1 1
ICMPv6 echo reply 1 1
ICMPv6 group membership query 1 0
ICMPv6 group membership report 1 0
ICMPv6 group membership reduction 1 0
ICMPv6 destination unreachable 1 0
ICMPv6 time exceeded 1 0
ICMPv6 parameter problem 1 0
ICMPv6 packet too big 1 0
IPv6 extension header abnormal 1 0
IPv6 extension header exceeded 1 0
Table 11 Command output
|
Field |
Description |
|
AttackType |
Type of the attack. |
|
AttackTimes |
Number of times that the attack occurred. This command output displays only attacks that are detected. |
|
Dropped |
Number of dropped packets. |
|
ICMPv6 flood |
ICMPv6 flood attack. This field is not displayed when no ICMPv6 flood attack is detected. |
|
Large ICMPv6 |
Large ICMPv6 attack. This field is not displayed when no large ICMPv6 attack is detected. |
|
ICMPv6 echo request |
ICMPv6 echo request attack. This field is not displayed when no ICMPv6 echo request attack is detected. |
|
ICMPv6 echo reply |
ICMPv6 echo reply attack. This field is not displayed when no ICMPv6 echo reply attack is detected. |
|
ICMPv6 group membership query |
ICMPv6 group membership query attack. This field is not displayed when no ICMPv6 group membership query attack is detected. |
|
ICMPv6 group membership report |
ICMPv6 group membership report attack. This field is not displayed when no ICMPv6 group membership report attack is detected. |
|
ICMPv6 group membership reduction |
ICMPv6 group membership reduction attack. This field is not displayed when no ICMPv6 group membership reduction attack is detected. |
|
ICMPv6 destination unreachable |
ICMPv6 destination unreachable attack. This field is not displayed when no ICMPv6 destination unreachable attack is detected. |
|
ICMPv6 time exceeded |
ICMPv6 time exceeded attack. This field is not displayed when no ICMPv6 time exceeded attack is detected. |
|
ICMPv6 parameter problem |
ICMPv6 parameter problem attack. This field is not displayed when no ICMPv6 parameter problem attack is detected. |
|
ICMPv6 packet too big |
ICMPv6 packet too big attack. This field is not displayed when no ICMPv6 packet too big attack is detected. |
|
IPv6 extension header abnormal |
Abnormal IPv6 extension header attack. This field is not displayed when no abnormal IPv6 extension header attack is detected. |
|
IPv6 extension header exceeded |
IPv6 extension header exceeded attack. This field is not displayed when no IPv6 extension header exceeded attack is detected. |
Related commands
reset attack-defense statistics interface
display attack-defense statistics local
Use display attack-defense statistics local to display attack detection and prevention statistics for the device.
Syntax
display attack-defense statistics local
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display attack detection and prevention statistics for the device.
<Sysname> display attack-defense statistics local
Attack defense policy name: abc
Scan attack defense statistics:
AttackType AttackTimes Dropped
Port scan 2 23
IP sweep 3 33
Distribute port scan 1 10
Flood attack defense statistics:
AttackType AttackTimes Dropped
SYN flood 1 0
ACK flood 1 0
SYN-ACK flood 3 5000
RST flood 2 0
FIN flood 2 0
UDP flood 1 0
ICMP flood 1 0
ICMPv6 flood 1 0
DNS flood 1 0
DNS reply flood 1 0
HTTP flood 1 0
SIP flood 1 1000
HTTPS flood 1 0
HTTP slow attack defense statistics:
AttackType AttackTimes
HTTP slow attack 1
Signature attack defense statistics:
AttackType AttackTimes Dropped
IP option record route 1 100
IP option security 2 0
IP option stream ID 3 0
IP option internet timestamp 4 1
IP option loose source routing 5 0
IP option strict source routing 6 0
IP option route alert 3 0
Fragment 1 0
Impossible 1 1
Teardrop 1 1
Tiny fragment 1 0
IP options abnormal 3 0
Smurf 1 0
Ping of death 1 0
Traceroute 1 0
Large ICMP 1 0
TCP NULL flag 1 0
TCP all flags 1 0
TCP SYN-FIN flags 1 0
TCP FIN only flag 1 0
TCP invalid flag 1 0
TCP Land 1 0
Winnuke 1 0
UDP Bomb 1 0
Snork 1 0
Fraggle 1 0
Large ICMPv6 1 0
ICMP echo request 1 0
ICMP echo reply 1 0
ICMP source quench 1 0
ICMP destination unreachable 1 0
ICMP redirect 2 0
ICMP time exceeded 3 0
ICMP parameter problem 4 0
ICMP timestamp request 5 0
ICMP timestamp reply 6 0
ICMP information request 7 0
ICMP information reply 4 0
ICMP address mask request 2 0
ICMP address mask reply 1 0
ICMPv6 echo request 1 1
ICMPv6 echo reply 1 1
ICMPv6 group membership query 1 0
ICMPv6 group membership report 1 0
ICMPv6 group membership reduction 1 0
ICMPv6 destination unreachable 1 0
ICMPv6 time exceeded 1 0
ICMPv6 parameter problem 1 0
ICMPv6 packet too big 1 0
IPv6 extension header abnormal 1 0
IPv6 extension header exceeded 1 0
Table 12 Command output
|
Field |
Description |
|
AttackType |
Type of the attack. |
|
AttackTimes |
Number of times that the attack occurred. This command output displays only attacks that are detected. |
|
Dropped |
Number of dropped packets. |
|
ICMPv6 flood |
ICMPv6 flood attack. This field is not displayed when no ICMPv6 flood attack is detected. |
|
Large ICMPv6 |
Large ICMPv6 attack. This field is not displayed when no large ICMPv6 attack is detected. |
|
ICMPv6 echo request |
ICMPv6 echo request attack. This field is not displayed when no ICMPv6 echo request attack is detected. |
|
ICMPv6 echo reply |
ICMPv6 echo reply attack. This field is not displayed when no ICMPv6 echo reply attack is detected. |
|
ICMPv6 group membership query |
ICMPv6 group membership query attack. This field is not displayed when no ICMPv6 group membership query attack is detected. |
|
ICMPv6 group membership report |
ICMPv6 group membership report attack. This field is not displayed when no ICMPv6 group membership report attack is detected. |
|
ICMPv6 group membership reduction |
ICMPv6 group membership reduction attack. This field is not displayed when no ICMPv6 group membership reduction attack is detected. |
|
ICMPv6 destination unreachable |
ICMPv6 destination unreachable attack. This field is not displayed when no ICMPv6 destination unreachable attack is detected. |
|
ICMPv6 time exceeded |
ICMPv6 time exceeded attack. This field is not displayed when no ICMPv6 time exceeded attack is detected. |
|
ICMPv6 parameter problem |
ICMPv6 parameter problem attack. This field is not displayed when no ICMPv6 parameter problem attack is detected. |
|
ICMPv6 packet too big |
ICMPv6 packet too big attack. This field is not displayed when no ICMPv6 packet too big attack is detected. |
|
IPv6 extension header abnormal |
Abnormal IPv6 extension header attack. This field is not displayed when no abnormal IPv6 extension header attack is detected. |
|
IPv6 extension header exceeded |
IPv6 extension header exceeded attack. This field is not displayed when no IPv6 extension header exceeded attack is detected. |
Related commands
reset attack-defense statistics local
display attack-defense top-attack-statistics
Use display attack-defense top-attack-statistics to display top 10 attack statistics.
Syntax
display attack-defense top-attack-statistics { last-1-hour | last-24-hours | last-30-days } [ by-attacker | by-type | by-victim ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
last-1-hour: Specifies the most recent 1 hour.
last-24-hours: Specifies the most recent 24 hours.
last-30-days: Specifies the most recent 30 days.
by-attacker: Displays top 10 attack statistics by attacker.
by-type: Displays all attack statistics by attack type.
by-victim: Displays top 10 attack statistics by victim.
Usage guidelines
If you do not specify the by-attacker, by-type, or by-victim keyword, this command displays attack statistics by attacker, victim, attack type.
Examples
# Display top 10 attack statistics in the most recent 1 hour.
<Sysname> display attack-defense top-attack-statistics last-1-hour
Top attackers:
No. VPN instance Attacker IP Attacks
1 200.200.200.55 21
2 200.200.200.21 16
3 200.200.200.133 12
4 200.200.200.19 10
5 200.200.200.4 8
6 200.200.200.155 8
7 200.200.200.93 5
8 200.200.200.67 3
9 200.200.200.70 1
10 200.200.200.23 1
Top victims:
No. VPN instance Victim IP Attacks
1 -- 201.200.200.12 21
2 -- 201.200.200.32 16
3 -- 201.200.200.14 12
4 -- 201.200.200.251 12
5 -- 201.200.200.10 7
6 -- 201.200.200.77 6
7 -- 201.200.200.96 2
8 -- 201.200.200.22 2
9 -- 201.200.200.154 2
10 -- 201.200.200.18 1
Top attack types:
Attack type Attacks
Scan 155
Syn 155
Table 13 Command output
|
Field |
Description |
|
Top attackers |
Top 10 attack statistics by attacker. |
|
No. |
Rank on the list. |
|
VPN instance |
This field is not supported in the current software version. VPN instance to which the attacker or victim belongs. If the attacker or victim belongs to the public network, this field is not displayed. |
|
Attacks |
Number of attacks. |
|
Top victims |
Top 10 attack statistics by victim. |
|
Top attack types |
Attack statistics by attack type. |
Related commands
attack-defense top-attack-statistics enable
dns-flood action
Use dns-flood action to specify global actions against DNS flood attacks.
Use undo dns-flood action to restore the default.
Syntax
dns-flood action { drop | logging } *
undo dns-flood action
Default
No global action is specified for DNS flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent DNS packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent DNS packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for DNS flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against DNS flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood action drop
Related commands
dns-flood detect
dns-flood detect non-specific
dns-flood port
dns-flood source-threshold
dns-flood threshold
dns-flood detect
Use dns-flood detect to configure IP address-specific DNS flood attack detection.
Use undo dns-flood detect to remove the IP address-specific DNS flood attack detection configuration.
Syntax
dns-flood detect { ip ipv4-address | ipv6 ipv6-address } [ port port-list ] [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo dns-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific DNS flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
port port-list: Specifies a space-separated list of up to 24 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold threshold-value: Specifies the maximum receiving rate in pps for DNS packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected DNS flood attack. If no action is specified, the global actions set by the dns-flood action command apply.
drop: Drops subsequent DNS packets destined for the protected IP address.
logging: Enables logging for DNS flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With DNS flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of DNS packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure DNS flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log DNS flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output DNS flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view DNS flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure DNS flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood detect ip 192.168.1.2 port 53 threshold 2000
Related commands
dns-flood action
dns-flood detect non-specific
dns-flood port
dns-flood threshold
dns-flood detect non-specific
Use dns-flood detect non-specific to enable global DNS flood attack detection.
Use undo dns-flood detect non-specific to disable global DNS flood attack detection.
Syntax
dns-flood detect non-specific
undo dns-flood detect non-specific
Default
Global DNS flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following DNS flood attack prevention types:
· Source-based DNS flood attack prevention—Monitors the receiving rate of DNS packets on a per-source IP basis.
· Destination-based DNS flood attack prevention—Monitors the receiving rate of DNS packets on a per-destination IP basis.
The global DNS flood attack detection applies to all IP addresses except for those specified by the dns-flood detect command. The global detection uses the global trigger threshold set by the dns-flood threshold or dns-flood source-threshold command and global actions specified by the dns-flood action command.
Examples
# Enable global DNS flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood detect non-specific
Related commands
dns-flood action
dns-flood detect
dns-flood port
dns-flood source-threshold
dns-flood threshold
dns-flood port
Use dns-flood port to specify the global ports to be protected against DNS flood attacks.
Use undo dns-flood port to restore the default.
Syntax
dns-flood port port-list
undo dns-flood port
Default
The global DNS flood attack prevention protects port 53.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only DNS packets destined for the specified ports.
The global ports apply to global DNS flood attack detection and IP address-specific DNS flood attack detection with no port specified.
Examples
# Specify the ports 53 and 61000 as the global ports to be protected against DNS flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood port 53 61000
Related commands
dns-flood action
dns-flood detect
dns-flood detect non-specific
dns-flood source-threshold
dns-flood threshold
dns-flood threshold
Use dns-flood threshold to set the global threshold for triggering destination-based DNS flood attack prevention.
Use undo dns-flood threshold to restore the default.
Syntax
dns-flood threshold threshold-value
undo dns-flood threshold
Default
The global threshold is 10000 for triggering destination-based DNS flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for DNS packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based DNS flood attack prevention is disabled.
Usage guidelines
With global DNS flood attack detection configured, the device is in attack detection state. When the receiving rate of DNS packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global DNS flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of DNS packets sent to a protected DNS server is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based DNS flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood threshold 100
Related commands
dns-flood action
dns-flood detect
dns-flood detect non-specific
dns-flood port
dns-flood source-threshold
Use dns-flood source-threshold to set the global threshold for triggering source-based DNS flood attack prevention.
Use undo dns-flood source-threshold to restore the default.
Syntax
dns-flood source-threshold threshold-value
undo dns-flood source-threshold
Default
The global threshold is 10000 for triggering source-based DNS flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for DNS packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based DNS flood attack prevention is disabled.
Usage guidelines
With global DNS flood attack detection configured, the device is in attack detection state. When the receiving rate of DNS packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based DNS flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-flood source-threshold 100
Related commands
dns-flood action
dns-flood detect ip
dns-flood detect non-specific
dns-flood port
dns-reply-flood action
Use dns-reply-flood action to specify global actions against DNS response flood attacks.
Use undo dns-reply-flood action to restore the default.
Syntax
dns-reply-flood action { drop | logging } *
undo dns-reply-flood action
Default
No global action is specified for DNS response flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent DNS responses destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent DNS responses originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for DNS response flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log DNS response flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output DNS response flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view DNS response flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against DNS response flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood action drop
Related commands
dns-reply-flood detect
dns-reply-flood detect non-specific
dns-reply-flood source-threshold
dns-reply-flood threshold
dns-reply-flood detect
Use dns-reply-flood detect to configure IP address-specific DNS response flood attack detection.
Use undo dns-reply-flood detect to remove the IP address-specific DNS response flood attack detection configuration.
Syntax
dns-reply-flood detect { ip ipv4-address | ipv6 ipv6-address } [ port port-list ] [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo dns-reply-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific DNS response flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected.
port port-list: Specifies a space-separated list of up to 24 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold threshold-value: Specifies the maximum receiving rate in pps for DNS responses that are destined for the protected IP address. The value range is 1 to 1000000, and the default value is 1000.
action: Specifies the actions against a detected DNS response flood attack.
drop: Drops subsequent DNS responses destined for the protected IP address.
logging: Enables logging for DNS response flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
You can configure DNS response flood attack detection for multiple IP addresses in one attack defense policy.
With DNS response flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of DNS responses destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The logging keyword enables the attack detection and prevention module to log DNS response flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output DNS response flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view DNS response flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure DNS response flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood detect ip 192.168.1.2 port 53 threshold 2000
Related commands
dns-reply-flood action
dns-reply-flood detect non-specific
dns-reply-flood port
dns-reply-flood threshold
dns-reply-flood detect non-specific
Use dns-reply-flood detect non-specific to enable global DNS response flood attack detection.
Use undo dns-reply-flood detect non-specific to disable global DNS response flood attack detection.
Syntax
dns-reply-flood detect non-specific
undo dns-reply-flood detect non-specific
Default
Global DNS response flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following DNS response flood attack prevention types:
· Source-based DNS response flood attack prevention—Monitors the receiving rate of DNS responses on a per-source IP basis.
· Destination-based DNS response flood attack prevention—Monitors the receiving rate of DNS responses on a per-destination IP basis.
The global DNS response flood attack detection applies to all IP addresses except for those specified by the dns-reply-flood detect or dns-reply-flood source-threshold command. The global detection uses the global trigger threshold set by the dns-reply-flood threshold command and global actions specified by the dns-flood action command.
Examples
# Enable global DNS response flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood detect non-specific
Related commands
dns-reply-flood action
dns-reply-flood detect
dns-reply-flood port
dns-reply-flood source-threshold
dns-reply-flood threshold
dns-reply-flood port
Use dns-reply-flood port to specify the global ports to be protected against DNS response flood attacks.
Use undo dns-reply-flood port to restore the default.
Syntax
dns-reply-flood port port-list
undo dns-reply-flood port
Default
The global DNS response flood attack prevention protects port 53.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only DNS response packets destined for the specified ports.
The global ports apply to global DNS response flood attack detection and IP address-specific DNS response flood attack detection with no port specified.
Examples
# Specify the ports 53 and 61000 as the global ports to be protected against DNS response flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood port 53 61000
Related commands
dns-reply-flood action
dns-reply-flood detect
dns-reply-flood detect non-specific
dns-reply-flood source-threshold
dns-reply-flood threshold
dns-reply-flood threshold
Use dns-reply-flood threshold to set the global threshold for triggering destination-based DNS response flood attack prevention.
Use undo dns-reply-flood threshold to restore the default.
Syntax
dns-reply-flood threshold threshold-value
undo dns-reply-flood threshold
Default
The global threshold is 10000 for triggering destination-based DNS response flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for DNS responses that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based DNS response flood attack prevention is disabled.
Usage guidelines
With global DNS response flood attack detection configured, the device is in attack detection state. When the receiving rate of DNS responses destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global DNS response flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of DNS responses sent to a protected DNS client is normally large, set a high threshold. A low threshold might affect the client services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based DNS response flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood threshold 100
Related commands
dns-reply-flood action
dns-reply-flood detect ip
dns-reply-flood detect non-specific
dns-reply-flood port
dns-reply-flood source-threshold
Use dns-reply-flood source-threshold to set the global threshold for triggering source-based DNS response flood attack prevention.
Use undo dns-reply-flood source-threshold to restore the default.
Syntax
dns-reply-flood source-threshold threshold-value
undo dns-reply-flood source-threshold
Default
The global threshold is 10000 for triggering source-based DNS response flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for DNS responses that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based DNS response flood attack prevention is disabled.
Usage guidelines
With global DNS response flood attack detection configured, the device is in attack detection state. When the receiving rate of DNS responses originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based DNS response flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] dns-reply-flood source-threshold 100
Related commands
dns-reply-flood action
dns-reply-flood detect ip
dns-reply-flood detect non-specific
dns-reply-flood port
exempt acl
Use exempt acl to configure attack detection exemption.
Use undo exempt acl to restore the default.
Syntax
exempt acl [ ipv6 ] { acl-number | name acl-name }
undo exempt acl [ ipv6 ]
Default
Attack detection exemption is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ipv6: Specifies an IPv6 ACL. To specify an IPv4 ACL, do not use this keyword.
acl-number: Specifies an ACL by its number:
· 2000 to 2999 for basic ACLs.
· 3000 to 3999 for advanced ACLs.
name acl-name: Specifies an ACL by its name. The acl-name argument is a case-insensitive string of 1 to 63 characters. It must start with an English letter and to avoid confusion, it cannot be all.
Usage guidelines
The attack defense policy uses an ACL to identify exempted packets. The policy does not check the packets permitted by the ACL. You can configure the ACL to identify packets from trusted hosts. The exemption feature reduces the false alarm rate and improves packet processing efficiency.
If an ACL is used for attack detection exemption, only the following match criteria in the ACL permit rules take effect:
· Source IP address.
· Destination IP address.
· Source port.
· Destination port.
· Protocol.
· The fragment keyword for matching non-first fragments.
If the specified ACL does not exist or does not contain a rule, attack detection exemption does not take effect.
Examples
# Configure an ACL to permit packets sourced from 1.1.1.1. Configure attack detection exemption for packets matching the ACL in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] acl basic 2001
[Sysname-acl-ipv4-basic-2001] rule permit source 1.1.1.1 0
[Sysname-acl-ipv4-basic-2001] quit
[Sysname] attack-defense policy atk-policy-1
[attack-defense-policy-atk-policy-1] exempt acl 2001
Related commands
attack-defense policy
fin-flood action
Use fin-flood action to specify global actions against FIN flood attacks.
Use undo fin-flood action to restore the default.
Syntax
fin-flood action { drop | logging } *
undo fin-flood action
Default
No global action is specified for FIN flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent FIN packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent FIN packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for FIN flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against FIN flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] fin-flood action drop
Related commands
fin-flood detect
fin-flood detect non-specific
fin-flood source-threshold
fin-flood threshold
fin-flood detect
Use fin-flood detect to configure IP address-specific FIN flood attack detection.
Use undo fin-flood detect to remove the IP address-specific FIN flood attack detection configuration.
Syntax
fin-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo fin-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific FIN flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for FIN packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected FIN flood attack. If no action is specified, the global actions set by the fin-flood action command apply.
drop: Drops subsequent FIN packets destined for the protected IP address.
logging: Enables logging for FIN flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With FIN flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of FIN packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure FIN flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log FIN flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output FIN flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view FIN flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure FIN flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] fin-flood detect ip 192.168.1.2 threshold 2000
Related commands
fin-flood action
fin-flood detect non-specific
fin-flood threshold
fin-flood detect non-specific
Use fin-flood detect non-specific to enable global FIN flood attack detection.
Use undo fin-flood detect non-specific to disable global FIN flood attack detection.
Syntax
fin-flood detect non-specific
undo fin-flood detect non-specific
Default
Global FIN flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following FIN flood attack prevention types:
· Source-based FIN flood attack prevention—Monitors the receiving rate of FIN packets on a per-source IP basis.
· Destination-based FIN flood attack prevention—Monitors the receiving rate of FIN packets on a per-destination IP basis.
The global FIN flood attack detection applies to all IP addresses except for those specified by the fin-flood detect command. The global detection uses the global trigger threshold set by the fin-flood threshold or fin-flood source-threshold command and global actions specified by the fin-flood action command.
Examples
# Enable global FIN flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] fin-flood detect non-specific
Related commands
fin-flood action
fin-flood detect
fin-flood source-threshold
fin-flood threshold
fin-flood threshold
Use fin-flood threshold to set the global threshold for triggering destination-based FIN flood attack prevention.
Use undo fin-flood threshold to restore the default.
Syntax
fin-flood threshold threshold-value
undo fin-flood threshold
Default
The global threshold is 10000 for triggering destination-based FIN flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for FIN packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based FIN flood attack prevention is disabled.
Usage guidelines
With global FIN flood attack detection configured, the device is in attack detection state. When the receiving rate of FIN packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global FIN flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of FIN packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based FIN flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] fin-flood threshold 100
Related commands
fin-flood action
fin-flood detect
fin-flood detect non-specific
fin-flood source-threshold
Use fin-flood source-threshold to set the global threshold for triggering source-based FIN flood attack prevention.
Use undo fin-flood source-threshold to restore the default.
Syntax
fin-flood source-threshold threshold-value
undo fin-flood source-threshold
Default
The global threshold is 10000 for triggering source-based FIN flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for FIN packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based FIN flood attack prevention is disabled.
Usage guidelines
With global FIN flood attack detection configured, the device is in attack detection state. When the receiving rate of FIN packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based FIN flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] fin-flood source-threshold 100
Related commands
fin-flood action
fin-flood detect
fin-flood detect non-specific
http-flood action
Use http-flood action to specify global actions against HTTP flood attacks.
Use undo http-flood action to restore the default.
Syntax
http-flood action { drop | logging } *
undo http-flood action
Default
No global action is specified for HTTP flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent HTTP packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent HTTP packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for HTTP flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against HTTP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood action drop
Related commands
http-flood detect
http-flood detect non-specific
http-flood source-threshold
http-flood threshold
http-flood detect
Use http-flood detect to configure IP address-specific HTTP flood attack detection.
Use undo http-flood detect to remove the IP address-specific HTTP flood attack detection configuration.
Syntax
http-flood detect { ip ipv4-address | ipv6 ipv6-address } [ port port-list ] [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo http-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific HTTP flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
port port-list: Specifies a space-separated list of up to 24 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold threshold-value: Specifies the maximum receiving rate in pps for HTTP packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected HTTP flood attack. If no action is specified, the global actions set by the http-flood action command apply.
drop: Drops subsequent HTTP packets destined for the protected IP address.
logging: Enables logging for HTTP flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With HTTP flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of HTTP packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure HTTP flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log HTTP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output HTTP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view HTTP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure HTTP flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood detect ip 192.168.1.2 port 80 8080 threshold 2000
Related commands
http-flood action
http-flood detect non-specific
http-flood port
http-flood threshold
http-flood detect non-specific
Use http-flood detect non-specific to enable global HTTP flood attack detection.
Use undo http-flood detect non-specific to disable global HTTP flood attack detection.
Syntax
http-flood detect non-specific
undo http-flood detect non-specific
Default
Global HTTP flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following HTTP flood attack prevention types:
· Source-based HTTP response flood attack prevention—Monitors the receiving rate of HTTP packets on a per-source IP basis.
· Destination-based HTTP response flood attack prevention—Monitors the receiving rate of HTTP packets on a per-destination IP basis.
The global HTTP flood attack detection applies to all IP addresses except for those specified by the http-flood detect command. The global detection uses the global trigger threshold set by the http-flood threshold or http-flood source-threshold command and global actions specified by the http-flood action command.
Examples
# Enable global HTTP flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood detect non-specific
Related commands
http-flood action
http-flood detect
http-flood source-threshold
http-flood threshold
http-flood port
Use http-flood port to specify the global ports to be protected against HTTP flood attacks.
Use undo http-flood port to restore the default.
Syntax
http-flood port port-list
undo http-flood port
Default
The global HTTP flood attack prevention protects port 80.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only HTTP packets destined for the specified ports.
The global ports apply to global HTTP flood attack detection and IP address-specific HTTP flood attack detection with no port specified.
Examples
# Specify the ports 80 and 8080 as the global ports to be protected against HTTP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood port 80 8080
Related commands
http-flood action
http-flood detect
http-flood detect non-specific
http-flood source-threshold
http-flood threshold
http-flood threshold
Use http-flood threshold to set the global threshold for triggering destination-based HTTP flood attack prevention.
Use undo http-flood threshold to restore the default.
Syntax
http-flood threshold threshold-value
undo http-flood threshold
Default
The global threshold is 10000 for triggering destination-based HTTP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for HTTP packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based HTTP flood attack prevention is disabled.
Usage guidelines
With global HTTP flood attack detection configured, the device is in attack detection state. When the receiving rate of HTTP packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global HTTP flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of HTTP packets sent to a protected HTTP server is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering HTTP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood threshold 100
Related commands
http-flood action
http-flood detect
http-flood detect non-specific
http-flood port
http-flood source-threshold
Use http-flood source-threshold to set the global threshold for triggering source-based HTTP flood attack prevention.
Use undo http-flood source-threshold to restore the default.
Syntax
http-flood source-threshold threshold-value
undo http-flood source-threshold
Default
The global threshold is 10000 for triggering source-based HTTP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for HTTP packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based HTTP flood attack prevention is disabled.
Usage guidelines
With global HTTP flood attack detection configured, the device is in attack detection state. When the receiving rate of HTTP packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based HTTP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-flood source-threshold 100
Related commands
http-flood action
http-flood detect
http-flood detect non-specific
http-flood port
http-slow-attack action
Use http-slow-attack action to specify the global actions against HTTP slow attacks.
Use undo http-slow-attack action to restore the default.
Syntax
http-slow-attack action logging
undo http-slow-attack action
Default
No global actions are specified for HTTP slow attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
logging: Enables logging for HTTP slow attack events. The log messages will be sent to the log system.
Examples
# In attack defense policy atk-policy-1, specify logging as the global action against HTTP slow attacks.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack action logging
Related commands
http-slow-attack detect
http-slow-attack detect non-specific
http-slow-attack period
http-slow-attack port
http-slow-attack threshold
http-slow-attack detect
Use http-slow-attack detect to configure IP address-specific HTTP slow attack detection.
Use undo http-slow-attack detect to remove the IP address-specific HTTP slow attack detection configuration.
Syntax
http-slow-attack detect { ip ipv4-address | ipv6 ipv6-address } [ port { start-port-number [ to end-port-number ] } &<1-16> ] [ threshold { alert-number alert-number | content-length content-length | payload-length payload-length | packet-number packet-number }* ] [ period period ] [ action logging ]
undo http-slow-attack detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific HTTP slow attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
port port-list: Specifies a space-separated list of up to 16 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold: Specifies the threshold for triggering HTTP slow attack prevention. If you do not specify this argument, the global threshold settings for triggering HTTP slow attack prevention apply.
alert-number alert-number: Specifies a threshold for HTTP concurrent connections. The value range is 1 to 1200000, and the default is 5000.
content-length content-length: Specifies a threshold for the Content-Length field value in an HTTP packet. The value range is 100 to 100000000, and the default is 10000.
payload-length payload-length: Specifies a threshold for the payload size in an HTTP packet. The value range is 1 to 1000, and the default is 50.
packet-number packet-number: Specifies a threshold for abnormal packets. The value range is 1 to 1000, and the default is 10.
period period: Specifies a detection period in the range of 1 to 1200 seconds. If you do not specify this option, the global detection period applies.
action: Specifies actions against HTTP slow attacks. If you do not specify an action, the global defensive actions apply.
logging: Enables logging for HTTP slow attack events. The log messages will be sent to the log system.
Usage guidelines
If you specify part of threshold parameters for IP address-specific HTTP slow attack detection, the default settings rather than the global settings apply to the unspecified threshold parameters.
Examples
# Configure HTTP slow attack detection for 1.1.1.1 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack detect ip 1.1.1.1 port 80 8080 threshold alert-number 3000 content-length 10000 payload-length 20 packet-number 10 action logging
Related commands
http-slow-attack action
http-slow-attack detect non-specific
http-slow-attack period
http-slow-attack port
http-slow-attack threshold
http-slow-attack detect non-specific
Use http-slow-attack detect non-specific to enable global HTTP slow attack detection.
Use undo http-slow-attack detect non-specific to disable global HTTP slow attack detection.
Syntax
http-slow-attack detect non-specific
undo http-slow-attack detect non-specific
Default
Global HTTP slow attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
After you enable global HTTP slow attack detection, the device uses the following global settings to protect IP addresses:
· Threshold settings set by using the http-slow-attack threshold command.
· Detection period set by using the http-slow-attack period command.
· Ports set by using the http-slow-attack port command.
· Defensive actions set by using the http-slow-attack action command.
Examples
# Enable global HTTP slow attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack detect non-specific
Related commands
http-slow-attack action
http-slow-attack detect
http-slow-attack period
http-slow-attack port
http-slow-attack threshold
http-slow-attack period
Use http-slow-attack period to set the global HTTP slow attack detection period.
Use undo http-slow-attack period to restore the default.
Syntax
http-slow-attack period period
undo http-slow-attack period
Default
The global HTTP slow attack detection period is 60 seconds.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
period period: Specifies the detection period in seconds. The value range is 1 to 1200, and the default is 60.
Examples
# Set the HTTP slow attack detection period to 10 seconds in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack period 10
Related commands
http-slow-attack action
http-slow-attack detect
http-slow-attack detect non-specific
http-slow-attack port
http-slow-attack threshold
http-slow-attack port
Use http-slow-attack port to specify global ports to be protected against HTTP slow attacks.
Use undo http-slow-attack port to restore the default.
Syntax
http-slow-attack port port-list &<1-32>
undo http-slow-attack port
Default
The global HTTP slow attack prevention protects port 80.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list &<1-32>: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only HTTP packets destined for the specified ports.
The global ports are used in global HTTP slow attack detection and IP address-specific HTTP slow attack detection with no protected ports specified.
As a best practice, specify port 80 as the global protected port against HTTP slow attacks. If you specify other ports, make sure these ports are used for HTTP communication. If the specified ports are not used for HTTP communication, the device resources will be wasted in inspecting non-HTTP slow attack packets.
Examples
# Specify ports 80 and 8080 as the global ports to be protected against HTTP slow attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack port 80 8000
Related commands
http-slow-attack action
http-slow-attack detect
http-slow-attack detect non-specific
http-slow-attack period
http-slow-attack threshold
http-slow-attack threshold
Use http-slow-attack threshold to set global thresholds for triggering HTTP slow attack prevention.
Use undo http-slow-attack threshold to restore the default.
Syntax
http-slow-attack threshold [ alert-number alert-number | content-length content-length | payload-length payload-length | packet-number packet-number ]*
undo http-slow-attack threshold
Default
The device enters HTTP slow attack detection state when the number of HTTP concurrent connections exceeds 5000. An HTTP packet is a slow attack packet if its Content-Length field value is greater than 10000 and its payload is less than 50 bytes. When the device receives more than 10 slow attack packets within the detection period, it takes defensive actions.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
alert-number alert-number: Specifies a threshold for HTTP concurrent connections. The value range is 1 to 1200000, and the default is 5000.
content-length content-length: Specifies a threshold for the Content-Length field value in an HTTP packet. The value range is 100 to 100000000, and the default is 10000.
payload-length payload-length: Specifies a threshold for the payload size in an HTTP packet. The value range is 1 to 1000, and the default is 50.
packet-number packet-number: Specifies a threshold for HTTP slow attack packets. The value range is 1 to 1000, and the default is 10.
Usage guidelines
The device enters the HTTP slow attack detection state when the number of HTTP concurrent connections exceeds the threshold. An HTTP packet is a slow attack packet if its Content-Length field value is greater than the content-length value and its payload is less than the payload-length value. When the number of attack packets received within the detection period exceeds the threshold, the device takes defensive actions.
If you do not specify a threshold for a parameter, the default value for the parameter applies.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure global HTTP slow attack detection thresholds in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] http-slow-attack threshold alert-number 3000 content-length 10000 payload-length 20 packet-number 10
Related commands
http-slow-attack action
http-slow-attack detect
http-slow-attack detect non-specific
http-slow-attack period
http-slow-attack port
https-flood action
Use https-flood action to specify global actions against HTTPS flood attacks.
Use undo https-flood action to restore the default.
Syntax
https-flood action { client-verify | drop | logging } *
undo https-flood action
Default
No global action is specified for HTTPS flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
client-verify: Adds the victim IP addresses to the protected IP list for HTTPS client verification. If HTTPS client verification is enabled, the device provides proxy services for protected servers. This keyword does not take effect on source-based flood attack prevention.
drop: Drops subsequent HTTPS packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent HTTPS packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for HTTPS flood attack events. The log messages will be sent to the log system.
Usage guidelines
For the HTTPS flood attack detection to collaborate with the HTTPS client verification, make sure the client-verify keyword is specified and the HTTPS client verification is enabled. To enable HTTPS client verification, use the client-verify https enable command.
The logging keyword enables the attack detection and prevention module to log HTTPS flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output HTTPS flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view HTTPS flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Network Management and Monitoring Configuration Guide.
Examples
# Specify drop as the global action against HTTPS flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood action drop
Related commands
client-verify https enable
https-flood detect
https-flood detect non-specific
https-flood source-threshold
https-flood threshold
https-flood detect
Use https-flood detect to configure IP address-specific HTTPS flood attack detection.
Use undo https-flood detect to remove the IP address-specific HTTPS flood attack detection configuration.
Syntax
https-flood detect { ip ipv4-address | ipv6 ipv6-address } [ port port-list ] [ threshold threshold-value ] [ action { { client-verify | drop | logging } * | none } ]
undo https-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific HTTPS flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
port port-list: Specifies a space-separated list of up to 24 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold threshold-value: Specifies the maximum receiving rate in pps for HTTPS packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected HTTPS flood attack. If no action is specified, the global actions set by the https-flood action command apply.
client-verify: Adds the victim IP addresses to the protected IP list for HTTPS client verification. If HTTPS client verification is enabled, the device provides proxy services for protected servers.
drop: Drops subsequent HTTPS packets destined for the protected IP address.
logging: Enables logging for HTTPS flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With HTTPS flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of HTTPS packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure HTTPS flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log HTTPS flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output HTTPS flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view HTTPS flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Network Management and Monitoring Configuration Guide.
Examples
# Configure HTTPS flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood detect ip 192.168.1.2 port 443 threshold 2000
Related commands
https-flood action
https-flood detect non-specific
https-flood port
https-flood threshold
https-flood detect non-specific
Use https-flood detect non-specific to enable global HTTPS flood attack detection.
Use undo https-flood detect non-specific to disable global HTTPS flood attack detection.
Syntax
https-flood detect non-specific
undo https-flood detect non-specific
Default
Global HTTPS flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following HTTPS flood attack prevention types:
· Source-based HTTPS response flood attack prevention—Monitors the receiving rate of HTTPS packets on a per-source IP basis.
· Destination-based HTTPS response flood attack prevention—Monitors the receiving rate of HTTPS packets on a per-destination IP basis.
The global HTTPS flood attack detection applies to all IP addresses except for those specified by the https-flood detect command. The global detection uses the global trigger threshold set by the https-flood threshold or https-flood source-threshold command and global actions specified by the https-flood action command.
Examples
# Enable global HTTPS flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood detect non-specific
Related commands
https-flood action
https-flood detect
https-flood source-threshold
https-flood threshold
https-flood port
Use https-flood port to specify the global ports to be protected against HTTPS flood attacks.
Use undo https-flood port to restore the default.
Syntax
https-flood port port-list
undo https-flood port
Default
The global HTTPS flood attack prevention protects port 443.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only HTTPS packets destined for the specified ports.
The global ports apply to global HTTPS flood attack detection and IP address-specific HTTPS flood attack detection with no port specified.
Examples
# Specify the port 443 as the global ports to be protected against HTTPS flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood port 443
Related commands
https-flood action
https-flood detect
https-flood detect non-specific
https-flood source-threshold
https-flood threshold
https-flood threshold
Use https-flood threshold to set the global threshold for triggering destination-based HTTPS flood attack prevention.
Use undo https-flood threshold to restore the default.
Syntax
https-flood threshold threshold-value
undo https-flood threshold
Default
The global threshold is 10000 for triggering destination-based HTTPS flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for HTTPS packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based HTTPS flood attack prevention is disabled.
Usage guidelines
With global HTTPS flood attack detection configured, the device is in attack detection state. When the receiving rate of HTTPS packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global HTTPS flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of HTTPS packets sent to a protected HTTPS server is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering HTTPS flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood threshold 100
Related commands
https-flood action
https-flood detect
https-flood detect non-specific
https-flood port
https-flood source-threshold
Use https-flood source-threshold to set the global threshold for triggering source-based HTTPS flood attack prevention.
Use undo https-flood source-threshold to restore the default.
Syntax
https-flood source-threshold threshold-value
undo https-flood source-threshold
Default
The global threshold is 10000 for triggering source-based HTTPS flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for HTTPS packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based HTTPS flood attack prevention is disabled.
Usage guidelines
With global HTTPS flood attack detection configured, the device is in attack detection state. When the receiving rate of HTTPS packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based HTTPS flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] https-flood source-threshold 100
Related commands
https-flood action
https-flood detect
https-flood detect non-specific
https-flood port
icmp-flood action
Use icmp-flood action to specify global actions against ICMP flood attacks.
Use undo icmp-flood action to restore the default.
Syntax
icmp-flood action { drop | logging } *
undo icmp-flood action
Default
No global action is specified for ICMP flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent ICMP packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent ICMP packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for ICMP flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log ICMP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ICMP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ICMP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against ICMP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmp-flood action drop
Related commands
icmp-flood detect non-specific
icmp-flood detect ip
icmp-flood source-threshold
icmp-flood threshold
icmp-flood detect ip
Use icmp-flood detect ip to configure IP address-specific ICMP flood attack detection.
Use undo icmp-flood detect ip to remove the IP address-specific ICMP flood attack detection configuration.
Syntax
icmp-flood detect ip ip-address [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo icmp-flood detect ip ip-address
Default
IP address-specific ICMP flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
threshold threshold-value: Specifies the maximum receiving rate in pps for ICMP packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected ICMP flood attack. If no action is specified, the global actions set by the icmp-flood action command apply.
drop: Drops subsequent ICMP packets destined for the protected IP address.
logging: Enables logging for ICMP flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With ICMP flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of ICMP packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure ICMP flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log ICMP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ICMP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ICMP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure ICMP flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmp-flood detect ip 192.168.1.2 threshold 2000
Related commands
icmp-flood action
icmp-flood detect non-specific
icmp-flood threshold
icmp-flood detect non-specific
Use icmp-flood detect non-specific to enable global ICMP flood attack detection.
Use undo icmp-flood detect non-specific to disable global ICMP flood attack detection.
Syntax
icmp-flood detect non-specific
undo icmp-flood detect non-specific
Default
Global ICMP flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following ICMP flood attack prevention types:
· Source-based ICMP flood attack prevention—Monitors the receiving rate of ICMP packets on a per-source IP basis.
· Destination-based ICMP flood attack prevention—Monitors the receiving rate of ICMP packets on a per-destination IP basis.
The global ICMP flood attack detection applies to all IP addresses except for those specified by the icmp-flood detect ip command. The global detection uses the global trigger threshold set by the icmp-flood threshold or icmp-flood source-threshold command and global actions specified by the icmp-flood action command.
Examples
# Enable global ICMP flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmp-flood detect non-specific
Related commands
icmp-flood action
icmp-flood detect ip
icmp-flood source-threshold
icmp-flood threshold
icmp-flood threshold
Use icmp-flood threshold to set the global threshold for triggering destination-based ICMP flood attack prevention.
Use undo icmp-flood threshold to restore the default.
Syntax
icmp-flood threshold threshold-value
undo icmp-flood threshold
Default
The global threshold is 10000 for triggering destination-based ICMP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ICMP packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based ICMP flood attack prevention is disabled.
Usage guidelines
With global ICMP flood attack detection configured, the device is in attack detection state. When the receiving rate of ICMP packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global ICMP flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of ICMP packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based ICMP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmp-flood threshold 100
Related commands
icmp-flood action
icmp-flood detect ip
icmp-flood detect non-specific
icmp-flood source-threshold
Use icmp-flood source-threshold to set the global threshold for triggering source-based ICMP flood attack prevention.
Use undo icmp-flood source-threshold to restore the default.
Syntax
icmp-flood source-threshold threshold-value
undo icmp-flood source-threshold
Default
The global threshold is 10000 for triggering source-based ICMP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ICMP packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based ICMP flood attack prevention is disabled.
Usage guidelines
With global ICMP flood attack detection configured, the device is in attack detection state. When the receiving rate of ICMP packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based ICMP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmp-flood source-threshold 100
Related commands
icmp-flood action
icmp-flood detect
icmp-flood detect non-specific
icmpv6-flood action
Use icmpv6-flood action to specify global actions against ICMPv6 flood attacks.
Use undo icmpv6-flood action to restore the default.
Syntax
icmpv6-flood action { drop | logging } *
undo icmpv6-flood action
Default
No global action is specified for ICMPv6 flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent ICMPv6 packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent ICMPv6 packets originating from the attacker IPv6 addresses in source-based flood attack prevention.
logging: Enables logging for ICMPv6 flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log ICMPv6 flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ICMPv6 flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ICMPv6 flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against ICMPv6 flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmpv6-flood action drop
Related commands
icmpv6-flood detect ipv6
icmpv6-flood detect non-specific
icmpv6-flood source-threshold
icmpv6-flood threshold
icmpv6-flood detect ipv6
Use icmpv6-flood detect ipv6 to configure IPv6 address-specific ICMPv6 flood attack detection.
Use undo icmpv6-flood detect ipv6 to remove the IPv6 address-specific ICMPv6 flood attack detection configuration.
Syntax
icmpv6-flood detect ipv6 ipv6-address [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo icmpv6-flood detect ipv6 ipv6-address
Default
IPv6 address-specific ICMPv6 flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
Ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for ICMPv6 packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected ICMPv6 flood attack. If no action is specified, the global actions set by the icmpv6-flood action command apply.
drop: Drops subsequent ICMPv6 packets destined for the protected IPv6 address.
logging: Enables logging for ICMPv6 flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With ICMPv6 flood attack detection configured for an IPv6 address, the device is in attack detection state. When the receiving rate of ICMPv6 packets to the IPv6 address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure ICMPv6 flood attack detection for multiple IPv6 addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log ICMPv6 flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output ICMPv6 flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view ICMPv6 flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure ICMPv6 flood attack detection for 2012::12 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmpv6-flood detect ipv6 2012::12 threshold 2000
Related commands
icmpv6-flood action
icmpv6-flood detect non-specific
icmpv6-flood threshold
icmpv6-flood detect non-specific
Use icmpv6-flood detect non-specific to enable global ICMPv6 flood attack detection.
Use undo icmpv6-flood detect non-specific to disable global ICMPv6 flood attack detection.
Syntax
icmpv6-flood detect non-specific
undo icmpv6-flood detect non-specific
Default
Global ICMPv6 flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following ICMPv6 flood attack prevention types:
· Source-based ICMPv6 flood attack prevention—Monitors the receiving rate of ICMPv6 messages on a per-source IP basis.
· Destination-based ICMPv6 flood attack prevention—Monitors the receiving rate of ICMPv6 messages on a per-destination IP basis.
The global ICMPv6 flood attack detection applies to all IPv6 addresses except for those specified by the icmpv6-flood detect ipv6 command. The global detection uses the global trigger threshold set by the icmpv6-flood threshold or icmpv6-flood source-threshold command and global actions specified by the icmpv6-flood action command.
Examples
# Enable global ICMPv6 flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmpv6-flood detect non-specific
Related commands
icmpv6-flood action
icmpv6-flood detect ipv6
icmpv6-flood source-threshold
icmpv6-flood threshold
icmpv6-flood threshold
Use icmpv6-flood threshold to set the global threshold for triggering destination-based ICMPv6 flood attack prevention.
Use undo icmpv6-flood threshold to restore the default.
Syntax
icmpv6-flood threshold threshold-value
undo icmpv6-flood threshold
Default
The global threshold is 10000 for triggering destination-based ICMPv6 flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ICMPv6 packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based ICMPv6 flood attack prevention is disabled.
Usage guidelines
With global ICMPv6 flood attack detection configured, the device is in attack detection state. When the receiving rate of ICMPv6 packets destined for an IPv6 address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global ICMPv6 flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of ICMPv6 packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based ICMPv6 flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmpv6-flood threshold 100
Related commands
icmpv6-flood action
icmpv6-flood detect ipv6
icmpv6-flood detect non-specific
icmpv6-flood source-threshold
Use icmpv6-flood source-threshold to set the global threshold for triggering source-based ICMPv6 flood attack prevention.
Use undo icmpv6-flood source-source-threshold to restore the default.
Syntax
icmpv6-flood source-threshold threshold-value
undo icmpv6-flood source-threshold
Default
The global threshold is 10000 for triggering source-based ICMPv6 flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for ICMPv6 packets that originate from an IPv6 address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based ICMPv6 flood attack prevention is disabled.
Usage guidelines
With global ICMPv6 flood attack detection configured, the device is in attack detection state. When the receiving rate of ICMPv6 packets originating from an IPv6 address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based ICMPv6 flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] icmpv6-flood source-threshold 100
Related commands
icmpv6-flood action
icmpv6-flood detect
icmpv6-flood detect non-specific
reset attack-defense policy flood
Use reset attack-defense policy flood statistics to clear flood attack detection and prevention statistics for protected IP addresses.
Syntax
reset attack-defense policy policy-name flood protected { ip | ipv6 } statistics
Views
User view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an attack defense policy by its name. The policy name is a case-insensitive string of 1 to 31 characters. Valid characters include uppercase and lowercase letters, digits, underscores (_), and hyphens (-).
ip: Specifies protected IPv4 addresses.
ipv6: Specifies protected IPv6 addresses.
statistics: Clears flood attack detection and prevention statistics.
Examples
# Clear flood attack detection and prevention statistics for protected IPv4 addresses in attack defense policy abc.
<Sysname> reset attack-defense policy abc flood protected ip statistics
# Clear flood attack detection and prevention statistics for protected IPv6 addresses in attack defense policy abc.
<Sysname> reset attack-defense policy abc flood protected ipv6 statistics
Related commands
display attack-defense policy ip
display attack-defense policy ipv6
reset attack-defense statistics interface
Use reset attack-defense statistics interface to clear attack detection and prevention statistics for an interface.
Syntax
reset attack-defense statistics interface interface-type interface-number
Views
User view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Examples
# Clear attack detection and prevention statistics for VLAN-interface 100.
<Sysname> reset attack-defense statistics interface vlan-interface 100
Related commands
display attack defense policy
reset attack-defense statistics local
Use reset attack-defense statistics local to clear attack detection and prevention statistics for the device.
Syntax
reset attack-defense statistics local
Views
User view
Predefined user roles
network-admin
Examples
# Clear attack detection and prevention statistics for the device.
<Sysname> reset attack-defense statistics local
Related commands
display attack-defense statistics local
reset attack-defense top-attack-statistics
Use reset attack-defense top-attack-statistics to clear top 10 attack statistics.
Syntax
reset attack-defense top-attack-statistics
Views
User view
Predefined user roles
network-admin
network-operator
Examples
# Clear top 10 attack statistics.
<Sysname> reset attack-defense top-attack-statistics
Related commands
attack-defense top-attack-statistics enable
display attack-defense top-attack-statistics
rst-flood action
Use rst-flood action to specify global actions against RST flood attacks.
Use undo rst-flood action to restore the default.
Syntax
rst-flood action { drop | logging } *
undo rst-flood action
Default
No global action is specified for RST flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent RST packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent RST packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for RST flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against RST flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood action drop
Related commands
rst-flood detect
rst-flood detect non-specific
rst-flood source-threshold
rst-flood threshold
rst-flood detect
Use rst-flood detect to configure IP address-specific RST flood attack detection.
Use undo rst-flood detect to remove the IP address-specific RST flood attack detection configuration.
Syntax
rst-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo rst-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific RST flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for RST packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected RST flood attack. If no action is specified, the global actions set by the rst-flood action command apply.
drop: Drops subsequent RST packets destined for the protected IP address.
logging: Enables logging for RST flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With RST flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of RST packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device considers returns to the attack detection state.
You can configure RST flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log RST flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output RST flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view RST flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure RST flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood detect ip 192.168.1.2 threshold 2000
Related commands
rst-flood action
rst-flood detect non-specific
rst-flood threshold
rst-flood detect non-specific
Use rst-flood detect non-specific to enable global RST flood attack detection.
Use undo rst-flood detect non-specific to disable global RST flood attack detection.
Syntax
rst-flood detect non-specific
undo rst-flood detect non-specific
Default
Global RST flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following RST flood attack prevention types:
· Source-based RST flood attack prevention—Monitors the receiving rate of RST packets on a per-source IP basis.
· Destination-based RST flood attack prevention—Monitors the receiving rate of RST packets on a per-destination IP basis.
The global RST flood attack detection applies to all IP addresses except for those specified by the rst-flood detect command. The global detection uses the global trigger threshold set by the rst-flood threshold or rst-flood source-threshold command and global actions specified by the rst-flood action command.
Examples
# Enable global RST flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood detect non-specific
Related commands
rst-flood action
rst-flood detect
rst-flood source-threshold
rst-flood threshold
rst-flood threshold
Use rst-flood threshold to set the global threshold for triggering destination-based RST flood attack prevention.
Use undo rst-flood threshold to restore the default.
Syntax
rst-flood threshold threshold-value
undo rst-flood threshold
Default
The global threshold is 10000 for triggering destination-based RST flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for RST packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based RST flood attack prevention is disabled.
Usage guidelines
With global RST flood attack detection configured, the device is in attack detection state. When the receiving rate of RST packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global RST flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of RST packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based RST flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood threshold 100
Related commands
rst-flood action
rst-flood detect
rst-flood detect non-specific
rst-flood source-threshold
Use rst-flood source-threshold to set the global threshold for triggering source-based RST flood attack prevention.
Use undo rst-flood source-threshold to restore the default.
Syntax
rst-flood source-threshold threshold-value
undo rst-flood source-threshold
Default
The global threshold is 10000 for triggering source-based RST flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for RST packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based RST flood attack prevention is disabled.
Usage guidelines
With global RST flood attack detection configured, the device is in attack detection state. When the receiving rate of RST packets originating from to an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based RST flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood source-threshold 100
Related commands
rst-flood action
rst-flood detect
rst-flood detect non-specific
scan detect
Use scan detect to configure scanning attack detection.
Use undo scan detect to remove the scanning attack detection configuration.
Syntax
scan detect level { { high | low | medium } | user-defined { port-scan-threshold threshold-value | ip-sweep-threshold threshold-value } * [ period period-value ] } action { drop | logging } *
undo scan detect
Default
No scanning attack detection is configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
level: Specifies the level of the scanning attack detection.
high: Specifies the high level. This level can detect most of the scanning attacks, but has a high false alarm rate. Some packets from active hosts might be considered as attack packets. For high level detection, the detection cycle is 10 seconds. The threshold for triggering port scan attack prevention is 5000 packets in a detection cycle. The threshold for triggering IP sweep attack prevention is 5000 packets in a detection cycle.
low: Specifies the low level. This level provides basic scanning attack detection. It has a low false alarm rate but many scanning attacks cannot be detected. For low level detection, the detection cycle is 10 seconds. The threshold for triggering port scan attack prevention is 100000 packets in a detection cycle. The threshold for triggering IP sweep attack prevention is 100000 packets in a detection cycle.
medium: Specifies the medium level. Compared with the high and low levels, this level has medium false alarm rate and attack detection accuracy. For medium level detection, the detection cycle is 10 seconds. The threshold for triggering port scan attack prevention is 40000 packets. The threshold for triggering IP sweep attack prevention is 40000 packets.
user-defined: Specifies the user-defined level. This level allows you to set the thresholds and detection cycle for port scan and IP sweep attacks on demand.
port-scan-threshold threshold-value: Specifies the maximum number of packets sent from an IP address to different ports within a detection cycle. The value range is 1 to 1000000000.
ip-sweep-threshold threshold-value: Specifies the maximum number of packets sent from an IP address to different IP addresses within a detection cycle. The value range is 1 to 1000000000.
period period-value: Sets the scanning attack detection cycle in the range of 1 to 1000000000 seconds. The default value is 10.
action: Specifies the actions against scanning attacks.
drop: Drops subsequent packets from detected scanning attack sources. The log messages will be sent to the log system.
logging: Enables logging for scanning attack events.
Examples
# Configure low level scanning attack detection and specify the prevention action as drop in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] scan detect level low action drop
signature { large-icmp | large-icmpv6 } max-length
Use signature { large-icmp | large-icmpv6 } max-length to set the maximum length of safe ICMP or ICMPv6 packets. A large ICMP or ICMPv6 attack occurs if an ICMP or ICMPv6 packet larger than the specified length is detected.
Use undo signature { large-icmp | large-icmpv6 } max-length to restore the default.
Syntax
signature { large-icmp | large-icmpv6 } max-length length
undo signature { large-icmp | large-icmpv6 } max-length
Default
The maximum length of safe ICMP or ICMPv6 packets is 4000 bytes.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
large-icmp: Specifies large ICMP packet attack signature.
large-icmpv6: Specifies large ICMPv6 packet attack signature.
length: Specifies the maximum length of safe ICMP or ICMPv6 packets, in bytes. The value range for ICMP packets is 28 to 65534. The value range for ICMPv6 packets is 48 to 65534.
Examples
# Set the maximum length of safe ICMP packets for large ICMP attack to 50000 bytes in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] signature large-icmp max-length 50000
Related commands
signature detect
signature detect
Use signature detect to enable signature detection for single-packet attacks and specify the prevention actions.
Use undo signature detect to disable signature detection for single-packet attacks.
Syntax
signature detect { fraggle | fragment | impossible | land | large-icmp | large-icmpv6 | smurf | snork | tcp-all-flags | tcp-fin-only | tcp-invalid-flags | tcp-null-flag | tcp-syn-fin | tiny-fragment | traceroute | udp-bomb | winnuke } [ action { { drop | logging } * | none } ]
undo signature detect { fraggle | fragment | impossible | land | large-icmp | large-icmpv6 | smurf | snork | tcp-all-flags | tcp-fin-only | tcp-invalid-flags | tcp-null-flag | tcp-syn-fin | tiny-fragment | traceroute | udp-bomb | winnuke }
signature detect { ip-option-abnormal | ping-of-death | teardrop } action { drop | logging } *
undo signature detect { ip-option-abnormal | ping-of-death | teardrop }
signature detect icmp-type { icmp-type-value | address-mask-reply | address-mask-request | destination-unreachable | echo-reply | echo-request | information-reply | information-request | parameter-problem | redirect | source-quench | time-exceeded | timestamp-reply | timestamp-request } [ action { { drop | logging } * | none } ]
undo signature detect icmp-type { icmp-type-value | address-mask-reply | address-mask-request | destination-unreachable | echo-reply | echo-request | information-reply | information-request | parameter-problem | redirect | source-quench | time-exceeded | timestamp-reply | timestamp-request }
signature detect icmpv6-type { icmpv6-type-value | destination-unreachable | echo-reply | echo-request | group-query | group-reduction | group-report | packet-too-big | parameter-problem | time-exceeded } [ action { { drop | logging } * | none } ]
undo signature detect icmpv6-type { icmpv6-type-value | destination-unreachable | echo-reply | echo-request | group-query | group-reduction | group-report | packet-too-big | parameter-problem | time-exceeded }
signature detect ip-option { option-code | internet-timestamp | loose-source-routing | record-route | route-alert | security | stream-id | strict-source-routing } [ action { { drop | logging } * | none } ]
undo signature detect ip-option { option-code | internet-timestamp | loose-source-routing | record-route | route-alert | security | stream-id | strict-source-routing }
signature detect ipv6-ext-header ext-header-value [ action { { drop | logging } * | none } ]
undo signature detect ipv6-ext-header next-header-value
signature detect ipv6-ext-header-abnormal [ action { { drop | logging } * | none } ]
undo signature detect ipv6-ext-header-abnormal
signature detect ipv6-ext-header-exceed [ limit limit-value ] [ action { { drop | logging } * | none } ]
undo signature detect ipv6-ext-header-exceed
Default
Signature detection is disabled for all single-packet attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
fraggle: Specifies the fraggle attack.
fragment: Specifies the IP fragment attack.
icmp-type: Specifies an ICMP packet attack by the packet type. You can specify the packet type by a number or a keyword:
· icmp-type-value: Specifies the ICMP packet type in the range of 0 to 255.
· address-mask-reply: Specifies the ICMP address mask reply type.
· address-mask-request: Specifies the ICMP address mask request type.
· destination-unreachable: Specifies the ICMP destination unreachable type.
· echo-reply: Specifies the ICMP echo reply type.
· echo-request: Specifies the ICMP echo request type.
· information-reply: Specifies the ICMP information reply type.
· information-request: Specifies the ICMP information request type.
· parameter-problem: Specifies the ICMP parameter problem type.
· redirect: Specifies the ICMP redirect type.
· source-quench: Specifies the ICMP source quench type.
· time-exceeded: Specifies the ICMP time exceeded type.
· timestamp-reply: Specifies the ICMP timestamp reply type.
· timestamp-request: Specifies the ICMP timestamp request type.
icmpv6-type: Specifies an ICMPv6 packet attack by the packet type. You can specify the packet type by a number or a keyword:
· icmpv6-type-value: Specifies the ICMPv6 packet type in the range of 0 to 255.
· destination-unreachable: Specifies the ICMPv6 destination unreachable type.
· echo-reply: Specifies the ICMPv6 echo reply type.
· echo-request: Specifies the ICMPv6 echo request type.
· group-query: Specifies the ICMPv6 group query type.
· group-reduction: Specifies the ICMPv6 group reduction type.
· group-report: Specifies the ICMPv6 group report type.
· packet-too-big: Specifies the ICMPv6 packet too big type.
· parameter-problem: Specifies the ICMPv6 parameter problem type.
· time-exceeded: Specifies the ICMPv6 time exceeded type.
impossible: Specifies the IP impossible packet attack.
ip-option: Specifies an IP option. You can specify the IP option by a number or a keyword:
· option-code: Specifies the IP option in the range of 1 to 255.
· internet-timestamp: Specifies the timestamp option.
· loose-source-routing: Specifies the loose source routing option.
· record-route: Specifies the record route option.
· route-alert: Specifies the route alert option.
· security: Specifies the security option.
· stream-id: Specifies the stream identifier option.
· strict-source-routing: Specifies the strict source route option.
ip-option-abnormal: Specifies the abnormal IP option attack.
ipv6-ext-header ext-header-value: Specifies an IPv6 extension header by its value in the range of 0 to 255.
ipv6-ext-header-abnormal: Specifies the abnormal IPv6 extension header attack.
ipv6-ext-header-exceed: Specifies the IPv6 extension header exceeded attack.
land: Specifies the Land attack.
large-icmp: Specifies the large ICMP packet attack.
large-icmpv6: Specifies the large ICMPv6 packet attack.
limit limit-value: Specifies the upper limit of IPv6 extension headers. The value range is 0 to 7, and the default is 0. An IPv6 packet is an IPv6 extension header exceeded attack packet if the number of its IPv6 extension headers exceeds the upper limit.
ping-of-death: Specifies the ping-of-death attack.
smurf: Specifies the smurf attack.
snork: Specifies the UDP snork attack.
tcp-all-flags: Specifies the attack where the TCP packet has all flags set.
tcp-fin-only: Specifies the attack where the TCP packet has only the FIN flag set.
tcp-invalid-flags: Specifies the attack that uses TCP packets with invalid flags.
tcp-null-flag: Specifies the attack where the TCP packet has no flags set.
tcp-syn-fin: Specifies the attack where the TCP packet has both SYN and FIN flags set.
teardrop: Specifies the teardrop attack.
tiny-fragment: Specifies the tiny fragment attack.
traceroute: Specifies the traceroute attack.
udp-bomb: Specifies the UDP bomb attack.
winnuke: Specifies the WinNuke attack.
action: Specifies the actions against the single-packet attack. If you do not specify this keyword, the default action of the attack level to which the single-packet attack belongs is used.
drop: Drops packets that match the specified signature.
logging: Enables logging for the specified single-packet attack.
none: Takes no action.
Usage guidelines
You can use this command multiple times to enable signature detection for multiple single-packet attack types.
When you specify a packet type by a number, if the packet type has a corresponding keyword, the keyword is displayed in command output. If the packet type does not have a corresponding keyword, the number is displayed.
In abnormal IPv6 extension header and IPv6 extension header exceeded attack detection, the device examines the ESP header and headers before it. Headers after the ESP header are not examined.
The logging keyword enables the attack detection and prevention module to log single-packet attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output single-packet attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view single-packet attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Enable signature detection for the IP fragment attack and specify the prevention action as drop in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] signature detect fragment action drop
Related commands
signature level action
signature level action
Use signature level action to specify the actions against single-packet attacks on a specific level.
Use undo signature level action to restore the default.
Syntax
signature level { high | info | low | medium } action { { drop | logging } * | none }
undo signature level { high | info | low | medium } action
Default
For informational-level and low-level single-packet attacks, the action is logging.
For medium-level and high-level single-packet attacks, the actions are logging and drop.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
high: Specifies the high level. None of the currently supported single-packet attacks belongs to this level.
info: Specifies the informational level. For example, large ICMP packet attack is on this level.
low: Specifies the low level. For example, the traceroute attack is on this level.
medium: Specifies the medium level. For example, the WinNuke attack is on this level.
drop: Drops packets that match the specified level.
logging: Enable logging for single-packet attacks on the specified level.
none: Takes no action.
Usage guidelines
According to their severity, single-packet attacks are divided into four levels: info, low, medium, and high. Enabling signature detection for a specific level enables signature detection for all single-packet attacks on that level.
If you enable signature detection for a single-packet attack also by using the signature detect command, action parameters in the signature detect command take effect.
The logging keyword enables the attack detection and prevention module to log single-packet attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output single-packet attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view single-packet attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify the action against informational-level single-packet attacks as drop in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy 1
[Sysname-attack-defense-policy-1] signature level info action drop
Related commands
signature detect
signature level detect
signature level detect
Use signature level detect to enable signature detection for single-packet attacks on a specific level.
Use undo signature level detect to disable signature detection for single-packet attacks on a specific level.
Syntax
signature level { high | info | low | medium } detect
undo signature level { high | info | low | medium } detect
Default
Signature detection is disabled for all levels of single-packet attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
high: Specifies the high level. None of the currently supported single-packet attacks belongs to this level.
info: Specifies the informational level. For example, large ICMP packet attack is on this level.
low: Specifies the low level. For example, the traceroute attack is on this level.
medium: Specifies the medium level. For example, the WinNuke attack is on this level.
Usage guidelines
According to their severity, single-packet attacks are divided into four levels: info, low, medium, and high. Enabling signature detection for a specific level enables signature detection for all single-packet attacks on that level. Use the signature level action command to specify the actions against single-packet attacks on a specific level. If you enable signature detection for a single-packet attack also by using the signature detect command, action parameters in the signature detect command take effect.
To display the level to which a single-packet attack belongs, use the display attack-defense policy command.
Examples
# Enable signature detection for informational-level single-packet attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy 1
[Sysname-attack-defense-policy-1] signature level info detect
Related commands
display attack-defense policy
signature detect
signature level action
sip-flood action
Use sip-flood action to specify global actions against SIP flood attacks.
Use undo sip-flood action to restore the default.
Syntax
sip-flood action { drop | logging } *
undo sip-flood action
Default
No global action is specified for SIP flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent SIP packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent SIP packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for SIP flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log SIP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output SIP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view SIP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against SIP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood action drop
Related commands
sip-flood detect
sip-flood detect non-specific
sip-flood port
sip-flood source-threshold
sip-flood threshold
sip-flood detect
Use sip-flood detect to configure IP address-specific SIP flood attack detection.
Use undo sip-flood detect to remove IP address-specific SIP flood attack detection configuration.
Syntax
sip-flood detect { ip ipv4-address | ipv6 ipv6-address } [ port port-list ] [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo sip-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific SIP flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
port port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number. If you do not specify this option, the global ports apply.
threshold threshold-value: Specifies the maximum receiving rate in pps for SIP packets that are destined for the protected IP address. The value range is 1 to 1000000, and the default value is 1000.
action: Specifies the actions against a detected SIP flood attack. If no action is specified, the global actions set by the sip-flood action command apply.
drop: Drops subsequent SIP packets destined for the protected IP address.
logging: Enables logging for SIP flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With SIP flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of SIP packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure SIP flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log SIP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output SIP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view SIP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure SIP flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood detect ip 192.168.1.2 threshold 2000
Related commands
sip-flood action
sip-flood detect non-specific
sip-flood port
sip-flood threshold
sip-flood detect non-specific
Use sip-flood detect non-specific to enable global SIP flood attack detection.
Use undo sip-flood detect non-specific to disable global SIP flood attack detection.
Syntax
sip-flood detect non-specific
undo sip-flood detect non-specific
Default
Global SIP flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following SIP flood attack prevention types:
· Source-based SIP flood attack prevention—Monitors the receiving rate of SIP packets on a per-source IP basis.
· Destination-based SIP flood attack prevention—Monitors the receiving rate of SIP packets on a per-destination IP basis.
The global SIP flood attack detection applies to all IP addresses except those specified by the sip-flood detect command. The global detection is configured by using the following commands:
· Global ports set by using the sip-flood port command.
· Global trigger threshold set by using the sip-flood threshold or sip-flood source-threshold command.
· Global actions specified by using the sip-flood action command.
Examples
# Enable global SIP flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood detect non-specific
Related commands
sip-flood action
sip-flood detect
sip-flood port
sip-flood source-threshold
sip-flood threshold
sip-flood port
Use sip-flood port to specify the global ports to be protected against SIP flood attacks.
Use undo sip-flood port to restore the default.
Syntax
sip-flood port port-list
undo sip-flood port
Default
The global SIP flood attack prevention protects port 5060.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
port-list: Specifies a space-separated list of up to 32 port number items. Each item specifies a port by its port number or a range of ports in the form of start-port-number to end-port-number. The end-port-number cannot be smaller than the start-port-number.
Usage guidelines
The device detects only SIP packets destined for the specified ports.
The global ports apply to global SIP flood attack detection and IP address-specific SIP flood attack detection with no port specified.
Examples
# Specify ports 5060 and 65530 as the global ports to be protected against SIP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood port 5060 65530
Related commands
sip-flood action
sip-flood detect
sip-flood detect non-specific
sip-flood source-threshold
sip-flood threshold
sip-flood threshold
Use sip-flood threshold to set the global threshold for triggering destination-based SIP flood attack prevention.
Use undo sip-flood threshold to restore the default.
Syntax
sip-flood threshold threshold-value
undo sip-flood threshold
Default
The global threshold is 10000 for triggering destination-based SIP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SIP packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based SIP flood attack prevention is disabled.
Usage guidelines
With global SIP flood attack detection configured, the device is in attack detection state. When the receiving rate of SIP packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global SIP flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of SIP packets sent to a protected SIP server is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based SIP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood threshold 100
Related commands
sip-flood action
sip-flood detect
sip-flood detect non-specific
sip-flood source-threshold
Use sip-flood source-threshold to set the global threshold for triggering source-based SIP flood attack prevention.
Use undo sip-flood source-threshold to restore the default.
Syntax
sip-flood source-threshold threshold-value
undo sip-flood source-threshold
Default
The global threshold is 10000 for triggering source-based SIP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SIP packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based SIP flood attack prevention is disabled.
Usage guidelines
With global SIP flood attack detection configured, the device is in attack detection state. When the receiving rate of SIP packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based SIP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] sip-flood source-threshold 100
Related commands
sip-flood action
sip-flood detect
sip-flood detect non-specific
sip-flood port
syn-ack-flood action
Use syn-ack-flood action to specify global actions against SYN-ACK flood attacks.
Use undo syn-ack-flood action to restore the default.
Syntax
syn-ack-flood action { drop | logging }*
undo syn-ack-flood action
Default
No global action is specified for SYN-ACK flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent SYN-ACK packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent SYN-ACK packets originating from the attacker IP addresses in source-based flood attack prevention..
logging: Enables logging for SYN-ACK flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against SYN-ACK flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-ack-flood action drop
Related commands
syn-ack-flood detect
syn-ack-flood detect non-specific
syn-ack-flood source-threshold
syn-ack-flood threshold
syn-ack-flood detect
Use syn-ack-flood detect to configure IP address-specific SYN-ACK flood attack detection.
Use undo syn-ack-flood detect to remove the IP address-specific SYN-ACK flood attack detection configuration.
Syntax
syn-ack-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo syn-ack-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific SYN-ACK flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for SYN-ACK packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected SYN-ACK flood attack. If no action is specified, the global actions set by the syn-ack-flood action command apply.
drop: Drops subsequent SYN-ACK packets destined for the protected IP address.
logging: Enables logging for SYN-ACK flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With SYN-ACK flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of SYN-ACK packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure SYN-ACK flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log SYN-ACK flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output SYN-ACK flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view SYN-ACK flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure SYN-ACK flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-ack-flood detect ip 192.168.1.2 threshold 2000
Related commands
syn-ack-flood action
syn-ack-flood detect non-specific
syn-ack-flood threshold
syn-ack-flood detect non-specific
Use syn-ack-flood detect non-specific to enable global SYN-ACK flood attack detection.
Use undo syn-ack-flood detect non-specific to disable global SYN-ACK flood attack detection.
Syntax
syn-ack-flood detect non-specific
undo syn-ack-flood detect non-specific
Default
Global SYN-ACK flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following SYN-ACK flood attack prevention types:
· Source-based SYN-ACK flood attack prevention—Monitors the receiving rate of SYN-ACK packets on a per-source IP basis.
· Destination-based SYN-ACK flood attack prevention—Monitors the receiving rate of SYN-ACK packets on a per-destination IP basis.
The global SYN-ACK flood attack detection applies to all IP addresses except for those specified by the syn-ack-flood detect command. The global detection uses the global trigger threshold set by the syn-ack-flood threshold or syn-ack-flood source-threshold command and global actions specified by the syn-ack-flood action command.
Examples
# Enable global SYN-ACK flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-ack-flood detect non-specific
Related commands
syn-ack-flood action
syn-ack-flood detect
syn-ack-flood source-threshold
syn-ack-flood threshold
syn-ack-flood threshold
Use syn-ack-flood threshold to set the global threshold for triggering destination-based SYN-ACK flood attack prevention.
Use undo syn-ack-flood threshold to restore the default.
Syntax
syn-ack-flood threshold threshold-value
undo syn-ack-flood threshold
Default
The global threshold is 10000 for triggering destination-based SYN-ACK flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SYN-ACK packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based SYN-ACK flood attack prevention is disabled.
Usage guidelines
With global SYN-ACK flood attack detection configured, the device is in attack detection state. When the receiving rate of SYN-ACK packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global SYN-ACK flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of SYN-ACK packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based SYN-ACK flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-ack-flood threshold 100
Related commands
syn-ack-flood action
syn-ack-flood detect
syn-ack-flood detect non-specific
syn-ack-flood source-threshold
Use syn-ack-flood source-threshold to set the global threshold for triggering source-based SYN-ACK flood attack prevention.
Use undo syn-ack-flood source-threshold to restore the default.
Syntax
syn-ack-flood source-threshold threshold-value
undo syn-ack-flood source-threshold
Default
The global threshold is 10000 for triggering source-based SYN-ACK flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SYN-ACK packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based SYN-ACK flood attack prevention is disabled.
Usage guidelines
With global SYN-ACK flood attack detection configured, the device is in attack detection state. When the receiving rate of SYN-ACK packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based SYN-ACK flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-ack-flood source-threshold 100
Related commands
syn-ack-flood action
syn-ack-flood detect
syn-ack-flood detect non-specific
syn-flood action
Use syn-flood action to specify global actions against SYN flood attacks.
Use undo syn-flood action to restore the default.
Syntax
syn-flood action { drop | logging } *
undo syn-flood action
Default
No global action is specified for SYN flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent SYN packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent SYN packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for SYN flood attack events. The log messages will be sent to the log system.
Examples
# Specify drop as the global action against SYN flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-flood action drop
Related commands
syn-flood detect
syn-flood detect non-specific
syn-flood source-threshold
syn-flood threshold
syn-flood detect
Use syn-flood detect to configure IP address-specific SYN flood attack detection.
Use undo syn-flood detect to remove the IP address-specific SYN flood attack detection configuration.
Syntax
syn-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo syn-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific SYN flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::.
threshold threshold-value: Specifies the maximum receiving rate in pps for SYN packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected SYN flood attack. If no action is specified, the global actions set by the syn-flood action command apply.
drop: Drops subsequent SYN packets destined for the protected IP address.
logging: Enables logging for SYN flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With SYN flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of SYN packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure SYN flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log SYN flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output SYN flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view SYN flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure SYN flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-flood detect ip 192.168.1.2 threshold 2000
Related commands
syn-flood action
syn-flood detect non-specific
syn-flood threshold
syn-flood detect non-specific
Use syn-flood detect non-specific to enable global SYN flood attack detection.
Use undo syn-flood detect non-specific to disable global SYN flood attack detection.
Syntax
syn-flood detect non-specific
undo syn-flood detect non-specific
Default
Global SYN flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following SYN flood attack prevention types:
· Source-based SYN flood attack prevention—Monitors the receiving rate of SYN packets on a per-source IP basis.
· Destination-based SYN flood attack prevention—Monitors the receiving rate of SYN packets on a per-destination IP basis.
The global SYN flood attack detection applies to all IP addresses except for those specified by the syn-flood detect command. The global detection uses the global trigger threshold set by the syn-flood threshold or syn-flood source-threshold command and global actions specified by the syn-flood action command.
Examples
# Enable global SYN flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-flood detect non-specific
Related commands
syn-flood action
syn-flood detect
syn-flood source-threshold
syn-flood threshold
syn-flood threshold
Use syn-flood threshold to set the global threshold for triggering destination-based SYN flood attack prevention.
Use undo syn-flood threshold to restore the default.
Syntax
syn-flood threshold threshold-value
undo syn-flood threshold
Default
The global threshold is 10000 for triggering destination-based SYN flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SYN packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based SYN flood attack prevention is disabled.
Usage guidelines
With global SYN flood attack detection configured, the device is in attack detection state. When the receiving rate of SYN packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global SYN flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of SYN packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based SYN flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-flood threshold 100
Related commands
syn-flood action
syn-flood detect
syn-flood detect non-specific
syn-flood source-threshold
Use syn-flood source-threshold to set the global threshold for triggering source-based SYN flood attack prevention.
Use undo syn-flood source-threshold to restore the default.
Syntax
syn-flood source-threshold threshold-value
undo syn-flood source-threshold
Default
The global threshold is 10000 for triggering source-based SYN flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for SYN packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based SYN flood attack prevention is disabled.
Usage guidelines
With global SYN flood attack detection configured, the device is in attack detection state. When the receiving rate of SYN packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based SYN flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] syn-flood source-threshold 100
Related commands
syn-flood action
syn-flood detect
syn-flood detect non-specific
threshold-learn apply
Use threshold-learn apply to apply the most recent threshold that the device has learned.
Syntax
threshold-learn apply
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
You can configure this command to apply the most recent threshold that the device has learned to a flood attack defense policy that meets the following requirements:
· The threshold learning feature is enabled for the policy.
· Auto applying the learned threshold is disabled for the policy.
The learned threshold is set as the global threshold for triggering flood attack prevention. The command does not take effect when auto application of the learned threshold is enabled for the policy. If you execute this command multiple times, the most recent configuration takes effect.
Before you apply the most recently learned threshold to a flood attack defense policy, make sure global attack detection is enabled for all existing flood types in this policy.
Examples
# Apply the most recent threshold that the device has learned to attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn apply
Related commands
threshold-learn enable
threshold-learn auto-apply enable
Use threshold-learn auto-apply enable to enable auto application of the learned threshold.
Use undo threshold-learn auto-apply enable to disable auto application of the learned threshold.
Syntax
threshold-learn auto-apply enable
undo threshold-learn auto-apply enable
Default
Auto application of the learned threshold is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
This command applies to only flood attack defense policies that are enabled with the threshold learning feature (set with the threshold-learn enable command). Each time the device learns a threshold, it uses the learned value to update the global threshold for triggering flood attack prevention. The formula for calculating the new global threshold is learned threshold × (1 + tolerance value). The learned threshold equals the peak packet receiving rate that the device has learned within the learning duration.
To set a tolerance value, execute the threshold-learn tolerance-value command. Setting a tolerance value can prevent packet loss when the network experiences a traffic spike without being attacked.
Before you apply the most recently learned threshold to a flood attack defense policy, make sure global attack detection is enabled for all existing flood types in this policy.
Examples
# Enable auto application of the learned threshold for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn auto-apply enable
Related commands
threshold-learn enable
threshold-learn tolerance-value
threshold-learn duration
Use threshold-learn duration to set the threshold learning duration.
Use undo threshold-learn duration to restore the default.
Syntax
threshold-learn duration duration
undo threshold-learn duration
Default
The threshold learning duration is 1440 minutes.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
duration: Specifies the threshold learning duration in the range of 1 to 1200000 minutes.
Usage guidelines
The device starts threshold learning when you apply an attack defense policy enabled with the threshold learning feature. The learned threshold equals the peak packet receiving rate learned within the duration. To ensure that the device learns the peak rate in a whole day, set a learning duration longer than 1440 minutes (24 hours). If you change the learning duration during the learning process, the device will restart threshold learning.
Examples
# Set the threshold learning duration to 2880 minutes (48 hours) for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn duration 2880
Related commands
threshold-learn enable
threshold-learn loop
threshold-learn enable
Use threshold-learn enable to enable the threshold learning feature for flood attack prevention.
Use undo threshold-learn enable to disable the threshold learning feature for flood attack prevention.
Syntax
threshold-learn enable
undo threshold-learn enable
Default
The threshold learning feature for flood attack prevention is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
An appropriate threshold can effectively prevent attacks. If the global threshold for triggering flood attack prevention is too low, false positives might occur, causing performance degradation or packet loss. If the global threshold is too high, false negatives might occur, making the network defenseless. Therefore, it is a good practice to enable the threshold learning feature. This feature allows the device to automatically learn the global threshold based on the traffic flows in the network.
Examples
# Enable the threshold learning feature for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn enable
Related commands
threshold-learn auto-apply enable
threshold-learn duration
threshold-learn interval
Use threshold-learn interval to set the threshold learning interval.
Use undo threshold-learn interval to restore the default.
Syntax
threshold-learn interval interval
undo threshold-learn interval
Default
The threshold learning interval is 1440 minutes.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
interval: Specifies a threshold learning interval in the range of 1 to 1200000 minutes.
Usage guidelines
The device performs periodic threshold learning when you apply an attack defense policy that meets the following requirements:
· The threshold learning feature is enabled for the policy by using the threshold-learn enable command.
· The periodic learning mode is set by using the threshold-learn mode periodic command.
Examples
# Set the threshold learning interval to 120 minutes for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn interval 120
Related commands
threshold-learn enable
threshold-learn mode
threshold-learn mode
Use threshold-learn mode to set the threshold learning mode.
Use undo threshold-learn mode to restore the default.
Syntax
threshold-learn mode { once | periodic }
undo threshold-learn mode
Default
The one-time learning mode is set.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
once: Specifies the one-time learning mode.
periodic: Specifies the periodic learning mode.
Usage guidelines
This command allows you to set the following threshold learning modes:
· One-time learning—The device performs threshold learning only once. This mode is applicable to stable networks.
· Periodic learning—The device performs threshold learning at intervals. The most recent learned threshold always takes effect. This mode is applicable to unstable networks. To set the threshold learning duration, use the threshold-learn duration command. To set the threshold learning interval, use the threshold-learn interval command.
Examples
# Set the periodic learning mode for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn mode periodic
Related commands
threshold-learn duration
threshold-learn enable
threshold-learn interval
threshold-learn tolerance-value
Use threshold-learn tolerance-value to set the threshold learning tolerance value.
Use undo threshold-learn tolerance-value to restore the default.
Syntax
threshold-learn tolerance-value tolerance-value
undo threshold-learn tolerance-value
Default
The threshold learning tolerance value is 50.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
tolerance-value: Specifies the threshold learning tolerance value in percentage, in the range of 0 to 4000.
Usage guidelines
When auto applying the learned threshold is enabled, the device uses the learned threshold and tolerance value to calculate the global threshold for triggering flood attack prevention. The formula for calculating the global threshold is learned threshold × (1 + tolerance value). Therefore, the calculated global threshold is larger than the learned threshold. This can prevent packet loss when the network experiences a traffic spike without being attacked.
The tolerance value takes effect only when auto applying the learned threshold is enabled.
Examples
# Set the threshold learning tolerance value to 100 for attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn auto-apply enable
[Sysname-attack-defense-policy-atk-policy-1] threshold-learn tolerance-value 100
Related commands
threshold-learn auto-apply enable
threshold-learn enable
udp-flood action
Use udp-flood action to specify global actions against UDP flood attacks.
Use undo udp-flood action to restore the default.
Syntax
udp-flood action { drop | logging } *
undo udp-flood action
Default
No global action is specified for UDP flood attacks.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
drop: Drops subsequent UDP packets destined for the victim IP addresses in destination-based flood attack prevention, or drops subsequent UDP packets originating from the attacker IP addresses in source-based flood attack prevention.
logging: Enables logging for UDP flood attack events. The log messages will be sent to the log system.
Usage guidelines
The logging keyword enables the attack detection and prevention module to log UDP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output UDP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view UDP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Specify drop as the global action against UDP flood attacks in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] udp-flood action drop
Related commands
udp-flood detect
udp-flood detect non-specific
udp-flood source-threshold
udp-flood threshold
udp-flood detect
Use udp-flood detect to configure IP address-specific UDP flood attack detection.
Use undo udp-flood detect to remove the IP address-specific UDP flood attack detection configuration.
Syntax
udp-flood detect { ip ipv4-address | ipv6 ipv6-address } [ threshold threshold-value ] [ action { { drop | logging } * | none } ]
undo udp-flood detect { ip ipv4-address | ipv6 ipv6-address }
Default
IP address-specific UDP flood attack detection is not configured.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IPv4 address to be protected. The ip-address argument cannot be 255.255.255.255 or 0.0.0.0.
ipv6 ipv6-address: Specifies the IPv6 address to be protected. The IPv6 address cannot be a multicast address or ::
threshold threshold-value: Specifies the maximum receiving rate in pps for UDP packets that are destined for the protected IP address. The value range is 1 to 1000000.
action: Specifies the actions against a detected UDP flood attack. If no action is specified, the global actions set by the udp-flood action command apply.
drop: Drops subsequent UDP packets destined for the protected IP address.
logging: Enables logging for UDP flood attack events. The log messages will be sent to the log system.
none: Takes no action.
Usage guidelines
With UDP flood attack detection configured for an IP address, the device is in attack detection state. When the receiving rate of UDP packets destined for the IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
You can configure UDP flood attack detection for multiple IP addresses in one attack defense policy.
The logging keyword enables the attack detection and prevention module to log UDP flood attack events and send log messages to the information center.
With the information center, you can set log message filtering and output rules, including output destinations.
The information center can output UDP flood attack logs to any destinations except the console and the monitor terminal. If you configure the console or monitor terminal as an output destination, the output destination setting will not take effect.
To view UDP flood attack logs stored on the device, use the display logbuffer command. Make sure you do not disable log output to the log buffer, which is enabled by default.
For more information about configuring the information center, see Device Management Configuration Guide.
Examples
# Configure UDP flood attack detection for 192.168.1.2 in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] udp-flood detect ip 192.168.1.2 threshold 2000
Related commands
udp-flood action
udp-flood detect non-specific
udp-flood threshold
udp-flood detect non-specific
Use udp-flood detect non-specific to enable global UDP flood attack detection.
Use undo udp-flood detect non-specific to disable global UDP flood attack detection.
Syntax
udp-flood detect non-specific
undo udp-flood detect non-specific
Default
Global UDP flood attack detection is disabled.
Views
Attack defense policy view
Predefined user roles
network-admin
Usage guidelines
The device supports the following UDP flood attack prevention types:
· Source-based UDP flood attack prevention—Monitors the receiving rate of UDP packets on a per-source IP basis.
· Destination-based UDP flood attack prevention—Monitors the receiving rate of UDP packets on a per-destination IP basis.
The global UDP flood attack detection applies to all IP addresses except for those specified by the udp-flood detect command. The global detection uses the global trigger threshold set by the udp-flood threshold or udp-flood source-threshold command and global actions specified by the udp-flood action command.
Examples
# Enable global UDP flood attack detection in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] udp-flood detect non-specific
Related commands
udp-flood action
udp-flood detect
udp-flood source-threshold
udp-flood threshold
udp-flood threshold
Use udp-flood threshold to set the global threshold for triggering destination-based UDP flood attack prevention.
Use undo udp-flood threshold to restore the default.
Syntax
udp-flood threshold threshold-value
undo udp-flood threshold
Default
The global threshold is 10000 for triggering destination-based UDP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for UDP packets that are destined for an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the destination-based UDP flood attack prevention is disabled.
Usage guidelines
With global UDP flood attack detection configured, the device is in attack detection state. When the receiving rate of UDP packets destined for an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
The global threshold applies to global UDP flood attack detection. Adjust the threshold according to the application scenarios.
· If the number of UDP packets sent to a protected server, such as an HTTP or FTP server, is normally large, set a high threshold. A low threshold might affect the server services.
· For a network that is unstable or susceptible to attacks, set a low threshold.
Examples
# Set the global threshold to 100 for triggering destination-based UDP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] rst-flood threshold 100
Related commands
udp-flood action
udp-flood detect
udp-flood detect non-specific
udp-flood source-threshold
udp-flood source-threshold
Use udp-flood source-threshold to set the global threshold for triggering source-based UDP flood attack prevention.
Use undo udp-flood source-threshold to restore the default.
Syntax
udp-flood source-threshold threshold-value
undo udp-flood source-threshold
Default
The global threshold is 10000 for triggering source-based UDP flood attack prevention.
Views
Attack defense policy view
Predefined user roles
network-admin
Parameters
threshold-value: Specifies the maximum receiving rate in pps for UDP packets that originate from an IP address. The value range is 0 to 1000000. If you set the threshold value to 0, the source-based UDP flood attack prevention is disabled.
Usage guidelines
With global UDP flood attack detection configured, the device is in attack detection state. When the receiving rate of UDP packets originating from an IP address keeps reaching or exceeding the threshold, the device enters prevention state and takes the specified actions. When the rate drops below the silence threshold (three-fourths of the threshold), the device returns to the attack detection state.
Examples
# Set the global threshold to 100 for triggering source-based UDP flood attack prevention in attack defense policy atk-policy-1.
<Sysname> system-view
[Sysname] attack-defense policy atk-policy-1
[Sysname-attack-defense-policy-atk-policy-1] udp-flood source-threshold 100
Related commands
udp-flood action
udp-flood detect
udp-flood detect non-specific
whitelist enable
Use whitelist enable to enable the whitelist feature on an interface.
Use undo whitelist enable to disable the whitelist feature on an interface.
Syntax
whitelist enable
undo whitelist enable
Default
The whitelist feature is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
If the global whitelist feature is enabled, the whitelist feature is enabled on all interfaces. If the global whitelist feature is disabled, you can use this command to enable the whitelist feature on individual interfaces.
Examples
# Enable the whitelist feature on VLAN-interface 100.
<Sysname> system-view
[Sysname] interface vlan-interface 100
[Sysname-Vlan-interface100] whitelist enable
whitelist global enable
Use whitelist global enable to enable the global whitelist feature.
Use undo whitelist global enable to disable the global whitelist feature.
Syntax
whitelist global enable
undo whitelist global enable
Default
The global whitelist feature is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
If you enable the global whitelist feature, the whitelist feature is enabled on all interfaces.
Examples
# Enable the global whitelist feature.
<Sysname> system-view
[Sysname] whitelist global enable
whitelist object-group
Use whitelist object-group to add an address object group to the whitelist.
Use undo whitelist object-group to restore the default.
Syntax
whitelist object-group object-group-name
undo whitelist object-group
Default
No address object group is added to the whitelist.
Views
System view
Predefined user roles
network-admin
Parameters
object-group-name: Specifies an address object group by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
This command must be used together with the address object group feature. For more information about address object groups, see object group configuration in Security Configuration Guide.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Add address object group object-group1 to the whitelist.
<Sysname> system-view
[Sysname] whitelist object-group object-group1
