Send connman mailing list submissions to
[email protected]
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
[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. Re: Failed to create storage directory: No such file or
directory (JH)
2. Re: crash of connmand ([email protected])
3. Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented ([email protected])
4. Re: crash of connmand (Daniel Wagner)
5. Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented (Daniel Wagner)
6. Re: documentation seems off: configure missing (Daniel Wagner)
7. Re: documentation seems off: configure missing (Daniel Wagner)
8. Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 28 Mar 2019 09:06:03 +1100
From: JH <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: Jussi Laakkonen <[email protected]>, connman
<[email protected]>
Subject: Re: Failed to create storage directory: No such file or
directory
Message-ID:
<CAA=hcWT+Pq-4P-Zwhz9Y=HpEPh2-quvXsCj01pA=4ctrxna...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
> Yocto is probably using an older version of ConnMan. You might want to
> update the corresponding recipe.
Will do, Thanks Daniel.
- jupiter
------------------------------
Message: 2
Date: Wed, 27 Mar 2019 23:47:56 +0100
From: <[email protected]>
To: [email protected]
Subject: Re: crash of connmand
Message-ID: <20190327234756.6d0c61a7@huit>
Content-Type: text/plain; charset=US-ASCII
Hi,
I hope I compiled the git version correctly (see my "documentation
seems to be off" mail)...
But using it, when restarting it did NOT crash anymore!
Thanks!!
Tormen
--
On Wed, 27 Mar 2019 20:58:00 +0100
<[email protected]> wrote:
> Hi :)
>
> On Wed, 27 Mar 2019 20:08:34 +0100
> Daniel Wagner <[email protected]> wrote:
>
> > On 3/27/19 6:47 PM, [email protected] wrote:
> > > Please find the output of connmand -n -d here:
> > > http://sprunge.us/zyKJkl
> >
> > If this is ConnMan version 1.36, then I am not surprised iwd
> > doesn't work. You need at least one patch which fixes the crash.
> > Try current HEAD and see if it still crashes.
>
> Hun. Oops, I fear it is:
>
> community/connman 1.36-2 [installed]
> Intel's modular network connection manager
>
> (archlinux... but there is no newer release yet)
>
> I'll try the git version and let you know.
>
> Tormen
>
> >
> > Thanks,
> > Daniel
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Message: 3
Date: Thu, 28 Mar 2019 00:16:50 +0100
From: <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented
Message-ID: <20190328001650.3766aa7d@huit>
Content-Type: text/plain; charset=US-ASCII
Hi again,
please note the below was tested on an archlinux machine using:
aur/connman-git 1.36.r164.gb7ddedc4-1 (+13 0.53%) (Installed)
core/wpa_supplicant 2:2.6-2 (914.5 KiB 4.1 MiB) (Installed)
Well, it /seems/ that the wpa_supplicant has the same problems than the
community/iwd 0.14-1 (333.5 KiB 1.1 MiB) (Installed)
I had tested and ran tests before, when starting this thread.
Here is what I did:
I deactivated and masked iwd.service, I activated and started
wpa_supplicant.service.
I then set a journalctl cursor --> see journalctl.log
-->
http://sprunge.us/pXxKPU
I then started:
CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d
see 2019-03-27_connmand_-n_-d___wit_wpa_supplicant.log
-->
http://sprunge.us/IoSfR5
And issued a bunch of connmanctl commands, see cli.txt
-->
http://sprunge.us/hJbZV3
Please let me know if I missed anything or if the above seems correct.
And if there is anything I can do to assist further.
Thanks again for *any* hint to help me get past this.
Tormen
--
On Wed, 27 Mar 2019 21:00:20 +0100
<[email protected]> wrote:
> Hi,
>
> Thanks again!
>
> On Wed, 27 Mar 2019 20:05:32 +0100
> Daniel Wagner <[email protected]> wrote:
>
> > On 3/27/19 6:41 PM, [email protected] wrote:
> > > Is there an alternative (agent) that I could be using?
> >
> > Not sure what you mean with agent in this. We have two WiFi
> > 'drivers', one is wpa_supplicant and the other is iwd.
> >
> > > I am wondering how do others do? (how do you do?): Why is no one
> > > else complaining?
> >
> > Don't know. But are you sure you are use latest ConnMan?
>
> community/connman 1.36-2 [installed]
> Intel's modular network connection manager
> (archlinux,
> https://git.kernel.org/pub/scm/network/connman/connman.git/
> shows 1.36 as latest release)
>
> > > Is it because they all use wpa_supplicant?
> >
> > Again don't know. But likely.
>
> But than that means that wpa_supplicant should/could work better?
>
> Maybe I should retry this one then...
>
> Tormen
>
> >
> > > Or is there another possible agent? (systemd's netctl
> > > maybe ??)
> >
> > This is something different. An agent in ConnMan terminology is the
> > a D-Bus client which will be called by ConnMan. It's a kind of RPC.
> >
> > > And how does Jolla do?
> >
> > They have their own UI and are using wpa_supplicant from what I
> > know. But you can check this. All open source :)
> >
> > Thanks,
> > Daniel
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Message: 4
Date: Thu, 28 Mar 2019 08:20:06 +0100
From: Daniel Wagner <[email protected]>
To: [email protected], [email protected]
Subject: Re: crash of connmand
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 3/27/19 11:47 PM, [email protected] wrote:
> I hope I compiled the git version correctly (see my "documentation
> seems to be off" mail)...
>
> But using it, when restarting it did NOT crash anymore!
That was easy :)
------------------------------
Message: 5
Date: Thu, 28 Mar 2019 08:35:09 +0100
From: Daniel Wagner <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
On 3/28/19 12:16 AM, [email protected] wrote:
> Hi again,
>
> please note the below was tested on an archlinux machine using:
> aur/connman-git 1.36.r164.gb7ddedc4-1 (+13 0.53%) (Installed)
> core/wpa_supplicant 2:2.6-2 (914.5 KiB 4.1 MiB) (Installed)
>
> Well, it /seems/ that the wpa_supplicant has the same problems than the
> community/iwd 0.14-1 (333.5 KiB 1.1 MiB) (Installed)
> I had tested and ran tests before, when starting this thread.
>
> Here is what I did:
>
> I deactivated and masked iwd.service, I activated and started
> wpa_supplicant.service.
>
> I then set a journalctl cursor --> see journalctl.log
> -->
> http://sprunge.us/pXxKPU
>
> I then started:
> CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d
> see 2019-03-27_connmand_-n_-d___wit_wpa_supplicant.log
> -->
> http://sprunge.us/IoSfR5
Alright, it doesn't depend on iwd or wpa_supplicant. So let's see if
rfkill is enabled:
Mar 27 23:59:28 huit connmand[22082]: src/rfkill.c:rfkill_process()
Mar 27 23:59:28 huit connmand[22082]: src/rfkill.c:rfkill_process() idx
0 type 1 op 0 soft 0 hard 0
Mar 27 23:59:28 huit connmand[22082]:
src/technology.c:__connman_technology_add_rfkill() index 0 type 3 soft 0
hard 0
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_get()
type 3
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_find()
type 3
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_get()
technology (nil) driver 0x561c8e6662a0
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_get()
technology (nil) driver 0x561c8e666740
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_load()
technology 0x561c8f69e6c0
Mar 27 23:59:28 huit connmand[22082]: src/technology.c:technology_get()
technology 0x561c8f69e6c0 WiFi
Mar 27 23:59:28 huit connmand[22082]:
src/technology.c:technology_apply_rfkill_change() technology
0x561c8f69e6c0 --> 0/0 vs 0/0
This looks okay, rfkill doesn't tell us to block anything. So what is
the 'iw list' tool telling you?
> And issued a bunch of connmanctl commands, see cli.txt
> -->
> http://sprunge.us/hJbZV3
Ah, okay the agent part needs an update. Thanks for the report. Added to
the TODO list.
This shouldn't be a problem right now.
Thanks,
Daniel
------------------------------
Message: 6
Date: Thu, 28 Mar 2019 08:39:06 +0100
From: Daniel Wagner <[email protected]>
To: [email protected], connman <[email protected]>
Subject: Re: documentation seems off: configure missing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
> If so, could you provide me with the autoconf line to run?
You need to distinguish between the release version (tar file) and the
git tree. The release version contains the configure script. This will
be auto generated during the release steps.
If you want to build the git tree you need to generate the configure
script via the autotools. See bootstrap-configure script for this.
Thanks,
Daniel
------------------------------
Message: 7
Date: Thu, 28 Mar 2019 08:41:06 +0100
From: Daniel Wagner <[email protected]>
To: [email protected], connman <[email protected]>
Subject: Re: documentation seems off: configure missing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 3/27/19 9:38 PM, [email protected] wrote:
> Ok, I got it to work by preceeding the ./configure call with:
>
> autoreconf --install
> autoconf
>
> see also here:
>
> http://sprunge.us/JgiryH
>
> Is that right?
The bootstrap script contains following lines
#!/bin/sh
aclocal && \
autoheader && \
libtoolize --automake --copy --force && \
automake --add-missing --copy && \
autoconf
The autohell tools are hard to grasp, so autoreconf --install &&
autoconf is good enough... who knows :)
------------------------------
Message: 8
Date: Thu, 28 Mar 2019 10:50:54 +0100
From: <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented
Message-ID: <20190328105054.3479e2d9@huit>
Content-Type: text/plain; charset=US-ASCII
Hi,
On Thu, 28 Mar 2019 08:35:09 +0100
Daniel Wagner <[email protected]> wrote:
> Alright, it doesn't depend on iwd or wpa_supplicant. So let's see if
> rfkill is enabled:
>
> Mar 27 23:59:28 huit connmand[22082]: src/rfkill.c:rfkill_process()
> Mar 27 23:59:28 huit connmand[22082]: src/rfkill.c:rfkill_process()
> idx 0 type 1 op 0 soft 0 hard 0
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:__connman_technology_add_rfkill() index 0 type 3
> soft 0 hard 0
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_get() type 3
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_find() type 3
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_get() technology (nil) driver
> 0x561c8e6662a0 Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_get() technology (nil) driver
> 0x561c8e666740 Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_load() technology 0x561c8f69e6c0
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_get() technology 0x561c8f69e6c0 WiFi
> Mar 27 23:59:28 huit connmand[22082]:
> src/technology.c:technology_apply_rfkill_change() technology
> 0x561c8f69e6c0 --> 0/0 vs 0/0
>
> This looks okay, rfkill doesn't tell us to block anything. So what is
> the 'iw list' tool telling you?
... the list was EMPTY :((( really sorry about that!!!
As my laptop does not have a wlan hardware switch, I am removing the
wlan kernel module to save energy.
I was always wondering if this is the best way to achieve that.
I think I asked the intel guys once and they had confirmed that this
works... but I can't clearly remember anymore...
So the wlan-modules where not loaded ;)
Funnily the "technologies" command still said:
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Which is why I did not notice / think about it... because I thought
Powered means, well there is a wifi device and it's not rfkilled ...
Would be nice if the technologies command could list the number of
devices in each category that where found, no ?
Anyways: I am REAYLLY sorry!! And promise to try to make sure that this
won't happen again (iw list is easy enough to type ;))!!
So, here is what I did:
* ran a 'my-set wlan-on' (my command to disable / enable wifi)
((really simply handles rfkill + kernel modules you'll see the
commands ran below))
* checked with 'ip link', 'iw list': all good
* stopped wpa_supplicant, connman.service,
connman-vpn.service.
* exited cmst
* set the journalctl cursor and recordered all of the
following. Here is the resulting journalctl.log:
http://sprunge.us/QIenau
* started the wpa_supplicant.service
* ran: CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d
&>/root/connmand_-n_-d___wit_wpa_supplicant.log
-->
http://sprunge.us/PfwklC
* started cmst: Rescan button grayed out
* entered connmanctl, ran some commands, added a iw list and rfkill
-->
http://sprunge.us/vLh7Ve
It went further, but did not work!
- see the log: wifi scan gave a "no carrier" ?
* then I killed the connmand
* exited cmst
* systemctl restart connman.service
* started cmst
and /now/ cmst had a "Rescan" button and showed wireless networks
* ran my-set wlan-off
--> the rescan button grayed out in the still running cmst
* ran my-set wlan-on
--> the rescan button STAYED grayed out :(
* exited cmst
* restarted cmst
--> the rescan button was STILL grayed out !! :((
* systemctl restart connman.service
* started cmst
--> the rescan button was not grayed out anymore
So it seems to me that connman.service might not handle well the fact
that I remove and then add wlan kernel modules??
So I ran one more test to collect the connmand log for you while I
unload reload the wifi kernel modules.
It turns out that connman needs an extra push (manually) by
issuing connmanctl disable wifi, connmanctl enable wifi after reloading
the kernel modules, before connmanctl scan wifi works.
Even though connmanctl showed in "technologies" that wifi was Powered
off (when kernel modules unloaded) and showed it as Powered on after
kernel modules were reloaded!
Which seems to me to be a bug in connmand.
- But see for yourself, here is what I did:
* wlan is ON, iw list shows, rfkill: shows unblocked
* I kept cmst running (it showed the "Rescan" button + wlan
networks) this time to see if he handles well the restart of
connmand and it actually did :)
* systemctl stop connman.service
* systemctl stop wpa_supplicant.service
* set a journalctl cursor (as a marker in journalctl)
recorded all of the following
-->
http://sprunge.us/0HWp0j
* systemctl start wpa_supplicant.service
* CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d
-->
http://sprunge.us/jrXoWQ
* checked in cmst: it showed still "Rescan" and wlan-networks
* issued a bunch of connmanctl commands:
-->
http://sprunge.us/2OdDqz
Ok, I stop here :)
Tormen
> > And issued a bunch of connmanctl commands, see cli.txt
> > -->
> > http://sprunge.us/hJbZV3
>
> Ah, okay the agent part needs an update. Thanks for the report. Added
> to the TODO list.
>
> This shouldn't be a problem right now.
>
> Thanks,
> Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 41, Issue 30
***************************************
