Difference between revisions of "NetworkManager"

From ArchWiki
Jump to navigation Jump to search
(→‎Disable interfaces: - Replaced section 'Disable interfaces'; really don't think this section is needed. If someone can give me a reason it belongs, please let me know.)
Line 66: Line 66:
 
NetworkManager will require some additional steps to be able run properly.
 
NetworkManager will require some additional steps to be able run properly.
  
=== Disable current network setup ==
+
=== Disable current network setup ===
  
 
You'll want to disable your current network setup to be able to properly test NetworkManager.  First (if using the Arch Linux network scripts) stop the network:
 
You'll want to disable your current network setup to be able to properly test NetworkManager.  First (if using the Arch Linux network scripts) stop the network:

Revision as of 07:09, 21 March 2010

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

"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."
-- Fedora wiki

NetworkManager ver. 0.7 features

NetworkManager version 0.7 is a large overhaul of the program and has added:

  • Support for cellular data cards
  • Multiple Active Devices
  • System-wide Configuration
  • wpa_supplicant dbus Control Interface
  • More Wireless/Wired Authentication Methods

Base install

NetworkManager is available in the official repositories and can be installed by:

# pacman -S networkmanager

Applet install

To configure and have easy access to NetworkManager most people will want to install an applet. The applet usually resides in the system tray (or notification area) and allows network selection and configuration of NetworkManager. Various applets exist for different types of desktops.

GNOME

GNOMEs' applet (formerly gnome-network-manager) can be installed by:

# pacman -S network-manager-applet

KDE4

The KNetworkManager applet (widget) has been made available in KDE version 4.4:

# pacman -S kdeplasma-applets-networkmanagement

KDE3

Though no longer supported, Template:Package AUR is in the AUR:

# yaourt -S knetworkmanager

Xfce

Xfce uses the same applet as GNOME, but you will also want to install the Template:Package Official so that GNOME applets are capable of being displayed in the Xfce4 panel:

# pacman -S xfce4-xfapplet-plugin

Fluxbox and Other WMs

For other desktops, it is recommended to use the GNOME applet. You'll also need to be sure that the GNOME hicolor theme is installed to be able to display the applet:

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

Command line

cnetworkmanager, from the AUR, can be used to configure connections from the command line.

Configuration

NetworkManager will require some additional steps to be able run properly.

Disable current network setup

You'll want to disable your current network setup to be able to properly test NetworkManager. First (if using the Arch Linux network scripts) stop the network:

/etc/rc.d/network stop

Bring down your NIC's (Network Interface Controller, i.e. network card). For example:

ifconfig eth0  down
ifconfig wlan0 down

Edit Template:Filename and where you defined DHCP or a static IP address, comment them out:

#eth0="dhcp"                                                                    
#wlan0="dhcp"                                                                   
INTERFACES=(!eth0 !wlan0)

Set hostname

By default NetworkManager 0.7 will do a reverse lookup of your IP to determine your hostname. Generally, this will result in "localhost" or "localhost.localdomain". It will also attempt to manipulate the hostname of the system on the fly which will occasionally break Xorg.

The solution is to create the file Template:Filename, and add the following:

[main]
plugins = keyfile
 
[keyfile]
hostname = <your hostname>

Make sure you verify that Template:Filename is correct before continuing as NetworkManager may have altered it already before you had a chance to change this setting.

Edit daemons

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

DAEMONS=( ... !network dbus hal networkmanager ... )
Warning: Do not use backgrounding on hal and networkmanager daemons, as it may cause freeze of input devices at Xorg startup.
Note: If you happen to specify the fam daemon in your array, it must appear after networkmanager (the same also applies to portmap and netfs).

fam, however, is obsolete: gamin is recommended to be used to replace fam:

pacman -S gamin

fam should be automatically deleted by pacman. If it is not automatically deleted:

pacman -Rsu fam

Get in the network group

Add yourself to the network group, replacing Template:Codeline with the appropriate user name:

# gpasswd -a USERNAME network

Configure network services

There are quite a few network services that you will not want running until NetworkManager brings up an interface. Good examples are ntpd and network filesystem mounts of various types. NetworkManager can start these services when you bring an interface up, and stop them when you bring it down.

To use this feature, add scripts to /etc/NetworkManager/dispatcher.d and make them executable for all users. For security, make them owned by root:root and writable only by the owner. The scripts will be run in alphabetical order at interface up time (with arguments interface up), and in reverse alphabetical order at interface down time (with arguments interface down). To ensure what order they come up in, simply add an alphabetical character and an underscore at the front of the script name; for example, a_portmap and b_netfs (which ensures that the portmapper is up before NFS mounts are attempted).

A useful naming scheme: a_portmap b_netfs c_ntpdate d_ntpd e_cups f_clamav. Typical usage for this is running a local NTP server on a system that does not connect to foreign wireless networks, and that also employs NFS mounts. There is no point in cups if you are not on the network. Clamav's freshclam signature updater requires networking to connect.

Warning: if you connect to foreign or public networks, be aware of what services you are starting and what servers you expect to be available for them to connect to. You could make a security hole by starting the wrong services while connected to a public network.

Proxy settings

Network Manager does not directly handle proxy settings.

See: Proxy settings

PolicyKit issues

Note: Following is probably not need for KDE 4 anymore, as there should be PolicyKit integration as of KDE 4.3. At least with knetworkmanager from [kdemod-core], the author did not run into any troubles.

Because many Display Managers (including KDM) do not natively support policykit at login, you will run into some permission issues with D-Bus and NetworkManager.

While there are several options to resolve this issue, choose only one:

 session       optional        pam_ck_connector.so
Warning: This may cause the malfunction of KDE PowerDevil.
       <policy group="users">
               <allow send_destination="org.freedesktop.NetworkManager"/>
               <allow send_interface="org.freedesktop.NetworkManager"/>
       </policy>
If this does not work, check if there are any policy errors by starting NetworkManager manually:
 # kill `pidof NetworkManager`
 # NetworkManager --no-daemon
  • Put the following script in ~/.kde4/Autostart or similar for other WMs or DEs:
 #!/bin/bash
 ck-launch-session

Troubleshooting

Some fixes to common problems.

Network Management Disabled

Sometimes when NM shuts down the pid (state) file does not get removed and you will get a 'Network management disabled' message. If this happens, you'l have to remove it manually:

rm /var/lib/NetworkManager/NetworkManager.state

If this happens upon reboot, you can add an action to your Template:Filename to have it removed upon bootup:

nmpid=/var/lib/NetworkManager/NetworkManager.state
[ -f $nmpid ] && rm $nmpid

DHCP problems

If you have problems with getting an IP via DHCP try to add the following to your Template:Filename:

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

Where Template:Codeline is the MAC-adress of this NIC.

Problems starting nm-applet as normal user

Sometimes, the gnome applet fails to start with the following error:

** (nm-applet:2941): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings
service.
  Message: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security
policies in the configuration file'

Or if you can see the nm-applet icon in xfce4's panel's notification area while login as root but can't see it if login as a normal user, it could indicate you need to modify the policy settings to get nm-applet started as normal user. (Try to start nm-applet in terminal as normal user will give you the error above.)

This depends on NetworkManager changing its behaviour since version 0.7, ignoring the "network" group altogether and instead uses ConsoleKit, which seems to be problematic at times. This solution was provided by madhatter:

Add the following to your /etc/dbus-1/system.d/NetworkManager.conf

        <policy group="network">
                <allow send_destination="org.freedesktop.NetworkManager"
                       send_interface="org.freedesktop.NetworkManager"/>
        </policy>
        

And to /etc/dbus-1/system.d/nm-applet.conf

    <policy group="network">
        <allow own="org.freedesktop.NetworkManagerUserSettings"/>
        <allow send_destination="org.freedesktop.NetworkManagerUserSettings"
               send_interface="org.freedesktop.NetworkManagerUserSettings"/>

        <deny send_interface="org.freedesktop.NetworkManagerSettings.Secrets"/>
    </policy>

Loutout and back you should have it in the panel and can select any network to connect, type the password then you are ready to go.

For OpenVpn you need to add following line in Template:Filename

<allow send_destination="org.freedesktop.NetworkManager"
       send_interface="org.freedesktop.NetworkManager.openvpn"/>

in section Template:Codeline.

Missing default route

On at least one KDE4 system, no default route was created when establishing wireless connections with NetworkManager. Changing the route settings of the wireless connection to remove the default selection "Use only for resources on this connection" solved the issue.

3G modem not detected

If NetworkManager (from v0.7.999) does not detect your 3G modem, but you still can connect using wvdial, try installing modemmanager package using Template:Codeline and restart NetworkManager daemon with Template:Codeline. Replug your modem or restart.

VPN problems in Networkmanager 0.7.999

If you get the error message "invalid secrets" when trying to connect to your VPN provider using the PPTP protocol, try installing the git versions instead: networkmanager, nm-applet and the pptp plugin.

Tips and tricks

Checking if networking is up inside a cron job or script

Some cron jobs require networking to be up to succeed. You may wish to avoid running these jobs when the network is down. To accomplish this, add an if test for networking that queries NetworkManager's nm-tool and checks the state of networking. The test shown here succeeds if any interface is up, and fails if they are all down. This is convenient for laptops that might be hardwired, might be on wireless, or might be off the network.

if [ `nm-tool|grep State|cut -f2 -d' '` == "connected" ]; then
       #Whatever you want to do if the network is online
else
       #Whatever you want to do if the network is offline - note, this and the else above are optional
fi

This useful for a cron.hourly script that runs fpupdate for the F-Prot virus scanner signature update, as an example. Another way it might be useful, with a little modification, is to differentiate between networks using various parts of the output from nm-tool; for example, since the active wireless network is denoted with an asterisk, you could grep for the network name and then grep for a literal asterisk.

Automatically unlock keyring after login

This will prevent nm-applet from asking for your keyring password.

  • In Template:Filename (or your corresponding daemon in /etc/pam.d), add these lines at the end of the "auth" and "session" blocks if they do not exist already:
 auth            optional        pam_gnome_keyring.so
 session         optional        pam_gnome_keyring.so  auto_start
 password    optional    pam_gnome_keyring.so
Next time you log in, you should be asked if you want the password to be unlocked automatically on login.
Note: See http://live.gnome.org/GnomeKeyring/Pam for reference, and if you are using kde / kdm, you can use pam-keyring-tool from the AUR.
  • Put a script like the following in ~/.kde4/Autostart:
 $!/bin/sh
 echo PASSWORD | /usr/bin/pam-keyring-tool --unlock --keyring=default -s
Similar should work with openbox, lxde, etc.

Automatically connect on boot

Since version 0.7 the NetworkManager is able to connect on boot, before a user has logged in and unlocked the keyring.

  • First make sure that the keyfile plugin is loaded; Template:Filename should look like this:
 [main]
 plugins=keyfile
  • If this was not in the file before, you have to restart nm-system-settings:
 # killall -TERM nm-system-settings
or simply reboot.
  • Now grant your user the right to modify system-connections with:
 $ sudo polkit-auth --grant org.freedesktop.network-manager-settings.system.modify --user "YOURUSERNAME"
Finally, in the connection-editor, check the Available to all users box.

The connection is now saved in /etc/NetworkManager/system-connections/"CONNECTION NAME". On reboot, NetworkManager will try to connect to it, when in range.

Ignore specific devices

Sometimes it is desired, that network manager ignores some devices and do not try to get an IP.

  • First you have to find out the Hal UDI (e.g. with lshal):
 ...
 info.product = 'Networking Interface'  (string)
 info.subsystem = 'net'  (string)
 info.udi = '/org/freedesktop/Hal/devices/net_00_1f_11_01_06_55'  (string)
 linux.hotplug_type = 2  (0x2)  (int)
 linux.subsystem = 'net'  (string)
 ...
  • Add the udi to /etc/NetworkManager/nm-system-settings.conf:
 [keyfile]
   unmanaged-devices=/org/freedesktop/Hal/devices/net_00_1f_11_01_06_55
Multiple devices can be specified, delimited by semicolons:
 [keyfile]
   unmanaged-devices=/org/freedesktop/Hal/devices/net_00_1f_11_01_06_55;/org/freedesktop/Hal/devices/net_00_2c_6d_e2_08_af

You do not need to restart networkmanager for the changes to take effect.

See also