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

AR650, AR1600, and AR6100 V300R003

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).
(Optional) Configuring an Identity Filter Set

(Optional) Configuring an Identity Filter Set

Context

  • When a device functions as a responder during IKE negotiation, it can specify the peer allowed to connect to it to improve security.

    An IPSec policy template or an IPSec profile specifies the peer based on the identity filter set.

    As shown in Figure 4-32, the headquarters gateway RouterC functions as the responder. An IPSec policy template is configured on RouterC, only RouterA matches the IP address in the identity filter set.

    Figure 4-32  Responder specifying a qualified initiator
  • In an IPSec over DSVPN application, multiple mGRE tunnel interfaces are configured on the hub which provides only one IP address for spoke access. The mGRE tunnel interfaces use the same source address or source interface. To solve this problem, set parameters in the identity filter set to specify the mGRE tunnel interface of each IKE packet.

    For the detailed configuration of DSVPN, see DSVPN Configuration.

    In a DSVPN application as shown in Figure 4-33, Spoke1 and Spoke2 belong to DSVPN 1, while Spoke3 and Spoke4 belong to DSVPN 2. Spoke1 wants to communicate with Spoke2, and Spoke3 wants to communicate with Spoke4. However, the hub provides only one public network IP address for spokes access. After you configure an identity filter set on the hub, it determines the mGRE tunnel interface of each spoke based on parameters in the identity filter set.

    Figure 4-33  Responder specifying a qualified initiator in the IPSec over DSVPN application

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ike identity identity-name

    The identity filter set view is displayed.

    NOTE:
    You can set one or more parameters in the identity filter set view, depending on the device specification.

  3. (Optional) Run dn name

    The DN of an allowed peer for IKE negotiation is configured.

    By default, no DN of allowed peer for IKE negotiation is configured.

  4. (Optional) Run ip address ip-address { mask | mask-length }

    The IP address of an allowed peer for IKE negotiation is configured.

    By default, no IP address of allowed peer for IKE negotiation is configured.

  5. (Optional) Run fqdn fqdn-name

    The name of an allowed peer for IKE negotiation is configured.

    By default, no name of allowed peer for IKE negotiation is configured.

  6. (Optional) Run user-fqdn fqdn-name

    The domain name of an allowed peer for IKE negotiation is configured.

    By default, no domain name of allowed peer for IKE negotiation is configured.

Follow-up Procedure

Run the match ike-identity identity-name command in the ipsec policy template view or IPSec profile view to reference the identity filter set.

Download
Updated: 2019-04-12

Document ID: EDOC1100041799

Views: 31368

Downloads: 43

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