From e74c568b07b50b97873fb4ee1d776dedefbd54d6 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 1 Oct 2021 23:05:04 +0200 Subject: New upstream version 1.32.12 --- docs/libnm/html/NMSettingIP4Config.html | 122 ++------------------------------ 1 file changed, 5 insertions(+), 117 deletions(-) (limited to 'docs/libnm/html/NMSettingIP4Config.html') diff --git a/docs/libnm/html/NMSettingIP4Config.html b/docs/libnm/html/NMSettingIP4Config.html index 328d05b2..6c0038ff 100644 --- a/docs/libnm/html/NMSettingIP4Config.html +++ b/docs/libnm/html/NMSettingIP4Config.html @@ -15,9 +15,7 @@ @@ -74,36 +72,6 @@
-

Properties

-
----- - - - - - - - - - - - - - - - - - -
-char *dhcp-client-idRead / Write
-char *dhcp-fqdnRead / Write
-char *dhcp-vendor-class-identifierRead / Write
-
-

Types and Values

@@ -147,28 +115,16 @@ - - - -
#define NM_SETTING_IP4_CONFIG_METHOD_DISABLED
 NMSettingIP4Config
-

Object Hierarchy

-
    GObject
-    ╰── NMSetting
-        ╰── NMSettingIPConfig
-            ╰── NMSettingIP4Config
-
-
-

Description

The NMSettingIP4Config object is a NMSetting subclass that describes properties related to IPv4 addressing, routing, and Domain Name Service.

NMSettingIP4Config has few properties or methods of its own; it inherits almost everything from NMSettingIPConfig.

-

NetworkManager supports 5 values for the “method” property +

NetworkManager supports 5 values for the “method” property for IPv4. If "auto" is specified then the appropriate automatic method (DHCP, PPP, etc) is used for the interface and most other properties can be left unset. If "link-local" is specified, then a link-local address in the @@ -200,7 +156,7 @@ nm_setting_ip4_config_new (voidconst char * nm_setting_ip4_config_get_dhcp_client_id (NMSettingIP4Config *setting); -

Returns the value contained in the “dhcp-client-id” +

Returns the value contained in the “dhcp-client-id” property.

Parameters

@@ -228,7 +184,7 @@ addresses via DHCP.

nm_setting_ip4_config_get_dhcp_fqdn ()

const char *
 nm_setting_ip4_config_get_dhcp_fqdn (NMSettingIP4Config *setting);
-

Returns the value contained in the “dhcp-fqdn” +

Returns the value contained in the “dhcp-fqdn” property.

Parameters

@@ -257,7 +213,7 @@ property.

const char *
 nm_setting_ip4_config_get_dhcp_vendor_class_identifier
                                (NMSettingIP4Config *setting);
-

Returns the value contained in the “dhcp_vendor_class_identifier” +

Returns the value contained in the “dhcp_vendor_class_identifier” property.

Parameters

@@ -350,74 +306,6 @@ through that interface to the default network.

This connection does not use or require IPv4 address and it should be disabled.

-
-
-

NMSettingIP4Config

-
typedef struct _NMSettingIP4Config NMSettingIP4Config;
-

IPv4 Settings

-
-
-
-

Property Details

-
-

The “dhcp-client-id” property

-
  “dhcp-client-id”           char *
-

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.

-

Owner: NMSettingIP4Config

-

Flags: Read / Write

-

Default value: NULL

-
-
-
-

The “dhcp-fqdn” property

-
  “dhcp-fqdn”                char *
-

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.

-

Owner: NMSettingIP4Config

-

Flags: Read / Write

-

Default value: NULL

-

Since: 1.2

-
-
-
-

The “dhcp-vendor-class-identifier” property

-
  “dhcp-vendor-class-identifier” char *
-

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

-

Owner: NMSettingIP4Config

-

Flags: Read / Write

-

Default value: NULL

-