我的路由器与AWS上ipsec的配置信息均正确,加密方式也都相同。但是始终无法连接。
2017-11-28 13:55:18 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1). 2017-11-28 13:55:20 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送PAYLOAD_MALFORMED通告信息到54.223.27.201:4500. 2017-11-28 13:55:32 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 收到54.223.27.201的ISAKMP主模式协商请求. 2017-11-28 13:55:32 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:55:42 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:55:50 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送PAYLOAD_MALFORMED通告信息到54.223.27.201:4500. 2017-11-28 13:55:50 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 收到54.223.27.201的ISAKMP主模式协商请求. 2017-11-28 13:55:50 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:56:00 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:56:20 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:56:28 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1). 2017-11-28 13:57:00 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 收到54.223.27.201的ISAKMP主模式协商请求. 2017-11-28 13:57:00 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:57:10 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:57:30 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:57:38 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1). 2017-11-28 13:57:56 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1). 2017-11-28 13:58:10 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 收到54.223.27.201的ISAKMP主模式协商请求. 2017-11-28 13:58:10 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:58:20 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:58:40 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:59:06 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1). 2017-11-28 13:59:20 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 收到54.223.27.201的ISAKMP主模式协商请求. 2017-11-28 13:59:20 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:59:22 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 采用主模式发起ISAKMP协商. 2017-11-28 13:59:22 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:59:30 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:59:50 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送已加密的INVALID_ID_INFORMATION通告信息到54.223.27.201:4500. 2017-11-28 13:59:51 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: 发送PAYLOAD_MALFORMED通告信息到54.223.27.201:4500. 2017-11-28 14:00:16 [debug] : 113.108.164.126<->54.223.27.201[BAIJI-AWS]: ISAKMP 协商超时(1).
(0)
最佳答案
本端是野蛮模式,AWS是主模式吧,我看本段发出发的报文封装的是4500端口,应该是前两个报文已经过去了,然后AWS就没有回复了,协商超时,然后又收到AWS发过来的主模式协商请求,应该还是配置问题。
(0)
路由器报INVALID_ID_INFORMATION错误,说明两端的id类型不匹配,看端口号为4500,是过了nat设备的,建议两端都采用野蛮模式,id类型选择name类型应该就可以建立了
(0)
暂无评论
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论