• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

★ Typical configuration example of MSR V7 non-fixed address combined with DDNS to establish IPsec tunnel

2020-04-14 Published
  • 0关注
  • 0收藏 1425浏览
粉丝:3人 关注:1人

Network Topology

[Network Topology & Requirements]

Both the headquarters and branch equipment are MSR3620, and both use PPPoE to dynamically obtain addresses. It is necessary to use DDNS technology to establish an IPSec VPN between the branch and headquarters equipment.

 

Configuration Steps

1. Headquarters configuration

 

#

  dialer-group 1 rule ip permit

#

  dns server 114.114.114.114 // DNS server configuration, required

#

ddns policy GigabitEthernet0 / 0 // DDNS configuration

  url oray: //***.***

  username xxx

  password cipher $c$3$FfX6Z0QOVZmxJNi9wBg3TXqVJo2BwHGRgJvieDwFAEM=

  interval 0 0 1

#

interface Dialer0

  ppp pap local-user xxx password cipher $c$3$7Gw/H5un4WfVczBy9PhVSnwUhwtzt0y5IS0M

  dialer bundle enable

  dialer-group 1

  ip address ppp-negotiate

  nat outbound 3200

  ddns apply policy GigabitEthernet0 / 0 fqdn ***.*** // interface application DDNS

  ipsec apply policy 123 // Bind the IPsec policy to the Dialer interface

#

interface GigabitEthernet0 / 0

  pppoe-client dial-bundle-number 0

#

  ip route-static 0.0.0.0 0 Dialer0 // Configure the default route

#

acl advanced 3200 // NAT ACL

  rule 5 deny ip source 192.168.16.0 0.0.15.255 destination 192.168.0.0 0.0.15.255 // reject IPsec data flow

  rule 1000 permit ip

#

ipsec transform-set 123 // Configure IPsec security proposal

  esp encryption-algorithm 3des-cbc

  esp authentication-algorithm sha1

#

ipsec policy-template 123 65535 // Configure IPsec policy template

  transform-set 123

  ike-profile 123

#

ipsec policy 123 65535 isakmp template 123 // Apply the template to the policy

#

ike profile 123 // Configure IKE Profile

  keychain 123

  exchange-mode aggressive

  match remote identity fqdn 123

  proposal 65535

#

ike proposal 65535 // Configure IKE proposal

  encryption-algorithm 3des-cbc

  authentication-algorithm md5

#

ike keychain 123 // Configure IPsec pre-shared key

  pre-shared-key hostname 123 key cipher $c$3$kR2YXCsG8am/6KexFkGTgg2Y+dRksRw3wA==

 

 

2. Branch configuration

 

#

  dialer-group 1 rule ip permit

#

  dns server 114.114.114.114 // DNS server configuration, required

#

interface Dialer0

  ppp pap local-user xxx password cipher $c$3$JkPr7vTBqgi+CcN3SEgqs6iP5Ytiag8NKTB

  dialer bundle enable

  dialer-group 1

  ip address ppp-negotiate

  nat outbound 3100

  ipsec apply policy 123 // Bind the IPsec policy to the Dialer interface

#

interface GigabitEthernet0 / 0

  pppoe-client dial-bundle-number 0

#

  ip route-static 0.0.0.0 0 Dialer0 // Configure the default route

#

acl advanced 3000 // IPsec ACL

  rule 5 permit ip source 192.168.0.0 0.0.15.255 destination 192.168.16.0 0.0.15.255

#

acl advanced 3100 // NAT ACL

  rule 5 deny ip source 192.168.0.0 0.0.15.255 destination 192.168.16.0 0.0.15.255 // reject IPsec data flow

  rule 1000 permit ip

#

ipsec transform-set 123 // Configure IPsec security proposal

  esp encryption-algorithm 3des-cbc

  esp authentication-algorithm sha1

#

ipsec policy 123 65535 isakmp // Configure IPsec policy

  transform-set 123

  security acl 3000

  remote-address ***.*** // The peer address is designated as the DDNS address

  ike-profile 123

#

  ike identity fqdn 123 // Configure IKE FQDN

#

ike profile 123 // Configure IKE Profile

  keychain 123

  exchange-mode aggressive

  match remote identity address 0.0.0.0 0.0.0.0 // Because the remote address is not fixed, match all addresses

  proposal 65535

#

ike proposal 65535 // Configure IKE proposal

  encryption-algorithm 3des-cbc

  authentication-algorithm md5

#

ike keychain 123  // Configure the IPsec pre-shared key. Note that the pre-shared-key address here must include the remote-address in the IPsec security policy, otherwise it will prompt that the pre-share-key cannot be found.

  pre-shared-key address 0.0.0.0 0.0.0.0 key cipher $c$3$bPT/nV7B9eYpBabcqorgjs8502r8yPqTCg ==


Key Configuration

1. Note that the pre-shared-key address on the non-template side must contain the remote-address in the IPsec security policy, and cannot be the FQDN of the peer, otherwise it will prompt that the pre-share-key cannot be found, and the error is as follows:

 

* Aug 18 19: 47: 54: 397 2018 xxx IKE / 7 / EVENT: vrf = 0, local = x.x.x.x, remote = x.x.x.x / 500 Pre-shared key matching address x.x.x.x not found

 

2. Note that both routers need to be configured with DNS.

 

3. Note that the IPsec policy is applied to the Dialer port, not the physical port.


该案例对您是否有帮助:

您的评价:1

若您有关于案例的建议,请反馈:

0 comments

No comments

Add Comments:

举报

×

侵犯我的权益 >
对根叔知了社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔知了社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明

提出建议

    +

亲~登录后才可以操作哦!

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作