On Oct 3, 2019, at 5:45 AM, Alberto Martínez Setién <alberto.martinez@deusto.es> wrote:
I thought that default_eap_type worked that way
No, it works the way it's documented to work. The default_eap_type is what the server *suggests* that the client use. If you read the debug output, you would see that the client sends a NAK to that request, and instead asks for a different EAP type. But even then, default_eap_type applies to *EAP*. It doesn't apply to PAP or MSCHAPv2.
Does iOS prefer doing TTLS + MS-CHAPv2 over TTLS-PAP?
Generally, yes. Why? Ask Apple. We didn't write iOS.
There is no way of letting it know the preferred method without the use of a WiFi profile?
Generally, no. Why? Ask Apple. We didn't write iOS.
I believe that this is an answer to my question before. But is it really so? Does the iPad always do TTLS+MSCHAPv2 when trying to connect to an unconfigured 802.1x network?
Why are you asking us that question? We didn't write iOS. Alan DeKok.