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 - VPN

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

This document describes VPN features on the device and provides configuration procedures and configuration examples.
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).
IPSec Does Not Take Effect When Both IPSec and NAT Are Configured on a Device Interface. How This Problem Is Solved?

IPSec Does Not Take Effect When Both IPSec and NAT Are Configured on a Device Interface. How This Problem Is Solved?

If NAT is configured on an interface to which an IPSec policy is applied, IPSec may not take effect. You can use the following methods:
  • Configure the destination IP address that matches the deny clause in an ACL referenced by NAT as the destination IP address in an ACL referenced by IPSec. In this case, data flows protected by IPSec are not translated by NAT.
  • Configure the ACL rule referenced by NAT to match the IP address translated by NAT.
NOTE:

After a deny rule is configured in NAT, you are advised to run the reset session all or reset nat session all command to delete incorrect NAT entries.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 153364

Downloads: 369

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