No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - Security

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the basic concepts, configuration procedures, and configuration examples in different application scenarios of the network management feature supported by the device.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Traffic Identification Rules

Configuring Traffic Identification Rules


To implement destination-based accounting, the device must be able to identify the traffic destined for different networks according to access control lists (ACLs).


  1. Run system-view

    The system view is displayed.

  2. Configure traffic identification rules.

    1. Run acl [ number ] acl-number [ match-order { auto | config } ]

      An advanced ACL is created by using an ACL number and the advanced ACL view is displayed.

      Or run acl name acl-name { advance | acl-number } [ match-order { auto | config } ]

      An advanced ACL is created by using an ACL name and the advanced ACL view is displayed.

      By default, no ACL exists on the device.

    2. Run rule [ rule-id ] permit ip { source { source-ip-address { source-wildcard | src-netmask } | any } | destination { destination-ip-address { destination-wildcard | des-netmask } | any } } *

      An advanced ACL rule is created.

      By default, no ACL rule exists on the device.


    The number of an advanced ACL is in the range from 3000 to 3999.

    The ACL (with the number in the range of 3000-3031) configured or modified for wireless users takes effect only after being delivered to APs by the commit command.

    The destination address is mandatory and the source address is optional. You can configure both the source and destination addresses to precisely specify the traffic on which accounting is performed.

    If the any parameter is configured to specify all source and destination addresses, the traffic identification rule is invalid.

Updated: 2019-08-07

Document ID: EDOC1100034077

Views: 137187

Downloads: 244

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next