[Bug 893678] New: No network with wicked
https://bugzilla.novell.com/show_bug.cgi?id=893678 https://bugzilla.novell.com/show_bug.cgi?id=893678#c0 Summary: No network with wicked Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pilotgi@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 As with previous snapshots of Factory, version 20140820 installed fine but I had no network with wicked. I configured my wireless with YaST with no problems and my wireless card was assigned wls5s5 but there is no connection. After entering 'sudo wicked show-config wlp5s5' I got: wicked: wlp5s5 configuration applied to nanny wicked: Interface wait time reached wlp5s5 setup-in-progress After 'wicked ifstatus all' here's the part referring to wlp5s5: setup-in-progress link: #3 state device-up, mtu 1500 type: wireless config: compat:/etc/sysconfig/network/ifcfg-wlp5s5 lo was configured with addr 127.0.0.1/8 Configuring my network with NetworkManager was successful. 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.
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c1
Pawel Wieczorkiewicz
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c2
--- Comment #2 from kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c3
--- Comment #3 from kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c4
--- Comment #4 from kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c5
--- Comment #5 from kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c
kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c6
Pawel Wieczorkiewicz
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c7
kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c8
--- Comment #8 from kevin vandeventer
https://bugzilla.novell.com/show_bug.cgi?id=893678
https://bugzilla.novell.com/show_bug.cgi?id=893678#c9
Graham Davis
http://bugzilla.novell.com/show_bug.cgi?id=893678
--- Comment #21 from kevin vandeventer
A "systemctl stop NetworkManager" is not sufficient -- there is a NM setting causing to stop NM only, but not the dhclient processes started by NM...
See also bug#895447 => "systemctl --kill-who=all kill NetworkManager".
We're working on a documentation how to do it manually -- here the a paste from current draft:
"[...] Procedure to enable NetworkManager manually:
1) First, stop the running network (wicked) service to get a clean state (configuration may differ):
systemctl is-active network.service && \ systemctl stop network.service
2) Then, stop the wicked-daemon services as well:
systemctl is-active wickedd.service && \ systemctl stop wickedd.service
3) Disable wicked, enable NetworkManager.service (creates alias link):
systemctl disable wicked.service systemctl --force enable NetworkManager.service
4) Start the NetworkManager service via the alias link:
systemctl start network.service
or directly:
systemctl start NetworkManager.service
Procedure to disable NetworkManager and switch to wicked.service manually:
1) Stop the running NetworkManager.service:
systemctl is-active NetworkManager.service && \ systemctl --kill-who=all kill NetworkManager.service
Note: The normal NetworkManager.service stop action stops NetworkManager, but leaves processes such as dhcp clients running to not break network connectivity when it is restarted on update or there is a remote fs mounted while shutdown. The --kill-who=all kill action ensures to stop them too as they conflict with the wicked service using a different implementation.
2) Disable NetworkManager, enable wicked.service (creates alias link):
systemctl disable NetworkManager.service systemctl --force enable wicked.service
3) Start the new network.service, which now is wicked.service:
systemctl start wicked.service
or via the alias link:
systemctl start network.service
The wickedd daemon service are started automatically via dependencies.[...]" I tried this method also but still no IP address for wlp5s5. I tried rebooting but that didn't help.
The results of 'wicked ifup wlp5s5' was the same as before: wicked: device wlp5s5 failed: operation timed out wlp5s5 setup-in-progress -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=893678
Alberto Planas Dominguez
participants (1)
-
bugzilla_noreply@novell.com