You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checked the issue tracker for similar issues to ensure this is not a duplicate.
Provided a clear description of your suggestion.
Included any relevant context or examples.
Issue or Suggestion Description
Hello Devs,
We are currently using this setup
STM32mp133
esp32c3
interface: SPI
mode: SoftAp
type: esp-hosted-ng
Linux HostAP startup tool: Hostapd
Master commit used on both side: 250e292
Description:
We have compiled the driver, we can see it via ifconfig, even station mode (connecting from esp32 to a hotspot) works fine.
Then we wanted to confirm that connecting from any device to esp softAP and we noticed it did not work. We were also seeinig errors on esp32 monitor side on logs.
This seems like security config mismatch, meaning the laptop asking some security protocol, which is not supported, and resulting in disconnection and return of WIFI_REASON_UNSUPP_RSN_IE_VERSION as not connected. But I think @kapilkedawat can confirm it.
I appreciate your patience on this case. We will confirm if it is a bug or actual expected behaviour.
Checklist
Issue or Suggestion Description
Hello Devs,
We are currently using this setup
STM32mp133
esp32c3
interface: SPI
mode: SoftAp
type: esp-hosted-ng
Linux HostAP startup tool: Hostapd
Master commit used on both side: 250e292
Description:
We have compiled the driver, we can see it via ifconfig, even station mode (connecting from esp32 to a hotspot) works fine.
Then we wanted to confirm that connecting from any device to esp softAP and we noticed it did not work. We were also seeinig errors on esp32 monitor side on logs.
Logs:
(look for the line E (238925) FW_MAIN: Sending data failed=12309 which come only connecting via Laptop)
error screenshot:
Can you tell us what is missing and what can be different via Laptop?
Thank you very much in advance.
The text was updated successfully, but these errors were encountered: