Differences between revisions 1 and 21 (spanning 20 versions)
Revision 1 as of 2007-12-12 07:58:27
Size: 822
Editor: FranklinPiat
Comment: import page NetworkManagerIntegration (couldn't rename it)
Revision 21 as of 2011-03-25 11:49:30
Size: 4108
Comment: added table of contents
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 - [[it/NetworkManager|Italiano]] - [[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>>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}} ||
----
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).
Line 4: Line 13:
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 15:
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 18:
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]] and [[file:///usr/share/doc/network-manager/README.Debian|/usr/share/doc/network-manager/README.Debian]]
 * [[DebianMan:5/interfaces|interfaces(5)]] man page

== NetworkManager in Squeeze ==

=== Wired Networks are Unmanaged ===

As of Debian [[DebianSqueeze|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
}}}

Since DebianPkg:network-manager version 0.8.1-4, existing wired/wireless interfaces in {{{/etc/network/interfaces}}} are disabled with a #NetworkManager# prefix during package installation, then re-enabled when the network-manager package is removed (Debian bug DebianBug:530024).

=== 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 "autconfigure the eth0 interface".

== FAQ ==
 Q. How do I configure a static IP address (for a server, etc) ? :: A) Configure {{{/etc/network/interfaces}}}, see 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]]).

== 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://en.opensuse.org/Projects/KNetworkManager]] - KDE front-end
 * [[http://vidner.net/martin/software/cnetworkmanager/]] - Command-line client
----
CategoryNetwork

Translation(s): English - Italiano - Русский


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.

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.

http://www.gnome.org/projects/NetworkManager/images/wireless-at-tealuxe.png


NetworkManager is composed of two parts:

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

  2. A front-end (network-manager-gnome, network-manager-kde or cnetworkmanager).

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:

NetworkManager in Squeeze

Wired Networks are Unmanaged

As of Debian 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

Since network-manager version 0.8.1-4, existing wired/wireless interfaces in /etc/network/interfaces are disabled with a #NetworkManager# prefix during package installation, then re-enabled when the network-manager package is removed (Debian bug 530024).

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 "autconfigure the eth0 interface".

FAQ

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

A) Configure /etc/network/interfaces, see 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).

See Also


CategoryNetwork