822
Comment: import page NetworkManagerIntegration (couldn't rename it)
|
5100
|
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 ||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[ru/NetworkManager|Русский]] -~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]|| ---- = 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 12: |
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 14: |
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 17: |
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 === {i} This ''problem'' is very likely to occur to people who upgrade to [[DebianSqueeze|Squeeze]], see DebianBug:530024 . Unmanaged devices means NetworkManager doesn't handle those 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/nm-system-settings.conf}}} contains: {{{ [main] plugins=ifupdown,keyfile [ifupdown] managed=false }}} To allow NetworkManager to manage wired interfaces, either: * 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}}}) 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 }}} === "Auto Ethernet" and "Auto eth0" === * ''Auto Ethernet'' means "Select and 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}}}. 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 |
NetworkManager
NetworkManager attempts to keep an active network connection available at all times. |
|
NetworkManager is composed of two parts:
A daemon running as root (network-manager).
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:
/usr/share/doc/network-manager/README and /usr/share/doc/network-manager/README.Debian
interfaces(5) man page
NetworkManager in Squeeze
Wired Networks are Unmanaged
Unmanaged devices means NetworkManager doesn't handle those devices. This occurs when two conditions are met:
The file /etc/network/interfaces contains anything about the interface, even:
allow-hotplug eth0 iface eth0 inet dhcp
And /etc/NetworkManager/nm-system-settings.conf contains:
[main] plugins=ifupdown,keyfile [ifupdown] managed=false
To allow NetworkManager to manage wired interfaces, either:
Comment the relevant lines in /etc/network/interfaces to restore the behavior experienced in Lenny.
orSet 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)
Restart network-manager or X is not enough. It seems you must reboot your computer in order to apply your changes.
(Click on the Comments to show Syslog error's error message related to this problem):
"Auto Ethernet" and "Auto eth0"
Auto Ethernet means "Select and 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.
- 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
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