Differences between revisions 15 and 64 (spanning 49 versions)
Revision 15 as of 2010-04-30 18:11:15
Size: 5097
Editor: ?hpvmgulo
Comment:
Revision 64 as of 2021-12-14 11:13:52
Size: 7270
Comment: fix header mistake
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[NetworkManager|Русский]] -~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]|| ##For Translators - to have a constantly up to date translation header in you page, you can just add a line like the following (with the comment's character at the start of the line removed)
## <<Include(NetworkManager, ,from="^##TAG:TRANSLATION-HEADER-START",to="^##TAG:TRANSLATION-HEADER-END")>>
##TAG:TRANSLATION-HEADER-START
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: [[NetworkManager|English]] – [[fr/NetworkManager|Français]] – [[it/NetworkManager|Italiano]] – [[de/NetworkManager|German]] – [[pt_BR/NetworkManager|Português (Brasil)]] – [[zh_CN/NetworkManager|简体中文]] – [[ru/NetworkManager|Русский]] -~
##TAG:TRANSLATION-HEADER-END
Line 4: Line 9:
= NetworkManager = <<TableOfContents(3)>>
----
Line 6: Line 12:
||<tablestyle="width:100%" style="border:0;vertical-align:top">[[http://www.gnome.org/projects/NetworkManager/|NetworkManager]] attempts to keep an active network connection available at all times.<<BR>><<BR>>The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is __intended__ to replace default routes, obtain IP addresses from a DHCP server and change nameservers whenever it sees fit. In effect, the goal of NetworkManager is to make networking __Just Work__.<<BR>><<BR>>If you have special needs, The upstream's developers would like to hear about them, but understand that NetworkManager is not intended to serve the needs of all users. ||<style="border:0"> {{http://www.gnome.org/projects/NetworkManager/images/wireless-at-tealuxe.png}} || ||<tablestyle="width:100%" style="border:0;vertical-align:top">[[https://wiki.gnome.org/Projects/NetworkManager|NetworkManager]] attempts to keep an active network connection available at all times.<<BR>><<BR>>The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is __intended__ to replace default routes, obtain IP addresses from a DHCP server and change nameservers whenever it sees fit. In effect, the goal of NetworkManager is to make networking __Just Work__.<<BR>><<BR>>Whilst it was originally targeted at desktops, it has more recently been chosen as the default network management software for some [[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/index|non-Debian server-oriented Linux distributions.]] If you have special needs, the upstream's developers would like to hear about them, but understand that NetworkManager is not intended to serve the needs of all users. ||<style="border:0;vertical-align: top;"> [[https://commons.wikimedia.org/wiki/File:NetworkManager.png|{{https://upload.wikimedia.org/wikipedia/commons/c/c0/NetworkManager.png}}]] ||
If not using Network Manager:
 * For basic or simple configurations (e.g. workstation), the regular way to configure the network was using interfaces configuration file at /etc/network/interfaces. Details are described in NetworkConfiguration. It still may be used.
 * Another way to configure: leverage on [[https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_without_gui|Systemd]]
Line 8: Line 17:
NetworkManager is composed of two parts:
 1. A daemon running as root (DebianPkg:network-manager).
 1. A front-end (DebianPkg:network-manager-gnome, DebianPkg:network-manager-kde or DebianPkg:cnetworkmanager).
NetworkManager is composed of two layers:
 1. A daemon running as root: DebianPkg:network-manager.
 1. A front-end: nmcli and nmtui (enclosed in package {{{network-manager}}}), DebianPkg:nm-tray, DebianPkg:network-manager-gnome (nm-applet), DebianPkg:plasma-nm.
Additionally, there are various plugins available that enable NetworkManager to handle other, special connections like different types of VPN connections.
Line 14: Line 24:
NetworkManager keeps connection information on known individual networks in configuration files called ''profiles''. Those are stored at [[file:///etc/NetworkManager/system-connections/|/etc/NetworkManager/system-connections/]]. For options in these files refer to the manpage on nm-settings: {{{man nm-settings}}} or [[DebianMan:nm-settings|online]]. They can be edited (as [[root]]) using a text editor or the nm-connection-editor (enclosed in {{{network-manager-gnome}}}).

For changes in configuration to become effective, you may have to restart the NetworkManager daemon:

{{{
sudo service network-manager restart
}}}

Starting with Debian 11 (bullseye), use:
{{{
sudo service NetworkManager restart
}}}
Line 15: Line 38:
The features of NetworkManager are described on its [[http://projects.gnome.org/NetworkManager/|homepage]].
The features of NetworkManager are described on its [[https://wiki.gnome.org/Projects/NetworkManager|homepage]].
Line 19: Line 43:
Line 20: Line 45:
 * [[file:///usr/share/doc/network-manager/README|/usr/share/doc/network-manager/README]] and [[file:///usr/share/doc/network-manager/README.Debian|/usr/share/doc/network-manager/README.Debian]]  * [[file:///usr/share/doc/network-manager/README|/usr/share/doc/network-manager/README]] ([[https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/README|online]]) and [[file:///usr/share/doc/network-manager/README.Debian|/usr/share/doc/network-manager/README.Debian]] ([[https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/debian/network-manager.README.Debian|online]])
Line 23: Line 48:
== NetworkManager in Squeeze == <<Anchor(NetworkManager_in_Squeeze)>>
== Wired Networks are Unmanaged
==
Line 25: Line 51:
=== Wired Networks are Unmanaged ===
 {i} This ''problem'' is very likely to occur to people who upgrade to [[DebianSqueeze|Squeeze]], see DebianBug:530024 .
As of [[DebianSqueeze|Debian 6.0 "Squeeze"]], NetworkManager does not manage '''any''' interface defined in {{{/etc/network/interfaces}}} by default.
Line 28: Line 53:
Unmanaged devices means NetworkManager doesn't handle those devices. This occurs when two conditions are met: Unmanaged devices means NetworkManager doesn't handle those network devices. This occurs when two conditions are met:
Line 31: Line 56:
 {{{
{{{
Line 36: Line 62:
 1. And {{{/etc/NetworkManager/nm-system-settings.conf}}} contains:
 {{{
 1. And {{{/etc/NetworkManager/NetworkManager.conf}}} contains:

{{{
Line 45: Line 72:
To allow NetworkManager to manage wired interfaces, either: == Enabling Interface Management ==
Line 47: Line 74:
 * Comment the relevant lines in {{{/etc/network/interfaces}}} to restore the behavior experienced in [[DebianLenny|Lenny]]. <<BR>> ''or''
 * Set {{{managed=true}}} in {{{nm-system-settings.conf}}} if you want network-manager to handle interfaces that are declared in {{{/etc/network/interfaces}}} (you need to kill {{{nm-system-settings}}})
If you want NetworkManager to handle interfaces that are enabled in {{{/etc/network/interfaces}}}:
Line 50: Line 76:
Restart network-manager or X is not enough. It seems you must reboot your computer in order to apply your changes.
 
(Click on the <<GetText(Comments)>> to show Syslog error's error message related to this problem): {{{#!wiki comment
NetworkManager: <info> starting...
NetworkManager: <info> (eth0): new Ethernet device (driver: 'e1000e')
NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1a_6b_38_00_e0
NetworkManager: <info> Trying to start the system settings daemon...
nm-system-settings: SCPlugin-Ifupdown: init!
nm-system-settings: SCPlugin-Ifupdown: update_system_hostname
nm-system-settings: SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
nm-system-settings: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, autoconnect:0, id:Ifupdown (eth0)
nm-system-settings: SCPluginIfupdown: management mode: unmanaged
nm-system-settings: SCPlugin-Ifupdown: devices added (udi:/org/freedesktop/Hal/devices/net_00_1a_6b_38_00_e0, iface: eth0)
nm-system-settings: Ifupdown: get unmanaged devices count: 1
 * Set {{{managed=true}}} in {{{/etc/NetworkManager/NetworkManager.conf}}}.
 * Restart NetworkManager:

{{{
sudo service network-manager restart
Line 66: Line 83:
=== "Auto Ethernet" and "Auto eth0" ===
 * ''Auto Ethernet'' means "Select and Ethernet interface automatically"
 * ''Auto eth0'' means ''autconfigure the eth0 interface''.
Starting with Debian 11 (bullseye), use:
{{{
sudo service NetworkManager restart
}}}

== "Auto Ethernet" and "Auto eth0" ==

 * ''Auto Ethernet'' means "Select an Ethernet interface automatically"
 * ''Auto eth0'' means "autoconfigure the eth0 interface".
Line 71: Line 94:
 Q. How do I configure a static IP address (for a server, etc) ? :: A) Configure {{{/etc/network/interfaces}}}.
 Q. How do I configure a static IP address (for a server, etc) ? :: A) Use nm-connection-editor or configure {{{/etc/network/interfaces}}} as described in NetworkConfiguration.

 Q. How can I configure DNS for NetworkManager? :: A) The short answer is to use nm-connection-editor. For the long answer see the corresponding entry in NetworkConfiguration.
Line 75: Line 101:
 Q. How to setup a connection sharing ("hotspot") for a wired interface ? :: A) First make sure to install dnsmasq-base (but not dnsmasq unless you disable the system daemon in /etc/default/dnsmasq). Then use nm-connection-editor and setup a new profile using "shared to other computer" as the method for IPv4 (not possible from Gnome3's gnome-control-center). This hides all the complexity (dnsmasq, iptables, sysctl). Finally, use that profile for the network interface connected to the shared network. For Wi-Fi interfaces, a hotspot functionality is provided which uses the same functionality besides setting up an ad-hoc WiFi network.
 
Line 76: Line 104:
Line 78: Line 107:
 * [[VPN-client|VPN clients. Some of them use Network Manager.]]
Line 80: Line 110:
 * [[http://projects.gnome.org/NetworkManager/users/]] - Project homepage and GNOME front-end (with some documentation);
  * [[http://live.gnome.org/NetworkManager]] - Various resources (FAQ, mailing list...)
 * [[http://en.opensuse.org/Projects/KNetworkManager]] - KDE front-end
 * [[http://vidner.net/martin/software/cnetworkmanager/]] - Command-line client

 * [[https://wiki.gnome.org/Projects/NetworkManager]] – Project homepage and GNOME front-end (with some documentation)
 * [[DebianMan:1/nmtui|nmtui(1)]] – Interactive text client
 * [[DebianMan:1/nmcli|nmcli(1)]] – Command-line client
Line 85: Line 116:
CategoryNetwork CategoryNetwork CategorySoftware

Translation(s): EnglishFrançaisItalianoGermanPortuguês (Brasil)简体中文Русский



NetworkManager attempts to keep an active network connection available at all times.

The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is intended to replace default routes, obtain IP addresses from a DHCP server and change nameservers whenever it sees fit. In effect, the goal of NetworkManager is to make networking Just Work.

Whilst it was originally targeted at desktops, it has more recently been chosen as the default network management software for some non-Debian server-oriented Linux distributions. If you have special needs, the upstream's developers would like to hear about them, but understand that NetworkManager is not intended to serve the needs of all users.

https://commons.wikimedia.org/wiki/File:NetworkManager.png

If not using Network Manager:

  • For basic or simple configurations (e.g. workstation), the regular way to configure the network was using interfaces configuration file at /etc/network/interfaces. Details are described in NetworkConfiguration. It still may be used.

  • Another way to configure: leverage on Systemd


NetworkManager is composed of two layers:

  1. A daemon running as root: network-manager.

  2. A front-end: nmcli and nmtui (enclosed in package network-manager), nm-tray, network-manager-gnome (nm-applet), plasma-nm.

Additionally, there are various plugins available that enable NetworkManager to handle other, special connections like different types of VPN connections.

NetworkManager will only handle interfaces not declared in /etc/network/interfaces (see README file).

NetworkManager keeps connection information on known individual networks in configuration files called profiles. Those are stored at /etc/NetworkManager/system-connections/. For options in these files refer to the manpage on nm-settings: man nm-settings or online. They can be edited (as root) using a text editor or the nm-connection-editor (enclosed in network-manager-gnome).

For changes in configuration to become effective, you may have to restart the NetworkManager daemon:

sudo service network-manager restart

Starting with Debian 11 (bullseye), use:

sudo service NetworkManager restart

Features

The features of NetworkManager are described on its homepage.

Documentation

Make sure you read the fine manual:

Wired Networks are Unmanaged

As of Debian 6.0 "Squeeze", NetworkManager does not manage any interface defined in /etc/network/interfaces by default.

Unmanaged devices means NetworkManager doesn't handle those network devices. This occurs when two conditions are met:

  1. The file /etc/network/interfaces contains anything about the interface, even:

allow-hotplug eth0
iface eth0 inet dhcp
  1. And /etc/NetworkManager/NetworkManager.conf contains:

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

Enabling Interface Management

If you want NetworkManager to handle interfaces that are enabled in /etc/network/interfaces:

  • Set managed=true in /etc/NetworkManager/NetworkManager.conf.

  • Restart NetworkManager:

sudo service network-manager restart

Starting with Debian 11 (bullseye), use:

sudo service NetworkManager restart

"Auto Ethernet" and "Auto eth0"

  • Auto Ethernet means "Select an Ethernet interface automatically"

  • Auto eth0 means "autoconfigure the eth0 interface".

FAQ

Q. How do I configure a static IP address (for a server, etc) ?

A) Use nm-connection-editor or configure /etc/network/interfaces as described in NetworkConfiguration.

Q. How can I configure DNS for NetworkManager?

A) The short answer is to use nm-connection-editor. For the long answer see the corresponding entry in NetworkConfiguration.

Q. Why can't I see NetworkManager with my new user account ?

A) Make sure human users are in the netdev group (see /usr/share/doc/network-manager-gnome/README.Debian).

Q. How to setup a connection sharing ("hotspot") for a wired interface ?

A) First make sure to install dnsmasq-base (but not dnsmasq unless you disable the system daemon in /etc/default/dnsmasq). Then use nm-connection-editor and setup a new profile using "shared to other computer" as the method for IPv4 (not possible from Gnome3's gnome-control-center). This hides all the complexity (dnsmasq, iptables, sysctl). Finally, use that profile for the network interface connected to the shared network. For Wi-Fi interfaces, a hotspot functionality is provided which uses the same functionality besides setting up an ad-hoc WiFi network.

See Also


CategoryNetwork CategorySoftware