Project

General

Profile

Bug #11193

IPsec KeyID Not Working on Development Snapshots

Added by Jim Pingle 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
IPsec
Target version:
Start date:
12/29/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.5.0
Affected Architecture:
Release Notes:
Default

Description

Configuring a tunnel with an ID type of KeyID fails to connect. In the secrets section of swanctl.conf, the ID is not specified with the type, which appears to be a problem similar to #9243. That affected the local/remote section, and it's OK there now, but the type is missing still in the secrets.

To me, I have a patch that corrects the problem.

Associated revisions

Revision 131b41fc (diff)
Added by Jim Pingle 3 months ago

Correct IPsec secrets section ID type handling. Fixes #11193

History

#1 Updated by Jim Pingle 3 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Alhusein Zawi 3 months ago

Working as expected , "KeyID tag" as My identifier/ Peer identifier

<12> looking for peer configs matching 172.17.99.33[id33test]...172.17.99.22[id22test]
<12> candidate "con100000", match: 20/20/3100 (me/other/ike)
<con100000|12> selected peer config 'con100000'
<con100000|12> authentication of 'id22test' with pre-shared key successful
<con100000|12> authentication of 'id33test' (myself) with pre-shared key
<con100000|12> successfully created shared key MAC
<con100000|12> IKE_SA con100000[12] established between 172.17.99.33[id33test]...172.17.99.22[id22test]
<con100000|12> IKE_SA con100000[12] state change: CONNECTING => ESTABLISHED

2.5.0.a.20201230.0250

#3 Updated by Jim Pingle 3 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF