NetworkManager
NetworkManager provides automatic network detection and configuration for the system. Once enabled, the NetworkManager service also monitors the network interfaces, and may automatically switch to the best connection at any given time. Applications that include NetworkManager support may automatically switch between on-line and off-line modes when the system gains or loses network connectivity.
These facilities are most useful for modern laptops, where the user may move between wireless networks, and plug in to a variety of wired networks, but NetworkManager also provides features that are relevant to workstations. Current versions of NetworkManager support modem connections, and certain types of VPN. Development of these features is ongoing.
NetworkManager requires Fedora to have drivers for the wired and wireless interfaces on the computer. Many manufacturers of modems and wireless devices provide limited support for Linux. You may need to install additional drivers or firmware on your Fedora system in order to activate these interfaces.
Intel Wireless Adapters
Centrino laptops use Intel wireless adapters. Fedora Core 4 and above include drivers for Intel wireless adapters, but Fedora may not include the proprietary firmware files needed to activate these devices.
To enable the wireless interfaces on Centrino laptops and other computers that use Intel PRO/Wireless adapters, copy the firmware files to /lib/firmware/
on your system. You may download these files from the IPW2200 Project Website: http://ipw2200.sourceforge.net/.
Reboot your system after installing firmware files, to ensure that the adapter initializes correctly.
See the IPW2200 page for more information.
Enabling NetworkManager on Fedora 6
The installation process for Fedora Core 6 automatically provides NetworkManager. To enable it, enter the following commands in a terminal window:
- Set the main service to automatically start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManager on'
- Set the dispatcher service to automatically start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on'
- Start the services:
su -c '/sbin/service NetworkManager start ; /sbin/service NetworkManagerDispatcher start'
For each
su
command, enter the root password at the prompt.
The NetworkManager tray icon automatically appears on your desktop once the services are started. If the NetworkManager service is active, then the tray icon appears each time that you log in to your desktop.
NetworkManager also stores any W.A.P key in the gnome-keyring manager. If after login, your prompted to enter the keyring password so that NetworkManager can access the key, then keep reading. This can become a daunting task everytime youlogin to enter the keyring password. If your login password & the keyring password are the same, then there is a tool built to open the keyring for you on login.the package is called pam_keyring. This is available in extras. To configure your system first install pam_keyring with yum
su -c 'yum -y install pam_keyring'
Second you'll need to modify your /etc/pam.d/gdm file.
su -c 'gedit /etc/pam.d/gdm'
Add the following lines
auth optional pam_keyring.so try_first_pass session optional pam_keyring.so
The order in which this lines are placed in this file are important, Here is a copy from my system
#%PAM-1.0 auth required pam_env.so auth optional pam_keyring.so try_first_pass <--- auth include system-auth account required pam_nologin.so account include system-auth password include system-auth session optional pam_keyinit.so force revoke session include system-auth session required pam_loginuid.so session optional pam_console.so session optional pam_keyring.so <---
Now reboot your pc. After login the keyring will be unlocked for you. If your keyring password is different from your login password, don't worry, there is a tool available to change it.
su -c 'yum -y install gnome-keyring-manager gnome-keyring pam_keyring
Once you have installed pam_keyring and gnome-keyring, you will need to log out and back on. Then you can run
/usr/libexec/pam-keyring-tool -c
to change the default password. Alternatively you can now change a password through gnome-keyring-manager. Download and install gnome-keyring-manager. Then highlight the keyring and select Change Keyring Password from the Keyring menu of gnome-keyring-manager.
Enabling NetworkManager on Fedora 5
The installation process for Fedora Core 5 automatically provides NetworkManager. To enable it, enter the following commands in a terminal window:
- Set the main service to automatically start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManager on'
- Set the dispatcher service to automatically start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on'
- Start the services:
su -c '/sbin/service NetworkManager start ; /sbin/service NetworkManagerDispatcher start'
For each
su
command, enter the root password at the prompt.
The NetworkManager tray icon automatically appears on your desktop once the services are started. If the NetworkManager service is active, then the tray icon appears each time that you log in to your desktop.
Enabling NetworkManager on Fedora 4
Fedora Core 4 includes packages for NetworkManager. To install and enable NetworkManager on Fedora Core 4, enter the following commands in a terminal window:
- Install the software:
su -c 'yum install NetworkManager NetworkManager-glib NetworkManager-gnome'
- Set the main service to start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManager on'
- Set the dispatcher service to start on boot:
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on'
- Start the services:
su -c '/sbin/service NetworkManager start ; /sbin/service NetworkManagerDispatcher start'
- Now enter this command to load the tray icon:
NetworkManagerInfo &
For each
su
command, enter the root password at the prompt.
If you are upgrading from FC3 via yum, you may need to run /sbin/fixfiles relabel /etc
. Ensure that you have latest SELinux policy package.
NetworkManager and the KDE Desktop
Unfortunately, KDE currently lacks the libraries that would be required to write a desktop control applet. Specifically, the necessary QT-DBUS bindings are not yet ready. QT-DBUS bindings are currently expected to be available as part of KDE 4.0.
Further Information
The Red Hat Magazine article on NetworkManager is a good summary of the technology.