Hi, I've recently started noticing on my laptop that iwd gets stuck on 'connecting' state when I boot a **second time** right after poweroff. The fix is quite easy. Just disconnect and connect again from iwctl.

I recall having a similar issue not long ago. Maybe a regression was introduced. For the record, router and connection settings are the same as before. Arch Linux with kernel 5.16-zen1. Thanks! _______________________________________________ iwd mailing list -- iwd(a)lists.01.org To unsubscribe send an email to iwd-leave(a)lists.01.org

Hi James, I've gone through debugging and this is what I have: https://termbin.com/y9vq 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 /etc/iwd/main.conf [General] EnableNetworkConfiguration=true AddressRandomization=once [Network] NameResolvingService=resolvconf I've also tried to collect iwmon logs but they are huge, like almost 2 MB. Should I filter some of the info as the wiki shows (--nortnl -- nowiphy --noscan). Thanks! _______________________________________________ iwd mailing list -- iwd(a)lists.01.org To unsubscribe send an email to iwd-leave(a)lists.01.org

These are the logs with IWD_DHCP_DEBUG=1. https://termbin.com/yn9k On first attempt I didn't manage to get a connection due to DHCP, but after stopping/starting it worked. _______________________________________________ iwd mailing list -- iwd(a)lists.01.org To unsubscribe send an email to iwd-leave(a)lists.01.org

Hi again, I managed to trigger the problem while dumping tcp packets. Here is the result: # ~ tcpdump -i wlan0 port 67 or port 68 -s 0 -w dhcp.pcap tcpdump: listening on wlan0, link-type EN10MB (Ethernet), snapshot length 262144 bytes ^C 12 packets captured 12 packets received by filter 0 packets dropped by kernel # ~ tcpdump -r dhcp.pcap reading from file dhcp.pcap, link-type EN10MB (Ethernet), snapshot length 262144 18:33:36.492009 IP _gateway.bootps > 192.168.1.35.bootpc: BOOTP/DHCP, Reply, length 284 18:33:36.492212 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:33:38.606330 IP _gateway.bootps > 192.168.1.36.bootpc: BOOTP/DHCP, Reply, length 284 18:33:40.021633 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:33:48.860117 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:34:05.360324 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:34:14.092945 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:34:14.705123 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:34:16.217430 IP _gateway.bootps > host.bootpc: BOOTP/DHCP, Reply, length 284 18:34:16.217613 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300 18:34:16.313729 IP _gateway.bootps > host.bootpc: BOOTP/DHCP, Reply, length 284 18:34:16.320877 IP _gateway.bootps > host.bootpc: BOOTP/DHCP, Reply, length 284 So I stopped / started iwd.service and checked that connection was lost (no ping). Then started dumping packets while iwctl was constantly reporting 'connecting' state. From there I just disconnected and connected again successfully and aborted tcpdump.

_______________________________________________ iwd mailing list -- iwd(a)lists.01.org To unsubscribe send an email to iwd-leave(a)lists.01.org

Sorry, didn't know that. I reproduced the problem again and uploaded the file here: https://transfer.sh/get/jiEvOg/dhcp.pcap Hope this helps!

_______________________________________________ iwd mailing list -- iwd(a)lists.01.org To unsubscribe send an email to iwd-leave(a)lists.01.org

Out of curiosity what kind of network hardware are you using? Are you just using an off the shelf router or some custom openwrt/hostapd setup?

Below is a patch for ELL [1]. If its possible for you to apply it and rebuild both IWD/ELL manually to test that would be great. The issue should be solved but you will see an additional print when you normally would see IWD hang and never get connected:

This actually got merged an hour or two ago