* KnownNetwork AutoConnect property changed signal
@ 2020-01-18 16:21 Daniel Wagner
2020-01-29 17:04 ` Denis Kenzior
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Wagner @ 2020-01-18 16:21 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]
Hi,
I'm in the process of updating the iwd plugin for ConnMan. Since
ConnMan wants to decide when to connect to a network, I decided to
tell iwd not to auto connect to any known networks. Not sure if this
will work but that's a different topic.
Anyway, during boot up the plugin discovers the known network and for
each network with AutoConnect set to true it will issue an set
property call. There is also a property changed callback which does
the same.
[iwd]# known-networks "owl stretching time" show
Known Network: owl stretching time
--------------------------------------------------------------------------------
Settable Property Value
--------------------------------------------------------------------------------
Name owl stretching time
Hidden
* AutoConnect no
[iwd]# known-networks owl stretching time set-property AutoConnect yes
I observe following:
connmand[27914]: plugins/iwd.c:known_network_property_change() 0x1af1450 auto_connect 0
connmand[27914]: plugins/iwd.c:known_network_property_change() 0x1af1450 auto_connect 1
connmand[27914]: plugins/iwd.c:disable_auto_connect()
connmand[27914]: plugins/iwd.c:known_network_property_change() 0x1af1450 auto_connect 1
connmand[27914]: plugins/iwd.c:disable_auto_connect()
connmand[27914]: plugins/iwd.c:known_network_property_change() 0x1af1450 auto_connect 0
connmand[27914]: plugins/iwd.c:known_network_property_change() 0x1af1450 auto_connect 0
and monitor-iwd sees
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = False
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] LastConnectedTime = 2020-01-18T16:10:34Z
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = True
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = True
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = False
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = False
I am bit surprised by the number of property changed signals. I
expected to see only 'auto_connect 1' and then a 'auto_connect 0'.
I verified the behavior without ConnMan running:
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = False
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] LastConnectedTime = 2020-01-18T16:19:26Z
{KnownNetwork} [/net/connman/iwd/6f776c2073747265746368696e672074696d65_psk] AutoConnect = True
Is this supposed to be so?
Thanks,
Daniel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-01-29 17:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-18 16:21 KnownNetwork AutoConnect property changed signal Daniel Wagner
2020-01-29 17:04 ` Denis Kenzior
2020-01-29 17:50 ` Daniel Wagner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.