[Bug 911562] New: wicked does not activate interfaces
http://bugzilla.opensuse.org/show_bug.cgi?id=911562 Bug ID: 911562 Summary: wicked does not activate interfaces Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jengelh@inai.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 618568 --> http://bugzilla.opensuse.org/attachment.cgi?id=618568&action=edit SCREENSHOT This wicked wicked daemon is messed up, and I have NO idea why, because it outputs so LITTLE information. Manually calling ifup starts the interface, but WHY can it not already do that at boot? This is SO stupid. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
--- Comment #1 from Jan Engelhardt
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
--- Comment #3 from Jan Engelhardt
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Inge Svensson
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
--- Comment #5 from Jan Engelhardt
Apparently your ethernet device and tap device do not have a link (or it's too early for dhcp in case of eth) during boot. Therefore wicked client (started standalone, i.e. without nanny) timeouts and interfaces are left w/o addresses assigned.
That is *a normal condition*. TAP devices won't have a link until the first client connects, which may be never. Nevertheless, the _preconfigured static_ address(es) *must* always be added (irrespective of device type tun/tap/bridge/bond, and irrespective of carrier), or programs, like apache, will fail to bind to them. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
--- Comment #6 from Jan Engelhardt
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
--- Comment #7 from Jan Engelhardt
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Jan Engelhardt
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Marius Tomaschewski
Apparently your ethernet device and tap device do not have a link (or it's too early for dhcp in case of eth) during boot. Therefore wicked client (started standalone, i.e. without nanny) timeouts and interfaces are left w/o addresses assigned.
That is *a normal condition*. TAP devices won't have a link until the first client connects, which may be never.
Yes, there is a userspace driver daemon required.
Nevertheless, the _preconfigured static_ address(es) *must* always be added (irrespective of device type tun/tap/bridge/bond, and irrespective of carrier), or programs, like apache, will fail to bind to them.
We will add a ifcfg config flag [and for tun/tap activate it by default] and the code to handle it as needed, allowing to ignore the link state and set up the static IP addresses regardless of the link state. But, setting IP addresses when link is UP is a correct default [not here or in some other special cases]. A link is required for upper layers, e.g.: - bridge STP [bridge with enabled STP will never come up without a port with link up as it STP to verify the port without carrier] - any kind on link authentication - lldp and other stuff - duplicate address detection note: it is enabled by default for IPv6 and as a new feature, also for IPv4 [it is also a MUST in current rfc's to do it]. - dhcp and other autoconfig stuff As we've fixed some other high prio bugs, we can start working on this issue now too [for 0.6.16] -> corrected it's priority. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Inge Svensson
http://bugzilla.opensuse.org/show_bug.cgi?id=911562
Pawel Wieczorkiewicz
participants (1)
-
bugzilla_noreply@novell.com