Defining Custom Dos Classifications - Avaya G250 Administration

Accessing the Avaya G250/G350 Media Gateway
Table 4: DoS attack classifications (continued)
DoS Attack
UNKNOW_L4_IP_PROTOCOL
UNATHENTICATED_ACCESS

Defining custom DoS classifications

You can define custom DoS attack classifications using Access Control List (ACL) rules. ACL
rules control which packets are authorized to pass through an interface. A custom DoS class is
defined by configuring criteria for an ACL rule and tagging the ACL with a DoS classification
label.
Note:
For general information about configuring policy rules, refer to
Note:
Chapter 20: Configuring policy
Defining a DoS class using ACLs
1. Use the ip access-control-list command to enter the configuration mode of an
ACL. For example:
G350-001(super)# ip access-control-list 301
2. Use the ip-rule command to enter the configuration mode of an ACL rule. For example:
G350-001(super)# ip-rule 1
3. Use the dos-classification command to configure the name of the DoS attack
classification. Possible values are: fraggle, smurf, ip-spoofing,
other-attack-100, other-attack-101, other-attack-102,
other-attack-103, other-attack-104, and other-attack-105. For example:
G350-001(super-ACL 301/ip rule 1)# dos-classification smurf
Done!
64 Administration for the Avaya G250 and Avaya G350 Media Gateways
Description
Packets with unknown (unsupported or
administratively closed) protocol in IP packet
with TO-ME interface as a destination.
Failure to authenticate services.
on page 531.
2 of 2