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

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).
How Are deny and permit Actions in ACL Rules Used in Different Services?

How Are deny and permit Actions in ACL Rules Used in Different Services?

The deny and permit actions in ACL rules have different functions in different services.

  • Traffic policy

    1. When permit is used in the ACL rule, the system executes the specified traffic behavior only when traffic matches the ACL rule. When the traffic behavior is deny, the system discards traffic matching the rule. When the traffic behavior is permit, the system forwards traffic matching the rule.

    2. When deny is used in the ACL rule, the system discards packets when traffic matches the ACL rule, and the action in the traffic behavior does not take effect (except traffic statistics collection and traffic mirroring actions).

    3. If an ACL does not contain rules, the traffic policy referencing the ACL does not take effect.

  • Simplified traffic policy

    1. When permit is used in the ACL rule, the system executes the behavior in the simplified traffic policy, for example, allowing the matching packets to pass and limiting the rate of matching packets.

    2. When deny is used in the ACL rule and the ACL is applied to simplified traffic policy, the system discards the packets matching the ACL rule.

    3. If an ACL does not contain rules, the simplified traffic policy using the ACL does not take effect.

  • IPSec

    1. When permit is used in the ACL rule, the system uses IPSec policies to protect traffic matching the ACL rule, and then forwards the traffic.

    2. When deny is used in the ACL rule, the system discards the packets matching the ACL rule.

    3. When the ACL does not contain rules, the IPSec policy referencing the ACL does not take effect. That is, the system forwards the packets passing the interface without performing any other operation.

  • Firewall

    1. When permit is used in the ACL rule:
      • When the ACL is applied to the inbound traffic, the system forwards the packets matching the ACL rule sent from the low-priority zone to the high-priority zone.
      • When the ACL is applied to the outbound traffic, the system forwards the packets matching the ACL rule sent from the high-priority zone to the low-priority zone.
    2. When deny is used in the ACL rule:

      • When the ACL is applied to the inbound traffic, the system discards the packets matching the ACL rule sent from the low-priority zone to the high-priority zone.
      • When the ACL is applied to the outbound traffic, the system discards the packets matching the ACL rule sent from the high-priority zone to the low-priority zone.
    3. When the ACL does not contain rules:

      • When the ACL is applied to the inbound traffic, the ACL does not take effect, and the system discards all packets sent from the low-priority zone to the high-priority zone.
      • When the ACL is applied to the outbound traffic, the ACL does not take effect, and the system allows all packets sent from the high-priority zone to the low-priority zone.
  • NAT

    1. When permit is used in the ACL rule, the system uses the address pool to translate addresses for the packets of which the source IP address is specified in the ACL rule.

    2. When deny is used in the ACL rule or the ACL does not contain rules, the NAT policy referencing the ACL does not take effect. That is, the system searches routes for packets, but does not translate addresses.

  • Telnet

    1. When permit is used in the ACL rule:
      • When the ACL is applied to the inbound traffic, only the devices matching the ACL rule can access the local device.
      • When the ACL is applied to the outbound traffic, the local device can access other devices matching the ACL rule.
    2. When deny is used in the ACL rule:

      • When the ACL is applied to the inbound traffic, the devices matching the ACL rule cannot access the local device.
      • When the ACL is applied to the outbound traffic, the local device cannot access the devices matching the ACL rule.
    3. When the ACL contains rules but the packets from other devices do not match the ACL rules:

      • When the ACL is applied to the inbound traffic, other devices cannot access the local device.
      • When the ACL is applied to the outbound traffic, the local device cannot access other devices.
    4. When the ACL does not contain rules:

      • When the ACL is applied to the inbound traffic, any device can access the local device.
      • When the ACL is applied to the outbound traffic, the local device can access any device.
  • HTTP

    1. When permit is used in the ACL rule, another device with the specified source IP address can set up an HTTP connection with the local device.
    2. When deny is used in the ACL rule, other devices cannot set up HTTP connections with the local device.
    3. When the ACL contains rules but the packets from other devices do not match the ACL rules, other devices cannot set up HTTP connections with the local device.
    4. When the ACL does not contain rules, any device can set up an HTTP connection with the local device.
  • FTP

    1. When permit is used in the ACL rule, another device with the specified source IP address can set up an FTP connection with the local device.

    2. When deny is used in the ACL rule, other devices cannot set up FTP connections with the local device.

    3. When the ACL contains rules but the packets from other devices do not match the ACL rules, other devices cannot set up FTP connections with the local device.
    4. When the ACL does not contain rules, any device can set up an FTP connection with the local device.

  • TFTP

    1. When permit is used in the ACL rule, the local device can set up a TFTP connection with the device with the specified source IP address.

    2. When deny is used in the ACL rule, the local device cannot set up a TFTP connection with any device.

    3. When the ACL contains rules but the packets from other devices do not match the ACL rules, other devices cannot set up TFTP connections with the local device.
    4. When the ACL does not contain rules, the local device can set up TFTP connections with any devices.

  • SNMP

    1. When permit is used in the ACL rule, the NMS with the specified source IP address can access the local device.

    2. When deny is used in the ACL rule, no NMS can access the local device.

    3. When the ACL does not contain rules, any NMS can access the local device.

  • NTP

    1. When permit is used in the ACL rule, the access control right configured in ntp-service access takes effect.

    2. When deny is used in the ACL rule, the access control right configured in ntp-service access does not take effect.

    3. When the ACL does not contain rules, the access control right configured in ntp-service access does not take effect.

Translation
Download
Updated: 2019-05-20

Document ID: EDOC1100034077

Views: 112353

Downloads: 206

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