summary refs log tree commit diff
path: root/docs/api/html/nm-settings-dbus.html
blob: 8ccfcdb711178191a9e90b82993500165c4aee33 (plain) 
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
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283

<!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-dbus: NetworkManager Reference Manual</title>
<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<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="nmtui.html" title="nmtui">
<link rel="next" href="nm-settings-nmcli.html" title="nm-settings-nmcli">
<meta name="generator" content="GTK-Doc V1.33.1 (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="nmtui.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="nm-settings-nmcli.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="nm-settings-dbus"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">nm-settings-dbus</span></h2>
<p>nm-settings-dbus — Description of settings and properties of NetworkManager connection profiles on the D-Bus API</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 a concept of connection profiles, sometimes referred to as
          connections only. These connection profiles contain a network configuration. When
          NetworkManager activates a connection profile on a network device the configuration will
          be applied and an active network connection will be established. Users are free to create
          as many connection profiles as they see fit. Thus they are flexible in having various network
          configurations for different networking needs. The connection profiles are handled by
          NetworkManager via <span class="emphasis"><em>settings service</em></span> and are exported on D-Bus
          (<span class="emphasis"><em>/org/freedesktop/NetworkManager/Settings/&lt;num&gt;</em></span> objects).
          The conceptual objects can be described as follows:
          </p>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody><tr>
<td><p><span class="term">Connection (profile)</span></p></td>
<td><p>
                  A specific, encapsulated, independent group of settings describing
                  all the configuration required to connect to a specific network.
                  It is referred to by a unique identifier called the UUID. A connection
                  is tied to a one specific device type, but not necessarily a specific
                  hardware device. It is composed of one or more <span class="emphasis"><em>Settings</em></span>
                  objects.
                </p></td>
</tr></tbody>
</table></div>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody><tr>
<td><p><span class="term">Setting</span></p></td>
<td><p>
                  A group of related key/value pairs describing a specific piece of a
                  <span class="emphasis"><em>Connection (profile)</em></span>. Settings keys and allowed values are
                  described in the tables below. Keys are also referred to as properties.
                  Developers can find the setting objects and their properties in the libnm-core
                  sources. Look for the <code class="function">*_class_init</code> functions near the bottom
                  of each setting source file.
                </p></td>
</tr></tbody>
</table></div>
<div class="variablelist">
<p>
              The settings and properties shown in tables below list all available connection
              configuration options. However, note that not all settings are applicable to all
              connection types. NetworkManager provides a command-line tool <span class="emphasis"><em>nmcli</em></span>
              that allows direct configuration of the settings and properties according to a connection
              profile type. <span class="emphasis"><em>nmcli</em></span> connection editor has also a built-in
              <span class="emphasis"><em>describe</em></span> command that can display description of particular settings
              and properties of this page.
            </p>
<table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody></tbody>
</table>
</div>
<div class="refsect2">
<a name="id-1.2.8.4.3"></a><h3>connection setting</h3>
<p>General Connection Profile Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.auth-retries"></a>auth-retries</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.autoconnect"></a>autoconnect</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.autoconnect-priority"></a>autoconnect-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.autoconnect-retries"></a>autoconnect-retries</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.autoconnect-slaves"></a>autoconnect-slaves</td>
<td align="left">NMSettingConnectionAutoconnectSlaves (int32)</td>
<td align="left"> </td>
<td>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.dns-over-tls"></a>dns-over-tls</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.id"></a>id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.lldp"></a>lldp</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether LLDP is enabled for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.llmnr"></a>llmnr</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.master"></a>master</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Interface name of the master device or UUID of the master connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.mdns"></a>mdns</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.metered"></a>metered</td>
<td align="left">NMMetered (int32)</td>
<td align="left"> </td>
<td>Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.mud-url"></a>mud-url</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.multi-connect"></a>multi-connect</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.permissions"></a>permissions</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>An array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.read-only"></a>read-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.secondaries"></a>secondaries</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.slave-type"></a>slave-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.stable-id"></a>stable-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret-key. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.timestamp"></a>timestamp</td>
<td align="left">uint64</td>
<td align="left">0</td>
<td>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.uuid"></a>uuid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.wait-device-timeout"></a>wait-device-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.connection.zone"></a>zone</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.4"></a><h3>6lowpan setting</h3>
<p>6LoWPAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.6lowpan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.5"></a><h3>802-1x setting</h3>
<p>IEEE 802.1x Authentication Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.altsubject-matches"></a>altsubject-matches</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.anonymous-identity"></a>anonymous-identity</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.auth-timeout"></a>auth-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.ca-cert"></a>ca-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.ca-cert-password"></a>ca-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.ca-cert-password-flags"></a>ca-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "ca-cert-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.ca-path"></a>ca-path</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.client-cert"></a>client-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.client-cert-password"></a>client-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.client-cert-password-flags"></a>client-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "client-cert-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.domain-match"></a>domain-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.domain-suffix-match"></a>domain-suffix-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.eap"></a>eap</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>The allowed EAP method to be used when authenticating to the network with 802.1x.  Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast".  Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.identity"></a>identity</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Identity string for EAP authentication methods.  Often the user's user or login name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.optional"></a>optional</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.pac-file"></a>pac-file</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded file path containing PAC for EAP-FAST.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.password-raw"></a>password-raw</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.password-raw-flags"></a>password-raw-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password-raw" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase1-auth-flags"></a>phase1-auth-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase1-fast-provisioning"></a>phase1-fast-provisioning</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning).  See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase1-peaplabel"></a>phase1-peaplabel</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Forces use of the new PEAP label during key derivation.  Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1.  Set to "1" to force use of the new PEAP label.  See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase1-peapver"></a>phase1-peapver</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property.  When unset, the version reported by the server will be used.  Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version.  To do so, this property may be set to "0" or "1" to force that specific PEAP version.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-altsubject-matches"></a>phase2-altsubject-matches</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-auth"></a>phase2-auth</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method.  For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-autheap"></a>phase2-autheap</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-ca-cert"></a>phase2-ca-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-ca-cert-password"></a>phase2-ca-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-ca-cert-password-flags"></a>phase2-ca-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-ca-cert-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-ca-path"></a>phase2-ca-path</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-client-cert"></a>phase2-client-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-client-cert-password"></a>phase2-client-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-client-cert-password-flags"></a>phase2-client-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-client-cert-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-domain-match"></a>phase2-domain-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-domain-suffix-match"></a>phase2-domain-suffix-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-private-key"></a>phase2-private-key</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-private-key-password"></a>phase2-private-key-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-private-key-password-flags"></a>phase2-private-key-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-private-key-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.phase2-subject-match"></a>phase2-subject-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.pin"></a>pin</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PIN used for EAP authentication methods.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.pin-flags"></a>pin-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "pin" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.private-key"></a>private-key</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users.  Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.private-key-password"></a>private-key-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.private-key-password-flags"></a>private-key-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "private-key-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.subject-match"></a>subject-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-1x.system-ca-certs"></a>system-ca-certs</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch.  The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.6"></a><h3>adsl setting</h3>
<p>ADSL Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.encapsulation"></a>encapsulation</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Encapsulation of ADSL connection.  Can be "vcmux" or "llc".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Password used to authenticate with the ADSL service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.protocol"></a>protocol</td>
<td align="left">string</td>
<td align="left"> </td>
<td>ADSL connection protocol.  Can be "pppoa", "pppoe" or "ipoatm".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Username used to authenticate with the ADSL service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.vci"></a>vci</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>VCI of ADSL connection</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.adsl.vpi"></a>vpi</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>VPI of ADSL connection</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.7"></a><h3>bluetooth setting</h3>
<p>Bluetooth Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bluetooth.bdaddr"></a>bdaddr</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>The Bluetooth address of the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bluetooth.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.8"></a><h3>bond setting</h3>
<p>Bonding Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bond.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bond's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bond.options"></a>options</td>
<td align="left">dict of string to string</td>
<td align="left">{'mode': 'balance-rr'}</td>
<td>Dictionary of key/value pairs of bonding options.  Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.9"></a><h3>bridge setting</h3>
<p>Bridging Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.ageing-time"></a>ageing-time</td>
<td align="left">uint32</td>
<td align="left">300</td>
<td>The Ethernet MAC address aging time, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.forward-delay"></a>forward-delay</td>
<td align="left">uint32</td>
<td align="left">15</td>
<td>The Spanning Tree Protocol (STP) forwarding delay, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.group-address"></a>group-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, The MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.group-forward-mask"></a>group-forward-mask</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.hello-time"></a>hello-time</td>
<td align="left">uint32</td>
<td align="left">2</td>
<td>The Spanning Tree Protocol (STP) hello time, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bridge's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.max-age"></a>max-age</td>
<td align="left">uint32</td>
<td align="left">20</td>
<td>The Spanning Tree Protocol (STP) maximum message age, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-hash-max"></a>multicast-hash-max</td>
<td align="left">uint32</td>
<td align="left">4096</td>
<td>Set maximum size of multicast hash table (value must be a power of 2).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-last-member-count"></a>multicast-last-member-count</td>
<td align="left">uint32</td>
<td align="left">2</td>
<td>Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-last-member-interval"></a>multicast-last-member-interval</td>
<td align="left">uint64</td>
<td align="left">100</td>
<td>Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-membership-interval"></a>multicast-membership-interval</td>
<td align="left">uint64</td>
<td align="left">26000</td>
<td>Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-querier"></a>multicast-querier</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-querier-interval"></a>multicast-querier-interval</td>
<td align="left">uint64</td>
<td align="left">25500</td>
<td>If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-query-interval"></a>multicast-query-interval</td>
<td align="left">uint64</td>
<td align="left">12500</td>
<td>Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-query-response-interval"></a>multicast-query-response-interval</td>
<td align="left">uint64</td>
<td align="left">1000</td>
<td>Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-query-use-ifaddr"></a>multicast-query-use-ifaddr</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-router"></a>multicast-router</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-snooping"></a>multicast-snooping</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-startup-query-count"></a>multicast-startup-query-count</td>
<td align="left">uint32</td>
<td align="left">2</td>
<td>Set the number of IGMP queries to send during startup phase.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.multicast-startup-query-interval"></a>multicast-startup-query-interval</td>
<td align="left">uint64</td>
<td align="left">3125</td>
<td>Sets the time (in deciseconds) between queries sent out at startup to determine membership information.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.priority"></a>priority</td>
<td align="left">uint32</td>
<td align="left">32768</td>
<td>Sets the Spanning Tree Protocol (STP) priority for this bridge.  Lower values are "better"; the lowest priority bridge will be elected the root bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.stp"></a>stp</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.vlan-default-pvid"></a>vlan-default-pvid</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.vlan-filtering"></a>vlan-filtering</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Control whether VLAN filtering is enabled on the bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.vlan-protocol"></a>vlan-protocol</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, the protocol used for VLAN filtering. Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.vlan-stats-enabled"></a>vlan-stats-enabled</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Controls whether per-VLAN stats accounting is enabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge.vlans"></a>vlans</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.10"></a><h3>bridge-port setting</h3>
<p>Bridge Port Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge-port.hairpin-mode"></a>hairpin-mode</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge-port.path-cost"></a>path-cost</td>
<td align="left">uint32</td>
<td align="left">100</td>
<td>The Spanning Tree Protocol (STP) port cost for destinations via this port.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge-port.priority"></a>priority</td>
<td align="left">uint32</td>
<td align="left">32</td>
<td>The Spanning Tree Protocol (STP) priority of this bridge port.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.bridge-port.vlans"></a>vlans</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.11"></a><h3>cdma setting</h3>
<p>CDMA-based Mobile Broadband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.cdma.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.cdma.number"></a>number</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.cdma.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.cdma.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.cdma.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.12"></a><h3>dcb setting</h3>
<p>Data Center Bridging Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-fcoe-flags"></a>app-fcoe-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-fcoe-mode"></a>app-fcoe-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-fcoe-priority"></a>app-fcoe-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-fip-flags"></a>app-fip-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-fip-priority"></a>app-fip-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-iscsi-flags"></a>app-iscsi-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.app-iscsi-priority"></a>app-iscsi-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-bandwidth"></a>priority-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-flow-control"></a>priority-flow-control</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-flow-control-flags"></a>priority-flow-control-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-group-bandwidth"></a>priority-group-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-group-flags"></a>priority-group-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-group-id"></a>priority-group-id</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-strict-bandwidth"></a>priority-strict-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.dcb.priority-traffic-class"></a>priority-traffic-class</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.13"></a><h3>dummy setting</h3>
<p>Dummy Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.14"></a><h3>ethtool setting</h3>
<p>Ethtool Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.15"></a><h3>generic setting</h3>
<p>Generic Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.16"></a><h3>gsm setting</h3>
<p>GSM-based Mobile Broadband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.apn"></a>apn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.auto-config"></a>auto-config</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.device-id"></a>device-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.home-only"></a>home-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.network-id"></a>network-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.number"></a>number</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.pin"></a>pin</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.pin-flags"></a>pin-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "pin" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.sim-id"></a>sim-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.sim-operator-id"></a>sim-operator-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.gsm.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.17"></a><h3>infiniband setting</h3>
<p>Infiniband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.infiniband.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.infiniband.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.infiniband.p-key"></a>p-key</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.infiniband.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.infiniband.transport-mode"></a>transport-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.18"></a><h3>ipv4 setting</h3>
<p>IPv4 Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.address-data"></a>address-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv4 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.addresses"></a>addresses</td>
<td align="left">array of array of uint32</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv4 address structures.  Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dad-timeout"></a>dad-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-client-id"></a>dhcp-client-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-fqdn"></a>dhcp-fqdn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-hostname"></a>dhcp-hostname</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-iaid"></a>dhcp-iaid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-reject-servers"></a>dhcp-reject-servers</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-send-hostname"></a>dhcp-send-hostname</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-timeout"></a>dhcp-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dhcp-vendor-class-identifier"></a>dhcp-vendor-class-identifier</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server. Since 1.28</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dns"></a>dns</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>Array of IP addresses of DNS servers (as network-byte-order integers)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dns-options"></a>dns-options</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dns-priority"></a>dns-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>DNS servers priority. The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins.  If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.dns-search"></a>dns-search</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.gateway"></a>gateway</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.ignore-auto-dns"></a>ignore-auto-dns</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.ignore-auto-routes"></a>ignore-auto-routes</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.may-fail"></a>may-fail</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.method"></a>method</td>
<td align="left">string</td>
<td align="left"> </td>
<td>IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.never-default"></a>never-default</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.required-timeout"></a>required-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.route-data"></a>route-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv4 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'next-hop' entry, containing the next hop IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.route-metric"></a>route-metric</td>
<td align="left">int64</td>
<td align="left">-1</td>
<td>The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.route-table"></a>route-table</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv4.routes"></a>routes</td>
<td align="left">array of array of uint32</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.19"></a><h3>ipv6 setting</h3>
<p>IPv6 Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.addr-gen-mode"></a>addr-gen-mode</td>
<td align="left">int32</td>
<td align="left">1</td>
<td>Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. On D-Bus, the absence of an addr-gen-mode setting equals enabling stable-privacy. For keyfile plugin, the absence of the setting on disk means EUI64 so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.address-data"></a>address-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv6 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.addresses"></a>addresses</td>
<td align="left">array of legacy IPv6 address struct (a(ayuay))</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv6 address structures.  Each IPv6 address structure is composed of an IPv6 address, a prefix length (1 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dad-timeout"></a>dad-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-duid"></a>dhcp-duid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-hostname"></a>dhcp-hostname</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-iaid"></a>dhcp-iaid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-reject-servers"></a>dhcp-reject-servers</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-send-hostname"></a>dhcp-send-hostname</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dhcp-timeout"></a>dhcp-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dns"></a>dns</td>
<td align="left">array of byte array</td>
<td align="left"> </td>
<td>Array of IP addresses of DNS servers (in network byte order)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dns-options"></a>dns-options</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dns-priority"></a>dns-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>DNS servers priority. The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins.  If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.dns-search"></a>dns-search</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.gateway"></a>gateway</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.ignore-auto-dns"></a>ignore-auto-dns</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.ignore-auto-routes"></a>ignore-auto-routes</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.ip6-privacy"></a>ip6-privacy</td>
<td align="left">NMSettingIP6ConfigPrivacy (int32)</td>
<td align="left"> </td>
<td>Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.may-fail"></a>may-fail</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.method"></a>method</td>
<td align="left">string</td>
<td align="left"> </td>
<td>IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.never-default"></a>never-default</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.ra-timeout"></a>ra-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.required-timeout"></a>required-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.route-data"></a>route-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv6 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'next-hop' entry, containing the next hop IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.route-metric"></a>route-metric</td>
<td align="left">int64</td>
<td align="left">-1</td>
<td>The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.route-table"></a>route-table</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.routes"></a>routes</td>
<td align="left">array of legacy IPv6 route struct (a(ayuayu))</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv6 address, a prefix length (1 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ipv6.token"></a>token</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.20"></a><h3>ip-tunnel setting</h3>
<p>IP Tunneling Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.encapsulation-limit"></a>encapsulation-limit</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.flags"></a>flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.flow-label"></a>flow-label</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.input-key"></a>input-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.local"></a>local</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.output-key"></a>output-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.path-mtu-discovery"></a>path-mtu-discovery</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether to enable Path MTU Discovery on this tunnel.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.remote"></a>remote</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.tos"></a>tos</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ip-tunnel.ttl"></a>ttl</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.21"></a><h3>macsec setting</h3>
<p>MACSec Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.encrypt"></a>encrypt</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether the transmitted traffic must be encrypted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.mka-cak"></a>mka-cak</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.mka-cak-flags"></a>mka-cak-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "mka-cak" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.mka-ckn"></a>mka-ckn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.mode"></a>mode</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.port"></a>port</td>
<td align="left">int32</td>
<td align="left">1</td>
<td>The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.send-sci"></a>send-sci</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macsec.validation"></a>validation</td>
<td align="left">int32</td>
<td align="left">2</td>
<td>Specifies the validation mode for incoming frames.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.22"></a><h3>macvlan setting</h3>
<p>MAC VLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macvlan.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macvlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macvlan.promiscuous"></a>promiscuous</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether the interface should be put in promiscuous mode.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.macvlan.tap"></a>tap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the interface should be a MACVTAP.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.23"></a><h3>match setting</h3>
<p>Match settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.match.driver"></a>driver</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of driver names to match. Each element is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&amp;', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.match.interface-name"></a>interface-name</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of interface names to match. Each element is a shell wildcard pattern. An element can be prefixed with a pipe symbol (|) or an ampersand (&amp;). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&amp;!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&amp;\\!a" is an mandatory match for literally "!a".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.match.kernel-command-line"></a>kernel-command-line</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported. See NMSettingMatch:interface-name for how special characters '|', '&amp;', '!' and '\\' are used for optional and mandatory matches and inverting the match.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.match.path"></a>path</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier. For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0". The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev"). Each element of the list is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&amp;', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.24"></a><h3>802-11-olpc-mesh setting</h3>
<p>OLPC Wireless Mesh Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-olpc-mesh.channel"></a>channel</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Channel on which the mesh network to join is located.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-olpc-mesh.dhcp-anycast-address"></a>dhcp-anycast-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-olpc-mesh.ssid"></a>ssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>SSID of the mesh network to join.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.25"></a><h3>ovs-bridge setting</h3>
<p>OvsBridge Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-bridge.datapath-type"></a>datapath-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The data path type. One of "system", "netdev" or empty.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-bridge.fail-mode"></a>fail-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The bridge failure mode. One of "secure", "standalone" or empty.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-bridge.mcast-snooping-enable"></a>mcast-snooping-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable multicast snooping.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-bridge.rstp-enable"></a>rstp-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable RSTP.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-bridge.stp-enable"></a>stp-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable STP.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.26"></a><h3>ovs-dpdk setting</h3>
<p>OvsDpdk Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-dpdk.devargs"></a>devargs</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Open vSwitch DPDK device arguments.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-dpdk.n-rxq"></a>n-rxq</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.27"></a><h3>ovs-interface setting</h3>
<p>Open vSwitch Interface Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-interface.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The interface type. Either "internal", "system", "patch", "dpdk", or empty.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.28"></a><h3>ovs-patch setting</h3>
<p>OvsPatch Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-patch.peer"></a>peer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.29"></a><h3>ovs-port setting</h3>
<p>OvsPort Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.bond-downdelay"></a>bond-downdelay</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The time port must be inactive in order to be considered down.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.bond-mode"></a>bond-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.bond-updelay"></a>bond-updelay</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The time port must be active before it starts forwarding traffic.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.lacp"></a>lacp</td>
<td align="left">string</td>
<td align="left"> </td>
<td>LACP mode. One of "active", "off", or "passive".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.tag"></a>tag</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The VLAN tag in the range 0-4095.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-port.vlan-mode"></a>vlan-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.30"></a><h3>ppp setting</h3>
<p>Point-to-Point Protocol Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.baud"></a>baud</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to set the serial port to the specified baudrate.  This value should normally be left as 0 to automatically choose the speed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.crtscts"></a>crtscts</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals.  This value should normally be set to FALSE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.lcp-echo-failure"></a>lcp-echo-failure</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer.  The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.lcp-echo-interval"></a>lcp-echo-interval</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value).  Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.mppe-stateful"></a>mppe-stateful</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.mru"></a>mru</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to request that the peer send packets no larger than the specified size.  If non-zero, the MRU should be between 128 and 16384.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to send packets no larger than the specified size.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.no-vj-comp"></a>no-vj-comp</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, Van Jacobsen TCP header compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.noauth"></a>noauth</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client.  If FALSE, require authentication from the remote side.  In almost all cases, this should be TRUE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.nobsdcomp"></a>nobsdcomp</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, BSD compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.nodeflate"></a>nodeflate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, "deflate" compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.refuse-chap"></a>refuse-chap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the CHAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.refuse-eap"></a>refuse-eap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the EAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.refuse-mschap"></a>refuse-mschap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the MSCHAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.refuse-mschapv2"></a>refuse-mschapv2</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the MSCHAPv2 authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.refuse-pap"></a>refuse-pap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the PAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.require-mppe"></a>require-mppe</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session.  If either 64-bit or 128-bit MPPE is not available the session will fail.  Note that MPPE is not used on mobile broadband connections.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.ppp.require-mppe-128"></a>require-mppe-128</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE.  If 128-bit MPPE is not available the session will fail.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.31"></a><h3>pppoe setting</h3>
<p>PPP-over-Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.pppoe.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.pppoe.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Password used to authenticate with the PPPoE service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.pppoe.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.pppoe.service"></a>service</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.pppoe.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Username used to authenticate with the PPPoE service.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.32"></a><h3>proxy setting</h3>
<p>WWW Proxy Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.proxy.browser-only"></a>browser-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the proxy configuration is for browser only.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.proxy.method"></a>method</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.proxy.pac-script"></a>pac-script</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PAC script for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.proxy.pac-url"></a>pac-url</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PAC URL for obtaining PAC file.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.33"></a><h3>serial setting</h3>
<p>Serial Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.serial.baud"></a>baud</td>
<td align="left">uint32</td>
<td align="left">57600</td>
<td>Speed to use for communication over the serial port.  Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.serial.bits"></a>bits</td>
<td align="left">uint32</td>
<td align="left">8</td>
<td>Byte-width of the serial communication. The 8 in "8n1" for example.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.serial.parity"></a>parity</td>
<td align="left">byte</td>
<td align="left"> </td>
<td>The connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.serial.send-delay"></a>send-delay</td>
<td align="left">uint64</td>
<td align="left">0</td>
<td>Time to delay between each byte sent to the modem, in microseconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.serial.stopbits"></a>stopbits</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.34"></a><h3>sriov setting</h3>
<p>SR-IOV settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.sriov.autoprobe-drivers"></a>autoprobe-drivers</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.sriov.total-vfs"></a>total-vfs</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.sriov.vfs"></a>vfs</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.35"></a><h3>tc setting</h3>
<p>Linux Traffic Control Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tc.qdiscs"></a>qdiscs</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of TC queueing disciplines. When the "tc" setting is present, qdiscs from this property are applied upon activation. If the property is empty, all qdiscs are removed and the device will only have the default qdisc assigned by kernel according to the "net.core.default_qdisc" sysctl. If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs present on the interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tc.tfilters"></a>tfilters</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of TC traffic filters. When the "tc" setting is present, filters from this property are applied upon activation. If the property is empty, NetworkManager removes all the filters. If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.36"></a><h3>team setting</h3>
<p>Teaming Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.config"></a>config</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the team's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.link-watchers"></a>link-watchers</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.mcast-rejoin-count"></a>mcast-rejoin-count</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd mcast_rejoin.count.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.mcast-rejoin-interval"></a>mcast-rejoin-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd mcast_rejoin.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.notify-peers-count"></a>notify-peers-count</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd notify_peers.count.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.notify-peers-interval"></a>notify-peers-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd notify_peers.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner"></a>runner</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-active"></a>runner-active</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Corresponds to the teamd runner.active.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-agg-select-policy"></a>runner-agg-select-policy</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.agg_select_policy.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-fast-rate"></a>runner-fast-rate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Corresponds to the teamd runner.fast_rate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-hwaddr-policy"></a>runner-hwaddr-policy</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.hwaddr_policy.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-min-ports"></a>runner-min-ports</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.min_ports.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-sys-prio"></a>runner-sys-prio</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.sys_prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-tx-balancer"></a>runner-tx-balancer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.tx_balancer.name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-tx-balancer-interval"></a>runner-tx-balancer-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.tx_balancer.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team.runner-tx-hash"></a>runner-tx-hash</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.tx_hash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.37"></a><h3>team-port setting</h3>
<p>Team Port Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.config"></a>config</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.lacp-key"></a>lacp-key</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.lacp_key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.lacp-prio"></a>lacp-prio</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.link-watchers"></a>link-watchers</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.prio"></a>prio</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Corresponds to the teamd ports.PORTIFNAME.prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.queue-id"></a>queue-id</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.team-port.sticky"></a>sticky</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Corresponds to the teamd ports.PORTIFNAME.sticky.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.38"></a><h3>tun setting</h3>
<p>Tunnel Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.group"></a>group</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The group ID which will own the device. If set to NULL everyone will be able to use the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.multi-queue"></a>multi-queue</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.owner"></a>owner</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The user ID which will own the device. If set to NULL everyone will be able to use the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.pi"></a>pi</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.tun.vnet-hdr"></a>vnet-hdr</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.39"></a><h3>user setting</h3>
<p>General User Profile Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.user.data"></a>data</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.40"></a><h3>vlan setting</h3>
<p>VLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.egress-priority-map"></a>egress-priority-map</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.flags"></a>flags</td>
<td align="left">NMVlanFlags (uint32)</td>
<td align="left"> </td>
<td>One or more flags which control the behavior and features of the VLAN interface.  Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol). The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.id"></a>id</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.ingress-priority-map"></a>ingress-priority-map</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the vlan's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.41"></a><h3>vpn setting</h3>
<p>VPN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.data"></a>data</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.persistent"></a>persistent</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.secrets"></a>secrets</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.service-type"></a>service-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.timeout"></a>timeout</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vpn.user-name"></a>user-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.42"></a><h3>vrf setting</h3>
<p>VRF settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.vrf.table"></a>table</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The routing table for this VRF.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.43"></a><h3>vxlan setting</h3>
<p>VXLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.ageing"></a>ageing</td>
<td align="left">uint32</td>
<td align="left">300</td>
<td>Specifies the lifetime in seconds of FDB entries learnt by the kernel.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.destination-port"></a>destination-port</td>
<td align="left">uint32</td>
<td align="left">8472</td>
<td>Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.id"></a>id</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.l2-miss"></a>l2-miss</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether netlink LL ADDR miss notifications are generated.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.l3-miss"></a>l3-miss</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether netlink IP ADDR miss notifications are generated.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.learning"></a>learning</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.limit"></a>limit</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.local"></a>local</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the source IP address to use in outgoing packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.proxy"></a>proxy</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether ARP proxy is turned on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.remote"></a>remote</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.rsc"></a>rsc</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether route short circuit is turned on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.source-port-max"></a>source-port-max</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.source-port-min"></a>source-port-min</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.tos"></a>tos</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the TOS value to use in outgoing packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.vxlan.ttl"></a>ttl</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the time-to-live value to use in outgoing packets.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.44"></a><h3>wifi-p2p setting</h3>
<p>Wi-Fi P2P Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wifi-p2p.peer"></a>peer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The P2P device that should be connected to. Currently, this is the only way to create or join a group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wifi-p2p.wfd-ies"></a>wfd-ies</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>The Wi-Fi Display (WFD) Information Elements (IEs) to set. Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wifi-p2p.wps-method"></a>wps-method</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags indicating which mode of WPS is to be used. There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.45"></a><h3>wimax setting</h3>
<p>WiMax Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wimax.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wimax.network-name"></a>network-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.46"></a><h3>802-3-ethernet setting</h3>
<p>Wired Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.accept-all-mac-addresses"></a>accept-all-mac-addresses</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.assigned-mac-address"></a>assigned-mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.auto-negotiate"></a>auto-negotiate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.cloned-mac-address"></a>cloned-mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>This D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.duplex"></a>duplex</td>
<td align="left">string</td>
<td align="left"> </td>
<td>When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.generate-mac-address-mask"></a>generate-mac-address-mask</td>
<td align="left">string</td>
<td align="left"> </td>
<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.mac-address-blacklist"></a>mac-address-blacklist</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.port"></a>port</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.s390-nettype"></a>s390-nettype</td>
<td align="left">string</td>
<td align="left"> </td>
<td>s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.s390-options"></a>s390-options</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.s390-subchannels"></a>s390-subchannels</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Identifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.speed"></a>speed</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.wake-on-lan"></a>wake-on-lan</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-3-ethernet.wake-on-lan-password"></a>wake-on-lan-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.47"></a><h3>wireguard setting</h3>
<p>WireGuard Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.fwmark"></a>fwmark</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets. Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.ip4-auto-default-route"></a>ip4-auto-default-route</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing". Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route. Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.ip6-auto-default-route"></a>ip6-auto-default-route</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Like ip4-auto-default-route, but for the IPv6 default route.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.listen-port"></a>listen-port</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.peer-routes"></a>peer-routes</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively. Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.peers"></a>peers</td>
<td align="left">array of 'a{sv}'</td>
<td align="left"> </td>
<td>Array of dictionaries for the WireGuard peers.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.private-key"></a>private-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The 256 bit private-key in base64 encoding.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wireguard.private-key-flags"></a>private-key-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "private-key" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.48"></a><h3>802-11-wireless setting</h3>
<p>Wi-Fi Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.ap-isolation"></a>ap-isolation</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode. If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc. If set to NM_TERNARY_FALSE (0), devices can talk to each other. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.assigned-mac-address"></a>assigned-mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.band"></a>band</td>
<td align="left">string</td>
<td align="left"> </td>
<td>802.11 frequency band of the network.  One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11.  This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible.  This setting depends on specific driver capability and may not work with all drivers.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.bssid"></a>bssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, directs the device to only associate with the given access point.  This capability is highly driver dependent and not supported by all devices.  Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.channel"></a>channel</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Wireless channel to use for the Wi-Fi connection.  The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel.  Because channel numbers overlap between bands, this property also requires the "band" property to be set.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.cloned-mac-address"></a>cloned-mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>This D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.generate-mac-address-mask"></a>generate-mac-address-mask</td>
<td align="left">string</td>
<td align="left"> </td>
<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.hidden"></a>hidden</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode. In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution. In AP mode, the created network does not broadcast its SSID. Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.mac-address-blacklist"></a>mac-address-blacklist</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.mac-address-randomization"></a>mac-address-randomization</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). This property is deprecated for 'cloned-mac-address'. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.mode"></a>mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.powersave"></a>powersave</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.rate"></a>rate</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.security"></a>security</td>
<td align="left"> </td>
<td align="left"> </td>
<td>This property is deprecated, but can be set to the value '802-11-wireless-security' when a wireless security setting is also present in the connection dictionary, for compatibility with very old NetworkManager daemons.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.seen-bssids"></a>seen-bssids</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.ssid"></a>ssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>SSID of the Wi-Fi network. Must be specified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.tx-power"></a>tx-power</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless.wake-on-wlan"></a>wake-on-wlan</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.49"></a><h3>802-11-wireless-security setting</h3>
<p>Wi-Fi Security Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.auth-alg"></a>auth-alg</td>
<td align="left">string</td>
<td align="left"> </td>
<td>When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.fils"></a>fils</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.group"></a>group</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.key-mgmt"></a>key-mgmt</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Key management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only). This property must be set for any Wi-Fi connection that uses security.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.leap-password"></a>leap-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.leap-password-flags"></a>leap-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "leap-password" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.leap-username"></a>leap-username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.pairwise"></a>pairwise</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.pmf"></a>pmf</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.proto"></a>proto</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.psk"></a>psk</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.psk-flags"></a>psk-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "psk" property. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key-flags"></a>wep-key-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key-type"></a>wep-key-type</td>
<td align="left">NMWepKeyType (uint32)</td>
<td align="left"> </td>
<td>Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key0"></a>wep-key0</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key1"></a>wep-key1</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key2"></a>wep-key2</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-key3"></a>wep-key3</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wep-tx-keyidx"></a>wep-tx-keyidx</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.802-11-wireless-security.wps-method"></a>wps-method</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags indicating which mode of WPS is to be used if any. There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities. WPS can be disabled by setting this property to a value of 1.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.50"></a><h3>wpan setting</h3>
<p>IEEE 802.15.4 (WPAN) MAC Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wpan.channel"></a>channel</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wpan.mac-address"></a>mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wpan.page"></a>page</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wpan.pan-id"></a>pan-id</td>
<td align="left">uint32</td>
<td align="left">65535</td>
<td>IEEE 802.15.4 Personal Area Network (PAN) identifier.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.wpan.short-address"></a>short-address</td>
<td align="left">uint32</td>
<td align="left">65535</td>
<td>Short IEEE 802.15.4 address to be used within a restricted environment.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.51"></a><h3>bond-port setting</h3>
<p>Bond Port Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.bond-port.queue-id"></a>queue-id</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.52"></a><h3>hostname setting</h3>
<p>Hostname settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.hostname.from-dhcp"></a>from-dhcp</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether the system hostname can be determined from DHCP on this connection. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.hostname.from-dns-lookup"></a>from-dns-lookup</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.hostname.only-from-default"></a>only-from-default</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings-dbus.property.hostname.priority"></a>priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority. If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.53"></a><h3>ovs-external-ids setting</h3>
<p>OVS External IDs Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.ovs-external-ids.data"></a>data</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>A dictionary of key/value pairs with exernal-ids for OVS.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.8.4.54"></a><h3>veth setting</h3>
<p>Veth Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings-dbus.property.veth.peer"></a>peer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>This property specifies the peer interface name of the veth. This property is mandatory.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="secrets-flags"></a><h3>Secret flag types:</h3>
<p>
            Each password or secret property in a setting has an associated <span class="emphasis"><em>flags</em></span> property
            that describes how to handle that secret. The <span class="emphasis"><em>flags</em></span> property is a bitfield
            that contains zero or more of the following values logically OR-ed together.
          </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>0x0 (none) - the system is responsible for providing and storing this secret. This
              may be required so that secrets are already available before the user logs in.
              It also commonly means that the secret will be stored in plain text on disk, accessible
              to root only. For example via the keyfile settings plugin as described in the "PLUGINS" section
              in <a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a>.
              </p></li>
<li class="listitem"><p>0x1 (agent-owned) - 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>0x2 (not-saved) - this secret should not be saved but should be requested from the user
              each time it is required. This flag should be used for One-Time-Pad secrets, PIN codes from hardware tokens,
              or if the user simply does not want to save the secret.</p></li>
<li class="listitem"><p>0x4 (not-required) - 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/NetworkManager/system-connections</code> or distro plugin-specific location</p>
</div>
<div class="refsect1">
<a name="see_also"></a><h2>See Also</h2>
<p><a class="link" href="nm-settings-nmcli.html" title="nm-settings-nmcli"><span class="citerefentry"><span class="refentrytitle">nm-settings-nmcli</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="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>,
        <a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a></p>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.33.1</div>
</body>
</html>
generated by cgit-pink 1.3.0-6-gf8a5 (git 2.35.1) at 2026-08-27 21:29:51 +0000