connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Jade Lovelace <lists@jade.fyi>
Cc: connman@lists.linux.dev, iwd@lists.linux.dev
Subject: Re: bug: 802.1x configuration is not turned into an iwd KnownNetwork
Date: Mon, 2 Jan 2023 09:29:41 +0100	[thread overview]
Message-ID: <20230102082941.rhlb4dfwzhkvmav7@beryllium.lan> (raw)
In-Reply-To: <CAFA9we_ArzwtDidQkEQTL-vEPC2GGnRTqZB7jbx=UZ-R1MkzoA@mail.gmail.com>

On Wed, Dec 28, 2022 at 02:16:03PM +0100, Jade Lovelace wrote:
> I just set up an 802.1x configuration with Connman and iwd and it
> seems that Connman is not telling iwd about its network configuration
> files and turning them into iwd KnownNetworks.
> 
> When I create a config file for a network in /var/lib/connman for an
> 802.1x network, then try to connect to it, it will get stuck in
> "association":
> 
> connmanctl> services wifi_9cb6d0f7daaf_7075626c6963726f616d_managed_ieee8021x
> /net/connman/service/wifi_9cb6d0f7daaf_7075626c6963726f616d_managed_ieee8021x
>   Type = wifi
>   Security = [ ieee8021x ]
>   State = association
>   Strength = 56
>   Favorite = True
>   Immutable = True
>   AutoConnect = True
>   Name = publicroam
> 
> I had a think about this and concluded it was probably that connman
> didn't create the known network on the iwd side, which I confirmed by
> manually creating /var/lib/iwd/publicroam.8021x with the correct
> configuration, solving the issue. I suspect that if I was using some
> UI for connman that creates networks via D-Bus rather than via
> configuration files, it might work, but the fact that the connman
> config files don't apply to iwd is inconsistent with the behaviour
> under wpa_supplicant.

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.

> I am using connman-1.41 on NixOS.
> 
> Here is my config "publicroam.config":
> 
> [service_publicroam]
> Type=wifi
> Name=publicroam
> EAP=peap
> Phase2=MSCHAPV2
> Identity=<REDACTED>
> Passphrase=<REDACTED>
> 
> Here is the relevant connman log (with iwd debug logging on):
> 
> Dec 28 13:24:34 snowflake connmand[266352]:
> plugins/iwd.c:object_added() net.connman.iwd.Network
> /net/connman/iwd/0/5/7075626c6963726f616d_8021x
> Dec 28 13:24:34 snowflake connmand[266352]:
> plugins/iwd.c:create_network() device /net/connman/iwd/0/5 name
> 'publicroam' type 8021x connected 0 known_network (null)
> Dec 28 13:24:34 snowflake connmand[266352]:
> plugins/iwd.c:station_property_change() /net/connman/iwd/0/5 scanning
> 0
> Dec 28 13:24:34 snowflake connmand[266352]:
> plugins/iwd.c:station_property_change() /net/connman/iwd/0/5 scanning
> 1
> Dec 28 13:24:34 snowflake connmand[266352]: plugins/iwd.c:ordered_networks_cb()
> <<< REDACTED >>>
> Dec 28 13:24:55 snowflake connmand[266352]: EAP type has not been
> found. Most likely ConnMan is not able to find a configuration for
> given 8021X network. Check SSID or Name match with the network name.
> 
> ^^^^^^^ ------ This was when I tried to ask it to connect prior to
> configuring it
> 
> <<< REDACTED >>>
> Dec 28 13:27:04 snowflake connmand[266352]: Adding configuration publicroam
> Dec 28 13:27:04 snowflake connmand[266352]: Adding service
> configuration publicroam
> 
> ^^^^^^^ ------ Then I added a configuration here
> 
> Dec 28 13:27:04 snowflake connmand[266352]:
> plugins/iwd.c:cm_network_connect_cb()
> /net/connman/iwd/0/5/7075626c6963726f616d_8021x connect failed:
> net.connman.iwd.NotConfigured
> 
> ^^^^^^^ ------ But connecting fails
> 
> Jade
> 

  reply	other threads:[~2023-01-02  8:29 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 [this message]
2023-01-03 15:20   ` Denis Kenzior
2023-01-16  7:31     ` Daniel Wagner

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=20230102082941.rhlb4dfwzhkvmav7@beryllium.lan \
    --to=wagi@monom.org \
    --cc=connman@lists.linux.dev \
    --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 NNTP newsgroup(s).