Browsing Russian translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Russian guidelines.
110 of 14 results
126.
Do you want to provide it? %s
Do you want to provide them? %s
(no translation yet)
Translated by Maxim Taranov
Reviewed by Maxim Taranov
(no translation yet)
Translated by Maxim Taranov
Reviewed by Maxim Taranov
(no translation yet)
Translated by Maxim Taranov
Reviewed by Maxim Taranov
Located in ../clients/cli/connections.c:4647
823.
The WireGuard config file must be a valid interface name followed by ".conf"
(no translation yet)
Located in ../clients/common/nm-vpn-helpers.c:377
852.
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
972.
This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The '$' character is treated special to perform dynamic substitutions at runtime. Currently supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:152
976.
Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. Note that this property only works together with NMSettingConnection:interface-name to identify the device that will be waited for. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:156
1027.
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.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:212 ../clients/common/settings-docs.h.in:232
1102.
The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface also when it is zero. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:313
1162.
The P2P device that should be connected to. Currently this is the only way to create or join a group.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:374
1167.
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. Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:379
1168.
Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, a unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto. Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips.
(no translation yet)
Located in ../clients/common/settings-docs.h.in:380
110 of 14 results

This translation is managed by Russian Ubuntu Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: #D|zeR by RSIS, Al Tarakanoff, Aleksey Kabanov, Alex Lutz, Alexander Matveev, Alexey 'huNTer' Kolosov, Alexey Kotov, Andrey S. Bobryshev, Andy Lemz, Anton Patsev, Artem Popov, Copied by Zanata, Dmitry Shachnev, Dr Gregory House, Eugene Roskin, Evgeny, Ivlev Denis, JTux, Leonid Kanter, Leonid Ryzhov, Mathieu Trudel-Lapierre, Maxim Taranov, Melman, Michael Rybinsky, Nick Lavlinsky, Olcha Artna, Oleg Lyash, Roman Mindlin, Sergey Sedov, Stalker, Stas Solovey, TuzelKO, Xamuh, Yuri Kozlov, Yuri Myasoedov, Yuri Myasoedov, iseedeadcode, vanya, zamazan4ik, Глория Хрусталёва, Данил Тютюник, Устин, ☠Jay ZDLin☠.