https://bugzilla.suse.com/show_bug.cgi?id=1224860 https://bugzilla.suse.com/show_bug.cgi?id=1224860#c5 --- Comment #5 from Marius Tomaschewski <mt@suse.com> --- (In reply to Patrick Schaaf from comment #3)
(In reply to Marius Tomaschewski from comment #1)
Thank you for looking into this, and all the explanation. What you write, matches my understanding / expectation. Note that I do not use STARTMODE=off but (on the "underlings") STARTMODE=manual.
Yes. While STARTMODE=off disables an interface in any ifup, STARTMODE=manual disables to start it in the "wicked ifup all" call (made by network.service) at boot aka needs manual "wicked ifup <name1>" call. See also ifcfg(5) man page: ``` STARTMODE {manual*|auto|nfsroot|hotplug|off} Choose when the interface should be set up. manual Interface will be set up if ifup is called manually auto Interface will be set up as soon as it is available (and service net- work was started). This either happens at boot time when network is starting or via hotplug when a interface is added to the system (by adding a device or loading a driver). To be backward compliant onboot, on and boot are aliases for auto. hotplug Interface will be activated when it is available. Use instead of auto for devices which may be missed, such as bonding slaves, usb or other plugable hardware. nfsroot Nearly like auto, but interfaces with this startmode will be not shut down by default. Use this mode when you use a root filesystem via network or want to avoid interface shutdown. To force a nfsroot inter- face down, use either wicked ifdown --force device-down <interface> or ifdown <interface> -o force. off Will never be activated. ``` -- You are receiving this mail because: You are on the CC list for the bug.