From ArchWiki
Revision as of 19:11, 5 September 2008 by Georgia tech swagger (Talk | contribs) (KDE)

Jump to: navigation, search

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n links end


NetworkManager is an advanced network connection tool. It attempts to make networking invisible to the end user, so that when moving into areas you've been before, NetworkManager automatically connects to the last network you chose to connect to.


Check that wireless_tools is installed first, otherwise Networkmanager won't work.

Also check that HAL[[1]] is installed, and loaded as a daemon in rc.conf. You may have to enable dbus as a daemon as well, or Networkmanager may crash.


# pacman -S gnome-network-manager


WARNING: As of 9/2/08, knetworkmanager is no longer in any Arch official repositories. Use "knetworkmanager3" in AUR instead.

# pacman -S knetworkmanager


Xfce uses the same package as GNOME, however it requires the xfapplet plugin as well, which allows GNOME applets to be displayed within the xfce4-panel:

# pacman -S gnome-network-manager xfce4-xfapplet-plugin

If after installation you get four or more instances of nm-applet running when automatically starting gnome services and you're not using a session manager; consider doing the following:

1) Kill all nm-applet processes
2) Add nm-applet --sm-disable to the autostarted applications.
3) Log out of xfce.
4) Delete the XFCE session file (in ~/.cache/sessions/)
5) Log into xfce and all is good.

Fluxbox and Other WM's

You will need the hicolor theme to be able to run nm-applet:

# pacman -S gnome-network-manager hicolor-icon-theme

After configuring your system for use with the network manager, to autostart the network manager applet, go to settings --> Autostarted Applications then add, "nm-applet --sm-disable &", This should start up the network manager applet on startup, the "--sm-disable" option is used to prevent multiple instances of the nm-applet, you should only need it if multiple instances are running when you startup.


If you want to use NetworkManager on an interface you will have to disable it in /etc/rc.conf. You can do this by placing a '!' in front of the interface of your choice, for example:

INTERFACES=(lo !eth0 !ath0)

Note: I had to enable (i.e, remove the '!') eth0 again afterwards for my card to work, although YMMV. Confirmed with ath_pci madwifi module - I also had to re-enable my cards for them to work.

NetworkManager parses your /etc/rc.conf to see if you want to have a static or dynamic IP on your interfaces.

So just put your preferred config into it.

example for static IP:

 eth0="eth0 netmask broadcast"

example for dynamic IP:


You must also "disable" the default network daemon, and add the hal, dhcdbd and networkmanager daemons in this order:

DAEMONS=( ... !network hal dhcdbd networkmanager ... )

Note: If you happen to specify the fam daemon in your array, it must appear after networkmanager. The same also applies to portmap if specified.

Finally, add yourself to the network group as shown below (replacing USERNAME with the appropriate username):

# gpasswd -a USERNAME network

Note: If you have problems with getting an IP via DHCP try to add the following to your /etc/dhclient.conf:

 interface "eth0" {
   send dhcp-client-identifier 01:aa:bb:cc:dd:ee:ff;

Where aa:bb:cc:dd:ee:ff is the MAC-adress of this nic.

Automatically unlock keyring in GNOME after login

This will prevent nm-applet from asking for your keyring password. Note that this will only work when logging in via GDM.

In /etc/pam.d/gdm, add these lines at the end of the 'auth', 'session' blocks:

auth            optional
session         optional  auto_start

In /etc/pam.d/passwd, add this line to the 'password' block:

password    optional

Next time you log in, you should get asked if you want the password to be unlocked automatically on login.

See for reference.

Additional Resources