[oS-en] What can cause NM to choose the worse WiFi signal available?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was trying to watch a video, old laptop connected to the sitting room TV, but VLC was having trouble, then NFS having trouble, not mounting the share, then sshfs also having trouble... (with a reboot in the middle, and an update yesterday). Then I notice that NM applet indicate an horrible signal level. This is daft, the laptop sits 2 metres away from the house router with a perfect signal, yet it connects to the other WiFi on the house level above, terrible signal. Why would it do that? The machine is still on Leap 15.4, but has been running perfect for months. I just hibernated after each video session, no trouble, NFS working reliably. I just did run an update yesterday, and NFS was not automatically up after reboot. Did not occur to me to check the WiFi. Why would NFS not switch over automatically to a much better signal? - -- Cheers Carlos E. R. (from 15.5 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZeeWGhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVDfMAnR8zCF6izRnBWA2D0/pM SNqquvPrAKCRHmk8SorhoQPVyrr0QubMOyRvSg== =6kwQ -----END PGP SIGNATURE-----
On Tue, 5 Mar 2024 23:00:58 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Why would NFS not switch over automatically to a much better signal?
Go to sleep and wake up with a fresh mind. NFS doesn't know anything about the network connection except whether it works at the moment. It's never even heard of wi-fi.
On 2024-03-06 01:49, Dave Howorth wrote:
On Tue, 5 Mar 2024 23:00:58 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Why would NFS not switch over automatically to a much better signal?
Go to sleep and wake up with a fresh mind. NFS doesn't know anything about the network connection except whether it works at the moment. It's never even heard of wi-fi.
I'm not asking about NFS. I'm asking why NM chooses a connection that has a terrible signal when there is another one with a wonderful signal. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 06.03.2024 05:09, Carlos E. R. wrote:
On 2024-03-06 01:49, Dave Howorth wrote:
On Tue, 5 Mar 2024 23:00:58 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Why would NFS not switch over automatically to a much better signal?
Go to sleep and wake up with a fresh mind. NFS doesn't know anything about the network connection except whether it works at the moment. It's never even heard of wi-fi.
I'm not asking about NFS. I'm asking why NM chooses a connection that has a terrible signal when there is another one with a wonderful signal.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/474
On 2024-03-06 05:23, Andrei Borzenkov wrote:
On 06.03.2024 05:09, Carlos E. R. wrote:
On 2024-03-06 01:49, Dave Howorth wrote:
On Tue, 5 Mar 2024 23:00:58 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Why would NFS not switch over automatically to a much better signal?
Go to sleep and wake up with a fresh mind. NFS doesn't know anything about the network connection except whether it works at the moment. It's never even heard of wi-fi.
I'm not asking about NFS. I'm asking why NM chooses a connection that has a terrible signal when there is another one with a wonderful signal.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/474
Interesting, thanks. Yes, the AP upstairs has bigger bandwidth. I'm looking at the downstairs router, and for bandwidth it says "20 Mhz in coexistence". The alternative is "20/40 Mhz in coexistence". I'll switch to the later. No idea what coexistence may be. (It has 5Ghz, but the laptop doesn't). -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
In data martedì 5 marzo 2024 23:00:58 CET, Carlos E. R. ha scritto:
Hi,
I was trying to watch a video, old laptop connected to the sitting room TV, but VLC was having trouble, then NFS having trouble, not mounting the share, then sshfs also having trouble... (with a reboot in the middle, and an update yesterday). Then I notice that NM applet indicate an horrible signal level.
This is daft, the laptop sits 2 metres away from the house router with a perfect signal, yet it connects to the other WiFi on the house level above, terrible signal.
Why would it do that?
The machine is still on Leap 15.4, but has been running perfect for months. I just hibernated after each video session, no trouble, NFS working reliably. I just did run an update yesterday, and NFS was not automatically up after reboot. Did not occur to me to check the WiFi.
Why would NFS not switch over automatically to a much better signal?
-- Cheers
Carlos E. R. (from 15.5 x86_64 at Telcontar) Networkmanager does actually not connect to the strongest signal, but to the first signal. If you have memorized the wlan emitters in your NM the first thing it looks at is priority. Provided you have not given ANY priority, any of the WLANs you are registered to will connect. Once it is connected it will not automatically change to the a new stronger one. Such a highjacking would also not be desirable, imagine somebody who spoofs a SSID and does it with a higher signal strengths would highjack your NM to disconnect and re-connect to it to eavesdrop on it. If NM begins the frequency scan with 2.4 gHz and your best signal is 5 then tough luck.
If you did instead give priorities, it will first scan for the WLAN with the highest priority. If not available it will switch downward until it reaches the last available with the lowest priority in the list. For what I know NW is not able to choose by signal strength, prioritizing for it, if your priority settings are all set to zero. I actually do not consider this a bug. It is more of a choice or a feature to be enhanced.
On 2024-03-06 09:17, Stakanov via openSUSE Users wrote:
In data martedì 5 marzo 2024 23:00:58 CET, Carlos E. R. ha scritto:
Hi,
I was trying to watch a video, old laptop connected to the sitting room TV, but VLC was having trouble, then NFS having trouble, not mounting the share, then sshfs also having trouble... (with a reboot in the middle, and an update yesterday). Then I notice that NM applet indicate an horrible signal level.
This is daft, the laptop sits 2 metres away from the house router with a perfect signal, yet it connects to the other WiFi on the house level above, terrible signal.
Why would it do that?
The machine is still on Leap 15.4, but has been running perfect for months. I just hibernated after each video session, no trouble, NFS working reliably. I just did run an update yesterday, and NFS was not automatically up after reboot. Did not occur to me to check the WiFi.
Why would NFS not switch over automatically to a much better signal?
errata: NM, obviously.
Networkmanager does actually not connect to the strongest signal, but to the first signal. If you have memorized the wlan emitters in your NM the first thing it looks at is priority. Provided you have not given ANY priority, any of the WLANs you are registered to will connect. Once it is connected it will not automatically change to the a new stronger one. Such a highjacking would also not be desirable, imagine somebody who spoofs a SSID and does it with a higher signal strengths would highjack your NM to disconnect and re-connect to it to eavesdrop on it.
The password would not match.
If NM begins the frequency scan with 2.4 gHz and your best signal is 5 then tough luck.
I noticed my other laptop chose one or the other randomly.
If you did instead give priorities, it will first scan for the WLAN with the highest priority. If not available it will switch downward until it reaches the last available with the lowest priority in the list.
I didn't set priorities, as far as I remember, no reason to.
For what I know NW is not able to choose by signal strength, prioritizing for it, if your priority settings are all set to zero. I actually do not consider this a bug. It is more of a choice or a feature to be enhanced.
It may be bandwidth. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
In data mercoledì 6 marzo 2024 13:55:32 CET, Carlos E. R. ha scritto:
On 2024-03-06 09:17, Stakanov via openSUSE Users wrote:
In data martedì 5 marzo 2024 23:00:58 CET, Carlos E. R. ha scritto:
I didn't set priorities, as far as I remember, no reason to.
For what I know NW is not able to choose by signal strength, prioritizing for
it, if your priority settings are all set to zero.
I actually do not consider this a bug. It is more of a choice or a feature to be enhanced.
It may be bandwidth.
-- Cheers / Saludos,
Carlos E. R. (from 15.5 x86_64 at Telcontar)
At home here I tried with priorities. Works flawlessly, I priorized the 5G networks but the 2.4 connect thereafter when the first for some reason are not reachable. So I would try priorities anyway (provide your asset benefits (more than one SSID, not a mesh etc.
When I first saw this thread my first thought was, "What can cause New Mexico to choose the worst WiFi signal available?" -- God is Great Beer is good Liberals are crazy!
participants (5)
-
Andrei Borzenkov -
Bill Walsh -
Carlos E. R. -
Dave Howorth -
Stakanov