Networkmanager (Русский)
From ArchWiki
i18n |
---|
Русский |
Deutsch |
English |
Italiano |
Español |
Português do Brasil |
简体中文 |
Türkçe |
Contents |
Введение
Network Manager is a set of co-operative tools that make networking simple and straightforward. Whether wireless or wired, Network Manager allows you to quickly move from one network to another: once a network has been configured and joined once, it can be detected and re-joined automatically at a later date.
Network Manager 0.7 is a major overhaul of the NetworkManager program.
Some of the new features include:
- Support for cellular data cards
- Multiple Active Devices
- System-wide Configuration
- wpa_supplicant dbus Control Interface
- More Wireless/Wired Authentication Methods
Шаг 1: Установка
NetworkManager доступен в репозитарии extra. Для его установки наберите следующую команду:
pacman -S networkmanager libnetworkmanager
Шаг 2: Интеграция в окружение рабочего стола
Gnome
network-manager-applet (formerly gnome-network-manager) is available in the extra repository:
pacman -S network-manager-applet
KDE
KDE4
Плазмойд NetworkManager'а для KDE4 можно найти в репозитарии extra, он называется kdeplasma-applets-networkmanager. Обращаем ваше внимание: данный плазмойд находиться на стадии разработки и не является стабильным.
KDE3
You can try to use knetworkmanager which is no longer maintained in any Arch official repositories in binary form. You can get it from the AUR.
Xfce
Xfce uses the same package as GNOME:
pacman -S network-manager-applet
You can also install xfapplet plugin, which allows GNOME applets to be displayed within the xfce4 panel:
pacman -S 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:
- Kill all nm-applet processes
- Add nm-applet --sm-disable to the autostarted applications.
- Log out of xfce.
- Delete the XFCE session file (in ~/.cache/sessions/)
- 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 NetworkManager, to autostart the NetworkManager 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.
Шаг 3: Настройка
Disable the interfaces
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 172.19.3.18 netmask 255.255.255.0 broadcast 172.19.3.255"
example for dynamic IP:
eth0="dhcp"
Изменение имени компьютера в сети
By default NetworkManager 0.7 will do a reverse lookup of your ip to determine your hostname. Most times this will result in "localhost".
The solution is to create the file /etc/NetworkManager/nm-system-settings.conf, and add the following.
[main] plugins = keyfile [keyfile] hostname = <your hostname>
Настройка демонов
You must disable the default network daemon and add the hal and networkmanager daemons in this order:
DAEMONS=( ... !network hal networkmanager ... )
Добавление пользователя в группу network
Add yourself to the network group, replacing USERNAME with the appropriate user name:
# gpasswd -a USERNAME network
Настройка сетевых служб
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 just 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, and in reverse alphabetical order at interface down time. 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).
I found this naming trick useful for the following items: a_portmap b_netfs c_ntpdate d_ntpd e_cups f_clamav I run a local NTP server, and do not connect my laptop to foreign wireless networks. I also make NFS mounts. There's no point in cups if you're not on the network. Clamav's freshclam signature updater requires networking to connect. I may hack on it some to separate the freshclam service from the clamav on-access scanner so I can keep the on-access scanner running all the time but only run freshclam when the networking is up.
Настройка прокси
Network Manager doesn't directly handle proxy settings.
See Proxy settings for more informations.
Проблемы безопасности
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.
There are several options to resolve this issue (Choose only one).
- Install Consolekit and add the following line to /etc/pam.d/kde
session optional pam_ck_connector.so
- Add the following lines to /etc/dbus-1/system.d/NetworkManager.conf
<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
- If none of those work
Refer to this forum: http://bbs.archlinux.org/viewtopic.php?id=63576
Возможные проблемы
Проблемы с DHCP
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.
Продвинутые настроки и твики
Checking Whether Networking Is Up In 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
I find 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.
Автоматическое открытие брелка при входе в GNOME
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 pam_gnome_keyring.so session optional pam_gnome_keyring.so auto_start
In /etc/pam.d/passwd, add this line to the 'password' block:
password optional pam_gnome_keyring.so
Next time you log in, you should get asked if you want the password to be unlocked automatically on login.
See http://live.gnome.org/GnomeKeyring/Pam for reference.
Автоматическое соединение при загрузке системы
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 /etc/NetworkManager/nm-system-settings should look like this:
[main] plugins=keyfile
If this wasn't 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"
And 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.