Jump to content

NetworkManager

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Magioladitis (talk | contribs) at 23:04, 27 July 2014 (Replace unicode entity nbsp for character [NBSP] (or space) per WP:NBSP + other fixes, replaced: → (6) using AWB (10331)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

NetworkManager
Original author(s)Red Hat
Initial releaseNovember 19, 2004; 19 years ago (2004-11-19)
Stable release
0.9.9.98 / June 21, 2014; 10 years ago (2014-06-21)
Repository
Written inC with GObject
Operating systemSUS/POSIX
Type
LicenseGNU GPL
Websitehttp://projects.gnome.org/NetworkManager/

NetworkManager is a software utility aimed at simplifying the use of computer networks on Linux-based and other Unix-like operating systems.

History

Red Hat initiated a NetworkManager project in 2004 with the goal of enabling Linux users to deal more easily with modern networking needs, particularly wireless networking. NetworkManager takes an opportunistic approach to network selection, attempting to use the best available connection as outages occur, or as the user roams between wireless networks. It prefers Ethernet connections over “known” wireless networks, which are preferred over wireless networks with SSIDs to which the user has never connected. The user is prompted for WEP or WPA keys as needed.

The NetworkManager project was among the first major Linux desktop components to utilize D-Bus and HAL extensively. Since June 2009, however, NetworkManager no longer depends on HAL. Since 0.9.10 (~2014), NetworkManager doesn't require the D-Bus daemon to be running for root operation.[1]

Software architecture

NetworkManager has two components:

  1. the NetworkManager daemon, the actual software which manages connections and reports network changes
  2. several graphical front-ends for diverse surfaces, such as GNOME Shell, GNOME Panel, KDE Plasma Workspaces, Cinnamon, etc.

Both components are intended by the developers to be reasonably portable, and the applet is available to desktop environments which implement the Freedesktop.org System Tray Protocol,[2] including GNOME, KDE Plasma Workspaces, Enlightenment (window manager) and Xfce. As the components communicate via D-Bus, applications can be written to be “link-aware”, or to replace the provided applet entirely. One example is KNetworkManager, a KDE frontend to NetworkManager developed by Novell for SUSE Linux.

Graphical front-ends

NetworkManagement
NetworkManager back-end for KDE SC 4, provides a plasma widget frontend.[3]
KNetworkManager
the K Desktop Environment 3 frontend developed by Novell.[4]
nm-applet
is the GNOME applet for NetworkManager.
nmcli
built-in command line interface (added in 2010,[5] e.g. in Fedora 13 Alpha,[6] which was released in late May 2010).
cnetworkmanager
command line interface for NetworkManager.[7]

Mobile broadband configuration assistant

Antti Kaijanmäki announced the development of a mobile broadband configuration assistant for NetworkManager in April 2008[8] it became available in NetworkManager version 0.7.0. Together with the package mobile-broadband-provider-info the connection is easily configured.

See also

References

  1. ^ http://blogs.gnome.org/dcbw/2014/06/20/well-build-a-dream-house-of-net/
  2. ^ Havoc Pennington <hp@redhat.com>. "System Tray Protocol Specification". Standards.freedesktop.org. Retrieved 2012-02-04.{{cite web}}: CS1 maint: extra punctuation (link) CS1 maint: multiple names: authors list (link)
  3. ^ "NetworkManagement GIT". Projects.kde.org. Retrieved 2012-02-04.
  4. ^ KNetworkManager documentation[dead link]
  5. ^ Initial pieces of nmcli, gitweb
  6. ^ Features/NetworkManagerCmdline - FedoraProject wiki, Fedora 13 Alpha release notes - FedoraProject wiki
  7. ^ "cnetworkmanager - Command Line Interface for NetworkManager". Vidner.net. Retrieved 2012-02-04.
  8. ^ "Announce on networkmanager-list". Mail.gnome.org. 2008-04-10. Retrieved 2012-02-04.
  9. ^ "UMTSmon". Umtsmon.sourceforge.net. Retrieved 2012-02-04.