Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Strange inconsistant WiFi network behaviour (JH)
2. Impossible to retry when entering wrong password with connmanctl.
([email protected])
----------------------------------------------------------------------
Date: Thu, 30 Jan 2020 12:33:54 +1100
From: JH <[email protected]>
Subject: Re: Strange inconsistant WiFi network behaviour
To: Emil Petersky <[email protected]>
Cc: linux-wireless <[email protected]>, connman
<[email protected]>
Message-ID:
<CAA=hcwree3aezatormhvrtuwpvkponxwidu0ck4cbjwhw_o...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On 1/30/20, JH <[email protected]> wrote:
> Thanks Emil and Jan,
>
> On 1/29/20, Ryll, Jan (GED-SDD2) <[email protected]> wrote:
>> Try to increase distance from router or other WiFi device.
>
> Tried, but no avail.
Sorry Emil, I had spoken too soon, it is connected now. Why that
means, RF noise or interference from another device?
>> there are WiFi routers like AVM which are implement the WiFi Stack in a
>> stricter way than other routers or other WiFi chips-firmware.
>> I mention this cause weh ad some issue with a cypress wifi firmware which
>> leads to "sometimes" disconnect from routers. And we figured out that
>> this
>> was mostly the case with AVM. We are in contact with AVM in it turns out
>> that the AVM router work proberly. The issues was with the cypress
>> chipset
>> firmware. Now we are in contact with cypress and they accepted the issue.
>> So it is not always a connman problem :-) .
>
> That really worries me, my WiFi router is TP-Link AC1200 dual band
> router, it should have no problem for my device to connect it as I
> mentioned I have two devices one could connected without any issues.
> that definitely won't be my WiFi chip uBlox Lily issues, if it was,
> the another unit would not be possible to connect to my WiFi router in
> office.
>
> I am not saying it is connman problem or mwifiex problem or kernel
> problem, what I like is to get helps and clues from open source
> communities to help me to debug and to find issues, it could be my
> contributions as well if there could be potential open source bugs to
> be found from my test, debug and report :-).
>
> Thank you.
>
> Kind regards,
>
> - jh
>>
>> -----Original Message-----
>> From: JH <[email protected]>
>> Sent: Wednesday, January 29, 2020 10:22 AM
>> To: linux-wireless <[email protected]>; connman
>> <[email protected]>
>> Subject: Strange inconsistant WiFi network behaviour
>>
>> Hi,
>>
>> I have 2 iMX6 devices running uBlox Lily WiFi, mrvl firmware
>> sd8801_uapsta.bin in kernel 4.19.75. In my office, a WiFi router is just
>> 1
>> meter away, the WiFi signal should not be a problem. One device could
>> connect to the WiFi router well and stably, one could not, here were
>> error
>> messages:
>>
>> [ 408.990029] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
>> Invalid Sched_scan parameters
>> .....................
>>
>> [56.986414] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
>> Invalid Sched_scan parameter
>>
>> connmand[13469]:
>> ../connman-1.35/src/service.c:preferred_tech_add_by_type() type 5 service
>> 0x119120 Telstra
>> connmand[13469]: ../connman-1.35/src/service.c:auto_connect_service()
>> preferred 1 sessions 0 reason auto
>> connmand[13469]: ../connman-1.35/src/ntp.c:send_timeout() send timeout
>> 2 (retries 0)
>> connmand[13469]:
>> ../connman-1.35/plugins/ofono.c:netreg_update_strength() /ubloxqmi_2
>> Strength 80
>> connmand[13469]: ../connman-1.35/src/ntp.c:send_timeout() send timeout
>> 4 (retries 1)
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:throw_wifi_scan()
>> device 0x118da8 0x116c78
>> connmand[13469]:
>> ../connman-1.35/src/device.c:connman_device_ref_debug() 0x118da8 ref 4 by
>> ../connman-1.35/plugins/wifi.c:1214:throw_wifi_scan()
>> connmand[13469]:
>> ../connman-1.35/src/device.c:connman_device_set_scanning() device
>> 0x118da8 scanning 1
>> connmand[13469]:
>> ../connman-1.35/src/technology.c:__connman_technology_scan_started()
>> device 0x118da8
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:autoscan_timeout()
>> interval
>> 27
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:interface_state() wifi
>> 0x11a7c8 interface state 4
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:scan_started()
>> connmand[13469]: ../connman-1.35/src/rtnl.c:rtnl_message() NEWLINK len
>> 56 type 16 flags 0x0000 seq 0 pid 0
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:scan_finished()
>> connmand[13469]: ../connman-1.35/plugins/wifi.c:interface_state() wifi
>> 0x11a7c8 interface state 3
>>
>> Both devices were installed the same firmware and software, if it was
>> firmware / software issues, both would not be able to connect to WiFi, as
>> one device could connect to the office WiFi router well, it could not the
>> WiFi router problem either.
>>
>> If I move the faulty one to my home, it could connect to my home WiFi, so
>> the device does not have WiFi problem, that is really confusing, what
>> could
>> cause that kind problem and how to debug and fix it?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jh
>> _______________________________________________
>> connman mailing list -- [email protected] To unsubscribe send an email
>> to
>> [email protected]
>>
>
------------------------------
Date: Thu, 30 Jan 2020 01:39:50 -0000
From: [email protected]
Subject: Impossible to retry when entering wrong password with
connmanctl.
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hello!
We are on version 1.37, we are using wpa_supplicant 2.9 with a kernel 4.19.
When we are trying to use the connmanctl to connect to a protected wifi network
it works well without a problem. However, if we make a mistake when we type the
passphrase, it's impossible to retry. It does that to any network that we have
tried.
It is impossible to retry because for some reason when we are asked to retry
(https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/agent.c?h=1.37#n365),
this gets "cancel" by the agent
(https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/agent.c?h=1.37#n254)
and we lose the ability to retry forever for this network unless we delete the
settings for this particular network. I never get a chance to enter yes or no.
It never enters the callback
(https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/agent.c?h=1.37#n312),
that was set at line 365 in client/agent.c
We looked at the d-bus-monitor and we get two types of error: `-3` and we do
get a `16`, from 80211 AssocCode status code. -3 from what I can understand is
internal.
Now, since I have not seen this issue from others, I'm wondering if it's
related to our wifi chip misbehaving? I heard about a new thing called `iwd`,
but I haven't tested it, maybe I could give this a shot.
Thanks,
Max
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 51, Issue 39
***************************************
