|
262.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/cli/devices.c:693
|
|
645.
|
|
|
the property doesn't contain interface name '%s '
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/nm-meta-setting-desc.c:3752
|
|
649.
|
|
|
the property doesn't contain vf with index %u
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/nm-meta-setting-desc.c:3927
|
|
879.
|
|
|
Key management used for the connection. One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa-none" (Ad-Hoc WPA-PSK), "wpa-psk" (infrastructure WPA-PSK), "sae" (SAE) or "wpa-eap" (WPA-Enterprise). This property must be set for any Wi-Fi connection that uses security.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:27
|
|
949.
|
|
|
When a value grater 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.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:99
|
|
1049.
|
|
|
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.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:207
../clients/common/settings-docs.h.in:227
|
|
1055.
|
|
|
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.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:213
../clients/common/settings-docs.h.in:234
|
|
1132.
|
|
|
Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random". When setting the runner, all the properties specific to the runner will be reset to the default value; all the properties specific to other runners will be set to an empty value (or if not possible to a default value).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:309
|
|
1187.
|
|
|
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.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../clients/common/settings-docs.h.in:365
|
|
1521.
|
|
|
key '%s .%s ' is not not a valid 256 bit key in base64 encoding
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../libnm-core/nm-keyfile.c:2940
|