Re: iwd 1.18 doesn't connect to network on boot

Re: iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

> Aha!  Thanks for tracking this down.  I believe the patch I just sent to the 
> mailing list should fix.

Thanks for the quick fix :)

I've already tested the patch and problem is gone. Great!

Re: iwd 1.18 doesn't connect to network on boot

[Denis Kenzior]

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

Hi Jason,

On 9/27/21 10:56 AM, 58e33db1-f428-4823-8cc3-d962d0fb8aa8(a)slmail.me wrote:
>> Well, I'm even more stumped then.  Looking at the commits in 1.18, I do not
>> believe we changed anything even remotely related to this.  Even more
>> interesting is that this only happens on boot and not in subsequent attempts
>> which makes this hard to duplicate.
>>
>> I'll poke around some more, but I think a git bisect is the only way to narrow
>> this down.
> 
> Well Denis, I've managed to track it down to this commit:
> 

Aha!  Thanks for tracking this down.  I believe the patch I just sent to the 
mailing list should fix.

Regards,
-Denis

Re: iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

> Well, I'm even more stumped then.  Looking at the commits in 1.18, I do not 
> believe we changed anything even remotely related to this.  Even more 
> interesting is that this only happens on boot and not in subsequent attempts 
> which makes this hard to duplicate.
> 
> I'll poke around some more, but I think a git bisect is the only way to narrow 
> this down.

Well Denis, I've managed to track it down to this commit:

commit ad228461abbfe1875e15624b2be0c1535e623307
Date:   Fri Aug 27 05:02:03 2021 +0200

    netconfig: Move loading settings to new method, refactor
    
    Split loading settings out of network_configure into a new method,
    network_load_settings.  Make sure both consistently handle errors by
    printing messages and informing the caller.

 src/netconfig.c | 236 +++++++++++++++++++++++++++++++++++---------------------
 src/netconfig.h |   5 +-
 src/p2p.c       |  12 ++-
 src/station.c   |  20 +++--
 4 files changed, 175 insertions(+), 98 deletions(-)

I've done all the testing with AddressRandomization=network in main.conf.

Cheers.

Re: iwd 1.18 doesn't connect to network on boot

[Denis Kenzior]

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

Hi Jason,

> Well, I've discovered how to trigger the problem in my scenario. It's all related with setting AddressRandomization to 'network'. The other two possible values 'disabled' (default) and 'once' both work fine.

Well, I'm even more stumped then.  Looking at the commits in 1.18, I do not 
believe we changed anything even remotely related to this.  Even more 
interesting is that this only happens on boot and not in subsequent attempts 
which makes this hard to duplicate.

I'll poke around some more, but I think a git bisect is the only way to narrow 
this down.

Regards,
-Denis

Re: iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

> Hi Jason,
> 
> > Here you have. For some reason is not getting an IP:
> > 
> 
> <snip>
> 
> > iwd[11413]: src/station.c:station_connect_cb() 6, result: 0
> > iwd[11413]: src/station.c:station_connect_ok()
> 
> Yep, so we connect OK, start DHCP
> 
> > iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> > iwd[11413]: [DHCPv4] l_dhcp_client_start:1174 Entering state: DHCP_STATE_SELECTING
> > iwd[11413]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
> > iwd[11413]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
> > iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
> > iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
> > iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> > iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> > iwd[11413]: src/station.c:station_early_neighbor_report_cb() ifindex: 6, error: -110(Connection timed out)
> > iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> > iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> > iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> > iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> > 
> 
> But nothing gets received from the DHCP server.  I'm a bit stumped since we 
> haven't touched anything related to dhcp between 1.17 and 1.18.  We started 
> sending the DHCP rapid commit option in iwd 1.17, so maybe that is why your 
> server is ignoring us?
> 
> Does starting dhcpcd or something while iwd is in this 'connecting' state obtain 
> an IP?
> 
> > I think is relevant to the bug that I'm using this unit to start iwd.service:
> > 
> > # /usr/lib/systemd/system/iwd.service
> > [Unit]
> > Description=Wireless service
> > After=network-pre.target
> > Before=network.target
> > Wants=network.target
> > 
> > [Service]
> > Type=dbus
> > BusName=net.connman.iwd
> > ExecStart=/usr/lib/iwd/iwd
> > NotifyAccess=main
> > LimitNPROC=1
> > Restart=on-failure
> > CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_RAW CAP_NET_BIND_SERVICE
> > PrivateTmp=true
> > NoNewPrivileges=true
> > DevicePolicy=closed
> > DeviceAllow=/dev/rfkill rw
> > ProtectHome=yes
> > ProtectSystem=strict
> > ProtectControlGroups=yes
> > ProtectKernelModules=yes
> > ConfigurationDirectory=iwd
> > StateDirectory=iwd
> > StateDirectoryMode=0700
> > 
> > [Install]
> > WantedBy=multi-user.target
> > 
> > # /etc/systemd/system/iwd.service.d/override.conf
> > [Service]
> > RuntimeDirectory=resolvconf
> > ReadWritePaths=/etc/resolv.conf
> > 
> > I remeber adding the override part few months ago due to another bug [1]. For some reason, forcing a disconnect/connect with iwctl doesn't hit the same problem.
> 
> But we're not even getting this far to even invoke resolvconf...
> 
> Any chance you can run a git bisect or otherwise narrow down what earlier 
> version of iwd was working properly at boot?
> 
> Regards,
> -Denis

Well, I've discovered how to trigger the problem in my scenario. It's all related with setting AddressRandomization to 'network'. The other two possible values 'disabled' (default) and 'once' both work fine.

Previous version 1.17 didn't show this behaviour. Anyway, I'm happy with 'once' since I no longer have specific settings by MAC in the router.

For the record, this configuration was working until version 1.17 included:

[General]
EnableNetworkConfiguration=true
AddressRandomization=network

[Network]
NameResolvingService=resolvconf

Re: iwd 1.18 doesn't connect to network on boot

[Denis Kenzior]

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

Hi Jason,

> Here you have. For some reason is not getting an IP:
> 

<snip>

> iwd[11413]: src/station.c:station_connect_cb() 6, result: 0
> iwd[11413]: src/station.c:station_connect_ok()

Yep, so we connect OK, start DHCP

> iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> iwd[11413]: [DHCPv4] l_dhcp_client_start:1174 Entering state: DHCP_STATE_SELECTING
> iwd[11413]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
> iwd[11413]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
> iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
> iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
> iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> iwd[11413]: src/station.c:station_early_neighbor_report_cb() ifindex: 6, error: -110(Connection timed out)
> iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
> iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
> 

But nothing gets received from the DHCP server.  I'm a bit stumped since we 
haven't touched anything related to dhcp between 1.17 and 1.18.  We started 
sending the DHCP rapid commit option in iwd 1.17, so maybe that is why your 
server is ignoring us?

Does starting dhcpcd or something while iwd is in this 'connecting' state obtain 
an IP?

> I think is relevant to the bug that I'm using this unit to start iwd.service:
> 
> # /usr/lib/systemd/system/iwd.service
> [Unit]
> Description=Wireless service
> After=network-pre.target
> Before=network.target
> Wants=network.target
> 
> [Service]
> Type=dbus
> BusName=net.connman.iwd
> ExecStart=/usr/lib/iwd/iwd
> NotifyAccess=main
> LimitNPROC=1
> Restart=on-failure
> CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_RAW CAP_NET_BIND_SERVICE
> PrivateTmp=true
> NoNewPrivileges=true
> DevicePolicy=closed
> DeviceAllow=/dev/rfkill rw
> ProtectHome=yes
> ProtectSystem=strict
> ProtectControlGroups=yes
> ProtectKernelModules=yes
> ConfigurationDirectory=iwd
> StateDirectory=iwd
> StateDirectoryMode=0700
> 
> [Install]
> WantedBy=multi-user.target
> 
> # /etc/systemd/system/iwd.service.d/override.conf
> [Service]
> RuntimeDirectory=resolvconf
> ReadWritePaths=/etc/resolv.conf
> 
> I remeber adding the override part few months ago due to another bug [1]. For some reason, forcing a disconnect/connect with iwctl doesn't hit the same problem.

But we're not even getting this far to even invoke resolvconf...

Any chance you can run a git bisect or otherwise narrow down what earlier 
version of iwd was working properly at boot?

Regards,
-Denis

Re: iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

> Hi Jason,
> 
> <snip>
> 
> > iwd[4842]: src/station.c:station_connect_cb() 8, result: 0
> > iwd[4842]: src/station.c:station_connect_ok()
> 
> So the interesting thing is that we connect successfully, so the issue is 
> actually in netconfig somewhere.  Can you tell me which version you had before 
> that worked?  Was it 1.17 or earlier?
> 
> > iwd[4842]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
> > iwd[4842]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
> > iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> > iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
> > iwd[4842]: src/station.c:station_early_neighbor_report_cb() ifindex: 8, error: -110(Connection timed out)
> > 
> > This is the point where connection is stuck and iwctl reports 'connecting' indefinitely despite being authenticated already.
> 
> Ok, can you get us a log with IWD_DHCP_DEBUG set as well?  See 'man 7 iwd.debug'
> 
> Regards,
> -Denis

Here you have. For some reason is not getting an IP:

iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification New Station(19)
kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 2/3)
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Authenticate(37)
iwd[11413]: src/netdev.c:netdev_authenticate_event()
kernel: wlan0: authenticated
kernel: wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
kernel: wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1411 status=0 aid=1)
iwd[11413]: src/netdev.c:netdev_unicast_notify() Unicast notification 129
iwd[11413]: src/netdev.c:netdev_control_port_frame_event()
kernel: wlan0: associated
iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Associate(38)
iwd[11413]: src/netdev.c:netdev_associate_event()
iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Connect(46)
iwd[11413]: src/netdev.c:netdev_connect_event()
iwd[11413]: src/eapol.c:eapol_handle_ptk_1_of_4() ifindex=6
iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
iwd[11413]: src/netdev.c:netdev_unicast_notify() Unicast notification 129
iwd[11413]: src/netdev.c:netdev_control_port_frame_event()
iwd[11413]: src/eapol.c:eapol_handle_ptk_3_of_4() ifindex=6
iwd[11413]: src/netdev.c:netdev_set_gtk() 6
iwd[11413]: src/station.c:station_handshake_event() Setting keys
iwd[11413]: src/netdev.c:netdev_set_tk() 6
iwd[11413]: src/netdev.c:netdev_set_rekey_offload() 6
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Notify CQM(64)
iwd[11413]: src/station.c:station_connect_cb() 6, result: 0
iwd[11413]: src/station.c:station_connect_ok()
iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
iwd[11413]: [DHCPv4] l_dhcp_client_start:1174 Entering state: DHCP_STATE_SELECTING
iwd[11413]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
iwd[11413]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
iwd[11413]: src/netdev.c:netdev_link_notify() event 16 on ifindex 6
iwd[11413]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
iwd[11413]: src/station.c:station_early_neighbor_report_cb() ifindex: 6, error: -110(Connection timed out)
iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
iwd[11413]: [DHCPv4] dhcp_client_send_discover:346
iwd[11413]: [DHCPv4] dhcp_client_timeout_resend:526
iwd[11413]: [DHCPv4] dhcp_client_send_discover:346

I think is relevant to the bug that I'm using this unit to start iwd.service:

# /usr/lib/systemd/system/iwd.service
[Unit]
Description=Wireless service
After=network-pre.target
Before=network.target
Wants=network.target

[Service]
Type=dbus
BusName=net.connman.iwd
ExecStart=/usr/lib/iwd/iwd
NotifyAccess=main
LimitNPROC=1
Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_RAW CAP_NET_BIND_SERVICE
PrivateTmp=true
NoNewPrivileges=true
DevicePolicy=closed
DeviceAllow=/dev/rfkill rw
ProtectHome=yes
ProtectSystem=strict
ProtectControlGroups=yes
ProtectKernelModules=yes
ConfigurationDirectory=iwd
StateDirectory=iwd
StateDirectoryMode=0700

[Install]
WantedBy=multi-user.target

# /etc/systemd/system/iwd.service.d/override.conf
[Service]
RuntimeDirectory=resolvconf
ReadWritePaths=/etc/resolv.conf

I remeber adding the override part few months ago due to another bug [1]. For some reason, forcing a disconnect/connect with iwctl doesn't hit the same problem.

# Generated by resolvconf
nameserver 127.0.0.1
options trust-ad edns0

[1] https://bugs.archlinux.org/task/67069

Re: iwd 1.18 doesn't connect to network on boot

[Denis Kenzior]

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

Hi Jason,

<snip>

> iwd[4842]: src/station.c:station_connect_cb() 8, result: 0
> iwd[4842]: src/station.c:station_connect_ok()

So the interesting thing is that we connect successfully, so the issue is 
actually in netconfig somewhere.  Can you tell me which version you had before 
that worked?  Was it 1.17 or earlier?

> iwd[4842]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
> iwd[4842]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
> iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
> iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
> iwd[4842]: src/station.c:station_early_neighbor_report_cb() ifindex: 8, error: -110(Connection timed out)
> 
> This is the point where connection is stuck and iwctl reports 'connecting' indefinitely despite being authenticated already.

Ok, can you get us a log with IWD_DHCP_DEBUG set as well?  See 'man 7 iwd.debug'

Regards,
-Denis

Re: iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

> Hi Jason,
> 
> On 9/23/21 6:04 AM, 58e33db1-f428-4823-8cc3-d962d0fb8aa8(a)slmail.me wrote:
> > Hi,
> > 
> > I'm on Arch Linux and after recent iwd upgrade to version 1.18 I'm no longer connected to my home network when booting. Previous version works just fine. I've managed to workaround the issue simply by going to iwctl and manually doing disconnect/connect every time I boot the computer.
> 
> Not much to go on.  Can you tell us what the previous version of iwd was?  How 
> is your AP configured? WPA2-Personal? WPA3-Personal?  At a minimum we also need 
> logs from iwd and preferably iwmon.  See https://iwd.wiki.kernel.org/debugging
> 
> Regards,
> -Denis

Hi Denis,

AP authentication is WPA2-Personal. I turned on logging and these are the relevant lines:

iwd[4842]: src/station.c:station_autoconnect_next() autoconnect: Trying SSID: xxxxxxxx
iwd[4842]: src/station.c:station_autoconnect_next() autoconnect: 'xx:xx:xx:xx:xx:xx' freq: 2447, rank: 2184, strength: -6500
iwd[4842]: src/netdev.c:netdev_cqm_rssi_update()
iwd[4842]: src/wiphy.c:wiphy_radio_work_insert() Inserting work item 2
iwd[4842]: src/station.c:__station_connect_network() connecting to BSS xx:xx:xx:xx:xx:xx
iwd[4842]: src/station.c:station_enter_state() Old State: autoconnect_quick, new state: connecting (auto)
iwd[4842]: src/scan.c:scan_cancel() Trying to cancel scan id 1 for wdev 8
iwd[4842]: src/wiphy.c:wiphy_radio_work_done() Work item 1 done
iwd[4842]: src/wiphy.c:wiphy_radio_work_next() Starting work item 2
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_mac_power_down_cb() Setting generated address on ifindex: 8 to: 9a:a7:a9:ba:16:52
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/wiphy.c:wiphy_reg_notify() Notification of command Wiphy Reg Change(113)
iwd[4842]: src/wiphy.c:wiphy_update_reg_domain() New reg domain country code for phy0 is XX
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/scan.c:scan_notify() Scan notification Trigger Scan(33)
iwd[4842]: src/station.c:station_netdev_event() Associating
iwd[4842]: src/scan.c:scan_notify() Scan notification New Scan Results(34)
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
kernel: wlan0: authenticate with xx:xx:xx:xx:xx:xx
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification New Station(19)
kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
kernel: wlan0: send auth to xx:xx:xx:xx:xx:xx (try 2/3)
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Authenticate(37)
iwd[4842]: src/netdev.c:netdev_authenticate_event()
kernel: wlan0: authenticated
kernel: wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
kernel: wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1411 status=0 aid=1)
iwd[4842]: src/netdev.c:netdev_unicast_notify() Unicast notification 129
iwd[4842]: src/netdev.c:netdev_control_port_frame_event()
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Associate(38)
iwd[4842]: src/netdev.c:netdev_associate_event()
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Connect(46)
iwd[4842]: src/netdev.c:netdev_connect_event()
iwd[4842]: src/eapol.c:eapol_handle_ptk_1_of_4() ifindex=8
kernel: wlan0: associated
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
iwd[4842]: src/netdev.c:netdev_unicast_notify() Unicast notification 129
iwd[4842]: src/netdev.c:netdev_control_port_frame_event()
iwd[4842]: src/eapol.c:eapol_handle_ptk_3_of_4() ifindex=8
iwd[4842]: src/netdev.c:netdev_set_gtk() 8
iwd[4842]: src/station.c:station_handshake_event() Setting keys
iwd[4842]: src/netdev.c:netdev_set_tk() 8
iwd[4842]: src/netdev.c:netdev_set_rekey_offload() 8
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Notify CQM(64)
iwd[4842]: src/station.c:station_connect_cb() 8, result: 0
iwd[4842]: src/station.c:station_connect_ok()
iwd[4842]: src/netconfig.c:netconfig_ipv6_select_and_install() IPV6 configuration disabled
iwd[4842]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
iwd[4842]: src/netdev.c:netdev_link_notify() event 16 on ifindex 8
iwd[4842]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
iwd[4842]: src/station.c:station_early_neighbor_report_cb() ifindex: 8, error: -110(Connection timed out)

This is the point where connection is stuck and iwctl reports 'connecting' indefinitely despite being authenticated already.

Anything else just tell me.

Thanks.

Re: iwd 1.18 doesn't connect to network on boot

[Denis Kenzior]

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

Hi Jason,

On 9/23/21 6:04 AM, 58e33db1-f428-4823-8cc3-d962d0fb8aa8(a)slmail.me wrote:
> Hi,
> 
> I'm on Arch Linux and after recent iwd upgrade to version 1.18 I'm no longer connected to my home network when booting. Previous version works just fine. I've managed to workaround the issue simply by going to iwctl and manually doing disconnect/connect every time I boot the computer.

Not much to go on.  Can you tell us what the previous version of iwd was?  How 
is your AP configured? WPA2-Personal? WPA3-Personal?  At a minimum we also need 
logs from iwd and preferably iwmon.  See https://iwd.wiki.kernel.org/debugging

Regards,
-Denis

iwd 1.18 doesn't connect to network on boot

[58e33db1-f428-4823-8cc3-d962d0fb8aa8]

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

Hi,

I'm on Arch Linux and after recent iwd upgrade to version 1.18 I'm no longer connected to my home network when booting. Previous version works just fine. I've managed to workaround the issue simply by going to iwctl and manually doing disconnect/connect every time I boot the computer.

Before doing this iwctl reports 'connecting' state indefinitely. Network coverage is always good. I have the laptop sitting on a table very close to the router and AFAIK, it didn't receive any firmware upgrade recently.

A little bit more of context in case it helps:

/etc/iwd/main.conf
[General]
EnableNetworkConfiguration=true
AddressRandomization=network

[Network]
NameResolvingService=resolvconf

iwevent
Waiting for Wireless Events from interfaces...
10:10:55.646290 wlan0 Scan request completed
10:10:57.801675 wlan0 Scan request completed
10:10:58.106493 wlan0 New Access Point/Cell address:Not-Associated => this is the disconnect
10:11:31.786703 wlan0 Scan request completed
10:11:31.871341 wlan0 Association Request IEs:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
10:11:31.871401 wlan0 Association Response IEs:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
10:11:31.871436 wlan0 New Access Point/Cell address:xx:xx:xx:xx:xx:xx

Distro mantainers just upgraded to latest upstream release, without any other modification on PKGBUILD.

https://github.com/archlinux/svntogit-community/blob/9b59977cbb8eb2ffe42ab613b033efa21c36c053/trunk/PKGBUILD


Thanks for helping!
--
Jason