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: Impossible to retry when entering wrong password with connmanctl.
(Maxime Roussin-Bélanger)
2. Weird behavior (JH)
3. How to set up wifi.config to be a WiFi AP (JH)
4. Failed to can wifi Invalid Sched_scan parameters (JH)
----------------------------------------------------------------------
Date: Mon, 3 Feb 2020 18:06:08 -0500
From: Maxime Roussin-Bélanger <[email protected]>
Subject: Re: Impossible to retry when entering wrong password with
connmanctl.
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<CAE=T-s5SQb1M59B0=7dNbaFu+ffQ1dAUWGv4yg_7445tk_x7=w...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000086d698059db3f9f1"
--00000000000086d698059db3f9f1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi Daniel! Tested iwd.
On Mon, Feb 3, 2020 at 1:59 AM Daniel Wagner <[email protected]> wrote:
>
> Hi Max,
>
> On Sun, Feb 02, 2020 at 01:51:10PM -0500, Maxime Roussin-B=C3=A9langer wr=
ote:
> > On Sun, Feb 2, 2020 at 9:40 AM Daniel Wagner <[email protected]> wrote:
> > After the 'timeout', I get the output `Agent request cancelled by
ConnMan`.
>
> Okay, I'm not sure if I saw this message when trying to provoke the
> timeout.
>
> > This cancel the retry prompt. Which I can see, but instead I'm shown th=
e
> > `connmanctl>`
> > to enter a connmanctl command.
> >
> > >
> > > > 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 wha=
t
> > > > I can understand is internal.
> > >
> > > Which communication are you monitoring? ConnMan - wpa_supplicant? You
> > > can also turn up the debug level on ConnMan side by setting the
> > > environment variable CONNMAN_SUPPLICANT_DEBUG=3D1 and enabling the
> > > connman log 'connmand -n -d'
> >
> > I monitored both.
>
> Can you upload the ConnMan log somehwere? I'd like to understand how
> we end up canceling the request and then block any further
> attempt.
>
> > > Accoring the WiFi spec, 16 means group key handshake timeout.
> > >
> > > I've tried to simulate the timeout by not entering a passphrase but
> > > again, it's still working for me.
> >
> > I don't really know how WiFi works at a lower level, but it seems that
if
> > I send the wrong password to the AP, the AP doesn't answer back. This
> > seems to trigger the timeout, or maybe the AP sends back a response, bu=
t
> > my device driver fails to handle the situation? We use brcm80211.
>
> Okay, so there might be two problems. One is that ConnMan is gets
> stuck in a state where you can't retry to connect with a new
> password. The other sounds like a driver/firmware problem.
>
> > We've been using lttng to aggregate the tracing logs from
> > connman, wpa_supplicant and the kernel to have a complete
> > picture. This as not been easy to figure out what is going on, but
> > so far it seems to always relate to our hardware integration... (We hav=
e
> > other WiFi problems)
>
> Nifty setup :)
>
> > I'm not sure iwd will be helpful if our hardware integration is at
> > fault here... but it will give us more hints to where the problem is.
>
> The nl80211 interface got a lot of bug fixes since iwd exists. Before
> iwd there was only wpa_supplicant and the interface suffered from the
> single user user problem. iwd exersices this API differently than
> wpa_supplicant. This could paper over some of the problems or maybe
> not.
I started using iwd, and the first thing that happened was that I lost the
ability to
scan. Everytime I type `scan wifi`, from connmanctl, I get
`Error /net/connman/technology/wifi: Not Supported`. This error is -95.
The backtrace looks like:
manager.c:get_technologies()
technology.c:scan() technology 0x559d75d760 request from :1.19
connman_device_request_scan() device 0x559d7664d0 err -95
connman_device_request_scan() device 0x559d762ba0 err -95
technology.c:reply_scan_pending() technology 0x559d75f760 err -95
>
> If it is not to complicated to intergrate, give it a try. This gives
> you at least some idea where the problem could be. And again iwmon is
> an excellent tool for monitoring the interface. I don't know if lttng
> is able to decode all the traces. Ususally, you can easily spot the
> problems in the traces generated by iwmon.
I had to add a bunch of cryptographic algorithm to the kernel to use iwd.
I analyzed the packets from iwmon with Wireshark and there was some
Malformed
packets error... We are using the 4.19 kernel, and iwd depends on a few
cryptographic
functions from 4.20. PKCS8 which is not in 4.19.
Thanks,
Max.
>
> Thanks,
> Daniel
--00000000000086d698059db3f9f1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Daniel! Tested iwd.<br><br>On Mon, Feb 3, 2020 at 1:59 =
AM Daniel Wagner <<a href=3D"mailto:[email protected]";>[email protected]</a>&g=
t; wrote:<br>><br>> Hi Max,<br>><br>> On Sun, Feb 02, 2020 at 0=
1:51:10PM -0500, Maxime Roussin-B=C3=A9langer wrote:<br>> > On Sun, F=
eb 2, 2020 at 9:40 AM Daniel Wagner <<a href=3D"mailto:[email protected]";>w=
[email protected]</a>> wrote:<br>> > After the 'timeout', I ge=
t the output `Agent request cancelled by ConnMan`.<br>><br>> Okay, I&=
#39;m not sure if I saw this message when trying to provoke the<br>> tim=
eout.<br>><br>> > This cancel the retry prompt. Which I can see, b=
ut instead I'm shown the<br>> > `connmanctl>`<br>> > to =
enter a connmanctl command.<br>> ><br>> > ><br>> > >=
; > We looked at the d-bus-monitor and we get two types of error: `-3`<b=
r>> > > > and we do get a `16`, from 80211 AssocCode status cod=
e. -3 from what<br>> > > > I can understand is internal.<br>>=
; > ><br>> > > Which communication are you monitoring? ConnM=
an - wpa_supplicant? You<br>> > > can also turn up the debug level=
on ConnMan side by setting the<br>> > > environment variable CONN=
MAN_SUPPLICANT_DEBUG=3D1 and enabling the<br>> > > connman log =
9;connmand -n -d'<br>> ><br>> > I monitored both.<br>><b=
r>> Can you upload the ConnMan log somehwere? I'd like to understand=
how<br>> we end up canceling the request and then block any further<br>=
> attempt.<br>><br>> > > Accoring the WiFi spec, 16 means gr=
oup key handshake timeout.<br>> > ><br>> > > I've tri=
ed to simulate the timeout by not entering a passphrase but<br>> > &g=
t; again, it's still working for me.<br>> ><br>> > I don=
9;t really know how WiFi works at a lower level, but it seems that if<br>&g=
t; > I send the wrong password to the AP, the AP doesn't answer back=
. This<br>> > seems to trigger the timeout, or maybe the AP sends bac=
k a response, but<br>> > my device driver fails to handle the situati=
on? We use brcm80211.<br>><br>> Okay, so there might be two problems.=
One is that ConnMan is gets<br>> stuck in a state where you can't r=
etry to connect with a new<br>> password. The other sounds like a driver=
/firmware problem.<br>><br>> > We've been using lttng to aggre=
gate the tracing logs from<br>> > connman, wpa_supplicant and the ker=
nel to have a complete<br>> > picture. This as not been easy to figur=
e out what is going on, but<br>> > so far it seems to always relate t=
o our hardware integration... (We have<br>> > other WiFi problems)<br=
>><br>> Nifty setup :)<br>><br>> > I'm not sure iwd will=
be helpful if our hardware integration is at<br>> > fault here... bu=
t it will give us more hints to where the problem is.<br>><br>> The n=
l80211 interface got a lot of bug fixes since iwd exists. Before<br>> iw=
d there was only wpa_supplicant and the interface suffered from the<br>>=
single user user problem. iwd exersices this API differently than<br>> =
wpa_supplicant. This could paper over some of the problems or maybe<div>>=
; not.</div><div><br></div><div>I started using iwd, and the first thing th=
at happened was that I lost the ability to</div><div>scan. Everytime I type=
`scan wifi`, from connmanctl, I get=C2=A0</div><div>`Error /net/connman/te=
chnology/wifi: Not Supported`. This error is -95.</div><div><br></div><div>=
The backtrace looks like:</div><div><br></div><div>manager.c:get_technologi=
es()</div><div>technology.c:scan() technology 0x559d75d760 request from :1.=
19</div><div>connman_device_request_scan() device 0x559d7664d0 err -95</div=
><div>connman_device_request_scan() device 0x559d762ba0 err -95<br></div><d=
iv>technology.c:reply_scan_pending() technology 0x559d75f760 err -95</div><=
div><br></div><div><br></div><div>><br>> If it is not to complicated =
to intergrate, give it a try. This gives<br>> you at least some idea whe=
re the problem could be. And again iwmon is<br>> an excellent tool for m=
onitoring the interface. I don't know if lttng<br>> is able to decod=
e all the traces. Ususally, you can easily spot the<br>> problems in the=
traces generated by iwmon.<div><br></div><div>I had to add a bunch of cryp=
tographic algorithm to the kernel to use iwd.</div><div><br></div><div>I an=
alyzed the packets from iwmon with Wireshark and there was some Malformed</=
div><div>packets error... We are using the 4.19 kernel, and iwd depends on =
a few cryptographic</div><div>functions from 4.20. PKCS8 which is not in 4.=
19.</div><div><br></div><div>Thanks,</div><div>Max.=C2=A0</div><div><br>>=
;<br>> Thanks,<br>> Daniel</div></div></div>
--00000000000086d698059db3f9f1--
------------------------------
Date: Tue, 4 Feb 2020 11:11:35 +1100
From: JH <[email protected]>
Subject: Weird behavior
To: connman <[email protected]>
Message-ID:
<CAA=hcWQqrhKGcx1XNKngy14-aYPtZiyVstCr0c72=7htiq7...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
I found it strange, how it could be an error of
/net/connman/technology/wifi: Not supported, but in technologies,
there was /net/connman/technology/wifi?
connmanctl> agent on
Agent registered
connmanctl> services
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Error /net/connman/technology/wifi: Not supported
connmanctl> technologies
/net/connman/technology/cellular
Name = Cellular
Type = cellular
Powered = True
Connected = False
Tethering = False
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = False
Thank you.
Kind regards,
- jh
------------------------------
Date: Tue, 4 Feb 2020 14:33:14 +1100
From: JH <[email protected]>
Subject: How to set up wifi.config to be a WiFi AP
To: connman <[email protected]>
Message-ID:
<CAA=hcWR04G_QLCeSmFOM2RWVtdd66=2+54XpXTV+fp=qykl...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
I usually set up the wifi.config to be a wifi client to connect to
WiFi route in house, how can I set up wifi.config in my device, so it
can be a WiFi AP?
Thank you.
Kind regards,
- jh
------------------------------
Date: Tue, 4 Feb 2020 16:00:54 +1100
From: JH <[email protected]>
Subject: Failed to can wifi Invalid Sched_scan parameters
To: linux-wireless <[email protected]>
Cc: connman <[email protected]>
Message-ID:
<CAA=hcWQuz9QTvbRJgFXBbYrB9RBmWajCJ=od49dyealw91t...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Here is more debug information:
# lsmod
Module Size Used by
option 45056 0
usb_wwan 20480 1 option
usbserial 36864 2 option,usb_wwan
mwifiex_sdio 36864 0
mwifiex 282624 1 mwifiex_sdio
evbug 16384 0
# dmesg | grep mwifiex
[ 34.511371] mwifiex_sdio mmc0:0001:1: info: FW download over, size
258680 bytes
[ 34.788787] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[ 34.873196] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[ 34.880490] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd
0x242 failed during initialization
[ 35.143577] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION:
mwifiex 1.0 (14.68.36.p60)
[ 35.152105] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0
(14.68.36.p60)
[ 59.004255] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 85.976707] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 166.949603] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 409.846886] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 709.774170] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 1009.659982] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 1309.572448] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 1609.481624] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 1909.370729] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 2209.279569] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 2509.170356] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 2809.085551] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3108.989242] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3348.887201] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3375.844143] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3456.825648] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3699.809750] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3699.952233] mwifiex_sdio mmc0:0001:1: info: trying to associate to
'Centaur24GRouter1' bssid 68:ff:7b:3e:d4:24
[ 3700.025358] mwifiex_sdio mmc0:0001:1: info: associated to bssid
68:ff:7b:3e:d4:24 successfully
[ 3706.132761] mwifiex_sdio mmc0:0001:1: info: successfully
disconnected from 68:ff:7b:3e:d4:24: reason code 15
[ 3717.123970] mwifiex_sdio mmc0:0001:1: info: trying to associate to
'Centaur24GRouter1' bssid 68:ff:7b:3e:d4:24
[ 3717.441578] mwifiex_sdio mmc0:0001:1: info: associated to bssid
68:ff:7b:3e:d4:24 successfully
[ 3723.543587] mwifiex_sdio mmc0:0001:1: info: successfully
disconnected from 68:ff:7b:3e:d4:24: reason code 15
[ 3727.794640] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3736.782236] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3763.809277] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 3844.811545] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 4087.803951] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 4387.748929] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 4687.718771] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 4987.705092] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 5287.646353] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 5587.643812] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[ 5753.760955] mwifiex_sdio mmc0:0001:1: info: trying to associate to
'Centaur24GRouter1' bssid 68:ff:7b:3e:d4:24
[ 5753.838800] mwifiex_sdio mmc0:0001:1: info: associated to bssid
68:ff:7b:3e:d4:24 successfully
[ 5754.162917] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x23f error, result=0x2
[ 5848.971534] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x23f error, result=0x2
[19611.826761] mwifiex_sdio mmc0:0001:1: info: successfully
disconnected from 68:ff:7b:3e:d4:24: reason code 3
[19654.931976] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[19686.885717] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[19713.896301] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[19794.907957] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20037.947625] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20337.974674] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20637.962485] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20716.944299] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20743.951609] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[20824.989582] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[21068.022269] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[21367.979313] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[21667.945929] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[21967.964944] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[22267.953450] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[22567.955314] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[22867.961508] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[23168.000460] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[23468.005767] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[23676.996473] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
[23703.958751] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
Where is the WiFi driver? Please let me know if you need more debug information.
Thank you.
Kind regards,
- jh
On 2/4/20, JH <[email protected]> wrote:
> Hi,
>
> I am running kernel 4.19.75 on iMX6, the WiFi was working most of
> time, but from time to time, the connman could not get WiFi be
> connected due to following error:
>
> [23703.958751] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
> Invalid Sched_scan parameters
>
> What does that error means, in which circumstance it occurred? How can
> we prevent it?
>
> Thank you.
>
> Kind regards,
>
> - jh
>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 4
**************************************
