On 28.09.2021 01:45, Marc Chamberlin wrote:
On 9/27/21 11:51 AM, Andrei Borzenkov wrote:
So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? For all I can tell default in YaST is "1", at least when support for
On 27.09.2021 19:13, Marc Chamberlin wrote: this variable was originally introduced and in current code.
Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent?
I am not sure I understand it. Do you mean that setting it to "1" is not persistent?
Correct Andrie, each time I start up Yast, and go into Network Settings, I find that the WIRELESS_AP_SCANMODE is set to zero (0) which makes it seem like that is the default value, and my having previously set it to one (1) is not persistent.
I can confirm it on 15.2 - editing wireless interface resets scan mode to 0 (new interface defaults to 1). Seeing that Leap 15.2 is near end of support and this problem is no more present in 15.3 I am not sure bug report makes much sense.