[opensuse-factory] Network Stack in 12.3
Hi all, As many are surely aware, there are 'funny' issues in 12.3 when it comes to the network stack. On my machine, I experienced WiFi not being able to connect at all (Intel chip). => Updating the kernel-firmware package (Used Larry's pkg!) worked around this.. Then, NetworkManager and sysconfig seem to cause real pain. sysconfig was updated to 0.80.x (and a respective change added to NM). Now, whenever I use this configuration (tested on cable/LAN), then there is either no default route set, or /etc/resolv.conf is not being written. Having my system back in shape by reverting to sysconfig 0.76.8 and reverting NM to not make use of sysconfig 0.8 features got me running again. Don't get me wrong: I don't say we should kill the progress of sysconfig, but we should postpone this for 13.1, as in my opinion we are way to late in the release to figure out what all goes wrong and needs fixing (the issue is larger than it looks at first, just look at issues caused by this like https://bugzilla.novell.com/show_bug.cgi?id=804052, where yast does not know how to perform the switch anymore between ifup and NM. As such, I very much vote for - Inclusion of kernel-firmware update, as prepared by Larry - Revert sysconfig to 0.78.8 - Revert the change in NetworkManager ( https://build.opensuse.org/package/rdiff?linkrev=base&package=NetworkManager... ) NOTE: Even doing this revert will leave machines which HAD these packages in a 'weird' state: NETWORKMANAGER=yes/no was removed from /etc/sysconfig/network/config with sysconfig 0.80 and rolling back to 0.78.8 adds =no to the system. So those machines might be in a very odd stage... yet, this is a 'rather' small subset of systems which we can possibly manage. Looking forward to some noise here! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On 02/16/2013 05:00 PM, Dimstar / Dominique Leuenberger wrote:
As many are surely aware, there are 'funny' issues in 12.3 when it comes to the network stack. this doesn't seem to be fixed with RC2/the current software stack.
I still have issues like /etc/resolv.conf not getting update anymore if I connect to a VPN. Even worse during an RC2 DVD installation without automatic configuration the network didn't work in stage 2 and the network interface was called em1 instead of eth0 while the LiveCD didn't had this problem.
On my machine, I experienced WiFi not being able to connect at all (Intel chip). => Updating the kernel-firmware package (Used Larry's pkg!) worked around this..
Then, NetworkManager and sysconfig seem to cause real pain. sysconfig was updated to 0.80.x (and a respective change added to NM). Now, whenever I use this configuration (tested on cable/LAN), then there is either no default route set, or /etc/resolv.conf is not being written.
Having my system back in shape by reverting to sysconfig 0.76.8 and reverting NM to not make use of sysconfig 0.8 features got me running again.
Don't get me wrong: I don't say we should kill the progress of sysconfig, but we should postpone this for 13.1, as in my opinion we are way to late in the release to figure out what all goes wrong and needs fixing (the issue is larger than it looks at first, just look at issues caused by this like https://bugzilla.novell.com/show_bug.cgi?id=804052, where yast does not know how to perform the switch anymore between ifup and NM.
As such, I very much vote for - Inclusion of kernel-firmware update, as prepared by Larry - Revert sysconfig to 0.78.8 - Revert the change in NetworkManager ( https://build.opensuse.org/package/rdiff?linkrev=base&package=NetworkManager... )
NOTE: Even doing this revert will leave machines which HAD these packages in a 'weird' state: NETWORKMANAGER=yes/no was removed from /etc/sysconfig/network/config with sysconfig 0.80 and rolling back to 0.78.8 adds =no to the system. So those machines might be in a very odd stage... yet, this is a 'rather' small subset of systems which we can possibly manage. So it seems that your suggested changes weren't integrated?
Tim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Dimstar / Dominique Leuenberger -
Tim