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.
(Daniel Wagner)
2. Re: Doesn't connect to strongest wifi (Torsten Wörtwein)
----------------------------------------------------------------------
Date: Mon, 3 Feb 2020 07:59:42 +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 Sun, Feb 02, 2020 at 01:51:10PM -0500, Maxime Roussin-Bélanger wrote:
> 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 the
> `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 what
> > > 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=1 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, but
> 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 have
> 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.
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.
Thanks,
Daniel
------------------------------
Date: Mon, 3 Feb 2020 02:46:58 -0500
From: Torsten Wörtwein <[email protected]>
Subject: Re: Doesn't connect to strongest wifi
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<CAJ4L66iqXex=LnrDVz1LCX32Pkopos5qw=WOt=jgpfg5ovj...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000006c019d059da721f2"
--0000000000006c019d059da721f2
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
On Sun, Feb 2, 2020 at 7:47 AM Daniel Wagner <[email protected]> wrote:
> iwd doesn't know about ConnMan's setting files. Are you sure ConnMan
> was not running in the background? I don't see how else iwd figured
> out the network settings. I assume you have a WPA2 enabled.
>
I'm quite sure connman wasn't running and yes it is WPA2. I had used
connman+iwd before then, I assume iwd remembered the settings which
connman told it at some point.
> Alright, this is sounds promising. Anyway, if you find anything not
> working with iwd I am sure we get things sorted out as the iwd
> developers are interested to get things fixed.
>
> And from my point of view, I am interested to get things fixed in
> ConnMan for iwd.
>
> For wpa_supplicant, I don't want to invest more of my personal
> time. Obviously, if someones sends fixes I am glad to except them. But
> personally I wont to implement or fix bugs on it except minimal
> maintaince work.
>
iwd is pretty awesome, I removed wpa_supplicant and connman (sorry,
iwd covers all my networking needs).
I was able to tweak the roaming behavior of iwd with it's RoamThreshold and
BandModifier5Ghz settings :)
Thanks,
Torsten
--0000000000006c019d059da721f2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hi Daniel,<br></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 2, 2020 at 7:47 AM Daniel W=
agner <<a href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
iwd doesn't know about ConnMan's setting files. Are you sure ConnMa=
n<br>
was not running in the background? I don't see how else iwd figured<br>
out the network settings. I assume you have a WPA2 enabled.<br></blockquote=
><div>I'm quite sure connman wasn't running and yes it is WPA2. I h=
ad used</div><div>connman+iwd before then, I assume iwd remembered the sett=
ings which</div><div>connman told it at some point.<br></div><div>=C2=A0<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">
Alright, this is sounds promising. Anyway, if you find anything not<br>
working with iwd I am sure we get things sorted out as the iwd<br>
developers are interested to get things fixed.<br>
<br>
And from my point of view, I am interested to get things fixed in<br>
ConnMan for iwd.<br>
<br>
For wpa_supplicant, I don't want to invest more of my personal<br>
time. Obviously, if someones sends fixes I am glad to except them. But<br>
personally I wont to implement or fix bugs on it except minimal<br>
maintaince work.<br></blockquote><div>iwd is pretty awesome, I removed wpa_=
supplicant and connman (sorry,</div><div>iwd covers all my networking needs=
).</div><div><br></div><div>I was able to tweak the roaming behavior of iwd=
with it's RoamThreshold and BandModifier5Ghz settings :)<br></div><div=
><br></div><div>Thanks,</div><div>Torsten<br></div><div>=C2=A0</div></div><=
/div>
--0000000000006c019d059da721f2--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 2
**************************************
