923
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.
logging
: Enables logging for UDP flood attack events.
Examples
# Specify
drop
as the global action against UDP flood attacks in the 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 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
} [
vpn-instance vpn-instance-name
]
[
threshold
threshold-value
] [
action
{ {
drop
|
logging
} * |
none
} ]
undo udp-flood detect
{
ip
ipv4-address
|
ipv6
ipv6-address
} [
vpn-instance vpn-instance-name
]
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
ipv4-address
argument cannot be
255.255.255.255 or 0.0.0.0.
ipv6
ipv6-address
: Specifies the IPv6 address to be protected.
vpn-instance vpn-instance-name
: Specifies the MPLS L3VPN instance to which the protected IP
address belongs. The
vpn-instance-name
argument is a case-sensitive string of 1 to 31 characters.
Do not specify this option if the protected IP address is on the public network.