SoftAP works if connecting via Mobile (Android/iOS) but Laptops(Windows/Linux) did not work. #502

mayurpatel19912009 · 2024-09-30T05:38:31Z

Checklist

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.

Logs:

Linux Host side logs: STM32MP133_log.txt
ESP32C3 side logs: ESP32C3_log.txt
(look for the line E (238925) FW_MAIN: Sending data failed=12309 which come only connecting via Laptop)
Hostapd config:

interface=wlan0
driver=nl80211
ssid=test_ssid
hw_mode=g
channel=1
macaddr_acl=0
auth_algs=1
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_passphrase=test_ssid
rsn_pairwise=CCMP
wpa_pairwise=CCMP
ctrl_interface=/tmp/hostapd

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:

mantriyogesh · 2024-09-30T06:09:41Z

@kapilkedawat ++

mayurpatel19912009 · 2024-09-30T08:16:39Z

@mantriyogesh,

can you tell me at least for now if its a known topic or something wrong from our side?

mantriyogesh · 2024-09-30T08:49:01Z

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.

kapilkedawat · 2024-09-30T09:04:38Z

@Shreyas0-7 please help to check. @mayurpatel19912009 please share hostapd logs as well. Please pass -ddd -K while starting hostapd.

mayurpatel19912009 · 2024-10-01T12:05:27Z

we added that flags in the service and logged it. We dont see many logs. Posting screenshot.

service running with your given flags

esp32c3 logs which i already posted above before.

Shreyas0-7 · 2024-10-01T12:21:29Z

Hey @mayurpatel19912009 is possible for you to capture the sniffer
Here are steps, can you please try this to capture sniffer
If you are using a Windows machine, try: https://www.youtube.com/watch?v=As9BUoOMk_A
If you are using an iOS machine, try: https://youtu.be/hxtgin0hgf8?si=nRvTdL24KiKHOPIs
If you are using a Linux machine do iwconfig, and select interface which you are not using
For example your interface is wlp0s20f3, try:

ifconfig wlp0s20f3 down
iwconfig wlp0s20f3 mode monitor
ifconfig wlp0s20f3 up
iwconfig wlp0s20f3 channel 6
wireshark

Please note that a lot of WiFi cards (NIC) don't support putting them in monitor mode. So it is vital to check the compatibility of your laptop's NIC.
Hope that helps.

mayurpatel19912009 · 2024-10-01T13:49:08Z

Just some que ,

Are you not able to reproduce this issue by yourself?
Connecting via Laptop works fine at your side?

It will make things fast if you can try to connect via Laptop and see the same issue.

Shreyas0-7 · 2024-10-03T07:19:18Z

Yes @mayurpatel19912009 I used the same hostapd configuration provided for test_ssid and was able to connect a linux client to the access point

iradmilo-bytelab · 2024-10-04T14:43:38Z

Hi @Shreyas0-7 ,

could you please state commit and branch you used for host and network adapter?
What hardware setup are you using and what is the communication interface between chips?

I followed these instructions (https://github.com/espressif/esp-hosted/blob/master/esp_hosted_ng/README.md#configuring-ap-with-hostapd)
on the config @mayurpatel19912009 described in the opening question and its still the same behavior as is described there (Mobile connects but not PC).

I am configuring CONFIG_AP_SUPPORT=y for the host, do I have to setup anything additional for the network adapter firmware?

Shreyas0-7 · 2024-10-05T05:51:36Z

Hey @iradmilo-bytelab
Hardware used c3 spi with rpi as host.
I used a4a5f00923b45f11d833a3631768f8f7ad1df868 commit for testing
Enabling CONFIG_AP_SUPPORT=y will enable ap support.
You can also do ./rpi_init.sh spi ap_support.
If you are facing error with connection with a client we need hostapd logs as well sniffer to debug it further more

iradmilo-bytelab · 2024-10-22T06:17:24Z

Hi @Shreyas0-7 ,

I am attaching wireshark capture file of linux PC trying to connect to AP provided by ESP32C3,
Setup is the same as in the original post.

ESP32_C3_AP_mode_PC_linux.pcapng.gz

Shreyas0-7 · 2024-10-22T06:51:53Z

Hey @iradmilo-bytelab I can see only association request in the capture, is it possible for you to turn on the capture first and then try to connect with softap. Also please do attach hostapd logs for the same. you can use -dd with hostapd command to enable logs.

iradmilo-bytelab · 2024-10-22T07:59:53Z

Hi @Shreyas0-7 , do you have a mail address where I can send you these files?

Shreyas0-7 · 2024-10-22T08:40:32Z

Hey @iradmilo-bytelab you can attach your files here

iradmilo-bytelab · 2024-10-22T10:45:30Z

hostapd_start_logs.gz
hostapd_logs.gz
ESPC3_AP.pcapng.gz

Master commit used on both sides is 30f4082

Shreyas0-7 · 2024-10-23T06:15:07Z

Hey @iradmilo-bytelab from the logs and capture we can observe that we are able associate a station and start 4 way handshake. But we are failing in between of 4 way handshake. To debug it further more can you please share dmesg logs as well.

iradmilo-bytelab · 2024-10-23T08:04:35Z

I am attaching dmesg logs form host side and logs from esp32c3 side:

Host_logs.gz
ESP_C3_side_logs.gz

Shreyas0-7 · 2024-10-23T09:42:51Z

Hey @iradmilo-bytelab can you please check you hardware connection between host and esp. Dmesg and esp log shows that connection is not stable.

iradmilo-bytelab · 2024-10-23T10:16:52Z

Hi @Shreyas0-7 ,

Thank you for the analysis.
Can you please point out the messages from the logs that indicate that connection is unstable?

Shreyas0-7 · 2024-10-23T11:40:34Z

Command timeout logs in dmesg suggest that connection might be unstable. Also you can check raw throughput to verify if connection is stable https://github.com/espressif/esp-hosted/blob/master/esp_hosted_ng/docs/Raw_TP_Testing.md.

iradmilo-bytelab · 2024-10-23T11:57:54Z

After checking the tp:

esp_2_host_tp.gz
host_2_esp_tp.gz

Is this expected tp?

Shreyas0-7 · 2024-10-23T12:00:13Z

Hey @iradmilo-bytelab do you have values for esp as well?

iradmilo-bytelab · 2024-10-23T12:27:12Z

Host_2_esp_raw_tp_host_side.gz
Host_2_esp_raw_tp_esp_side.gz
Esp_2_host_raw_tp_host_side.gz
Esp_2_host_raw_tp_esp_side.gz

Shreyas0-7 · 2024-10-24T10:09:27Z

Hey @iradmilo-bytelab thanks for the logs, raw throughput looks okay. I see scan issued on the interface multiple times in the logs, could you please check if there is a wpa_supplicant instance running on the host besides hostapd.

iradmilo-bytelab · 2024-10-24T10:39:52Z

wpa_supplicant and network manager were both killed and not working at the moment of testing.

Shreyas0-7 · 2024-10-25T06:29:28Z

Hey @iradmilo-bytelab can you please check if there are some background script which may be issuing scan? Could you also share a ps -a output when issue is coming.

iradmilo-bytelab · 2024-10-25T12:42:41Z

ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 11:15 ? 00:00:00 /sbin/init
root 2 0 0 11:15 ? 00:00:00 [kthreadd]
root 3 2 0 11:15 ? 00:00:00 [rcu_gp]
root 4 2 0 11:15 ? 00:00:00 [rcu_par_gp]
root 5 2 0 11:15 ? 00:00:00 [slub_flushwq]
root 6 2 0 11:15 ? 00:00:00 [netns]
root 10 2 0 11:15 ? 00:00:00 [mm_percpu_wq]
root 11 2 0 11:15 ? 00:00:00 [rcu_tasks_kthread]
root 12 2 0 11:15 ? 00:00:00 [ksoftirqd/0]
root 13 2 0 11:15 ? 00:00:00 [rcu_preempt]
root 14 2 0 11:15 ? 00:00:00 [kdevtmpfs]
root 15 2 0 11:15 ? 00:00:00 [inet_frag_wq]
root 22 2 0 11:15 ? 00:00:00 [oom_reaper]
root 23 2 0 11:15 ? 00:00:00 [writeback]
root 24 2 0 11:15 ? 00:00:00 [kcompactd0]
root 25 2 0 11:15 ? 00:00:00 [kblockd]
root 26 2 0 11:15 ? 00:00:00 [ata_sff]
root 27 2 0 11:15 ? 00:00:00 [edac-poller]
root 28 2 0 11:15 ? 00:00:00 [devfreq_wq]
root 29 2 0 11:15 ? 00:00:00 [watchdogd]
root 32 2 0 11:15 ? 00:00:00 [rpciod]
root 33 2 0 11:15 ? 00:00:00 [xprtiod]
root 34 2 0 11:15 ? 00:00:00 [kswapd0]
root 36 2 0 11:15 ? 00:00:00 [nfsiod]
root 38 2 0 11:15 ? 00:00:00 [optee_pcpu_noti]
root 39 2 0 11:15 ? 00:00:00 [hwrng]
root 40 2 0 11:15 ? 00:00:00 [mld]
root 41 2 0 11:15 ? 00:00:00 [ipv6_addrconf]
root 58 2 0 11:15 ? 00:00:00 [irq/43-5c004000.rtc]
root 59 2 0 11:15 ? 00:00:00 [irq/44-mmci-pl18x (cmd)]
root 61 2 0 11:15 ? 00:00:00 [mmc_complete]
root 63 2 0 11:15 ? 00:00:00 [jbd2/mmcblk1p8-8]
root 64 2 0 11:15 ? 00:00:00 [ext4-rsv-conver]
root 95 1 0 11:15 ? 00:00:00 /sbin/udevd -d
root 105 2 0 11:15 ? 00:00:00 [irq/47-4c002000.spi]
root 106 2 0 11:15 ? 00:00:00 [spi0]
root 110 2 0 11:15 ? 00:00:00 [kworker/0:3H-kblockd]
root 144 2 0 11:15 ? 00:00:00 [cfg80211]
root 148 2 0 11:15 ? 00:00:00 [ESP_SPI_WORK_QU]
message+ 223 1 0 11:15 ? 00:00:14 /usr/bin/dbus-daemon --system
root 233 1 0 11:15 ? 00:00:00 sshd: /usr/sbin/sshd [listener] 0 of 10-100 startups
root 237 1 0 11:15 ? 00:00:00 /usr/libexec/bluetooth/bluetoothd
root 244 2 0 11:15 ? 00:00:00 [ESP_CMD_WORK_QU]
root 246 2 0 11:15 ? 00:00:00 [kworker/u3:0-hci0]
root 248 2 0 11:15 ? 00:00:00 [kworker/u3:2-hci0]
root 252 2 0 11:15 ? 00:00:00 [cryptd]
root 274 1 0 11:15 ? 00:00:01 /usr/sbin/ModemManager
ntp 294 1 0 11:15 ? 00:00:00 /usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
root 302 1 0 11:15 ? 00:00:00 /sbin/syslogd -n -O /var/log/messages
root 305 1 0 11:15 ? 00:00:00 /sbin/klogd -n
root 316 1 0 11:15 ? 00:00:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive
root 329 1 0 11:15 ttySTM0 00:00:00 -sh
root 330 1 0 11:15 tty1 00:00:00 /sbin/getty 38400 tty1
root 378 2 0 12:19 ? 00:00:01 [kworker/0:2-events_power_efficient]
root 385 2 0 12:42 ? 00:00:00 [kworker/u2:2-events_unbound]
root 408 2 0 12:44 ? 00:00:00 [kworker/0:0H-kblockd]
root 422 2 0 12:46 ? 00:00:00 [kworker/0:1-pm]
root 428 2 0 12:47 ? 00:00:00 [kworker/u2:0-events_unbound]
root 430 1 0 12:47 ? 00:00:00 hostapd /etc/hostapd.conf -ddd -K -B
nobody 433 1 0 12:48 ? 00:00:00 dnsmasq -C /etc/dnsmasq.conf
root 447 329 99 12:54 ttySTM0 00:00:00 ps -ef

No scanning request at the moment, connecting to esp AP still not working.

Shreyas0-7 · 2024-10-28T10:45:54Z

Hey @iradmilo-bytelab
we have raised a internal MR which will validate scan command is not processed when interface is AP which is under review here is the patch for the changes can you please verify if this resolves your issue.

cd /PATH/esp_hosted/
git apply debug.patch
debug.zip

Also please enable debug logs as shown below using idf.py menuconfig for the firmware.

iradmilo-bytelab · 2024-10-29T13:52:20Z

@Shreyas0-7

1 ) RPI 3 - ESP32C3 SPI setup test

We have connected Raspberry Pi 3 Model B with esp32C3 chip using the hostapd conf and dnmasq template you provided in the README and did not get the AP mode to work. We cannot even get the AP to advertise in this RPI setup.

esp32c3_log.txt
hostapd_log.txt

commit used: 30f4082

Can you please screenshot me where you got Raspberry Pi ESP setup to work in AP mode?

Additionally: How did you get wpa_key_mgmt=SAE to work with hostapd (we are using version 2.10)?

2 ) STM32MP133 - ESP32C3 SPI patch test

After testing the provided patch we still are not able to connect to AP.

Host_logs_after_patch.txt
Esp_logs_after_patch.txt

3 ) Stable release
@mantriyogesh When can we expect stable release of ESP32 AP mode for ng_hosted?

Our customer will soon (in month or so) go into testing of the final product which has to have WIFI chip with AP mode functional.
At the moment we are not sure if we should continue with this chip or maybe try to use some other WIFI chip.

Can we organize a call session where we could troubleshoot the issue and get the information about a stable release?

cc: @mayurpatel19912009

mantriyogesh · 2024-10-29T14:11:51Z

@iradmilo-bytelab ,

Let me sync up internally and come back on this tomorrow..

mantriyogesh · 2024-10-29T14:43:55Z

Hello @mayurpatel19912009 ,

Noted. Let me test this feature on the raspberry pi I have and let me share you the logs, at least reproduce and face the issues as faced by you to at least know what is going wrong and come back on this. In any case, I understand you need urgent closure or commitment from our side.

mantriyogesh · 2024-10-29T15:54:48Z

Hello @mayurpatel19912009 ,

We are making a short video to showcase how we trigger the connection.
I think this would be the first thing, which can help to understand if there is any difference in setup / config or procedure.

@iradmilo-bytelab I would request you to wait up till tomorrow.
@Shreyas0-7 is making video. We will share this asap for your reference.

Shreyas0-7 · 2024-10-30T10:09:27Z

Hey @iradmilo-bytelab uploading the video with ps logs.
Here's a link to google drive with attachments
https://drive.google.com/file/d/1hCWqH7UuhlOrNf8ES_JBL7apczy2M7Io/view?usp=drive_link

mayurpatel19912009 · 2024-10-30T11:21:18Z

Thanks for the fast response. Our team will look into this.
before that some que which were not present in the vdo.

Did you try any other client like andoid / ios / windows to connect?
what about dhcp server/ dnsmasq configutation? Does it matter here? because an ip must be assigned to a client which is connecting to it.
which version of hostapd are you using?
Are you testing with kernel 4.19.118 which is a failry old kernel. we are using Linux 6.1.28 kernel. It will be really nice if you can test it on that. because min. / max tested supported kernel i have not seen on your documentation.

mantriyogesh · 2024-10-30T11:24:38Z

@Shreyas0-7 PTAL

iradmilo-bytelab · 2024-10-30T11:32:42Z

@Shreyas0-7
Thank you for the video.
Additionally please can you provide info how did you get 'wpa_key_mgmt=SAE' hostapd conf setting to run with hostapd?

mayurpatel19912009 · 2024-10-30T12:28:39Z

Yes, as @iradmilo-bytelab mentioned we get error when we use SAE in hostapd.conf

kapilkedawat · 2024-10-30T12:48:10Z

Thanks for the fast response. Our team will look into this. before that some que which were not present in the vdo.
Did you try any other client like andoid / ios / windows to connect?

Yes, we tried android and iOS client, however we don't test using windows much.

what about dhcp server/ dnsmasq configutation? Does it matter here? because an ip must be assigned to a client which is connecting to it.

Yes, dhcp server is required for IP, you can also use static IP depending on your requirement and usecase.

which version of hostapd are you using?

We use current hostapd version (v2.11) normally, however hostapd version doesn't matter much here since most features are present from long and you can use your current version(v2.10).

Are you testing with kernel 4.19.118 which is a failry old kernel. we are using Linux 6.1.28 kernel. It will be really nice if you can test it on that. because min. / max tested supported kernel i have not seen on your documentation.

Sure, we will retest with (recent kernel version + Linux laptop) again and see if any issue is observed.

Additionally please can you provide info how did you get 'wpa_key_mgmt=SAE' hostapd conf setting to run with hostapd?

You can recompile the hostapd with SAE feature enabled. Please enable this flag during recompilation.

mayurpatel19912009 · 2024-10-30T14:20:47Z

We are trying to replicate the same thing which you are doing

hostapd 2.10 (with SAE mode enabled) + exact same as config as yours
wpa_supplicant as connecting client + exact same config as yours

I am attaching a screenshot because thats what i can send you at the moment. Its not connecting. (left : hostapd log , right : wpa_supplicant log)

iradmilo-bytelab · 2024-10-30T14:59:26Z

@Shreyas0-7

With using hostapd 2.10 ( with SAE enabled) and hostapd and wpa_supplicant setup as in video example I get this result

wpa_supplicant linux notebook side:

sudo wpa_supplicant -i wlp0s20f3 -c ~/wpa2_esp.conf
Successfully initialized wpa_supplicant
wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=HR
wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=HR

wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: PMKSA-CACHE-ADDED dc:54:75:56:26:dd 0
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: Removed BSSID dc:54:75:56:26:dd from ignore list (clear)
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: Removed BSSID dc:54:75:56:26:dd from ignore list (clear)
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: Removed BSSID dc:54:75:56:26:dd from ignore list (clear)
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=1 duration=10 reason=CONN_FAILED
wlp0s20f3: CTRL-EVENT-SSID-REENABLED id=0 ssid="MY_SSID"
wlp0s20f3: BSSID dc:54:75:56:26:dd ignore list count incremented to 2, ignoring for 10 seconds
wlp0s20f3: Removed BSSID dc:54:75:56:26:dd from ignore list (clear)
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=2 duration=20 reason=CONN_FAILED
wlp0s20f3: CTRL-EVENT-SSID-REENABLED id=0 ssid="MY_SSID"
wlp0s20f3: BSSID dc:54:75:56:26:dd ignore list count incremented to 2, ignoring for 10 seconds
wlp0s20f3: Removed BSSID dc:54:75:56:26:dd from ignore list (clear)
wlp0s20f3: SME: Trying to authenticate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Trying to associate with dc:54:75:56:26:dd (SSID='MY_SSID' freq=2437 MHz)
wlp0s20f3: Associated with dc:54:75:56:26:dd
wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=dc:54:75:56:26:dd reason=2
wlp0s20f3: Added BSSID dc:54:75:56:26:dd into ignore list, ignoring for 10 seconds
wlp0s20f3: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=3 duration=30 reason=CONN_FAILED

cat ~/wpa2_esp.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="MY_SSID"
psk="MY_PASSPHRASE"
key_mgmt=SAE
ieee80211w=2
}

Host side:

root@mcm-ng:~# echo $(uname -r)
6.1.28

cat /etc/hostapd.conf

interface=wlan0
driver=nl80211
ssid=MY_SSID
hw_mode=g
channel=6
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_key_mgmt=SAE
wpa_passphrase=MY_PASSPHRASE
rsn_pairwise=CCMP
ieee80211w=2

root@mcm-ng:~# cat /etc/dnsmasq.conf
interface=wlan0 # Use the wireless interface
dhcp-range=192.168.1.2,192.168.1.100,255.255.255.0,24h # DHCP range
domain-needed # Don't forward short names
bogus-priv # Never forward addresses in the non-routed address spaces
expand-hosts # Use the expanded hostname

mayurpatel19912009 · 2024-10-30T15:08:51Z

to make sure its not in version of hostapd -> cross compiled 2.11 (same as yours)
Still the same error. There is something wrong with esp_32 host SPI Driver <> Firmware which is not letting us connect.

mayurpatel19912009 · 2024-10-30T15:10:09Z

So now very eager to see your latest Kernel (ex. 6.1.28) test from espressif side. I hope that also works on your side.

mantriyogesh · 2024-10-30T15:19:05Z

Btw, @mayurpatel19912009 ,

Do you have raspberry pi same as that of the setup?

If no, it's okay.

If yes, it would fasten to localise issue.

If you do not issue in raspberry pi and only in your Linux, I think we might need to dig deeper.

In any case we will try with latest raspberry pi (with highest possible kernel which come with raspberry pi) and let you know our findings.
cc: @Shreyas0-7

mayurpatel19912009 · 2024-11-04T07:27:24Z

No we dont have raspebrryPi here at the moment and have no plan and resources for that.
We tried to match exact tools and exact versions of tools which you are using. TLDR: we did exactly the same that you are doing in the video. But hard luck. Now only the difference is : Kernel version (which can make an impact on driver level).

That's why we are keen to know the output of your latest kernel tests. Fingers crossed.. :)

mantriyogesh · 2024-11-04T07:54:06Z

Sure , we are working on it, keep you posted.

Shreyas0-7 · 2024-11-04T14:12:50Z

Hey @mayurpatel19912009 @iradmilo-bytelab
We have observed an issue with one of our clients that appears similar to what you are experiencing (we can't be certain yet, as your packet capture didn't include all the required packets). In this particular case, we receive multiple auth/assoc requests, which causes the hostapd and driver states to become unstable. Could you please try the attached patch to see if it resolves your issue?
del_station.zip

iradmilo-bytelab · 2024-11-05T08:58:04Z

@Shreyas0-7 and @mantriyogesh Have you setup a configuration with linux kernel version later than 4.16 and what version did you setup. Additionally did you try this patch on that setup?

iradmilo-bytelab · 2024-11-05T09:11:52Z

Tried myself only the patch applied to the latest master and still not able to connect to AP

Host logs:

wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: Setup of interface done.
ctrl_iface not configured!
root@mcm-ng:~# [ 832.038384] esp32_spi: decode_common_resp: [0x4] Command failed
[ 832.043159] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1
[ 842.037911] esp32_spi: decode_common_resp: [0x4] Command failed
[ 842.042708] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1
[ 843.566067] esp32_spi: esp_cfg80211_del_station:
[ 844.124517] esp32_spi: esp_cfg80211_del_station:
[ 856.048930] esp32_spi: decode_common_resp: [0x4] Command failed
[ 856.053768] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1
[ 876.048681] esp32_spi: decode_common_resp: [0x4] Command failed
[ 876.053521] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1
[ 905.068397] esp32_spi: decode_common_resp: [0x4] Command failed
[ 905.073201] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1
[ 948.078848] esp32_spi: decode_common_resp: [0x4] Command failed
[ 948.083631] esp32_spi: cmd_scan_request: wait_and_decode_cmd_resp(priv, cmd_node) failure, ret: -1

Peripheral logs:

I (29956) supported_rates: 0x3fcbad20 01 0a 02 04 0b 16 0c 12 18 24 30 48 |.........$0H|
I (29966) ht_rates: 0x3fcbad2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (29976) ht_rates: 0x3fcbad3c 00 00 00 00 00 00 00 00 00 00 00 00 |............|
I (29985) vht_rates: 0x3fcbad48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |..............|
I (29995) he_rates: 0x3fcbad58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (30005) he_rates: 0x3fcbad68 00 00 00 00 00 00 00 00 00 00 00 |...........|
I (30015) wifi:new:<6,0>, old:<6,0>, ap:<6,1>, sta:<255,255>, prof:6
I (30084) FW_MAIN: AP station command

I (30084) FW_CMD: process_ap_station:got station add command

I (30085) mac: 0x3fcbad00 14 85 7f 23 ee d9 |...#..|
I (30092) FW_CMD: aid=0

I (30096) supported_rates: 0x3fcbad20 00 00 00 00 00 00 00 00 00 00 00 00 |............|
I (30106) ht_rates: 0x3fcbad2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (30116) ht_rates: 0x3fcbad3c 00 00 00 00 00 00 00 00 00 00 00 00 |............|
I (30125) vht_rates: 0x3fcbad48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |..............|
I (30135) he_rates: 0x3fcbad58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (30145) he_rates: 0x3fcbad68 00 00 00 00 00 00 00 00 00 00 00 |...........|
I (30154) FW_CMD: add_station_node_ap: not station add cmd, handle later

I (30194) FW_MAIN: AP station command

I (30194) FW_CMD: process_ap_station:got station add command

I (30194) mac: 0x3fcbad00 14 85 7f 23 ee d9 |...#..|
I (30202) FW_CMD: aid=0

I (30206) supported_rates: 0x3fcbad20 00 00 00 00 00 00 00 00 00 00 00 00 |............|
I (30216) ht_rates: 0x3fcbad2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (30226) ht_rates: 0x3fcbad3c 00 00 00 00 00 00 00 00 00 00 00 00 |............|
I (30235) vht_rates: 0x3fcbad48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |..............|
I (30245) he_rates: 0x3fcbad58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
I (30255) he_rates: 0x3fcbad68 00 00 00 00 00 00 00 00 00 00 00 |...........|
I (30264) FW_CMD: add_station_node_ap: not station add cmd, handle later

I (30424) FW_MAIN: Add key request

I (30424) FW_CMD: set_key_internal:1545

I (30424) FW_CMD: Setting PTK

I (30426) FW_CMD: Unregistered event: 14

I (30454) FW_MAIN: AP station command

I (30454) FW_CMD: process_ap_station:got station add command

I (30454) mac: 0x3fcbad00 14 85 7f 23 ee d9 |...#..|
I (30462) FW_CMD: aid=0

Shreyas0-7 · 2024-11-05T10:26:08Z

Hi @iradmilo-bytelab ,
Yes, we have tested this patch with the latest kernel version, v6.6 (bookworm). Please see the attached logs showing successful connections
hosted_ng_502_v6.zip
It also seems that you haven't applied the previous patch, which discards scan requests at the driver level for the SoftAP interface. I have attached a combined patch hosted_cmd_del.zip for you to test further.
From the hostapd logs, it appears that the scan request is not being initiated by hostapd. Could you please try again after stopping the Network Manager with this command:
sudo systemctl stop NetworkManager

iradmilo-bytelab · 2024-11-05T12:08:24Z

Hi,

thank you for providing the logs of the solution working on newer kernel version.

From my side I still cannot connect linux laptop to ESP AP, even after following all the instructions.

Commit of ESP hosted on host and peripheral is 4798049.

Kernel version is 6.1.28 (stm32mp-r1.1 mickledore)

Hostapd version is 11 built with SAE config flag.

./hostapd -v
hostapd v2.11
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2024, Jouni Malinen [email protected] and contributors

dnsmasq conf and hostapd conf are as in README of esp/hosted_ng.

Attaching logs from host, peripheral and linux PC where wpa_supplicant with stopped NM was utilized.

del_station_patch_test.zip

mayurpatel19912009 · 2024-11-05T16:07:10Z

Hello,

we tried completely from beginning by

checking out repo master
patched above patch
built driver and and firmware both again and flashed again
started hostapd with your config on our board (everything else off)
tried to connect via iPhone with creds it does not work
Tried to connect a Linux Ubuntu client with NetworkManager turned off and via wpa_supplicant.conf given by you and having support for SAE.
and it showed us first signed of connection.
i tried it to stop wpa_supplicant on my client PC while leting hostapd running.
i started wpa_supplicant again but this time it was not able to connect. (went to loop)
I stopped hostapd also on the board and started again. and then i was able to connect again via wpa_supplicant.

summary from this was : i have to restart hostapd every time once i am successfully connected via client to connect again.

one more point that i found as error in hostapd logs ->

nl80211: Failed to get current TX sequence for a key (link_id=-1 idx=1): -95 (Operation not supported)
nl80211: Failed to get current TX sequence for a key (link_id=-1 idx=4): -95 (Operation not supported)

We treid connecting via iPhone with SSID + PASS -> Not Connected
I am not understanding why are you using SAE. We are having many issues refgarding testing due to SAE mode. -> please try to use wpa or wpa2 from next tests so that we can do the same.

so finally, for your detailed info I am attaching a zip containing

hostapd_test.log: hostapd logs
wpa_supp.log: log for 1st try -> success
wpa_supp_2ndtime.log -> not connected
coection_test_05-11-2024.mkv -> showing all steps one by one for coonection

test.zip

Please let us know if these things gives some hints at your side.

Why we are able to connect only once? Before we restart hostapd
Why these nl80211 errors coming and what does it mean?
Why we are not able to connect via any other client (ex. ios) . please test atleast once at your side and let us know if that also works at your end.
Any other hint that you find from our logs?

Shreyas0-7 · 2024-11-07T14:12:07Z

Hey @mayurpatel19912009 thanks for reporting the issue. Recent issue observed was due a fix provided earlier. This issue has been resolved properly now. Please pull the latest change and check for reconnection.
Sure we can test using wpa2 also.
Don't apply previous patches and make sure the network manager is off for host
Please make sure you run ./setup.sh in /PATH/esp_hosted/esp_hosted_ng/esp/esp_driver to update new firmware libraries
If you are still facing the issue we are happy to help

iradmilo-bytelab · 2024-11-07T23:05:36Z

Hi @Shreyas0-7 ,

we are still not able to connect to ESP AP after pulling the latest changes.
Could we arrange a session where we could go through setting up and testing the AP functionality on our board?

Additionally I am attaching logs from esp side of the moment station tries to connect to AP, not sure if they are of any help.
esp_logs.log

Shreyas0-7 · 2024-11-08T05:09:47Z

Hey @iradmilo-bytelab
For us to debug the issue we need hostapd logs, esp logs, dmesg logs as well as sniffer capture
Can you please test it again and provide us the logs

iradmilo-bytelab · 2024-11-08T08:58:04Z

@Shreyas0-7 OK I will try capture the traffic, just give me more information before I do the test, should I change anything in ESP32C3 firmware menuconfig, do I need to kill network manager on the device connecting to the AP or only on the host? Can I use WPA2-PSK as key or do I need SAE for the solution to work?

Shreyas0-7 · 2024-11-08T09:26:38Z

Hey @iradmilo-bytelab

No you don't need to change anything for the firmware menuconfig just make sure you are trying on the latest master
Make sure you have this commit in your git log
commit cc1cfcc
Author: Shreyas Sheth
Date: Thu Nov 7 12:55:28 2024 +0530

fix(esp_hosted_ng): Softap fix delete node
Kill network manager on host side on which you are trying to start softAP
You can use WPA2-PSK for the solution

iradmilo-bytelab · 2024-11-08T12:13:23Z

@Shreyas0-7

I get it to connect, at least from logs, however disconnection happens after around a minute.
I was connecting through Linux interface with which I normally connect to APs.
I tried connecting afterwards (not in logs) again and it does not connect at all.

Logs:
8_11_2024_debug_connecting_2_AP.zip

iradmilo-bytelab · 2024-11-08T13:02:59Z

Also
dmesg.log

iradmilo-bytelab · 2024-11-14T14:32:45Z

@Shreyas0-7

Thank you for helping us get the solution working. The trick was to kill NetworkManager and wpa_supplicant.
However we need NM and wpa functional for setting up and controlling the cellular network. Can you please help us how to setup wlan interface in NetworkManager so that AP still works?

Shreyas0-7 · 2024-11-15T12:43:08Z

Hey @iradmilo-bytelab
We have added changes to support softap with NetworkManager.
Please pull the new changes.
You can use this command to start softap using nmcli
sudo nmcli dev wifi hotspot ifname wlan0 con-name MyHotspot ssid "MYSSID" password "MYPASSWORD" band bg channel 6

SoftAP works if connecting via Mobile (Android/iOS) but Laptops(Windows/Linux) did not work. #502

SoftAP works if connecting via Mobile (Android/iOS) but Laptops(Windows/Linux) did not work. #502

Comments

mayurpatel19912009 commented Sep 30, 2024

Checklist

Issue or Suggestion Description

mantriyogesh commented Sep 30, 2024

mayurpatel19912009 commented Sep 30, 2024

mantriyogesh commented Sep 30, 2024

kapilkedawat commented Sep 30, 2024

mayurpatel19912009 commented Oct 1, 2024

Shreyas0-7 commented Oct 1, 2024

mayurpatel19912009 commented Oct 1, 2024

Shreyas0-7 commented Oct 3, 2024

iradmilo-bytelab commented Oct 4, 2024

Shreyas0-7 commented Oct 5, 2024

iradmilo-bytelab commented Oct 22, 2024

Shreyas0-7 commented Oct 22, 2024

iradmilo-bytelab commented Oct 22, 2024

Shreyas0-7 commented Oct 22, 2024

iradmilo-bytelab commented Oct 22, 2024 • edited Loading

Shreyas0-7 commented Oct 23, 2024

iradmilo-bytelab commented Oct 23, 2024

Shreyas0-7 commented Oct 23, 2024

iradmilo-bytelab commented Oct 23, 2024

Shreyas0-7 commented Oct 23, 2024

iradmilo-bytelab commented Oct 23, 2024

Shreyas0-7 commented Oct 23, 2024

iradmilo-bytelab commented Oct 23, 2024

Shreyas0-7 commented Oct 24, 2024

iradmilo-bytelab commented Oct 24, 2024

Shreyas0-7 commented Oct 25, 2024

iradmilo-bytelab commented Oct 25, 2024

Shreyas0-7 commented Oct 28, 2024

iradmilo-bytelab commented Oct 29, 2024 • edited Loading

mantriyogesh commented Oct 29, 2024

mantriyogesh commented Oct 29, 2024

mantriyogesh commented Oct 29, 2024

Shreyas0-7 commented Oct 30, 2024

mayurpatel19912009 commented Oct 30, 2024 • edited Loading

mantriyogesh commented Oct 30, 2024

iradmilo-bytelab commented Oct 30, 2024 • edited Loading

mayurpatel19912009 commented Oct 30, 2024 • edited Loading

kapilkedawat commented Oct 30, 2024

mayurpatel19912009 commented Oct 30, 2024

iradmilo-bytelab commented Oct 30, 2024

mayurpatel19912009 commented Oct 30, 2024

mayurpatel19912009 commented Oct 30, 2024 • edited Loading

mantriyogesh commented Oct 30, 2024 • edited Loading

mayurpatel19912009 commented Nov 4, 2024

mantriyogesh commented Nov 4, 2024

Shreyas0-7 commented Nov 4, 2024 • edited Loading

iradmilo-bytelab commented Nov 5, 2024

iradmilo-bytelab commented Nov 5, 2024

Shreyas0-7 commented Nov 5, 2024

iradmilo-bytelab commented Nov 5, 2024

mayurpatel19912009 commented Nov 5, 2024

Shreyas0-7 commented Nov 7, 2024

iradmilo-bytelab commented Nov 7, 2024

Shreyas0-7 commented Nov 8, 2024 • edited Loading

iradmilo-bytelab commented Nov 8, 2024

Shreyas0-7 commented Nov 8, 2024

iradmilo-bytelab commented Nov 8, 2024

iradmilo-bytelab commented Nov 8, 2024

iradmilo-bytelab commented Nov 14, 2024

Shreyas0-7 commented Nov 15, 2024

iradmilo-bytelab commented Oct 22, 2024 •

edited

Loading

iradmilo-bytelab commented Oct 29, 2024 •

edited

Loading

mayurpatel19912009 commented Oct 30, 2024 •

edited

Loading

iradmilo-bytelab commented Oct 30, 2024 •

edited

Loading

mayurpatel19912009 commented Oct 30, 2024 •

edited

Loading

mayurpatel19912009 commented Oct 30, 2024 •

edited

Loading

mantriyogesh commented Oct 30, 2024 •

edited

Loading

Shreyas0-7 commented Nov 4, 2024 •

edited

Loading

Shreyas0-7 commented Nov 8, 2024 •

edited

Loading