I’ve noticed this since the early Milestone releases. If I boot into runlevel 3 and press esc to see the output of the boot process, it stops at “starting the networkmanager” and begins a 30 second countdown. The result is it stops at 1 sec and then outputs “waiting” in yellow.
The boot process finishes and I can log in but I’m not connected to my network. It says that networkmanager is running but I have no ip address. Once I start X and KDE, my network connects normally.
Is anyone else getting this?
Is there a way I can get an ip address while in runlevel 3?
Network manager is in fact a (local) server, that acts on requests of a (local) client. This client is normaly the network applet in a desktop and thus of course belongs to a GUI session.
I do not know if there are CLI network manager clients, but then again you have to log in in the CLI first.
Normaly systems that run only in runlevel 3 do not need a network manager because they are more server like systems and thus have a fixed network setup (in openSUSE YaST called: traditional with ifup"). Then the network is fully available when runlevel 3 (or higher) is reached.
Ah yes, the DW networkmangler. I’d like to know who decided that his 3rd party code was better than what had gone before from ‘inhouse’. (where are schaa and hoenig when we need 'em?) He obviously thinks that nobody uses cables or he’d have put an ‘enable’ against it. His little heart icon is nice though
Thanks for the response, koen_dewitte. My config file looks a little different:
## Type: integer
## Default: 30
# Some interfaces need some time to come up or come asynchronously via hotplug.
# WAIT_FOR_INTERFACES is a global wait for all mandatory interfaces in
# seconds. If empty no wait occurs.