diff options
Diffstat (limited to 'docs/api/html/nm-settings-ifcfg-rh.html')
| -rw-r--r-- | docs/api/html/nm-settings-ifcfg-rh.html | 1876 |
1 files changed, 1876 insertions, 0 deletions
diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html new file mode 100644 index 00000000..7a92c0f9 --- /dev/null +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -0,0 +1,1876 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>nm-settings-ifcfg-rh: NetworkManager D-Bus API Reference Manual</title> +<meta name="generator" content="DocBook XSL Stylesheets V1.78.1"> +<link rel="home" href="index.html" title="NetworkManager D-Bus API Reference Manual"> +<link rel="up" href="manpages.html" title="UNIX Manual Pages"> +<link rel="prev" href="nm-settings-keyfile.html" title="nm-settings-keyfile"> +<link rel="next" href="ix01.html" title="Index"> +<meta name="generator" content="GTK-Doc V1.24 (XML mode)"> +<link rel="stylesheet" href="style.css" type="text/css"> +</head> +<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> +<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle"> +<td width="100%" align="left" class="shortcuts"></td> +<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> +<td><a accesskey="u" href="manpages.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> +<td><a accesskey="p" href="nm-settings-keyfile.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="n" href="ix01.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +</tr></table> +<div class="refentry"> +<a name="nm-settings-ifcfg-rh"></a><div class="titlepage"></div> +<div class="refnamediv"><table width="100%"><tr> +<td valign="top"> +<h2><span class="refentrytitle">nm-settings-ifcfg-rh</span></h2> +<p>nm-settings-ifcfg-rh — Description of <span class="emphasis"><em>ifcfg-rh</em></span> settings plugin</p> +</td> +<td class="gallery_image" valign="top" align="right"></td> +</tr></table></div> +<div class="refsect1"> +<a name="id-1.4.7.4"></a><h2>DESCRIPTION</h2> +<p> + NetworkManager is based on the concept of connection profiles that contain + network configuration (see <span class="citerefentry"><span class="refentrytitle">nm-settings</span>(5)</span> 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 <span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span>. + </p> +<p> + The <span class="emphasis"><em>ifcfg-rh</em></span> plugin is used on the Fedora and Red Hat + Enterprise Linux distributions to read/write configuration from/to + the traditional <code class="filename">/etc/sysconfig/network-scripts/ifcfg-*</code> files. + Each NetworkManager connection maps to one <code class="filename">ifcfg-*</code> file, with + possible usage of <code class="filename">keys-*</code> for passwords, <code class="filename">route-*</code> + for static IPv4 routes and <code class="filename">route6-*</code> for static IPv6 routes. + The plugin currently supports reading and writing Ethernet, Wi-Fi, InfiniBand, + VLAN, Bond, Bridge, and Team connections. Unsupported connection types (such as + WWAN, PPPoE, VPN, or ADSL) are handled by <span class="emphasis"><em>keyfile</em></span> plugin + (<span class="citerefentry"><span class="refentrytitle">nm-settings-keyfile</span>(5)</span>). + The main reason for using <span class="emphasis"><em>ifcfg-rh</em></span> plugin is the compatibility + with legacy configurations for <span class="emphasis"><em>ifup</em></span> and <span class="emphasis"><em>ifdown</em></span> + (initscripts). + </p> +</div> +<div class="refsect1"> +<a name="id-1.4.7.5"></a><h2>File Format</h2> +<p> + The <span class="emphasis"><em>ifcfg-rh</em></span> config format is a simple text file containing + VARIABLE="value" lines. The format is described in <code class="filename">sysconfig.txt</code> + of <span class="emphasis"><em>initscripts</em></span> package. Note that the configuration files + may be sourced by <span class="emphasis"><em>initscripts</em></span>, so they must be valid shell + scripts. That means, for instance, that <code class="literal">#</code> character can be used + for comments, strings with spaces must be quoted, special characters must be escaped, + etc. + </p> +<p> + Users can create or modify the <span class="emphasis"><em>ifcfg-rh</em></span> 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 (see <span class="emphasis"><em>monitor-connection-file</em></span> in + <span class="citerefentry"><span class="refentrytitle">nm-settings</span>(5)</span>, and <span class="emphasis"><em>nmcli con (re)load</em></span>). + </p> +<p><b>Some <span class="emphasis"><em>ifcfg-rh</em></span> configuration examples: </b></p> +<pre class="programlisting"><span class="bold"><strong>Simple DHCP ethernet configuration:</strong></span> +NAME=ethernet +UUID=1c4ddf70-01bf-46d6-b04f-47e842bd98da +TYPE=Ethernet +BOOTPROTO=dhcp +DEFROUTE=yes +PEERDNS=yes +PEERROUTES=yes +IPV4_FAILURE_FATAL=no +ONBOOT=yes + </pre> +<pre class="programlisting"><span class="bold"><strong>Simple ethernet configuration with static IP:</strong></span> +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-em2 +UUID=51bb3904-c0fc-4dfe-83b2-0a71e7928c13 +DEVICE=em2 +ONBOOT=yes + </pre> +<pre class="programlisting"><span class="bold"><strong>WPA2 Enterprise WLAN (TTLS with inner MSCHAPV2 authentication):</strong></span> +ESSID="CompanyWLAN" +MODE=Managed +KEY_MGMT=WPA-EAP +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-11a6-4810-9e1a-99039dea84c4 +ONBOOT=yes + </pre> +<pre class="programlisting"><span class="bold"><strong>Bridge and bridge port configuration:</strong></span> +ifcfg-bridge: ifcfg-bridge-port: +NAME=bridge NAME=bridge007-port-eth0 +UUID=4be99ce0-c5b2-4764-8b77-ec226e440125 UUID=3ad56c4a-47e1-419b-b0d4-8ad86eb967a3 +DEVICE=bridge007 DEVICE=eth0 +STP=yes ONBOOT=yes +TYPE=Bridge TYPE=Ethernet +BRIDGING_OPTS=priority=32768 BRIDGE=bridge007 +ONBOOT=yes +BOOTPROTO=dhcp + + </pre> +<pre class="programlisting"><span class="bold"><strong>Bonding configuration:</strong></span> +ifcfg-BOND: ifcfg-BOND-slave: +NAME=BOND NAME=BOND-slave +UUID=b41888aa-924c-450c-b0f8-85a4f0a51b4a UUID=9bb048e4-286a-4cc3-b104-007dbd20decb +DEVICE=bond100 DEVICE=eth0 +BONDING_OPTS="mode=balance-rr miimon=100" ONBOOT=yes +TYPE=Bond TYPE=Ethernet +BONDING_MASTER=yes MASTER=bond100 +ONBOOT=yes SLAVE=yes +BOOTPROTO=dhcp + + </pre> +<pre class="programlisting"><span class="bold"><strong>Team and team port configuration:</strong></span> +ifcfg-my_team0: +DEVICE=team0 +TEAM_CONFIG="{ \"device\": \"team0\", \"runner\": {\"name\": \"roundrobin\"}, \"ports\": {\"eth1\": {}, \"eth2\": {}} }" +DEVICETYPE=Team +BOOTPROTO=dhcp +NAME=team0-profile +UUID=1d3460a0-7b37-457f-a300-fe8d92da4807 +ONBOOT=yes + +ifcfg-my_team0_slave1: +NAME=team0-slave1 +UUID=d5aed298-c567-4cc1-b808-6d38ecef9e64 +DEVICE=eth1 +ONBOOT=yes +TEAM_MASTER=team0 +DEVICETYPE=TeamPort + +ifcfg-my_team0_slave2: +NAME=team0-slave2 +UUID=94e75f4e-e5ad-401c-8962-31e0ae5d2215 +DEVICE=eth2 +ONBOOT=yes +TEAM_MASTER=team0 +DEVICETYPE=TeamPort + </pre> +<p> + The UUID values in the config files must be unique. You can use <span class="emphasis"><em>uuidgen</em></span> + 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> +</div> +<div class="refsect1"> +<a name="id-1.4.7.6"></a><h2>Differences against initscripts</h2> +<p> + The main differences of NetworkManager ifcfg-rh plugin and traditional + initscripts are: + </p> +<div class="variablelist"><table border="0" class="variablelist"> +<colgroup> +<col align="left" valign="top"> +<col> +</colgroup> +<tbody> +<tr> +<td><p><span class="term"><span class="bold"><strong>NM_CONTROLLED=yes|no</strong></span></span></p></td> +<td><p> + NM_CONTROLLED is NetworkManager-specific variable used by NetworkManager + for determining whether the device of the <span class="emphasis"><em>ifcfg</em></span> file + should be managed. NM_CONTROLLED=yes is supposed if the variable is not + present in the file. + Note that if you have more <span class="emphasis"><em>ifcfg</em></span> 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></td> +</tr> +<tr> +<td><p><span class="term"><span class="bold"><strong>New variables</strong></span></span></p></td> +<td><p> + 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></td> +</tr> +<tr> +<td><p><span class="term"><span class="bold"><strong>Semantic change of variables</strong></span></span></p></td> +<td> +<p> + NetworkManager had to slightly change the semantic for a few variables. + </p> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> +<li class="listitem"><p><code class="literal">PEERDNS</code> - + 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></li> +<li class="listitem"><p><code class="literal">ONBOOT</code> - + initscripts use ONBOOT=yes to mark the devices that are to be activated + during boot. NetworkManager extents this to also mean that this profile + can be used for auto-connecting at any time.</p></li> +<li class="listitem"><p><code class="literal">BOOTPROTO</code> - + NetworkManager supports traditional values <span class="emphasis"><em>none</em></span> (static), + <span class="emphasis"><em>dhcp</em></span>. But it also allows additional values to + enable new addressing methods. They are <span class="emphasis"><em>autoip</em></span> for IPv4 + link-local addressing using Avahi daemon and <span class="emphasis"><em>shared</em></span> for + connection sharing. When <span class="emphasis"><em>shared</em></span> is used, NetworkManager + assigns the interface 10.42.0.1, or it uses the first static address, + if configured.</p></li> +</ul></div> +</td> +</tr> +</tbody> +</table></div> +<p> + See the next section for detailed mapping of NetworkManager properties and + <span class="emphasis"><em>ifcfg-rh</em></span> variables. Variable names, format and usage + differences in NetworkManager and initscripts are documented in the tables bellow. + </p> +</div> +<div class="refsect1"> +<a name="id-1.4.7.7"></a><h2>DETAILS</h2> +<p><span class="emphasis"><em>ifcfg-rh</em></span> plugin variables marked with <span class="emphasis"><em>(+)</em></span> + are NetworkManager specific extensions not understood by traditional initscripts. + </p> +<div class="table"> +<a name="id-1.4.7.7.3"></a><p class="title"><b>Table 69. 802-1x setting</b></p> +<div class="table-contents"><table summary="802-1x setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">eap</td> +<td align="left">IEEE_8021X_EAP_METHODS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">EAP method for 802.1X authentication.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_EAP_METHODS=PEAP<span class="bold"><strong> + +Allowed values: </strong></span>"LEAP", "PWD", "TLS", "PEAP", "TTLS", "FAST"</td> +</tr> +<tr> +<td align="left">identity</td> +<td align="left">IEEE_8021X_IDENTITY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Identity for EAP authentication methods.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_IDENTITY=itsme</td> +</tr> +<tr> +<td align="left">anonymous-identity</td> +<td align="left">IEEE_8021X_ANON_IDENTITY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Anonymous identity for EAP authentication methods.</td> +</tr> +<tr> +<td align="left">pac-file</td> +<td align="left">IEEE_8021X_PAC_FILE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">File with PAC (Protected Access Credential) for EAP-FAST.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_PAC_FILE=/home/joe/my-fast.pac</td> +</tr> +<tr> +<td align="left">ca-cert</td> +<td align="left">IEEE_8021X_CA_CERT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">CA certificate for EAP.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_CA_CERT=/home/joe/cacert.crt</td> +</tr> +<tr> +<td align="left">ca-path</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">subject-match</td> +<td align="left">IEEE_8021X_SUBJECT_MATCH<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Substring to match subject of server certificate against.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_SUBJECT_MATCH="Red Hat"</td> +</tr> +<tr> +<td align="left">altsubject-matches</td> +<td align="left">IEEE_8021X_ALTSUBJECT_MATCHES<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">List of strings to be matched against the altSubjectName.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_ALTSUBJECT_MATCHES="s1.domain.cc"</td> +</tr> +<tr> +<td align="left">domain-suffix-match</td> +<td align="left">IEEE_8021X_DOMAIN_SUFFIX_MATCH<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Suffix to match domain of server certificate against.</td> +</tr> +<tr> +<td align="left">client-cert</td> +<td align="left">IEEE_8021X_CLIENT_CERT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Client certificate for EAP.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_CLIENT_CERT=/home/joe/mycert.crt</td> +</tr> +<tr> +<td align="left">phase1-peapver</td> +<td align="left">IEEE_8021X_PEAP_VERSION<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Use to force a specific PEAP version.<span class="bold"><strong> + +Allowed values: </strong></span>0, 1</td> +</tr> +<tr> +<td align="left">phase1-peaplabel</td> +<td align="left">IEEE_8021X_PEAP_FORCE_NEW_LABEL<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Use to force the new PEAP label during key derivation.<span class="bold"><strong> + +Allowed values: </strong></span>yes, no</td> +</tr> +<tr> +<td align="left">phase1-fast-provisioning</td> +<td align="left">IEEE_8021X_FAST_PROVISIONING<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enable in-line provisioning of EAP-FAST credentials.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_FAST_PROVISIONING="allow-auth allow-unauth"<span class="bold"><strong> + +Allowed values: </strong></span>space-separated list of these values [allow-auth, allow-unauth]</td> +</tr> +<tr> +<td align="left">phase2-auth</td> +<td align="left">IEEE_8021X_INNER_AUTH_METHODS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Inner non-EAP authentication methods. IEEE_8021X_INNER_AUTH_METHODS can contain values both for 'phase2-auth' and 'phase2-autheap' properties.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_INNER_AUTH_METHODS=PAP<span class="bold"><strong> + +Allowed values: </strong></span>"PAP", "CHAP", "MSCHAP", "MSCHAPV2", "GTC", "OTP", "MD5" and "TLS"</td> +</tr> +<tr> +<td align="left">phase2-autheap</td> +<td align="left">IEEE_8021X_INNER_AUTH_METHODS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Inner EAP-based authentication methods. Note that IEEE_8021X_INNER_AUTH_METHODS is also used for 'phase2-auth' values.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_INNER_AUTH_METHODS="MSCHAPV2 EAP-TLS"<span class="bold"><strong> + +Allowed values: </strong></span>"EAP-MD5", "EAP-MSCHAPV2", "EAP-GTC", "EAP-OTP" and "EAP-TLS"</td> +</tr> +<tr> +<td align="left">phase2-subject-match</td> +<td align="left">IEEE_8021X_PHASE2_SUBJECT_MATCH<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Substring to match subject of server certificate against.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_PHASE2_SUBJECT_MATCH="Red Hat"</td> +</tr> +<tr> +<td align="left">phase2-altsubject-matches</td> +<td align="left">IEEE_8021X_PHASE2_ALTSUBJECT_MATCHES<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left"> </td> +</tr> +<tr> +<td align="left">phase2-domain-suffix-match</td> +<td align="left">IEEE_8021X_PHASE2_DOMAIN_SUFFIX_MATCH<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Suffix to match domain of server certificate for phase 2 against.</td> +</tr> +<tr> +<td align="left">phase2-client-cert</td> +<td align="left">IEEE_8021X_INNER_CLIENT_CERT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Client certificate for inner EAP method.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_INNER_CLIENT_CERT=/home/joe/mycert.crt</td> +</tr> +<tr> +<td align="left">password</td> +<td align="left">IEEE_8021X_PASSWORD<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">UTF-8 encoded password used for EAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> +</tr> +<tr> +<td align="left">password-flags</td> +<td align="left">IEEE_8021X_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for IEEE_8021X_PASSWORD password. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">password-raw</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">password-raw-flags</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">private-key</td> +<td align="left">IEEE_8021X_PRIVATE_KEY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Private key for EAP-TLS.<span class="bold"><strong> + +Example: </strong></span>IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12</td> +</tr> +<tr> +<td align="left">private-key-password</td> +<td align="left">IEEE_8021X_PRIVATE_KEY_PASSWORD<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password for IEEE_8021X_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> +</tr> +<tr> +<td align="left">private-key-password-flags</td> +<td align="left">IEEE_8021X_PRIVATE_KEY_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for IEEE_8021X_PRIVATE_KEY_PASSWORD password. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">phase2-private-key</td> +<td align="left">IEEE_8021X_INNER_PRIVATE_KEY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Private key for inner authentication method for EAP-TLS.</td> +</tr> +<tr> +<td align="left">phase2-private-key-password</td> +<td align="left">IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password for IEEE_8021X_INNER_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> +</tr> +<tr> +<td align="left">phase2-private-key-password-flags</td> +<td align="left">IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD password. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">pin</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">pin-flags</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">system-ca-certs</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not handled by ifcfg-rh plugin.</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.4"></a><p class="title"><b>Table 70. bond setting</b></p> +<div class="table-contents"><table summary="bond setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody><tr> +<td align="left">options</td> +<td align="left">BONDING_OPTS</td> +<td align="left"> </td> +<td align="left">Bonding options.<span class="bold"><strong> + +Example: </strong></span>BONDING_OPTS="miimon=100 mode=broadcast"</td> +</tr></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.5"></a><p class="title"><b>Table 71. bridge-port setting</b></p> +<div class="table-contents"><table summary="bridge-port setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">priority</td> +<td align="left">BRIDGING_OPTS: priority=</td> +<td align="left">32</td> +<td align="left">STP priority.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 63</td> +</tr> +<tr> +<td align="left">path-cost</td> +<td align="left">BRIDGING_OPTS: path_cost=</td> +<td align="left">100</td> +<td align="left">STP cost.<span class="bold"><strong> + +Allowed values: </strong></span>1 - 65535</td> +</tr> +<tr> +<td align="left">hairpin-mode</td> +<td align="left">BRIDGING_OPTS: hairpin_mode=</td> +<td align="left">yes</td> +<td align="left">Hairpin mode of the bridge port.</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.6"></a><p class="title"><b>Table 72. bridge setting</b></p> +<div class="table-contents"><table summary="bridge setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">mac-address</td> +<td align="left">MACADDR<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">MAC address of the bridge. Note that this requires a recent kernel support, originally introduced in 3.15 upstream kernel) MACADDR for bridges is an NM extension.</td> +</tr> +<tr> +<td align="left">stp</td> +<td align="left">STP</td> +<td align="left">no</td> +<td align="left">Span tree protocol participation.</td> +</tr> +<tr> +<td align="left">priority</td> +<td align="left">BRIDGING_OPTS: priority=</td> +<td align="left">32768</td> +<td align="left">STP priority.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 32768</td> +</tr> +<tr> +<td align="left">forward-delay</td> +<td align="left">DELAY</td> +<td align="left">15</td> +<td align="left">STP forwarding delay.<span class="bold"><strong> + +Allowed values: </strong></span>2 - 30</td> +</tr> +<tr> +<td align="left">hello-time</td> +<td align="left">BRIDGING_OPTS: hello_time=</td> +<td align="left">2</td> +<td align="left">STP hello time.<span class="bold"><strong> + +Allowed values: </strong></span>1 - 10</td> +</tr> +<tr> +<td align="left">max-age</td> +<td align="left">BRIDGING_OPTS: max_age=</td> +<td align="left">20</td> +<td align="left">STP maximum message age.<span class="bold"><strong> + +Allowed values: </strong></span>6 - 40</td> +</tr> +<tr> +<td align="left">ageing-time</td> +<td align="left">BRIDGING_OPTS: ageing_time=</td> +<td align="left">300</td> +<td align="left">Ethernet MAC ageing time.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 1000000</td> +</tr> +<tr> +<td align="left">multicast-snooping</td> +<td align="left">BRIDGING_OPTS: multicast_snooping=</td> +<td align="left">1</td> +<td align="left">IGMP snooping support.<span class="bold"><strong> + +Allowed values: </strong></span>0 or 1</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.7"></a><p class="title"><b>Table 73. connection setting</b></p> +<div class="table-contents"><table summary="connection setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">id</td> +<td align="left">NAME<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">User friendly name for the connection profile.</td> +</tr> +<tr> +<td align="left">uuid</td> +<td align="left">UUID<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">UUID for the connection profile. When missing, NetworkManager creates the UUID itself (by hashing the file).</td> +</tr> +<tr> +<td align="left">interface-name</td> +<td align="left">DEVICE</td> +<td align="left"> </td> +<td align="left">Interface name of the device this profile is bound to. The variable can be left out when the profile should apply for more devices. Note that DEVICE can be required for some connection types.</td> +</tr> +<tr> +<td align="left">type</td> +<td align="left">TYPE (DEVICETYPE, DEVICE)</td> +<td align="left"> </td> +<td align="left">Base type of the connection. DEVICETYPE is used for teaming connections.<span class="bold"><strong> + +Example: </strong></span>TYPE=Ethernet; TYPE=Bond; TYPE=Bridge; DEVICETYPE=TeamPort<span class="bold"><strong> + +Allowed values: </strong></span>Ethernet, Wireless, InfiniBand, Bridge, Bond, Vlan, Team, TeamPort</td> +</tr> +<tr> +<td align="left">permissions</td> +<td align="left">USERS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">USERS restrict the access for this conenction to certain users only.<span class="bold"><strong> + +Example: </strong></span>USERS="joe bob"</td> +</tr> +<tr> +<td align="left">autoconnect</td> +<td align="left">ONBOOT</td> +<td align="left">yes</td> +<td align="left">Whether the connection should be autoconnected (not only while booting).</td> +</tr> +<tr> +<td align="left">autoconnect-priority</td> +<td align="left">AUTOCONNECT_PRIORITY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">0</td> +<td align="left">Connection priority for automatic activation. Connections with higher numbers are preferred when selecting profiles for automatic activation.<span class="bold"><strong> + +Example: </strong></span>AUTOCONNECT_PRIORITY=20<span class="bold"><strong> + +Allowed values: </strong></span>-999 to 999</td> +</tr> +<tr> +<td align="left">zone</td> +<td align="left">ZONE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Trust level of this connection. The string is usually used for a firewall.<span class="bold"><strong> + +Example: </strong></span>ZONE=Work</td> +</tr> +<tr> +<td align="left">master</td> +<td align="left">MASTER, TEAM_MASTER, BRIDGE</td> +<td align="left"> </td> +<td align="left">Reference to master connection. The variable used depends on the connection type.</td> +</tr> +<tr> +<td align="left">slave-type</td> +<td align="left">MASTER, TEAM_MASTER, DEVICETYPE, BRIDGE</td> +<td align="left"> </td> +<td align="left">Slave type doesn't map directly to a variable, but it is recognized using different variables. MASTER for bonding, TEAM_MASTER and DEVICETYPE for teaming, BRIDGE for bridging.</td> +</tr> +<tr> +<td align="left">autoconnect-slaves</td> +<td align="left">AUTOCONNECT-SLAVES<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">missing variable means global default</td> +<td align="left">Whether slaves of this connection should be auto-connected when this connection is activated.</td> +</tr> +<tr> +<td align="left">secondaries</td> +<td align="left">SECONDARY_UUIDS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">UUID of VPN connections that should be activated together with this connection.</td> +</tr> +<tr> +<td align="left">gateway-ping-timeout</td> +<td align="left">GATEWAY_PING_TIMEOUT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">0</td> +<td align="left">If greater than zero, the IP connectivity will be checked by pinging the gateway and waiting for the specified timeout (in seconds).<span class="bold"><strong> + +Example: </strong></span>GATEWAY_PING_TIMEOUT=5</td> +</tr> +<tr> +<td align="left">metered</td> +<td align="left">CONNECTION_METERED</td> +<td align="left"> </td> +<td align="left">Whether the device is metered<span class="bold"><strong> + +Example: </strong></span>CONNECTION_METERED=yes<span class="bold"><strong> + +Allowed values: </strong></span>yes,no,unknown</td> +</tr> +<tr> +<td align="left">lldp</td> +<td align="left">LLDP</td> +<td align="left">missing variable means global default</td> +<td align="left">whether LLDP is enabled for the connection<span class="bold"><strong> + +Example: </strong></span>LLDP=no<span class="bold"><strong> + +Allowed values: </strong></span>boolean value or 'rx'</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.8"></a><p class="title"><b>Table 74. dcb setting</b></p> +<div class="table-contents"><table summary="dcb setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">app-fcoe-flags</td> +<td align="left">DCB_APP_FCOE_ENABLE, DCB_APP_FCOE_ADVERTISE, DCB_APP_FCOE_WILLING</td> +<td align="left">no</td> +<td align="left">FCOE flags.<span class="bold"><strong> + +Example: </strong></span>DCB_APP_FCOE_ENABLE=yes DCB_APP_FCOE_ADVERTISE=yes</td> +</tr> +<tr> +<td align="left">app-fcoe-priority</td> +<td align="left">DCB_APP_FCOE_PRIORITY</td> +<td align="left"> </td> +<td align="left">Priority of FCoE frames.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 7</td> +</tr> +<tr> +<td align="left">app-fcoe-mode</td> +<td align="left">DCB_APP_FCOE_MODE</td> +<td align="left">fabric</td> +<td align="left">FCoE controller mode.<span class="bold"><strong> + +Allowed values: </strong></span>fabric, vn2vn</td> +</tr> +<tr> +<td align="left">app-iscsi-flags</td> +<td align="left">DCB_APP_ISCSI_ENABLE, DCB_APP_ISCSI_ADVERTISE, DCB_APP_ISCSI_WILLING</td> +<td align="left">no</td> +<td align="left">iSCSI flags.</td> +</tr> +<tr> +<td align="left">app-iscsi-priority</td> +<td align="left">DCB_APP_ISCSI_PRIORITY</td> +<td align="left"> </td> +<td align="left">Priority of iSCSI frames.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 7</td> +</tr> +<tr> +<td align="left">app-fip-flags</td> +<td align="left">DCB_APP_FIP_ENABLE, DCB_APP_FIP_ADVERTISE, DCB_APP_FIP_WILLING</td> +<td align="left">no</td> +<td align="left">FIP flags.</td> +</tr> +<tr> +<td align="left">app-fip-priority</td> +<td align="left">DCB_APP_FIP_PRIORITY</td> +<td align="left"> </td> +<td align="left">Priority of FIP frames.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 7</td> +</tr> +<tr> +<td align="left">priority-flow-control-flags</td> +<td align="left">DCB_PFC_ENABLE, DCB_PFC_ADVERTISE, DCB_PFC_WILLING</td> +<td align="left">no</td> +<td align="left">Priority flow control flags.</td> +</tr> +<tr> +<td align="left">priority-flow-control</td> +<td align="left">DCB_PFC_UP</td> +<td align="left"> </td> +<td align="left">Priority flow control values. String of 8 "0" and "1", where "0". means "do not transmit priority pause", "1" means "transmit pause".<span class="bold"><strong> + +Example: </strong></span>DCB_PFC_UP=01101110</td> +</tr> +<tr> +<td align="left">priority-group-flags</td> +<td align="left">DCB_PG_ENABLE, DCB_PG_ADVERTISE, DCB_PG_WILLING</td> +<td align="left">no</td> +<td align="left">Priority groups flags.</td> +</tr> +<tr> +<td align="left">priority-group-id</td> +<td align="left">DCB_PG_ID</td> +<td align="left"> </td> +<td align="left">Priority groups values. String of eight priorities (0 - 7) or "f" (unrestricted).<span class="bold"><strong> + +Example: </strong></span>DCB_PG_ID=1205f173</td> +</tr> +<tr> +<td align="left">priority-group-bandwidth</td> +<td align="left">DCB_PG_PCT</td> +<td align="left"> </td> +<td align="left">Priority groups values. Eight bandwidths (in percent), separated with commas.<span class="bold"><strong> + +Example: </strong></span>DCB_PG_PCT=10,5,10,15,10,10,10,30</td> +</tr> +<tr> +<td align="left">priority-bandwidth</td> +<td align="left">DCB_PG_UPPCT</td> +<td align="left"> </td> +<td align="left">Priority values. Eight bandwidths (in percent), separated with commas. The sum of the numbers must be 100.<span class="bold"><strong> + +Example: </strong></span>DCB_PG_UPPCT=7,13,10,10,15,15,10,20</td> +</tr> +<tr> +<td align="left">priority-strict-bandwidth</td> +<td align="left">DCB_PG_STRICT</td> +<td align="left"> </td> +<td align="left">Priority values. String of eight "0" or "1", where "0" means "may not utilize all bandwidth", "1" means "may utilize all bandwidth".<span class="bold"><strong> + +Example: </strong></span>DCB_PG_STRICT=01101110</td> +</tr> +<tr> +<td align="left">priority-traffic-class</td> +<td align="left">DCB_PG_UP2TC</td> +<td align="left"> </td> +<td align="left">Priority values. String of eight trafic class values (0 - 7).<span class="bold"><strong> + +Example: </strong></span>DCB_PG_UP2TC=01623701</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><p> + 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> +<div class="table"> +<a name="id-1.4.7.7.10"></a><p class="title"><b>Table 75. infiniband setting</b></p> +<div class="table-contents"><table summary="infiniband setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">mac-address</td> +<td align="left">HWADDR</td> +<td align="left"> </td> +<td align="left">IBoIP 20-byte hardware address of the device (in traditional hex-digits-and-colons notation).<span class="bold"><strong> + +Example: </strong></span>HWADDR=01:02:03:04:05:06:07:08:09:0A:01:02:03:04:05:06:07:08:09:11</td> +</tr> +<tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the interface.</td> +</tr> +<tr> +<td align="left">transport-mode</td> +<td align="left">CONNECTED_MODE</td> +<td align="left">CONNECTED_MODE=no</td> +<td align="left">CONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" mode</td> +</tr> +<tr> +<td align="left">p-key</td> +<td align="left">PKEY_ID (and PKEY=yes)</td> +<td align="left">PKEY=no</td> +<td align="left">InfiniBand P_Key. The value can be a hex number prefixed with "0x" or a decimal number. When PKEY_ID is specified, PHYSDEV and DEVICE also must be specified.<span class="bold"><strong> + +Example: </strong></span>PKEY=yes PKEY_ID=2 PHYSDEV=mlx4_ib0 DEVICE=mlx4_ib0.8002</td> +</tr> +<tr> +<td align="left">parent</td> +<td align="left">PHYSDEV (PKEY=yes)</td> +<td align="left">PKEY=no</td> +<td align="left">InfiniBand parent device.<span class="bold"><strong> + +Example: </strong></span>PHYSDEV=ib0</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.11"></a><p class="title"><b>Table 76. ip-tunnel setting</b></p> +<div class="table-contents"><table summary="ip-tunnel setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.12"></a><p class="title"><b>Table 77. ipv4 setting</b></p> +<div class="table-contents"><table summary="ipv4 setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">method</td> +<td align="left">BOOTPROTO</td> +<td align="left">none</td> +<td align="left">Method used for IPv4 protocol configuration.<span class="bold"><strong> + +Allowed values: </strong></span>none, dhcp (bootp), static, ibft, autoip, shared</td> +</tr> +<tr> +<td align="left">dns</td> +<td align="left">DNS1, DNS2, ...</td> +<td align="left"> </td> +<td align="left">List of DNS servers. Even if NetworkManager supports many DNS servers, initscripts and resolver only care about the first three, usually.<span class="bold"><strong> + +Example: </strong></span>DNS1=1.2.3.4 DNS2=10.0.0.254 DNS3=8.8.8.8</td> +</tr> +<tr> +<td align="left">dns-search</td> +<td align="left">DOMAIN</td> +<td align="left"> </td> +<td align="left">List of DNS search domains.</td> +</tr> +<tr> +<td align="left">addresses</td> +<td align="left">IPADDR, PREFIX, IPADDR1, PREFIX1, ...</td> +<td align="left"> </td> +<td align="left">List of static IP addresses.<span class="bold"><strong> + +Example: </strong></span>IPADDR=10.5.5.23 PREFIX=24 IPADDR1=1.1.1.2 PREFIX1=16</td> +</tr> +<tr> +<td align="left">gateway</td> +<td align="left">GATEWAY</td> +<td align="left"> </td> +<td align="left">Gateway IP address.<span class="bold"><strong> + +Example: </strong></span>GATEWAY=10.5.5.1</td> +</tr> +<tr> +<td align="left">routes</td> +<td align="left">ADDRESS1, NETMASK1, GATEWAY1, METRIC1, ...</td> +<td align="left"> </td> +<td align="left">List of static routes. They are not stored in ifcfg-* file, but in route-* file instead.</td> +</tr> +<tr> +<td align="left">ignore-auto-routes</td> +<td align="left">PEERROUTES<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">PEERROUTES has the opposite meaning as 'ignore-auto-routes' property.</td> +</tr> +<tr> +<td align="left">ignore-auto-dns</td> +<td align="left">PEERDNS</td> +<td align="left">yes</td> +<td align="left">PEERDNS has the opposite meaning as 'ignore-auto-dns' property.</td> +</tr> +<tr> +<td align="left">dhcp-send-hostname</td> +<td align="left">DHCP_SEND_HOSTNAME<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">Whether DHCP_HOSTNAME should be sent to the DHCP server.</td> +</tr> +<tr> +<td align="left">dhcp-hostname</td> +<td align="left">DHCP_HOSTNAME</td> +<td align="left"> </td> +<td align="left">Hostname to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.</td> +</tr> +<tr> +<td align="left">never-default</td> +<td align="left">DEFROUTE (GATEWAYDEV in /etc/sysconfig/network)</td> +<td align="left">yes</td> +<td align="left">DEFROUTE=no tells NetworkManager that this connection should not be assigned the default route. DEFROUTE has the opposite meaning as 'never-default' property.</td> +</tr> +<tr> +<td align="left">may-fail</td> +<td align="left">IPV4_FAILURE_FATAL<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">IPV4_FAILURE_FATAL has the opposite meaning as 'may-fail' property.</td> +</tr> +<tr> +<td align="left">route-metric</td> +<td align="left">IPV4_ROUTE_METRIC<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">-1</td> +<td align="left">IPV4_ROUTE_METRIC is the default IPv4 metric for routes on this connection. If set to -1, a default metric based on the device type is used.</td> +</tr> +<tr> +<td align="left">dhcp-client-id</td> +<td align="left">DHCP_CLIENT_ID<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">A string sent to the DHCP server to identify the local machine.<span class="bold"><strong> + +Example: </strong></span>DHCP_CLIENT_ID=ax-srv-1</td> +</tr> +<tr> +<td align="left">dad-timeout</td> +<td align="left">ARPING_WAIT</td> +<td align="left">missing variable means global default (config override or 3)</td> +<td align="left">Timeout (in seconds) for performing DAD before configuring IPv4 addresses. 0 turns off the DAD completely, -1 means default value.<span class="bold"><strong> + +Example: </strong></span>ARPING_WAIT=2</td> +</tr> +<tr> +<td align="left">dhcp-timeout</td> +<td align="left">IPV4_DHCP_TIMEOUT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">A timeout after which the DHCP transaction fails in case of no response.<span class="bold"><strong> + +Example: </strong></span>IPV4_DHCP_TIMEOUT=10</td> +</tr> +<tr> +<td align="left">dhcp-fqdn</td> +<td align="left">DHCP_FQDN</td> +<td align="left"> </td> +<td align="left">FQDN to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.<span class="bold"><strong> + +Example: </strong></span>DHCP_FQDN=foo.bar.com</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.13"></a><p class="title"><b>Table 78. ipv6 setting</b></p> +<div class="table-contents"><table summary="ipv6 setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">method</td> +<td align="left">IPV6INIT, IPV6FORWARDING, IPV6_AUTOCONF, DHCPV6C</td> +<td align="left">IPV6INIT=yes; IPV6FORWARDING=no; IPV6_AUTOCONF=!IPV6FORWARDING, DHCPV6=no</td> +<td align="left">Method used for IPv6 protocol configuration. ignore ~ IPV6INIT=no; auto ~ IPV6_AUTOCONF=yes; dhcp ~ IPV6_AUTOCONF=no and DHCPV6C=yes</td> +</tr> +<tr> +<td align="left">dns</td> +<td align="left">DNS1, DNS2, ...</td> +<td align="left"> </td> +<td align="left">List of DNS servers. NetworkManager uses the variables both for IPv4 and IPv6.</td> +</tr> +<tr> +<td align="left">dns-search</td> +<td align="left">DOMAIN</td> +<td align="left"> </td> +<td align="left">List of DNS search domains.</td> +</tr> +<tr> +<td align="left">addresses</td> +<td align="left">IPV6ADDR, IPV6ADDR_SECONDARIES</td> +<td align="left"> </td> +<td align="left">List of static IP addresses.<span class="bold"><strong> + +Example: </strong></span>IPV6ADDR=ab12:9876::1 IPV6ADDR_SECONDARIES="ab12:9876::2 ab12:9876::3"</td> +</tr> +<tr> +<td align="left">gateway</td> +<td align="left">IPV6_DEFAULTGW</td> +<td align="left"> </td> +<td align="left">Gateway IP address.<span class="bold"><strong> + +Example: </strong></span>IPV6_DEFAULTGW=abbe::1</td> +</tr> +<tr> +<td align="left">routes</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">List of static routes. They are not stored in ifcfg-* file, but in route6-* file instead in the form of command line for 'ip route add'.</td> +</tr> +<tr> +<td align="left">ignore-auto-routes</td> +<td align="left">IPV6_PEERROUTES<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">IPV6_PEERROUTES has the opposite meaning as 'ignore-auto-routes' property.</td> +</tr> +<tr> +<td align="left">ignore-auto-dns</td> +<td align="left">IPV6_PEERDNS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">IPV6_PEERDNS has the opposite meaning as 'ignore-auto-dns' property.</td> +</tr> +<tr> +<td align="left">dhcp-hostname</td> +<td align="left">DHCP_HOSTNAME</td> +<td align="left"> </td> +<td align="left">Hostname to send the DHCP server.</td> +</tr> +<tr> +<td align="left">never-default</td> +<td align="left">IPV6_DEFROUTE<span class="emphasis"><em>(+)</em></span>, (and IPV6_DEFAULTGW, IPV6_DEFAULTDEV in /etc/sysconfig/network)</td> +<td align="left">IPV6_DEFROUTE=yes (when no variable specified)</td> +<td align="left">IPV6_DEFROUTE=no tells NetworkManager that this connection should not be assigned the default IPv6 route. IPV6_DEFROUTE has the opposite meaning as 'never-default' property.</td> +</tr> +<tr> +<td align="left">may-fail</td> +<td align="left">IPV6_FAILURE_FATAL<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">IPV6_FAILURE_FATAL has the opposite meaning as 'may-fail' property.</td> +</tr> +<tr> +<td align="left">route-metric</td> +<td align="left">IPV6_ROUTE_METRIC<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">-1</td> +<td align="left">IPV6_ROUTE_METRIC is the default IPv6 metric for routes on this connection. If set to -1, a default metric based on the device type is used.</td> +</tr> +<tr> +<td align="left">ip6-privacy</td> +<td align="left">IPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Configure IPv6 Privacy Extensions for SLAAC (RFC4941).<span class="bold"><strong> + +Example: </strong></span>IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes<span class="bold"><strong> + +Allowed values: </strong></span>IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6_PRIVACY_PREFER_PUBLIC_IP: yes, no</td> +</tr> +<tr> +<td align="left">addr-gen-mode</td> +<td align="left">IPV6_ADDR_GEN_MODE</td> +<td align="left">eui64</td> +<td align="left">Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217).<span class="bold"><strong> + +Example: </strong></span>IPV6_ADDR_GEN_MODE=stable-privacy<span class="bold"><strong> + +Allowed values: </strong></span>IPV6_ADDR_GEN_MODE: eui64, stable-privacy</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.14"></a><p class="title"><b>Table 79. macvlan setting</b></p> +<div class="table-contents"><table summary="macvlan setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.15"></a><p class="title"><b>Table 80. team-port setting</b></p> +<div class="table-contents"><table summary="team-port setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody><tr> +<td align="left">config</td> +<td align="left">TEAM_PORT_CONFIG</td> +<td align="left"> </td> +<td align="left">Team port configuration in JSON. See man teamd.conf for details.</td> +</tr></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.16"></a><p class="title"><b>Table 81. team setting</b></p> +<div class="table-contents"><table summary="team setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody><tr> +<td align="left">config</td> +<td align="left">TEAM_CONFIG</td> +<td align="left"> </td> +<td align="left">Team configuration in JSON. See man teamd.conf for details.</td> +</tr></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.17"></a><p class="title"><b>Table 82. tun setting</b></p> +<div class="table-contents"><table summary="tun setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.18"></a><p class="title"><b>Table 83. vlan setting</b></p> +<div class="table-contents"><table summary="vlan setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">parent</td> +<td align="left">DEVICE or PHYSDEV</td> +<td align="left"> </td> +<td align="left">Parent interface of the VLAN.</td> +</tr> +<tr> +<td align="left">id</td> +<td align="left">VLAN_ID or DEVICE</td> +<td align="left"> </td> +<td align="left">VLAN identifier.</td> +</tr> +<tr> +<td align="left">flags</td> +<td align="left">GVRP, MVRP, VLAN_FLAGS</td> +<td align="left"> </td> +<td align="left">VLAN flags.<span class="bold"><strong> + +Allowed values: </strong></span>"yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS</td> +</tr> +<tr> +<td align="left">ingress-priority-map</td> +<td align="left">VLAN_INGRESS_PRIORITY_MAP</td> +<td align="left"> </td> +<td align="left">Ingress priority mapping.<span class="bold"><strong> + +Example: </strong></span>VLAN_INGRESS_PRIORITY_MAP=4:2,3:5</td> +</tr> +<tr> +<td align="left">egress-priority-map</td> +<td align="left">VLAN_EGRESS_PRIORITY_MAP</td> +<td align="left"> </td> +<td align="left">Egress priority mapping.<span class="bold"><strong> + +Example: </strong></span>VLAN_EGRESS_PRIORITY_MAP=5:4,4:1,3:7</td> +</tr> +<tr> +<td align="left">interface-name</td> +<td align="left">PHYSDEV and VLAN_ID, or DEVICE</td> +<td align="left"> </td> +<td align="left">VLAN interface name. If all variables are set, parent device from PHYSDEV takes precedence over DEVICE, but VLAN id from DEVICE takes precedence over VLAN_ID.<span class="bold"><strong> + +Example: </strong></span>PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.19"></a><p class="title"><b>Table 84. vxlan setting</b></p> +<div class="table-contents"><table summary="vxlan setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.20"></a><p class="title"><b>Table 85. 802-3-ethernet setting</b></p> +<div class="table-contents"><table summary="802-3-ethernet setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">port</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not saved by the plugin.</td> +</tr> +<tr> +<td align="left">speed</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not saved by the plugin.</td> +</tr> +<tr> +<td align="left">duplex</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not saved by the plugin.</td> +</tr> +<tr> +<td align="left">auto-negotiate</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not saved by the plugin.</td> +</tr> +<tr> +<td align="left">mac-address</td> +<td align="left">HWADDR</td> +<td align="left"> </td> +<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05).</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left">MACADDR</td> +<td align="left"> </td> +<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">It denies usage of the connection for any device whose address is listed.<span class="bold"><strong> + +Example: </strong></span>HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"</td> +</tr> +<tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the interface.</td> +</tr> +<tr> +<td align="left">s390-subchannels</td> +<td align="left">SUBCHANNELS</td> +<td align="left"> </td> +<td align="left">Subchannels for IBM S390 hosts.<span class="bold"><strong> + +Example: </strong></span>SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c</td> +</tr> +<tr> +<td align="left">s390-nettype</td> +<td align="left">NETTYPE</td> +<td align="left"> </td> +<td align="left">Network type of the S390 host.<span class="bold"><strong> + +Example: </strong></span>NETTYPE=qeth<span class="bold"><strong> + +Allowed values: </strong></span>"qeth", "lcs" or "ctc"</td> +</tr> +<tr> +<td align="left">s390-options</td> +<td align="left">OPTIONS and PORTNAME, CTCPROTO,</td> +<td align="left"> </td> +<td align="left">S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables.</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.21"></a><p class="title"><b>Table 86. 802-11-wireless-security setting</b></p> +<div class="table-contents"><table summary="802-11-wireless-security setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">key-mgmt</td> +<td align="left">KEY_MGMT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Key management menthod.<span class="bold"><strong> + +Allowed values: </strong></span>IEEE8021X, WPA-PSK, WPA-EAP</td> +</tr> +<tr> +<td align="left">wep-tx-keyidx</td> +<td align="left">DEFAULTKEY</td> +<td align="left">1</td> +<td align="left">Index of active WEP key.<span class="bold"><strong> + +Allowed values: </strong></span>1, 2, 3, 4</td> +</tr> +<tr> +<td align="left">auth-alg</td> +<td align="left">SECURITYMODE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Authentication algorithm for WEP.<span class="bold"><strong> + +Allowed values: </strong></span>restricted, open, leap</td> +</tr> +<tr> +<td align="left">proto</td> +<td align="left">WPA_ALLOW_WPA<span class="emphasis"><em>(+)</em></span>, WPA_ALLOW_WPA2<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Allowed WPA protocols, WPA and WPA2 (RSN).<span class="bold"><strong> + +Allowed values: </strong></span>yes, no</td> +</tr> +<tr> +<td align="left">pairwise</td> +<td align="left">CIPHER_PAIRWISE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restrict pairwise encryption algorithms, specified as a space separated list.<span class="bold"><strong> + +Allowed values: </strong></span>CCMP, TKIP</td> +</tr> +<tr> +<td align="left">group</td> +<td align="left">CIPHER_GROUP<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restrict group/broadcast encryption algorithms, specified as a space separated list.<span class="bold"><strong> + +Allowed values: </strong></span>CCMP, TKIP, WEP40, WEP104</td> +</tr> +<tr> +<td align="left">leap-username</td> +<td align="left">IEEE_8021X_IDENTITY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Login name for LEAP.</td> +</tr> +<tr> +<td align="left">wep-key0</td> +<td align="left">KEY1, KEY_PASSPHRASE1<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">The first WEP key (used in most networks). See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key1</td> +<td align="left">KEY2, KEY_PASSPHRASE2<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 1. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key2</td> +<td align="left">KEY3, KEY_PASSPHRASE3<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 2. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key3</td> +<td align="left">KEY4, KEY_PASSPHRASE4<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 3. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key-flags</td> +<td align="left">WEP_KEY_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">psk</td> +<td align="left">WPA_PSK</td> +<td align="left"> </td> +<td align="left">Pre-Shared-Key for WPA networks.</td> +</tr> +<tr> +<td align="left">psk-flags</td> +<td align="left">WPA_PSK_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for WPA_PSK_FLAGS. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)<span class="bold"><strong> + +Example: </strong></span>WPA_PSK_FLAGS=user</td> +</tr> +<tr> +<td align="left">leap-password</td> +<td align="left">IEEE_8021X_PASSWORD<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> +</tr> +<tr> +<td align="left">leap-password-flags</td> +<td align="left">IEEE_8021X_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for IEEE_8021X_PASSWORD_FLAGS. (see <a class="xref" href="secrets-flags.html" title="Secret flag types">the section called “Secret flag types”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">wep-key-type</td> +<td align="left">KEY<i> or KEY_PASSPHRASE<i><span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases.<span class="bold"><strong> + +Example: </strong></span>KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.4.7.7.22"></a><p class="title"><b>Table 87. 802-11-wireless setting</b></p> +<div class="table-contents"><table summary="802-11-wireless setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">ssid</td> +<td align="left">ESSID</td> +<td align="left"> </td> +<td align="left">SSID of Wi-Fi network.<span class="bold"><strong> + +Example: </strong></span>ESSID="Quick Net"</td> +</tr> +<tr> +<td align="left">mode</td> +<td align="left">MODE</td> +<td align="left"> </td> +<td align="left">Wi-Fi network mode.<span class="bold"><strong> + +Allowed values: </strong></span>Ad-Hoc, Managed (Auto) [case insensitive]</td> +</tr> +<tr> +<td align="left">band</td> +<td align="left">BAND<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">BAND alone is honored, but CHANNEL overrides BAND since it implies a band.<span class="bold"><strong> + +Example: </strong></span>BAND=bg<span class="bold"><strong> + +Allowed values: </strong></span>a, bg</td> +</tr> +<tr> +<td align="left">channel</td> +<td align="left">CHANNEL</td> +<td align="left"> </td> +<td align="left">Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg".<span class="bold"><strong> + +Example: </strong></span>CHANNEL=6</td> +</tr> +<tr> +<td align="left">bssid</td> +<td align="left">BSSID<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restricts association only to a single AP.<span class="bold"><strong> + +Example: </strong></span>BSSID=00:1E:BD:64:83:21</td> +</tr> +<tr> +<td align="left">rate</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">tx-power</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">mac-address</td> +<td align="left">HWADDR</td> +<td align="left"> </td> +<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05).</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left">MACADDR</td> +<td align="left"> </td> +<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">It denies usage of the connection for any device whose address is listed.</td> +</tr> +<tr> +<td align="left">seen-bssids</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the wireless interface.</td> +</tr> +<tr> +<td align="left">hidden</td> +<td align="left">SSID_HIDDEN<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Whether the network hides the SSID.</td> +</tr> +<tr> +<td align="left">powersave</td> +<td align="left">POWERSAVE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables Wi-Fi power saving.<span class="bold"><strong> + +Example: </strong></span>POWERSAVE=enable<span class="bold"><strong> + +Allowed values: </strong></span>default, ignore, enable, disable</td> +</tr> +<tr> +<td align="left">mac-address-randomization</td> +<td align="left">MAC_ADDRESS_RANDOMIZATION<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables Wi-Fi MAC address randomization.<span class="bold"><strong> + +Example: </strong></span>MAC_ADDRESS_RANDOMIZATION=always<span class="bold"><strong> + +Allowed values: </strong></span>default, never, always</td> +</tr> +<tr> +<td align="left">security</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is deprecated and not handled by ifcfg-rh-plugin.</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><p>The following settings are not supported by <span class="emphasis"><em>ifcfg-rh</em></span> plugin:</p> +<p>adsl, bluetooth, ppp, pppoe, serial, generic, gsm, cdma, 802-11-olpc-mesh, wimax, vpn</p> +<div class="refsect2"> +<a name="secrets-flags"></a><h3>Secret flags</h3> +<p> + Each secret property in a NetworkManager setting has an associated + <span class="emphasis"><em>flags</em></span> property that describes how to handle that secret. + In the <span class="emphasis"><em>fcfg-rh</em></span> plugin variables for secret flags have a + <span class="emphasis"><em>_FLAGS</em></span> 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> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> +<li class="listitem"><p><code class="literal">user</code> - a user-session secret agent is responsible for providing + and storing this secret; when it is required, agents will be asked to provide it.</p></li> +<li class="listitem"><p><code class="literal">ask</code> - the associated password is not saved but it will be + requested from the user each time it is required.</p></li> +<li class="listitem"><p><code class="literal">unused</code> - 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></li> +</ul></div> +</div> +</div> +<div class="refsect1"> +<a name="id-1.4.7.8"></a><h2>AUTHOR</h2> +<p><span class="author"><span class="firstname">NetworkManager developers</span></span></p> +</div> +<div class="refsect1"> +<a name="id-1.4.7.9"></a><h2>FILES</h2> +<p><code class="filename">/etc/sysconfig/network-scripts/ifcfg-*</code></p> +<p><code class="filename">/etc/sysconfig/network-scripts/keys-*</code></p> +<p><code class="filename">/etc/sysconfig/network-scripts/route-*</code></p> +<p><code class="filename">/etc/sysconfig/network-scripts/route6-*</code></p> +<p><code class="filename">/usr/share/doc/initscripts/sysconfig.txt</code></p> +</div> +<div class="refsect1"> +<a name="id-1.4.7.10"></a><h2>SEE ALSO</h2> +<p>https://developer.gnome.org/NetworkManager/unstable/ref-settings.html</p> +<p>nm-settings(5), nm-settings-keyfile(5), NetworkManager(8), NetworkManager.conf(5), nmcli(1), nmcli-examples(5)</p> +</div> +</div> +<div class="footer"> +<hr>Generated by GTK-Doc V1.24</div> +</body> +</html> \ No newline at end of file |