From: Jade Lovelace <lists@jade.fyi>
To: Daniel Wagner <wagi@monom.org>
Cc: connman@lists.linux.dev, iwd@lists.linux.dev
Subject: Re: bug: iwd KnownNetworks AutoConnect setting desynchronizes with connman's, breaking auto connect
Date: Fri, 6 Jan 2023 14:04:14 -0500 [thread overview]
Message-ID: <CAFA9we9hh9gORA9EB4Sm7opJi_Rfb6c9L8KJz2rC_1zXnUShfA@mail.gmail.com> (raw)
In-Reply-To: <20230102083554.nindhbg3b4edrgfo@beryllium.lan>
> ConnMan completle relies on iwd to do the right thing, so this question is more
> for the iwd developers. I don't think ConnMan should start fiddling with the
> AutoConnect settings after the initial configuration.
Ah, I see. Based on my look through the iwd code, I also don't see any
evidence for why it's changing, absent someone telling it to do so
over D-Bus, so I wonder what's going on there. If I have it happen
again I'll try to poke around on the iwd side some more to try to get
further information.
Jade
prev parent reply other threads:[~2023-01-06 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 13:39 bug: iwd KnownNetworks AutoConnect setting desynchronizes with connman's, breaking auto connect Jade Lovelace
2023-01-02 8:35 ` Daniel Wagner
2023-01-06 19:04 ` Jade Lovelace [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=CAFA9we9hh9gORA9EB4Sm7opJi_Rfb6c9L8KJz2rC_1zXnUShfA@mail.gmail.com \
--to=lists@jade.fyi \
--cc=connman@lists.linux.dev \
--cc=iwd@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).