Bug 1166933

With "the interface not running" i meant that after a reboot it didn't come up.

The patch that installed the failing wpa_supplicant version references bug 
1165266 (bugzilla)

(In reply to Gerben Jansen from comment #2)
> The patch that installed the failing wpa_supplicant version references bug 
> 1165266 (bugzilla)

It must be reverted. This is absolutely wrong.

(In reply to Gerben Jansen from comment #0)
Please show the output of the wpa_supplicant error with which it does not start and the output of "ip addr" after that.

Created attachment 833572 [details]
output of journalctl -b

I am not the original reporter, but as I was having the same problem I can supply the needed details. Full output of 'journalctl -b' is in previous comment, relevant lines to me seem to be the following:


Mar 22 10:02:09 susa dbus-daemon[936]: [system] Activating via systemd: service name='fi.epitest.hostap.WPASupplicant' unit='wpa_supplicant.service' requested by ':1.15' (uid=0 pid=1008 comm="/usr/sbin/wickedd --systemd --foreground ")
Mar 22 10:02:34 susa dbus-daemon[936]: [system] Failed to activate service 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms)
Mar 22 10:02:34 susa wickedd[1008]: ni_wpa_interface_bind(wlan0): Operation not permitted
Mar 22 10:02:34 susa wickedd[1008]: wpa_supplicant doesn't know interface wlan0
Mar 22 10:02:34 susa wickedd-nanny[1042]: device wlan0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
Mar 22 10:02:34 susa wickedd-nanny[1042]: wlan0: failed to bring up device, still continuing
Mar 22 10:02:35 susa kernel: r8169 0000:02:00.0 eth0: link down
Mar 22 10:02:39 susa wicked[1118]: lo              up
Mar 22 10:02:39 susa wicked[1118]: eth0            setup-in-progress
Mar 22 10:02:39 susa wicked[1118]: wlan0           device-not-running
Mar 22 10:02:39 susa systemd[1]: Started wicked managed network interfaces.
Mar 22 10:02:39 susa systemd[1]: Reached target Network.
Mar 22 10:02:39 susa systemd[1]: Starting WPA Supplicant daemon...
Mar 22 10:02:39 susa systemd[1]: Started WPA Supplicant daemon.


And output of 'ip addr':

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:24:8c:75:57:96 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f8:1a:67:19:40:24 brd ff:ff:ff:ff:ff:ff


I apologise for possible poor formatting of this comment.

(In reply to Toomas Aas from comment #6)
Thank you for the information.
I am surprised at the old name of network interfaces.
Is this so default in Leap?

> Is this so default in Leap?
Yes, mine is called wlan1 because i had the same troubles starting up the interface some months ago. After fixing that, mine was called wlan1 (instead of wlan0)

I have 2 files, both create with: wpa-log.sh

wpa.ok is its result right after booting with wpa_supplicant-2.6-lp151.4.4.x86_64,
wpa.fail with wpa_supplicant-2.6-lp151.5.3.1.x86_64

After installing wpa_supplicant-2.6-lp151.5.3.1.x86_64, i already had lost my wifi network, i rebooted my laptop (which took longer than usual) and ran the wpa-log.sh script.

Created attachment 833574 [details]
wpa-log.sh

Created attachment 833575 [details]
wpa.ok

Created attachment 833576 [details]
wpa.fail

(In reply to Toomas Aas from comment #6)
> Mar 22 10:02:34 susa dbus-daemon[936]: [system] Failed to activate service
> 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms)

Direct consequence of After=network.target on system boot.

...
> Mar 22 10:02:39 susa systemd[1]: Started wicked managed network interfaces.
> Mar 22 10:02:39 susa systemd[1]: Reached target Network.
> Mar 22 10:02:39 susa systemd[1]: Starting WPA Supplicant daemon...
> Mar 22 10:02:39 susa systemd[1]: Started WPA Supplicant daemon.
> 

Now it is started but it is too late.

(In reply to Gerben Jansen from comment #11)
> Created attachment 833576 [details]
> wpa.fail

I think I found a general solution.
If I understood correctly, wicked only uses the file "wpa_supplicant.service", while systemd-networkd uses "wpa_supplicant @ .service".

The solution is obvious.

In wpa_supplicant.service
Before=network.target
After=dbus.service


In wpa_supplicant@.service
After=dbus.service network.target

The problem is that I just couldn't get wicked + wpa_suplicant to work in Tumbleweed.

dbus-daemon[629]: [system] Activating via systemd: service name='fi.epitest.hostap.WPASupplicant' unit='wpa_supplicant.service' requested by ':1.13' (uid=0 pid=778 comm="/usr/sbin/wickedd --systemd --foreground ")
systemd[1]: Starting WPA Supplicant daemon...
systemd[1]: Started WPA Supplicant daemon.
systemd[1]: systemd-rfkill.service: Succeeded.
nscd: 650 проверяется отслеживаемый файл «/etc/services»: Нет такого файла или каталога
dbus-daemon[629]: [system] Failed to activate service 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms)
wickedd[778]: ni_wpa_interface_bind(wlo1): Operation not permitted
wickedd[778]: wpa_supplicant doesn't know interface wlo1
wickedd-nanny[782]: device wlo1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
wickedd-nanny[782]: wlo1: failed to bring up device, still continuing
kernel: [   62.843162] RTL8211B Gigabit Ethernet r8169-300:00: attached PHY driver [RTL8211B Gigabit Ethernet] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
kernel: [   62.993007] r8169 0000:03:00.0 enp3s0: Link is Down
wicked[783]: enp3s0          setup-in-progress
wicked[783]:
If it doesn’t help right away, try rebooting and trying to configure wi-fi again. wlo1            device-not-running

Although without wicked it starts up and works great!

Please check my theory.
1 Install the wpa_supplicant-2.6-lp151.5.3.1.x86_64.rpm package (which faild).
2 edit the file "sudo vim /usr/lib/systemd/system/wpa_supplicant.service"
Before=network.target
After=dbus.service
3 sudo systemctl daemon-reexec
4 sudo systemctl restart wpa_supplicant network

If it doesn’t help right away, try rebooting and trying to configure wi-fi again and tell me about the result.

(In reply to Илья Индиго from comment #13)
> 
> The problem is that I just couldn't get wicked + wpa_suplicant to work in
> Tumbleweed.
> 

https://bugzilla.opensuse.org/show_bug.cgi?id=1167325

I think so, wicked, with this principle of operation, can not change the Mac-Address of the wireless interface (LLADDR)?
And does it suit everyone?

I sent SR to main project.
https://build.opensuse.org/request/show/787244

> In wpa_supplicant.service
> Before=network.target
> After=dbus.service
>
> In wpa_supplicant@.service
> After=dbus.service network.target

wpa_supplicant.service already had that string,, added "network.target" to wpa_supplicant@.service

Installed version 2.6-lp151.5.3.1-x86_64 and typed "reboot"

System hung on shutdown, so i had to hard-power it off.

Next on startup the interface was still not working.

(In reply to Gerben Jansen from comment #17)
> > In wpa_supplicant.service
> > Before=network.target
> > After=dbus.service
> >
> > In wpa_supplicant@.service
> > After=dbus.service network.target
> 
> wpa_supplicant.service already had that string,, added "network.target" to
> wpa_supplicant@.service
> 
> Installed version 2.6-lp151.5.3.1-x86_64 and typed "reboot"
> 
> System hung on shutdown, so i had to hard-power it off.
> 
> Next on startup the interface was still not working.

Ok, try change both files wpa_supplicant.service and wpa_supplicant@.service to

Before=network.target
After=dbus.service

And reboot.

(In reply to Илья Индиго from comment #15)
> I think so, wicked, with this principle of operation, can not change the
> Mac-Address of the wireless interface (LLADDR)?

It can.

(In reply to Илья Индиго from comment #18)
> (In reply to Gerben Jansen from comment #17)
> > > In wpa_supplicant.service
> > > Before=network.target
> > > After=dbus.service
> > >
> > > In wpa_supplicant@.service
> > > After=dbus.service network.target
> > 
> > wpa_supplicant.service already had that string,, added "network.target" to
> > wpa_supplicant@.service
> > 
> > Installed version 2.6-lp151.5.3.1-x86_64 and typed "reboot"
Something is wrong.

In lp151.5.3.1
Both files must be with
After = dbus.service network.target

In lp151.4.4 both files must be with
Before = network.target
After = dbus.service

Either you were mistaken when you answered, or you did something wrong. (Your package did not install normally and did not overwrite the files)

This is the only difference between these versions, I do not understand why it did not work for you.

(In reply to Илья Индиго from comment #13)
> If I understood correctly,

You did not.

> wicked only uses the file
> "wpa_supplicant.service",

No, wicked is using D-Bus service. Wicked neither knows nor cares how this D-Bus service became available. 

> while systemd-networkd uses "wpa_supplicant @
> .service".
> 

systemd-networkd neither knows nor cares about wpa_supplicant at all. It does not communicate with wpa_supplicant, nor does it attempt to start any service related to wpa_supplicant. Its job begins when wireless interface is associated to AP. How that happens is outside of systemd-networkd scope.

That said, as delivered currently wpa_supplicant@.service template is simply broken. Only one process can bind to a given D-Bus service, so at any point only one of wpa_supplicant@.service or wpa_supplicant.service may be active which does not allow having multiple interfaces. Once wpa_supplicant.service is started, no other wpa_supplicant@.service instances may become active.

(In reply to Илья Индиго from comment #20)
> (In reply to Илья Индиго from comment #18)
> > (In reply to Gerben Jansen from comment #17)
> > > > In wpa_supplicant.service
> > > > Before=network.target
> > > > After=dbus.service
> > > >
> > > > In wpa_supplicant@.service
> > > > After=dbus.service network.target
> > > 
> > > wpa_supplicant.service already had that string,, added "network.target" to
> > > wpa_supplicant@.service
> > > 
> > > Installed version 2.6-lp151.5.3.1-x86_64 and typed "reboot"
> Something is wrong.
> 
> In lp151.5.3.1
> Both files must be with
> After = dbus.service network.target
> 
> In lp151.4.4 both files must be with
> Before = network.target
> After = dbus.service
> 
> Either you were mistaken when you answered, or you did something wrong.
> (Your package did not install normally and did not overwrite the files)
> 
> This is the only difference between these versions, I do not understand why
> it did not work for you.

Илья Индиго, i now installed version 2.6-lp151.5.3.1-x86_64, checked that both file contained as you said:
==> wpa_supplicant.service <==
[Unit]
Description=WPA Supplicant daemon
After=dbus.service network.target

==> wpa_supplicant@.service <==
[Unit]
Description=WPA Supplicant daemon (interface %i)
After=dbus.service network.target

rebooted and the interface didn't start. (i have a wpa.fail2 file for this)
I now lock the wpa_supplicant-2.6-lp151.4.4.x86_64 version and let you and Andrei discuss over this ....

Created attachment 833580 [details]
wpa.fail2

(In reply to Илья Индиго from comment #18)
> (In reply to Gerben Jansen from comment #17)
> > > In wpa_supplicant.service
> > > Before=network.target
> > > After=dbus.service
> > >
> > > In wpa_supplicant@.service
> > > After=dbus.service network.target
> > 
> > wpa_supplicant.service already had that string,, added "network.target" to
> > wpa_supplicant@.service
> > 
> > Installed version 2.6-lp151.5.3.1-x86_64 and typed "reboot"
> > 
> > System hung on shutdown, so i had to hard-power it off.
> > 
> > Next on startup the interface was still not working.
> 
> Ok, try change both files wpa_supplicant.service and wpa_supplicant@.service
> to
> 
> Before=network.target
> After=dbus.service
> 
> And reboot.

Changing just wpa_supplicant.service to

Before=network.target
After=debus.service

Corrects the problem I reported in bug 1167319

(In reply to Andrei Borzenkov from comment #21)
I wrote the current Leap 15.1 KDE-live to a USB flash drive and checked.

1 As I thought, wpa_suplicant@.srvice has no effect on wicked.

2 Version 4.4 really works, but only at boot time.
It is enough to execute "sudo systemctl restart wpa_supplicant" and it does not work again and "sudo systemctl restart network" does not help anymore.
3 As I thought, LLADDR does not work for a wireless interface. "ip addr" shows the old address.

The conclusion is that something is clearly wrong with wicked!
With systemd-networkd, such problems can only be dreamed of in a nightmare.

Jim, yes. It works with your settings. I was misunderstanding Илья

Илья
> I wrote the current Leap 15.1 KDE-live to a USB flash drive and checked.
You mean that you released the patch without checking it against 15.1 ???

I did not ask to add it in 15.1
I asked him to add in 15.2.(In reply to Gerben Jansen from comment #26)
> Jim, yes. It works with your settings. I was misunderstanding Илья
> 
> Илья
> > I wrote the current Leap 15.1 KDE-live to a USB flash drive and checked.
> You mean that you released the patch without checking it against 15.1 ???

1 I did not ask to add it in 15.1. I asked it to add in 15.2.
2 By default, all Leap use Network Manager where wi-fi works great.

Still a problem in leap 15.1. This is a user antagonistic bug. You can block updates in Yast but the KDE update widget in the lower right corner - or whatever it operates - ignores the block. Explain to me how I tell my 86 year old mom not to update "wpa-supplicant" when packagekit ignores the block and installs the broken version anyway. It does. I checked.

*** Bug 1167319 has been marked as a duplicate of this bug. ***

https://build.opensuse.org/request/show/788607

*** Bug 1167801 has been marked as a duplicate of this bug. ***

*** Bug 1148444 has been marked as a duplicate of this bug. ***

This apparently also affects the TumbleWeed netinstall.

As the log show, wpa_supplicant does not know the Wifi interface.

This can be confirmed with:

$> dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1
->    dict entry(
         string "Interfaces"
         variant             array [
            ]
      )

The array should contain an objectpath like "/fi/w1/wpa_supplicant1/Interfaces/10"

$> dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/10 org.freedesktop.DBus.Properties.Get string:fi.w1.wpa_supplicant1.Interface string:Ifname
->   variant       string "wlp6s0"

The interface has to be created with CreateInterface, see https://w1.fi/wpa_supplicant/devel/dbus.html

(In reply to Stefan Brüns from comment #33)
> This apparently also affects the TumbleWeed netinstall.

Even if this bug is fixed, TW is impossible to install over WiFi due to https://bugzilla.opensuse.org/show_bug.cgi?id=1156920. Wicked simply does not work with current wpa_supplicant.

Marked as Ship stopper for SLE15-SP2 (confirmed on SLES15-SP2-JeOS.aarch64-15.2-RaspberryPi-Build11.14)

needinfo for screening-team is useless

*** Bug 1167551 has been marked as a duplicate of this bug. ***

SUSE-RU-2020:0913-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1166933
CVE References: 
Sources used:
SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src):    wpa_supplicant-2.6-4.17.1
SUSE Linux Enterprise Module for Basesystem 15-SP1 (src):    wpa_supplicant-2.6-4.17.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

*** Bug 1167886 has been marked as a duplicate of this bug. ***

openSUSE-RU-2020:0478-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1166933
CVE References: 
Sources used:
openSUSE Leap 15.1 (src):    wpa_supplicant-2.6-lp151.5.7.1

Fixed in wpa_supplicant-2.6-lp151.5.7.1.x86_64

SUSE-SU-2020:3380-1: An update that fixes 22 vulnerabilities, contains one feature is now available.

Category: security (moderate)
Bug References: 1131644,1131868,1131870,1131871,1131872,1131874,1133640,1144443,1150934,1156920,1166933,1167331,930077,930078,930079
CVE References: CVE-2015-4141,CVE-2015-4142,CVE-2015-4143,CVE-2015-8041,CVE-2017-13077,CVE-2017-13078,CVE-2017-13079,CVE-2017-13080,CVE-2017-13081,CVE-2017-13082,CVE-2017-13086,CVE-2017-13087,CVE-2017-13088,CVE-2018-14526,CVE-2019-11555,CVE-2019-13377,CVE-2019-16275,CVE-2019-9494,CVE-2019-9495,CVE-2019-9497,CVE-2019-9498,CVE-2019-9499
JIRA References: SLE-14992
Sources used:
SUSE Linux Enterprise Server for SAP 15 (src):    wpa_supplicant-2.9-4.20.1
SUSE Linux Enterprise Server 15-LTSS (src):    wpa_supplicant-2.9-4.20.1
SUSE Linux Enterprise Module for Basesystem 15-SP2 (src):    wpa_supplicant-2.9-4.20.1
SUSE Linux Enterprise Module for Basesystem 15-SP1 (src):    wpa_supplicant-2.9-4.20.1
SUSE Linux Enterprise High Performance Computing 15-LTSS (src):    wpa_supplicant-2.9-4.20.1
SUSE Linux Enterprise High Performance Computing 15-ESPOS (src):    wpa_supplicant-2.9-4.20.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

SUSE-SU-2020:3424-1: An update that fixes 19 vulnerabilities, contains one feature is now available.

Category: security (moderate)
Bug References: 1131644,1131868,1131870,1131871,1131872,1131874,1133640,1144443,1150934,1156920,1165266,1166933,1167331
CVE References: CVE-2015-8041,CVE-2017-13077,CVE-2017-13078,CVE-2017-13079,CVE-2017-13080,CVE-2017-13081,CVE-2017-13082,CVE-2017-13086,CVE-2017-13087,CVE-2017-13088,CVE-2018-14526,CVE-2019-11555,CVE-2019-13377,CVE-2019-16275,CVE-2019-9494,CVE-2019-9495,CVE-2019-9497,CVE-2019-9498,CVE-2019-9499
JIRA References: SLE-14992
Sources used:
SUSE Linux Enterprise Server 12-SP5 (src):    wpa_supplicant-2.9-23.3.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

openSUSE-SU-2020:2053-1: An update that fixes 22 vulnerabilities is now available.

Category: security (moderate)
Bug References: 1131644,1131868,1131870,1131871,1131872,1131874,1133640,1144443,1150934,1156920,1166933,1167331,930077,930078,930079
CVE References: CVE-2015-4141,CVE-2015-4142,CVE-2015-4143,CVE-2015-8041,CVE-2017-13077,CVE-2017-13078,CVE-2017-13079,CVE-2017-13080,CVE-2017-13081,CVE-2017-13082,CVE-2017-13086,CVE-2017-13087,CVE-2017-13088,CVE-2018-14526,CVE-2019-11555,CVE-2019-13377,CVE-2019-16275,CVE-2019-9494,CVE-2019-9495,CVE-2019-9497,CVE-2019-9498,CVE-2019-9499
JIRA References: 
Sources used:
openSUSE Leap 15.1 (src):    wpa_supplicant-2.9-lp151.5.10.1

openSUSE-SU-2020:2059-1: An update that fixes 22 vulnerabilities is now available.

Category: security (moderate)
Bug References: 1131644,1131868,1131870,1131871,1131872,1131874,1133640,1144443,1150934,1156920,1166933,1167331,930077,930078,930079
CVE References: CVE-2015-4141,CVE-2015-4142,CVE-2015-4143,CVE-2015-8041,CVE-2017-13077,CVE-2017-13078,CVE-2017-13079,CVE-2017-13080,CVE-2017-13081,CVE-2017-13082,CVE-2017-13086,CVE-2017-13087,CVE-2017-13088,CVE-2018-14526,CVE-2019-11555,CVE-2019-13377,CVE-2019-16275,CVE-2019-9494,CVE-2019-9495,CVE-2019-9497,CVE-2019-9498,CVE-2019-9499
JIRA References: 
Sources used:
openSUSE Leap 15.2 (src):    wpa_supplicant-2.9-lp152.8.3.1

SUSE-SU-2022:1853-1: An update that fixes 20 vulnerabilities, contains one feature is now available.

Category: security (important)
Bug References: 1131644,1131868,1131870,1131871,1131872,1131874,1133640,1144443,1156920,1165266,1166933,1167331,1182805,1194732,1194733
CVE References: CVE-2015-8041,CVE-2017-13077,CVE-2017-13078,CVE-2017-13079,CVE-2017-13080,CVE-2017-13081,CVE-2017-13082,CVE-2017-13086,CVE-2017-13087,CVE-2017-13088,CVE-2018-14526,CVE-2019-11555,CVE-2019-13377,CVE-2019-9494,CVE-2019-9495,CVE-2019-9497,CVE-2019-9498,CVE-2019-9499,CVE-2022-23303,CVE-2022-23304
JIRA References: SLE-14992
Sources used:
SUSE OpenStack Cloud Crowbar 9 (src):    wpa_supplicant-2.9-15.22.1
SUSE OpenStack Cloud Crowbar 8 (src):    wpa_supplicant-2.9-15.22.1
SUSE OpenStack Cloud 9 (src):    wpa_supplicant-2.9-15.22.1
SUSE OpenStack Cloud 8 (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server for SAP 12-SP4 (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server for SAP 12-SP3 (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server 12-SP4-LTSS (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server 12-SP3-LTSS (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server 12-SP3-BCL (src):    wpa_supplicant-2.9-15.22.1
SUSE Linux Enterprise Server 12-SP2-BCL (src):    wpa_supplicant-2.9-15.22.1
HPE Helion Openstack 8 (src):    wpa_supplicant-2.9-15.22.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.