Bugzilla – Bug 608677
Switching to NetworkManager, NIS is gone
Last modified: 2016-04-15 11:47:23 UTC
I just installed M7 on a laptop from the Net (SLP/DHCP) and I ended up with the traditional networking method. I disabled firewall. Then I enabled NIS and automounter and it worked as usual. Then I switched to NetworkManager using yast. NIS (and automounter) no longer works. NetworkManager rewrote resolve.conf and it looks fine, IMO (I'm supressing the actual addresses): # Generated by NetworkManager domain suse.de search suse.de nue.novell.com nameserver xxx nameserver yyy
resolv.conf has nothing to do with NIS. Using NIS with NetworkManager is and never was a valid usecase. What does "no longer works" mean? Any error messages, anything in the log files, ...?
If NM does not work in a NIS environment, yast must at least warn, if the user on a NIS client machine tries to switch from "Traditional Method with ifup" to "User Controlled with NetworkManager" and we must add some such warning to our docs.
The nis was not in Factory now, I'll submit it later.
I mean the patch for NIS in NetworkManager.
I've commit the NIS support in NM. 41285 State:new By:BinLi When:2010-06-09T13:24:44 submit: home:BinLi:branches:GNOME:Factory/NetworkManager -> GNOME:Factory Descr: NIS support and update resolv.conf once(bnc#608677, bnc#595708, bnc#544195, bnc#537907)
Fixed. Thanks for your report.
This is an autogenerated message for OBS integration: This bug (608677) was mentioned in https://build.opensuse.org/request/show/41997 11.3 / NetworkManager