NMSettingIPConfig — Abstract base class for IPv4 and IPv6 - addressing, routing, and name service properties

--++ @@ -1152,7 +1152,7 @@ - + - + @@ -1194,7 +1194,7 @@ - + @@ -1210,17 +1210,17 @@ - + - + - + - + - + @@ -1256,8 +1256,8 @@

Types and Values

gint	dad-timeout	Read / Write / Construct	Read / Write
@@ -1174,7 +1174,7 @@
gboolean	dhcp-send-hostname	Read / Write / Construct	Read / Write
gint
gint	dns-priority	Read / Write / Construct	Read / Write
GStrv
gboolean	ignore-auto-dns	Read / Write / Construct	Read / Write
gboolean	ignore-auto-routes	Read / Write / Construct	Read / Write
gboolean	may-fail	Read / Write / Construct	Read / Write
@@ -1231,12 +1231,12 @@
gboolean	never-default	Read / Write / Construct	Read / Write
gint64	route-metric	Read / Write / Construct	Read / Write
guint

--++ @@ -2439,7 +2439,7 @@ nm_ip_route_set_dest (dest


  must be a valid address of route
 's family. If you aren't sure you
-have a valid address, use nm_utils_ipaddr_valid() to check it.
+have a valid address, use nm_utils_ipaddr_is_valid() to check it.
 
 Parameters


@@ -5918,10 +5918,10 @@ property.


@@ -6049,7 +6049,7 @@ property.


@@ -6057,11 +6057,11 @@ property.


@@ -6069,7 +6069,7 @@ property.


@@ -6323,11 +6323,11 @@ FQDN.


@@ -6335,7 +6335,7 @@ FQDN.


@@ -6343,8 +6343,8 @@ FQDN.


@@ -6352,10 +6352,10 @@ FQDN.


@@ -6363,9 +6363,9 @@ FQDN.


@@ -6382,6 +6382,7 @@ FQDN.
   “addresses”                GPtrArray *
 Array of IP addresses.
 [type GPtrArray(NMIPAddress)]
+Owner: NMSettingIPConfig
 Flags: Read / Write
 
 
@@ -6395,7 +6396,8 @@ 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Allowed values: [-1,30000]
 Default value: -1
 Since: 1.2
@@ -6408,6 +6410,7 @@ timeout in milliseconds.
 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.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Default value: NULL
 
@@ -6432,6 +6435,7 @@ are set in the request:
 a global default is looked up in NetworkManager configuration. If that value
 is unset or also NM_DHCP_HOSTNAME_FLAG_NONE, then the standard FQDN flags
 described above are sent in the DHCP requests.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Default value: 0
 Since: 1.22
@@ -6452,6 +6456,7 @@ 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.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Default value: NULL
 Since: 1.22
@@ -6465,7 +6470,8 @@ 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: TRUE
 
 
@@ -6476,6 +6482,7 @@ providing a static hostname for the computer.  If the
 globally configured default is used. If still unspecified, a device specific
 timeout is used (usually 45 seconds).
 Set to 2147483647 (MAXINT32) for infinity.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Allowed values: >= 0
 Default value: 0
@@ -6485,6 +6492,7 @@ timeout is used (usually 45 seconds).
 The “dns” property
   “dns”                      GStrv
 Array of IP addresses of DNS servers.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 
 
@@ -6495,6 +6503,7 @@ timeout is used (usually 45 seconds).
 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.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Since: 1.2
 
@@ -6506,7 +6515,7 @@ distinct from an empty list of properties.
 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.
+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.
@@ -6528,7 +6537,8 @@ 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: 0
 Since: 1.4
 
@@ -6540,6 +6550,7 @@ negative DNS priority value, the subdomain is ignored.
 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.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 
 
@@ -6548,6 +6559,7 @@ to complete unqualified host names.
   “gateway”                  gchar *
 The gateway associated with this configuration. This is only meaningful
 if “addresses” is also set.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Default value: NULL
 
@@ -6560,7 +6572,8 @@ if “dns” and “dns-search” properties, if
 any, are used.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: FALSE
 
 
@@ -6570,7 +6583,8 @@ any, are used.
 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: FALSE
 
 
@@ -6584,7 +6598,8 @@ 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: TRUE
 
 
@@ -6606,6 +6621,7 @@ configuration.  The TRUE, this connection will never be the default connection for this
 IP type, meaning it will never be assigned the default route by
 NetworkManager.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Default value: FALSE
 
 
@@ -6633,7 +6650,8 @@ 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.
-Flags: Read / Write / Construct
+Owner: NMSettingIPConfig
+Flags: Read / Write
 Allowed values: [-1,4294967295]
 Default value: -1
 
@@ -6653,6 +6671,7 @@ table (except static routes that explicitly configure a different table). Additi
 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.
+Owner: NMSettingIPConfig
 Flags: Read / Write
 Default value: 0
 Since: 1.10
@@ -6663,6 +6682,7 @@ of NetworkManager.
   “routes”                   GPtrArray *
 Array of IP routes.
 [type GPtrArray(NMIPRoute)]
+Owner: NMSettingIPConfig
 Flags: Read / Write
 
 
@@ -6672,6 +6692,6 @@ of NetworkManager.
 
 
 
-
Generated by GTK-Doc V1.29
+Generated by GTK-Doc V1.32.1
 
 
\ No newline at end of file
-- 
cgit 1.3.0-6-gf8a5

NM_IP_ADDRESS_CMP_FLAGS_WITH_ATTRS	when comparing two addresses, - also consider their attributes. Warning: note that attributes are GVariants - and they don't have a total order. In other words, if the address differs only - by their attributes, the returned compare order is not total. In that case, - the return value merely indicates equality (zero) or inequality. +also consider their attributes. Warning: note that attributes are GVariants +and they don't have a total order. In other words, if the address differs only +by their attributes, the returned compare order is not total. In that case, +the return value merely indicates equality (zero) or inequality.
NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET	whether to allow parsing - IPv4 addresses. +IPv4 addresses.
NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET6	whether to allow parsing - IPv6 addresses. If both `NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET` +IPv6 addresses. If both `NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET` and - `NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET6` +`NM_IP_ROUTING_RULE_AS_STRING_FLAGS_AF_INET6` are unset, it's the same - as setting them both. +as setting them both.
NM_IP_ROUTING_RULE_AS_STRING_FLAGS_VALIDATE	if set, ensure that the - rule verfies or fail. +rule verfies or fail.
NM_DHCP_HOSTNAME_FLAG_NONE	no flag set. The default value from - Networkmanager global configuration is used. If such value is unset - or still zero, the DHCP request will use standard FQDN flags, i.e. - `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` and - `NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED` for IPv4 and - `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` for IPv6. +Networkmanager global configuration is used. If such value is unset +or still zero, the DHCP request will use standard FQDN flags, i.e. +`NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` and +`NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED` for IPv4 and +`NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` for IPv6.
NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE	whether the server should - do the A RR (FQDN-to-address) DNS updates. +do the A RR (FQDN-to-address) DNS updates.
NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED	if set, the FQDN is encoded - using canonical wire format. Otherwise it uses the deprecated - ASCII encoding. This flag is allowed only for DHCPv4. +using canonical wire format. Otherwise it uses the deprecated +ASCII encoding. This flag is allowed only for DHCPv4.
NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE	when not set, request the - server to perform updates (the PTR RR and possibly the A RR - based on the `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` flag). If - this is set, the `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` flag - should be cleared. +server to perform updates (the PTR RR and possibly the A RR +based on the `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` flag). If +this is set, the `NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE` flag +should be cleared.
NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS	when set, no FQDN flags are - sent in the DHCP FQDN option. When cleared and all other FQDN - flags are zero, standard FQDN flags are sent. This flag is - incompatible with any other FQDN flag. +sent in the DHCP FQDN option. When cleared and all other FQDN +flags are zero, standard FQDN flags are sent. This flag is +incompatible with any other FQDN flag.

NMSettingIPConfig

Functions

Types and Values

Parameters

The `“dns”` property