Differences between revisions 55 and 56
⇤ ← Revision 55 as of 2021-04-25 18:22:58 →
Size: 6390
Editor: ?max
Comment: systemctl tool update
← Revision 56 as of 2021-04-26 05:59:50 → ⇥
Size: 6274
Editor: PaulWise
Comment: cleanups
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
||<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>>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/7/html/Networking_Guide/sec-NetworkManager_and_the_Network_Scripts.html|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}}]] || ||<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}}]] ||
Line 18: Line 18:
For changes in configuration to become effective, you may have to restart the NetworkManager daemon (as user {{{root}}} or using [[sudo]]): For changes in configuration to become effective, you may have to restart the NetworkManager daemon:
Line 20: Line 21:
systemctl restart network-manager sudo service network-manager restart
Line 24: Line 25:
Line 28: Line 30:
Line 34: Line 37:
Line 39: Line 43:
 {{{
{{{
Line 45: Line 50:
 {{{
{{{
Line 54: Line 60:
Line 58: Line 65:
 {{{
systemctl restart network-manager
{{{
sudo service network-manager restart
Line 63: Line 71:
Line 67: Line 76:
Line 76: Line 86:
Line 83: Line 94:
 * [[http://old-en.opensuse.org/Projects/KNetworkManager]] – KDE front-end
Line 88: Line 98:

Translation(s): English – Français – Italiano – German – Português Brasileiro – 简体中文 – Русский

Contents

  1. Features
  2. Documentation
  3. Wired Networks are Unmanaged
  4. Enabling Interface Management
  5. "Auto Ethernet" and "Auto eth0"
  6. FAQ
  7. See Also
  8. External Links

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

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

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

"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