Differences between revisions 1 and 41 (spanning 40 versions)
Revision 1 as of 2007-12-12 07:58:27
Size: 822
Editor: FranklinPiat
Comment: import page NetworkManagerIntegration (couldn't rename it)
Revision 41 as of 2018-08-11 23:10:33
Size: 5411
Editor: RicardoCosta
Comment: Inserted the link to the brazilian page. Insert a missing A) (Answer) in a FAQ
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
[http://people.redhat.com/dcbw/NetworkManager] aims to manage all network connections itself. However, Debian's networking infrastructure is nicely modular, and it seems a shame to lose a lot of available flexibility for the convenience of !NetworkManager.
#language en
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[fr/NetworkManager|Français]] - [[it/NetworkManager|Italiano]] - [[de/NetworkManager|German]] - [[pt_BR/NetworkManager|Português Brasileiro]] - [[zh_CN/NetworkManager|简体中文]] -[[ru/NetworkManager|Русский]] -~
----
<<TableOfContents(3)>>
----
= NetworkManager =
<<Anchor(intro)>>
||<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://upload.wikimedia.org/wikipedia/commons/c/c0/NetworkManager.png}} ||
----
NetworkManager is composed of two parts:
 1. A daemon running as root (DebianPkg:network-manager).
 1. A front-end (nmcli, nmtui, DebianPkg:network-manager-gnome, DebianPkg:plasma-nm).
Line 4: Line 14:
The ideal solution would be for [http://people.redhat.com/dcbw/NetworkManager] to call out to ifupdown as required, but this has some drawbacks:
 * ifupdown can be used to manage wireless networks
 * could depend on there being a decent ifupdown setup to start with
 * could conflict with other network management tools, such as gnome-system-tools
NetworkManager will only handle interfaces not declared in {{{/etc/network/interfaces}}} (see [[#doc|README]] file).
Line 9: Line 16:
Bug:270538 is an ITP for Network Manager == Features ==
The features of NetworkManager are described on its [[http://projects.gnome.org/NetworkManager/|homepage]].
Line 11: Line 19:
Note : DebPkg:network-manager was shipped with Debian Etch -- -- FranklinPiat [[DateTime(2007-08-05T10:48:18Z)]] <<Anchor(doc)>>
== Documentation ==
Make sure you read the fine manual:
 * [[file:///usr/share/doc/network-manager/README|/usr/share/doc/network-manager/README]] [[https://salsa.debian.org/utopia-team/network-manager/blob/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/master/debian/network-manager.README.Debian|(online)]]
 * [[DebianMan:5/interfaces|interfaces(5)]] man page

<<Anchor(NetworkManager_in_Squeeze)>>
== Wired Networks are Unmanaged ==

As of [[DebianSqueeze|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:
 {{{
/etc/init.d/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 [[file:///usr/share/doc/network-manager-gnome/README.Debian|/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 ==
 * [[PPP]]
 * [[WiFi/HowToUse]]

== External Links ==
 * [[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://old-en.opensuse.org/Projects/KNetworkManager]] - KDE front-end
 * [[DebianMan:1/nmtui|nmtui(1)]] - Interactive text client
 * [[DebianMan:1/nmcli|nmcli(1)]] - Command-line client
----
CategoryNetwork

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



NetworkManager

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://upload.wikimedia.org/wikipedia/commons/c/c0/NetworkManager.png


NetworkManager is composed of two parts:

  1. A daemon running as root (network-manager).

  2. A front-end (nmcli, nmtui, network-manager-gnome, plasma-nm).

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

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
  2. 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:

    /etc/init.d/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