Hello Everyone

I am just curious because NetworkManager was included in the recent KDE 4.8.2 upgrade. I have an icon in my try which says it is not running, please start it. I have no trouble with wicd, works fine, but I was curious if NetworkManager has any advantages. When I try to start NetworkManager to try it, it doesn't allow me to start it:

I ran this as root. If root can't start it, who can?

Bob

Try either: a) chmod +x /etc/rc.d/rc.networkmanager and after that /etc/rc.d/rc.networkmanager start
or b) sh /etc/rc.d/rc.networkmanager start
And let us know how do you like it

as mentioned in the ChangeLog, you have to give execute permission first

There is a short (short on details ) discussion here:

http://www.linuxquestions.org/questi...ed-bug-933893/

Well, I appreciate the help on getting it started, but I wish I hadn't tried. Now I can't get my wireless working at all. Network manager tries to connect but even after I have entered my WPA password, it is it's connected but won't get me online because it continually says "waiting for authorization".

Now no networking works. Anyone know how I can restore what I had before? I was using the old fashion Slack connection with W PA, which also no longer works.

Appreciate the help.

EDIT: Got back wireless networking by stopping NetworkManager and starting inet1. But I used to be online as soon as I booted up. NetworkManager has cocked all that up.

Bob

On my laptop and netbook, NetworkManager found more wireless networks (including my own) and maintained connection better than wicd.

I have been using NetworkManager supplied as an extra in Alien_Bob's build of KDE 4.8.1. on my netbook for some time and have had no problems with connections. I like NetworkManager as it allows to me handle all my interfaces (wired, wireless and USB modem) from the one screen. My USB modem is not handled by wicd.
Handling NetworkManager from the command line using nmcli is not as intuitive as handling wicd using wicd-curses. Also there are differences in how you handle changing system configuration upon connection. Using wicd you can setup post connect scripts to do tasks such as changing firewall settings. NetworkManager requires setting up scripts in /etc/NetworkManager/dispatcher.d/ as I reported here. http://www.linuxquestions.org/questi...tables-924621/

I finally got it working correctly by stopping inet1. I suppose the two were conflicting. I must have a little script in rc.local starting inet1 at boot, and when I started networkmanager it wouldn't get an ip address. Anyway, I will use it for a while and see which is better. Signal strength is the same for both. So far, don't see much advantage to NetworkManager except a nice little icon in the tray which I didn't have with inet1 or wicd.

Still learning.....

Bob

Hmm.. I read somewhere that NM supports creating ad-hoc network whereas Wicd doesn't.
I needed to create ad-hoc network for my iPad coz I didn't have a wifi router before
but in the end I gave it up anyway,, couldn't get NM working

I prefer NetworkManager because when I wake my laptop from sleep it automatically re-establishes the network connection. Even if I have moved location and it needs to connect to a different network it handles this quickly and automatically. wicd requires that I tell it to reconnect/change network.

Brian

Not difficult. In your rc.M file in /ete/rc.d/ you can #out the lines concerning wicd (or remove them all together) and add NetworkManager. Here is an example:

Then make /etc/rc.d/rc.networkmanager executable and reboot your computer.
All there is to it.


Edit in: If you are using KDE then you only have to add the NetworkManager widget to your panel and your are set to go. If you are using KDE 4.8.2, Networkmanager and ModemManager are now part of the whole KDE bundle (in -current).
If you are using Xfce it is a bit more complex as you have to install NetworkManager, ModemManager, the networkmanager applet and a bunch of gnome dependencies. If you are running Xfce 4.8x then the dependencies are probably already installed. Your will probably have to add gnome-keyring, libgnome-keyring (which doesn't work half the time and forgets pass keys) and glib-networking.

1 members found this post helpful.

He can use KnetworkManager as well. I've managed to compile it from a RPM source package for SuSE 11.4 with no additional dependencies (on latest -current), but I think that you can get the source also from here. Later I'll try to packaged it in a Slackware package. Don't know what will happen if you try to install pre-build RPM package.

Knetworkmanager is dead. It is no longer developed. For KDE 4.x you should use networkmanagement instead. That contains the task bar widget (aka plasmoid) and the systemsettings applet for configuring NetworkManager.

Eric

Robby's Xfce 4.8 repository contains all the dependencies you need to get NM working under Xfce, and NM itself is in the extra/ directory. It's pretty stable. I prefer it over wicd and rc.inet1 on my laptop because I routinely switch between Ethernet, wireless and 3G Internet access and don't want to hassle myself with running scripts to switch between them.

Well, may be you're right, but the source that I get from SusE RPM when compiled produces knetworkmanager binary and some so files. When started it creates icon in notification area (sys tray) with two options in context menu (Enable networking and Manage connections) and it opens KDE systemsettings applet as standalone application if you select Manage connections. I'm not sure whether the source of Network Management from projects.kde.org contains the same code, may be SuSE RPM is some kind of custom implementation specific to SuSE. However, it is suitable only if you have KDE installed along with XFCE.