<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi colleagues,</p>
<p>according to
<a class="moz-txt-link-freetext" href="https://wiki.strongswan.org/projects/strongswan/wiki/IdentityParsing">https://wiki.strongswan.org/projects/strongswan/wiki/IdentityParsing</a>
:</p>
<p>"If the string begins with @# the type is set to KEY_ID and the
string following that prefix is assumed to be the hex-encoded
binary value of the identity."</p>
<p>It seems, I understand incorrectly the statement above, because
configuration for the key-id 'aa' (where @#6161 stands for HEX
codes of twin 'a') -<br>
</p>
<pre>ikev2-psk {
[ ... ]
remote {
auth = psk
id = @#6161
}
</pre>
<p> do not work - StrongSwan do not consider this connection when
choosing between few.</p>
<p>What is the right way to describe id for PSK connection where
remote part uses key-id type, e.g. on Cisco it is "crypto isakmp
identity key-id aa"?</p>
<p>And which id need to be used in 'secrets' section to achieve the
result? Should it be</p>
<pre>ike-cisco1 {
id = aa
secret = qwerty
}
</pre>
<p>or</p>
<pre>ike-cisco1 {
id = @#6161
secret = qwerty
}
</pre>
<p>or something else done on the right way?<br>
</p>
<p>Thank you!</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison</pre>
</body>
</html>