Re: Cannot turn on AP mode without any error message

From: James Prestwood <prestwoj@gmail.com>
To: Chang Liu <goduck777@gmail.com>, iwd@lists.linux.dev
Subject: Re: Cannot turn on AP mode without any error message
Date: Wed, 31 Aug 2022 09:04:36 -0700	[thread overview]
Message-ID: <e5c70eecaa96e951176b6f99912822cb2ef5b3a9.camel@gmail.com> (raw)
In-Reply-To: <7fc91799-e030-fe90-44e9-c6490fbb6bb8@gmail.com>

Hi,

> src/netdev.c:netdev_set_interface_event() Interface type changed from
> station to ap
> src/manager.c:manager_config_notify() Notification of command Set 
> Interface(6)
> src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> Terminate
> 
> The output of iwmon is
> 
> < Request: Set Interface (0x06) len 16 [ack] 
> 1661908452.816568
>      Interface Index: 13 (0x0000000d)
>      Interface Type: 3 (0x00000003)
>  > Event: Set Interface (0x06) len 160 
> 1661908452.816674
>      Interface Index: 13 (0x0000000d)
>      Interface Name: wlan0
>      Wiphy: 0 (0x00000000)
>      Interface Type: 3 (0x00000003)
>      Wireless Device: 12 (0x000000000000000c)
>      MAC Address 9C:B6:D0:9A:5F:B7
>      Generation: 28 (0x0000001c)
>      4-Address: 0 (0x00)
>      Wiphy TX Power Level: 0 (0x00000000)
>      TXQ Stats: len 72
>          08 00 01 00 00 00 00 00 08 00 02 00 00 00 00 00 
> ................
>          08 00 03 00 00 00 00 00 08 00 04 00 00 00 00 00 
> ................
>          08 00 05 00 00 00 00 00 08 00 06 00 00 00 00 00 
> ................
>          08 00 08 00 00 00 00 00 08 00 09 00 00 00 00 00 
> ................
>          08 00 0a 00 00 00 00 00                          ........
>  > Response: Set Interface (0x06) len 4 [0x100] 
> 1661908452.816676
>      Status: Success (0)
> 

So we set to AP mode which is successful...

> < Request: Start AP (0x0f) len 224 [ack] 
> 1661908454.347354
>      Beacon Head: len 49
>          80 00 00 00 ff ff ff ff ff ff 9c b6 d0 9a 5f b7 
> .............._.
>          9c b6 d0 9a 5f b7 00 00 00 00 00 00 00 00 00 00 
> ...._...........
>          64 00 11 00 00 03 32 50 4c 01 03 82 0b 16 03 01 
> d.....2PL.......
>          06                                               .
>      Beacon Tail: len 48
>          30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 
> 0...............
>          00 0f ac 02 00 00 dd 18 00 50 f2 04 10 4a 00 01 
> .........P...J..
>          10 10 44 00 01 02 10 49 00 06 00 37 2a 00 01 20 
> ..D....I...7*..
>      Information Elements: len 0
>      IE Probe Response: len 0
>      IE Assoc Response: len 0
>      Beacon Interval: 100 (0x00000064)
>      DTIM Period: 3 (0x00000003)
>      Interface Index: 13 (0x0000000d)
>      SSID: len 3
>          32 50 4c                                         2PL
>      Hidden SSID: 0 (0x00000000)
>      Cipher Suites Pairwise:
>          CCMP (00:0f:ac) suite  04
>      Cipher Suite Group: CCMP (00:0f:ac) suite  04
>      WPA Versions: 2 (0x00000002)
>      AKM Suites:
>          PSK; RSNA PSK (00:0f:ac) suite  02
>      Auth Type: 0 (0x00000000)
>      Wiphy Frequency: 2437 (0x00000985)
>      Channel Width: 1 (0x00000001)
>      Socket Owns Interface/Connection: true
>      Control Port over NL80211: true
>  > Response: Start AP (0x0f) len 4 [0x100] 
> 1661908454.437724
>      Status: Success (0)

Then start the AP which is successful...

>  > Event: Stop AP (0x10) len 28 
> 1661908457.014173
>      Wiphy: 0 (0x00000000)
>      Interface Index: 13 (0x0000000d)
>      Wireless Device: 12 (0x000000000000000c)

Then 3 seconds later the kernel sends STOP_AP...

So the kernel, for whatever reason, stopped the AP. Are you able to try
out hostapd (with iwmon running) and see if this works? That would tell
us if its a kernel problem, or if IWD is doing something unexpected for
this driver.

Thanks,
James