David C. Rankin composed on 2018-04-19 00:17 (UTC-0500):
Felix Miata wrote:
Happens to me when the ethernet cable is not plugged in securely.
I have unplugged my ethernet after install, so this is just bringing wlan0 up. It looks like there is something left in the setup that is waiting for eth0. That interface should just be brought up, but wicked shouldn't be waiting for it to get an address.
Yast says under eth0 (General) Activate Device is set to "At Boot Time" - should I change that to
On Cable Connect On Hotplug
It doesn't hurt to bring the "device" up, it just shouldn't activate the device until the cable is plugged in.
Makes sense to me. Grep of icked from 15.0b journal tail: Apr 19 02:18:18 gb250 systemd[1]: Starting wicked DHCPv4 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Starting wicked DHCPv6 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Starting wicked AutoIPv4 supplicant service... Apr 19 02:18:18 gb250 systemd[1]: Started wicked DHCPv4 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Started wicked AutoIPv4 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Started wicked DHCPv6 supplicant service. Apr 19 02:18:18 gb250 systemd[1]: Starting wicked network management service daemon... Apr 19 02:18:19 gb250 systemd[1]: Started wicked network management service daemon. Apr 19 02:18:19 gb250 systemd[1]: Starting wicked network nanny service... Apr 19 02:18:19 gb250 systemd[1]: Started wicked network nanny service. Apr 19 02:18:19 gb250 systemd[1]: Starting wicked managed network interfaces... Apr 19 02:18:49 gb250 wicked[660]: lo up Apr 19 02:18:49 gb250 wicked[660]: eth0 setup-in-progress Apr 19 02:18:49 gb250 systemd[1]: Started wicked managed network interfaces. 30 second needless wait. Nothing I own uses anything but wired ethernet. Only about 2 out of hundreds or maybe thousands of installations going back to RedHat 5 here have been configured to use DHCP. All the rest, including those that lose 30 seconds to Wicked at boot if the cable isn't properly connected, use fixed IP. I don't remember ever having any such delay from ifup at boot time, when networks that didn't need to be "managed" weren't. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org