On 9/26/21 1:41 AM, Per Jessen wrote:

Marc Chamberlin wrote:

...

So why am I now having to execute these manual steps after using Yast to set up wlan0? Can't say that looking through log files has been very helpful either and I am starting to get a bit out of my league here. I just want to be able to rely on Yast to set up my network interfaces. I haven't tried setting eth0 yet, will await for any helpful ideas first, before spinning my wheels with eth0.

Thanks as always, in advance, for any help offered, I much appreciate it especially when I have wandered off into some sort of quagmire like this issue that suddenly sprung up on me!     Marc C. Hi Marc,

you are really using YaST to manage your wicked config - essentially a text file:

/etc/sysconfig/network/ifcfg-wlan0

Let us the contents of that, maybe obscure the wifi password.

I think it might also be useful if you start with 'ifdown wlan0' so we have a known starting point. Then try to activate the network interface with 'ifup wlan0' and let us see what 'ip addr show dev wlan0' says after that.

If there is any problem connecting to the access point, 'dmesg' might show some interesting messages.

Thanks Per, and can do -

marcslaptop:/var/log # ifdown wlan0 wlan0           device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0' marcslaptop:/var/log # ifup wlan0 wlan0           setup-in-progress marcslaptop:/var/log # ip addr show dev wlan0 3: wlan0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000     link/ether e4:a7:a0:46:83:e0 brd ff:ff:ff:ff:ff:ff

The only thing dmesg shows that is related to the wi-fi wlan0 interface is -

[92283.790584] wlan0: deauthenticating from 98:de:d0:f9:93:ca by local choice (Reason: 3=DEAUTH_LEAVING) [92389.805091] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM [92389.979695] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM [92390.060594] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring

The MAC address 98:de:d0:f9:93:ca is for the 'ChamberlinCupola' access point.      HTH's to understand what is going on with my wlan0 setup process...   Marc -- *"The Truth is out there" - Spooky* *_   _   .   .   .       .   .   .   _   _       .   _   _   _   _   .       .   .   .           _   .   .       .           .   _   _       .   _       _   _   .   .   .       .   _   _   .       _   .   .   _       .   _   _           _   _       .   _       .   _   .       _   .   _   . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)

On Mon, Sep 27, 2021 at 10:14 AM Per Jessen wrote:

Marc Chamberlin wrote:

...

Thanks Per, and can do -

...

marcslaptop:/var/log # ifdown wlan0 wlan0 device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0'

Comparing to one of my systems with wicked and wifi - I have WIRELESS_AP_SCANMODE='1'

That sounds quite probable. From the man page Mode 0 means the driver performs the scan. Mode 1 means wpa_supplicant takes care of scanning. Mode 2 is basically the same as mode 0 but the access point gets chosen by security policy and SSID. This mode does not support multiple network settings. Default is 1 for most drivers. Usually scanning is controlled by network management programs. I wonder if there are any drivers that perform periodical scans automatically. And even if they do, what is the interval between these scans?

Marc Chamberlin wrote:

So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? 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 guess we ought to ask where that default value comes from? I compared to my settings on a Nano Pi Neo Air, where the wifi is an AP6212 (IIRC). -- Per Jessen, Zürich (20.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.

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.    Marc...

...

Feels like we are starting to make progress on solving this issue! I will look forward to hearing additional thoughts, Thanks again for your help and insights.   Marc...

-- *"The Truth is out there" - Spooky* *_   _   .   .   .       .   .   .   _   _       .   _   _   _   _   .       .   .   .           _   .   .       .           .   _   _       .   _       _   _   .   .   .       .   _   _   .       _   .   .   _       .   _   _           _   _       .   _       .   _   .       _   .   _   . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)

Hello, In the Message; Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <58194721-2c59-2a7f-057e-ed3182f2f464@marcchamberlin.com> Date & Time: Sun, 26 Sep 2021 18:10:38 -0700 [MC] == Marc Chamberlin has written: [...] MC> Thanks Masaru for the suggestion, it was a good idea, but still no joy. MC> resolve.conf looks just fine and hasn't changed on my laptop for a long MC> time. I did double check to make sure my own DNS servers are running, MC> both are and report no issues. Same for my DHCPD server, no issues, nor MC> does it report, in it's log file, that an attempt was made to get an IP MC> address from/for my laptop, when my laptop fails to set up wlan0 properly. MC> What seems odd to me is that just executing - MC> > iwlist wlan0 scan MC> i.e. simply doing a scan for APs is enough to often setup wlan0 and MC> retrieve an IP address from my DHCPD server! Which service are you using, wicked or NetworkManager? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."

Hello, In the Message; Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : Date & Time: Sun, 26 Sep 2021 19:58:40 -0700 [MC] == Marc Chamberlin has written: [...] MC> Thanks again Masaru with another good question that I should have MC> stated. I am using Wicked.    Marc.... Thanks. Have you checked the status of mac address randomization in Android? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'

On 9/27/21 4:39 AM, Masaru Nomiya wrote:

Hello,

In the Message;

Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <87mtnye0be.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Mon, 27 Sep 2021 20:15:49 +0900

[MN] == Masaru Nomiya has written:

MN> Hello,

MN> In the Message;

MN> Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. MN> Message-ID : MN> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700

MN> [MC] == Marc Chamberlin has written:

MN> [...] MC> My problem began with either one of two events, the first being I had MC> just updated my laptop with a bunch of updates, didn't keep track of MC> what was installed, and cannot say for certain that the updates are the MC> culprit.

MN> Could you show the result of;

MN> $ rpm -qa --last | grep "Fri Sep 24"

MN> Regards, and Good Night

If you updated on Sep 25, please execute as follows;

$ rpm -qa --last | grep "Sat Sep 25"

Regards. Hello again Masaru,  I got no results from the queries you suggested so I did a more general query and this is the results -

marcslaptop:/var/log # rpm -qa --last | grep "Fri Sep 24" marcslaptop:/var/log # rpm -qa --last | grep "Sat Sep 25" marcslaptop:/var/log # rpm -qa --last | more xen-libs-4.13.3_04-lp152.2.30.1.x86_64        Wed 22 Sep 2021 01:30:33 PM PDT chromium-93.0.4577.82-lp152.2.125.1.x86_64    Wed 22 Sep 2021 01:30:31 PM PDT x11-video-nvidiaG05-470.74-lp152.44.1.x86_64  Wed 22 Sep 2021 01:29:52 PM PDT nvidia-computeG05-470.74-lp152.44.1.x86_64    Wed 22 Sep 2021 01:28:40 PM PDT nvidia-glG05-470.74-lp152.44.1.x86_64         Wed 22 Sep 2021 01:28:30 PM PDT nvidia-gfxG05-kmp-default-470.74_k5.3.18_lp152.19-lp152.44.1.x86_64 Wed 22 Sep 2021 01:15:58 PM PDT java-11-openjdk-11.0.12.0-lp152.2.18.1.x86_64 Tue 21 Sep 2021 02:20:08 PM PDT java-11-openjdk-headless-11.0.12.0-lp152.2.18.1.x86_64 Tue 21 Sep 2021 02:20:05 PM PDT libsoftokn3-hmac-3.68-lp152.2.10.1.x86_64     Tue 21 Sep 2021 02:19:16 PM PDT mozilla-nss-3.68-lp152.2.10.1.x86_64          Tue 21 Sep 2021 02:19:15 PM PDT xorg-x11-fonts-legacy-7.6-lp152.7.6.1.noarch  Tue 21 Sep 2021 02:19:14 PM PDT libsoftokn3-3.68-lp152.2.10.1.x86_64          Tue 21 Sep 2021 02:18:42 PM PDT yast2-country-4.2.23-lp152.2.9.1.x86_64       Tue 21 Sep 2021 02:18:37 PM PDT xorg-x11-fonts-7.6-lp152.7.6.1.noarch         Tue 21 Sep 2021 02:18:36 PM PDT mozilla-nss-certs-3.68-lp152.2.10.1.x86_64    Tue 21 Sep 2021 02:18:33 PM PDT yast2-country-data-4.2.23-lp152.2.9.1.x86_64  Tue 21 Sep 2021 02:18:32 PM PDT xorg-x11-fonts-core-7.6-lp152.7.6.1.noarch    Tue 21 Sep 2021 02:18:32 PM PDT libfreebl3-hmac-3.68-lp152.2.10.1.x86_64      Tue 21 Sep 2021 02:18:32 PM PDT xorg-x11-fonts-converted-7.6-lp152.7.6.1.noarch Tue 21 Sep 2021 02:18:28 PM PDT mozilla-nspr-4.32-lp152.2.6.1.x86_64          Tue 21 Sep 2021 02:18:22 PM PDT libfreebl3-3.68-lp152.2.10.1.x86_64           Tue 21 Sep 2021 02:18:22 PM PDT libcroco-0_6-3-0.6.13-lp152.2.3.1.x86_64      Tue 21 Sep 2021 02:18:20 PM PDT fonttosfnt-1.1.0-lp152.2.5.1.x86_64           Tue 21 Sep 2021 02:18:20 PM PDT PackageKit-lang-1.1.13-lp152.3.27.1.noarch    Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-gtk3-module-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-gstreamer-plugin-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-backend-zypp-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:36 AM PDT PackageKit-1.1.13-lp152.3.27.1.x86_64         Sat 18 Sep 2021 09:40:36 AM PDT nvme-cli-1.10-lp152.2.18.1.x86_64             Sat 18 Sep 2021 09:40:35 AM PDT libpackagekit-glib2-18-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:35 AM PDT wireshark-ui-qt-3.4.7-lp152.2.18.1.x86_64     Fri 17 Sep 2021 07:20:40 AM PDT wireshark-3.4.7-lp152.2.18.1.x86_64           Fri 17 Sep 2021 07:20:39 AM PDT libwireshark14-3.4.7-lp152.2.18.1.x86_64      Fri 17 Sep 2021 07:20:37 AM PDT libwiretap11-3.4.7-lp152.2.18.1.x86_64        Fri 17 Sep 2021 07:20:30 AM PDT ghostscript-x11-9.52-lp152.2.7.1.x86_64       Fri 17 Sep 2021 07:20:29 AM PDT yast2-users-4.2.13-lp152.2.6.1.x86_64         Fri 17 Sep 2021 07:20:28 AM PDT libwsutil12-3.4.7-lp152.2.18.1.x86_64         Fri 17 Sep 2021 07:20:28 AM PDT ghostscript-9.52-lp152.2.7.1.x86_64           Fri 17 Sep 2021 07:20:27 AM PDT autoyast2-installation-4.2.55-lp152.2.15.1.noarch Wed 15 Sep 2021 10:59:52 PM PDT yast2-installation-4.2.53-lp152.2.21.1.noarch Wed 15 Sep 2021 10:59:46 PM PDT kernel-default-devel-5.3.18-lp152.92.2.x86_64 Wed 15 Sep 2021 10:59:45 PM PDT yast2-4.2.95-lp152.2.31.1.x86_64              Wed 15 Sep 2021 10:59:40 PM PDT kernel-devel-5.3.18-lp152.92.2.noarch         Wed 15 Sep 2021 10:59:39 PM PDT yast2-logs-4.2.95-lp152.2.31.1.x86_64         Wed 15 Sep 2021 10:59:28 PM PDT libcares2-1.17.1+20200724-lp152.2.12.1.x86_64 Wed 15 Sep 2021 10:59:28 PM PDT kernel-macros-5.3.18-lp152.92.2.noarch        Wed 15 Sep 2021 10:59:27 PM PDT kernel-default-5.3.18-lp152.92.2.x86_64       Wed 15 Sep 2021 10:58:36 PM PDT cronie-1.5.1-lp152.7.3.1.x86_64               Tue 14 Sep 2021 10:25:13 PM PDT netcfg-11.6-lp152.4.3.1.noarch                Tue 14 Sep 2021 10:25:12 PM PDT gcc-7-lp152.5.6.1.x86_64                      Tue 14 Sep 2021 10:25:12 PM PDT libaom0-1.0.0-lp152.3.3.1.x86_64              Tue 14 Sep 2021 10:25:11 PM PDT cron-4.2-lp152.7.3.1.x86_64                   Tue 14 Sep 2021 10:25:10 PM PDT cpp-7-lp152.5.6.1.x86_64                      Tue 14 Sep 2021 10:25:09 PM PDT openssl-1_1-1.1.1d-lp152.7.24.1.x86_64        Sun 12 Sep 2021 09:07:08 PM PDT libopenssl1_1-32bit-1.1.1d-lp152.7.24.1.x86_64 Sun 12 Sep 2021 09:07:06 PM PDT libopenssl1_1-1.1.1d-lp152.7.24.1.x86_64      Sun 12 Sep 2021 09:07:04 PM PDT hwdata-0.351-lp152.2.15.1.noarch              Fri 10 Sep 2021 10:01:56 PM PDT ntfs-3g-2021.8.22-lp152.5.3.1.x86_64          Thu 09 Sep 2021 09:28:06 PM PDT ntfsprogs-2021.8.22-lp152.5.3.1.x86_64        Thu 09 Sep 2021 09:28:05 PM PDT libntfs-3g87-2021.8.22-lp152.5.3.1.x86_64     Thu 09 Sep 2021 09:28:04 PM PDT yast2-update-4.2.22-lp152.2.10.1.x86_64       Tue 07 Sep 2021 05:48:16 PM PDT libpcre2-8-0-10.31-lp152.4.3.1.x86_64         Tue 07 Sep 2021 05:48:13 PM PDT libpcre2-16-0-10.31-lp152.4.3.1.x86_64        Tue 07 Sep 2021 05:48:12 PM PDT libesmtp-1.0.6-lp152.4.3.1.x86_64             Tue 07 Sep 2021 05:48:12 PM PDT libxerces-c-3_1-3.1.4-lp152.5.3.1.x86_64      Mon 06 Sep 2021 02:14:47 PM PDT HTHs   Marc

--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'

-- *"The Truth is out there" - Spooky* *_   _   .   .   .       .   .   .   _   _       .   _   _   _   _   .       .   .   .           _   .   .       .           .   _   _       .   _       _   _   .   .   .       .   _   _   .       _   .   .   _       .   _   _           _   _       .   _       .   _   .       _   .   _   . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)