/usr/share/gtk-doc/html/NetworkManager/nm-settings-ifcfg-rh.html is in network-manager-dev 1.10.6-2ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 | <!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 Reference Manual</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="index.html" title="NetworkManager Reference Manual">
<link rel="up" href="manpages.html" title="Part I. Manual Pages">
<link rel="prev" href="nm-settings-keyfile.html" title="nm-settings-keyfile">
<link rel="next" href="nm-online.html" title="nm-online">
<meta name="generator" content="GTK-Doc V1.27 (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="nm-online.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="description"></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
(<a class="link" href="nm-settings-keyfile.html" title="nm-settings-keyfile"><span class="citerefentry"><span class="refentrytitle">nm-settings-keyfile</span>(5)</span></a>).
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="file_format"></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="differences_against_initscripts"></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>
<li class="listitem"><p><code class="literal">HWADDR</code> -
initscripts compare the currently set hardware address of a device, while
NetworkManager considers the permanent one.</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 below.
</p>
</div>
<div class="refsect1">
<a name="details"></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.2.9.7.3"></a><p class="title"><b>Table 34. 802-1x setting</b></p>
<div class="table-contents"><table class="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">phase1-auth-flags</td>
<td align="left">IEEE_8021X_PHASE1_AUTH_FLAGS<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">Authentication flags for the supplicant<span class="bold"><strong>
Example: </strong></span>IEEE_8021X_PHASE1_AUTH_FLAGS="tls-1-0-disable tls-1-1-disable"<span class="bold"><strong>
Allowed values: </strong></span>space-separated list of authentication flags names</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="nm-settings.html#secrets-flags" 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">IEEE_8021X_PASSWORD_RAW<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">password used for EAP, encoded as a hexadecimal string. It can also go to "key-" lookaside file.<span class="bold"><strong>
Example: </strong></span>IEEE_8021X_PASSWORD_RAW=041c8320083aa4bf</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="nm-settings.html#secrets-flags" 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="nm-settings.html#secrets-flags" 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>
<tr>
<td align="left">auth-timeout</td>
<td align="left">IEEE_8021X_AUTH_TIMEOUT<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">Timeout in seconds for the 802.1X authentication. Zero means the global default or 25.</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.4"></a><p class="title"><b>Table 35. bond setting</b></p>
<div class="table-contents"><table class="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.2.9.7.5"></a><p class="title"><b>Table 36. bridge-port setting</b></p>
<div class="table-contents"><table class="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.2.9.7.6"></a><p class="title"><b>Table 37. bridge setting</b></p>
<div class="table-contents"><table class="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">BRIDGE_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) BRIDGE_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.2.9.7.7"></a><p class="title"><b>Table 38. connection setting</b></p>
<div class="table-contents"><table class="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 filename).</td>
</tr>
<tr>
<td align="left">stable-id</td>
<td align="left">STABLE_ID<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">Token to generate stable IDs.</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">Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session.<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">autoconnect-retries</td>
<td align="left">AUTOCONNECT_RETRIES<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">The number of times a connection should be autoactivated before giving up and switching to the next one.<span class="bold"><strong>
Example: </strong></span>AUTOCONNECT_RETRIES=1<span class="bold"><strong>
Allowed values: </strong></span>-1 (use global default), 0 (forever) or a positive value</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, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, BRIDGE, BRIDGE_UUID</td>
<td align="left"> </td>
<td align="left">Reference to master connection. The variable used depends on the connection type and the value. In general, if the *_UUID variant is present, the variant without *_UUID is ignored. NetworkManager attempts to write both for compatibility with legacy tooling.</td>
</tr>
<tr>
<td align="left">slave-type</td>
<td align="left">MASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, DEVICETYPE, BRIDGE, BRIDGE_UUID</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 and MASTER_UUID for bonding, TEAM_MASTER, TEAM_MASTER_UUID and DEVICETYPE for teaming, BRIDGE and BRIDGE_UUID 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<span class="emphasis"><em>(+)</em></span>
</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<span class="emphasis"><em>(+)</em></span>
</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>
<tr>
<td align="left">auth-retries</td>
<td align="left">AUTH_RETRIES<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">Number of retries for authentication.</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.8"></a><p class="title"><b>Table 39. dcb setting</b></p>
<div class="table-contents"><table class="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.2.9.7.10"></a><p class="title"><b>Table 40. infiniband setting</b></p>
<div class="table-contents"><table class="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). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.<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.2.9.7.11"></a><p class="title"><b>Table 41. ipv4 setting</b></p>
<div class="table-contents"><table class="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, OPTIONS1, ...</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">route-table</td>
<td align="left">IPV4_ROUTE_TABLE<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">IPV4_ROUTE_TABLE enables policy-routing and sets the default routing table.</td>
</tr>
<tr>
<td align="left">dns-options</td>
<td align="left">RES_OPTIONS<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">List of DNS options to be added to /etc/resolv.conf<span class="bold"><strong>
Example: </strong></span>RES_OPTIONS=ndots:2 timeout:3</td>
</tr>
<tr>
<td align="left">dns-priority</td>
<td align="left">IPV4_DNS_PRIORITY<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.<span class="bold"><strong>
Example: </strong></span>IPV4_DNS_PRIORITY=20</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. A binary value can be specified using hex notation ('aa:bb:cc').<span class="bold"><strong>
Example: </strong></span>DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44"</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.2.9.7.12"></a><p class="title"><b>Table 42. ipv6 setting</b></p>
<div class="table-contents"><table class="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">IPV6_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">route-table</td>
<td align="left">IPV6_ROUTE_TABLE<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">IPV6_ROUTE_TABLE enables policy-routing and sets the default routing table.</td>
</tr>
<tr>
<td align="left">dns-priority</td>
<td align="left">IPV6_DNS_PRIORITY<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">0</td>
<td align="left">The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.<span class="bold"><strong>
Example: </strong></span>IPV6_DNS_PRIORITY=20</td>
</tr>
<tr>
<td align="left">dns-options</td>
<td align="left">IPV6_RES_OPTIONS<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">List of DNS options to be added to /etc/resolv.conf<span class="bold"><strong>
Example: </strong></span>IPV6_RES_OPTIONS=ndots:2 timeout:3</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>
<tr>
<td align="left">token</td>
<td align="left">IPV6_TOKEN</td>
<td align="left"> </td>
<td align="left">The IPv6 tokenized interface identifier token<span class="bold"><strong>
Example: </strong></span>IPV6_TOKEN=::53</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.13"></a><p class="title"><b>Table 43. ovs-bridge setting</b></p>
<div class="table-contents"><table class="table" summary="ovs-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></tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.14"></a><p class="title"><b>Table 44. ovs-interface setting</b></p>
<div class="table-contents"><table class="table" summary="ovs-interface 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.2.9.7.15"></a><p class="title"><b>Table 45. ovs-patch setting</b></p>
<div class="table-contents"><table class="table" summary="ovs-patch 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.2.9.7.16"></a><p class="title"><b>Table 46. ovs-port setting</b></p>
<div class="table-contents"><table class="table" summary="ovs-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></tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.17"></a><p class="title"><b>Table 47. proxy setting</b></p>
<div class="table-contents"><table class="table" summary="proxy 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">PROXY_METHOD<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">none</td>
<td align="left">Method for proxy configuration. For "auto", WPAD is used for proxy configuration, or set the PAC file via PAC_URL or PAC_SCRIPT.<span class="bold"><strong>
Allowed values: </strong></span>none, auto</td>
</tr>
<tr>
<td align="left">browser-only</td>
<td align="left">BROWSER_ONLY<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left">no</td>
<td align="left">Whether the proxy configuration is for browser only.</td>
</tr>
<tr>
<td align="left">pac-url</td>
<td align="left">PAC_URL<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">URL for PAC file.<span class="bold"><strong>
Example: </strong></span>PAC_URL=http://wpad.mycompany.com/wpad.dat</td>
</tr>
<tr>
<td align="left">pac-script</td>
<td align="left">PAC_SCRIPT<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">Path of the PAC script.<span class="bold"><strong>
Example: </strong></span>PAC_SCRIPT=/home/joe/proxy.pac</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.18"></a><p class="title"><b>Table 48. tc setting</b></p>
<div class="table-contents"><table class="table" summary="tc 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">qdiscs</td>
<td align="left">QDISC1, QDISC2, ...</td>
<td align="left"> </td>
<td align="left">Queueing disciplines<span class="bold"><strong>
Example: </strong></span>QDISC1=ingress, QDISC2="root handle 1234: fq_codel"</td>
</tr>
<tr>
<td align="left">qdiscs</td>
<td align="left">FILTER1, FILTER2, ...</td>
<td align="left"> </td>
<td align="left">Traffic filters<span class="bold"><strong>
Example: </strong></span>FILTER1="parent ffff: matchall action simple sdata Input", ...</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.19"></a><p class="title"><b>Table 49. team-port setting</b></p>
<div class="table-contents"><table class="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.2.9.7.20"></a><p class="title"><b>Table 50. team setting</b></p>
<div class="table-contents"><table class="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.2.9.7.21"></a><p class="title"><b>Table 51. user setting</b></p>
<div class="table-contents"><table class="table" summary="user 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">data</td>
<td align="left">NM_USER_*</td>
<td align="left"> </td>
<td align="left">each key/value pair is stored as a separate variable with name composed by concatenating NM_USER_ with the encoded key. The key is encoded by substituting lowercase letters with uppercase and prepending uppercase letters with an underscore. A dot is encoded as a double underscore. Remaining characters are encoded as underscore followed by a 3 digit octal representation of the character.<span class="bold"><strong>
Example: </strong></span>NM_USER_FOO__BAR=something</td>
</tr></tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.22"></a><p class="title"><b>Table 52. vlan setting</b></p>
<div class="table-contents"><table class="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.2.9.7.23"></a><p class="title"><b>Table 53. 802-3-ethernet setting</b></p>
<div class="table-contents"><table class="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">ETHTOOL_OPTS</td>
<td align="left"> </td>
<td align="left">Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable.</td>
</tr>
<tr>
<td align="left">duplex</td>
<td align="left">ETHTOOL_OPTS</td>
<td align="left"> </td>
<td align="left">Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable.</td>
</tr>
<tr>
<td align="left">auto-negotiate</td>
<td align="left">ETHTOOL_OPTS</td>
<td align="left"> </td>
<td align="left">Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration).</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). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</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">generate-mac-address-mask</td>
<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</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.2.9.7.24"></a><p class="title"><b>Table 54. 802-11-wireless-security setting</b></p>
<div class="table-contents"><table class="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">pmf</td>
<td align="left">PMF<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">Enables or disables PMF (802.11w)<span class="bold"><strong>
Example: </strong></span>PMF=required<span class="bold"><strong>
Allowed values: </strong></span>default, disable, optional, required</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="nm-settings.html#secrets-flags" 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="nm-settings.html#secrets-flags" 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="nm-settings.html#secrets-flags" 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>; KEY_TYPE<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. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted.<span class="bold"><strong>
Example: </strong></span>KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey</td>
</tr>
<tr>
<td align="left">wps-method</td>
<td align="left">WPS_METHOD</td>
<td align="left"> </td>
<td align="left">Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used.<span class="bold"><strong>
Example: </strong></span>WPS_METHOD=disabled, WPS_METHOD="pin pbc"</td>
</tr>
</tbody>
</table></div>
</div>
<br class="table-break"><div class="table">
<a name="id-1.2.9.7.25"></a><p class="title"><b>Table 55. 802-11-wireless setting</b></p>
<div class="table-contents"><table class="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). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</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">generate-mac-address-mask</td>
<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span>
</td>
<td align="left"> </td>
<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</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>802-11-olpc-mesh, adsl, bluetooth, cdma, dummy, generic, gsm, ip-tunnel, macsec, macvlan, ppp, pppoe, serial, tun, vpn, vxlan, wimax</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="files"></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="see_also"></a><h2>See Also</h2>
<p><a class="link" href="nm-settings.html" title="nm-settings"><span class="citerefentry"><span class="refentrytitle">nm-settings</span>(5)</span></a>,
<a class="link" href="nm-settings-keyfile.html" title="nm-settings-keyfile"><span class="citerefentry"><span class="refentrytitle">nm-settings-keyfile</span>(5)</span></a>,
<a class="link" href="NetworkManager.html" title="NetworkManager"><span class="citerefentry"><span class="refentrytitle">NetworkManager</span>(8)</span></a>,
<a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a>,
<a class="link" href="nmcli.html" title="nmcli"><span class="citerefentry"><span class="refentrytitle">nmcli</span>(1)</span></a>,
<a class="link" href="nmcli-examples.html" title="nmcli-examples"><span class="citerefentry"><span class="refentrytitle">nmcli-examples</span>(7)</span></a></p>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.27</div>
</body>
</html>
|