From: Grant Erickson <gerickson@nuovations.com>
To: connman@lists.linux.dev
Subject: Clarifying ConnMan Configuration Multi-technology Feature Fusion and Online/Ready Transitions
Date: Tue, 10 Oct 2023 20:37:34 -0700 [thread overview]
Message-ID: <2CD24062-D2D6-4E13-A6A9-7EA130D38131@nuovations.com> (raw)
I am working with connman at commit 24180d1243bf on a system with Ethernet, Wi-Fi, and Cellular with the following configuration:
[General]
AllowDomainnameUpdates=false
AllowHostnameUpdates=false
AlwaysConnectedTechnologies=ethernet,wifi,cellular
BackgroundScanning=true
DefaultAutoConnectTechnologies=ethernet,wifi,cellular
EnableOnlineCheck=true
EnableOnlineToReadyTransition=true
FallbackTimeservers=0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org
FallbackNameservers=8.8.8.8,8.8.4.4
PreferredTechnologies=ethernet,wifi,cellular
SingleConnectedTechnology=false
TetheringTechnologies=
I’ve pored over connman.conf.5 a number of times now and acknowledge that ‘EnableOnlineToReadyTransition’ is marked experimental; however, I am trying to understand how the above configuration is supposed to work relative to my understanding of how I believe it should work relative to how it documented in connman.conf.5.
What I see happening is that net.connman.Manager.State is frequently flipping between “Ready” and “Online” (on the order of seconds) and that a majority of the time, none of the connected services associated with the above three technologies is ever “Online”, just “Ready”.
My expectation is that Ethernet would be marked “Online” and steadily stay there until such time as there is a failure of some sort for that technology, at which time I’d expected “Wi-Fi” to then get promoted to “Online” if possible and, failing that, “Cellular” promoted to “Online”.
Am I misunderstanding and/or misconfiguring things relative to my assumptions?
Best,
Grant
--
Principal
Nuovations
gerickson@nuovations.com
http://www.nuovations.com/
next reply other threads:[~2023-10-11 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 3:37 Grant Erickson [this message]
2023-10-14 1:05 ` Clarifying ConnMan Configuration Multi-technology Feature Fusion and Online/Ready Transitions Grant Erickson
2023-11-08 14:46 ` Marcel Holtmann
2023-11-08 15:30 ` Grant Erickson
2023-11-08 16:03 ` daniel antoine
2023-11-08 18:41 ` Marcel Holtmann
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=2CD24062-D2D6-4E13-A6A9-7EA130D38131@nuovations.com \
--to=gerickson@nuovations.com \
--cc=connman@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).