diff options
Diffstat (limited to 'docs/api/html/settings-ipv4.html')
| -rw-r--r-- | docs/api/html/settings-ipv4.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html index 5f98dd5e..cc51c04f 100644 --- a/docs/api/html/settings-ipv4.html +++ b/docs/api/html/settings-ipv4.html @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.17.2.2.1"></a><p class="title"><b>Table 82. </b></p> +<a name="id-1.3.3.17.2.2.1"></a><p class="title"><b>Table 83. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -62,7 +62,7 @@ <tr> <td><pre class="screen">addresses</pre></td> <td><pre class="screen">array of array of uint32</pre></td> -<td><pre class="screen">[]</pre></td> +<td><pre class="screen"></pre></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> @@ -104,25 +104,25 @@ <tr> <td><pre class="screen">dns</pre></td> <td><pre class="screen">array of uint32</pre></td> -<td><pre class="screen">[]</pre></td> +<td><pre class="screen"></pre></td> <td>Array of IP addresses of DNS servers (as network-byte-order integers)</td> </tr> <tr> <td><pre class="screen">dns-options</pre></td> <td><pre class="screen">array of string</pre></td> -<td><pre class="screen">[]</pre></td> +<td><pre class="screen"></pre></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.</td> </tr> <tr> <td><pre class="screen">dns-priority</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">0</pre></td> -<td>DNS servers priority. The relative priority for DNS servers specified by this setting. A lower value is better (higher priority). Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs 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 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. When multiple devices have configurations with the same priority, the one with an active default route will be preferred. Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used. When using a DNS resolver that supports split-DNS as dns=dnsmasq or dns=systemd-resolved, each connection is used to query domains in its search list. 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 highest priority (lowest numerical value) wins. If a connection specifies a domain which is subdomain of another domain with a negative DNS priority value, the subdomain is ignored.</td> +<td>DNS servers priority. The relative priority for DNS servers specified by this setting. A lower value is better (higher priority). Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs 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 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. When multiple devices have configurations with the same priority, the one with an active default route will be preferred. Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used. When using a DNS resolver that supports Conditional Forwarding as dns=dnsmasq or dns=systemd-resolved, each connection is used to query domains in its search list. 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 highest priority (lowest numerical value) wins. If a connection specifies a domain which is subdomain of another domain with a negative DNS priority value, the subdomain is ignored.</td> </tr> <tr> <td><pre class="screen">dns-search</pre></td> <td><pre class="screen">array of string</pre></td> -<td><pre class="screen">[]</pre></td> +<td><pre class="screen"></pre></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.</td> </tr> <tr> @@ -153,7 +153,7 @@ <td><pre class="screen">method</pre></td> <td><pre class="screen">string</pre></td> <td><pre class="screen"></pre></td> -<td>IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "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> +<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><pre class="screen">never-default</pre></td> @@ -182,7 +182,7 @@ <tr> <td><pre class="screen">routes</pre></td> <td><pre class="screen">array of array of uint32</pre></td> -<td><pre class="screen">[]</pre></td> +<td><pre class="screen"></pre></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> |