3:04 p.m.
Hello,
I started to use connman 1.37 with YOCTO (pyro)
I observed the connman 1.37 source code that YOCTO uses is different
from the source code in
https://kernel.googlesource.com/pub/scm/network/connman/connman/.
To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
I enabled the wlan0 interface but did not connect to any network. I
see my log if filled with these messages:
wlcore: firmware booted (Rev 6.3.10.0.142)
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlcore: down
I didn't see this behavior on connman 1.35 version,
Thanks,
Chaitanya
--
--
Chaitanya
8:58 a.m.
Hi Chaitanya,
On Thu, Jan 30, 2020 at 04:04:55PM -0500, chaitanya cherukuri wrote:
I observed the connman 1.37 source code that YOCTO uses is different
from the source code in
https://kernel.googlesource.com/pub/scm/network/connman/connman/.
To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
That is strange. I checkout out the above repository and find the file:
$ find -name ipv4ll.c
./gdhcp/ipv4ll.c
I also cheked Yocto's ConnMan recipe:
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivit...
There are no funky changes or patches on top. Not sure how ipv4ll.c
get's lost. Do you have some sort of license clearing robot removing
files in post processing? Anyway, the upstream mirror looks ok.
I enabled the wlan0 interface but did not connect to any network. I
see my log if filled with these messages:
wlcore: firmware booted (Rev 6.3.10.0.142)
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlcore: down
I didn't see this behavior on connman 1.35 version,
wlcore message is the driver message. This is not from ConnMan. Did
you upgrade the complete Yocto distribution? If so, did you upgrade
the kernel and wpa_supplicant as well? I ask because I don't think
ConnMan is making troubles. It's more likely an upgrade of the kernel
or wpa_supplicant breaks your setup.
Enable the debug level on ConnMan side by setting the environment
variable CONNMAN_SUPPLICANT_DEBUG=1 and enabling the connman log
'connmand -n -d'. Furthermore, there is iwmon from the iwd project
which is an excellent debugging tool for looking at the kernel nl80211
interface. You can monitor all the traffic between wpa_supplicant and
the kernel.
Thanks,
Daniel
5:59 p.m.
Hi Daniel,
On Sun, Feb 2, 2020, 9:58 AM Daniel Wagner <wagi(a)monom.org> wrote:
Hi Chaitanya,
On Thu, Jan 30, 2020 at 04:04:55PM -0500, chaitanya cherukuri wrote:
> I observed the connman 1.37 source code that YOCTO uses is different
> from the source code in
> https://kernel.googlesource.com/pub/scm/network/connman/connman/.
> To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
That is strange. I checkout out the above repository and find the file:
$ find -name ipv4ll.c
./gdhcp/ipv4ll.c
I also cheked Yocto's ConnMan recipe:
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivit...
There are no funky changes or patches on top. Not sure how ipv4ll.c
get's lost. Do you have some sort of license clearing robot removing
files in post processing? Anyway, the upstream mirror looks ok.
I don't have any robot or post processing scripts to remove the files.
Thank you for confirming that upstream mirror is ok.
I enabled the wlan0 interface but did not connect to any network. I
> see my log if filled with these messages:
> wlcore: firmware booted (Rev 6.3.10.0.142)
> IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> wlcore: down
>
> I didn't see this behavior on connman 1.35 version,
wlcore message is the driver message. This is not from ConnMan. Did
you upgrade the complete Yocto distribution? If so, did you upgrade
the kernel and wpa_supplicant as well? I ask because I don't think
ConnMan is making troubles. It's more likely an upgrade of the kernel
or wpa_supplicant breaks your setup.
Enable the debug level on ConnMan side by setting the environment
variable CONNMAN_SUPPLICANT_DEBUG=1 and enabling the connman log
'connmand -n -d'. Furthermore, there is iwmon from the iwd project
which is an excellent debugging tool for looking at the kernel nl80211
interface. You can monitor all the traffic between wpa_supplicant and
the kernel.
I didn't upgrade the complete Yocto distribution. I only upgraded connman
and wpa_supplicant. I figured that the older version of wpa_supplicant was
also installed and was causing the problems. I will use iwmon for
monitoring traffic between wpa_supplicant and kernel. Can I use
wpa_supplicant version 2.6 for both connman 1.36? Can I replace
wpa_supplicant with iwd for scanning?
Thanks,
Daniel
3:24 a.m.
I didn't upgrade the complete Yocto distribution. I only
upgraded connman
and wpa_supplicant. I figured that the older version of wpa_supplicant was
also installed and was causing the problems.
No surprise there.
I will use iwmon for monitoring traffic between wpa_supplicant and
kernel. Can I use wpa_supplicant version 2.6 for both connman 1.36?
wpa_supplicant 2.6 is really old and I woulnd't recommend it. Go for
the latest released version. Same goes for ConnMan.
Can I replace wpa_supplicant with iwd for scanning?
No, either you use wpa_supplicant or iwd. You can't use both at the
same time.
Thanks,
Daniel
12:19 p.m.
On Thu, Feb 6, 2020 at 4:24 AM Daniel Wagner <wagi(a)monom.org> wrote:
> I didn't upgrade the complete Yocto distribution. I only
upgraded
connman
> and wpa_supplicant. I figured that the older version of wpa_supplicant
was
> also installed and was causing the problems.
No surprise there.
> I will use iwmon for monitoring traffic between wpa_supplicant and
> kernel. Can I use wpa_supplicant version 2.6 for both connman 1.36?
wpa_supplicant 2.6 is really old and I woulnd't recommend it. Go for
the latest released version. Same goes for ConnMan.
> Can I replace wpa_supplicant with iwd for scanning?
No, either you use wpa_supplicant or iwd. You can't use both at the
same time
if I have both installed, do I need to create any services files, so
connman uses iwd to connect and scan wireless networks instead of
wpa_supplicant?
does iwd work connman version 1.36 or do I need to user 1.37?
I observed the connman 1.37 source code that YOCTO uses is different
from the source code in
https://kernel.googlesource.com/pub/scm/network/connman/connman/.
To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
That is strange. I checkout out the above repository and find the file:
$ find -name ipv4ll.c
./gdhcp/ipv4ll.c
I also cheked Yocto's ConnMan recipe:
Sorry to get back to the source code difference. I cloned the master branch
from https://git.kernel.org/pub/scm/network/connman/connman.git/ and
compared with connman-1.37 ( from
https://git.kernel.org/pub/scm/network/connman/connman.git/refs/) which are
different. Is that what you expect>
Thanks,
Daniel
Thanks,
Chaitanya
12:31 p.m.
On Thu, Feb 06, 2020 at 01:19:05PM -0500, chaitanya cherukuri wrote:
> No, either you use wpa_supplicant or iwd. You can't use both
at the
> same time
if I have both installed, do I need to create any services files, so
connman uses iwd to connect and scan wireless networks instead of
wpa_supplicant?
Starting wpa_supplicant or iwd is done by something like
systemd. ConnMan doesn't start them. ConnMan monitors the D-Bus and as
soon it finds wpa_supplicant on iwd on the bus it starts using them.
Yes, so install iwd and start/stop it with systemd or the rc.d scripts
if this is what you have on your embedded system.
does iwd work connman version 1.36 or do I need to user 1.37?
Basically you want ConnMan the not yet released 1.38 with the latest
iwd release (currently 1.4)
> I observed the connman 1.37 source code that YOCTO uses is
different
> from the source code in
> https://kernel.googlesource.com/pub/scm/network/connman/connman/.
> To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
That is strange. I checkout out the above repository and find the file:
$ find -name ipv4ll.c
./gdhcp/ipv4ll.c
I also cheked Yocto's ConnMan recipe:
Sorry to get back to the source code difference. I cloned the master branch
from https://git.kernel.org/pub/scm/network/connman/connman.git/ and
compared with connman-1.37 ( from
https://git.kernel.org/pub/scm/network/connman/connman.git/refs/) which are
different. Is that what you expect>
Ah I think I understand your problem. The git tree is not identically
with the tar.gz file. The git tree contains really only those files
which are 'source'. Any file which can be generated is not part of the
git tree. So in order to build the git tree you need some 'special'
tools like autoheader on your system. The tar.gz contains generated
files and therefore you don't have so many build dependencies as the
git tree.
Thanks,
Daniel
3:26 p.m.
Hi Daniel,
On Thu, Feb 6, 2020 at 1:31 PM Daniel Wagner <wagi(a)monom.org> wrote:
On Thu, Feb 06, 2020 at 01:19:05PM -0500, chaitanya cherukuri wrote:
> > No, either you use wpa_supplicant or iwd. You can't use both at the
> > same time
>
> if I have both installed, do I need to create any services files, so
> connman uses iwd to connect and scan wireless networks instead of
> wpa_supplicant?
Starting wpa_supplicant or iwd is done by something like
systemd. ConnMan doesn't start them. ConnMan monitors the D-Bus and as
soon it finds wpa_supplicant on iwd on the bus it starts using them.
Yes, so install iwd and start/stop it with systemd or the rc.d scripts
if this is what you have on your embedded system.
> does iwd work connman version 1.36 or do I need to user 1.37?
Basically you want ConnMan the not yet released 1.38 with the latest
iwd release (currently 1.4)
> > I observed the connman 1.37 source code that YOCTO uses is
different
> > from the source code in
> > https://kernel.googlesource.com/pub/scm/network/connman/connman/.
> > To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
>
> That is strange. I checkout out the above repository and find the
file:
>
> $ find -name ipv4ll.c
> ./gdhcp/ipv4ll.c
>
> I also cheked Yocto's ConnMan recipe:
> Sorry to get back to the source code difference. I cloned the master
branch
> from https://git.kernel.org/pub/scm/network/connman/connman.git/ and
> compared with connman-1.37 ( from
> https://git.kernel.org/pub/scm/network/connman/connman.git/refs/) which
are
> different. Is that what you expect>
Ah I think I understand your problem. The git tree is not identically
with the tar.gz file. The git tree contains really only those files
which are 'source'. Any file which can be generated is not part of the
git tree. So in order to build the git tree you need some 'special'
tools like autoheader on your system. The tar.gz contains generated
files and therefore you don't have so many build dependencies as the
git tree.
Thank you for the clarification.
Thanks,
Daniel
--
--
Chaitanya
357
days inactive
364
days old
6 comments
2 participants
participants (2)
-
chaitanya cherukuri -
Daniel Wagner