Bugzilla – Bug 174801
no nis possible after minimal install (multiple BOOTPROTO=dhcp due to NM)
Last modified: 2008-07-16 15:44:17 UTC
doing a minimal install of 10.1 on bramble.suse.de after install, no NIS is possible, ypdomainname is never set for some reason. likely some package is missing to actually do the right thing. but its not obvious what package that is.
Created attachment 82985 [details] bug174801.tar.bz2
What does it mean "no NIS is possible"? NIS configuration does not work? Or is NIS option missing in the selection of authenticaton types?
ypdomainname is not set during boot. not necessary a yast bug.
probably not
In boot.msg, sysconfig says for all interfaces "dhcpcd is still waiting for data", and when ypbind starts, it says "No domainname setskipped". It seems that no address had been obtained in time. I think that's how it works currently. We don't have a 'rcypbind reload' in a post-configuration hook script, so far. Christian, is that a correct view? (sorry about always asking so stupid questions, but I may not be up to speed with current boot/network setup framework)
Don't configure multiple interfaces with STARTMODE=auto and BOOTPROTO=dhcp. If you want that, then you should set DHCLIENT_PRIMARY_DEVICE. Read the explanation in ifcfg.template. So this is either invalid or a configuration bug.
yast did that for me.
It should not.
Olaf enabled NM and then disabled it again, triggering the bug. yast2-network-2.13.20, if it enables NetworkManager, will create minimal ifcfgs so that the firewall UI can manipulate with the NICs and assign them to zones. The ifcfgs have STARTMODE=auto and BOOTPROTO=dhcp. Lukas, do we still need the feature now that SFw has the "any" feature?
Well, the 'any' feature wasn't tested for functions used in the Firewall proposal, also functions used in yast2-firewall module were not changed. There are completely new functions in the SuSEFirewall module for this feature and they were used only for CWMSuSEFirewallInterfaces. e.g.: compare SuSEFirewall::GetZonesOfInterfaces() and SuSEFirewall::GetZonesOfInterfacesWithAnyFeatureSupported() Yes, I could create some special function in the SuSEFirewall module if you tell me what exactly should it do :)
Reassigning to the new maintainer of yast2-network.
>>There are completely new functions in the SuSEFirewall module for this >>feature and they were used only for CWMSuSEFirewallInterfaces. Lukas, could you provide more details that functions you mean?
It seems that neither 10.2 nor 10.3 contain such problem with enabling/disabling NetworkManager, mainly because it creates ifcfg files which can be later handled by NetworkDevices module used by Firewall. We don't expect doing anything with this for 10.1, so closing as WONTFIX. Sorry.