Re: NM and exposing bgscan roam threshold

On Tue, 2018-05-15 at 13:27 +0200, Shawn Adams wrote:

I see some great work in the latest 1.8.6 - thank you !!!

* Implemented support for Wi-Fi PMF (Protected Management Frames,
    802.11w), which can be configured via the wifi-sec.pmf property.

* Background scanning is now disabled for non-WPA-Enterprise Wi-Fi

* Always enable Proactive Key Caching (PKC, also called OKC) for WPA
    WiFi configurations

How feasible would it be to allow the user to use nm-cli or the UI to

the bgscan roam threshold ?

# read, set:

wpa_cli -p /run/wpa_supplicant -i wlan5 get_network 0 bgscan

wpa_cli -p /run/wpa_supplicant -i wlan5 set_network 0 bgscan


IMO, optimally this should not require configuration but works well by

Exposing a roam threashold seems much too specific. If at all, it
should be a more general option, that affects the eagerness to

But I am thinking, maybe we wouldn't want to configure this in the
connection profile either. Because during one associtaion, the user's
preferences might change (e.g. is he currently in a VOIP call, maybe
he wants to do less scanning and less roaming). This preference seems
volatile, meaning NetworkManager (and even more supplicant) should just
do the best possible job autonomously.

Of course, more concrete suggestions are welcome :)

Maybe you can elaborate on the issues that you have?


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]