https://bugzilla.novell.com/show_bug.cgi?id=677618 https://bugzilla.novell.com/show_bug.cgi?id=677618#c0 Summary: /sbin/ifup prevents concurrent use of NetworkManager-managed & NetControl-managed interfaces; WORKAROUND Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pgngw+dev001+novell.com@f-m.fm QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110303 SUSE/3.6.15-1.1 Firefox/3.6.15 if NM is enabled in opensuse, ifup's code prevents concurrently bringing up/using a non-NM-managed interface example use case: (common across all our laptops, e.g., in part because the SharedFolder function in VirtualBox is slow to connect & fragile to maintain) -- opensuse 11.3 on a 'roaming' laptop, needing NetworkManager-controlled ethX/wlanX interfaces -- VirtualBox running a Windows7 VM -- VBox passed two interfaces (1) dynamically allocated NAT address, for external/internet access (2) private, static IP (e.g., 10.10.10.2) -- Samba server running on laptop, config'd as WINS Server, listening @ vboxnet0 interface, allocated a statisIP (e.g., 10.10.10.1). in order for this to work, smb/nmb must be up-&-running before VirtualBox, or the VM fails @ network mount / WINS service access vboxnet0 must be up/functional before smb/nmb, or smb segfaults. adding either a custom init.d script proper network/smb dependencies, or adding stanza to bring up the interface in ./etc/init.d/after.local fails @ 'ifup', if in Yast, network's GlobalSettings -> Network Manager. in that case, at any attempt ifup vboxnet0 "network interface is managed by the NetworkManager -> skipping" this originates in /sbin/ifup itself, which incorrectly presume that there can be NO use-case for mixed NM & !NM network management, in order to get this to work, changing in, /sbin/ifup ... ###################################################################### # Check if NetworkManager is running, inform the user and exit # - if [ "$NETWORKMANAGER" = yes ] && ! netcontrol_running ; then - if [ "$SCRIPTNAME" != ifdown -a "$INTERFACE" != lo ] ; then - mesg "Network interface is managed by the NetworkManager -> skipping" - exit $R_NOTIMPL - fi - elif nm_running && [ "$INTERFACE" != lo ] ; then - mesg "Network interface is managed by the NetworkManager -> skipping" - exit $R_NOTIMPL - fi + #if [ "$NETWORKMANAGER" = yes ] && ! netcontrol_running ; then + # if [ "$SCRIPTNAME" != ifdown -a "$INTERFACE" != lo ] ; then + # mesg "Network interface is managed by the NetworkManager -> skipping" + # exit $R_NOTIMPL + # fi + #elif nm_running && [ "$INTERFACE" != lo ] ; then + # mesg "Network interface is managed by the NetworkManager -> skipping" + # exit $R_NOTIMPL + #fi ... adding to, /etc/init.d/after.local ... test "$RUNLEVEL" = "5" && /sbin/ifup vboxnet0 test "$RUNLEVEL" = "5" && /etc/init.d/smb start test "$RUNLEVEL" = "5" && /etc/init.d/nmb start ... and ensuring, chkconfig smb off chkconfig nmb off does the trick. the workaround is sloppy, and won't survive an ifup update, of course. the _real_ issue at hand, however, is the incorrect assumption that mixed network is NOT a viable use-case. in discussions in #nm, Dan Williams argues that is most certainly should be, that being the very definition of an un-managed interface; namely, one that NM simply doesn't touch ... Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.