|
 |
a31528 |
# Configuration file for NetworkManager.
|
|
|
a31528 |
#
|
|
|
a31528 |
# See "man 5 NetworkManager.conf" for details.
|
|
|
a31528 |
#
|
|
|
a31528 |
# The directories /usr/lib/NetworkManager/conf.d/ and /var/run/NetworkManager/conf.d/
|
|
|
a31528 |
# can contain additional configuration snippets installed by packages. These files are
|
|
|
a31528 |
# read before NetworkManager.conf and have thus lowest priority.
|
|
|
a31528 |
# The directory /etc/NetworkManager/conf.d/ can contain additional configuration
|
|
|
a31528 |
# snippets. Those snippets are merged last and overwrite the settings from this main
|
|
|
a31528 |
# file.
|
|
|
a31528 |
#
|
|
|
a31528 |
# The files within one conf.d/ directory are read in asciibetical order.
|
|
|
a31528 |
#
|
|
|
a31528 |
# If /etc/NetworkManager/conf.d/ contains a file with the same name as
|
|
|
a31528 |
# /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored.
|
|
|
a31528 |
# Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can
|
|
|
a31528 |
# put an empty file to /etc with the same name. The same applies with respect
|
|
|
a31528 |
# to the directory /var/run/NetworkManager/conf.d where files in /var/run shadow
|
|
|
a31528 |
# /usr/lib and are themselves shadowed by files under /etc.
|
|
|
a31528 |
#
|
|
|
a31528 |
# If two files define the same key, the one that is read afterwards will overwrite
|
|
|
a31528 |
# the previous one.
|
|
|
a31528 |
|
|
|
a31528 |
[main]
|
|
|
a31528 |
#plugins=ifcfg-rh,ibft
|
|
|
a31528 |
|
|
|
a31528 |
|
|
|
a31528 |
[logging]
|
|
|
a31528 |
# When debugging NetworkManager, enabling debug logging is of great help.
|
|
|
a31528 |
#
|
|
|
a31528 |
# Logfiles contain no passwords and little sensitive information. But please
|
|
|
a31528 |
# check before posting the file online. You can also personally hand over the
|
|
|
a31528 |
# logfile to a NM developer to treat it confidential. Meet us on #nm on freenode.
|
|
|
a31528 |
# Please post full logfiles except minimal modifications of private data.
|
|
|
a31528 |
#
|
|
|
a31528 |
# You can also change the log-level at runtime via
|
|
|
a31528 |
# $ nmcli general logging level TRACE domains ALL
|
|
|
a31528 |
# However, usually it's cleaner to enable debug logging
|
|
|
a31528 |
# in the configuration and restart NetworkManager so that
|
|
|
a31528 |
# debug logging is enabled from the start.
|
|
|
a31528 |
#
|
|
|
a31528 |
# You will find the logfiles in syslog, for example via
|
|
|
a31528 |
# $ journalctl -u NetworkManager
|
|
|
a31528 |
#
|
|
|
a31528 |
# Note that debug logging of NetworkManager can be quite verbose. Some messages
|
|
|
a31528 |
# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
|
|
|
a31528 |
# in man journald.conf).
|
|
|
a31528 |
#
|
|
|
a31528 |
#level=TRACE
|
|
|
a31528 |
#domains=ALL
|