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: How to set up wifi.config to be a WiFi AP (Daniel Wagner)
2. Re: Failed to can wifi Invalid Sched_scan parameters
(Daniel Wagner)
3. Re: Impossible to retry when entering wrong password with connmanctl.
(Maxime Roussin-Bélanger)
4. Re: Impossible to retry when entering wrong password with connmanctl.
(Daniel Wagner)
5. Re: Impossible to retry when entering wrong password with connmanctl.
(Maxime Roussin-Bélanger)
6. Re: Impossible to retry when entering wrong password with connmanctl.
(Daniel Wagner)
----------------------------------------------------------------------
Date: Tue, 4 Feb 2020 09:10:59 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: How to set up wifi.config to be a WiFi AP
To: JH <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi JH,
On Tue, Feb 04, 2020 at 02:33:14PM +1100, JH wrote:
> 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?
You can edit the /var/lib/connman/settings file. Please note, you can
only edit if ConnMan is not running. ConnMan will overwrite it.
[global]
OfflineMode=false
[Wired]
Enable=true
Tethering=false
[WiFi]
Enable=true
Tethering=true
Tethering.Identifier=yoyo
Tethering.Passphrase=0000000000
[Bluetooth]
Enable=true
Tethering=false
Thanks,
Daniel
------------------------------
Date: Tue, 4 Feb 2020 09:14:35 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Failed to can wifi Invalid Sched_scan parameters
To: JH <[email protected]>
Cc: linux-wireless <[email protected]>, connman
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi JH,
On Tue, Feb 04, 2020 at 04:00:54PM +1100, JH wrote:
> [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.
linux/drivers/net/wireless/marvell/mwifiex
> > 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?
The 'Invalid Sched_scan parameters' indicates, wpa_supplicant is
providing the wrong parameters. Best thing is to monitor between
wpa_supplicant and kernel the netlink messages. iwmon is an excellent
tool for this.
Thanks,
Daniel
------------------------------
Date: Tue, 4 Feb 2020 12:19:10 -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-s4-kqx-1q2KpWmhKmKJg=ztoly8rfrxcqzah9aaumn...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000085f343059dc33ef1"
--00000000000085f343059dc33ef1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi Daniel! Same unfortunate problem with iwd 1.4 and connman master.
On Tue, Feb 4, 2020 at 2:52 AM Daniel Wagner <[email protected]> wrote:
>
> On Mon, Feb 03, 2020 at 06:06:08PM -0500, Maxime Roussin-B=C3=A9langer wr=
ote:
> > Hi Daniel! Tested iwd.
>
> Yay!
>
> > 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
>
> Looks like you are using not the current head. I just recently updated
> the iwd plugin. Before that the scan trigger was not implemented.
>
> But that you can ignore this for the time being. You can also trigger
> the scan by iwctl.
Updated to connman master and the error is now gone! Thanks.
>
> > > 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.
>
> Yes, iwd uses the kernel cryptographic subsystem and doesn't ship it's
own.
>
> > I analyzed the packets from iwmon with Wireshark and there was some
> > Malformed packets error...
>
> That doesn't look too good. Are the malformed packets from the kernel
> or from iwd? Either way I would reproduce this with a current kernel
> and see if it's a problem. If yes, please report it upstream.
I started using iwd 1.4 and those malformed packets are gone.. So not an
issue anymore.
>
> > 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.
>
> Ah, didn't think about this. Indeed the minimum vanilla kernel needed
> is 4.20. Though I remember they iwd folks have maintained their
> patches outside of the kernel for a while for all the different kernel
> versions. Maybe you could pick those for the testing.
I don't know if you have seen my previous reply with the screenshot and the
log output, but I have the same problem with connman where the retry fails.
If I use `iwctl` I can retry the connection to an AP if I entered an
incorrect password.
Maybe connmanctl has an edge case (mine) where for my particular error it
doesn't
handle it well? I think that if you see the screenshot, you might have
better intuition.
I'll be in the #connman IRC if you want to talk in realtime.
Thanks,
Maxime.
>
> Thanks,
> Daniel
--00000000000085f343059dc33ef1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Daniel! Same unfortunate=C2=A0problem with iwd 1.4 and =
connman master.<br><br>On Tue, Feb 4, 2020 at 2:52 AM Daniel Wagner <<a =
href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<br>><br>>=
; On Mon, Feb 03, 2020 at 06:06:08PM -0500, Maxime Roussin-B=C3=A9langer wr=
ote:<br>> > Hi Daniel! Tested iwd.<br>><br>> Yay!<br>><br>&g=
t; > I started using iwd, and the first thing that happened was that I l=
ost the<br>> > ability to<br>> > scan. Everytime I type `scan w=
ifi`, from connmanctl, I get<br>> > `Error /net/connman/technology/wi=
fi: Not Supported`. This error is -95.<br>> ><br>> > The backtr=
ace looks like:<br>> ><br>> > manager.c:get_technologies()<br>&=
gt; > technology.c:scan() technology 0x559d75d760 request from :1.19<br>=
> > connman_device_request_scan() device 0x559d7664d0 err -95<br>>=
> connman_device_request_scan() device 0x559d762ba0 err -95<br>> >=
; technology.c:reply_scan_pending() technology 0x559d75f760 err -95<br>>=
<br>> Looks like you are using not the current head. I just recently upd=
ated<br>> the iwd plugin. Before that the scan trigger was not implement=
ed.<br>><br>> But that you can ignore this for the time being. You ca=
n also trigger<br>> the scan by iwctl.<div><br></div><div>Updated to con=
nman master and the error is now gone! Thanks.</div><div><br>><br>> &=
gt; > If it is not to complicated to intergrate, give it a try. This giv=
es<br>> > > you at least some idea where the problem could be. And=
again iwmon is<br>> > > an excellent tool for monitoring the inte=
rface. I don't know if lttng<br>> > > is able to decode all th=
e traces. Ususally, you can easily spot the<br>> > > problems in t=
he traces generated by iwmon.<br>> ><br>> > I had to add a bunc=
h of cryptographic algorithm to the kernel to use iwd.<br>><br>> Yes,=
iwd uses the kernel cryptographic subsystem and doesn't ship it's =
own.<br>><br>> > I analyzed the packets from iwmon with Wireshark =
and there was some<br>> > Malformed packets error...<br>><br>> =
That doesn't look too good. Are the malformed packets from the kernel<b=
r>> or from iwd? Either way I would reproduce this with a current kernel=
<br>> and see if it's a problem. If yes, please report it upstream.<=
/div><div><br></div><div>I started using iwd 1.4 and those malformed packet=
s are gone.. So not an</div><div>issue anymore.</div><div><br>><br>> =
> We are using the 4.19 kernel, and iwd depends on a few cryptographic<b=
r>> > functions from 4.20. PKCS8 which is not in 4.19.<br>><br>>=
; Ah, didn't think about this. Indeed the minimum vanilla kernel needed=
<br>> is 4.20. Though I remember they iwd folks have maintained their<br=
>> patches outside of the kernel for a while for all the different kerne=
l<br>> versions. Maybe you could pick those for the testing.</div><div><=
br></div><div>I don't know if you have seen my previous reply with the =
screenshot and the=C2=A0</div><div>log output, but I have the same problem =
with connman where the retry fails.</div><div><br></div><div>If I use `iwct=
l` I can retry the connection to an AP if I entered an incorrect password.<=
/div><div><br></div><div>Maybe connmanctl has an edge case (mine) where for=
my particular error it doesn't</div><div>handle it well? I think that =
if you see the screenshot, you might have better intuition.</div><div><br><=
/div><div>I'll be in the #connman IRC if you want to talk in realtime.<=
/div><div><br></div><div>Thanks,</div><div>Maxime.</div><div><br></div><div=
>><br>> Thanks,<br>> Daniel</div></div>
--00000000000085f343059dc33ef1--
------------------------------
Date: Tue, 4 Feb 2020 18:37:47 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Impossible to retry when entering wrong password with
connmanctl.
To: Maxime Roussin-Bélanger <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
Hi Max,
On Tue, Feb 04, 2020 at 12:19:10PM -0500, Maxime Roussin-Bélanger wrote:
> Updated to connman master and the error is now gone! Thanks.
That is good news!
> I started using iwd 1.4 and those malformed packets are gone.. So not an
> issue anymore.
Good to know.
> I don't know if you have seen my previous reply with the screenshot and the
> log output, but I have the same problem with connman where the retry fails.
I did see it and tried to figure out what's going on. Though run out of time.
> If I use `iwctl` I can retry the connection to an AP if I entered an
> incorrect password.
That is a good test. That means if you just use iwd/iwctl there is no
problem. With this information it's clear ConnMan is doing something
wierd. It's propably the agent code in ConnMan which gets confused by
the error from the wpa_supplicant plugin but also with the iwd plugin.
> Maybe connmanctl has an edge case (mine) where for my particular error it
> doesn't
> handle it well? I think that if you see the screenshot, you might have
> better intuition.
Indeed the screenshot was helping. One thing I see there is WPS. Maybe
this is the thing which makes thing go wrong. Could you try to disable
WPS and see if this makes a difference?
> I'll be in the #connman IRC if you want to talk in realtime.
I'm also there. Though during office hours it's kind of difficult to
do hobby projects :)
Thanks,
Daniel
------------------------------
Date: Tue, 4 Feb 2020 14:49:11 -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-s7UcWMkzjpWkuYEhuLhAvStLgSk=-oblncwj+ygupw...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000003aa74059dc5570c"
--00000000000003aa74059dc5570c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello!
On Tue, Feb 4, 2020 at 12:37 PM Daniel Wagner <[email protected]> wrote:
>
> Hi Max,
>
> On Tue, Feb 04, 2020 at 12:19:10PM -0500, Maxime Roussin-B=C3=A9langer wr=
ote:
> > Updated to connman master and the error is now gone! Thanks.
>
> That is good news!
>
> > I started using iwd 1.4 and those malformed packets are gone.. So not a=
n
> > issue anymore.
>
> Good to know.
>
> > I don't know if you have seen my previous reply with the screenshot and
the
> > log output, but I have the same problem with connman where the retry
fails.
>
> I did see it and tried to figure out what's going on. Though run out of
time.
>
> > If I use `iwctl` I can retry the connection to an AP if I entered an
> > incorrect password.
>
> That is a good test. That means if you just use iwd/iwctl there is no
> problem. With this information it's clear ConnMan is doing something
> wierd. It's propably the agent code in ConnMan which gets confused by
> the error from the wpa_supplicant plugin but also with the iwd plugin.
>
> > Maybe connmanctl has an edge case (mine) where for my particular error
it
> > doesn't
> > handle it well? I think that if you see the screenshot, you might have
> > better intuition.
>
> Indeed the screenshot was helping. One thing I see there is WPS. Maybe
> this is the thing which makes thing go wrong. Could you try to disable
> WPS and see if this makes a difference?
Actually, I was trying to connect to a random AP that was in the list, and
it has the wps
support, but if I try to connect to any other network I do have the same
problem.
Thanks,
Max.
>
> > I'll be in the #connman IRC if you want to talk in realtime.
>
> I'm also there. Though during office hours it's kind of difficult to
> do hobby projects :)
>
> Thanks,
> Daniel
--00000000000003aa74059dc5570c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello!<br><br>On Tue, Feb 4, 2020 at 12:37 PM Daniel Wagne=
r <<a href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<br>&g=
t;<br>> Hi Max,<br>><br>> On Tue, Feb 04, 2020 at 12:19:10PM -0500=
, Maxime Roussin-B=C3=A9langer wrote:<br>> > Updated to connman maste=
r and the error is now gone! Thanks.<br>><br>> That is good news!<br>=
><br>> > I started using iwd 1.4 and those malformed packets are g=
one.. So not an<br>> > issue anymore.<br>><br>> Good to know.<b=
r>><br>> > I don't know if you have seen my previous reply wit=
h the screenshot and the<br>> > log output, but I have the same probl=
em with connman where the retry fails.<br>><br>> I did see it and tri=
ed to figure out what's going on. Though run out of time.<br>><br>&g=
t; > If I use `iwctl` I can retry the connection to an AP if I entered a=
n<br>> > incorrect password.<br>><br>> That is a good test. Tha=
t means if you just use iwd/iwctl there is no<br>> problem. With this in=
formation it's clear ConnMan is doing something<br>> wierd. It's=
propably the agent code in ConnMan which gets confused by<br>> the erro=
r from the wpa_supplicant plugin but also with the iwd plugin.<br>><br>&=
gt; > Maybe connmanctl has an edge case (mine) where for my particular e=
rror it<br>> > doesn't<br>> > handle it well? I think that =
if you see the screenshot, you might have<br>> > better intuition.<br=
>><br>> Indeed the screenshot was helping. One thing I see there is W=
PS. Maybe<br>> this is the thing which makes thing go wrong. Could you t=
ry to disable<br>> WPS and see if this makes a difference?<div><br></div=
><div>Actually, I was trying to connect to a random AP that was in the list=
, and it has the wps</div><div>support, but if I try to connect to any othe=
r network I do have the same problem.</div><div><br></div><div>Thanks,</div=
><div>Max.</div><div><br>><br>> > I'll be in the #connman IRC =
if you want to talk in realtime.<br>><br>> I'm also there. Though=
during office hours it's kind of difficult to<br>> do hobby project=
s :)<br>><br>> Thanks,<br>> Daniel</div></div>
--00000000000003aa74059dc5570c--
------------------------------
Date: Wed, 5 Feb 2020 08:55:16 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Impossible to retry when entering wrong password with
connmanctl.
To: Maxime Roussin-Bélanger <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
On Tue, Feb 04, 2020 at 02:49:11PM -0500, Maxime Roussin-Bélanger wrote:
> > Indeed the screenshot was helping. One thing I see there is WPS. Maybe
> > this is the thing which makes thing go wrong. Could you try to disable
> > WPS and see if this makes a difference?
>
> Actually, I was trying to connect to a random AP that was in the
> list, and it has the wps support, but if I try to connect to any
> other network I do have the same problem.
Okay, so it's something else.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 6
**************************************
