Hallo Martin, thank you very much for this!


      
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?
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.
Where can I find "late configuration switching" or the concept of it in the documentation?

Regards
Hans
-- 
Hans Riethmann

ortecin GmbH
Waffenplatzstrasse 40, 8002 Zuerich

mobile: +41 79 689 1052, phone:  +41 44 280 2828

<<attachment: hans_riethmann.vcf>>

_______________________________________________
Users mailing list
[email protected]
https://lists.strongswan.org/mailman/listinfo/users

Reply via email to