Re: Setup help request

[James Prestwood <prestwoj@gmail.com>]

Hi Mauro,

On 1/2/24 7:11 AM, Mauro Condarelli wrote:
> Thanks James,
> comments inline below.
>
> SNIP!
>
> On 1/2/24 15:07, Mauro Condarelli wrote:
>> On 1/2/24 14:01, James Prestwood wrote:
>>> I think there is more going on but for starters it appears whatever 
>>> app your using to scan is sending an invalid probe request frame. 
>>> This causes IWD to ignore it which seems like the reason you cant 
>>> even see the AP in the scans. I've attached a patch you can test, 
>>> but I'm not sure this is something we can really upstream since its 
>>> out of spec. The concerning IE is Extended capabilities, this is 
>>> something IWD actually uses and parses, so the fact there is a 
>>> duplicate and each one is different makes it impossible to know 
>>> which one we should use. The probe request is including multiple 
>>> entries for "Extended Capabilities" and "FILS Request Parameters 
>>> (tag 258)". With the patch applied, and some other modifications to 
>>> iwmon you can see two entries for these IEs:
>>>
>>>                     Extended Capabilities: len 10
>>>                         Capability: bit  2: Extended channel switching
>>>                         Capability: bit 17: WNM-Sleep mode
>>>                         Capability: bit 19: BSS transition
>>>                         Capability: bit 25: SSID list
>>>                         Capability: bit 46: WNM- Notification
>>>                         Capability: bit 62: Opmode Notification
>>>                         04 00 0a 02 00 40 00 40 80 
>>> 01                    .....@.@..
>>>                     Tag 258: len 2
>>>                         00 
>>> 12                                            ..
>>>                     Extended Capabilities: len 10
>>>                         Capability: bit 17: WNM-Sleep mode
>>>                         Capability: bit 19: BSS transition
>>>                         Capability: bit 25: SSID list
>>>                         Capability: bit 46: WNM- Notification
>>>                         00 00 0a 02 00 40 00 00 00 
>>> 01                    .....@....
>>>                     Tag 258: len 2
>>>                         00 ff
>>>
>>> If this patch doesn't resolve the issue could you re-run the test 
>>> and start iwmon at the very beginning, prior to starting IWD?
>> I'll do it ASAP, but it will take a bit of time since I'll have to 
>> compile from sources (I installed from standard Debian package).
> Done.
> Only change in behavior was smartphone could see `beelink`, but not to 
> connect to it (no password asked)
> This means now my two (standard) clients behave in the same way.

Ok, so I'm not seeing any request to even connect from the AP side of 
things. Since your clients aren't even asking for a password I suspect 
it thinks there is some issue with compatibility. You could try using 
hostapd with a very basic configuration and see if that works, then we 
can go from there:

hw_mode=g
channel=1
ssid=testssid

wpa=1
wpa_pairwise=TKIP
wpa_passphrase=secret123

>
> I also changed my start script as follows:
> -------------------------
> #!/bin/bash
>
> iwmon --write /tmp/iwmon.pcap >/tmp/iwmon.log 2>&1 &
> IWMON_PID=$!
> /usr/libexec/iwd -d >/tmp/iwd.log 2>&1 &
> IWD_PID=$!
>
> sleep 5
> iwctl device list
> iwctl device wlan0 set-property Mode ap
> iwctl ap wlan0 start-profile beelink
> iwctl ap wlan0 show
>
> mc
>
> kill $IWMON_PID
> kill $IWD_PID
>
> cd /tmp
> tar cJf iw.tar.xz iwmon.pcap iwmon.log iwd.log
> -------------------------
>
> I attach logs.
>
> Sorry being a continued nuisance.

No worries, its all part of the process. AP mode in IWD is still 
experimental, there are obviously kinks to work out still.

> Mauro