<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000066" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hallo Martin, thank you very much for
this!<br>
<br>
</div>
<blockquote cite="mid:1382951406.3017.19.camel@martin" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Selecting test-oti.dom.ch failed due to strongswan always using peer
'dev' (the first one) and the eap_identity missmatching. Looks like
the peer config is selected before the eap-tls comes into play. Am I
missing something here?
</pre>
</blockquote>
<pre wrap="">
Yes, the peer config is selected before EAP-TLS starts, as the daemon
has to know, among other things, what EAP method to initiate.
However, strongSwan knows a concept of "late configuration switching";
it allows to switch to a different (compatible) connection after
authentication when it sees that the current selection is unacceptable.</pre>
</blockquote>
Where can I find "late configuration switching" or the concept of it
in the documentation?<br>
<br>
Regards<br>
Hans<br>
<pre class="moz-signature" cols="72">--
Hans Riethmann
ortecin GmbH
Waffenplatzstrasse 40, 8002 Zuerich
mobile: +41 79 689 1052, phone: +41 44 280 2828
</pre>
</body>
</html>