Bug #11193: IPsec KeyID Not Working on Development Snapshots - pfSense - pfSense bugtracker

Actions

Copy link

Bug #11193

closed

IPsec KeyID Not Working on Development Snapshots

Added by Jim Pingle almost 4 years ago. Updated almost 4 years ago.

Status:

Resolved

Priority:

High

Assignee:

Jim Pingle

Category:

IPsec

Target version:

2.5.0

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.

Actions

Copy link

Updated by Jim Pingle almost 4 years ago

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

Applied in changeset 131b41fcc1f16037c752b26c6a1036c2d1c5c2de.

Actions

Copy link

Updated by Alhusein Zawi almost 4 years ago

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

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

2.5.0.a.20201230.0250

Actions

Copy link