From: Daniel Wagner <wagi@monom.org>
To: Denis Kenzior <denkenz@gmail.com>
Cc: Jade Lovelace <lists@jade.fyi>,
connman@lists.linux.dev, iwd@lists.linux.dev
Subject: Re: bug: 802.1x configuration is not turned into an iwd KnownNetwork
Date: Mon, 16 Jan 2023 08:31:28 +0100 [thread overview]
Message-ID: <20230116073128.u6oazqb5o3vvzp7b@beryllium.lan> (raw)
In-Reply-To: <cbf0c602-a854-bc24-a7ae-0eec05be86ec@gmail.com>
Hi Denis
On Tue, Jan 03, 2023 at 09:20:46AM -0600, Denis Kenzior wrote:
> > ConnMan interacts with iwd only via the D-Bus interface. I can't remember that
> > we added any code to do any provisioning in iwd (also a quick glance over the
> > iwd plugin code doesn't ring any bell). Also I couldn't find any API doc in iwd
> > which covers this topic. So I don't know if it is currently possible to
> > provision iwd via the D-Bus API.
>
> There's no way to provision 802.1x networks over D-Bus. However, connman
> can write provisioning files to iwd's storage dir (/var/lib/iwd typically)
> and iwd will pick these up. This is what the NM backend does.
Thanks for the feedback. ConnMan has also no D-Bus API for provisioning a 802.1x
network. The user has to provide a config file for ConnMan for this use case as
too.
Not really sold on the idea to add code to copy over the config settings.
Thanks,
Daniel
prev parent reply other threads:[~2023-01-16 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 13:16 bug: 802.1x configuration is not turned into an iwd KnownNetwork Jade Lovelace
2023-01-02 8:29 ` Daniel Wagner
2023-01-03 15:20 ` Denis Kenzior
2023-01-16 7:31 ` Daniel Wagner [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=20230116073128.u6oazqb5o3vvzp7b@beryllium.lan \
--to=wagi@monom.org \
--cc=connman@lists.linux.dev \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=lists@jade.fyi \
/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).