This is a cache of https://discuss.96boards.org/t/16-02-ssid-not-broadcasting-correctly-when-hostapd-active/477. It is a snapshot of the page at 2024-11-01T03:20:31.483+0000.
16.02: SSID not broadcasting correctly when HOSTAPD active - DragonBoard410c - 96Boards Forum

16.02: SSID not broadcasting correctly when HOSTAPD active

Hi,
I want to use the DB410c in a headless IoT application where I first bring up the device as a Wireless Access Point, then give it an SSID and password so that it can connect to a Wi-Fi router as a Station. However, under the latest release 16.02, whenever I configure wireless using hostapd, the SSID isn’t visible to Wi-Fi clients. I have confirmed that this works in release 15.11. I don’t want to use 15.11 because it is missing the ‘410c/ubuntu: Can’t SSH in’ bug fixes that are also needed for headless development.

I suspect something in those fixes broke AP mode. Looking at the recent wcn36xx changes, I’m guessing the new code for adding the Traffic Information Map in smd.c is the culprit. It mucks around with the beacon message with padding and memmove.

The scripts I used to setup the AP were posted during the ‘410c/ubuntu: Can’t SSH in’ thread:
http://pakl.net/hotspot_410c_configure.sh
http://pakl.net/hotspot_410c_launch.sh

When properly configured the AP looks like this:


> sudo bash hotspot_410c_launch.sh
...
wlan0: AP-ENABLED
> sudo iw wlan0 info
Interface wlan0
        ifindex 3
        wdev 0x1
        addr 02:00:94:5b:24:18
        ssid My410C
        type AP
        wiphy 0
        channel 1 (2412 MHz), width: 20 MHz (no HT), center1: 2412 MHz

I get similar output (except for addr) on both 15.11 and 16.02, but only 15.11 actually shows up as an AP in an ‘nmcli d wifi’ scan from a second 410c.

If someone from the landing team could investigate this issue and file a bug if necessary, I’d be most grateful.

~ Dave

Hi Dave,

I believe I’m seeing the same problem here (and have started investigating it).

Could you confirm that when this happens the dmesg contains a few lines stating that the wcnss processor has crashed?

Regards,
Bjorn