Differences between revisions 19 and 20
Revision 19 as of 2010-11-28 10:56:59
Size: 5043
Editor: GeoffSimmons
Comment: /etc/NetworkManager/nm-system-settings.conf is moved to /etc/NetworkManager/NetworkManager.conf during postinst as of network-manager 0.8.1-2.
Revision 20 as of 2011-02-05 14:28:03
Size: 4084
Editor: GeoffSimmons
Comment: Amend with details on BTS #530024 resolution, formatting.
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 - [[it/NetworkManager|Italiano]] - [[ru/NetworkManager|Русский]] -~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]|| ~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[it/NetworkManager|Italiano]] - [[ru/NetworkManager|Русский]]-~
Line 6: Line 6:
||<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">[[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}} ||
Line 26: Line 26:
 {i} This ''problem'' is very likely to occur to people who upgrade to [[DebianSqueeze|Squeeze]], see DebianBug:530024 .
Line 28: Line 27:
Unmanaged devices means NetworkManager doesn't handle those devices. This occurs when two conditions are met: 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:
Line 45: Line 46:
To allow NetworkManager to manage wired interfaces, either: 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).
Line 47: Line 48:
 * Comment the relevant lines in {{{/etc/network/interfaces}}} to restore the behavior experienced in [[DebianLenny|Lenny]]. <<BR>> ''or''
 * Set {{{managed=true}}} in {{{NetworkManager.conf}}} if you want network-manager to handle interfaces that are declared in {{{/etc/network/interfaces}}}
=== Enabling Interface Management ===
Line 50: Line 50:
Finally, restart NetworkManager: If you want NetworkManager to handle interfaces that are enabled in {{{/etc/network/interfaces}}}:

 * Set {{{managed=true}}} in {{{/etc/NetworkManager/NetworkManager.conf}}}.
 * Restart NetworkManager:
Line 53: Line 56:
}}}

(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
Line 74: Line 63:
 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) Configure {{{/etc/network/interfaces}}}, see NetworkConfiguration.

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