Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: 54d22547-afc0-4701-b1fc-5a2a2e411646 at simplelogin.co
To: iwd at lists.01.org
Subject: Re: iwd 1.21 stuck on connecting state
Date: Fri, 14 Jan 2022 20:08:09 +0000	[thread overview]
Message-ID: <20220114200809.2807.69459@ml01.vlan13.01.org> (raw)
In-Reply-To: 2aaa505ef89f9ec1635c30e3a65674fe489f6580.camel@gmail.com

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

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!

             reply	other threads:[~2022-01-14 20:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 20:08 54d22547-afc0-4701-b1fc-5a2a2e411646 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-03 21:41 iwd 1.21 stuck on connecting state James Prestwood
2022-02-03 20:10 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-02-03 17:28 James Prestwood
2022-02-03 16:05 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-31 22:15 James Prestwood
2022-01-31 20:09 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-31 19:31 Denis Kenzior
2022-01-31 17:28 James Prestwood
2022-01-29 20:03 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-27 19:00 James Prestwood
2022-01-27 17:51 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-18 17:39 James Prestwood
2022-01-18 11:43 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-14 20:51 James Prestwood
2022-01-13 17:22 James Prestwood
2022-01-13 11:27 54d22547-afc0-4701-b1fc-5a2a2e411646

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220114200809.2807.69459@ml01.vlan13.01.org \
    --to=iwd@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox