Currently i don't see the IP accounting feature is conman for WiFi Clients.
I like to contribute the implementation for IP Accounting for WiFi Clients. Can somebody provide the procedure to contribute.
I've created an soft access point with connman by enabling tethering.
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = True
TetheringIdentifier = MySSID
TetheringPassphrase = TestPassPhrase
I have 2 clients connected to this access point.
Then I want to scan for other WiFi networks. This fails with -> "Device or resource busy"
Execution of "iwlist scan" find networks at same time. Why it not work with connman scan?
I am working on an open source Arch Arm based audio player. We used to sue
netctl, but that was a bit sloppy and slow. We then investigated
connman/iwd and have been impressed with the simplicity, speed, connection
reliability and also the 'just works' nature of it.
We have noticed that it does not seem to work very well with avahi, though.
Our device advertises itself on the LAN via avahi-daemon and will be
connected in this manner as well. What we notice is that mDNS access is
very slow and unuse-able in most cases. This will not fly for us. Is there
some setting or other incompatibility causing this or is it something
beyond connman that I just cannot figure out?
What I have tried and done:
1) Disabled systemd-resolved and enabled avahi-daemon - This seems to
interfere with avahi even if mDNS is disabled. If I use mDNS enabled with
systemd-resolved and enable the mDNS on the link, I can ping the host and
connection as I have seen in the Firefox Console, I use
/run/connman/resolv.conf as a soft link to /etc/resolv.conf and have as my
nsswitch.conf hosts line this:
hosts: files mdns [NOTFOUND=return] dns
this gives very fast access via ip either v6 or v4, but broken web page
displays via *.local.
2) Enabled systemd-resolved and disabled avahi-daemon. This is slightly
faster to access the device, but the js is still broken and does not
display the page correctly. But this is not a solution as systemd-resolved
does not advertise any services, so it is a non-starter for this particular
project, so any mdns browse does not detect the server.
My next trick it to try systemd-resolved with iwd and see if it is any
Basically: Is there any basic incompatibility with avahi and connman? I see
that connman can turn on mDNS on a per connection basis, but it is only
compatible with systemd-resolved according to this:Connman Config
Is there a reason for this?
I messaged a while back about connecting to a wired 802.1x connection via connman. I was able to make a rudimentary integration using ead as the supplicant. This worked. However, ead has a version requirement for the Linux kernel that is >= 4.20 for EAP-TLS. Unfortunately, the device I am targeting does not have a new enough kernel available. I am investigating the feasibility of using wpa_supplicant for the wired 802.1x connection similar to how it is done for the wifi plugin. The device does not require simultaneous use of WiFi and Ethernet. We are setting SingleConnectedTechnology=true. The device is fixed in place and has no need to roam. It can be configured to connect to WiFi or Ethernet (and hopefully 802.1x).
I have started an integration, using the wifi plugin as a pattern. I am creating a new plugin (and disabling the ethernet one). It looks like the g_supplicant code (and probably wpa_supplicant) only allows one user. Is there a way to switch between the two of them, or is this a no go?
Thanks for any insight!
Is anyone working on iwd scan integration? Currently, if iwd is installed
and wpa_supplicant is not, "connmanctl scan" just hangs and requires ctrl c
to get the prompt back. An error and a return would be useful.
[please no html emails, just plain text emails]
On Wed, May 06, 2020 at 05:26:34PM +0000, Bnà Marco wrote:
> Hi all and thanks in advance to everyone that would like to help me.
> My problem is related to the attempt to automatically establish a BNEP from a board ARM with Yocto and Bluez to a Windows PC.
> The pairing is established successfully but I'm unable to finalize bnep creation with "connmanctl connect bluetooth_mac1_mac2".
> Here is the attached log of the error.
May 4 23:28:18 imx7-var-som bluetoothd: bnep: failed
May 4 23:28:18 imx7-var-som bluetoothd: connect failed Input/output error
May 4 23:28:18 imx7-var-som connmand: ../connman-1.35/plugins/bluetooth.c:pan_connect_cb() network 0x1e58bd8 org.bluez.Error.Failed
From a quick glance, I'd say you need to enable more verbose logging in BlueZ
and may it tells a bit more what's wrong.
Is the bnep module loaded?
I find myself wanting to obtain the connman service configuration when
there is a only 1 or 2 services.
It would be nice if there would be a option to dump all services state,
like connmanctl dump or connmanctl services --all.
Any comments before I would invest time in such a patch?