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: [PATCH] iwd: Use path to look up network when updating signal strength
(Daniel Wagner)
2. Re: Doesn't connect to strongest wifi (Torsten Wörtwein)
3. Re: Doesn't connect to strongest wifi (Daniel Wagner)
----------------------------------------------------------------------
Date: Tue, 28 Jan 2020 19:19:23 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH] iwd: Use path to look up network when updating
signal strength
To: David Weidenkopf <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
> My focus this week is actually on 8021x. I got distracted when I
> noticed signal strength not updating :), and troubleshooting
> freeradius setup is a challenge.I will have comments, bug reports > or fixes
> soon, I hope.
Excellent!
Note the iwd plugin currently can't handle the full agent API from iwd.
I'd expect some parts not working, especially when doing 8021x. We need
to move the wpa_supplicant hacks in service.c out of the way before
the iwd plugin is able to forward the requests. The ConnMan design
shows the usual single user syndrome. In this case wpa_supplicant.
------------------------------
Date: Tue, 28 Jan 2020 20:47:48 -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:
<caj4l66jmyw+z-5shzkvkakejj4dllxjkqbz4xw-z3463ctr...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="000000000000d88dd2059d3d8770"
--000000000000d88dd2059d3d8770
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Tue, Jan 28, 2020 at 2:47 AM Daniel Wagner <[email protected]> wrote:
> Hi Torsten,
>
> On Mon, Jan 27, 2020 at 09:35:49PM -0500, Torsten W=C3=B6rtwein wrote:
> > On Mon, Jan 27, 2020 at 12:20 PM Daniel Wagner <[email protected]> wrote:
> > > What does connman -n -d plugins/wifi.c say about the SSIDs and the
> > > found frequencis? ConnMan has to tell wpa_supplicant which SSID and
> > > frequency to connect to. Though even if that is not wrong decision,
> > > wpa_supplicant should then automatically roam to the strongest signal=
.
> > >
> >
> > It seems to list only one frequency - only the lines containing the
> > router's/repeater's SSID:
> > connmand[895]: plugins/wifi.c:get_latest_connections() ssid
> > 726976656e64656c6c freq 5240 modified 1580175624
> > connmand[895]: plugins/wifi.c:add_scan_param() SSID 726976656e64656c6c
> > added to scanned list of 1 entries
> > connmand[895]: plugins/wifi.c:network_added()
> 726976656e64656c6c_managed_psk
> > connmand[895]: plugins/wifi.c:network_added()
> 726976656e64656c6c_managed_psk
> >
> > The router uses 2412/5240/5825 (5825 is from 'ASUS Smart Connect') and
> the
> > repeater uses 2417/5500. I was much closer to the repeater than to the
> > router when running "connmand -n -d plugins/wifi.c".
>
> One thing you could try for a workaround is to change the frequency
> stored in the settings file. First stop ConnMan (because it will
> overwrite those files). Go to
> /var/lib/connman/wifi_xxxxxxx_726976656e64656c6c_managed_psk and edit
> the settings file. There should be a Frequency entry with 5240. What
> happens if you change this to 5500?
>
Thanks Daniel! Unfortunately, connman changes it automatically back to the
router lower 5Ghz wifi (5240).
Interestingly, the output of "connmand -n -d plugins/wifi.c" changed. It
reports the repeaters 5Ghz wifi, which I manually entered:
connmand[43097]: plugins/wifi.c:get_latest_connections() ssid
726976656e64656c6c freq 5500 modified 1580261980
But it still ends up using 5240 (and changes the settings file back to
5240).
> I also noticed, that not all SSIDs might have been listed:
> > connmand[895]: plugins/wifi.c:wifi_scan() max ssids 16
> > connmand[895]: plugins/wifi.c:add_scan_param() SSID
> > 5265736964656e6365496e6e5f4755455354 added to scanned list of 15 entrie=
s
>
> wpa_supplicant exposes a lot of networking details and the wifi plugin
> in ConnMan has to do a lot of work. And I am not surprised this
> doesn't work as expected.
>
> Anyway, try the workaround to see if we are going into the right
> direction.
>
> Thanks,
> Daniel
>
--000000000000d88dd2059d3d8770
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 28, 2020 at 2:47 AM Daniel Wa=
gner <<a href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<br=
></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Hi Torsten,<br>
<br>
On Mon, Jan 27, 2020 at 09:35:49PM -0500, Torsten W=C3=B6rtwein wrote:<br>
> On Mon, Jan 27, 2020 at 12:20 PM Daniel Wagner <<a href=3D"mailto:w=
[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br>
> > What does connman -n -d plugins/wifi.c say about the SSIDs and th=
e<br>
> > found frequencis? ConnMan has to tell wpa_supplicant which SSID a=
nd<br>
> > frequency to connect to. Though even if that is not wrong decisio=
n,<br>
> > wpa_supplicant should then automatically roam to the strongest si=
gnal.<br>
> ><br>
> <br>
> It seems to list only one frequency - only the lines containing the<br=
>
> router's/repeater's SSID:<br>
> connmand[895]: plugins/wifi.c:get_latest_connections() ssid<br>
> 726976656e64656c6c freq 5240 modified 1580175624<br>
> connmand[895]: plugins/wifi.c:add_scan_param() SSID 726976656e64656c6c=
<br>
> added to scanned list of 1 entries<br>
> connmand[895]: plugins/wifi.c:network_added() 726976656e64656c6c_manag=
ed_psk<br>
> connmand[895]: plugins/wifi.c:network_added() 726976656e64656c6c_manag=
ed_psk<br>
> <br>
> The router uses 2412/5240/5825 (5825 is from 'ASUS Smart Connect&#=
39;) and the<br>
> repeater uses 2417/5500. I was much closer to the repeater than to the=
<br>
> router when running "connmand -n -d plugins/wifi.c".<br>
<br>
One thing you could try for a workaround is to change the frequency<br>
stored in the settings file. First stop ConnMan (because it will<br>
overwrite those files). Go to<br>
/var/lib/connman/wifi_xxxxxxx_726976656e64656c6c_managed_psk and edit<br>
the settings file. There should be a Frequency entry with 5240. What<br>
happens if you change this to 5500?<br></blockquote><div><br></div><div>Tha=
nks Daniel! Unfortunately, connman changes it automatically back to the rou=
ter lower 5Ghz wifi (5240).</div><div>Interestingly, the output of "co=
nnmand -n -d plugins/wifi.c" changed. It reports the repeaters 5Ghz wi=
fi, which I manually entered:</div><div><br></div><div>connmand[43097]: plu=
gins/wifi.c:get_latest_connections() ssid 726976656e64656c6c freq 5500 modi=
fied 1580261980</div><div>=C2=A0</div><div>But it still ends up using 5240 =
(and changes the settings file back to 5240).<br></div><div><br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">
> I also noticed, that not all SSIDs might have been listed:<br>
> connmand[895]: plugins/wifi.c:wifi_scan() max ssids 16<br>
> connmand[895]: plugins/wifi.c:add_scan_param() SSID<br>
> 5265736964656e6365496e6e5f4755455354 added to scanned list of 15 entri=
es<br>
<br>
wpa_supplicant exposes a lot of networking details and the wifi plugin<br>
in ConnMan has to do a lot of work. And I am not surprised this<br>
doesn't work as expected.<br>
<br>
Anyway, try the workaround to see if we are going into the right<br>
direction.<br>
<br>
Thanks,<br>
Daniel<br>
</blockquote></div></div>
--000000000000d88dd2059d3d8770--
------------------------------
Date: Wed, 29 Jan 2020 08:47:07 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Doesn't connect to strongest wifi
To: Torsten Wörtwein <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
Hi Torsten,
On Tue, Jan 28, 2020 at 08:47:48PM -0500, Torsten Wörtwein wrote:
> On Tue, Jan 28, 2020 at 2:47 AM Daniel Wagner <[email protected]> wrote:
> > One thing you could try for a workaround is to change the frequency
> > stored in the settings file. First stop ConnMan (because it will
> > overwrite those files). Go to
> > /var/lib/connman/wifi_xxxxxxx_726976656e64656c6c_managed_psk and edit
> > the settings file. There should be a Frequency entry with 5240. What
> > happens if you change this to 5500?
> >
>
> Thanks Daniel! Unfortunately, connman changes it automatically back to the
> router lower 5Ghz wifi (5240).
> Interestingly, the output of "connmand -n -d plugins/wifi.c" changed. It
> reports the repeaters 5Ghz wifi, which I manually entered:
>
> connmand[43097]: plugins/wifi.c:get_latest_connections() ssid
> 726976656e64656c6c freq 5500 modified 1580261980
>
> But it still ends up using 5240 (and changes the settings file back to
> 5240).
Too bad. I've got a setup with several APs spanning one network and
for me my device roams between the APs. I notice I don't see any of
the 'freq' debug messages. Any chance you could give the iwd plugin a
try? I really don't want to spend more time on wpa_supplicant.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 51, Issue 37
***************************************
