Send connman mailing list submissions to
connman@lists.01.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
connman-requ...@lists.01.org
You can reach the person managing the list at
connman-ow...@lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Configuration for offline Ethernet connections (Joe Rutledge)
2. Crash when running connmand along iwd (Doron Behar)
3. Re: Configuration for offline Ethernet connections
(Stephen Dawson-Haggerty)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Oct 2018 10:39:14 +0100
From: Joe Rutledge <joe.rutle...@phabrix.com>
To: connman@lists.01.org
Subject: Configuration for offline Ethernet connections
Message-ID: <a1f6dc5e-cb20-8956-45ec-6a5ed3243...@phabrix.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi All,
I'd like to know (and possibly set) the configuration for an Ethernet
connection when the connection is either down or physically not
connected. Is this possible to do via the DBUS API, or must I grind the
config file (in which case is there anything that can help me do that,
such that I don't get left behind when the format changes)?
Thanks,
Joe
------------------------------
Message: 2
Date: Fri, 26 Oct 2018 15:08:19 +0300
From: Doron Behar <doron.be...@gmail.com>
To: connman@lists.01.org
Subject: Crash when running connmand along iwd
Message-ID: <20181026120819.4j3tvicqexfkj...@nuc.doronbehar.com>
Content-Type: text/plain; charset=utf-8
I have connman version 1.36 and iwd version 0.10 installed and every
time I run iwd along with connman it crashes.
Here is part of the output of `journalctl --unit iwd --unit connman`:
Oct 26 15:04:03 NUC systemd[1]: Starting Wireless service...
Oct 26 15:04:03 NUC iwd[3721]: Wireless daemon version 0.10
Oct 26 15:04:03 NUC systemd[1]: Started Wireless service.
Oct 26 15:04:03 NUC iwd[3721]: Wiphy: 0, Name: phy0
Oct 26 15:04:03 NUC iwd[3721]: Bands: 2.4 GHz 5 GHz
Oct 26 15:04:03 NUC iwd[3721]: Ciphers: CCMP TKIP BIP
Oct 26 15:04:03 NUC iwd[3721]: Supported iftypes: ad-hoc station ap
Oct 26 15:04:03 NUC iwd[3721]: No ControlPortOverNL80211 setting, defaulting to
False
Oct 26 15:04:03 NUC connmand[2988]: wlp2s0 {RX} 10603 packets 1056120 bytes
Oct 26 15:04:03 NUC connmand[2988]: wlp2s0 {TX} 420 packets 102727 bytes
Oct 26 15:04:03 NUC connmand[2988]: wlp2s0 {update} flags 36867 <UP>
Oct 26 15:04:03 NUC connmand[2988]: wlp2s0 {newlink} index 3 address
34:13:E8:35:48:E6 mtu 1500
Oct 26 15:04:03 NUC connmand[2988]: wlp2s0 {newlink} index 3 operstate 2 <DOWN>
Oct 26 15:04:03 NUC connmand[2988]: Aborting (signal 11) [/usr/bin/connmand]
Oct 26 15:04:03 NUC connmand[2988]: ++++++++ backtrace ++++++++
Oct 26 15:04:03 NUC connmand[2988]: #0 0x7fc7a3e01e00 in /usr/lib/libc.so.6
Oct 26 15:04:03 NUC connmand[2988]: #1 0x561d85e16ea7 in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #2 0x561d85e1746b in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #3 0x561d85e810d4 in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #4 0x561d85e8235e in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #5 0x561d85e7cd04 in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #6 0x561d85e7cf08 in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #7 0x7fc7a414cd75 in
/usr/lib/libdbus-1.so.3
Oct 26 15:04:03 NUC connmand[2988]: #8 0x561d85e7bed1 in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #9 0x7fc7a41f4271 in
/usr/lib/libglib-2.0.so.0
Oct 26 15:04:03 NUC connmand[2988]: #10 0x7fc7a41f5f89 in
/usr/lib/libglib-2.0.so.0
Oct 26 15:04:03 NUC connmand[2988]: #11 0x7fc7a41f6f62 in
/usr/lib/libglib-2.0.so.0
Oct 26 15:04:03 NUC connmand[2988]: #12 0x561d85df6c8b in /usr/bin/connmand
Oct 26 15:04:03 NUC connmand[2988]: #13 0x7fc7a3dee223 in /usr/lib/libc.so.6
Oct 26 15:04:03 NUC connmand[2988]: +++++++++++++++++++++++++++
With `wpa_supplicant` I don't have this problem but I'd really like to
get rid of it and move to `iwd`.
Thanks.
------------------------------
Message: 3
Date: Fri, 26 Oct 2018 09:54:02 -0700
From: Stephen Dawson-Haggerty <st...@comfyapp.com>
To: joe.rutle...@phabrix.com
Cc: connman@lists.01.org
Subject: Re: Configuration for offline Ethernet connections
Message-ID:
<CAODrDpGUaK97to4ygDbGzvE8sgTj+BXWjESr2_=bo0nbqpu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
There was a discussion a few years ago on this list that I found, and the
consensus seemed to be that you can't do it over dbus (for internal
reasons). The config files would work though; but we've been forced to
just see what it writes out and then edit them. They're pretty simple at
least, and connman watches them for changes so you don't have restart it.
On Fri, Oct 26, 2018 at 2:39 AM Joe Rutledge <joe.rutle...@phabrix.com>
wrote:
> Hi All,
>
> I'd like to know (and possibly set) the configuration for an Ethernet
> connection when the connection is either down or physically not
> connected. Is this possible to do via the DBUS API, or must I grind the
> config file (in which case is there anything that can help me do that,
> such that I don't get left behind when the format changes)?
>
> Thanks,
>
> Joe
>
> _______________________________________________
> connman mailing list
> connman@lists.01.org
> https://lists.01.org/mailman/listinfo/connman
>
--
*Steve Dawson-Haggerty* | CTO and Co-Founder
(631) 741-3378
comfyapp.com <https://www.comfyapp.com/?home>
Have you heard about Comfy Insights <http://comfy.us/insights-ef> yet?
Follow us on:
<https://www.linkedin.com/company/comfy-by-building-robotics->
<https://twitter.com/comfyapp> <https://www.facebook.com/comfyapp/>
<https://www.instagram.com/comfyapp/>
[image: Comfy Logo] <https://www.comfyapp.com/?home>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20181026/f229345c/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 36, Issue 22
***************************************
