So, the title should give some picture as to what I want to know about.
I understand that the K (KDE) network manager is a KDE app but does it actually function in runlevel 3?
By that I mean does it allow wireless connections to work?
I’ve been trying to do this but can’t. I have a need to while in KDE to sometime init 3 and while in runlevel 3 I need my wireless to work.
I havent figured out if Knetwork manager still functions outside of KDE or if I need to just use ifup traditional.
I did search the forum for threads related to knetwork manager and did not see anything related to this so I hope someone can assist me.
Also if I do need to use ifup traditional method, is there anything specail I need to do so that it works without issues such as, uninstall knetwork manager or something else? I ask this because my previous attempts at using ifup (by switching to it from YAST) end up making my wireless not work. I can scan and find my network but after entering my creds it doesnt do anything. I managed to get it to work once somehow but after a shutdown and reboot it no longer worked.
Thanks for any assistance,
Just incase you need to know, I’m running Suse11.4 KDE 4.6, my wireless module I believe is a iwlagn or something like that. My laptop which Suse is running on is a Toshiba A665-S6086 core i3, 4GB RAM, 500GB HDD.
Hi
But NetworkManager is still running? 11.4 Gnome 3 works. Network is up and running at runlevel 3 as long as I have logged in to Gnome DE prior to running init 3.
No, neither knetworkmanager, nor the alternative networkmanager plasmoid will work outside of your KDE login, at least for wireless connections. However, a wired connection will still be made by the main NetworkManager process that does run at level 3.
The gnome network manager applet, however, can be used for connections that persist outside of a KDE login.
It is possible to run the gnome applet instead of the KDE applet, but it might require a change in the gtk theme. There’s a thread on doing that if you want to try.
Let me describe what I am currently doing.
In addition to KDE, I also have XFCE and LXDE installed. If I login to either XFCE or LXDE, I get the gnome networkmanager applet.
While in XFCE (or LXDE), I set up my main wireless network with the gnome applet. While setting it up, there is a box near the bottom with wording something like “share this connection with other users”. I check that. I am asked for the root password. That WiFi connection is then defined as a system wide connection (in directory “/etc/NetworkManager/system-connections”).
That system wide connection is made at network setup, and should work at runlevel 3 and 5, without requiring a KDE or XFCE login.
If you are using KDE (probably at runlevel 5), then the KDE network manager applet does show the connection. However, it won’t allow you to edit that system wide connection.
To summarize: only connections defined in “/etc/NetworkManager/system-connections” will work without a GUI desktop. And only the gnome applet can edit those system wide connections.
Thank you all for the informative replies.
I am using WPA2/PSK encryption (personal).
When I scan using Ifup, it does find my network, I even acquire an IP address to my wlan0 that matches my network. It doesnt seem like I’m getting a gateway address though and I need that to happen automatically as I am visiting locations that willl not reveal information to me that I can statically input.
Nrickert,
Thank you for sharing your setup. I may need to look to some setup similar if I cannot get Ifup to work properly.
You can configure your network settings at runlevel 3 with network manager using the curses-based command line app nmtui - NetworkManager Text User Interface
There is also the NetworkManager command-line tool, nmcli, which provides a command line way to configure networking by controlling NetworkManager, but it requires a bit more effort to understand and use.
You’re posting to a thread that is 4 years old. Almost no value at all in doing that. The NetworkManager tools have changed a lot since 2011, including the CLI-based tools.