NetworkManager (Español)

From ArchWiki
Revision as of 19:00, 18 January 2010 by Samkpo (talk | contribs) (Created page with 'Category:Internet y correo electrónico (Español) {{i18n_links_start}} {{i18n_entry|Deutsch|:Networkmanager (Deutsch)}} {{i18n_entry|English|:NetworkManager}} {{i18n_entry|…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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 entry Template:I18n links end


Network Manager es un set de herramientas co-operativas que hacen de la creación de redes simple y directa. Sea cableada o inalámbrica, Network Manager te permite mover rapidamente de una conexión a otra: una ves que NetworkManager se ha configurado y conectado a una red, esta puede ser detectada y re-conectada automáticamente a posteriori.

La versión 0.7 es una versión importante de Network Manager.

Algunas de las nuevas características incluyen:

   * Soporte para tarjetas de datos celulares
   * Diversos dispositivos activos
   * Configuración global del sistema
   * Interfaz de control dbus wpa_supplicant
   * Mas métodos de autenticación para redes cableadas/inalámbricas

Paso 1: Instalación

NetworkManager esta disponible en los repositorios:

# pacman -S networkmanager

Paso 2: GUIs


network-manager-applet (anteriormente gnome-network-manager) también esta ahi:

# pacman -S network-manager-applet

Si ningún icono de nm-applet esta en uno de tus paneles en Gnome, y si embargo estas seguro de que se esta ejecutando, intenta agregando un "Área de notificación" al panel.


Note: si las instrucciones siguientes no funcionan, network-manager-applet es una opción.


KNetworkManager esta disponible en los repositorios extra. Podes instalarlo con:

# pacman -S kdeplasma-applets-networkmanager

Hay una nueva versión de KNetworkManager en [kdemod-core] que proporciona un icono en la bandeja del sistema y la configuración:

# pacman -S kdemod-networkmanagement-knetworkmanager-kde4


Puedes intentar usar knetworkmanager el cual ya no es mantenido en ningún repositorio oficial de Arch. Puedes obtenerlo desde AUR.


Xfce usa el mismo paquete que GNOME:

# pacman -S network-manager-applet 

También podes instalar el plugin xfapplet, el cual permite que los applets de GNOME sean visualizados en el panel de xfce4:

# pacman -S xfce4-xfapplet-plugin

Si después de la instalación tenes cuatro o más instancias de nm-applet ejecutándose cuando los servicios de gnome inician automáticamente y vos no estas usando un administrador de sesión, considera hacer lo siguiente:

  1. Matar todos los procesos de nm-applet
  2. Agregar Template:Codeline a la lista de aplicaciones al inicio
  3. Salir de Xfce
  4. Borrar el archivo de sesión de XFCE (en Template:Filename)
  5. Ingresar en Xfce

Fluxbox y otros WMs

Necesitarás el tema hicolor para poder ejecutar nm-applet:

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

Después de configurar tu sistema para usarlo con NetworkManager, el inicio automático del applet se hace yendo a Configuración → Aplicaciones al inicio luego agrega, Template:Codeline. Esto deberia iniciar el network manager applet al inicio. La opción Template:Codeline es usada para prevenir multiples instancias de el nm-applet, y solo lo necesitas si multiples instancias se estan ejecutando cuando inicias sesión.

  • NetworkManager parece tener problemas para cargar en varios box-environments y compiz. Usando el prefijo ck-launch-session, nm-applet parece trabajar bien.


exec ck-launch-session startlxde

Command line

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

Step 3: Configuration

Disable interfaces

If you want to use NetworkManager on an interface you will have to disable it in Template:Filename. You can do this by placing a Template:Codeline in front of the interface of your choice, for example:

INTERFACES=(!eth0 !ath0)
Note: You may have to enable (i.e, remove the Template:Codeline) eth0 again afterwards for my card to work. Confirmed with ath_pci madwifi module – you may also have to re-enable the network cards for them to work.

NetworkManager parses Template:Filename to see if you want to have a static or dynamic IP on your interfaces, so state your preferred configuration there.

Example for static IP:

 eth0="eth0 netmask broadcast"

Example for dynamic IP:


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:

plugins = 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 hal and networkmanager daemons in this order:

DAEMONS=( ... !network 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 if specified.

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
Warning: This may cause the malfunction of KDE PowerDevil.
       <policy group="users">
               <allow send_destination="org.freedesktop.NetworkManager"/>
               <allow send_interface="org.freedesktop.NetworkManager"/>
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:


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
  Message: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security
policies in the configuration file'

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:

Edit your /etc/dbus-1/system.d/NetworkManager.conf to read:

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
        <policy user="root">
                <allow own="org.freedesktop.NetworkManager"/>
                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>

        <allow own="org.freedesktop.NetworkManager.PPP"/>
                <allow send_destination="org.freedesktop.NetworkManager.PPP"/>
                <allow send_interface="org.freedesktop.NetworkManager.PPP"/>
        <policy group="network">
                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>
        <policy at_console="true">
                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>
        <policy context="default">
                <deny own="org.freedesktop.NetworkManager"/>
                <deny send_destination="org.freedesktop.NetworkManager"/>
                <deny send_interface="org.freedesktop.NetworkManager"/>

                <deny own="org.freedesktop.NetworkManager.PPP"/>
                <deny send_destination="org.freedesktop.NetworkManager.PPP"/>
                <deny send_interface="org.freedesktop.NetworkManager.PPP"/>

        <limit name="max_replies_per_connection">512</limit>

Also, change your /etc/dbus-1/system.d/nm-applet.conf to read:

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
    <policy user="root">
        <allow own="org.freedesktop.NetworkManagerUserSettings"/>

        <allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
        <allow send_interface="org.freedesktop.NetworkManagerSettings"/>

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

        <deny send_interface="org.freedesktop.NetworkManagerSettings.Secrets"/>
    <policy at_console="true">
        <allow own="org.freedesktop.NetworkManagerUserSettings"/>

        <allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
        <allow send_interface="org.freedesktop.NetworkManagerSettings"/>

        <deny send_interface="org.freedesktop.NetworkManagerSettings.Secrets"/>
    <policy context="default">
        <deny own="org.freedesktop.NetworkManagerUserSettings"/>

        <allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
        <allow send_interface="org.freedesktop.NetworkManagerSettings"/>
        <deny send_interface="org.freedesktop.NetworkManagerSettings.Secrets"/>

    <limit name="max_replies_per_connection">512</limit>

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

<allow send_destination="org.freedesktop.NetworkManager" />
<allow 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.

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
       #Whatever you want to do if the network is offline - note, this and the else above are optional

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
 session         optional  auto_start
 password    optional
Next time you log in, you should be asked if you want the password to be unlocked automatically on login.
Note: See 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:
 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:
  • 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 --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:
Multiple devices can be specified, delimited by a semicolon:

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

See also