H3C实现IPSec over GRE典型配置
IPSec over GRE 指使用GRE对使用IPSec封装的数据包进行封装,IPSec over GRE在隧道接口上实现IPSec加密。系统检测隧道接口上需要加密的数据流(配置一个ACL来匹配两个用户网段之间的数据流)。匹配ACL的任何数据包都会被封装成IPSec数据包,然后在通过隧道传输之前封装成GRE数据包。与ACL不匹配的数据包会直接在GRE隧道中传输,而不会使用IPSec进行封装,这意味着这些数据包的传输方式并不安全。这里的外层GRE头也不在这层IPsec的保护范围内。
你可以认为这里的IPsec保护范围由ACL决定,没被匹配到的流量不会被加密。GRE本身没有像IKE那样的安全协商握手,所以不能把它说成“GRE建链过程没有加密”;如果隧道中的OSPF报文没有被ACL匹配,也不会受到这条IPsec策略的保护。
0. 实验环境
Router A和Router B之间建立GRE隧道,Router A和Router B下的PC网段间流量走GRE,并用 IPsec 保护经过 GRE 隧道的指定流量,Router C 模拟 ISP 侧设备。
模拟器:H3C官方模拟器HCL,即H3C Cloud Lab
设备:H3C MSR36-20 Version 7.1.075, Alpha 7571
拓扑图:

1. 基础配置
A和B之间使用静态路由使出口路由可达,并且先起个OSPF进程,使用环回口作为Router-id,因为最后它们要在tunnel上实现OSPF的互联。
Router A:
#
ospf 1 router-id 100.1.1.1
area 0.0.0.0
#
interface LoopBack0
ip address 100.1.1.1 255.255.255.0
ospf 1 area 0.0.0.0
#
interface GigabitEthernet0/0
port link-mode route
ip address 10.1.1.2 255.255.255.0
#
interface GigabitEthernet0/1
port link-mode route
ip address 192.168.1.1 255.255.255.0
ospf 1 area 0.0.0.0
#
ip route-static 0.0.0.0 0 10.1.1.1
#
Router C:
#
interface GigabitEthernet0/0
port link-mode route
ip address 10.1.1.1 255.255.255.0
#
interface GigabitEthernet0/1
port link-mode route
ip address 20.1.1.1 255.255.255.0
#
Router B:
#
ospf 1 router-id 200.1.1.1
area 0.0.0.0
#
interface LoopBack0
ip address 200.1.1.1 255.255.255.0
ospf 1 area 0.0.0.0
#
interface GigabitEthernet0/0
port link-mode route
ip address 20.1.1.2 255.255.255.0
#
interface GigabitEthernet0/1
port link-mode route
ip address 192.168.2.1 255.255.255.0
ospf 1 area 0.0.0.0
#
ip route-static 0.0.0.0 0 20.1.1.1
#
2. GRE tunnel 配置
模拟器默认设备系统版本都是V7,需要在创建Tunnel的时候就指定为GRE隧道。Tunnel要将源设定为自己的出口IP,目的是对端的设备的出口IP,以A为视角的话,Tunnel source 就是它的出口IP,destination是B的出口IP,反过来也是这样。顺便将OSPF网络设定成P2P模式,方便快速建立邻居。
Router A:
interface Tunnel0 mode gre
ip address 172.16.1.1 255.255.255.0
ospf network-type p2p
ospf 1 area 0.0.0.0
source 10.1.1.2
destination 20.1.1.2
Router B:
interface Tunnel0 mode gre
ip address 172.16.1.2 255.255.255.0
ospf network-type p2p
ospf 1 area 0.0.0.0
source 20.1.1.2
destination 10.1.1.2
3. IPSec 配置
两台设备都需要创建ACL抓取需要加密的流量,不然不会触发IPSec加密行为。同时需要注意transform-set的加密和认证参数需要一致, V7设备预共享密钥的配置需要在ike keychain中配置,不同于V5设备。复制配置时仍要逐项核对本端与对端地址、ACL方向、算法和预共享密钥。
下面的3DES、MD5和示例密钥 123 保留为旧实验记录,不作为新部署的配置建议;生产使用要按当前设备支持及安全要求选择算法和密钥。
Router A:
acl advanced 3000
rule 0 permit ip source 192.168.1.0 0.0.0.255 destination 192.168.2.0 0.0.0.255
rule 5 permit ip source 192.168.2.0 0.0.0.255 destination 192.168.1.0 0.0.0.255
#
ipsec transform-set 123
esp encryption-algorithm 3des-cbc
esp authentication-algorithm md5
#
ipsec policy 123 1 isakmp
transform-set 123
security acl 3000
remote-address 172.16.1.2
#
ike keychain 1
pre-shared-key address 172.16.1.2 255.255.255.255 key simply 123
Router B:
acl advanced 3000
rule 0 permit ip source 192.168.1.0 0.0.0.255 destination 192.168.2.0 0.0.0.255
rule 5 permit ip source 192.168.2.0 0.0.0.255 destination 192.168.1.0 0.0.0.255
#
ipsec transform-set 123
esp encryption-algorithm 3des-cbc
esp authentication-algorithm md5
#
ipsec policy 123 1 isakmp
transform-set 123
security acl 3000
remote-address 172.16.1.1
#
ike keychain 1
pre-shared-key address 172.16.1.1 255.255.255.255 key simply 123
4. 启用IPSec
最后,我们只要在tunnel口下把在第三步创建的IPSec policy 调用出来就可以了。
Router A/B:
interface Tunnel0 mode gre
ipsec apply policy 123
5. 验证结果
我们直接ping下,首次触发IKE/IPsec协商时可能出现超时,但不是第一个包一定会丢。ping通只能说明当时存在可达路径,还要检查IKE/IPsec SA、加解密计数和外部链路抓包,确认指定流量确实受到了保护。

由于Router A和Router B内网的流量已在ACL中定义为需加密保护的流量,因此将触发IPsec进行加密。可以通过如下显示信息看到,IKE协商成功,生成了SA。
<H3C>display ike sa
Connection-ID Remote Flag DOI
------------------------------------------------------------------
1 172.16.1.1 RD IPsec
Flags:
RD--READY RL--REPLACED FD-FADING RK-REKEY
可以通过如下显示信息查看协商生成的IPsec SA。
<H3C>display ipsec sa
-------------------------------
Interface: Tunnel0
-------------------------------
-----------------------------
IPsec policy: 123
Sequence number: 1
Mode: ISAKMP
-----------------------------
Tunnel id: 0
Encapsulation mode: tunnel
Perfect Forward Secrecy:
Inside VPN:
Extended Sequence Numbers enable: N
Traffic Flow Confidentiality enable: N
Path MTU: 1420
Tunnel:
local address: 172.16.1.2
remote address: 172.16.1.1
Flow:
sour addr: 192.168.2.0/255.255.255.0 port: 0 protocol: ip
dest addr: 192.168.1.0/255.255.255.0 port: 0 protocol: ip
[Inbound ESP SAs]
SPI: 1503174692 (0x5998a024)
Connection ID: 30064771075
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843199/3316
Max received sequence-number: 4
Anti-replay check enable: Y
Anti-replay window size: 64
UDP encapsulation used for NAT traversal: N
Status: Active
[Outbound ESP SAs]
SPI: 3411111458 (0xcb516e22)
Connection ID: 30064771074
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843199/3316
Max sent sequence-number: 4
UDP encapsulation used for NAT traversal: N
Status: Active
可以通过如下显示信息查看GRE接口状态。 下面显示keepalive未启用,接口UP不等于对端可达,也不等于IPsec已经保护了业务。
[H3C]display interface tunnel0
Tunnel0
Current state: UP
Line protocol state: UP
Description: Tunnel0 Interface
Bandwidth: 64 kbps
Maximum transmission unit: 1476
Internet address: 172.16.1.2/24 (primary)
Tunnel source 20.1.1.2, destination 10.1.1.2
Tunnel keepalive disabled
Tunnel TTL 255
Tunnel protocol/transport GRE/IP
GRE key disabled
Checksumming of GRE packets disabled
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 18 bytes/sec, 144 bits/sec, 0 packets/sec
Last 300 seconds output rate: 18 bytes/sec, 144 bits/sec, 0 packets/sec
Input: 1711 packets, 122752 bytes, 0 drops
Output: 1699 packets, 120360 bytes, 0 drops
GRE封装后,抓包软件仍能识别出里面的 ICMP 报文:

启用IPsec后,匹配ACL的流量先受IPsec保护,再封装进GRE。外部链路抓包时仍可看到外层GRE,展开后才是里面的ESP;要结合抓包位置和封装层级来看。

6. 改用GRE over IPSec方案
GRE over IPSec技术是使用IPSec对已经被GRE封装的数据包进行封装。GRE over IPSec在物理接口上实现IPSec加密。系统检测需要在物理接口上加密的GRE数据流(配置一个ACL,以匹配两个网关之间的GRE数据流)。只要ACL匹配了两端之间的GRE流量,并且这些流量实际经过应用策略的出口,GRE内承载的业务和控制报文都可以受到IPsec保护。这里说的是保护GRE封装后的报文,不是给GRE增加一个加密建链过程。
GRE over IPsec支持隧道和传输模式。隧道模式会增加新的外层IP头,传输模式在适用条件下可以减少这部分开销,但并不能保证不分片。还要按封装后的实际长度检查路径MTU、DF和PMTUD,必要时调整隧道MTU或TCP MSS。本文保留的SA输出显示 Encapsulation mode: tunnel,不能据此当作已经验证了transport模式。
也就是说,需要把IPsec对端改成两端物理出口地址,在物理出口调用策略,并重新核对ACL。下面是修改后的关键配置片段,不是可以直接覆盖原配置的完整脚本:切换时还要移除Tunnel0上的旧策略引用,清理ACL里的旧用户网段规则,并确认SA按新参数重新建立。示例ACL使用 permit ip 匹配两端物理地址,范围比只匹配GRE更宽;如果只想保护GRE,应按所用版本的语法限制协议。
6.1. 配置修改
Router A:
acl advanced 3000
rule 0 permit ip source 10.1.1.2 32 destination 20.1.1.2 32
#
ipsec transform-set 123
esp encryption-algorithm 3des-cbc
esp authentication-algorithm md5
#
ipsec policy 123 1 isakmp
transform-set 123
security acl 3000
remote-address 20.1.1.2
#
ike keychain 1
pre-shared-key address 20.1.1.2 255.255.255.255 key simply 123
#
interface GigabitEthernet0/0
ipsec apply policy 123
Router B:
acl advanced 3000
rule 0 permit ip source 20.1.1.2 32 destination 10.1.1.2 32
#
ipsec transform-set 123
esp encryption-algorithm 3des-cbc
esp authentication-algorithm md5
#
ipsec policy 123 1 isakmp
transform-set 123
security acl 3000
remote-address 10.1.1.2
#
ike keychain 1
pre-shared-key address 10.1.1.2 255.255.255.255 key simply 123
#
interface GigabitEthernet0/0
ipsec apply policy 123
6.2 验证结果
下面保留当时的验证输出。上面的Router B对端地址已按拓扑修正,但没有据此重新跑一次实验,复现时仍需重新核对两端SA、流量计数与抓包结果。
[H3C]dis ike sa
Connection-ID Remote Flag DOI
------------------------------------------------------------------
10 20.1.1.2 RD IPsec
Flags:
RD--READY RL--REPLACED FD-FADING RK-REKEY
[H3C]dis ipsec sa
-------------------------------
Interface: GigabitEthernet0/0
-------------------------------
-----------------------------
IPsec policy: 123
Sequence number: 1
Mode: ISAKMP
-----------------------------
Tunnel id: 0
Encapsulation mode: tunnel
Perfect Forward Secrecy:
Inside VPN:
Extended Sequence Numbers enable: N
Traffic Flow Confidentiality enable: N
Path MTU: 1444
Tunnel:
local address: 10.1.1.2
remote address: 20.1.1.2
Flow:
sour addr: 10.1.1.2/255.255.255.255 port: 0 protocol: ip
dest addr: 20.1.1.2/255.255.255.255 port: 0 protocol: ip
[Inbound ESP SAs]
SPI: 3221028236 (0xbffcfd8c)
Connection ID: 98784247808
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843199/3419
Max received sequence-number: 9
Anti-replay check enable: Y
Anti-replay window size: 64
UDP encapsulation used for NAT traversal: N
Status: Active
[Outbound ESP SAs]
SPI: 3175456113 (0xbd459d71)
Connection ID: 193273528321
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843198/3419
Max sent sequence-number: 10
UDP encapsulation used for NAT traversal: N
Status: Active
-----------------------------
IPsec policy: 123
Sequence number: 1
Mode: ISAKMP
-----------------------------
Tunnel id: 0
Encapsulation mode: tunnel
Perfect Forward Secrecy:
Inside VPN:
Extended Sequence Numbers enable: N
Traffic Flow Confidentiality enable: N
Path MTU: 1444
Tunnel:
local address: 10.1.1.2
remote address: 20.1.1.2
Flow:
sour addr: 10.1.1.2/255.255.255.255 port: 0 protocol: ip
dest addr: 20.1.1.2/255.255.255.255 port: 0 protocol: ip
[Inbound ESP SAs]
SPI: 2902764455 (0xad04aba7)
Connection ID: 12884901891
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843197/3469
Max received sequence-number: 28
Anti-replay check enable: Y
Anti-replay window size: 64
UDP encapsulation used for NAT traversal: N
Status: Active
[Outbound ESP SAs]
SPI: 2962522711 (0xb0948257)
Connection ID: 12884901890
Transform set: ESP-ENCRYPT-3DES-CBC ESP-AUTH-MD5
SA duration (kilobytes/sec): 1843200/3600
SA remaining duration (kilobytes/sec): 1843196/3469
Max sent sequence-number: 30
UDP encapsulation used for NAT traversal: N
Status: Active
改用 GRE over IPsec 后,抓包能看到外层源 IP、目的 IP 和 ESP,受保护的内层内容无法直接解读。
