From: Jupiter <jupiter.hce@gmail.com>
To: connman <connman@lists.linux.dev>
Cc: Daniel Wagner <wagi@monom.org>
Subject: Connman stability degraded upgrading new versions
Date: Tue, 14 Sep 2021 16:58:15 +1000 [thread overview]
Message-ID: <CAA=hcWQTDvN-vh+UgXx8jpV--NPBrXWWsd1O6Sg=FVufPapDWw@mail.gmail.com> (raw)
Hi Daniel,
When I used connman v1.35, it was very stable, it could switch to 4G
LTE automatically and reliably when the WiFi was not available.
After upgrading to version 1.37, that network automatic switch is
gone, I have to restart connman to make it work.
After trying to upgrade to version 1.39 in the Hardknott branch, I
cannot not even get WiFi and 4G LTE work, the WiFi network was
assigned with a fake IP address 10.x.x.x, it could not get the 4G LTE
interface. I have to abandon the upgrading. I was told that connman
1.39 did not work well with Hardknott libraries, I have no idea who is
managing the connman release on OE Yocto build.
What has been changed in connman new versions? I must miss something,
I was told that connman uses WPA supplicant for WiFi, I have used WPA
supplicant v2.6 for the connman v1.37, could it be WPA_supplicant
problem, or Yocto build problem or connman problem? My apology, I
don't have good debug skills to debug it, but if you could instruct me
debug technique I'll provide more testing and debug information.
Thank you.
Kind regards,
- jupiter
next reply other threads:[~2021-09-14 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 6:58 Jupiter [this message]
2021-09-20 7:12 ` Connman stability degraded upgrading new versions Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA=hcWQTDvN-vh+UgXx8jpV--NPBrXWWsd1O6Sg=FVufPapDWw@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=connman@lists.linux.dev \
--cc=wagi@monom.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).