{"id":4472,"date":"2022-12-20T18:08:44","date_gmt":"2022-12-20T21:08:44","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/nmsettingsifcfgrh-man5\/"},"modified":"2022-12-20T18:08:44","modified_gmt":"2022-12-20T21:08:44","slug":"nmsettingsifcfgrh-man5","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/nmsettingsifcfgrh-man5\/","title":{"rendered":"NM−SETTINGS−IFCFG−RH (man5)"},"content":{"rendered":"

NM\u2212SETTINGS\u2212IFCFG\u2212RH<\/h1>\n

NAME<\/a>
DESCRIPTION<\/a>
FILE FORMAT<\/a>
DIFFERENCES AGAINST INITSCRIPTS<\/a>
DETAILS<\/a>
FILES<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

nm-settings-ifcfg-rh \u2212 Description of ifcfg\u2212rh<\/i> settings plugin<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

NetworkManager is based on the concept of connection profiles that contain network configuration (see nm-settings<\/b>(5) for details). The profiles can be stored in various formats. NetworkManager uses plugins for reading and writing the data. The plugins can be configured in NetworkManager.conf<\/b>(5).<\/p>\n

The ifcfg\u2212rh<\/i> plugin is used on the Fedora and Red Hat Enterprise Linux distributions to read\/write configuration from\/to the traditional \/etc\/sysconfig\/network\u2212scripts\/ifcfg\u2212* files. Each NetworkManager connection maps to one ifcfg\u2212* file, with possible usage of keys\u2212* for passwords, route\u2212* for static IPv4 routes and route6\u2212* for static IPv6 routes. The plugin currently supports reading and writing Ethernet, Wi\u2212Fi, InfiniBand, VLAN, Bond, Bridge, and Team connections. Unsupported connection types (such as WWAN, PPPoE, VPN, or ADSL) are handled by keyfile<\/i> plugin (nm-settings-keyfile<\/b>(5)). The main reason for using ifcfg\u2212rh<\/i> plugin is the compatibility with legacy configurations for ifup<\/i> and ifdown<\/i> (initscripts).<\/p>\n

FILE FORMAT <\/a> <\/h2>\n

The ifcfg\u2212rh<\/i> config format is a simple text file containing VARIABLE=”value” lines. The format is described in sysconfig.txt of initscripts<\/i> package. Note that the configuration files may be sourced by initscripts<\/i>, so they must be valid shell scripts. That means, for instance, that # character can be used for comments, strings with spaces must be quoted, special characters must be escaped, etc.<\/p>\n

Users can create or modify the ifcfg\u2212rh<\/i> connection files manually, even if that is not the recommended way of managing the profiles. However, if they choose to do that, they must inform NetworkManager about their changes (for example via nmcli con (re)load<\/i>).<\/p>\n

Some ifcfg-rh configuration examples:<\/b>.<\/p>\n

Simple DHCP ethernet configuration:<\/b>
NAME=ethernet
UUID=1c4ddf70\u221201bf\u221246d6\u2212b04f\u221247e842bd98da
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
ONBOOT=yes<\/p>\n

Simple ethernet configuration with static IP:<\/b>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.1.0.25
PREFIX=24
GATEWAY=10.1.0.1
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=ethernet\u2212em2
UUID=51bb3904\u2212c0fc\u22124dfe\u221283b2\u22120a71e7928c13
DEVICE=em2
ONBOOT=yes<\/p>\n

WPA2 Enterprise WLAN (TTLS with inner MSCHAPV2 authentication):<\/b>
ESSID=”CompanyWLAN”
MODE=Managed
KEY_MGMT=WPA\u2212EAP
TYPE=Wireless
IEEE_8021X_EAP_METHODS=TTLS
IEEE_8021X_IDENTITY=joe
IEEE_8021X_PASSWORD_FLAGS=ask
IEEE_8021X_INNER_AUTH_METHODS=MSCHAPV2
IEEE_8021X_CA_CERT=\/home\/joe\/.cert\/company.crt
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME=MyCompany
UUID=f79848ff\u221211a6\u22124810\u22129e1a\u221299039dea84c4
ONBOOT=yes<\/p>\n

Bridge and bridge port configuration:<\/b>
ifcfg\u2212bridge: ifcfg\u2212bridge\u2212port:
NAME=bridge NAME=bridge007\u2212port\u2212eth0
UUID=4be99ce0\u2212c5b2\u22124764\u22128b77\u2212ec226e440125 UUID=3ad56c4a\u221247e1\u2212419b\u2212b0d4\u22128ad86eb967a3
DEVICE=bridge007 DEVICE=eth0
STP=yes ONBOOT=yes
TYPE=Bridge TYPE=Ethernet
BRIDGING_OPTS=priority=32768 BRIDGE=bridge007
ONBOOT=yes
BOOTPROTO=dhcp<\/p>\n

Bonding configuration:<\/b>
ifcfg\u2212BOND: ifcfg\u2212BOND\u2212slave:
NAME=BOND NAME=BOND\u2212slave
UUID=b41888aa\u2212924c\u2212450c\u2212b0f8\u221285a4f0a51b4a UUID=9bb048e4\u2212286a\u22124cc3\u2212b104\u2212007dbd20decb
DEVICE=bond100 DEVICE=eth0
BONDING_OPTS=”mode=balance\u2212rr miimon=100″ ONBOOT=yes
TYPE=Bond TYPE=Ethernet
BONDING_MASTER=yes MASTER=bond100
ONBOOT=yes SLAVE=yes
BOOTPROTO=dhcp<\/p>\n

Team and team port configuration:<\/b>
ifcfg\u2212my_team0:
DEVICE=team0
TEAM_CONFIG=”{ “device”: “team0”, “runner”: {“name”: “roundrobin”}, “ports”: {“eth1”: {}, “eth2″: {}} }”
DEVICETYPE=Team
BOOTPROTO=dhcp
NAME=team0\u2212profile
UUID=1d3460a0\u22127b37\u2212457f\u2212a300\u2212fe8d92da4807
ONBOOT=yes<\/p>\n

ifcfg\u2212my_team0_slave1:
NAME=team0\u2212slave1
UUID=d5aed298\u2212c567\u22124cc1\u2212b808\u22126d38ecef9e64
DEVICE=eth1
ONBOOT=yes
TEAM_MASTER=team0
DEVICETYPE=TeamPort<\/p>\n

ifcfg\u2212my_team0_slave2:
NAME=team0\u2212slave2
UUID=94e75f4e\u2212e5ad\u2212401c\u22128962\u221231e0ae5d2215
DEVICE=eth2
ONBOOT=yes
TEAM_MASTER=team0
DEVICETYPE=TeamPort<\/p>\n

The UUID values in the config files must be unique. You can use uuidgen<\/i> command line tool to generate such values. Alternatively, you can leave out UUID entirely. In that case NetworkManager will generate a UUID based on the file name.<\/p>\n

DIFFERENCES AGAINST INITSCRIPTS <\/a> <\/h2>\n

The main differences of NetworkManager ifcfg\u2212rh plugin and traditional initscripts are:<\/p>\n

NM_CONTROLLED=yes|no<\/b><\/p>\n

NM_CONTROLLED is NetworkManager\u2212specific variable used by NetworkManager for determining whether the device of the ifcfg<\/i> file should be managed. NM_CONTROLLED=yes is supposed if the variable is not present in the file. Note that if you have more ifcfg<\/i> files for a single device, NM_CONTROLLED=no in one of the files will cause the device not to be managed. The profile may not even be the active one.<\/p>\n

New variables<\/b><\/p>\n

NetworkManager has introduced some new variable, not present in initscripts, to be able to store data for its new features. The variables are marked as extensions in the tables below.<\/p>\n

Semantic change of variables<\/b><\/p>\n

NetworkManager had to slightly change the semantic for a few variables.<\/p>\n

\u2022 PEERDNS \u2212 initscripts interpret PEERDNS=no to mean “never touch resolv.conf”. NetworkManager interprets it to say “never add automatic (DHCP, PPP, VPN, etc.) nameservers to resolv.conf”.<\/p>\n

\u2022 ONBOOT \u2212 initscripts use ONBOOT=yes to mark the devices that are to be activated during boot. NetworkManager extends this to also mean that this profile can be used for auto\u2212connecting at any time.<\/p>\n

\u2022 BOOTPROTO \u2212 NetworkManager supports traditional values none<\/i> (static), dhcp<\/i>. But it also allows additional values to enable new addressing methods. They are autoip<\/i> for IPv4 link\u2212local addressing using Avahi daemon and shared<\/i> for connection sharing. When shared<\/i> is used, NetworkManager assigns the interface 10.42.0.1, or it uses the first static address, if configured.<\/p>\n

\u2022 HWADDR \u2212 initscripts compare the currently set hardware address of a device, while NetworkManager considers the permanent one.<\/p>\n

See the next section for detailed mapping of NetworkManager properties and ifcfg\u2212rh<\/i> variables. Variable names, format and usage differences in NetworkManager and initscripts are documented in the tables below.<\/p>\n

DETAILS <\/a> <\/h2>\n

ifcfg\u2212rh<\/i> plugin variables marked with (+)<\/i> are NetworkManager specific extensions not understood by traditional initscripts.<\/p>\n

Table\u00a01.\u00a06lowpan setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a02.\u00a0802\u22121x setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a03.\u00a0bond setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a04.\u00a0bridge\u2212port setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a05.\u00a0bridge setting
\u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a06.\u00a0connection setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a07.\u00a0dcb setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

All DCB related configuration is a NetworkManager extension. DCB=yes must be used explicitly to enable DCB so that the rest of the DCB_* variables can apply.<\/p>\n

Table\u00a08.\u00a0ethtool setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a09.\u00a0infiniband setting
\u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a010.\u00a0ipv4 setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a011.\u00a0ipv6 setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a012.\u00a0match setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a013.\u00a0ovs\u2212bridge setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a014.\u00a0ovs\u2212interface setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a015.\u00a0ovs\u2212dpdk setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a016.\u00a0ovs\u2212patch setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a017.\u00a0ovs\u2212port setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a018.\u00a0proxy setting
\u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a019.\u00a0sriov setting
\u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a020.\u00a0tc setting
\u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a021.\u00a0team\u2212port setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a022.\u00a0team setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a023.\u00a0user setting
\u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a024.\u00a0vlan setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a025.\u00a0vrf setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a026.\u00a0wifi\u2212p2p setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a027.\u00a0802\u22123\u2212ethernet setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a028.\u00a0wireguard setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a029.\u00a0802\u221211\u2212wireless\u2212security setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a030.\u00a0802\u221211\u2212wireless setting
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/b><\/p>\n

\"Image<\/b><\/p>\n

Table\u00a031.\u00a0wpan setting<\/b><\/p>\n

\"Image<\/b><\/p>\n

The following settings are not supported by ifcfg\u2212rh<\/i> plugin:<\/p>\n

802\u221211\u2212olpc\u2212mesh, adsl, bluetooth, cdma, dummy, generic, gsm, ip\u2212tunnel, macsec, macvlan, ppp, pppoe, serial, tun, vpn, vxlan, wimax<\/p>\n

Secret flags<\/b>
Each secret property in a NetworkManager setting has an associated flags<\/i> property that describes how to handle that secret. In the fcfg\u2212rh<\/i> plugin variables for secret flags have a _FLAGS<\/i> suffix. The variables contain one or more of the following values (space separated). Missing (or empty) *_FLAGS variable means that the password is owned by NetworkManager.<\/p>\n

\u2022 user \u2212 a user\u2212session secret agent is responsible for providing and storing this secret; when it is required, agents will be asked to provide it.<\/p>\n

\u2022 ask \u2212 the associated password is not saved but it will be requested from the user each time it is required.<\/p>\n

\u2022 unused \u2212 in some situations it cannot be automatically determined that a secret is required or not. This flag hints that the secret is not required and should not be requested from the user.<\/p>\n

FILES <\/a> <\/h2>\n

\/etc\/sysconfig\/network\u2212scripts\/ifcfg\u2212*<\/p>\n

\/etc\/sysconfig\/network\u2212scripts\/keys\u2212*<\/p>\n

\/etc\/sysconfig\/network\u2212scripts\/route\u2212*<\/p>\n

\/etc\/sysconfig\/network\u2212scripts\/route6\u2212*<\/p>\n

\/usr\/share\/doc\/initscripts\/sysconfig.txt<\/p>\n

SEE ALSO <\/a> <\/h2>\n

nm-settings<\/b>(5), nm-settings-keyfile<\/b>(5), NetworkManager<\/b>(8), NetworkManager.conf<\/b>(5), nmcli<\/b>(1), nmcli-examples<\/b>(7)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

nm-settings-ifcfg-rh \u2212 Description of ifcfg\u2212rh settings plugin <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1291,1447],"class_list":["post-4472","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-man5","tag-nm-settings-ifcfg-rh"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4472","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4472"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4472\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4472"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4472"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}