拓扑如上,现在是FW3旁挂SW4上和FW2做IPSEC,麻烦各位大佬帮忙看下为啥协商不起来,设备的配置我放在附件了。
(0)
最佳答案
补充一点FW3的debug信息如下:<FW3>*Jul 15 10:20:04:061 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Can't find block-flow node.
*Jul 15 10:20:04:062 2024 FW3 IPSEC/7/PACKET: -COntext=1;
Failed to find SA by SP, SP Index = 0, SP Convert-Seq = 65536.
*Jul 15 10:20:04:062 2024 FW3 IPSEC/7/ERROR: -COntext=1;
The reason of dropping packet is no available IPsec tunnel.
*Jul 15 10:20:04:062 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent SA-Acquire message : SP ID = 0
*Jul 15 10:20:04:062 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Received negotiate SA message from IPsec kernel.
*Jul 15 10:20:04:062 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Got SA time-based soft lifetime settings when filling Sp data.
Configured soft lifetime buffer : 0 seconds.
Configured global soft lifetime buffer : 0 seconds.
*Jul 15 10:20:04:072 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent delete SA message to Slot:1 Cpu:0, message type is 0x16.
*Jul 15 10:20:04:072 2024 FW3 IPSEC/7/EVENT: -COntext=1;
The SA doesn't exist in kernel.
*Jul 15 10:20:04:072 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Switch remote address no change, SP index is 0.
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Can't find block-flow node.
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/PACKET: -COntext=1;
Failed to find SA by SP, SP Index = 0, SP Convert-Seq = 65536.
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/ERROR: -COntext=1;
The reason of dropping packet is no available IPsec tunnel.
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent SA-Acquire message : SP ID = 0
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Received negotiate SA message from IPsec kernel.
*Jul 15 10:20:06:264 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Got SA time-based soft lifetime settings when filling Sp data.
Configured soft lifetime buffer : 0 seconds.
Configured global soft lifetime buffer : 0 seconds.
*Jul 15 10:20:06:265 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent delete SA message to Slot:1 Cpu:0, message type is 0x16.
*Jul 15 10:20:06:265 2024 FW3 IPSEC/7/EVENT: -COntext=1;
The SA doesn't exist in kernel.
*Jul 15 10:20:06:265 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Switch remote address no change, SP index is 0.
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Can't find block-flow node.
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/PACKET: -COntext=1;
Failed to find SA by SP, SP Index = 0, SP Convert-Seq = 65536.
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/ERROR: -COntext=1;
The reason of dropping packet is no available IPsec tunnel.
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent SA-Acquire message : SP ID = 0
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Received negotiate SA message from IPsec kernel.
*Jul 15 10:20:08:466 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Got SA time-based soft lifetime settings when filling Sp data.
Configured soft lifetime buffer : 0 seconds.
Configured global soft lifetime buffer : 0 seconds.
*Jul 15 10:20:08:467 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent delete SA message to Slot:1 Cpu:0, message type is 0x16.
*Jul 15 10:20:08:467 2024 FW3 IPSEC/7/EVENT: -COntext=1;
The SA doesn't exist in kernel.
*Jul 15 10:20:08:467 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Switch remote address no change, SP index is 0.
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Can't find block-flow node.
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/PACKET: -COntext=1;
Failed to find SA by SP, SP Index = 0, SP Convert-Seq = 65536.
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/ERROR: -COntext=1;
The reason of dropping packet is no available IPsec tunnel.
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent SA-Acquire message : SP ID = 0
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Received negotiate SA message from IPsec kernel.
*Jul 15 10:20:10:668 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Got SA time-based soft lifetime settings when filling Sp data.
Configured soft lifetime buffer : 0 seconds.
Configured global soft lifetime buffer : 0 seconds.
*Jul 15 10:20:10:669 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Sent delete SA message to Slot:1 Cpu:0, message type is 0x16.
*Jul 15 10:20:10:670 2024 FW3 IPSEC/7/EVENT: -COntext=1;
The SA doesn't exist in kernel.
*Jul 15 10:20:10:670 2024 FW3 IPSEC/7/EVENT: -COntext=1;
Switch remote address no change, SP index is 0.
undo t d
The current terminal is disabled to display debugging logs.
(0)
您好,以下是排查要点,请参考:
1、检查到分支的路由是否可达。
2、检查到分支的IPSEC VPN模式是否一致。
3、检查到分支的IPSEC VPN加密算法、认证算法、认证密钥是否正确。
4、检查与分支的IPSEC VPN的相互指向是否准确。
5、进一步检查下感兴趣数据流的源和目的是否已覆盖到位。
(0)
路由可达,模式都是野蛮模式,加密算法,认证算法,密钥都一致,由于是带NAT场景,FW2用的是安全策略模板,我也不知道应不应该这么配,能不能帮忙看下,非常感谢
路由可达,模式都是野蛮模式,加密算法,认证算法,密钥都一致,由于是带NAT场景,FW2用的是安全策略模板,我也不知道应不应该这么配,能不能帮忙看下,非常感谢
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明