8:17 p.m.
Hi,
I have one router which broadcasts 2GHz and 5GHz on the same SSID with the
same security settings. I also have a repeater which does exactly the same
(2+5Ghz, same SSID as the router, and same security settings as the
router). I have one visible entry in connman which merges all four of these
wifis.
Connman always connects to the router, even when the signal of the repeater
is much stronger. It would be great if connman would connect to the
stronger wifi source.
I'm running ArchLinux with connman 1.37, WPA-supplicant 2.9, and kernel
4.19.98. Please let me know how I can provide more useful information about
this issue.
Thanks,
Torsten
11:20 a.m.
Hi,
On Sun, Jan 26, 2020 at 09:17:43PM -0500, Torsten Wörtwein wrote:
I have one router which broadcasts 2GHz and 5GHz on the same SSID
with the
same security settings. I also have a repeater which does exactly the same
(2+5Ghz, same SSID as the router, and same security settings as the
router). I have one visible entry in connman which merges all four of these
wifis.
Connman always connects to the router, even when the signal of the repeater
is much stronger. It would be great if connman would connect to the
stronger wifi source.
I'm running ArchLinux with connman 1.37, WPA-supplicant 2.9, and kernel
4.19.98. Please let me know how I can provide more useful information about
this issue.
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.
I see that the Scan method has a 'AllowRoam' parameter [1]. Not sure if
that needs to be set in order to let wpa_supplicant automatically
roam. At least in the current version of ConnMan we don't set it.
Thanks,
Daniel
[1] https://w1.fi/wpa_supplicant/devel/dbus.html
8:35 p.m.
On Mon, Jan 27, 2020 at 12:20 PM Daniel Wagner <wagi(a)monom.org> wrote:
Hi,
On Sun, Jan 26, 2020 at 09:17:43PM -0500, Torsten Wörtwein wrote:
> I have one router which broadcasts 2GHz and 5GHz on the same SSID with
the
> same security settings. I also have a repeater which does exactly the
same
> (2+5Ghz, same SSID as the router, and same security settings as the
> router). I have one visible entry in connman which merges all four of
these
> wifis.
>
> Connman always connects to the router, even when the signal of the
repeater
> is much stronger. It would be great if connman would connect to the
> stronger wifi source.
>
> I'm running ArchLinux with connman 1.37, WPA-supplicant 2.9, and kernel
> 4.19.98. Please let me know how I can provide more useful information
about
> this issue.
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".
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 entries
I see that the Scan method has a 'AllowRoam' parameter [1]. Not sure if
that needs to be set in order to let wpa_supplicant automatically
roam. At least in the current version of ConnMan we don't set it.
Thanks,
Daniel
[1] https://w1.fi/wpa_supplicant/devel/dbus.html
I would be happy to test a patch :) I'm sorry, I'm not familiar enough
with the connman code base.
Thanks,
Torsten
1:47 a.m.
Hi Torsten,
On Mon, Jan 27, 2020 at 09:35:49PM -0500, Torsten Wörtwein wrote:
On Mon, Jan 27, 2020 at 12:20 PM Daniel Wagner <wagi(a)monom.org>
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?
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 entries
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
7:47 p.m.
On Tue, Jan 28, 2020 at 2:47 AM Daniel Wagner <wagi(a)monom.org> wrote:
Hi Torsten,
On Mon, Jan 27, 2020 at 09:35:49PM -0500, Torsten Wörtwein wrote:
> On Mon, Jan 27, 2020 at 12:20 PM Daniel Wagner <wagi(a)monom.org> 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 entries
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
1:47 a.m.
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 <wagi(a)monom.org>
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
5:04 p.m.
Hi Daniel,
On Wed, Jan 29, 2020 at 2:47 AM Daniel Wagner <wagi(a)monom.org> wrote:
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 <wagi(a)monom.org> 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.
I started IWD with
sudo /usr/lib/iwd/iwd -d
it then 'magically' (without connman) connected to the wifi - I assume it
reads connman's settings for that. IWD found all five wifis:
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:69'
with SSID: rivendell, freq: 5825, rank: 5932, strength: -6400
src/station.c:station_add_seen_bss() Processing BSS 'fa:1a:67:32:fa:1f'
with SSID: rivendell, freq: 2417, rank: 4707, strength: -3900
src/station.c:station_add_seen_bss() Processing BSS 'fa:1a:67:32:fa:20'
with SSID: rivendell, freq: 5500, rank: 4321, strength: -4400
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:61'
with SSID: rivendell, freq: 2427, rank: 4306, strength: -5500
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:65'
with SSID: rivendell, freq: 5240, rank: 2999, strength: -7000
src/station.c:station_autoconnect_next() Considering autoconnecting to BSS
'04:d9:f5:26:4f:69' with SSID: rivendell, freq: 5825, rank: 5932, strength:
-6400
5500 and 2417 should be the repeater, to which I was closer at the moment.
But it decided to connect to the router's high 5Ghz network.
And then started connmand:
sudo connmand -n -d plugins/iwd.c --wifi=iwd_agent
** (connmand:1923): WARNING **: 17:38:47.484: error
fi.w1.wpa_supplicant1.UnknownError
It didn't print any frequency information.
IWD seems to occasionally roam between the wifis :) For a brief period it
picked 2417. Overall it highly prefers 5825 even if that is the farthest
one away (to be fair, it worked - I didn't encounter connection issues).
Thanks,
Torsten
6:47 a.m.
Hi Torsten,
On Wed, Jan 29, 2020 at 06:04:07PM -0500, Torsten Wörtwein wrote:
I started IWD with
sudo /usr/lib/iwd/iwd -d
it then 'magically' (without connman) connected to the wifi - I assume it
reads connman's settings for that.
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.
IWD found all five wifis:
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:69'
with SSID: rivendell, freq: 5825, rank: 5932, strength: -6400
src/station.c:station_add_seen_bss() Processing BSS 'fa:1a:67:32:fa:1f'
with SSID: rivendell, freq: 2417, rank: 4707, strength: -3900
src/station.c:station_add_seen_bss() Processing BSS 'fa:1a:67:32:fa:20'
with SSID: rivendell, freq: 5500, rank: 4321, strength: -4400
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:61'
with SSID: rivendell, freq: 2427, rank: 4306, strength: -5500
src/station.c:station_add_seen_bss() Processing BSS '04:d9:f5:26:4f:65'
with SSID: rivendell, freq: 5240, rank: 2999, strength: -7000
src/station.c:station_autoconnect_next() Considering autoconnecting to BSS
'04:d9:f5:26:4f:69' with SSID: rivendell, freq: 5825, rank: 5932, strength:
-6400
5500 and 2417 should be the repeater, to which I was closer at the moment.
But it decided to connect to the router's high 5Ghz network.
If you are interested to see what's going on between iwd and the kernel
driver you can start the excellent iwmon by the iwd project.
And then started connmand:
sudo connmand -n -d plugins/iwd.c --wifi=iwd_agent
'--wifi=iwd_agent' doesn't really make anything. The '--wifi' option
is there to switch between the two APIs which wpa_supplicant
supports. So either nl80211 or WEXT. It doesn't do anything for the
iwd plugin.
** (connmand:1923): WARNING **: 17:38:47.484: error
fi.w1.wpa_supplicant1.UnknownError
The wifi plugin should not run. That means wpa_supplicant might run in
the background. Shutdown wpa_supplicant and block it from auto
start. systemd might do something in the background.
Furthermore, you should propably disable the wifi plugin at boot up or
just don't enable it during build time.
wpa_supplicant and iwd should never run at the same time.
It didn't print any frequency information.
IWD seems to occasionally roam between the wifis :) For a brief period it
picked 2417. Overall it highly prefers 5825 even if that is the farthest
one away (to be fair, it worked - I didn't encounter connection issues).
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.
Thanks,
Daniel
1:46 a.m.
Hi Daniel,
On Sun, Feb 2, 2020 at 7:47 AM Daniel Wagner <wagi(a)monom.org> 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
3:48 a.m.
On Mon, Feb 03, 2020 at 02:46:58AM -0500, Torsten Wörtwein wrote:
Hi Daniel,
On Sun, Feb 2, 2020 at 7:47 AM Daniel Wagner <wagi(a)monom.org> 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.
That explains it. iwd stores the credentials and that's why it was
able to auto connect.
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 :)
It's alright. Replacing wpa_supplicant with iwd is a win :)
Thanks,
Daniel
360
days inactive
367
days old
9 comments
2 participants
participants (2)
-
Daniel Wagner -
Torsten Wörtwein