|
Packit Service |
b23acc |
******************
|
|
Packit Service |
b23acc |
NetworkManager core daemon has moved to gitlab.freedesktop.org!
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
git clone https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
|
|
Packit Service |
b23acc |
******************
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Networking that Just Works
|
|
Packit Service |
b23acc |
--------------------------
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
NetworkManager attempts to keep an active network connection available at all
|
|
Packit Service |
b23acc |
times. The point of NetworkManager is to make networking configuration and
|
|
Packit Service |
b23acc |
setup as painless and automatic as possible. NetworkManager is intended to
|
|
Packit Service |
b23acc |
replace default route, replace other routes, set IP addresses, and in general
|
|
Packit Service |
b23acc |
configure networking as NM sees fit (with the possibility of manual override as
|
|
Packit Service |
b23acc |
necessary). In effect, the goal of NetworkManager is to make networking Just
|
|
Packit Service |
b23acc |
Work with a minimum of user hassle, but still allow customization and a high
|
|
Packit Service |
b23acc |
level of manual network control. If you have special needs, we'd like to hear
|
|
Packit Service |
b23acc |
about them, but understand that NetworkManager is not intended for every
|
|
Packit Service |
b23acc |
use-case.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
NetworkManager will attempt to keep every network device in the system up and
|
|
Packit Service |
b23acc |
active, as long as the device is available for use (has a cable plugged in,
|
|
Packit Service |
b23acc |
the killswitch isn't turned on, etc). Network connections can be set to
|
|
Packit Service |
b23acc |
'autoconnect', meaning that NetworkManager will make that connection active
|
|
Packit Service |
b23acc |
whenever it and the hardware is available.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
"Settings services" store lists of user- or administrator-defined "connections",
|
|
Packit Service |
b23acc |
which contain all the settings and parameters required to connect to a specific
|
|
Packit Service |
b23acc |
network. NetworkManager will _never_ activate a connection that is not in this
|
|
Packit Service |
b23acc |
list, or that the user has not directed NetworkManager to connect to.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
How it works:
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
The NetworkManager daemon runs as a privileged service (since it must access
|
|
Packit Service |
b23acc |
and control hardware), but provides a D-Bus interface on the system bus to
|
|
Packit Service |
b23acc |
allow for fine-grained control of networking. NetworkManager does not store
|
|
Packit Service |
b23acc |
connections or settings, it is only the mechanism by which those connections
|
|
Packit Service |
b23acc |
are selected and activated.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
To store pre-defined network connections, two separate services, the "system
|
|
Packit Service |
b23acc |
settings service" and the "user settings service" store connection information
|
|
Packit Service |
b23acc |
and provide these to NetworkManager, also via D-Bus. Each settings service
|
|
Packit Service |
b23acc |
can determine how and where it persistently stores the connection information;
|
|
Packit Service |
b23acc |
for example, the GNOME applet stores its configuration in GConf, and the system
|
|
Packit Service |
b23acc |
settings service stores its config in distro-specific formats, or in a distro-
|
|
Packit Service |
b23acc |
agnostic format, depending on user/administrator preference.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
A variety of other system services are used by NetworkManager to provide
|
|
Packit Service |
b23acc |
network functionality: wpa_supplicant for wireless connections and 802.1x
|
|
Packit Service |
b23acc |
wired connections, pppd for PPP and mobile broadband connections, DHCP clients
|
|
Packit Service |
b23acc |
for dynamic IP addressing, dnsmasq for proxy nameserver and DHCP server
|
|
Packit Service |
b23acc |
functionality for internet connection sharing, and avahi-autoipd for IPv4
|
|
Packit Service |
b23acc |
link-local addresses. Most communication with these daemons occurs, again,
|
|
Packit Service |
b23acc |
via D-Bus.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Why doesn't my network Just Work?
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Driver problems are the #1 cause of why NetworkManager sometimes fails to
|
|
Packit Service |
b23acc |
connect to wireless networks. Often, the driver simply doesn't behave in a
|
|
Packit Service |
b23acc |
consistent manner, or is just plain buggy. NetworkManager supports _only_
|
|
Packit Service |
b23acc |
those drivers that are shipped with the upstream Linux kernel, because only
|
|
Packit Service |
b23acc |
those drivers can be easily fixed and debugged. ndiswrapper, vendor binary
|
|
Packit Service |
b23acc |
drivers, or other out-of-tree drivers may or may not work well with
|
|
Packit Service |
b23acc |
NetworkManager, precisely because they have not been vetted and improved by the
|
|
Packit Service |
b23acc |
open-source community, and because problems in these drivers usually cannot
|
|
Packit Service |
b23acc |
be fixed.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Sometimes, command-line tools like 'iwconfig' will work, but NetworkManager will
|
|
Packit Service |
b23acc |
fail. This is again often due to buggy drivers, because these drivers simply
|
|
Packit Service |
b23acc |
aren't expecting the dynamic requests that NetworkManager and wpa_supplicant
|
|
Packit Service |
b23acc |
make. Driver bugs should be filed in the bug tracker of the distribution being
|
|
Packit Service |
b23acc |
run, since often distributions customize their kernel and drivers.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Sometimes, it really is NetworkManager's fault. If you think that's
|
|
Packit Service |
b23acc |
the case, please file a bug at:
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Attaching NetworkManager debug logs from the journal (or wherever your
|
|
Packit Service |
b23acc |
distribution directs syslog's 'daemon' facility output, as
|
|
Packit Service |
b23acc |
/var/log/messages or /var/log/daemon.log) is often very helpful, and
|
|
Packit Service |
b23acc |
(if you can get) a working wpa_supplicant config file helps
|
|
Packit Service |
b23acc |
enormously. See the logging section of file
|
|
Packit Service |
b23acc |
contrib/fedora/rpm/NetworkManager.conf for how to enable debug logging
|
|
Packit Service |
b23acc |
in NetworkManager.
|