From: Denis Kenzior <denkenz@gmail.com>
To: Bruno Dantas <dantas@airpost.net>,
James Prestwood <prestwoj@gmail.com>,
iwd@lists.linux.dev
Subject: Re: iwd release 1.30 onwards cannot find available networks
Date: Mon, 12 Dec 2022 13:01:12 -0600 [thread overview]
Message-ID: <0df6f28d-4a77-dea2-dbf6-c83c6a25b8ae@gmail.com> (raw)
In-Reply-To: <126d2f2b-07ef-fd22-7656-dcd21f3cece0@airpost.net>
Hi Bruno,
>> Just to be clear, you are making sure IWD scans prior to calling 'get-
>> networks' right? i.e. station wlan0 scan?
>
> Yes, but the scan just hangs. I wait a full minute before interrupting the scan with Ctrl+c.
>
This doesn't make much sense. get-networks doesn't scan, it just returns the
cached networks that iwd knows about. If you want to scan, use 'station wlan0
scan'.
And can you elaborate what 'hangs' mean? If there are no networks, then you
should see a "No networks available" print or something similar.
>> But assuming IWD is scanning (or trying) we need to see some debug logs
>> for IWD, and best if you could also get an iwmon trace when IWD starts
>> up and issues scans, and when you call get-networks. More info how to
>> do that here:
>
> No problem. When using latest iwd 2.0, then letting it scan for a minute before interrupting, then running get-networks, here is the iwmon trace:
> https://pastebin.com/h7gHrS2w
>
> And "iwd -d" output:
> https://pastebin.com/2y5hHfWa
>
According to iwmon, there is nothing coming up in the scan results.
Can you run a few scans manually using 'station foo scan'?
Regards,
-Denis
next prev parent reply other threads:[~2022-12-12 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:54 iwd release 1.30 onwards cannot find available networks Bruno Dantas
2022-12-12 17:22 ` James Prestwood
2022-12-12 17:52 ` Bruno Dantas
2022-12-12 18:39 ` Paul Menzel
2022-12-12 18:58 ` Bruno Dantas
2022-12-12 19:01 ` Denis Kenzior [this message]
2022-12-12 19:27 ` Bruno Dantas
2022-12-12 19:38 ` Alvin Šipraga
2022-12-12 20:07 ` Bruno Dantas
2022-12-13 14:42 ` Bruno Dantas
2022-12-13 17:23 ` James Prestwood
2022-12-13 20:15 ` Bruno Dantas
2022-12-13 20:33 ` James Prestwood
2022-12-13 21:02 ` Bruno Dantas
2022-12-12 22:00 ` Denis Kenzior
2022-12-12 23:31 ` Bruno Dantas
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=0df6f28d-4a77-dea2-dbf6-c83c6a25b8ae@gmail.com \
--to=denkenz@gmail.com \
--cc=dantas@airpost.net \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.