From: James Prestwood <prestwoj@gmail.com>
To: Daniel Wagner <wagi@monom.org>,
"VAUTRIN Emmanuel (Canal Plus Prestataire)"
<Emmanuel.VAUTRIN@cpexterne.org>
Cc: "connman@lists.linux.dev" <connman@lists.linux.dev>, iwd@lists.01.org
Subject: Re: [PATCH] iwd: Mark only reachable networks as available
Date: Mon, 24 Jan 2022 13:54:32 -0800 [thread overview]
Message-ID: <cff392fd1d28547d00b24d8f39e43e7741bd7ce4.camel@gmail.com> (raw)
In-Reply-To: <20220123131447.yxpmf5y3ku6cefu4@beryllium.lan>
On Sun, 2022-01-23 at 14:14 +0100, Daniel Wagner wrote:
> On Fri, Jan 21, 2022 at 09:43:04AM +0000, VAUTRIN Emmanuel (Canal
> Plus Prestataire) wrote:
> > > Patch applied. I was not aware that iwd shows networks with no
> > > signal
> > > strength. Thanks!
> >
> > Great news, thank you Daniel!
> > Indeed, it is really rare, but I have noticed that during some full
> > test
> > campaigns, what I have never noticed (during years) with wpa-
> > supplicant.
>
> Alright, let's add the iwd mailing list. Maybe it's a bug, no idea.
I only see one way this could happen, with a select few drivers.
Looks like the kernel has two possible attributes for the signal
stength based on what the driver sets 'signal_type' to. IWD only
handles SIGNAL_DBM, but SIGNAL_UNSPEC is also possible.
What hardware did you see this on? Based on what I'm seeing in the
kernel it is probably one of zd1211rw, at76c50x-usb, adm8211, or
rtl8180?
I'm gonna guess this never got handled because the nl80211 docs say
this attribute is "unspecified units"...
Thanks,
James
> _______________________________________________
> iwd mailing list -- iwd@lists.01.org
> To unsubscribe send an email to iwd-leave@lists.01.org
prev parent reply other threads:[~2022-01-24 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220118125207.1204244-1-Emmanuel.VAUTRIN@cpexterne.org>
2022-01-18 12:56 ` [PATCH] iwd: Mark only reachable networks as available VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-21 7:54 ` Daniel Wagner
2022-01-21 9:43 ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-23 13:14 ` Daniel Wagner
2022-01-24 21:54 ` James Prestwood [this message]
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=cff392fd1d28547d00b24d8f39e43e7741bd7ce4.camel@gmail.com \
--to=prestwoj@gmail.com \
--cc=Emmanuel.VAUTRIN@cpexterne.org \
--cc=connman@lists.linux.dev \
--cc=iwd@lists.01.org \
--cc=wagi@monom.org \
/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;
as well as URLs for NNTP newsgroup(s).