Support for EAP client API

[david-cermak]

• Parse supplicant related headers and generate
  • remote eap-client headers
  • impl translating eap-client APIs -> remote APIs
  • __weak impl of the remote APIs
• some support scripts
• tests

Closes #19

[kapilkedawat]

do we need this config? Also this needs to be dependent of ESP_WIFI_ENTERPRISE_SUPPORT(compilation will still pass due to weak links but functionality wise we should make it dependent.)

[david-cermak]

Also this needs to be dependent of ESP_WIFI_ENTERPRISE_SUPPORT

Added dependency to WIFI_RMT_ENTERPRISE_SUPPORT (the same slave related option)

do we need this config?

I'd prefer that we keep this option, since it bring PUBLIC dependency to wpa_supplicant (which we might like to avoid for most cases IMO)

[kapilkedawat]

@Shreyas0-7 could you try eap changes with this MR?

[david-cermak]

@kapilkedawat Thanks for the quick review! I've added a CI check to build the enterprise example for P4, H2 and S3.
(CI passed previously on 03dc813, now I only cleaned-up the history)

@Shreyas0-7 could you try eap changes with this MR?

Note: this is just API addition, so you'd probably see an abort() after the

ESP_ERROR_CHECK(esp_eap_client_set_identity(...));

as the weak implementation would be pulled

[Shreyas0-7]

Hey @david-cermak, thank you, will check

[kapilkedawat]

@david-cermak The changes looks generally good to me..

However some points regarding both esp-remote and esp-mcu, do we actually need to add new config options for these components? IMO these configuration should somehow be derived from esp-idf's sdkconfig, so that user have the same experience as using esp-idf native WiFi.

[kapilkedawat]

Also @Shreyas0-7 is currently testing wifi enterprise using this, will update once he is done(we already have a working eap, will just sync changes and see if there is any difference).

[david-cermak]

@kapilkedawat

do we actually need to add new config options for these components?

You mean the WIFI_RMT_... (in wifi-remote component) vs those ESP_WIFI_... from esp_wifi? There are mainly for the coexistence of local and remote Wi-Fi(e.g. if someone wants to use native esp_wifi_connect()on S3 and at the same timeesp_wifi_remote_connect()` on the slave target, like C5)

[kapilkedawat]

Hi @david-cermak , Please help to merge this, we have verified this internally.

[david-cermak]

Please help to merge this, we have verified this internally.

Thanks for testing the changes. Okay, I will merge and publish the updates.

Note that the WIFI_RMT_ENTERPRISE_SUPPORT option is ON by deafult