Bug 354981

I think you are talking of the installation, right?
I just observed the same issue on a SLES10SP2 installation as well.
The network connection was open for the network test but shut down right after that. Therefore the registration process could not be run, because it needs network connection (btw. registration only runs when network connection succeeds).

Michal, do you need logs? (hope not, cause mine are already gone)

During installation, yes.  In 10.3, it did like you said, however you could hit back to go back to the network page and forward again and it would work.

This is for 11.0 Alpha 2.  It is simply not even doing that this time around. It does not enable it at all.  I can flip to the a console window and type ifconfig and only the Lo (local) appears, no Eth0 for the Xircom 10/100 card I am using (which is recognized in prior versions).  This is right after the network config (asks if I want to use DHCP, which I answer Yes) and it goes forward.  It is still  not configured by the time I get to the registration screen and is not after it is installed.  

Even after logging in as the user for the first time, the network has to be enabled manually via the Network manager (if you choose it vs ifconfig) before it comes up and begins to work.  It does not at any point do it automatically on successive logins. Always a manual process.    

In 11.0 you can't control NetworkManager-0.7 from command line.
In previous version, YaST uses dbus-send command to activate device, this is not possible now
I did some research http://idea.opensuse.org/content/ideas/control-networkmanager-from-cli
For this purpose we need to create some service that uses libnm-glib and libnm-util functionality to create some NetworkManagerUserSettings storage to create new Connection.
Tambet, what's your comment for that?

The way it works for NetworkManager 0.6 is a hack and is going to be resolved the right way for 0.7. NetworkManager now needs a predefined connection to activate a device and without applet, there's nothing on opensuse that provides it. There's already a system service daemon that provides "system connections" to NM prior login, ie connections configured by distro's native tools, yast for out case. The reason why it still doesn't work for us is that noone is working on the opensuse backend for it. I would like to, but I don't have time to work on it for now.

*** Bug 358794 has been marked as a duplicate of this bug. ***

*** Bug 364978 has been marked as a duplicate of this bug. ***

I just submitted a fix for this. NetworkManager can now fully work without any applets using the configuration provided by yast (files from /etc/sysconfig/network).

*** Bug 349442 has been marked as a duplicate of this bug. ***

I'll check it with next release

Tambet, please provide me some info how can I switch between two configurations written for netcontrol?

You mean which devices get activated? Otherwise, I didn't know yast allowed multiple configurations per device. At the momemnt, NM will prefer wired connection and will active it on startup (like what the subject of this bug says). In the near future, when we've enabled multiple active devices, it'll activate all the devices marked for activation on startup.

I was under impression headless machines (servers) don't really need to switch between network connections all that often and for the rare cases they do need it, yast could be used to enable/disable a device or to change it's configuration.

I forgot to comment comment #3, here it goes. It's not necessary to implement any more services to provide the connection information to NM, that's exactly what the NM's system-settings daemon is supposed to do. It consists of a general settings provider and plugins to turn any sort of configuration files to NMConnections. Currently, there are plugins for fedora and suse. The suse plugin could use some improvements for parsing wireless networks properties, but it's in my todo list. If you want to help out, I'd appreciate any patches.

*** Bug 366457 has been marked as a duplicate of this bug. ***

Continued from Bug 366457:

I just repeated a clean install from alpha2 DVD on a Sony Vaio PCG-SRX51P and expressly deselected NetworkManager. The eth0 interface (Intel e100) doesn't get set up either.

Running yast2 lan after the installation is through shows "not configured", editing the entry installs smpppd and kinternet and a few packages they depend on. Only then is eth0 usable.

*** Bug 384158 has been marked as a duplicate of this bug. ***

no, it works fine (your problem is some driver-issue)

What is this now ? Shrugging shoulders and signing off ? 

I can assure you it's not working, neither fine nor otherwise. And it's not a driver issue either, as driver works fine with ifup method.

Ok, attach /var/log/* from installation

I just completed an installation from the Beta2 live cd, this time NetworkManager is working "out of the box" yet ifup is not working at all. Attaching logs from this install and repeating the network install from boot.iso for comparison.

Created attachment 212507 [details]
yast2logs from installation off Beta2 live cd

As I wrote in comment #16, it works fine (I tested it with Beta2 too). Create a new bugreport with summary that corespondent to your problem. This bugreport is about NetworkManager during installation and it was solved (see comment #7)