Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Why is dbus mandatory (Louis Rannou)
2. DBus.Error AccessDenied (chaitanya cherukuri)
3. Re: MTU (Daniel Wagner)
4. Re: Why is dbus mandatory (Daniel Wagner)
5. Re: DBus.Error AccessDenied (Daniel Wagner)
----------------------------------------------------------------------
Date: Fri, 14 Feb 2020 15:56:00 +0100
From: Louis Rannou <[email protected]>
Subject: Why is dbus mandatory
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hi,
I wonder why is dbus mandatory ? Is it just for the client and plugins
or is it part of the core ?
We would like to use connman but we'd like it to be as small as
possible. Could you say it's possible to get rid of dbus ?
I looked for technical documentation such as architecture, but I could
not find any.
Thanks
Louis
------------------------------
Date: Fri, 14 Feb 2020 11:04:31 -0500
From: chaitanya cherukuri <[email protected]>
Subject: DBus.Error AccessDenied
To: [email protected]
Message-ID:
<calvd-wnxma0mvqf_eq1euskigr-1bvunps-afpce+p75r__...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hello,
I'm using connman version 1.37 in YOCTO version 2.5.3(pyro). I get the
following error message when user other than root try to access
connman interface
Device fault detected : org.freedesktop.DBus.Error.AccessDenied:
Rejected send message, 2 matched rules; type="method_call",
sender=":1.7" (uid=1001 pid=636 comm="python /opt/yocto
/bin/appserver/server.pyc ") interface="net.connman.Manager"
member="GetTechnologies" error name="(unset)" requested_reply="0"
destination=":1.0" (uid=0 pid=396 comm="/usr/sbin/connmand ")
In order to make it work, I have to modify the rules(see below)
connman.conf in /usr/shar/dbus-1/system.d/connman.conf,
</policy>
<policy context="default">
<allow send_destination="net.connman"/>
</policy>
</busconfig>
Is this the correct way to handle this? How do I integrate this change
during the build time?
Thanks,
Chaitanya
------------------------------
Date: Fri, 14 Feb 2020 18:00:16 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: MTU
To: Damien LEFEVRE <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Damien,
On Wed, Feb 12, 2020 at 12:07:08PM +0200, Damien LEFEVRE wrote:
> I wish there would be a way to configure the default IP settings per
> adapter name instead of MAC address to have a robust method.
BTW, there is also the option to match on the device name, see
a719719e1264 ("config: Add support matching on device name for
provisioning")
> The provision
> approach doesn't work for me because I cannot change the settings, unless I
> have missed something completely =)
Have you seen my patch posted on the ml about adding the MTU D-Bus API?
Thanks,
Daniel
------------------------------
Date: Fri, 14 Feb 2020 18:27:53 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Why is dbus mandatory
To: Louis Rannou <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Louis,
On Fri, Feb 14, 2020 at 03:56:00PM +0100, Louis Rannou wrote:
> I wonder why is dbus mandatory ? Is it just for the client and plugins or is
> it part of the core ?
The D-Bus APIs are part of the core. It's not an optional.
> We would like to use connman but we'd like it to be as small as possible.
> Could you say it's possible to get rid of dbus ?
Sure it's possible to get rid of the D-Bus code, it's just work. But
this would be something you have to do own your own.
> I looked for technical documentation such as architecture, but I could not
> find any.
It's a design decision. The way to control and talk to ConnMan is via
D-Bus.
Is your target platform/device just using WiFi? If so you could use
iwd directly for this. This would shrink the footprint considerable,
even though you still need D-Bus.
IIRC, the OpenWRT project has a network manager which is not depending
on D-Bus and is designed for small devices.
Thanks,
Daniel
------------------------------
Date: Fri, 14 Feb 2020 18:32:03 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: DBus.Error AccessDenied
To: chaitanya cherukuri <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi,
On Fri, Feb 14, 2020 at 11:04:31AM -0500, chaitanya cherukuri wrote:
> In order to make it work, I have to modify the rules(see below)
> connman.conf in /usr/shar/dbus-1/system.d/connman.conf,
> </policy>
> <policy context="default">
> <allow send_destination="net.connman"/>
> </policy>
> </busconfig>
>
> Is this the correct way to handle this?
It looks okay. You need to configure D-Bus correctly. I am using the
D-Bus configuration provided in the ConnMan sources, which seems to
work for me.
> How do I integrate this change during the build time?
Maybe the Yocto mailing list can help you here.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 16
***************************************
