Actions
Bug #11193
closed
IPsec KeyID Not Working on Development Snapshots
Start date:
12/29/2020
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:
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.
Updated by Jim Pingle over 3 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 131b41fcc1f16037c752b26c6a1036c2d1c5c2de.
Updated by Alhusein Zawi over 3 years 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 => ESTABLISHED2.5.0.a.20201230.0250
Actions