No description, website, or topics provided.
C Python C++ Shell Ruby Objective-C
Switch branches/tags
Nothing to show
Latest commit 2748bcf Apr 4, 2014 @thom311 thom311 examples: fix qt demo to work without STL support
The function toStdString() is only available when QT was
compiled with STL support. The configure script does
not check STL support and might build the QT examples
even if toStdString() is not available.

Fix this, by not using the function.

This fixes the previous commit f73e366
that I pushed accidentally.

Signed-off-by: Thomas Haller <>
Failed to load latest commit information.
callouts libnm-util, libnm-glib: add versioned deprecation/availability macros Feb 13, 2014
cli fix typos in documentation and messages Apr 3, 2014
data systemd: update NetworkManager-wait-online.service to wait for startup Mar 31, 2014
docs libnm-util, libnm-glib: add versioned deprecation/availability macros Feb 13, 2014
examples examples: fix qt demo to work without STL support Apr 4, 2014
include platform, devices: add support for vxlan devices Mar 6, 2014
initscript remove paldo initscript May 6, 2013
introspection fix typos in documentation and messages Apr 3, 2014
libgsystem @ 856b8f9 libgsystem: update libgsystem to latest master Jan 16, 2014
libnm-glib trivial: make clear the maximum bitrate is in kbit/s Apr 1, 2014
libnm-util libnm-util: fix leaks in test-general Apr 1, 2014
m4 build: add -Wformat-security to the default warning flags Apr 2, 2014
man man: use correct Mbit/s for maximum bitrate in nmcli-examples Apr 1, 2014
po po: fix "MB/s" -> "Mbit/s" Apr 1, 2014
policy policy: fix policy after dcbw/kill-at-console merge (bgo #707983) (rh… Jan 24, 2014
src platform: workaround older kernels that don't accept extended address… Apr 4, 2014
test nm-online: fix considering the --quiet option Mar 31, 2014
tools libnm-util, libnm-glib: add versioned deprecation/availability macros Feb 13, 2014
tui tui: allow ^Z to suspend the app Mar 24, 2014
vapi build: fix Vala bindings build and distcheck Mar 12, 2013
.dir-locals.el misc: add toplevel .dir-locals file that tells Emacs to show trailing… Mar 8, 2013
.gitignore libnm-glib: add testing framework and testcases Jan 23, 2014
.gitmodules build: drop the libndp submodule Feb 3, 2014
AUTHORS Update authors Nov 19, 2008
CONTRIBUTING doc: update code style docs Oct 7, 2009
COPYING docs: create new master NM documentation module Feb 16, 2011
ChangeLog fix typos in documentation and messages Apr 3, 2014
MAINTAINERS Update MAINTAINERS Sep 2, 2007 build: improve our use of glib's version macros to catch more bugs Feb 13, 2014
Makefile.glib build: update Makefile.glib Apr 19, 2013
NEWS release: update NEWS Jan 15, 2013 build: update NetworkManager.pc Jan 29, 2013
README trivial: typo fixes Sep 25, 2010
TODO todo: remove item about finished VPN IPv6 support Apr 10, 2013 build: drop the libndp submodule Feb 3, 2014 core: build with SELinux; don't break /etc/hostname context (rh #1070… Mar 31, 2014
valgrind.suppressions test: add valgrind suppressions Feb 18, 2014


2008-12-11: NetworkManager core daemon has moved to!

git clone git://

Networking that Just Works

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.  NetworkManager is intended to
replace default route, replace other routes, set IP addresses, and in general
configure networking as NM sees fit (with the possibility of manual override as
necessary).  In effect, the goal of NetworkManager is to make networking Just
Work with a minimum of user hassle, but still allow customization and a high
level of manual network control.  If you have special needs, we'd like to hear
about them, but understand that NetworkManager is not intended for every

NetworkManager will attempt to keep every network device in the system up and
active, as long as the device is available for use (has a cable plugged in,
the killswitch isn't turned on, etc).  Network connections can be set to
'autoconnect', meaning that NetworkManager will make that connection active
whenever it and the hardware is available.

"Settings services" store lists of user- or administrator-defined "connections",
which contain all the settings and parameters required to connect to a specific
network.  NetworkManager will _never_ activate a connection that is not in this
list, or that the user has not directed NetworkManager to connect to.

How it works:

The NetworkManager daemon runs as a privileged service (since it must access
and control hardware), but provides a D-Bus interface on the system bus to
allow for fine-grained control of networking.  NetworkManager does not store
connections or settings, it is only the mechanism by which those connections
are selected and activated.

To store pre-defined network connections, two separate services, the "system
settings service" and the "user settings service" store connection information
and provide these to NetworkManager, also via D-Bus.  Each settings service
can determine how and where it persistently stores the connection information;
for example, the GNOME applet stores its configuration in GConf, and the system
settings service stores it's config in distro-specific formats, or in a distro-
agnostic format, depending on user/administrator preference.

A variety of other system services are used by NetworkManager to provide
network functionality: wpa_supplicant for wireless connections and 802.1x
wired connections, pppd for PPP and mobile broadband connections, DHCP clients
for dynamic IP addressing, dnsmasq for proxy nameserver and DHCP server
functionality for internet connection sharing, and avahi-autoipd for IPv4
link-local addresses.  Most communication with these daemons occurs, again,
via D-Bus.

Why doesn't my network Just Work?

Driver problems are the #1 cause of why NetworkManager sometimes fails to
connect to wireless networks.  Often, the driver simply doesn't behave in a
consistent manner, or is just plain buggy.  NetworkManager supports _only_
those drivers that are shipped with the upstream Linux kernel, because only
those drivers can be easily fixed and debugged.  ndiswrapper, vendor binary
drivers, or other out-of-tree drivers may or may not work well with
NetworkManager, precisely because they have not been vetted and improved by the
open-source community, and because problems in these drivers usually cannot
be fixed.

Sometimes, command-line tools like 'iwconfig' will work, but NetworkManager will
fail.  This is again often due to buggy drivers, because these drivers simply
aren't expecting the dynamic requests that NetworkManager and wpa_supplicant
make.  Driver bugs should be filed in the bug tracker of the distribution being
run, since often distributions customize their kernel and drivers.

Sometimes, it really is NetworkManager's fault.  If you think that's the case,
please file a bug at and choose the NetworkManager
component.  Attaching the output of /var/log/messages or /var/log/daemon.log
(wherever your distribution directs syslog's 'daemon' facility output) is often
very helpful, and (if you can get) a working wpa_supplicant config file helps