Send connman mailing list submissions to
connman@lists.01.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
connman-requ...@lists.01.org
You can reach the person managing the list at
connman-ow...@lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Connman and IWD - Scanning Network - Update? (stef204)
2. RE: [PATCH 0/1] start online check even if service is not the default
service
(VAUTRIN Emmanuel (Canal Plus Prestataire))
----------------------------------------------------------------------
Date: Fri, 07 May 2021 05:50:28 -0600
From: stef204 <stef...@yandex.com>
Subject: Re: Connman and IWD - Scanning Network - Update?
To: Daniel Wagner <w...@monom.org>
Cc: "connman@lists.01.org" <connman@lists.01.org>
Message-ID: <1363341620388...@mail.yandex.com>
Content-Type: text/html; charset=utf-8
<div>Any luck with getting connman with IWD to detect wifi using connmanctl
'scan wifi'?</div><div> </div><div> </div><div>21.10.2019, 00:58, "Daniel
Wagner" <w...@monom.org>:</div><blockquote><p>On Thu, Oct 17, 2019 at
05:15:51AM -0600, stef204 wrote:</p><blockquote> Any updates or progress on
this issue?</blockquote><p><br />No not yet. Sorry.</p></blockquote>
------------------------------
Date: Fri, 7 May 2021 13:00:31 +0000
From: "VAUTRIN Emmanuel (Canal Plus Prestataire)"
<emmanuel.vaut...@cpexterne.org>
Subject: RE: [PATCH 0/1] start online check even if service is not the
default service
To: Christophe Ronco <c.ro...@kerlink.fr>, Daniel Wagner
<w...@monom.org>, "connman@lists.01.org" <connman@lists.01.org>,
"r...@gmx.de" <r...@gmx.de>
Message-ID: <pr1pr02mb479499bb5ec8a918240ea47f93...@pr1pr02mb4794.eur
prd02.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Christophe,
> First sorry for the delay. Many things to work on these days.
No problem.
> I tried with up-to-date HEAD with the same result. Logs are attached.
> Here is my analysis of these logs:
By my side, I am using a 1.39 with my more recent patches + the following conf
PreferredTechnologies=ethernet,wifi
SingleConnectedTechnology=false
TetheringTechnologies=wifi
NetworkInterfaceBlacklist=p2p
OnlineCheckInitialInterval=1
OnlineCheckMaxInterval=2
EnableOnlineToReadyTransition=true
I think I am reproducing a similar problem, with the Ethernet and a Hostspot,
IPv4.
I have gathered the following information, by monitoring the state changes via:
dbus-monitor --system "type=signal,member=PropertyChanged" | grep State -B1 -A1
> Start of connman with Ethernet cable plugged: wispr started on eth0
> service, http request OK, eth service goes online
signal time=1620381082.278227 sender=:1.9 -> destination=(null destination)
serial=77 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "idle"
signal time=1620381082.278276 sender=:1.9 -> destination=(null destination)
serial=78 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cod
string "State"
variant string "idle"
hisi-femac f9840000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
--
signal time=1620381084.366683 sender=:1.9 -> destination=(null destination)
serial=83 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "ready"
--
signal time=1620381084.484084 sender=:1.9 -> destination=(null destination)
serial=87 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cod
string "State"
variant string "online"
signal time=1620381084.485157 sender=:1.9 -> destination=(null destination)
serial=88 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "online"
Activating the Hotspot
signal time=1620381171.289037 sender=:1.9 -> destination=(null destination)
serial=177 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "association"
--
signal time=1620381171.727223 sender=:1.9 -> destination=(null destination)
serial=183 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "configuration"
--
signal time=1620381171.771218 sender=:1.9 -> destination=(null destination)
serial=185 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "ready"
> Ethernet cable unplugged: wispr started on wlan0 service, http request
signal time=1620381179.556617 sender=:1.9 -> destination=(null destination)
serial=197 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "ready"
signal time=1620381179.556743 sender=:1.9 -> destination=(null destination)
serial=198 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cd
string "State"
variant string "disconnect"
--
signal time=1620381179.564539 sender=:1.9 -> destination=(null destination)
serial=205 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cd
string "State"
variant string "idle"
--
signal time=1620381180.704742 sender=:1.9 -> destination=(null destination)
serial=215 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "online"
signal time=1620381180.706072 sender=:1.9 -> destination=(null destination)
serial=216 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "online"
> Ethernet cable plugged again: eth service back to ready, wispr not
> started, eth service stays ready
signal time=1620381217.443148 sender=:1.9 -> destination=(null destination)
serial=251 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cd
string "State"
variant string "disconnect"
--
signal time=1620381217.445797 sender=:1.9 -> destination=(null destination)
serial=255 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cd
string "State"
variant string "idle"
hisi-femac f9840000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
I am noticing that I am not notified by the state update to ready.
I confirm I can see the ready state for Ethernet., when I get the services via:
dbus-send --system --print-reply --dest=net.connman /
net.connman.Manager.GetServices
When I turn off the Hotspot, the Ethernet gets back to online state.
signal time=1620381443.274809 sender=:1.9 -> destination=(null destination)
serial=449 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "ready"
signal time=1620381443.275023 sender=:1.9 -> destination=(null destination)
serial=450 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "ready"
--
signal time=1620381446.972278 sender=:1.9 -> destination=(null destination)
serial=462 path=/net/connman/service/ethernet_001982fec40b_cable;
interface=net.cd
string "State"
variant string "online"
signal time=1620381446.972577 sender=:1.9 -> destination=(null destination)
serial=463 path=/; interface=net.connman.Manager; member=PropertyChanged
string "State"
variant string "online"
--
signal time=1620381449.898590 sender=:1.9 -> destination=(null destination)
serial=469 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "disconnect"
--
signal time=1620381449.904264 sender=:1.9 -> destination=(null destination)
serial=473 path=/net/connman/service/wifi_18c8e72ae371_74657374_managed_psk;
inted
string "State"
variant string "idle"
> Yes this is a big problem for me. If WiFi service stays online and
> Ethernet service stays ready, the default route is on WiFi so all
> traffic goes through WiFi instead of wired. This is bad and not what end
> user wants when he wrote "PreferredTechnologies = ethernet, wifi,
> cellular" in main.conf. WiFi is a backup and must not be used if
> Ethernet is OK. Looking at comments in main.conf I see current behavior
> (using WiFi service for default route when Ethernet service is working)
> as a bug.
Your concern makes totally sense.
> I don't think that reproducing my problem is difficult, can you tell me
> if you see the same behavior ? If not, could you send your debug logs,
> I'll try to understand what I did wrong.
I confirm it to be completely reproducible.
Moreover, I think that our validation team has noticed that after
the update from 1.37 to1.38.
It is not my priority, but will try to check it the next weeks.
Best Regards,
Emmanuel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- connman@lists.01.org
To unsubscribe send an email to connman-le...@lists.01.org
------------------------------
End of connman Digest, Vol 67, Issue 5
**************************************
