Re: iwd configure location and files

[Denis Kenzior <denkenz at gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

Hi Jupiter,

On 12/12/21 10:39 PM, Jupiter wrote:
> Thanks all for your advice.
> 
> Further debugging it, it seems failing DHCP was caused by an error of
> Deauthentication even, not clear if the iwd error caused mwifiex
> disconnected from WiFi modem or the mwifiex cause iwd fall:

You probably need to share full logs.  From what I remember from your previous 
logs, iwd was connecting successfully to the AP but DHCP client was not able to 
start.  I think you need to determine why that happens.  I suspect an strace or 
additional logging will be required on your system.  Perhaps permissions are not 
setup correctly?

<snip>

> Aug 04 15:26:03 solar iwd[345]: Received Deauthentication event,
> reason: 2, from_ap: true

That just means the AP has deauthenticated us.  This may be because we're not 
able to 4-Way handshake properly, or because we aren't requesting a DHCP 
address, or any other reason.

> I followed the document to enable all CRYPTO setup so I don't think it
> is a CRYPTO configured issue in the kernel.
> 

iwd would refuse to start if these options are not present.  So this is most 
likely not the culprit.

> Also searching the Internet to find someone added
> ControlPortOverNL80211=False to resolve that issue on kernel 5.9.2,
> but it did not work on my kernel 5.10.59:
> 
> # cat /etc/iwd/main.conf
> [General]
> EnableNetworkConfiguration=True
> ControlPortOverNL80211=False

If EnableNetworkConfiguration is set to False, does iwctl show you as 
successfully connected?

> 
> The other issue is the error from_ap, but I am connecting to a home
> WiFi modem, it should use a station, not ap, right? Or doesn't matter?

No, this is fine.  The message just states that AP was the initiator of the 
disconnect and not the local (iwd) device.

Regards,
-Denis