From: Gabriel Sanches <gabriel.sanches@prevas.dk>
To: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Online check failure does not downgrades service
Date: Fri, 19 Jan 2024 07:38:25 +0000 [thread overview]
Message-ID: <AM9PR10MB485454A9E0F1F672126EA4EFE1702@AM9PR10MB4854.EURPRD10.PROD.OUTLOOK.COM> (raw)
While testing the online check on continuous mode, I found out that it does not downgrades the service after the threshold is met.Seems like ipv6 being on state (ready) already prevents the downgrade. My assumption comes from inspecting
src/service.c:is_online_check_failure_threshold_met_predicate
Is this the correct behavior?
connman is on master@807ad961777ffffad36f53ea034583466a7073de
my main.conf file :
[General]
PreferredTechnologies=wifi,ethernet
DefaultAutoConnectTechnologies=wifi,ethernet
BackgroundScanning=true
EnableOnlineCheck=true
OnlineCheckConnectTimeout=10
OnlineCheckMode=continuous
OnlineCheckIntervalStyle=geometric
OnlineCheckInitialInterval=1
OnlineCheckMaxInterval=8
OnlineCheckFailuresThreshold=1
relevant log:
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:online_check_counters_log() service 0x18f29b0 (wifi_e8fb1ccdfacb_6d7563686f626f6d3547_managed_psk) ipv4 state 5 (online) failure(s/es) 2 ipv6 state 4
(ready) failure(s/es) 0
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:online_check_counter_threshold_is_met() service 0x18f29b0 (wifi_e8fb1ccdfacb_6d7563686f626f6d3547_managed_psk) failure threshold 1 failure(s) met 0
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:handle_continuous_online_check_failure() failures threshold was met 0 failures threshold is met 0 default 1
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:online_check_counters_log() service 0x18f29b0 (wifi_e8fb1ccdfacb_6d7563686f626f6d3547_managed_psk) ipv4 state 5 (online) failure(s/es) 2 ipv6 state 4
(ready) failure(s/es) 0
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:online_check_counter_threshold_is_met() service 0x18f29b0 (wifi_e8fb1ccdfacb_6d7563686f626f6d3547_managed_psk) failure threshold 1 failure(s) met 0
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:handle_continuous_online_check_failure() failures threshold was met 0, default 1
connmand[2065]: /usr/src/debug/connman/1.43-r0/src/service.c:complete_online_check() reschedule online check 1
reply other threads:[~2024-01-19 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AM9PR10MB485454A9E0F1F672126EA4EFE1702@AM9PR10MB4854.EURPRD10.PROD.OUTLOOK.COM \
--to=gabriel.sanches@prevas.dk \
--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).