-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP NG- Network with passphrase fails on linux openwrt host #567
Comments
Please attach the
Also ensure that you use latest master at both esp and host. |
I could not successfully run the idf script on the device itself due to limited resources. However I have the complete dmesg and the hostapd log with the latest esphosted version. |
@kapilkedawat PTAL.. |
Every other command getting timed out. I also note
but unsure if this is related to ESP-Hosted as such. |
@BrelJordan My bad, seems like transport issue, please verify your connections first and run raw throughput |
I think the problem occurs earlier during the configuration of the chip. Look at what the esp firmware says when I start hostapd with a paraphrase:
It sets the parameter authmode to 0 esp_hosted_ng/esp/esp_driver/esp-idf/components/esp_wifi/include/esp_wifi_types.h
|
The host driver is responsible for transmitting the hostapd configuration to the esp MCU. When looking at the source, it seems the auth_mode is not configured and hence has a default of 0. In the funtion esp_cfg80211_start_ap authmode is not populated. From what I see it should be in info->nl80211_auth_type. However some other variables from esp_ap_config :
are not configured. |
Hi @BrelJordan, Please run a raw throughput test once so that we can confirm the transport connections. |
@BrelJordan , Thanks for the Raw throughut from esp to host. |
Hi @mantriyogesh here are the results for host -> esp. |
Can you stop your logs in host, to realise if the tx and rx are having symmetrical bandwidths? There are a lot of debug logs in linux side. later point of time, you can enable the required ones? |
I was able to resolve the issue by reducing the SPI frequency to 10 MHz, which allowed me to connect to the AP. However, I am still not receiving an IP address from my host. Using Wireshark and tcpdump, I monitored both the client interface and the ESP-Hosted kernel module’s network interface. I observed that the client sends a DHCP request, but it never reaches the ESP host’s network interface. Has anyone encountered a similar issue? I’d appreciate any insights or tips on how to debug this further. Thanks in advance! |
Hi @BrelJordan, could you please share wireless sniffer capture? |
Do you mean I should export the capture in another Format and not just as clear text? I just did as psml, I added a .txt ending because github does not allow psml files. |
I also encountered the situation that DHCP is unreachable and the AP intranet is inaccessible after turning on CCMP encryption of WPA. Only if I set the AP mode to open mode, it will be completely normal. What should I do in this situation? |
Do you receive a DHCP request on the host? I don't. |
I meant wifi sniffer capture.
could you also share sniffer capture and esp and host logs? |
Hello I did as you asked, the host is : f0:f5:bd:e9:ae:c8 and the client the McTechno device. |
Hello @kapilkedawat from the wifi sniffer I see the dhcp request from the client. I activated debug Messages in the idf firmware to see what is going on. Comparing a psk2 secure and open network. For the secure Network I don't get this debug message: D (45322552) wifi:eb is dhcp or dns sport = 68, dport = 67 Both logs look very similar up to this point. Please help me and compare the logs you may see the issue I just can't find: |
Apologies for the delayed response. Are you using the latest driver and firmware? I just tested in open mode and was able to connect successfully. Could you capture a wireless sniffer trace and share the pcap file with us for analysis? (Please avoid exporting it to text.) Also, please provide details about your host system, including the Raspberry Pi version and Linux distribution/version used. |
Hello @kapilkedawat I am using OpenWrt with the Linux kernel version:6.6.37. Yes am am using the actual esp firmware and Kernel module. I have already done a WiFi sniffer you can download it from my second to last post. I just added .txt extension for the upload. |
Hi @BrelJordan we are not able to open wifi-monitoring.txt using wireshark, how did you capture it? |
Could you open the .pslm file? |
Yes, but that only contains headers in most cases, also need to analyze the packets in wireshark :) .. we will need your help since this is not reproducible for us. |
After I used fg, everything worked fine. Thanks everyone. |
Hello @Yjxslhz , Can you please let us know if you needed any kind of modifications to get FG working? @kapilkedawat |
@BrelJordan @Yjxslhz could you please pull latest code and retry(both firmware and host)? |
Ok I will try again |
Checklist
How often does this bug occurs?
always
Expected behavior
Create an access point with a Passphrase stations can connect to.
Hostapd config from esphosted's page:
Actual behavior (suspected bug)
The AP is created but without any password (authmode=0 ) and devices fail to connect because the host complains no key is given by the peer.
Terminal output:
esp32c3:
Error logs or terminal output
Steps to reproduce the behavior
1 On a linux host with the esphosted-ng kmod installed run:
hostapd -ddd host.conf
Project release version
commit hash: c79b7e1
System architecture
ARM 64-bit (Apple M1/M2, Raspberry Pi 4/5)
Operating system
Linux
Operating system version
openwrt 24
Shell
sh
Additional context
No response
The text was updated successfully, but these errors were encountered: