On Wed, Dec 4, 2013 at 3:04 AM, C
On Wed, Dec 4, 2013 at 7:00 AM, Claudio Freire
wrote: On Wed, Dec 4, 2013 at 2:35 AM, C
wrote: If there was a way to "fix" this on install... allow the user to choose ifup or NM... would that resolve it?
AFAIK, there is that choice, at least in advanced mode.
If it's there... then what about swapping? Set NM for default and leave it to those that know what they are doing to use advanced install and select ifup where it makes sense.
The default works well as-is. Ethernet ports tend to work out-of-the-box with ifup (which by default uses DHCP which is as plug-n-play as it gets). Wi-Fi ports are left unmanaged for NM to handle them. I have never had a system where wlan was the *only* port (ie: no eth). It's possible that the installation procedure configures such an interface to be ifup. That may need to be checked. Which, as I said a way back, you get checked by reporting the bug on the bugzilla. The DistroWatch thingy you linked sounds more like a misconfigure network router rather than a bug in ifup. It sounds as if the router was handing out IPv6 addresses even when the network didn't support it. I've seen this happen. Most recent versions of Firefox and the like will prefer IPv6 over IPv4, and if the network isn't properly set up, you get what DistroWatch reports. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org