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. Re: Wrong date (Daniel Wagner)
2. Re: Why connmand consume such higher CPU resource? (Daniel Wagner)
3. Re: Connman 1.35 authentication timeout and alternate configuration for
wired interface
(chaitanya cherukuri)
4. Re: lost busybox mysteriously (JH)
5. Doesn't connect to strongest wifi (Torsten Wörtwein)
6. 4G LTE connection stability with USB voltage requirement (JH)
----------------------------------------------------------------------
Date: Sun, 26 Jan 2020 12:44:08 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Wrong date
To: JH <[email protected]>, Yocto discussion list
<[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi JH,
On 25.01.20 23:15, JH wrote:
> I build the image from Yocto thud and running it in imx6, usually I
> got right the date, but today I got a weird wrong date:
>
> # date
> Wed Jan 15 08:13:14 UTC 2020
ConnMan will do a NTP query if a time server is reachable. The wrong
date indicates that this has not (yet) happen.
> What could cause that problem and how to fix it? The WiFi also got a
> wrong IP address 169.254.124.128, it was because failed DHCP response,
ConnMan has assigned an IPv4 link local address, so the DHCP request has
failed and therefore it's likely the NTP query has failed as well.
Thanks,
Daniel
------------------------------
Date: Sun, 26 Jan 2020 15:09:25 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Why connmand consume such higher CPU resource?
To: JH <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi JH,
On Sun, Jan 26, 2020 at 05:13:34PM +1100, JH wrote:
> So the same problem appeared in 1.35 that used old Yocto libraries and
> kernel, it was usually all good in terms of WiFi network IP
> allocation. It approved that the same problem in 1.37 is not related
> to the change of libraries. But I could not figure out what is the
> problem and how to fix it.
That would mean something in the network has changed, e.g. did you
upgrade your access points?
> > Yes, you should see a DCHP response frame.
>
> Hmm, still mysterious, any clue what could cause that problem?
So far we know there something fishy going on on the lower levels. Try
to increase the logging/debugging verbosity:
First, start wpa_supplicant by hand and '-dd' (maybe you need to kill
wpa_supplicant running in the backgroud)
# wpa_supplicant -dd -u -f wpa_supplicant.log
and then start ConnMan with
# CONNMAN_SUPPLICANT_DEBUG=1 ./connmand -n -d 2>&1 | ts '[%H:%M:%.S]' | tee
connman.log
Thanks,
Daniel
------------------------------
Date: Sun, 26 Jan 2020 10:25:13 -0500
From: chaitanya cherukuri <[email protected]>
Subject: Re: Connman 1.35 authentication timeout and alternate
configuration for wired interface
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<calvd-wno1pgl2y1u1lvzpp-yxtsxzha7oa0bekc9dhbr3no...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
On Fri, Jan 24, 2020 at 2:48 AM Daniel Wagner <[email protected]> wrote:
>
> Hi Chaitanya,
>
> On Thu, Jan 23, 2020 at 12:57:56PM -0500, chaitanya cherukuri wrote:
> > Thank you this is working. When the unit detects there is no uplink an
> > IPv4LL address is assigned.
> > Upon every reboot, a new IPv4LL address is assigned. Is there any way
> > to have the same IPv4LL address?
>
> No, IPv4LL is an autoconfig protocol, see
>
> https://en.wikipedia.org/wiki/Link-local_address
>
> Device discovering is done via the host name not the IP address
> (mDNS). If you want to connect to a headless device with our Laptop, just
> type in the
> device name as URL to access it via port 80.
>
> mDNS (aka zeroconf, bonjour) is supported by all modern operating
> system.
>
Thank you for the clarification and for answering my questions.
> Thanks,
> Daniel
Thanks,
Chaitanya
------------------------------
Date: Mon, 27 Jan 2020 10:35:09 +1100
From: JH <[email protected]>
Subject: Re: lost busybox mysteriously
To: Yocto discussion list <[email protected]>
Cc: linux-mtd <[email protected]>, connman
<[email protected]>
Message-ID:
<CAA=hcWRwi_EsMD2OBzVWtyX_SPJf05vqc09zhQzFdguKi0k=f...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
I have further investigated the problem, here is more information:
That the same problem of missing busybox was not just occurred during
the device running in the middle of operation, it was also occurred
during booting image from NAND, I saw several times that the first and
second cycles of booting image from NAND were working well, then some
following booting process would be crashed by missing busybox, then
could not run whole shell commands. I have been pondering if it could
be caused by NAND issue or network virus / fishy? Appreciate any
clues.
Thank you.
Kind regards,
- jh
On 1/26/20, JH <[email protected]> wrote:
> Hi,
>
> I have been building and running Yocto image on iMX6 with NAND flash
> for a year, recently, I found that busybox was certainly missing
> mysteriously, I could not check ls and other shell commands. I could
> not figure out what caused that problem, it's like the flash is
> leaking. Appreciate tips how to debug it?
>
> Thank you.
>
> - jh
>
------------------------------
Date: Sun, 26 Jan 2020 21:17:43 -0500
From: Torsten Wörtwein <[email protected]>
Subject: Doesn't connect to strongest wifi
To: [email protected]
Message-ID:
<CAJ4L66h2Ma2aJcnuhhP+eacOGH=f2oqnfmmybo2nabouf+o...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000035fbfd059d15b796"
--00000000000035fbfd059d15b796
Content-Type: text/plain; charset="UTF-8"
Hi,
I have one router which broadcasts 2GHz and 5GHz on the same SSID with the
same security settings. I also have a repeater which does exactly the same
(2+5Ghz, same SSID as the router, and same security settings as the
router). I have one visible entry in connman which merges all four of these
wifis.
Connman always connects to the router, even when the signal of the repeater
is much stronger. It would be great if connman would connect to the
stronger wifi source.
I'm running ArchLinux with connman 1.37, WPA-supplicant 2.9, and kernel
4.19.98. Please let me know how I can provide more useful information about
this issue.
Thanks,
Torsten
--00000000000035fbfd059d15b796
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi,<br><br>I have one router which broadcasts 2GHz and 5GH=
z on the same SSID with the same security settings. I also have a repeater =
which does exactly the same (2+5Ghz, same SSID as the router, and same secu=
rity settings as the router). I have one visible entry in connman which mer=
ges all four of these wifis.<br><br>Connman always connects to the router, =
even when the signal of the repeater is much stronger. It would be great if=
connman would connect to the stronger wifi source.<br><br>I'm running =
ArchLinux with connman 1.37, WPA-supplicant 2.9, and kernel 4.19.98. Please=
let me know how I can provide more useful information about this issue.<br=
><br>Thanks,<br>Torsten</div>
--00000000000035fbfd059d15b796--
------------------------------
Date: Mon, 27 Jan 2020 13:26:41 +1100
From: JH <[email protected]>
Subject: 4G LTE connection stability with USB voltage requirement
To: connman <[email protected]>
Cc: ofono <[email protected]>, linux-usb <[email protected]>
Message-ID:
<CAA=hcWTiqmULgD1JqEHUo4iXtrCt+zQAHmJL8=wpunqpa57...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
Apologies for cross posting.
I am running Yocto build image with kernel 4.19.75 on iMX6, the device
uses uBlox SARA-R4 4G LTE modem. I have an LTE connection stability
issue, it could connect to 4G LTE, then the connection was
disconnected between half an hour to an hour randomly, the error
messages were qmi_wwan of qmi_wwan 1-1:1.3: nonzero urb status
received: -71 and qmi_wwan 1-1:1.3: wdm_int_callback - usb_submit_urb
failed with result -19 for errors of EPROTO and ENODEV, many indicated
that kind of errors usually caused by insufficient USB voltage.
To diagnose it, I changed to use a DC regulated power supply to
connect USB voltage from a stable 5V DC regulated power supply, that
did help to stabilize the 4G LTE connection, the device has been
stable to connect to 4G LTE since yesterday (26 January AEST) morning
more than 24 hours which was not able to perform that stability if the
USB connected to a laptop or connected the device internal regulated
DC voltage from AC power supply.
What cannot convince to hardware engineers and what baffling me is
that I am also testing an image built from OpenWrt using network
manager netifd, it did not have LTE connection issue and it could
connect to 4G LTE much stable to use either USB power supply from a
laptop or device internal DC voltage from AC power supply. It does not
make sense if I say to the hardware engineer that device has power
supply issues. Why OpenWrt netifd is much stable than connman / ofono
in the same power supply conditions?
It seems to me there are subtle differences between connman / ofono
and OpenWrt netifd, could the connman / ofono require more rigid
stable USB voltage than OpenWrt netifd? Or could the OpenWrt netifd be
more superior than connman / ofono in terms of 4G LTE connections?
Appreciate your insight comments and advice.
Thank you.
Kind regards,
- jh
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 51, Issue 33
***************************************
