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

Reminder

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

upgrade

Configuration Guide - Security

S9300, S9300E, and S9300X V200R011C10

This document describes the configurations of Security, including ACL, reflective ACL, local attack defense, MFF, attack defense, traffic suppression and storm control, ARP security, port security, DHCP snooping, ND snooping, PPPoE+, IPSG, SAVI, URPF, keychain, separating the management plane from the service plane, security risks.
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 an Advanced ACL

Configuring an Advanced ACL

Context

Only advanced ACLs are supported in reflective ACL implementation. Therefore, you must configure an advanced ACL before using a reflective ACL.

The reflective ACL is applicable only to TCP, UDP, and ICMP protocols.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (Optional) Run time-range time-name { start-time to end-time days | from time1 date1 [ to time2 date2 ] }

    A time range is created.

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

    An advanced ACL with the specified number is created.

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

    An advanced ACL with the specified name is created.

    The acl-number value of an advanced ACL ranges from 3000 to 3999.

  4. Perform one of the following steps as required:

    You can configure the advanced ACL on the device according to the protocol type of IP packets. The reflective ACL is applicable to only the TCP, UDP, and ICMP protocols.

    • When protocol is TCP, run:

      rule [ rule-id ] { deny | permit } { protocol-number | tcp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | tcp-flag { ack | established | fin | psh | rst | syn | urg } * | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] *
    • When protocol is UDP, run:

      rule [ rule-id ] { deny | permit } { protocol-number | udp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] *
    • When protocol is ICMP, run:

      rule [ rule-id ] { deny | permit } { protocol-number | icmp } [ destination { destination-address destination-wildcard | any } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | icmp-type { icmp-name | icmp-type [ icmp-code ] } | source { source-address source-wildcard | any } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] *
    NOTE:

    The dscp dscp and precedence precedence parameters cannot be set for the same rule.

    The dscp dscp and tos tos parameters cannot be set for the same rule.

Translation
Download
Updated: 2019-04-01

Document ID: EDOC1000178410

Views: 126194

Downloads: 25

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