[strongSwan] Combining authentication types

[Noel Kuntze]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello Fred,

Yes and afaik, there is no diagram describing the points at which
charon checks for the correct conn section to choose.

Mit freundlichen Grüßen/Kind Regards,
Noel Kuntze

GPG Key ID: 0x63EC6658
Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658

Am 26.06.2015 um 15:07 schrieb Fred:
> On 26/06/2015 13:51, Noel Kuntze wrote:
>> Use eap-dynamic[1][2] then.
>>
>> [1] https://wiki.strongswan.org/projects/strongswan/wiki/Eap-dynamic
>> [2] https://www.strongswan.org/uml/testresults/ikev2/rw-eap-dynamic/index.html
>
> Thanks Noel.
>
> Am I right in thinking this is only required when the differing property is only the EAP method?
>
> And would this have worked fine in a different scenario where all the connections didn't use EAP.. but had some other distinguishing property? For e.g. if only coming from a specific IP or something? Is there a diagram or otherwise that explains the logic that StrongSwan follows in trying to select the correct conn section to use? and what connection settings can be used as selectors?
>
> Fred
> _______________________________________________
> Users mailing list
> Users at lists.strongswan.org
> https://lists.strongswan.org/mailman/listinfo/users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVjVGvAAoJEDg5KY9j7GZYpDUP/3bzYP0QsrVxVIhHf2B/m/8S
OcMmoV4FQmj2ky99dUeNGKQze/fw/CARpEq/Ff+h3tkkEq91opmIJ1uhJhDG7OVH
iDmaG7S+Bgx/GLXIMHuZ4Q5R6XBSxcq26FI1pdMZl3kxQJVOlBynYnZayasK/xeO
EHbuZzekYxtG0z2CdgXSZVqQkHIVl/tCsKEk+Sd1ml956hZcTQkyJsWuNDS/jqPO
QdZk2SJH7AQ5rWhH8a6UumRK2U6pkbBVTpe+ATsVu8/nlHoFu0F+yQV5gl4GxtbK
CQ17TqlJAWApnaWvcYb4nw1HurC03y3DR3JqtXB9tB3lIyfW1AdqVzH5BBvpYT8o
ngJnwxCNEfZodeC9ISVO7kKEBUHC33xwx+bWkF34QloTxLY13X7kdy0xfZltvC34
9tPWeun3hDS0hjAbBBboJzSXsL/tk0H9qEPiM/Z/KCebIUxHUjwF9Qv7b1ZAt+wo
sIgsnp19E6zakAkWq1KI87Q3NXDqgj0mVdOzdLZnQHcSc7kAifrOGEEUVmELkcuG
DS8b8hquCENbjxClEV8g+MiFCEEyd+PW9y6zpCmKZCuLSjfKfwb1u5nFPaZ5Z1Fm
pcIgIhxLydDwr7UIG/SMR+0Ay68c8C4PF3U005ZLRFIp/47dB1a5x3vyBTqMAlWq
tK4963m9MpJjKXDdTVuI
=jrFk
-----END PGP SIGNATURE-----