|
 |
9faaa1 |
# Configuration file for NetworkManager.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# See "man 5 NetworkManager.conf" for details.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# The directories /usr/lib/NetworkManager/conf.d/ and /run/NetworkManager/conf.d/
|
|
|
9faaa1 |
# can contain additional .conf snippets installed by packages. These files are
|
|
|
9faaa1 |
# read before NetworkManager.conf and have thus lowest priority.
|
|
|
9faaa1 |
# The directory /etc/NetworkManager/conf.d/ can contain additional .conf
|
|
|
9faaa1 |
# snippets. Those snippets are merged last and overwrite the settings from this main
|
|
|
9faaa1 |
# file.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# The files within one conf.d/ directory are read in asciibetical order.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# You can prevent loading a file /usr/lib/NetworkManager/conf.d/NAME.conf
|
|
|
9faaa1 |
# by having a file NAME.conf in either /run/NetworkManager/conf.d/ or /etc/NetworkManager/conf.d/.
|
|
|
9faaa1 |
# Likewise, snippets from /run can be prevented from loading by placing
|
|
|
9faaa1 |
# a file with the same name in /etc/NetworkManager/conf.d/.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# If two files define the same key, the one that is read afterwards will overwrite
|
|
|
9faaa1 |
# the previous one.
|
|
|
9faaa1 |
|
|
|
9faaa1 |
[main]
|
|
|
9faaa1 |
#plugins=keyfile,ifcfg-rh
|
|
|
9faaa1 |
|
|
|
9faaa1 |
|
|
|
9faaa1 |
[logging]
|
|
|
9faaa1 |
# When debugging NetworkManager, enabling debug logging is of great help.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# Logfiles contain no passwords and little sensitive information. But please
|
|
|
9faaa1 |
# check before posting the file online. You can also personally hand over the
|
|
|
9faaa1 |
# logfile to a NM developer to treat it confidential. Meet us on #nm on Libera.Chat.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# You can also change the log-level at runtime via
|
|
|
9faaa1 |
# $ nmcli general logging level TRACE domains ALL
|
|
|
9faaa1 |
# However, usually it's cleaner to enable debug logging
|
|
|
9faaa1 |
# in the configuration and restart NetworkManager so that
|
|
|
9faaa1 |
# debug logging is enabled from the start.
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# You will find the logfiles in syslog, for example via
|
|
|
9faaa1 |
# $ journalctl -u NetworkManager
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# Please post full logfiles for bug reports without pre-filtering or truncation.
|
|
|
9faaa1 |
# Also, for debugging the entire `journalctl` output can be interesting. Don't
|
|
|
9faaa1 |
# limit unnecessarily with `journalctl -u`. Exceptions are if you are worried
|
|
|
9faaa1 |
# about private data. Check before posting logfiles!
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
# Note that debug logging of NetworkManager can be quite verbose. Some messages
|
|
|
9faaa1 |
# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
|
|
|
9faaa1 |
# in man journald.conf). Please disable rate-limiting before collecting debug logs!
|
|
|
9faaa1 |
#
|
|
|
9faaa1 |
#level=TRACE
|
|
|
9faaa1 |
#domains=ALL
|