This rather straight forward. But is it used? Useful? Does StrongSWAN support it?
AUTH exchange has [CP] , TSi, TSr. When a receiver get these it reply with EAP and goes off to EAP authentican. However, it must hang on to [CP], TSi, TSr. And after the authentication respond to it. After EAP is complete the initiator does not send TSi and TSr again.
Configuration names: In general there may be conflicts in functionality between IKEv1 and IKEv2.
The username is called xauthusername in IKEv1. Is it appropriate to call that in v2?
May be a solution is first create a v2 only connection and then use new names.
WPA Supplicant source code has ikev2 has eap_server_ikev2.c what is that?
It seems CP Attribute types, RFC5996 3.15.1, is missing DOMAIN name. However, CISCO prviate extensions has them.
This page was last modified on 31 January 2018, at 17:00.