networkmanager配置文件_conf文件可以删除吗

大家好，又见面了，我是你们的朋友全栈君。如果您正在找激活码,请点击查看最新教程,关注关注公众号 “全栈程序员社区” 获取激活教程,可能之前旧版本教程已经失效.最新Idea2022.1教程亲测有效,一键激活。

Jetbrains全系列IDE稳定放心使用

Name

NetworkManager.conf – NetworkManager configuration file

Synopsis

/etc/NetworkManager/NetworkManager.conf

or


<SYSCONFDIR>/NetworkManager/NetworkManager.conf

where <SYSCONFDIR> depends on your distribution or build.

Description

NetworkManager.conf is a configuration file for NetworkManager. It is used to set up various aspects of NetworkManager’s behavior. The location ofthe file may be changed through use of the “–config=” argument for NetworkManager (8).

File Format

The configuration file format is so-called key file (sort of ini-style format). It consists of sections (groups) of key-value pairs. Lines beginning with a’#’ and blank lines are considered comments. Sections are started by a header line containing the section enclosed in ‘[‘ and ‘]’, and ended implicitly by thestart of the next section or the end of the file. Each key-value pair must be contained in a section.
Minimal system settings configuration file looks like this:

[main]
plugins=keyfile

Description of sections and available keys follows:

[main]

This section is the only mandatory section of the configuration file.

plugins=plugin1,plugin2, …

List plugin names separated by ‘,’. Plugins are used to read/write system-wide connection. When more plugins are specified, the connections are read fromall listed plugins. When writing connections, the plugins will be asked to save the connection in the order listed here. If the first plugin cannot write outthat connection type, or can’t write out any connections, the next plugin is tried. If none of the plugins can save the connection, the error is returned tothe user.

Available plugins:

keyfile

plugin is the generic plugin that supports all the connection types and capabilities that NetworkManager has. It writes files out in a .ini-style format in/etc/NetworkManager/system-connections. For security, it will ignore files that are readable or writeable by any user or group other than
root sinceprivate keys and passphrases may be stored in plaintext inside the file.

ifcfg-rh

plugin is used on the Fedora and Red Hat Enterprise Linux distributions to read and write configuration from the standard/etc/sysconfig/network-scripts/ifcfg-* files. It currently supports reading wired, WiFi, and 802.1x connections, but does not yet support reading or writingmobile broadband, PPPoE, or VPN connections. To allow reading and writing of these add
keyfile plugin to your configuration as well.

ifupdown

plugin is used on the Debian and Ubuntu distributions, and reads connections from /etc/network/interfaces. Since it cannot write connections out (thatsupport isn’t planned), it is usually paired with the
keyfile plugin to enable saving and editing of new connections. The
ifupdown pluginsupports basic wired and WiFi connections, including WPA-PSK.

ifcfg-suse

plugin is only provided for simple backward compatibility with SUSE and OpenSUSE configuration. Most setups should be using the
keyfile plugininstead. The
ifcfg-suse plugin supports reading wired and WiFi connections, but does not support saving any connection types.

dhcp=dhclient | dhcpcd

This key sets up what DHCP client NetworkManager will use. Presently
dhclient and
dhcpcd are supported. The client configured here should beavailable on your system too. If this key is missing, available DHCP clients are looked for in this order: dhclient, dhcpcd.

no-auto-default=<hwaddr>,<hwaddr>,…

Set devices for which NetworkManager shouldn’t create default wired connection (Auto eth0). NetworkManager creates a default wired connection for any wireddevice that is managed and doesn’t have a connection configured. List a device in this option to inhibit creating the default connection for the device.

When the default wired connection is deleted or saved to a new persistent connection by a plugin, the MAC address of the wired device is automatically added tothis list to prevent creating the default connection for that device again. Devices are specified by their MAC addresses, in lowercase. Multiple entries areseparated by commas.

Example:

no-auto-default=00:22:68:5c:5d:c4,00:1e:65:ff:aa:ee

wifi-wext-only=false | true

This option controls NetworkManager’s interaction with
wpa_supplicant (8). When
false (default), ‘nl80211’ supplicant driver andbackground scanning are used. This enables seamless connection and roaming in RSA token-enabled Wi-Fi networks. If you encounter any problems with ‘nl80211′(e.g. due to bad drivers), you can switch back to ‘wext’ supplicant driver by setting this option to true. Missing option or an unrecognizedvalue is regarded as
false.

[keyfile]

This section contains keyfile-specific options and thus only has effect when using
keyfile plugin.

hostname=<hostname>

Set a persistent hostname when using the
keyfile plugin.

unmanaged-devices=mac:<hwaddr>;mac:<hwaddr>;…

Set devices that should be ignored by NetworkManager when using the
keyfile plugin. Devices are specified in the following format:”mac:<hwaddr>”, where <hwaddr> is MAC address of the device to be ignored, in lowercase. Multiple entries are separated by a semicolon.Example:

unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1e:65:30:d1:c4

[ifupdown]

This section contains ifupdown-specific options and thus only has effect when using
ifupdown plugin.

managed=false | true

Controls whether interfaces listed in the ‘interfaces’ file are managed by NetworkManager. If set to
true, then interfaces listed in/etc/network/interfaces are managed by NetworkManager. If set to
false, then any interface listed in /etc/network/interfaces will be ignored byNetworkManager. Remember that NetworkManager controls the default route, so because the interface is ignored, NetworkManager may assign the default route tosome other interface. When the option is missing,
false value is taken as default.

[logging]

This section controls NetworkManager’s logging. Any settings here are overridden by the–log-level and –log-domains command-line options.

level=<level>

One of [ERR, WARN, INFO, DEBUG]. The ERR level logs only critical errors. WARN logs warnings that may reflect operation. INFO logs various informationalmessages that are useful for tracking state and operations. DEBUG enables verbose logging for debugging purposes. Subsequent levels also log all messages fromearlier levels; thus setting the log level to INFO also logs error and warning messages.

domains=<domain1>,<domain2>, …

The following log domains are available: [NONE, HW, RFKILL, ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING,SUPPLICANT, USER_SET, SYS_SET, SUSPEND, CORE, DEVICE, OLPC]. When “NONE” is given by itself, logging is disabled. MB = Mobile Broadband, USER_SET = usersettings operations and communication, SYS_SET = system settings service operations, OLPC = OLPC Mesh device operations, CORE = core daemon operations, DEVICE= activation and general interface operations.

See Also

http://live.gnome.org/NetworkManager/SystemSettings

networkmanager(8), nm-tool(1), nmcli(1).

Referenced By

nm-system-settings.conf(5)

转载自：https://linux.die.net/man/5/networkmanager.conf