From 70e18d99b8e3e77bb37e218d7ac582130156f8ef Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 25 Jan 2024 09:46:18 +0100 Subject: New upstream version 1.45.90 --- docs/api/html/nm-settings-keyfile.html | 67 +++++++++++++++++++++++++++------- 1 file changed, 54 insertions(+), 13 deletions(-) (limited to 'docs/api/html/nm-settings-keyfile.html') diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 12b405b1..6779fa4c 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -32,7 +32,7 @@

Description

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

@@ -53,21 +53,30 @@

File Format

The keyfile config format is a simple .ini-style - format. It consists of sections (groups) of key-value pairs. Each section - corresponds to a setting name as described in the settings specification - (nm-settings(5)). Each configuration key/value - pair in the section is one of the properties listed in the settings - specification. The majority of properties of the specification is written - in the same format into the keyfile too. However - some values are inconvenient for people to use. These are stored in the - files in more readable ways. These properties are described below. - An example could be IP addresses that are not written as integer arrays, - but more reasonably as "1.2.3.4/12 1.2.3.254". + format. It consists of sections (groups) of key-value pairs. More information of the generic key file format can be found at GLib key file format (Lines beginning with a '#' are comments, lists are separated by character ; etc.).

+

+ Each section corresponds to a setting name as described in the settings + specification (nm-settings-nmcli(5)). Each key/value pair in a + section is one of the properties from the specification. +

+

+ The majority of properties are written in the same format as the + specification into the keyfile. However, some + values are inconvenient for people to use so they are stored in the + keyfile in more readable ways. These properties + that differ from the specification are described below. + An example could be IP addresses that are not written as integer arrays, + but more reasonably as "1.2.3.4/12 1.2.3.254". + Also, some lists of complex values (addresses, routes, routing-rules), + instead of using a semicolon separated list, use one key-value pair + per list element, with the key being the singular of the property name + followed by the numeric index (i.e address1, address2, ...). +

Users can create or modify the keyfile connection files manually, even if that is not the recommended way of managing the profiles. @@ -175,7 +184,7 @@ id=4 There are several exceptions to this rule, mainly for making keyfile syntax easier for humans. The exceptions handled specially by keyfile plugin are listed below. Refer to - nm-settings(5) + nm-settings-nmcli(5) for all available settings and properties and their description.

Name aliases.  @@ -372,6 +381,22 @@ Example: gateway=192.168.100.1 Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16 + +routes (attributes) +route1_options, route2_options, ... +key=val[,key=val...] +Attributes defined for the routes, if any. The supported attributes are explained in ipv4.routes entry in `man nm-settings-nmcli`. + +Example: route1_options=mtu=1000,onlink=true + + +routing-rules +routing-rule1, routing-rule2, ... +routing rule string +Routing rules as defined with `ip rule add`, but with mandatory fixed priority. + +Example: routing-rule1=priority 5 from 192.167.4.0/24 table 45 + @@ -423,6 +448,22 @@ Example: gateway=abbe::1 Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11:5403 + +routes (attributes) +route1_options, route2_options, ... +key=val[,key=val...] +Attributes defined for the routes, if any. The supported attributes are explained in ipv6.routes entry in `man nm-settings-nmcli`. + +Example: route1_options=mtu=1000,onlink=true + + +routing-rules +routing-rule1, routing-rule2, ... +routing rule string +Routing rules as defined with `ip rule add`, but with mandatory fixed priority. + +Example: routing-rule1=priority 5 from 2001:4860:4860::/64 table 45 + @@ -558,7 +599,7 @@ Example: password=Popocatepetl

See Also

-

nm-settings(5), +

nm-settings-nmcli(5), nm-settings-ifcfg-rh(5), NetworkManager(8), NetworkManager.conf(5), -- cgit 1.3.0-6-gf8a5