On 30.12.2022 00:45, Simon Becherer wrote:
Hi,
i updated a not so often used laptop (last update done 01/2022 to the actual tumbleweed 20221228
after restarting i have no network adapters UP
if it is working, it looks like this:
================================================ wicked ifstatus all
lo up link: #1, state up type: loopback config: compat:suse:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 [static] addr: ipv6 ::1/128 [static]
enp3s0 enslaved link: #2, state up, mtu 1500, master bond0 type: ethernet, hwaddr 18:67:b0:b9:a6:58 config: compat:suse:/etc/sysconfig/network/ifcfg-enp3s0
wlp2s0 up link: #3, state up, mtu 1500 type: wireless, state established, ssid XAuaLiwaru9835, WPA2-PSK+WPA-PSK config: compat:suse:/etc/sysconfig/network/ifcfg-wlp2s0
bond0 up link: #4, state up, mtu 1500 type: bond, mode active-backup, hwaddr 18:67:b0:b9:a6:58 config: compat:suse:/etc/sysconfig/network/ifcfg-bond0 leases: ipv4 static granted addr: ipv4 192.168.0.23/24 [static] route: ipv4 default via 192.168.0.99 [static]
==================================== it is configured that if cable (enp3s0) is plugged in, it will use cable, and if not plugged in it will switch to whireless (wlp2s0) ==================================== if its not working (before starting manually) it has the status: "device-not-running" for enp3s0 wlp2s0 and bond0 ====================================
after playing around i found out that the command: ip link set enp3s0 up ip link set wlp2s0 up
will bring the network cards UP, but this i have to enter manually,
AND wicked ifup enp3s0 wicked ifup wlp2s0
will NOT bring the network cards UP. (therefore wicked will during boot hang and run out of time, then boot continues
========================================== here from boot: Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked AutoIPv4 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv4 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv6 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv6 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv4 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Started wicked AutoIPv4 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network management service daemon... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network management service daemon. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network nanny service... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network nanny service. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked managed network interfaces... Dez 29 21:54:38 becherer7 wicked[1227]: lo up Dez 29 21:54:38 becherer7 wicked[1227]: enp3s0 device-not-running Dez 29 21:54:38 becherer7 wicked[1227]: wlp2s0 device-not-running Dez 29 21:54:38 becherer7 wicked[1227]: bond0 device-not-running Dez 29 21:54:38 becherer7 systemd[1]: Finished wicked managed network interfaces.
I cannot reproduce it on VM with wicked. You may want to enable debug output to see what's going on.
================================================= and here when i try manually using wicked: Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: device wlp2s0: call to org.opensuse.Network.Interface.waitLinkUp() failed: General failure Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: wlp2s0: failed to bring up device, still continuing Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: device enp3s0: call to org.opensuse.Network.Interface.waitLinkUp() failed: General failure Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: enp3s0: failed to bring up device, still continuing ===================================================
what is wrong here? before update, always the network was running after boot. NOW its only running after i hack in the "ip link....." command.
did anybody have me an info how i could start the network again, during boot, AND why did the "wicked ifup..." will not work?? is this a bug? or a configuration problem?
some other systems i have updated did not show this problem. they are also running wicked. but did not have a wifi inside (using a bridge and an enslaved network-adapter).
regards,
simoN