diff options
| author | rebortg <github@ghlr.de> | 2022-10-24 21:49:31 +0200 |
|---|---|---|
| committer | rebortg <github@ghlr.de> | 2022-10-24 21:49:31 +0200 |
| commit | b18aa2f9d853b92e193269a53c1b00c9f48dd73f (patch) | |
| tree | f5b33453ef9ffcbe6567ce9220a785fdc8236220 /docs/_locale | |
| parent | 99ccd5cd0e0ac2efdc50f3eda88744601a0a996a (diff) | |
| download | vyos-documentation-b18aa2f9d853b92e193269a53c1b00c9f48dd73f.tar.gz vyos-documentation-b18aa2f9d853b92e193269a53c1b00c9f48dd73f.zip | |
migrate to new transifex client
Diffstat (limited to 'docs/_locale')
162 files changed, 0 insertions, 52513 deletions
diff --git a/docs/_locale/de_DE/LC_MESSAGES/404.po b/docs/_locale/de_DE/LC_MESSAGES/404.po deleted file mode 100644 index 9a5825ea..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/404.po +++ /dev/null @@ -1,40 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:56+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../404.rst:4 42917a064811496db687a7fa03efffaf -msgid "Page Not Found" -msgstr "" - -#: ../../404.rst:6 d0620a8760284f7c80177078dc193317 -msgid "" -"Sorry, We could not find a page. Try using the search box or go to the " -"release homepage:" -msgstr "" - -#: ../../404.rst:9 924fb0d486e14d928a5922a0507c2aaa -msgid "`1.2.x (crux) <https://docs.vyos.io/en/crux/>`_" -msgstr "" - -#: ../../404.rst:10 0aeab8255f2f4d468d43948024b1b0d8 -msgid "`1.3.x (equuleus) <https://docs.vyos.io/en/equuleus/>`_" -msgstr "" - -#: ../../404.rst:11 08ef1ea3d1de421baaa3d48442a83d88 -msgid "`rolling release (sagitta) <https://docs.vyos.io/en/latest/>`_" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/cloud-init.po b/docs/_locale/de_DE/LC_MESSAGES/automation/cloud-init.po deleted file mode 100644 index f0b41254..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/cloud-init.po +++ /dev/null @@ -1,492 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/cloud-init.rst:7 5a1e58e08ed74c5fa7cc0aeccc824ddb -msgid "VyOS cloud-init" -msgstr "" - -#: ../../automation/cloud-init.rst:9 b57440a9bce34a6eb76d28e83f310660 -msgid "" -"Cloud and virtualized instances of VyOS are initialized using the industry-" -"standard cloud-init. Via cloud-init, the system performs tasks such as " -"injecting SSH keys and configuring the network. In addition, the user can " -"supply a custom configuration at the time of instance launch." -msgstr "" - -#: ../../automation/cloud-init.rst:16 c7b2cea0881242eba6163a4d117bed1f -msgid "Config Sources" -msgstr "" - -#: ../../automation/cloud-init.rst:18 7941c60fef0341a5a744caf4634a2b5b -msgid "VyOS support three types of config sources." -msgstr "" - -#: ../../automation/cloud-init.rst:20 4f51359757f4479eae57bfea31130721 -msgid "" -"Metadata - Metadata is sourced by the cloud platform or hypervisor. In some " -"clouds, there is implemented as an HTTP endpoint at " -"``http://169.254.169.254``." -msgstr "" - -#: ../../automation/cloud-init.rst:24 4d39a74fa33b4d599ec13cc1f5bed499 -msgid "" -"Network configuration - This config source informs the system about the " -"network settings like IP addresses, routes, DNS. Available only in several " -"cloud and virtualization platforms." -msgstr "" - -#: ../../automation/cloud-init.rst:28 f49f055ec7354d9a9ddeba37cafd74f3 -msgid "" -"User-data - User-data is specified by the user. This config source offers " -"the ability to insert any CLI configuration commands into the configuration " -"before the first boot." -msgstr "" - -#: ../../automation/cloud-init.rst:34 c92475e7b9784db89a83843b7355825f -msgid "User-data" -msgstr "" - -#: ../../automation/cloud-init.rst:36 afb22e05c7614bb887894f6913f59417 -msgid "" -"Major cloud providers offer a means of providing user-data at the time of " -"instance launch. It can be provided as plain text or as base64-encoded text," -" depending on cloud provider. Also, it can be compressed using gzip, which " -"makes sense with a long configuration commands list, because of the hard " -"limit to ~16384 bytes for the whole user-data." -msgstr "" - -#: ../../automation/cloud-init.rst:42 1ade5247a27141fba6ebc4cffca0dbd4 -msgid "" -"The easiest way to configure the system via user-data is the Cloud-config " -"syntax described below." -msgstr "" - -#: ../../automation/cloud-init.rst:47 260de9e525f9497294684996454457c9 -msgid "Cloud-config modules" -msgstr "" - -#: ../../automation/cloud-init.rst:49 440c4a2d60674ac783a105eb4e25baca -msgid "In VyOS, by default, enables only two modules:" -msgstr "" - -#: ../../automation/cloud-init.rst:51 e934c507f557401cadb02574e8ef8343 -msgid "" -"``write_files`` - this module allows to insert any files into the filesystem" -" before the first boot, for example, pre-generated encryption keys, " -"certificates, or even a whole ``config.boot`` file. The format is described " -"in the cloudinit documentation `Cloud-init-write_files`_." -msgstr "" - -#: ../../automation/cloud-init.rst:55 1cf4edc857344fb693602873fc191d5f -msgid "" -"``vyos_userdata`` - the module accepts a list of CLI configuration commands " -"in a ``vyos_config_commands`` section, which gives an easy way to configure " -"the system during deployment." -msgstr "" - -#: ../../automation/cloud-init.rst:61 154581d4c6864f9a95196e246f6ef186 -msgid "cloud-config file format" -msgstr "" - -#: ../../automation/cloud-init.rst:63 4c286e38f4ef4732bb47d89e004a30b8 -msgid "" -"A cloud-config document is written in YAML. The file must begin with " -"``#cloud-config`` line. The only supported top-level keys are " -"``vyos_config_commands`` and ``write_files``. The use of these keys is " -"described in the following two sections." -msgstr "" - -#: ../../automation/cloud-init.rst:71 df934b7aa27d4f61b38aa39a09c223a3 -msgid "Initial Configuration" -msgstr "" - -#: ../../automation/cloud-init.rst:74 073a09a0edfd492f8a660b0c56ed4d38 -msgid "" -"The key used to designate a VyOS configuration is ``vyos_config_commands``. " -"What follows is VyOS configuration using the \"set-style\" syntax. Both " -"\"set\" and \"delete\" commands are supported." -msgstr "" - -#: ../../automation/cloud-init.rst:78 610d037891dc4c29a9cf61de1f97f081 -msgid "Commands requirements:" -msgstr "" - -#: ../../automation/cloud-init.rst:80 0d7a52496c8f433f87e8384f46102b96 -msgid "One command per line." -msgstr "" - -#: ../../automation/cloud-init.rst:81 f5ddeb42c3ca454caacc06f66342ae43 -msgid "If command ends in a value, it must be inside single quotes." -msgstr "" - -#: ../../automation/cloud-init.rst:82 d695ba3d75674b4ebe336d0ba024fe4c -msgid "A single-quote symbol is not allowed inside command or value." -msgstr "" - -#: ../../automation/cloud-init.rst:84 3b81fae7e5e34921b7d5729c1e1443e2 -msgid "" -"The commands list produced by the ``show configuration commands`` command on" -" a VyOS router should comply with all the requirements, so it is easy to get" -" a proper commands list by copying it from another router." -msgstr "" - -#: ../../automation/cloud-init.rst:88 b66086100a5c4d7e91fe9df3cdba22a0 -msgid "" -"The configuration specified in the cloud-config document overwrites default " -"configuration values and values configured via Metadata." -msgstr "" - -#: ../../automation/cloud-init.rst:91 cf8392222e2e4aada3e83cf24a334711 -msgid "" -"Here is an example cloud-config that appends configuration at the time of " -"first boot." -msgstr "" - -#: ../../automation/cloud-init.rst:107 7ac4e2c2b13b4bcba5cf96245596895c -msgid "System Defaults/Fallbacks" -msgstr "" - -#: ../../automation/cloud-init.rst:109 12a9a939ac2e4c9db7db16e5b08344bd -msgid "These are the VyOS defaults and fallbacks." -msgstr "" - -#: ../../automation/cloud-init.rst:111 bf96658e8ac746a08f667ba36b36c9b0 -msgid "SSH is configured on port 22." -msgstr "" - -#: ../../automation/cloud-init.rst:112 03570fecffce4ac8a69c7fe9adb37914 -msgid "``vyos``/``vyos`` credentials if no others specified by data source." -msgstr "" - -#: ../../automation/cloud-init.rst:113 c8d8dd97c06c4b78ac9caa9b4761649c -msgid "" -"DHCP on first Ethernet interface if no network configuration is provided." -msgstr "" - -#: ../../automation/cloud-init.rst:115 2e145b1477e34669bec37bdadc3c8154 -msgid "All of these can be overridden using the configuration in user-data." -msgstr "" - -#: ../../automation/cloud-init.rst:120 845892930f3a4465b390fce4f6fd701f -msgid "Command Execution at Initial Boot" -msgstr "" - -#: ../../automation/cloud-init.rst:122 4d20c2b6fed844e5997c822112a4f96f -msgid "" -"VyOS supports the execution of operational commands and linux commands at " -"initial boot. This is accomplished using ``write_files`` to certain files in" -" the /opt/vyatta/etc/config/scripts directory. Commands specified in " -"opt/vyatta/etc/config/scripts/vyos-preconfig-bootup.script are executed " -"prior to configuration. The /opt/vyatta/etc/config/scripts/vyos-postconfig-" -"bootup.script file contains commands to be executed after configuration. In " -"both cases, commands are executed as the root user." -msgstr "" - -#: ../../automation/cloud-init.rst:131 aae55067a9ac4887a911b230015ec5f9 -msgid "" -"Note that the /opt/vyatta/etc/config is used instead of the /config/scripts " -"directory referenced in the :ref:`command-scripting` section of the " -"documentation because the /config/script directory isn't mounted when the " -"``write_files`` module executes." -msgstr "" - -#: ../../automation/cloud-init.rst:136 3ad52c113fd44f5f9712b1e3d3fde0a7 -msgid "" -"The following example shows how to execute commands after the initial " -"configuration." -msgstr "" - -#: ../../automation/cloud-init.rst:153 b0ea9945f0ff4d1c9cb07531ccb0a081 -msgid "" -"If you need to gather information from linux commands to configure VyOS, you" -" can execute commands and then configure VyOS in the same script." -msgstr "" - -#: ../../automation/cloud-init.rst:156 59beca45859f453399c465e3502cd4b3 -msgid "" -"The following example sets the hostname based on the instance identifier " -"obtained from the EC2 metadata service." -msgstr "" - -#: ../../automation/cloud-init.rst:178 643d992607ac4362ad1a396e3837065a -msgid "NoCloud" -msgstr "" - -#: ../../automation/cloud-init.rst:180 f545509ef9fb488e8523799bad5c66a9 -msgid "" -"Injecting configuration data is not limited to cloud platforms. Users can " -"employ the NoCloud data source to inject user-data and meta-data on " -"virtualization platforms such as VMware, Hyper-V and KVM." -msgstr "" - -#: ../../automation/cloud-init.rst:184 2b2d4c6f2d214088b78d1f6ee5f676a8 -msgid "" -"While other methods exist, the most straightforward method for using the " -"NoCloud data source is creating a seed ISO and attaching it to the virtual " -"machine as a CD drive. The volume must be formatted as a vfat or ISO 9660 " -"file system with the label \"cidata\" or \"CIDATA\"." -msgstr "" - -#: ../../automation/cloud-init.rst:189 dc4845c5e4444218935c1b2262b6731b -msgid "" -"Create text files named user-data and meta-data. On linux-based systems, the" -" mkisofs utility can be used to create the seed ISO. The following syntax " -"will add these files to the ISO 9660 file system." -msgstr "" - -#: ../../automation/cloud-init.rst:197 1ed8e489b45d4d9a87524b1b4c089cd3 -msgid "" -"The seed.iso file can be attached to the virtual machine. As an example, the" -" method with KVM to attach the ISO as a CD drive follows." -msgstr "" - -#: ../../automation/cloud-init.rst:217 7a8f0a5f0bde43f197d6eb89b0cdc29f -msgid "" -"For more information on the NoCloud data source, visit its `page " -"<https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html>`_" -" in the cloud-init documentation." -msgstr "" - -#: ../../automation/cloud-init.rst:223 6c50539fd8294145bf4cca4981db28af -msgid "Troubleshooting" -msgstr "" - -#: ../../automation/cloud-init.rst:225 1608b5a68a754edfa27acafa62057558 -msgid "" -"If you encounter problems, verify that the cloud-config document contains " -"valid YAML. Online resources such as https://yamlvalidator.com/ provide a " -"simple tool for validating YAML." -msgstr "" - -#: ../../automation/cloud-init.rst:229 a3db85f1710145fdbd8c2181d1ada0a4 -msgid "" -"cloud-init logs to /var/log/cloud-init.log. This file can be helpful in " -"determining why the configuration varies from what you expect. You can fetch" -" the most important data filtering output for ``vyos`` keyword:" -msgstr "" - -#: ../../automation/cloud-init.rst:239 60f249a2e8a64bc1a9ab81609926604c -msgid "Cloud-init on Proxmox" -msgstr "" - -#: ../../automation/cloud-init.rst:241 a94fe08b104d4a45add735d528466212 -msgid "" -"Before starting, please refer to cloud-init `network-config-docs`_ in order " -"to know how to import user and network configurations." -msgstr "" - -#: ../../automation/cloud-init.rst:244 f3ad6b56da1048179d4587c5ac5d09e9 -msgid "Most important keys that needs to be considered:" -msgstr "" - -#: ../../automation/cloud-init.rst:246 f89e13c7ddfe4eb1ae24b64b7abe1c73 -msgid "VyOS configuration commands are defined in user-data file." -msgstr "" - -#: ../../automation/cloud-init.rst:248 27a35953378648f1966f05482a9329ef -msgid "Networking configurations shouldn't be passed in user-data file." -msgstr "" - -#: ../../automation/cloud-init.rst:250 ea015f712bac4a808fa1899062108879 -msgid "" -"If no networking configuration is provided, then dhcp client is going to be " -"enabled on first interface. Bare in mind that this configuration will be " -"inyected at an OS level, so don't expect to find dhcp client configuration " -"on vyos cli. Because of this behavior, in next example lab we will disable " -"dhcp-client configuration on eth0." -msgstr "" - -#: ../../automation/cloud-init.rst:256 259dd768212147ef9ad021440aaa4f09 -msgid "Also, this lab considers:" -msgstr "" - -#: ../../automation/cloud-init.rst:258 a85277b4738c471abd72d79b2639b35b -msgid "Proxmox IP address: **192.168.0.253/24**" -msgstr "" - -#: ../../automation/cloud-init.rst:260 c63831f9ddf14a8db29f00fea590c64c -msgid "" -"Storaged used: volume local, which is mounted on directory **/var/lib/vz**, " -"and contains all type of content, including snippets." -msgstr "" - -#: ../../automation/cloud-init.rst:263 3ed9315ed4f64b328bbf4f2e147340cf -msgid "" -"Remove default dhcp client on first interface, and load other configuration " -"during first boot, using cloud-init." -msgstr "" - -#: ../../automation/cloud-init.rst:268 cf856c6413e34601a093a2239e3df64c -msgid "Generate qcow image" -msgstr "" - -#: ../../automation/cloud-init.rst:270 894f4769e6324b32a683c0510fcfcd9a -msgid "" -"A VyOS qcow image with cloud-init options is needed. This can be obtained " -"using `vyos-vm-images`_ repo. After clonning the repo, edit the file " -"**qemu.yml** and comment the **download-iso** role." -msgstr "" - -#: ../../automation/cloud-init.rst:274 df71fe2982564599a5f44ba3a55f9794 -msgid "" -"In this lab, we are using 1.3.0 VyOS version and setting a disk of 10G. " -"Download VyOS .iso file and save it as ``/tmp/vyos.iso``. Command used for " -"generating qcow image:" -msgstr "" - -#: ../../automation/cloud-init.rst:284 3a763bbe4f6e47d4bc74ea16091b0544 -msgid "" -"File generated with previous command: ``/tmp/vyos-1.3.0-cloud-" -"init-10G-qemu.qcow2``" -msgstr "" - -#: ../../automation/cloud-init.rst:287 686677d85d264f1aad4df8ef4e3901b6 -msgid "Now, that file needs to be copied to proxmox server:" -msgstr "" - -#: ../../automation/cloud-init.rst:296 d0a265be824942f3bf27e86483b22443 -msgid "Prepare cloud-init files" -msgstr "" - -#: ../../automation/cloud-init.rst:298 16b77d3ee3804a148c8809bde254fc67 -msgid "In Proxmox server three files are going to be used for this setup:" -msgstr "" - -#: ../../automation/cloud-init.rst:300 3cff48ac8ac246aa9e69c66df565560c -msgid "" -"**network-config**: file that will indicate to avoid dhcp client on first " -"interface." -msgstr "" - -#: ../../automation/cloud-init.rst:303 ff9c9021dbf64b50809bb79aade0a92b -msgid "**user-data**: includes vyos-commands." -msgstr "" - -#: ../../automation/cloud-init.rst:305 f7b8139b2dc74420ab638a7c84859d6f -msgid "**meta-data**: empty file (required)." -msgstr "" - -#: ../../automation/cloud-init.rst:307 2f5769aa6f34455c89561c148233c3c6 -msgid "" -"In this lab, all files are located in ``/tmp/``. So, before going on, lets " -"move to that directory:" -msgstr "" - -#: ../../automation/cloud-init.rst:314 0287930f880d41d3adbc9d8fe5b6df1a -msgid "" -"**user-data** file must start with ``#cloud-config`` and contains vyos-" -"commands. For example:" -msgstr "" - -#: ../../automation/cloud-init.rst:333 b90181ca013447bab6244341bdc266ea -msgid "" -"**network-config** file only has configuration that disables the automatic " -"dhcp client on first interface." -msgstr "" - -#: ../../automation/cloud-init.rst:337 1db23d5d94754a2ab1081e30d3fe0da5 -msgid "Content of network-config file:" -msgstr "" - -#: ../../automation/cloud-init.rst:347 877a675380044cd586ebb0e05e4c531b -msgid "Finaly, file **meta-data** has no content, but it's required." -msgstr "" - -#: ../../automation/cloud-init.rst:351 8864c9d6648a40ac8dd41157ba845afb -msgid "Create seed.iso" -msgstr "" - -#: ../../automation/cloud-init.rst:353 1adab209dbb2495f83f9808c51ac9749 -msgid "" -"Once the three files were created, it's time to generate the ``seed.iso`` " -"image, which needs to be mounted to the new VM as a cd." -msgstr "" - -#: ../../automation/cloud-init.rst:356 d41701cb8aa3407e86af0b16966aea6c -msgid "Command for generating ``seed.iso``" -msgstr "" - -#: ../../automation/cloud-init.rst:363 46c3c877315148b3accab6ededd0c84c -msgid "" -"**NOTE**: be carefull while copying and pasting previous commands. Doble " -"quotes may need to be corrected." -msgstr "" - -#: ../../automation/cloud-init.rst:368 863a7a3b62c64d1cbdad92442a0386c5 -msgid "Creating the VM" -msgstr "" - -#: ../../automation/cloud-init.rst:370 3cdde5f24eb24df1907c63206757c453 -msgid "" -"Notes for this particular example, that may need to be modified in other " -"setups:" -msgstr "" - -#: ../../automation/cloud-init.rst:373 f1e258960ed34b2aa3b5ee9a663162ca -msgid "VM ID: in this example, VM ID used is 555." -msgstr "" - -#: ../../automation/cloud-init.rst:375 5ff861cc0d1c44be86c4bd9f67b4aff7 -msgid "VM Storage: ``local`` volume is used." -msgstr "" - -#: ../../automation/cloud-init.rst:377 60f1e819fadc486bbebfb084047c88cb -msgid "" -"ISO files storage: ``local`` volume is used for ``.iso`` file storage. In " -"this scenario ``local`` volume type is set to **directory**, abd attached to" -" ``/var/lib/vz``." -msgstr "" - -#: ../../automation/cloud-init.rst:381 11865be2e655411d870bea8c7e9b8acb -msgid "VM Resources: these parameters can be modified as needed." -msgstr "" - -#: ../../automation/cloud-init.rst:383 091d1eb812234a78a136ead5906ecdbf -msgid "" -"``seed.iso`` was previously created in directory ``/tmp/``. It's necessary " -"to move it to ``/var/lib/vz/template/iso``" -msgstr "" - -#: ../../automation/cloud-init.rst:390 f22c998b66c04304b73fc1dcdabc7ec0 -msgid "On proxmox server:" -msgstr "" - -#: ../../automation/cloud-init.rst:409 3c984167cf6b4083ba0310a3e8d0075f -msgid "Power on VM and verifications" -msgstr "" - -#: ../../automation/cloud-init.rst:411 182c863cbaaf422493b001eadc5b13a5 -msgid "From cli or GUI, power on VM, and after it boots, verify configuration" -msgstr "" - -#: ../../automation/cloud-init.rst:416 df2b02863d1847d386567809945976c9 -msgid "References" -msgstr "" - -#: ../../automation/cloud-init.rst:418 f9149026e8564f5aa658f00087d0c282 -msgid "VyOS `cloud-init-docs`_." -msgstr "" - -#: ../../automation/cloud-init.rst:420 9a146991908c4a6e8371986ba2e4d0c6 -msgid "Cloud-init `network-config-docs`_." -msgstr "" - -#: ../../automation/cloud-init.rst:422 32c72da7713245e293b1a7d0d4547827 -msgid "Proxmox `Cloud-init-Support`_." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/command-scripting.po b/docs/_locale/de_DE/LC_MESSAGES/automation/command-scripting.po deleted file mode 100644 index 7ec34bd8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/command-scripting.po +++ /dev/null @@ -1,194 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/command-scripting.rst:6 2c8c2f645849459f89dc1a54980764dc -msgid "Command Scripting" -msgstr "" - -#: ../../automation/command-scripting.rst:8 a81211b38eec4d71870e462e6651c57f -msgid "" -"VyOS supports executing configuration and operational commands non-" -"interactively from shell scripts." -msgstr "" - -#: ../../automation/command-scripting.rst:11 4cc198a3f7d24c02a154413cabfbcafb -msgid "" -"To include VyOS specific functions and aliases you need to ``source " -"/opt/vyatta/etc/functions/script-template`` files at the top of your script." -msgstr "" - -#: ../../automation/command-scripting.rst:21 195e544d2ec04affbf7cb5f96643fc40 -msgid "Run configuration commands" -msgstr "" - -#: ../../automation/command-scripting.rst:23 17f56fe10e0142e89dae23bf4372c53b -msgid "" -"Configuration commands are executed just like from a normal config session. " -"For example, if you want to disable a BGP peer on VRRP transition to backup:" -msgstr "" - -#: ../../automation/command-scripting.rst:37 be8951ac72144fdf9b0ae534c7040f51 -msgid "Run operational commands" -msgstr "" - -#: ../../automation/command-scripting.rst:39 8c78190b1a15458d9a5f0b0327b58972 -msgid "" -"Unlike a normal configuration session, all operational commands must be " -"prepended with ``run``, even if you haven't created a session with " -"configure." -msgstr "" - -#: ../../automation/command-scripting.rst:50 baf374a95fce4d9a81e78b279342a2ed -msgid "Run commands remotely" -msgstr "" - -#: ../../automation/command-scripting.rst:52 421af86bb192480ba3dad43c93bd835d -msgid "" -"Sometimes you simply wan't to execute a bunch of op-mode commands via SSH on" -" a remote VyOS system." -msgstr "" - -#: ../../automation/command-scripting.rst:63 db1bcedc53ff4ba8adc0f6efcbc8c6af -msgid "Will return:" -msgstr "" - -#: ../../automation/command-scripting.rst:77 cbbe6f88dc8d4e009c1e44918d8be89f -msgid "Other script languages" -msgstr "" - -#: ../../automation/command-scripting.rst:79 46162a174314441ab91c18aa9aaa1323 -msgid "" -"If you want to script the configs in a language other than bash you can have" -" your script output commands and then source them in a bash script." -msgstr "" - -#: ../../automation/command-scripting.rst:82 e579b800945a42238f353a642e0a70bc -msgid "Here is a simple example:" -msgstr "" - -#: ../../automation/command-scripting.rst:102 371f68a335124cc3b41c936e6427fefb -msgid "Executing Configuration Scripts" -msgstr "" - -#: ../../automation/command-scripting.rst:104 df683ee968244371935d1e5f54381ffc -msgid "" -"There is a pitfall when working with configuration scripts. It is tempting " -"to call configuration scripts with \"sudo\" (i.e., temporary root " -"permissions), because that's the common way on most Linux platforms to call " -"system commands." -msgstr "" - -#: ../../automation/command-scripting.rst:108 59f9aad0a42b43fa828f5a80c6dc4b5b -msgid "" -"On VyOS this will cause the following problem: After modifying the " -"configuration via script like this once, it is not possible to manually " -"modify the config anymore:" -msgstr "" - -#: ../../automation/command-scripting.rst:118 a053834b07a44621845caaa7ea29cec7 -msgid "" -"This will result in the following error message: ``Set failed`` If this " -"happens, a reboot is required to be able to edit the config manually again." -msgstr "" - -#: ../../automation/command-scripting.rst:121 9a5ca8218e28475181b872ae7951f075 -msgid "" -"To avoid these problems, the proper way is to call a script with the " -"``vyattacfg`` group, e.g., by using the ``sg`` (switch group) command:" -msgstr "" - -#: ../../automation/command-scripting.rst:128 b1877ee52bd24e759b2d42164c56fc63 -msgid "" -"To make sure that a script is not accidentally called without the " -"``vyattacfg`` group, the script can be safeguarded like this:" -msgstr "" - -#: ../../automation/command-scripting.rst:138 a73d2d5ad41b4aaca7b8c46e8978f080 -msgid "Executing pre-hooks/post-hooks Scripts" -msgstr "" - -#: ../../automation/command-scripting.rst:140 4b63288775e14ec79d7070908fb6507c -msgid "" -"VyOS has the ability to run custom scripts before and after each commit" -msgstr "" - -#: ../../automation/command-scripting.rst:142 df1cc1dea2984ac18439061fcc497f7e -msgid "" -"The default directories where your custom Scripts should be located are:" -msgstr "" - -#: ../../automation/command-scripting.rst:152 512a1b7409f149c09140fe2a7028b912 -msgid "" -"Scripts are run in alphabetical order. Their names must consist entirely of " -"ASCII upper- and lower-case letters,ASCII digits, ASCII underscores, and " -"ASCII minus-hyphens.No other characters are allowed." -msgstr "" - -#: ../../automation/command-scripting.rst:156 61e8706e6133433ebf34b6131240b637 -msgid "" -"Custom scripts are not executed with root privileges (Use sudo inside if " -"this is necessary)." -msgstr "" - -#: ../../automation/command-scripting.rst:159 a9ffdbf67dd040bbbccabfc967a01f44 -msgid "" -"A simple example is shown below, where the ops command executed in the post-" -"hook script is \"show interfaces\"." -msgstr "" - -#: ../../automation/command-scripting.rst:176 364370e38f4e42fbad4a02dc26aadf6b -msgid "Preconfig on boot" -msgstr "" - -#: ../../automation/command-scripting.rst:178 3015d098134f40f79b42c6cf31397430 -msgid "" -"The ``/config/scripts/vyos-preconfig-bootup.script`` script is called on " -"boot before the VyOS configuration during boot process." -msgstr "" - -#: ../../automation/command-scripting.rst:181 -#: ../../automation/command-scripting.rst:200 d6777b5c6e784829a7bcb980465f44d6 -#: fd486e82744a4d9ab8d582376a99fe51 -msgid "" -"Any modifications were done to work around unfixed bugs and implement " -"enhancements that are not complete in the VyOS system can be placed here." -msgstr "" - -#: ../../automation/command-scripting.rst:184 -#: ../../automation/command-scripting.rst:203 01578e1114e148bc8c4e57f22fac02b0 -#: 3afb2a6b8ef049fba0b5ee464db29e6d -msgid "The default file looks like this:" -msgstr "" - -#: ../../automation/command-scripting.rst:195 4122b5cd64b5428b9cea053dd25af3c0 -msgid "Postconfig on boot" -msgstr "" - -#: ../../automation/command-scripting.rst:197 8b08494bbe6340c4bc24143ae5fb4f35 -msgid "" -"The ``/config/scripts/vyos-postconfig-bootup.script`` script is called on " -"boot after the VyOS configuration is fully applied." -msgstr "" - -#: ../../automation/command-scripting.rst:212 e7f470d251e24d66affcfc9374388278 -msgid "" -"For configuration/upgrade management issues, modification of this script " -"should be the last option. Always try to find solutions based on CLI " -"commands first." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/index.po b/docs/_locale/de_DE/LC_MESSAGES/automation/index.po deleted file mode 100644 index 37f2d1bc..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/index.po +++ /dev/null @@ -1,30 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/index.rst:3 3901e58b6a9e4771bc4fdac1f10d707a -msgid "VyOS Automation" -msgstr "" - -#: ../../automation/index.rst:6 47c60c158f06404d97222b5b68773229 -msgid "Saltstack" -msgstr "" - -#: ../../automation/index.rst:7 9b93b4dad8db45c1a4d99186ab441d51 -msgid "startup scripts" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-ansible.po b/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-ansible.po deleted file mode 100644 index fea3d6c0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-ansible.po +++ /dev/null @@ -1,56 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/vyos-ansible.rst:6 e405b3cd16fd4277a3b245e98f939389 -msgid "Ansible" -msgstr "" - -#: ../../automation/vyos-ansible.rst:8 d20f4882f8ed42c48545b9e08440d24c -msgid "" -"VyOS supports configuration via ansible. Need to install ``ansible`` and " -"``python3-paramiko`` module" -msgstr "" - -#: ../../automation/vyos-ansible.rst:11 b256da61f8fb417e857e02cd654d1a53 -msgid "Structure of files" -msgstr "" - -#: ../../automation/vyos-ansible.rst:24 fe2d6a59800142aa8f7d7089c5903489 -msgid "File contents" -msgstr "" - -#: ../../automation/vyos-ansible.rst:26 b6825e1462764e35ac127d1305adc30e -msgid "ansible.cfg" -msgstr "" - -#: ../../automation/vyos-ansible.rst:35 dd37dc1fca7042b7a42de60899de039c -msgid "id_rsa_docker.pub. Needs to declare only public key exactly." -msgstr "" - -#: ../../automation/vyos-ansible.rst:42 244ef3fa45a64870b4c2f93f34f93297 -msgid "hosts" -msgstr "" - -#: ../../automation/vyos-ansible.rst:56 8dcbd822cb6641b8924558f1f81e4076 -msgid "main.yml" -msgstr "" - -#: ../../automation/vyos-ansible.rst:80 592908ab475948ca9d6640d236f6918c -msgid "Run ansible" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-api.po b/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-api.po deleted file mode 100644 index b9f86bb9..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-api.po +++ /dev/null @@ -1,167 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/vyos-api.rst:7 07d92ac230e84acd850c6c56f9238a08 -msgid "VyOS API" -msgstr "" - -#: ../../automation/vyos-api.rst:9 ec3a654fc40a41509c6320d64796822b -msgid "For configuration and enabling the API see :ref:`http-api`" -msgstr "" - -#: ../../automation/vyos-api.rst:13 13d0f2086690496290e1666ed1ac14df -msgid "Authentication" -msgstr "" - -#: ../../automation/vyos-api.rst:15 25d9abb447b84093a6cba32829e95073 -msgid "" -"All endpoints only listen on HTTP POST requests and the API KEY must set as " -"``key`` in the formdata." -msgstr "" - -#: ../../automation/vyos-api.rst:18 b15a5df54b174996a0f356f56895799c -msgid "" -"Below see one example for curl and one for python. The rest of the " -"documentation is reduced to curl." -msgstr "" - -#: ../../automation/vyos-api.rst:41 252ce6bc7e2245349d8f0883011edd9b -msgid "API Endpoints" -msgstr "" - -#: ../../automation/vyos-api.rst:44 3f35b10b1bdb4a729e744a243862c8e9 -msgid "/retrieve" -msgstr "" - -#: ../../automation/vyos-api.rst:46 22ecac4116354d649e383c4dbb67002a -msgid "" -"With the ``retrieve`` endpoint you get parts or the whole configuration." -msgstr "" - -#: ../../automation/vyos-api.rst:48 6a45d66826544acb962f4b1f2948fcb0 -msgid "" -"To get the whole configuration, pass an empty list to the ``path`` field" -msgstr "" - -#: ../../automation/vyos-api.rst:79 06b5968f35ca40faabf6f34fd38ac531 -msgid "" -"To only get a part of the configuration, for example ``system syslog``." -msgstr "" - -#: ../../automation/vyos-api.rst:106 5cf33fb0621d4263b8da22d1b15c168f -msgid "" -"if you just want the Value of a multi-valued node, use the ``returnValues`` " -"operation." -msgstr "" - -#: ../../automation/vyos-api.rst:109 3e3c810c9d35481191225d8204240e18 -msgid "For example, get the addresses of a ``dum0`` interface." -msgstr "" - -#: ../../automation/vyos-api.rst:129 32e76c75c60747ea90fc1da23ed22a21 -msgid "/reset" -msgstr "" - -#: ../../automation/vyos-api.rst:131 04506f0762a74afe90a49f3749da11a7 -msgid "The ``reset`` endpoint run a ``reset`` command." -msgstr "" - -#: ../../automation/vyos-api.rst:147 03e6e381062541a28f40487ac95d93d6 -msgid "/image" -msgstr "" - -#: ../../automation/vyos-api.rst:149 f066c84e0a4e448e84abc7f7594f47df -msgid "To add or delete an image, use the ``/image`` endpoint." -msgstr "" - -#: ../../automation/vyos-api.rst:151 b3446c29406246fb91eb70ec5e18e792 -msgid "add an image" -msgstr "" - -#: ../../automation/vyos-api.rst:168 fd06f368fea143e69379753c9718a5c4 -msgid "delete an image, for example ``1.3-rolling-202006070117``" -msgstr "" - -#: ../../automation/vyos-api.rst:185 7ef7094b6f624238a5c5eaf1be0666d4 -msgid "/show" -msgstr "" - -#: ../../automation/vyos-api.rst:187 9f1cdf71940045788be283501f2d710b -msgid "The ``/show`` endpoint is to show everything in the operational mode." -msgstr "" - -#: ../../automation/vyos-api.rst:189 35c82a691c0a43e68967e89023d43839 -msgid "For example, show which images are installed." -msgstr "" - -#: ../../automation/vyos-api.rst:209 8bd2484508c84078837601953b36655e -msgid "/generate" -msgstr "" - -#: ../../automation/vyos-api.rst:211 ad32f841945e4ae0bf0c6020efedb644 -msgid "The ``generate`` endpoint run a ``generate`` command." -msgstr "" - -#: ../../automation/vyos-api.rst:228 33f32365e11745ad8e267a8b323deb3a -msgid "/configure" -msgstr "" - -#: ../../automation/vyos-api.rst:230 be11836154a94618814cecb82ef8bf86 -msgid "" -"You can pass a ``set``, ``delete`` or ``comment`` command to the " -"``/configure`` endpoint." -msgstr "" - -#: ../../automation/vyos-api.rst:233 3fa4011df5394a10b66f8efa6c2f7f18 -msgid "``set`` a single command" -msgstr "" - -#: ../../automation/vyos-api.rst:249 d0fd1e24ed8944b3b0681e9ded9fee28 -msgid "``delete`` a single command" -msgstr "" - -#: ../../automation/vyos-api.rst:264 db6fe5f1b1ae4d72b7e9be759134c062 -msgid "" -"The API pushes every request to a session and commit it. But some of VyOS " -"components like DHCP and PPPoE Servers, IPSec, VXLAN, and other tunnels " -"require full configuration for commit. The endpoint will process multiple " -"commands when you pass them as a list to the ``data`` field." -msgstr "" - -#: ../../automation/vyos-api.rst:285 f0c2175c25fc43a98e4c157e4dd81c41 -msgid "/config-file" -msgstr "" - -#: ../../automation/vyos-api.rst:287 8c74b78f0845409aad565b935aa9fcd4 -msgid "The endpoint ``/config-file`` is to save or load a configuration." -msgstr "" - -#: ../../automation/vyos-api.rst:289 98a84ef55d9b46eda653b57c973106b6 -msgid "" -"Save a running configuration to the startup configuration. When you don't " -"specify the file when saving, it saves to ``/config/config.boot``." -msgstr "" - -#: ../../automation/vyos-api.rst:307 320e97c17b5a4bc5831e2bc06d60e11e -msgid "Save a running configuration to a file." -msgstr "" - -#: ../../automation/vyos-api.rst:323 482efdddbacf4305934ee05a988c3d4c -msgid "To Load a configuration file." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-napalm.po b/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-napalm.po deleted file mode 100644 index dfcf1e2e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-napalm.po +++ /dev/null @@ -1,60 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/vyos-napalm.rst:6 a458dac8c8414b63b48d2d702f96b7d0 -msgid "Napalm" -msgstr "" - -#: ../../automation/vyos-napalm.rst:8 e192c0db73584de984c9316e63ee6b5d -msgid "" -"VyOS supports some napalm_ functions for configuration and op-mode. It " -"requires more tests." -msgstr "" - -#: ../../automation/vyos-napalm.rst:11 380f8923978046bd999342f858bd3d73 -msgid "Install ``napalm-vyos`` module" -msgstr "" - -#: ../../automation/vyos-napalm.rst:21 1188d17bc22a4b94b26a42f5000971c2 -msgid "Op-mode" -msgstr "" - -#: ../../automation/vyos-napalm.rst:48 e46e17b55de8404198ffce64badd6d2e -msgid "Output op-mode" -msgstr "" - -#: ../../automation/vyos-napalm.rst:85 4b9386b23f6a4cb097a1a15d688d27b5 -msgid "Configuration" -msgstr "" - -#: ../../automation/vyos-napalm.rst:87 b74837137fea4fce960c3eea4a2a5c73 -msgid "We need 2 files, commands.conf and script itself." -msgstr "" - -#: ../../automation/vyos-napalm.rst:89 bf55d87890744b2996a8bc0f1b3757cc -msgid "Content of commands.conf" -msgstr "" - -#: ../../automation/vyos-napalm.rst:99 1f1b6521bb624b9393a916124d54d9e1 -msgid "Script vyos-napalm.py" -msgstr "" - -#: ../../automation/vyos-napalm.rst:129 63b5c22d2a674e0cbd6211a2cf5ddce6 -msgid "Output" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-netmiko.po b/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-netmiko.po deleted file mode 100644 index a67f5aaa..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/automation/vyos-netmiko.po +++ /dev/null @@ -1,36 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../automation/vyos-netmiko.rst:6 1e1871eb1060440dba0e768d6b404310 -msgid "Netmiko" -msgstr "" - -#: ../../automation/vyos-netmiko.rst:8 6ecaf43a6559480484b28c5cf9b91652 -msgid "" -"VyOS supports configuration via netmiko_. It requires to install " -"``python3-netmiko`` module." -msgstr "" - -#: ../../automation/vyos-netmiko.rst:12 fd4e8a489d28462dbcb0fded5000da1a -msgid "Example" -msgstr "" - -#: ../../automation/vyos-netmiko.rst:47 7741fe48ac53415bb39935b122505e2d -msgid "Output" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/changelog/1.po b/docs/_locale/de_DE/LC_MESSAGES/changelog/1.po deleted file mode 100644 index 03700a01..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/changelog/1.po +++ /dev/null @@ -1,6114 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../changelog/1.4.rst:3 d5f7f29f23754b61913cc7daeb3abbb9 -msgid "1.4 Sagitta" -msgstr "" - -#: ../../changelog/1.4.rst:12 b59777d5daf0401f8f3f7fd6c412da1d -msgid "2022-10-14" -msgstr "" - -#: ../../changelog/1.4.rst:14 1df0555133e5465cac6ac779d638fcc7 -msgid "" -":vytask:`T4750` (feature): Support of higher level SSH keys (sk-ssh-ed25519)" -msgstr "" - -#: ../../changelog/1.4.rst:15 9835f370242d4d16a733ce13fcad6c94 -msgid ":vytask:`T4672` (bug): RADIUS server disable does not work" -msgstr "" - -#: ../../changelog/1.4.rst:16 797a4072fb48432cbd8a4bc5b352e36c -msgid "" -":vytask:`T4749` (enhancment): Use config_dict for conf_mode http-api.py" -msgstr "" - -#: ../../changelog/1.4.rst:20 a4836b06294e42f9875093d1136a89ef -msgid "2022-10-13" -msgstr "" - -#: ../../changelog/1.4.rst:22 52413791aedd4bc599f96b1679f78d78 -msgid "" -":vytask:`T4746` (bug): Monitoring nft. table vyos_filter by default does not" -" exist but telegraf checks this table" -msgstr "" - -#: ../../changelog/1.4.rst:23 ee4452d1c19348e5bae2fa537d029700 -msgid "" -":vytask:`T4744` (bug): BGP directly connected neighbors don't compatible " -"with ebgp-multihop" -msgstr "" - -#: ../../changelog/1.4.rst:24 ce1d8c733bc54fdfbefdd641aa1fce8d -msgid ":vytask:`T4716` (feature): SSH ability to configure RekeyLimit" -msgstr "" - -#: ../../changelog/1.4.rst:25 1fde6ec82c9f4a8d89c4a25f00dd1bbf -msgid "" -":vytask:`T4343` (default): Expose powerdns network-timeout for service dns " -"forwarding" -msgstr "" - -#: ../../changelog/1.4.rst:26 79553dc86cb841839871389ad7fc1471 -msgid "" -":vytask:`T4312` (bug): Telegraf configuration doesn't accept IPs for URL" -msgstr "" - -#: ../../changelog/1.4.rst:27 985ba840883b4fea80f057e1f3cf0afb -msgid "" -":vytask:`T4274` (default): Extend OpenConnect RADIUS Timeout to Permit 2FA " -"Entry" -msgstr "" - -#: ../../changelog/1.4.rst:31 345e688dbea548b28f1cd5461a2cf3bc -msgid "2022-10-12" -msgstr "" - -#: ../../changelog/1.4.rst:33 158087219a854d4cb7bcd441919629a1 -msgid "" -":vytask:`T4747` (bug): Monitoring influxdb template input exec plugin does " -"not work" -msgstr "" - -#: ../../changelog/1.4.rst:34 6af4fb10a8e04424965679d038d91888 -msgid ":vytask:`T4740` (bug): Show conntrack table ipv6 fail" -msgstr "" - -#: ../../changelog/1.4.rst:35 17c4f64920e04fa2a5b1fa1f5de6da3f -msgid "" -":vytask:`T4730` (bug): Conntrack-sync error - listen-address is not the " -"correct type in config as it should be" -msgstr "" - -#: ../../changelog/1.4.rst:39 e934ef0d8c4b4caa8838c7213726680f -msgid "2022-10-11" -msgstr "" - -#: ../../changelog/1.4.rst:41 70cae164608f4d468e0080526f25d433 -msgid "" -":vytask:`T4742` (bug): Autocomplete in policy route rule x set table / does " -"not show the tables created in the static protocols" -msgstr "" - -#: ../../changelog/1.4.rst:42 4deeb9faa64d4b30a0785605f1f09af7 -msgid ":vytask:`T4741` (bug): set firewall zone Local local-zone failed" -msgstr "" - -#: ../../changelog/1.4.rst:43 97c94ff6192042a49be108a8bbd9957d -msgid "" -":vytask:`T4680` (bug): Telegraf prometheus-client listen-address invalid " -"format" -msgstr "" - -#: ../../changelog/1.4.rst:47 8bfc8328c8da42a5af8195626e71ce2f -msgid "2022-10-10" -msgstr "" - -#: ../../changelog/1.4.rst:49 bfa85ee03d0f4d068b05bce867de1061 -msgid ":vytask:`T538` (feature): Support for network mapping in NAT" -msgstr "" - -#: ../../changelog/1.4.rst:53 1404c0b2de3d4782ba8e53dcb889ca86 -msgid "2022-10-09" -msgstr "" - -#: ../../changelog/1.4.rst:55 5b152eb1f2f24a309cd0dcb3400199d9 -msgid "" -":vytask:`T4738` (enhancment): Extend automatic generation of schema " -"definition files to native configsession functions; use single " -"resolver/directive" -msgstr "" - -#: ../../changelog/1.4.rst:59 73464757ef664d8488c9abfd98ede3b5 -msgid "2022-10-08" -msgstr "" - -#: ../../changelog/1.4.rst:61 a6caf2f540814f23b48fe899d37d944d -msgid ":vytask:`T4707` (feature): Enable OSPF segment routing" -msgstr "" - -#: ../../changelog/1.4.rst:65 3c04cb111a834be3bb0f4203164b7e8b -msgid "2022-10-07" -msgstr "" - -#: ../../changelog/1.4.rst:67 3285df3e497346a4b1d5b131f00a61a8 -msgid ":vytask:`T4736` (bug): Error on JSON output of API query ShowConfig" -msgstr "" - -#: ../../changelog/1.4.rst:71 4108e6ae3cf343c6b0a140d2b7bfbda7 -msgid "2022-10-04" -msgstr "" - -#: ../../changelog/1.4.rst:73 044c33012e2d4b97b4f9e7566cff55d1 -msgid ":vytask:`T4708` (bug): 'show nat destination rules' throwing an error" -msgstr "" - -#: ../../changelog/1.4.rst:74 a8231e2062dc4fbba5a646177d7dd597 -msgid ":vytask:`T4700` (feature): Firewall - Add interface match criteria" -msgstr "" - -#: ../../changelog/1.4.rst:75 a22a1e548c2f46eab23f1993f3c6730d -msgid "" -":vytask:`T4699` (feature): Firewall - Add jump action - Add return action" -msgstr "" - -#: ../../changelog/1.4.rst:76 3c105da581264b5288f96ef2ef1b3a9e -msgid ":vytask:`T4651` (feature): Firewall - Add options to match packet size" -msgstr "" - -#: ../../changelog/1.4.rst:77 0918077e3668436c8b9886c620bc7552 -msgid "" -":vytask:`T4702` (bug): Wireguard peers configuration is not synchronized " -"with CLI" -msgstr "" - -#: ../../changelog/1.4.rst:78 0f4fe06823734099abe4bdf34cb43f36 -msgid "" -":vytask:`T4685` (bug): Interface does not exist on boot when used as " -"inbound-interface for local policy route" -msgstr "" - -#: ../../changelog/1.4.rst:79 93702061fa464b8da7102beb01411581 -msgid ":vytask:`T4652` (feature): Upgrade PowerDNS recursor to 4.7 series" -msgstr "" - -#: ../../changelog/1.4.rst:80 da72499599a14a65a3751add3f9ff4ec -msgid "" -":vytask:`T4582` (default): Router-advert: Preferred lifetime cannot equal " -"valid lifetime in PIOs" -msgstr "" - -#: ../../changelog/1.4.rst:84 8e5e95419013491194d5b5c4d10b300d -msgid "2022-09-29" -msgstr "" - -#: ../../changelog/1.4.rst:86 4a3e143da66348c3b2b4218831454cc5 -msgid "" -":vytask:`T4715` (feature): Auto logout user after a period of inactivity" -msgstr "" - -#: ../../changelog/1.4.rst:87 aa489f4153e543e7bff402595edcd38e -msgid "" -":vytask:`T4697` (bug): policy route: Generating ConfigError failes when tcp " -"flag is missing on set tcp-mss rule commit" -msgstr "" - -#: ../../changelog/1.4.rst:91 70329f42cfef4b479148858865b0957f -msgid "2022-09-27" -msgstr "" - -#: ../../changelog/1.4.rst:93 32dc0aeac6c34c23890a240dab4d2b4b -msgid "" -":vytask:`T4711` (feature): Ability to terminate user TTY and PTS sessions" -msgstr "" - -#: ../../changelog/1.4.rst:94 cddeb0c640224f949260a681a4c009d0 -msgid "" -":vytask:`T4557` (feature): fastnetmon: allow configure limits per protocol " -"(tcp, udp, icmp)" -msgstr "" - -#: ../../changelog/1.4.rst:98 a3b45f9df26240a0a58c1a5efcea48ad -msgid "2022-09-21" -msgstr "" - -#: ../../changelog/1.4.rst:100 51f535460f3940da9103361a63eb225f -msgid "" -":vytask:`T4678` (feature): Rewrite service ipoe-server to get_config_dict" -msgstr "" - -#: ../../changelog/1.4.rst:101 96250da613134bb0a7cde5e4ce3a52d0 -msgid "" -":vytask:`T4703` (feature): accel-ppp: combine vlan-id and vlan-range into " -"single CLI node" -msgstr "" - -#: ../../changelog/1.4.rst:105 7221fac71b12439b99d07f3b54d80089 -msgid "2022-09-20" -msgstr "" - -#: ../../changelog/1.4.rst:107 887cfdc7a1b84b7298bffbf32c5b52ea -msgid ":vytask:`T4693` (bug): ISIS segment routing was broken..." -msgstr "" - -#: ../../changelog/1.4.rst:111 1fc02f3e57664986af85aa0a4f189ce8 -msgid "2022-09-17" -msgstr "" - -#: ../../changelog/1.4.rst:113 e329f53ebc2f480a9d8760d50f8865bc -msgid "" -":vytask:`T4666` (bug): EAP-TLS no longer allows TLSv1.0 after T4537, T4584" -msgstr "" - -#: ../../changelog/1.4.rst:114 f158750afb1042c286592eb430aa1cc8 -msgid "" -":vytask:`T4665` (bug): Keepalived cannot use same VRID for VRRPv2 and VRRPv3" -msgstr "" - -#: ../../changelog/1.4.rst:118 1775abca3d2547ac8a1b90b20a1001ba -msgid "2022-09-16" -msgstr "" - -#: ../../changelog/1.4.rst:120 53a341bfdc6f479e8f1e7ee560cbe0cf -msgid "" -":vytask:`T4698` (enhancment): Drop validator name=\"range\" and replace it " -"with numeric" -msgstr "" - -#: ../../changelog/1.4.rst:121 08a2dfba1d66425dadb543046208931d -msgid "" -":vytask:`T4695` (feature): Add 'es' and 'jp106' keymap option keyboard-" -"layout" -msgstr "" - -#: ../../changelog/1.4.rst:122 bdd905cd7df8428887ca593c7f482364 -msgid "" -":vytask:`T4669` (enhancment): Extend numeric.ml for inversion of values and " -"range values" -msgstr "" - -#: ../../changelog/1.4.rst:126 36e1539a679e4d368af683a06be9f2e4 -msgid "2022-09-15" -msgstr "" - -#: ../../changelog/1.4.rst:128 f814aaf8834c4e4b8326beed754090f3 -msgid "" -":vytask:`T4679` (bug): OpenVPN site-to-site incorrect check for IPv6 local " -"and remote address" -msgstr "" - -#: ../../changelog/1.4.rst:129 f8396cc7a7d54986aeef3334a485f6f5 -msgid ":vytask:`T4691` (feature): Upgrade Linux Kernel to latest 5.15.y train" -msgstr "" - -#: ../../changelog/1.4.rst:130 643f2ba0d225489a9c64360ec7edd484 -msgid "" -":vytask:`T4630` (bug): Prevent attempts to use the same interface as a " -"source interface for pseudo-ethernet and MACsec at the same time" -msgstr "" - -#: ../../changelog/1.4.rst:131 b527da9c964c4f6189aab8d569667e77 -msgid "" -":vytask:`T4696` (default): Extend bgp parameters for bgp bestpath peer-type " -"multipath-relax" -msgstr "" - -#: ../../changelog/1.4.rst:135 00be896ca7ea4fdf82cc16a051f22125 -msgid "2022-09-12" -msgstr "" - -#: ../../changelog/1.4.rst:137 e0e12b67b0c44afbb9d8bf09e9f7840d -msgid "" -":vytask:`T4617` (feature): VRF specification is needed for telegraf " -"prometheus-client listen-address <address>" -msgstr "" - -#: ../../changelog/1.4.rst:138 f1423c4f8e5d469da3ad8383d55f6a27 -msgid "" -":vytask:`T4690` (bug): Update GraphQL resolver for 'SystemStatus' following " -"changes to 'show_uptime' op-mode script" -msgstr "" - -#: ../../changelog/1.4.rst:139 985f692c93a14c21b5d56665092cc05f -msgid ":vytask:`T4647` (feature): Add Google Virtual NIC (gVNIC) support" -msgstr "" - -#: ../../changelog/1.4.rst:140 112fa0902b604222ab3a87973bd826d8 -msgid ":vytask:`T4170` (feature): Rename \"policy ipv6-route\" -> \"policy route6\"" -msgstr "" - -#: ../../changelog/1.4.rst:144 36e8409d192b43f89466e2582809fccf -msgid "2022-09-09" -msgstr "" - -#: ../../changelog/1.4.rst:146 60dab94a509841fb9c8417c31813658c -msgid "" -":vytask:`T4682` (feature): Rewrite 'show system storage' in standardized " -"format" -msgstr "" - -#: ../../changelog/1.4.rst:147 4dc430eb4b8744e8a1705db600596985 -msgid ":vytask:`T4681` (feature): Complete standardization of show_uptime.py" -msgstr "" - -#: ../../changelog/1.4.rst:151 438e9c78508141738701e8f2cc4b39cc -msgid "2022-09-06" -msgstr "" - -#: ../../changelog/1.4.rst:153 31c802e4dc6c46309d025ecd81ae4158 -msgid "" -":vytask:`T4640` (enhancment): Integrate op-mode exception hierarchy into API" -msgstr "" - -#: ../../changelog/1.4.rst:154 4864c0b4f6d64dfdb62509c3296b3967 -msgid "" -":vytask:`T4597` (bug): Check bind port before assign service HTTPS API and " -"openconnect" -msgstr "" - -#: ../../changelog/1.4.rst:155 1fc2faff02bb4485aafd2db85db0e9a5 -msgid "" -":vytask:`T4674` (bug): API should show op-mode error message, if present" -msgstr "" - -#: ../../changelog/1.4.rst:156 a196d9c6ad734affacd09f80cfe13733 -msgid "" -":vytask:`T4673` (bug): op-mode bridge.py should raise error on show_fdb for " -"nonexistent bridge interface" -msgstr "" - -#: ../../changelog/1.4.rst:160 f064cd2a0e704093bd9d06525a82ee2f -msgid "2022-09-05" -msgstr "" - -#: ../../changelog/1.4.rst:162 c469e18c52784ef0b26e73516e4f3ded -msgid "" -":vytask:`T4668` (bug): Adding/removing members from bond doesn't " -"work/results in incorrect interface state" -msgstr "" - -#: ../../changelog/1.4.rst:163 056be1f4ef5942b79f78f11b6cf4d90d -msgid ":vytask:`T4663` (bug): Interface pseudo-ethernet does not change mode" -msgstr "" - -#: ../../changelog/1.4.rst:164 9b6cb271f19b4579ad3c9825f7535643 -msgid "" -":vytask:`T4655` (bug): Firewall in 1.4 sets the default action 'accept' " -"instead of 'drop'" -msgstr "" - -#: ../../changelog/1.4.rst:165 d01854cc06b2430b996819c6e11eab86 -msgid "" -":vytask:`T4628` (bug): ConfigTree() throws ValueError() if tagNode contains " -"whitespaces" -msgstr "" - -#: ../../changelog/1.4.rst:169 de7a6d4e59d64f229bb752f7a385da46 -msgid "2022-09-01" -msgstr "" - -#: ../../changelog/1.4.rst:171 dd4fedd60ce3461fab4f02a3768c5626 -msgid "" -":vytask:`T4606` (bug): monitor nat destination translation shows missing " -"script" -msgstr "" - -#: ../../changelog/1.4.rst:172 d02afa36891b42c2b76ae3af847cf39c -msgid "" -":vytask:`T4435` (bug): Policy route and firewall - error when using " -"undefined group" -msgstr "" - -#: ../../changelog/1.4.rst:173 b84b104ef30042b5b62b37573bbeac79 -msgid "" -":vytask:`T4147` (bug): New Firewall Implementation - proposed changes on " -"group implementation" -msgstr "" - -#: ../../changelog/1.4.rst:177 7bb195469a6143a489709721d7e7377f -msgid "2022-08-31" -msgstr "" - -#: ../../changelog/1.4.rst:179 2aa736d0f7c844f2833212c6bf7d1d07 -msgid "" -":vytask:`T4650` (feature): Rewire show nat translation to vyos.opmode format" -msgstr "" - -#: ../../changelog/1.4.rst:180 8c95baf530fa4aa9a0841d35302cc487 -msgid ":vytask:`T4644` (bug): Check bind port before assign vpn sstp" -msgstr "" - -#: ../../changelog/1.4.rst:181 f556c34ba1f7425f80e7faf7ebb39766 -msgid "" -":vytask:`T4643` (bug): Smoketest exclude either sstp or openconnect from " -"pki-misc default listen port" -msgstr "" - -#: ../../changelog/1.4.rst:182 6d68127eaa63425bbce6adb7a98c46f5 -msgid ":vytask:`T4569` (feature): Rewrite show bridge to new format" -msgstr "" - -#: ../../changelog/1.4.rst:183 5555258a1f0c433d9b40961f404fbc5f -msgid "" -":vytask:`T4547` (bug): Show vpn ipsec sa show unexpected prefix 'B' in " -"packets" -msgstr "" - -#: ../../changelog/1.4.rst:184 9ad6574bfd224819ac215458aa2d25b1 -msgid ":vytask:`T4367` (bug): NAT - Config tmp file not available" -msgstr "" - -#: ../../changelog/1.4.rst:188 3cb980602d4a4459a6fc206ce6c9e268 -msgid "2022-08-29" -msgstr "" - -#: ../../changelog/1.4.rst:190 112f837dd2aa447b8538b977c6312d13 -msgid "" -":vytask:`T4645` (bug): show nat source statistics lack argument --family" -msgstr "" - -#: ../../changelog/1.4.rst:191 02a7ca0b7eba45cf8876814c2f866710 -msgid "" -":vytask:`T4634` (bug): Bgp neighbor disable-connected-check does not work" -msgstr "" - -#: ../../changelog/1.4.rst:192 648edba6ecf8437d93bcde8cfec034cd -msgid ":vytask:`T4631` (feature): Add port and protocol to nat66" -msgstr "" - -#: ../../changelog/1.4.rst:193 ee2b6fd7dacc4369ad298d58dcbff522 -msgid ":vytask:`T4623` (feature): Add show conntrack statistics" -msgstr "" - -#: ../../changelog/1.4.rst:194 7ac83a9c56d1453c8c22a5a1f2fa4a61 -msgid ":vytask:`T4595` (bug): DPD interval and timeout do not work in DMVPN" -msgstr "" - -#: ../../changelog/1.4.rst:195 eceb333524144f0f847ba90f6f952f90 -msgid ":vytask:`T4594` (feature): Rewrite op-mode IPsec to vyos.opmode format" -msgstr "" - -#: ../../changelog/1.4.rst:196 a09904ffaa6c4f75b2995c5c0c2f87bf -msgid "" -":vytask:`T4508` (bug): Problem with values of the same environment in " -"different event handlers" -msgstr "" - -#: ../../changelog/1.4.rst:197 9045f5c8c54844bcac702145ff9c20ca -msgid "" -":vytask:`T4653` (bug): Interface offload options are not applied correctly" -msgstr "" - -#: ../../changelog/1.4.rst:198 440ffeb088274026a51840cd0447b693 -msgid ":vytask:`T4546` (bug): Does not connect Cisco spoke to VyOS hub." -msgstr "" - -#: ../../changelog/1.4.rst:199 0915d2f5904d49ecaf6cf7dfeca30240 -msgid "" -":vytask:`T4061` (default): Add util function to check for completion of boot" -" config" -msgstr "" - -#: ../../changelog/1.4.rst:200 026aaff74d604046a84060925c2f0bdf -msgid ":vytask:`T4654` (bug): RPKI cache incorrect description" -msgstr "" - -#: ../../changelog/1.4.rst:201 1a26d4335e2349ccb494e261516da59a -msgid "" -":vytask:`T4572` (bug): Add an option to force interface MTU to the value " -"received from DHCP" -msgstr "" - -#: ../../changelog/1.4.rst:205 215101f1c60c48f6b3f65f71ce13f03c -msgid "2022-08-26" -msgstr "" - -#: ../../changelog/1.4.rst:207 b9bc7c3998744feda0d184002e0d6b44 -msgid ":vytask:`T4642` (bug): proxy: hyphen not allowed in proxy URL" -msgstr "" - -#: ../../changelog/1.4.rst:211 470cad2deea34ee2b6aadf69e7da31d7 -msgid "2022-08-25" -msgstr "" - -#: ../../changelog/1.4.rst:213 6f7e5b3aad5f4b15a2649a3a173b2389 -msgid ":vytask:`T4626` (bug): Error showing nat66 source and destination" -msgstr "" - -#: ../../changelog/1.4.rst:214 40ae83c257ca48b49b275fd818dcac62 -msgid ":vytask:`T4622` (feature): Firewall allow drop packets by TCP MSS size" -msgstr "" - -#: ../../changelog/1.4.rst:218 353e217dd2394aa088fab7e297672486 -msgid "2022-08-24" -msgstr "" - -#: ../../changelog/1.4.rst:220 72958db8fefd4ddbbe61d42130a0c5b1 -msgid ":vytask:`T4641` (bug): prefix-list allows ipv6 prefix as input" -msgstr "" - -#: ../../changelog/1.4.rst:221 e10ab59c04b04b59af86ede0dddc4d54 -msgid ":vytask:`T4633` (feature): Change keepalived to v2.2.7" -msgstr "" - -#: ../../changelog/1.4.rst:225 55c61cd5f4774c06bbca44fde229814f -msgid "2022-08-23" -msgstr "" - -#: ../../changelog/1.4.rst:227 c58a1388abfc48f4b2a24e2eadab52c9 -msgid ":vytask:`T4618` (bug): Traffic policy not set on virtual interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:228 405afbbaad1b445abe8d673d224ad8e6 -msgid "" -":vytask:`T4538` (bug): Macsec does not work correctly when the interface " -"status changes." -msgstr "" - -#: ../../changelog/1.4.rst:232 addf04aa811e4704b5dcca63cb7be395 -msgid "2022-08-22" -msgstr "" - -#: ../../changelog/1.4.rst:234 e085743e7ebf43d79e22e632e2a5cf6a -msgid "" -":vytask:`T4089` (bug): Show nat destination rules shows ip address instead " -"of interface 'any'" -msgstr "" - -#: ../../changelog/1.4.rst:235 1ce162a7ddc04795afbc373faaacad07 -msgid ":vytask:`T4632` (bug): VLAN-aware bridge not working" -msgstr "" - -#: ../../changelog/1.4.rst:236 07c5ab40bba94e2cb91dc4e600cffd9e -msgid ":vytask:`T4637` (feature): Upgrade to podman 4.2.0" -msgstr "" - -#: ../../changelog/1.4.rst:240 392e126d2e544568bbbddd75248b3fa6 -msgid "2022-08-20" -msgstr "" - -#: ../../changelog/1.4.rst:242 e08a8c766d554cb3aefbe0d4ee23fc52 -msgid "" -":vytask:`T4596` (bug): \"show openconnect-server sessions\" command does not" -" work in the openconnect module" -msgstr "" - -#: ../../changelog/1.4.rst:246 7448ac182e914351ae7f00b577f5a69a -msgid "2022-08-19" -msgstr "" - -#: ../../changelog/1.4.rst:248 f16433fb247348f8b7c3553006c98999 -msgid ":vytask:`T4620` (bug): UPnP does not work due to incorrect template" -msgstr "" - -#: ../../changelog/1.4.rst:249 e01228bb916442c5be059936212fe654 -msgid "" -":vytask:`T4619` (bug): Static arp is not set if another entry is present" -msgstr "" - -#: ../../changelog/1.4.rst:250 3723e42b0f984e6681c5b7f1fd547e51 -msgid "" -":vytask:`T4611` (bug): UPnP rule IP should be a prefix instead of an address" -msgstr "" - -#: ../../changelog/1.4.rst:251 0ffa21ef2ad941a8bcf140869cd34424 -msgid ":vytask:`T4614` (feature): OpenConnect split-dns directive" -msgstr "" - -#: ../../changelog/1.4.rst:255 d313859624cf4128bb5bdcf917bed02e -msgid "2022-08-18" -msgstr "" - -#: ../../changelog/1.4.rst:257 4ffcf56f70d34aeaae16de279a863a0a -msgid ":vytask:`T4613` (bug): UPnP configuration without listen option fail" -msgstr "" - -#: ../../changelog/1.4.rst:258 3dd046e5b4ee40bab54a841743fe5f3f -msgid "" -":vytask:`T4570` (bug): Exception when trying to set up VXLAN over Wireguard" -msgstr "" - -#: ../../changelog/1.4.rst:262 9f847caa33134e93a7a7a4f41923f6e7 -msgid "2022-08-17" -msgstr "" - -#: ../../changelog/1.4.rst:264 0296ed9dd7f54f39824095b114197beb -msgid ":vytask:`T4598` (feature): nat66 - Add exclude options" -msgstr "" - -#: ../../changelog/1.4.rst:265 78d342ab7db541159749189fcb9f6415 -msgid "" -":vytask:`T4480` (default): add an ability to configure squid acl safe ports " -"and acl ssl safe ports" -msgstr "" - -#: ../../changelog/1.4.rst:269 5268c35e792a484098899dad1941026e -msgid "2022-08-16" -msgstr "" - -#: ../../changelog/1.4.rst:271 e6aeb5929006473888d523f379dc5632 -msgid "" -":vytask:`T4592` (bug): macsec: can not create two interfaces using the same " -"source-interface" -msgstr "" - -#: ../../changelog/1.4.rst:272 9552ca78fee14c3ca86d9f7cfc58a0e1 -msgid ":vytask:`T4584` (bug): hostap: create custom package build" -msgstr "" - -#: ../../changelog/1.4.rst:273 0993762e7cdd4bd2ad7a71395b0622e6 -msgid ":vytask:`T4413` (default): Add an API endpoint with basic system stats" -msgstr "" - -#: ../../changelog/1.4.rst:274 aff5c03a13384b9fbc4148affd713a9d -msgid ":vytask:`T4537` (bug): MACsec not working with cipher gcm-aes-256" -msgstr "" - -#: ../../changelog/1.4.rst:278 87982078d0ba4119bde2b01240dd8d4d -msgid "2022-08-15" -msgstr "" - -#: ../../changelog/1.4.rst:280 430d704b01aa436186e32cf824a65a56 -msgid ":vytask:`T4609` (bug): Unable to Restart Container VyOS 1.4" -msgstr "" - -#: ../../changelog/1.4.rst:281 2b0bbd96df83417f86df437b60920a29 -msgid "" -":vytask:`T4565` (bug): vlan aware bridge not working with - Kernel: T3318: " -"update Linux Kernel to v5.4.205 #249" -msgstr "" - -#: ../../changelog/1.4.rst:282 c6ccfbfed1af42f48f1e420d6df2ee8f -msgid "" -":vytask:`T3988` (default): Feature Request: IPsec Multiple local/remote " -"prefix for the tunnel" -msgstr "" - -#: ../../changelog/1.4.rst:283 2bb56d9989b14e64a92ce06ba1540716 -msgid ":vytask:`T2763` (feature): New SNMP resource request - SNMP over TCP" -msgstr "" - -#: ../../changelog/1.4.rst:287 b73cbb5cfa914501be61319012c635d3 -msgid "2022-08-14" -msgstr "" - -#: ../../changelog/1.4.rst:289 b6eeddb7600d47c280c219538623c60e -msgid "" -":vytask:`T4579` (bug): bridge: can not delete member interface CLI option " -"when VLAN is enabled" -msgstr "" - -#: ../../changelog/1.4.rst:290 dd8d34044401483688f10de432dc8316 -msgid "" -":vytask:`T4421` (default): Add support for floating point numbers in the " -"numeric validator" -msgstr "" - -#: ../../changelog/1.4.rst:291 3ab1b18c598246c3934e8e1834717076 -msgid "" -":vytask:`T3507` (bug): Bond with mode LACP show u/u in show interfaces even " -"if peer is not configured" -msgstr "" - -#: ../../changelog/1.4.rst:295 73c9dcaf864b4f57a6ce2eb78c01f94f -msgid "2022-08-12" -msgstr "" - -#: ../../changelog/1.4.rst:297 71fdf1025a084258bd5793f9b7da503e -msgid "" -":vytask:`T4603` (feature): Need a config option to specify NAS-IP-Address " -"for vpn l2tp" -msgstr "" - -#: ../../changelog/1.4.rst:301 049d6b06d86944d196b568d72e864819 -msgid "2022-08-10" -msgstr "" - -#: ../../changelog/1.4.rst:303 ea5f792d9a27478ea9ef0c688466891d -msgid ":vytask:`T4408` (feature): Add sshguard to protect against brut-forces" -msgstr "" - -#: ../../changelog/1.4.rst:307 f8edd767482e477fa60b374164156a53 -msgid "2022-08-08" -msgstr "" - -#: ../../changelog/1.4.rst:309 7b1a8f13391b4610b40db574f7beacd0 -msgid "" -":vytask:`T4586` (feature): Add to NAT66: SNAT destination address and DNAT " -"source address." -msgstr "" - -#: ../../changelog/1.4.rst:313 5453535bbcae4842a5b9aa6e6a7383b8 -msgid "2022-08-04" -msgstr "" - -#: ../../changelog/1.4.rst:315 9752fa21a37447ef84676940a96ee11d -msgid "" -":vytask:`T4257` (feature): Discussion on changing BGP autonomous system " -"number syntax" -msgstr "" - -#: ../../changelog/1.4.rst:319 27864da3e7044dd8bc76927ba4965e05 -msgid "2022-08-02" -msgstr "" - -#: ../../changelog/1.4.rst:321 17a942f0a9f04b82bb1992a5f662e7ba -msgid ":vytask:`T4585` (feature): Rewrite op-mode containers to vyos.opmode" -msgstr "" - -#: ../../changelog/1.4.rst:322 1e044530ad0b48d2be5f4e79b289fdcb -msgid ":vytask:`T4515` (default): Reduce telegraf binary size" -msgstr "" - -#: ../../changelog/1.4.rst:326 70856904fd2b4023a3927da5ca9aaf3a -msgid "2022-08-01" -msgstr "" - -#: ../../changelog/1.4.rst:328 27ccd062cfc344f98510d518787891c6 -msgid ":vytask:`T4581` (bug): 'show system cpu' not working" -msgstr "" - -#: ../../changelog/1.4.rst:329 0c596d6e2a9b428a82519cd95fb968e2 -msgid "" -":vytask:`T4578` (feature): Rewrite show dns forwarding statistics to new " -"format" -msgstr "" - -#: ../../changelog/1.4.rst:333 af1a634868794597ba5b58b976620c18 -msgid "2022-07-31" -msgstr "" - -#: ../../changelog/1.4.rst:335 62bf25767ddc47bb98b642f44f3dbbf7 -msgid "" -":vytask:`T4580` (bug): Handle the case of op-mode file names with hyphens in" -" GraphQL schema/resolver generation" -msgstr "" - -#: ../../changelog/1.4.rst:339 b387ea37470f456c9b6dbdb1fc2fd310 -msgid "2022-07-30" -msgstr "" - -#: ../../changelog/1.4.rst:341 7d1edb782f2f40f5af30ea04b15b8f90 -msgid "" -":vytask:`T4575` (feature): vyos.utill add new wrapper \"rc_cmd\" to get the " -"return code and output" -msgstr "" - -#: ../../changelog/1.4.rst:342 a4f3d1c779c248bdb389b72cc86a9977 -msgid ":vytask:`T4562` (feature): Rewrite show vrf to new format" -msgstr "" - -#: ../../changelog/1.4.rst:343 157ed377e57340d0b7ea24f707cc530c -msgid ":vytask:`T4545` (feature): Rewrite show nat source rules" -msgstr "" - -#: ../../changelog/1.4.rst:344 9ef7615cf0fd4571adcbbf5cc1ae29be -msgid "" -":vytask:`T4543` (bug): Show source nat statistics shows incorrect interface" -msgstr "" - -#: ../../changelog/1.4.rst:345 d0b9280119c841a3ba94cba3f3166c62 -msgid "" -":vytask:`T4503` (default): Prevent op mode scripts from restarting services " -"if there's a commit in progress" -msgstr "" - -#: ../../changelog/1.4.rst:346 2fc2aaa642c247b0a85edc332d549cdc -msgid "" -":vytask:`T4411` (feature): Add migration for service monitoring telegraf " -"influxdb" -msgstr "" - -#: ../../changelog/1.4.rst:350 5456bf5354ae4291a5a6c502a1b5e34c -msgid "2022-07-29" -msgstr "" - -#: ../../changelog/1.4.rst:352 49e651a64fed4b3c97b0b038e97c32a9 -msgid "" -":vytask:`T4554` (enhancment): Implement GraphQL resolvers for standardized " -"op-mode scripts" -msgstr "" - -#: ../../changelog/1.4.rst:353 eff3cae07a004440a3b6ca83be02e0f1 -msgid "" -":vytask:`T4518` (feature): Add XML for CLI conf mode load-balancing wan" -msgstr "" - -#: ../../changelog/1.4.rst:354 81ba5a65f9f34db7902e673833993ae0 -msgid "" -":vytask:`T4544` (enhancment): Generate schema definitions from standardized " -"op-mode scripts" -msgstr "" - -#: ../../changelog/1.4.rst:358 f3b3d8d7b2e045b9aad7dba6a90c6299 -msgid "2022-07-28" -msgstr "" - -#: ../../changelog/1.4.rst:360 0abf57aa1bb64f2b9e6469946f9b1c88 -msgid ":vytask:`T4531` (bug): NAT op-mode errors with exclude rules" -msgstr "" - -#: ../../changelog/1.4.rst:361 d211909266f14f5dbb8901dc65af745a -msgid ":vytask:`T3435` (bug): NAT rules show corruption" -msgstr "" - -#: ../../changelog/1.4.rst:365 d7ec4469a1324f6690b0818f21d9c76f -msgid "2022-07-27" -msgstr "" - -#: ../../changelog/1.4.rst:367 3b90f06ba2674ffbbb5efd29fd043842 -msgid "" -":vytask:`T4571` (bug): Sflow with vrf configured does not use vrf to " -"validate agent-address IP from vrf-configured interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:368 52b49f7b26fb40198d990e50f4b07a6e -msgid ":vytask:`T4552` (bug): Unable to reset IPsec IPv6 peer" -msgstr "" - -#: ../../changelog/1.4.rst:372 4603fbb5e90f4c7da858d0bdfb9a815a -msgid "2022-07-26" -msgstr "" - -#: ../../changelog/1.4.rst:374 f735d147d2e744bf8f1e88aa817daacf -msgid ":vytask:`T4568` (bug): show vpn debug peer doesn't work" -msgstr "" - -#: ../../changelog/1.4.rst:375 d69f33755bfc48cbaf98b931aa26d2b0 -msgid "" -":vytask:`T4556` (feature): fastnetmon: Allow configure white_list_path and " -"populate with hosts/networks that should be ignored." -msgstr "" - -#: ../../changelog/1.4.rst:376 111687b7be68454c9f42956f9be92a9c -msgid ":vytask:`T4495` (feature): Combine BGP reset op commands" -msgstr "" - -#: ../../changelog/1.4.rst:380 e8a37deed4c245a0ae4211f12f6a41d1 -msgid "2022-07-25" -msgstr "" - -#: ../../changelog/1.4.rst:382 cd89b0c34350482eb8f6fbb65b24b882 -msgid "" -":vytask:`T4567` (default): Merge experimental branch of GraphQL development" -msgstr "" - -#: ../../changelog/1.4.rst:383 b7bb3ea0160945559f222297214d8e78 -msgid ":vytask:`T4560` (bug): VRF and BGP neighbor local-as error" -msgstr "" - -#: ../../changelog/1.4.rst:384 df56f16deb0a4ca497966dea50c40908 -msgid ":vytask:`T4493` (bug): Incorrect help for \"show bgp neighbors\"" -msgstr "" - -#: ../../changelog/1.4.rst:385 8bfa6d3c6b2a48efb7c30cd54b071432 -msgid ":vytask:`T1233` (bug): ipsec vpn sa showing down" -msgstr "" - -#: ../../changelog/1.4.rst:389 192ebc3aad294be0947486a411adc795 -msgid "2022-07-22" -msgstr "" - -#: ../../changelog/1.4.rst:391 82dbd582a6ea4b888d55bf734dcf1898 -msgid "" -":vytask:`T4145` (bug): Conntrack table not showing after firewall rewriting" -msgstr "" - -#: ../../changelog/1.4.rst:395 0a7703a182864c20a42d07aab53c0a03 -msgid "2022-07-21" -msgstr "" - -#: ../../changelog/1.4.rst:397 d0d1ece37ddf4f6796ee901cfdc23195 -msgid ":vytask:`T4555` (feature): fastnetmon: add IPv6 support" -msgstr "" - -#: ../../changelog/1.4.rst:398 79a6efc16ded4bb1b137609cda8a0d38 -msgid "" -":vytask:`T4553` (default): Allow to set ban time on ddos-protection " -"configuration" -msgstr "" - -#: ../../changelog/1.4.rst:402 0aa4258026cd4372b6d5240ccd102d17 -msgid "2022-07-20" -msgstr "" - -#: ../../changelog/1.4.rst:404 bef16d3e320843acabb1de36407dc2e4 -msgid ":vytask:`T4056` (bug): Traffic policy not set in live configuration" -msgstr "" - -#: ../../changelog/1.4.rst:408 bfa78cafb7e14dc9a85c3eb96bd490e9 -msgid "2022-07-18" -msgstr "" - -#: ../../changelog/1.4.rst:410 c1e7f4f7789940fbb06e74493a0c5aff -msgid "" -":vytask:`T4523` (feature): OP-mode Extend conntrack output to get marks, " -"zones and directions" -msgstr "" - -#: ../../changelog/1.4.rst:411 14548fd63b7940d091d4b275d84a899d -msgid "" -":vytask:`T4228` (bug): bond: OS error thrown when two bonds use the same " -"member" -msgstr "" - -#: ../../changelog/1.4.rst:412 0dc9bdbc1663491eabe0284d75a96ccb -msgid "" -":vytask:`T4539` (feature): qat: update Intel QuickAssist release version " -"1.7.L.4.16.0-00017" -msgstr "" - -#: ../../changelog/1.4.rst:413 6e97e72a9da14bbe8ab2ab85d9bd2e95 -msgid "" -":vytask:`T4534` (bug): bond: bridge: error out if member interface is " -"assigned to a VRF instance" -msgstr "" - -#: ../../changelog/1.4.rst:414 2a469973572c40e4876f3c6054d01fa4 -msgid "" -":vytask:`T4525` (bug): Delete interface from VRF and add it to bonding error" -msgstr "" - -#: ../../changelog/1.4.rst:415 7793ed41d162439cb2eeab1fd3eea2d2 -msgid "" -":vytask:`T4522` (feature): bond: add ability to specify mii monitor interval" -" via CLI" -msgstr "" - -#: ../../changelog/1.4.rst:416 5038649e678b459eb700b968821200a7 -msgid ":vytask:`T4535` (feature): FRR: upgrade to stable/8.3 version" -msgstr "" - -#: ../../changelog/1.4.rst:417 4bbb911715f34a50822a88e48249676e -msgid "" -":vytask:`T4521` (bug): bond: ARP monitor interval is not configured despite " -"set via CLI" -msgstr "" - -#: ../../changelog/1.4.rst:418 7ad85eb1c6ad4341ad465015b706ae3e -msgid ":vytask:`T4540` (feature): firmware: update to Linux release 20220708" -msgstr "" - -#: ../../changelog/1.4.rst:422 a939c839b54b41cfb9458fde4c665365 -msgid "2022-07-17" -msgstr "" - -#: ../../changelog/1.4.rst:424 54a12923a4c54453a2b86f3e1b9e4fad -msgid "" -":vytask:`T4028` (bug): FRR 8.1 routes not being applied to routing table " -"after reboot if an interface has 2 ip addresses" -msgstr "" - -#: ../../changelog/1.4.rst:428 7f779f6ff08b4f66a49d7c4e9e559c1e -msgid "2022-07-15" -msgstr "" - -#: ../../changelog/1.4.rst:430 ae759fa7ef454ada88db8c7bac5f97b5 -msgid ":vytask:`T4494` (bug): Cannot reset BGP peer within VRF" -msgstr "" - -#: ../../changelog/1.4.rst:431 c624f93e35b84bf888139894d72c13e7 -msgid ":vytask:`T4536` (feature): FRR: move to systemd for daemon control" -msgstr "" - -#: ../../changelog/1.4.rst:435 1fef48123d87455798bf1b619d9806ed -msgid "2022-07-14" -msgstr "" - -#: ../../changelog/1.4.rst:437 3159f2bc77ce46e6a0f46722217a443f -msgid "" -":vytask:`T4491` (bug): Use empty string for internal name of root node of " -"config_tree" -msgstr "" - -#: ../../changelog/1.4.rst:441 91cca3c37e9f466bbe18dedf3ee31cbc -msgid "2022-07-13" -msgstr "" - -#: ../../changelog/1.4.rst:443 112cda7120de4a098ee51d8723964257 -msgid ":vytask:`T1375` (feature): Add clear dhcp server lease function" -msgstr "" - -#: ../../changelog/1.4.rst:447 d4e3ae8d57c8475e9b3d288481c959b9 -msgid "2022-07-12" -msgstr "" - -#: ../../changelog/1.4.rst:449 f753ee724183440cbc6abbb685598f55 -msgid ":vytask:`T4527` (bug): Prevent to create VRF name default" -msgstr "" - -#: ../../changelog/1.4.rst:450 a4ddd828bd9043009a4b66c0b978822b -msgid ":vytask:`T4084` (default): Dehardcode the default login banner" -msgstr "" - -#: ../../changelog/1.4.rst:451 64bef80685d642a89d2e003e2192f027 -msgid "" -":vytask:`T3948` (feature): IPSec VPN: Add a new option \"none\" for the " -"connection-type" -msgstr "" - -#: ../../changelog/1.4.rst:452 8ff8130bb6bb48b2a8ccb46baba8582b -msgid ":vytask:`T235` (feature): Ability to configure manual IP Rules" -msgstr "" - -#: ../../changelog/1.4.rst:456 04c61e704ad9421794c8fcc146d5a071 -msgid "2022-07-10" -msgstr "" - -#: ../../changelog/1.4.rst:458 058530726388427aae6be5a45abf1cf0 -msgid "" -":vytask:`T3836` (bug): Setting a default IPv6 route while getting IPv4 " -"gateway via DHCP removes the IPv4 gateway" -msgstr "" - -#: ../../changelog/1.4.rst:462 f49849a6afc84a4eaf7f3988e055294a -msgid "2022-07-09" -msgstr "" - -#: ../../changelog/1.4.rst:464 fdee3dfe37b64728b0ba79c73ed5edab -msgid "" -":vytask:`T4507` (feature): IPoE-server add multiplier option for shaper" -msgstr "" - -#: ../../changelog/1.4.rst:465 230456af2a8440e8bcfb9956fec19bae -msgid "" -":vytask:`T4499` (bug): NAT source translation not showing a single output" -msgstr "" - -#: ../../changelog/1.4.rst:466 1eb9bf6eb4514e53963541c50756e8bd -msgid "" -":vytask:`T4468` (bug): web-proxy source group cannot start with a number bug" -msgstr "" - -#: ../../changelog/1.4.rst:467 d62b89b910a54d90bce544994cf53bd1 -msgid "" -":vytask:`T4373` (feature): PPPoE-server add multiplier option for shaper" -msgstr "" - -#: ../../changelog/1.4.rst:468 5e1155c016334944a9ea5ab02c015f7a -msgid ":vytask:`T3353` (bug): PPPoE server wrong vlan-range generating config" -msgstr "" - -#: ../../changelog/1.4.rst:469 2a40be21a61b4fde931bee5e4a33cbae -msgid ":vytask:`T3648` (bug): op-mode: nat rules broken" -msgstr "" - -#: ../../changelog/1.4.rst:470 cd190385eb4145649717b6a0caaea1a5 -msgid "" -":vytask:`T4517` (feature): ip: Add options to enable directed broadcast " -"forwarding" -msgstr "" - -#: ../../changelog/1.4.rst:474 a66d6bb51c374539877074d2ae34e0d0 -msgid "2022-07-07" -msgstr "" - -#: ../../changelog/1.4.rst:476 cfe7b34aefaf4bed959ea05bbaf7e0ea -msgid "" -":vytask:`T4456` (bug): NTP client in VRF tries to bind to interfaces outside" -" VRF, logs many messages" -msgstr "" - -#: ../../changelog/1.4.rst:477 2951974f726b41dca9e264bbb54aab0b -msgid ":vytask:`T4509` (feature): Feature Request: DNS64" -msgstr "" - -#: ../../changelog/1.4.rst:481 0fd37c27d48b40b2a561ff27d67073e4 -msgid "2022-07-06" -msgstr "" - -#: ../../changelog/1.4.rst:483 24a0d7b2b17d458585fec42a35125b4e -msgid ":vytask:`T4513` (bug): Webproxy monitor commands do not work" -msgstr "" - -#: ../../changelog/1.4.rst:484 ae5b4217455a4d898b2faf741a1719c8 -msgid ":vytask:`T4299` (feature): Firewall - GeoIP filtering" -msgstr "" - -#: ../../changelog/1.4.rst:488 02870aa6b55d47b3b33527831b026d94 -msgid "2022-07-05" -msgstr "" - -#: ../../changelog/1.4.rst:490 74ad4ff3efb14157abef740e6822dd36 -msgid "" -":vytask:`T4378` (bug): Unable to submit wildcard (\"*.example.com\") A or " -"AAAA records in dns forwarder" -msgstr "" - -#: ../../changelog/1.4.rst:491 4936770f253c4bbd83925b72c1e3f522 -msgid "" -":vytask:`T2683` (default): no dual stack in system static-host-mapping host-" -"name" -msgstr "" - -#: ../../changelog/1.4.rst:492 e85aa1b04960420dbc50a36cde9bf27c -msgid ":vytask:`T478` (feature): Firewall address group (multi and nesting)" -msgstr "" - -#: ../../changelog/1.4.rst:496 66f9515ec9a7410ebfbdb2abd0463e26 -msgid "2022-07-04" -msgstr "" - -#: ../../changelog/1.4.rst:498 75ba95bc119b4f29a167b399ac22f0f8 -msgid "" -":vytask:`T4501` (bug): Syslog-identifier does not work in event handler" -msgstr "" - -#: ../../changelog/1.4.rst:499 1aefbfe0ab134389bd4a283bfb0c0aab -msgid ":vytask:`T3600` (bug): DHCP Interface static route breaks PBR" -msgstr "" - -#: ../../changelog/1.4.rst:500 769ac14b5e3d454d808a77419129755a -msgid "" -":vytask:`T4498` (feature): bridge: Add option to enable/disable IGMP/MLD " -"snooping" -msgstr "" - -#: ../../changelog/1.4.rst:504 32fff00c7d014743845f4c8607cecfa4 -msgid "2022-07-01" -msgstr "" - -#: ../../changelog/1.4.rst:506 8333cbb2a9824871b7a19ab2370001c5 -msgid ":vytask:`T2455` (bug): No support for the IPv6 VTI" -msgstr "" - -#: ../../changelog/1.4.rst:507 92855f2b97c942cc86759932bc90fbcb -msgid "" -":vytask:`T4490` (feature): BGP- warning message that AFI/SAFI is needed to " -"establish the neighborship" -msgstr "" - -#: ../../changelog/1.4.rst:508 597f73112d124f72b79e00b48ed225b0 -msgid "" -":vytask:`T4489` (bug): MPLS sysctl not persistent for tunnel interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:512 e8821f28f5f74fdbb4090ffde120af01 -msgid "2022-06-29" -msgstr "" - -#: ../../changelog/1.4.rst:514 706866a0ceb547188def40a8431b1b64 -msgid "" -":vytask:`T4477` (feature): router-advert: support RDNSS lifetime option" -msgstr "" - -#: ../../changelog/1.4.rst:518 92da9b1160fc4c0c94ca4e4f8ba3ad88 -msgid "2022-06-28" -msgstr "" - -#: ../../changelog/1.4.rst:520 6eec8643673d4308ac1cc0a805a4caa6 -msgid ":vytask:`T4486` (bug): Container can't be deleted" -msgstr "" - -#: ../../changelog/1.4.rst:521 8eac7a0cf202426cb5078f93de5cba2b -msgid "" -":vytask:`T4473` (bug): Use container network without network declaration " -"error" -msgstr "" - -#: ../../changelog/1.4.rst:522 c292ed76f3254cfa86e6102e7ca8e1a8 -msgid "" -":vytask:`T4458` (feature): Firewall - add support for matching ip ttl in " -"firewall rules" -msgstr "" - -#: ../../changelog/1.4.rst:523 b61e8bdeff824536ba2324eab7955c4e -msgid ":vytask:`T3907` (feature): Firewall - Set log levels" -msgstr "" - -#: ../../changelog/1.4.rst:527 660ca9d079d2403aa8bacb91229f0adf -msgid "2022-06-27" -msgstr "" - -#: ../../changelog/1.4.rst:529 369cdd22a45c484886ed677b863b5883 -msgid "" -":vytask:`T4484` (default): Firewall op-mode summary doesn't correctly handle" -" address group containing ranges" -msgstr "" - -#: ../../changelog/1.4.rst:533 605e3904c91f4062b6efbd58886daec5 -msgid "2022-06-25" -msgstr "" - -#: ../../changelog/1.4.rst:535 a28d11abffcb4f2fa44f779b4e779b90 -msgid "" -":vytask:`T4482` (bug): dhcp: toggle of \"dhcp-options no-default-route\" has" -" no effect" -msgstr "" - -#: ../../changelog/1.4.rst:536 a437262b49064e75b8730d3bfaf1b3c2 -msgid "" -":vytask:`T4483` (feature): Upgrade fastnetmon to v1.2.2 community edition" -msgstr "" - -#: ../../changelog/1.4.rst:540 44aa10ab0118410e8d3d96613b8adeab -msgid "2022-06-22" -msgstr "" - -#: ../../changelog/1.4.rst:542 d21c7fed72414d769a0d209d1ca26b8b -msgid "" -":vytask:`T1748` (feature): vbash: beautify tab completion output/line breaks" -msgstr "" - -#: ../../changelog/1.4.rst:546 ef0a2a6263b44a5687f9249f4dd719e3 -msgid "2022-06-20" -msgstr "" - -#: ../../changelog/1.4.rst:548 0e61bc4d3da8430e9ef43f1e931ba4ef -msgid ":vytask:`T1856` (feature): Support configuring IPSec SA bytes" -msgstr "" - -#: ../../changelog/1.4.rst:552 d5009d1588da4443bcfa79780a6ff8ce -msgid "2022-06-18" -msgstr "" - -#: ../../changelog/1.4.rst:554 511abd49eed34d5d8d863e1cb02e6e55 -msgid ":vytask:`T4467` (bug): Validator Does Not Accept Signed Numbers" -msgstr "" - -#: ../../changelog/1.4.rst:558 be4c2835b2034e05a6d65e7176e941a3 -msgid "2022-06-17" -msgstr "" - -#: ../../changelog/1.4.rst:560 a4865cd4b35743deba36d3d7854ffbda -msgid "" -":vytask:`T4209` (bug): Firewall incorrect handler for recent count and time" -msgstr "" - -#: ../../changelog/1.4.rst:564 fc3c39a937e04abfb8bf5534b6abe8dc -msgid "2022-06-16" -msgstr "" - -#: ../../changelog/1.4.rst:566 8fd0df766e624a4b8a89f9a19e8b6479 -msgid "" -":vytask:`T4352` (bug): wan-load balance - priority traffic rule doesn't work" -msgstr "" - -#: ../../changelog/1.4.rst:570 627f81d43b234b3183d2b64a6eee57ca -msgid "2022-06-15" -msgstr "" - -#: ../../changelog/1.4.rst:572 6c8c0e1453dd4b70880041aa3cf99cf8 -msgid "" -":vytask:`T4450` (feature): Route-map - Extend options for ip|ipv6 address " -"match" -msgstr "" - -#: ../../changelog/1.4.rst:573 22abb6c1b5944030bf35357933c1aff3 -msgid "" -":vytask:`T4449` (feature): Route-map - Extend options for ip next-hop match" -msgstr "" - -#: ../../changelog/1.4.rst:574 ef407e26c9294397944dfff65551b140 -msgid "" -":vytask:`T990` (feature): Make DNAT/SNAT a valid state in firewall rules." -msgstr "" - -#: ../../changelog/1.4.rst:578 9dd53dbd296c4a78a35ee50a68da04af -msgid "2022-06-12" -msgstr "" - -#: ../../changelog/1.4.rst:580 75098f7808474421822e3fc5236934ec -msgid "" -":vytask:`T4420` (feature): Feature Request: ocserv: show configured 2FA OTP " -"key" -msgstr "" - -#: ../../changelog/1.4.rst:581 1b3dcb75505e496ab0efe1d48aa717e3 -msgid "" -":vytask:`T4380` (default): Feature Request: ocserv: 2FA OTP key generator in" -" VyOS CLI" -msgstr "" - -#: ../../changelog/1.4.rst:585 5f146e3f70ac4a11ac7b706cc3dcc058 -msgid "2022-06-10" -msgstr "" - -#: ../../changelog/1.4.rst:587 e8a4e17d7bc94449be2a5c6907b68935 -msgid ":vytask:`T4365` (bug): NAT - Error on setting up tables" -msgstr "" - -#: ../../changelog/1.4.rst:588 82643c73ae4342da9ba8fa41e50e1775 -msgid "" -":vytask:`T4465` (feature): node.def generation misses whitespace on multiple" -" use of <path>" -msgstr "" - -#: ../../changelog/1.4.rst:592 f4814d51dcc140008c2d76aa099fc38c -msgid "2022-06-09" -msgstr "" - -#: ../../changelog/1.4.rst:594 d7e77330522a48f79e99763ae23b30b5 -msgid "" -":vytask:`T4444` (default): sstp: Feature request. Port number changing " -"support" -msgstr "" - -#: ../../changelog/1.4.rst:595 02a42c43d48e43c4b9f890b183fe9a00 -msgid ":vytask:`T2580` (feature): Support for ip pools for ippoe" -msgstr "" - -#: ../../changelog/1.4.rst:599 eb82d69da87a492faf64a9a7528b8d13 -msgid "2022-06-08" -msgstr "" - -#: ../../changelog/1.4.rst:601 b4e5f566745a45049f465bcb03deeb4f -msgid "" -":vytask:`T4447` (bug): DHCPv6 prefix delegation `sla-id` limited to 128" -msgstr "" - -#: ../../changelog/1.4.rst:605 28cb6a62de2b497d9659215cbe7edf8f -msgid "2022-05-31" -msgstr "" - -#: ../../changelog/1.4.rst:607 ab7a70e1b57f4f1b929521ed240fdbc4 -msgid "" -":vytask:`T4212` (default): PermissionError when generating/installing server" -" Certificate (generate pki certificate sign ...)" -msgstr "" - -#: ../../changelog/1.4.rst:608 76f897402db64024a242ad2398a53a41 -msgid ":vytask:`T4199` (bug): Commit failed when setting icmpv6 type any" -msgstr "" - -#: ../../changelog/1.4.rst:609 56bd1dabab984b2596864a9b9b9de5a5 -msgid "" -":vytask:`T4148` (bug): Firewall - Error messages not that clear as it were " -"in old firewall" -msgstr "" - -#: ../../changelog/1.4.rst:610 edb91ddc4f0e41379182b7503d3a08b0 -msgid "" -":vytask:`T3659` (bug): Configuration won't accept IPv6 addresses for site-" -"to-site VPN tunnel prefixes/traffic selectors" -msgstr "" - -#: ../../changelog/1.4.rst:614 c287307fefd1444c8af9f76ec7027c5a -msgid "2022-05-30" -msgstr "" - -#: ../../changelog/1.4.rst:616 fc6afa5c72f1439f8de52e1313a06844 -msgid ":vytask:`T4315` (feature): Telegraf - Output to prometheus" -msgstr "" - -#: ../../changelog/1.4.rst:620 1e9a28cc4b354c82a1d8a9aca697aaa4 -msgid "2022-05-29" -msgstr "" - -#: ../../changelog/1.4.rst:622 e1b1e6d1f37c4c32bdb7e7fc936b3233 -msgid ":vytask:`T2473` (feature): Xml for EIGRP [conf_mode]" -msgstr "" - -#: ../../changelog/1.4.rst:626 1f465652c2e74429b33d421508c1c10b -msgid "2022-05-28" -msgstr "" - -#: ../../changelog/1.4.rst:628 68fae881063f4f77aed8d66e174dbf36 -msgid "" -":vytask:`T4448` (feature): rip: add support for explicit version selection" -msgstr "" - -#: ../../changelog/1.4.rst:632 077e5b46af8d4726a02d503facc3a423 -msgid "2022-05-26" -msgstr "" - -#: ../../changelog/1.4.rst:634 df02e3c3d0f742609ec5eee18ad4c036 -msgid ":vytask:`T4442` (feature): HTTP API add action \"reset\"" -msgstr "" - -#: ../../changelog/1.4.rst:638 84cb5ae5ebc44e86af7935f53803a937 -msgid "2022-05-25" -msgstr "" - -#: ../../changelog/1.4.rst:640 79f23bd9eb404dc79c34cb3d1f2d48cb -msgid ":vytask:`T4410` (feature): Telegraf - Output to Splunk" -msgstr "" - -#: ../../changelog/1.4.rst:641 ea290959c97746df80121ab186462719 -msgid "" -":vytask:`T4382` (bug): Replacing legacy loadFile exposes missing steps in " -"migration scripts and other errors" -msgstr "" - -#: ../../changelog/1.4.rst:645 40ad9898ad3a45279ed9b59fb70a50c0 -msgid "2022-05-21" -msgstr "" - -#: ../../changelog/1.4.rst:647 56fe3edb58074ccf96d9348222ceb1bf -msgid ":vytask:`T4437` (bug): flow-accounting: support IPv6 flow collectors" -msgstr "" - -#: ../../changelog/1.4.rst:651 5b9b103dcc07448ea7f362347236ae1f -msgid "2022-05-20" -msgstr "" - -#: ../../changelog/1.4.rst:653 5ba3250564754a748db441b4566117b8 -msgid "" -":vytask:`T4418` (feature): Telegraf - output Plugin azure-data-explorer" -msgstr "" - -#: ../../changelog/1.4.rst:657 2d2dad5fce924d8dabe8f5859b0f0978 -msgid "2022-05-19" -msgstr "" - -#: ../../changelog/1.4.rst:659 6de54511136542c48327ddfb9ecf8317 -msgid "" -":vytask:`T4434` (bug): DMVPN: cisco-authentication password length is 8 " -"characters" -msgstr "" - -#: ../../changelog/1.4.rst:660 575363a71fc441dda2c5f9ed280c86b2 -msgid "" -":vytask:`T3938` (default): Rewrite the uptime script in Python to allow " -"using it as a library" -msgstr "" - -#: ../../changelog/1.4.rst:661 22565cb8b3d54af6976b5cc9511cbfd5 -msgid ":vytask:`T4334` (default): Make the config lexer reentrant" -msgstr "" - -#: ../../changelog/1.4.rst:665 ae208cff8e7d487aa4641063dd4e68b2 -msgid "2022-05-17" -msgstr "" - -#: ../../changelog/1.4.rst:667 e2a52981bfea4547ac8a003c0213bed0 -msgid ":vytask:`T4424` (bug): policy local-route6 shows ipv4 format" -msgstr "" - -#: ../../changelog/1.4.rst:671 462e7509e74b4f8fbb6f48b42aaaa948 -msgid "2022-05-16" -msgstr "" - -#: ../../changelog/1.4.rst:673 9a9fca7a6cb24a95bba96b6b5dd44e81 -msgid "" -":vytask:`T4377` (default): generate tech-support archive includes previous " -"archives" -msgstr "" - -#: ../../changelog/1.4.rst:677 5afd893ff394497bbb8f54629daa0600 -msgid "2022-05-12" -msgstr "" - -#: ../../changelog/1.4.rst:679 52ccb12a709c4c2c9c023a62514350bb -msgid ":vytask:`T4417` (bug): VRRP doesn't start with conntrack-sync" -msgstr "" - -#: ../../changelog/1.4.rst:680 932fb16140b44115bbc7891fda398773 -msgid ":vytask:`T4100` (feature): Firewall increase maximum number of rules" -msgstr "" - -#: ../../changelog/1.4.rst:684 c9532d0390bd486998cf68495cffe4f9 -msgid "2022-05-11" -msgstr "" - -#: ../../changelog/1.4.rst:686 8dccf4556dd04e9694a32849e4eb975b -msgid "" -":vytask:`T4405` (bug): DHCP client sometimes ignores `no-default-route` " -"option of an interface" -msgstr "" - -#: ../../changelog/1.4.rst:690 d64a0189346745deba54bff3d8ebb15d -msgid "2022-05-10" -msgstr "" - -#: ../../changelog/1.4.rst:692 58bfc487cf8e45558549d1f1b17e1eba -msgid ":vytask:`T4156` (default): Adding DHCP Option 13 (bootfile-size)" -msgstr "" - -#: ../../changelog/1.4.rst:693 e53ef62731cd4ccdb9436e9a84f075f3 -msgid "" -":vytask:`T1972` (feature): Allow setting interface name for " -"virtual_ipaddress in VRRP VRID" -msgstr "" - -#: ../../changelog/1.4.rst:697 83634890f9ce4427bef783b5a8c733fe -msgid "2022-05-07" -msgstr "" - -#: ../../changelog/1.4.rst:699 8b8f4f0144d14f97ad6b3045e8acc7a6 -msgid "" -":vytask:`T4361` (bug): `vyos.config.exists()` does not work for nodes with " -"multiple values" -msgstr "" - -#: ../../changelog/1.4.rst:700 69b490a969e84baeaa88065e7787c26f -msgid "" -":vytask:`T4354` (bug): Slave interfaces fall out from bonding during " -"configuration change" -msgstr "" - -#: ../../changelog/1.4.rst:701 be9bb87d6ecb4b119a711fcc41115202 -msgid "" -":vytask:`T4419` (feature): vrf: support to disable IP forwarding within a " -"given VRF" -msgstr "" - -#: ../../changelog/1.4.rst:705 74a37a077ca14f9abed604771056316b -msgid "2022-05-06" -msgstr "" - -#: ../../changelog/1.4.rst:707 154d70652a0d4b04a9de50711e329d1d -msgid "" -":vytask:`T4385` (bug): bgp: peer-group member cannot override remote-as of " -"peer-group" -msgstr "" - -#: ../../changelog/1.4.rst:711 b0a55c36a9bf4c4cb15d19119062754e -msgid "2022-05-05" -msgstr "" - -#: ../../changelog/1.4.rst:713 c25dd56430be49cdb0440157e7e4946d -msgid "" -":vytask:`T4414` (feature): Add route-map \"as-path prepend last-as x\" " -"option" -msgstr "" - -#: ../../changelog/1.4.rst:717 13ce49abb0f64ee192676be672a4ba85 -msgid "2022-05-03" -msgstr "" - -#: ../../changelog/1.4.rst:719 ee5b872aab3041e69ee8264bf2401f34 -msgid ":vytask:`T4395` (feature): Extend show vpn debug" -msgstr "" - -#: ../../changelog/1.4.rst:723 becbf4c9dcad47e58c13b898e9c58e51 -msgid "2022-05-01" -msgstr "" - -#: ../../changelog/1.4.rst:725 6ca0816863924135b7a5ad01d435a4e6 -msgid "" -":vytask:`T4369` (bug): OpenVPN: daemon not restarted on changes to " -"\"openvpn-option\" CLI node" -msgstr "" - -#: ../../changelog/1.4.rst:726 008c0f707e034f8c86390d1cb317cbc1 -msgid "" -":vytask:`T4363` (bug): salt-minion: default mine_interval option is not set" -msgstr "" - -#: ../../changelog/1.4.rst:727 8eede7e4959f4f0bb9bf3e10322995c3 -msgid ":vytask:`T4353` (feature): Add Jinja2 linter to vyos-1x build process" -msgstr "" - -#: ../../changelog/1.4.rst:731 1a7a0078c7b44360909b5646fcc16f5f -msgid "2022-04-29" -msgstr "" - -#: ../../changelog/1.4.rst:733 e862986cd96c4fecace5b33eef2afd1f -msgid "" -":vytask:`T4388` (bug): dhcp-server: missing constraint on tftp-server-name " -"option" -msgstr "" - -#: ../../changelog/1.4.rst:734 50b0a4660f02477dae1301b31b382371 -msgid "" -":vytask:`T4366` (bug): geneve: interface is removed on changes to e.g. " -"description" -msgstr "" - -#: ../../changelog/1.4.rst:738 a3c55dd9281c4e88961552cb469c40d8 -msgid "2022-04-28" -msgstr "" - -#: ../../changelog/1.4.rst:740 55cfbee75f5b4d9794abbb4591a7b9a8 -msgid "" -":vytask:`T4400` (bug): Container OP mode has delete where show and update " -"should be" -msgstr "" - -#: ../../changelog/1.4.rst:744 897af04f7d4d407184753aa55cc535ed -msgid "2022-04-27" -msgstr "" - -#: ../../changelog/1.4.rst:746 e15f80c50a6a4b72a73f9346964071ec -msgid "" -":vytask:`T4398` (bug): IPSec site-to-site generates unexpected passthrough " -"option" -msgstr "" - -#: ../../changelog/1.4.rst:747 59beb0f05d754582b6bf222fad63a168 -msgid "" -":vytask:`T4397` (feature): arp: migrate static ARP entry configuration to " -"get_config_dict() and make it VRF aware" -msgstr "" - -#: ../../changelog/1.4.rst:748 76ce854e1f9945008544e06da05fd6a8 -msgid "" -":vytask:`T4357` (feature): Allow free-form setting of DHCPv6 server options" -msgstr "" - -#: ../../changelog/1.4.rst:752 475fd2790cce4064bb30579a1a99fb06 -msgid "2022-04-26" -msgstr "" - -#: ../../changelog/1.4.rst:754 27192f927200411e82bb2fd532e146db -msgid "" -":vytask:`T4210` (bug): NAT source/destination negated ports throws an error" -msgstr "" - -#: ../../changelog/1.4.rst:755 34f100dbf0f44d3aa16e241e3f998354 -msgid ":vytask:`T4235` (default): Add config tree diff algorithm" -msgstr "" - -#: ../../changelog/1.4.rst:759 84ce5e71dff54d9eb9be7c7d3292b5b0 -msgid "2022-04-25" -msgstr "" - -#: ../../changelog/1.4.rst:761 8fbe47291de144ac881e2e1173a39d19 -msgid "" -":vytask:`T4390` (feature): op-mode: extend \"show log\" and \"monitor log\" " -"with additional daemons/subsystems to read journalctl logs" -msgstr "" - -#: ../../changelog/1.4.rst:762 42be44da6d7045d78fd3bb7a4bd65f52 -msgid ":vytask:`T4391` (bug): PPPoE: IPv6 not working after system boot" -msgstr "" - -#: ../../changelog/1.4.rst:766 a7add0167fea4fb2967a4b518b3db58f -msgid "2022-04-24" -msgstr "" - -#: ../../changelog/1.4.rst:768 130671c12fbb40cf9f36a540e9f74c79 -msgid "" -":vytask:`T4342` (bug): \"show ip ospf neighbor address x.x.x.x\" gives " -"\"unknown command\" error" -msgstr "" - -#: ../../changelog/1.4.rst:772 e4ef3f1a41924a6b8062a38b80de4b0e -msgid "2022-04-23" -msgstr "" - -#: ../../changelog/1.4.rst:774 86135981d3914e46b81261cfabd819f9 -msgid "" -":vytask:`T4386` (default): Applying limiter on traffic-policy \"in\" fails, " -"incorrectly reports mirror or redirect policy in use" -msgstr "" - -#: ../../changelog/1.4.rst:778 e69119b6e27247618de49e3ad271b1f7 -msgid "2022-04-22" -msgstr "" - -#: ../../changelog/1.4.rst:780 2834f302efa74dc69c85f68bb6d49261 -msgid "" -":vytask:`T4389` (feature): dhcp: add vendor option support for Ubiquity " -"Unifi controller" -msgstr "" - -#: ../../changelog/1.4.rst:784 d8f23e4fb5654a0e9c3d5467dd308d5b -msgid "2022-04-21" -msgstr "" - -#: ../../changelog/1.4.rst:786 ca1b7fa5ddb84a5890aaccbf01456c8b -msgid "" -":vytask:`T4384` (feature): pppoe: replace default-route CLI option with " -"common CLI nodes already present for DHCP" -msgstr "" - -#: ../../changelog/1.4.rst:790 0fabbeb85d8e438ba4dccf3ddc157c55 -msgid "2022-04-20" -msgstr "" - -#: ../../changelog/1.4.rst:792 11f2411f535b41d4b3ff9d4a33640f66 -msgid "" -":vytask:`T4345` (bug): New firewall code does not accept \"rate/time " -"interval\" syntax used in old config" -msgstr "" - -#: ../../changelog/1.4.rst:793 0752e970a59c45448a59438555bd0818 -msgid "" -":vytask:`T4231` (feature): Feature Request: ocserv: 2FA (password+OTP) " -"support in Openconnect" -msgstr "" - -#: ../../changelog/1.4.rst:797 3d40805026eb40ff88a41c1bed32136c -msgid "2022-04-19" -msgstr "" - -#: ../../changelog/1.4.rst:799 a2a453413deb45f1996a7c675b5e96fb -msgid "" -":vytask:`T4379` (bug): PPPoE: default-route lost after applying additional " -"static routes" -msgstr "" - -#: ../../changelog/1.4.rst:800 3551e1fc8a3b48109989d94a9991d41d -msgid "" -":vytask:`T4344` (bug): DHCP statistics not matching, conf-mode generates " -"incorrect pool name with dash" -msgstr "" - -#: ../../changelog/1.4.rst:801 1e17aefc48054bd8b304d0e690d98fd3 -msgid ":vytask:`T4268` (bug): Elevated LA while using VyOS monitoring feature" -msgstr "" - -#: ../../changelog/1.4.rst:805 045293efa739480abfb9f87c7d5914ba -msgid "2022-04-18" -msgstr "" - -#: ../../changelog/1.4.rst:807 8edd0bb8480146368fc5c30b17b86631 -msgid "" -":vytask:`T4351` (bug): Openvpn conf-mode \"openvpn-option\" is not respected" -msgstr "" - -#: ../../changelog/1.4.rst:808 cee7ae13a1e84ab0bb9fc6d2fa41878d -msgid ":vytask:`T4278` (default): vyos-vm-images: fix vagrant libvirt box" -msgstr "" - -#: ../../changelog/1.4.rst:809 8a21b9feeba747bf8ee1aa5e707dc4c3 -msgid "" -":vytask:`T4368` (bug): bgp: AS specified for local as is the same as the " -"remote as and this is not allowed." -msgstr "" - -#: ../../changelog/1.4.rst:810 02f2ff737323406f8df7557d25832a2a -msgid "" -":vytask:`T4370` (feature): vxlan: geneve: support configuration of df bit " -"option" -msgstr "" - -#: ../../changelog/1.4.rst:814 17219c4c4f0243f0822d5dffdca20e4f -msgid "2022-04-15" -msgstr "" - -#: ../../changelog/1.4.rst:816 7ba095ba94104e4dbc0bf2271788c216 -msgid "" -":vytask:`T4327` (default): Ethernet interface configuration fails on Hyper-V" -" due to speed/duplex/autoneg ethtool command error" -msgstr "" - -#: ../../changelog/1.4.rst:817 a1a668e9f8f7408a93463f8bce818d0b -msgid "" -":vytask:`T4364` (feature): salt-minion: Upgrade to 3004 and migrate to " -"get_config_dict()" -msgstr "" - -#: ../../changelog/1.4.rst:821 a5a4708729b849b4a50f3f135332dc5d -msgid "2022-04-13" -msgstr "" - -#: ../../changelog/1.4.rst:823 34a4da03b30a4f489a5f489b42286b12 -msgid "" -":vytask:`T4333` (feature): Jinja2: add plugin to test if a variable is " -"defined and not none to reduce template complexity" -msgstr "" - -#: ../../changelog/1.4.rst:827 987058f3439f488192c1edebfa5a907f -msgid "2022-04-08" -msgstr "" - -#: ../../changelog/1.4.rst:829 d753aaaf501b4a408bd77396a386f773 -msgid "" -":vytask:`T4331` (bug): IPv6 link local addresses are not configured when an " -"interface is in a VRF" -msgstr "" - -#: ../../changelog/1.4.rst:830 198e79e3bab54451b43ee901c7b434fc -msgid "" -":vytask:`T4347` (default): Return complete and consistent error codes from " -"HTTP API" -msgstr "" - -#: ../../changelog/1.4.rst:831 44864d413f0942f88445ef266016a70d -msgid "" -":vytask:`T4339` (bug): wwan: tab-completion results in \"No such file or " -"directory\" if there is no WWAN interface" -msgstr "" - -#: ../../changelog/1.4.rst:832 afc5971a34244659bc47aa1b0b70580c -msgid "" -":vytask:`T4338` (bug): wwan: changing interface description should not " -"trigger reconnect" -msgstr "" - -#: ../../changelog/1.4.rst:833 4b1225b9b74942f594fdf421c964aec7 -msgid "" -":vytask:`T4324` (bug): wwan: check alive script should only be run via cron " -"if a wwan interface is configured at all" -msgstr "" - -#: ../../changelog/1.4.rst:837 77f6cfa72c5748dcb57c0f67fa9e69d9 -msgid "2022-04-07" -msgstr "" - -#: ../../changelog/1.4.rst:839 dbe21c5c6eb34920b8ff6d02235ba701 -msgid "" -":vytask:`T4330` (bug): MTU settings cannot be applied when IPv6 is disabled" -msgstr "" - -#: ../../changelog/1.4.rst:840 111c23da645040328316377093042109 -msgid "" -":vytask:`T4346` (feature): Deprecate \"system ipv6 disable\" option to " -"disable address family within OS kernel" -msgstr "" - -#: ../../changelog/1.4.rst:841 11c9ac49ace94614a33e205ee8f0197d -msgid "" -":vytask:`T4319` (bug): The command \"set system ipv6 disable\" doesn't work " -"as expected." -msgstr "" - -#: ../../changelog/1.4.rst:842 e7fc33c0698a491b8d51c339f74a7ce4 -msgid "" -":vytask:`T4341` (feature): login: disable user-account prior to deletion and" -" wait until deletion is complete" -msgstr "" - -#: ../../changelog/1.4.rst:843 6a82b2f656834676bb20ee72372d6055 -msgid "" -":vytask:`T4336` (feature): isis: add support for MD5 authentication password" -" on a circuit" -msgstr "" - -#: ../../changelog/1.4.rst:847 2ac80277253d4b93ada1230884297f98 -msgid "2022-04-06" -msgstr "" - -#: ../../changelog/1.4.rst:849 30e96222f3c94aab9df3e62fdaecf5d2 -msgid "" -":vytask:`T4308` (feature): Op-comm \"Show log frr\" to view specific " -"protocol logs" -msgstr "" - -#: ../../changelog/1.4.rst:853 536c1372f7e14a35973875593483849d -msgid "2022-04-04" -msgstr "" - -#: ../../changelog/1.4.rst:855 1e65dc0305d24651b252250d3d76e6ea -msgid "" -":vytask:`T4329` (bug): Bgp policy route-map bug with set several " -"extcommunity rt" -msgstr "" - -#: ../../changelog/1.4.rst:859 957acf2d45724ccfb1ba388b2a408228 -msgid "2022-04-02" -msgstr "" - -#: ../../changelog/1.4.rst:861 bdddffcebbe04776888fe6cb8d921097 -msgid ":vytask:`T4335` (bug): open-vmdk fails to build under gcc-10.+" -msgstr "" - -#: ../../changelog/1.4.rst:865 b8bbe1962f144da2a3280f44f4886530 -msgid "2022-04-01" -msgstr "" - -#: ../../changelog/1.4.rst:867 f46d6400a48547db9ca02dd2b96fa1ee -msgid "" -":vytask:`T4332` (bug): bgp: deterministic-med cannot be disabled while " -"addpath-tx-bestpath-per-AS is in use" -msgstr "" - -#: ../../changelog/1.4.rst:871 5c4750550f534550b89b03ca295c15c4 -msgid "2022-03-31" -msgstr "" - -#: ../../changelog/1.4.rst:873 fed056f6f1c04fd2b7dc43753e45d1a4 -msgid ":vytask:`T4326` (feature): Add bgp option no-suppress-duplicates" -msgstr "" - -#: ../../changelog/1.4.rst:874 41370cb4b8a94a2791a499c5b51cb8ec -msgid ":vytask:`T4323` (default): ospf6d crashes on latest vyos nightly" -msgstr "" - -#: ../../changelog/1.4.rst:878 150c2461205d44f9a88b236619128cc3 -msgid "2022-03-29" -msgstr "" - -#: ../../changelog/1.4.rst:880 963cfba7515e4a708a47956f10e2bd21 -msgid "" -":vytask:`T3686` (bug): Bridging OpenVPN tap with no local-address breaks" -msgstr "" - -#: ../../changelog/1.4.rst:881 a82d54fe256d496ab944f08ccea1bbee -msgid ":vytask:`T3635` (default): Add ability to use mDNS repeater with VRRP" -msgstr "" - -#: ../../changelog/1.4.rst:885 01d1b4d6feed404cb2acfe30d7dedaf4 -msgid "2022-03-26" -msgstr "" - -#: ../../changelog/1.4.rst:887 47e7948de3e844f1bc657f5bb2524db9 -msgid "" -":vytask:`T4321` (default): Allow BGP neighbors between different VIFs on the" -" same VyOS" -msgstr "" - -#: ../../changelog/1.4.rst:891 cd0f66f7465346cc8315f489fa8d89ad -msgid "2022-03-24" -msgstr "" - -#: ../../changelog/1.4.rst:893 1837635e43e947579f4e75d59fb4bae9 -msgid "" -":vytask:`T4301` (bug): The \"arp-monitor\" option in bonding interface " -"settings does not work" -msgstr "" - -#: ../../changelog/1.4.rst:894 ec481c6043dd4daf8d2c5479d26766ee -msgid "" -":vytask:`T4294` (bug): Adding a new openvpn-option does not restart the " -"OpenVPN process" -msgstr "" - -#: ../../changelog/1.4.rst:895 8a16c90c483b46f28bd1bf3a58762947 -msgid ":vytask:`T4290` (bug): BGP source-interface fails to commit" -msgstr "" - -#: ../../changelog/1.4.rst:896 c29ee1049ded47a5a662abdc32a306c4 -msgid "" -":vytask:`T4230` (bug): OpenVPN server configuration deleted after reboot " -"when using a VRRP virtual-address" -msgstr "" - -#: ../../changelog/1.4.rst:900 c004fb830ae64af198b726154b2c5a41 -msgid "2022-03-23" -msgstr "" - -#: ../../changelog/1.4.rst:902 00aad53cbbeb4c27a52e0fbf4fca1964 -msgid "" -":vytask:`T4314` (bug): Latest 1.4 Rolling release config migration error" -msgstr "" - -#: ../../changelog/1.4.rst:906 8062ad5c8a0f4c499d5f88be8369ba51 -msgid "2022-03-21" -msgstr "" - -#: ../../changelog/1.4.rst:908 1e77a428304b43fda177ed5caabe3b38 -msgid "" -":vytask:`T4304` (feature): [OSPF]import/export filter inter-area prefix" -msgstr "" - -#: ../../changelog/1.4.rst:912 2568f4c8e0ca4c5eb52d15e584e1045f -msgid "2022-03-20" -msgstr "" - -#: ../../changelog/1.4.rst:914 2a0130db29d249a5b562873c43c1e1db -msgid "" -":vytask:`T4298` (default): vyos-vm-images: fix ansible group name and remove" -" obsolete empty command" -msgstr "" - -#: ../../changelog/1.4.rst:918 1b8750ecc7e846fb964723cd0d574608 -msgid "2022-03-18" -msgstr "" - -#: ../../changelog/1.4.rst:920 cd1302d632204864b62d68a21bd6aed4 -msgid ":vytask:`T4286` (bug): Fix for firewall ipv6 name address validator" -msgstr "" - -#: ../../changelog/1.4.rst:924 127d74f2fed44266bfd69039e78eb4ce -msgid "2022-03-15" -msgstr "" - -#: ../../changelog/1.4.rst:926 2be8406468334139a7bf5abecb5997c7 -msgid ":vytask:`T4302` (feature): FRRouting upgrade to release 8.2.2" -msgstr "" - -#: ../../changelog/1.4.rst:927 63f758069c964b9e94de1601714248f2 -msgid ":vytask:`T4293` (default): Add \"set ip-next-hop unchanged\" in route-map" -msgstr "" - -#: ../../changelog/1.4.rst:931 258c615733a5417baf4a9ec87a1a56de -msgid "2022-03-14" -msgstr "" - -#: ../../changelog/1.4.rst:933 e1fb009c5f324ddc9cf1bb6a38d986ce -msgid "" -":vytask:`T4275` (default): Incorrect val_help for local/remote prefix in " -"ipsec vpn" -msgstr "" - -#: ../../changelog/1.4.rst:937 59d2b0fc123c458a8486523b32568027 -msgid "2022-03-12" -msgstr "" - -#: ../../changelog/1.4.rst:939 14557b85f3c64bd5ac3041af3eca0ff2 -msgid "" -":vytask:`T4296` (bug): Interface config injected by Cloud-Init may interfere" -" with VyOS native" -msgstr "" - -#: ../../changelog/1.4.rst:940 48d581de07f2434cab2ea4cec0504802 -msgid "" -":vytask:`T4265` (feature): Add op-mode for bgp flowspec state and routes" -msgstr "" - -#: ../../changelog/1.4.rst:944 e974074fed424abf97784bb4c1041caa -msgid "2022-03-11" -msgstr "" - -#: ../../changelog/1.4.rst:946 f3dc3fd3d53c4da2a5df69d57c4cb995 -msgid "" -":vytask:`T4297` (bug): Interface configuration saving fails for ice/iavf " -"based interfaces because they can't change speed/duplex settings" -msgstr "" - -#: ../../changelog/1.4.rst:950 2230b5c49c2843a0895262d1122b99b3 -msgid "2022-03-09" -msgstr "" - -#: ../../changelog/1.4.rst:952 e96f920045c94147bb64c318826af362 -msgid ":vytask:`T3981` (feature): VRF support for flow-accounting" -msgstr "" - -#: ../../changelog/1.4.rst:956 44f3c0dbd10942da9fc93160111a59ef -msgid "2022-03-05" -msgstr "" - -#: ../../changelog/1.4.rst:958 18b70b1571fa4bf99305b20989b91b3e -msgid ":vytask:`T4259` (bug): The conntrackd daemon can be started wrongly" -msgstr "" - -#: ../../changelog/1.4.rst:962 7218308d9f5045fe8dff36ebab834527 -msgid "2022-03-03" -msgstr "" - -#: ../../changelog/1.4.rst:964 753cd03d8775448f9a076dca12cc400a -msgid "" -":vytask:`T4283` (feature): Add support to \"reject\" routes - emit an ICMP " -"unreachable when matched" -msgstr "" - -#: ../../changelog/1.4.rst:968 97f2d1ef305c48d08f9061ca7f7bbc3d -msgid "2022-03-01" -msgstr "" - -#: ../../changelog/1.4.rst:970 f09cf50b377045fba302ea9d46ac0b8f -msgid "" -":vytask:`T4277` (feature): flow-accounting: support sending flow-data via " -"VRF interface" -msgstr "" - -#: ../../changelog/1.4.rst:974 8fd14b29d23f4896b1e34829862c5279 -msgid "2022-02-28" -msgstr "" - -#: ../../changelog/1.4.rst:976 bf646b21055f48da85e7325be4acc81c -msgid ":vytask:`T4273` (bug): ssh: Upgrade from 1.2.X to 1.3.0 breaks config" -msgstr "" - -#: ../../changelog/1.4.rst:977 281990646c2d4723a19ae31876bb26ac -msgid ":vytask:`T4115` (bug): reboot in <x> not working as expected" -msgstr "" - -#: ../../changelog/1.4.rst:978 3e94afa81e7349eda87b9d973912fd35 -msgid "" -":vytask:`T3656` (bug): IPSec 1.4 : \"show vpn ike sa\" does not show the " -"correct default ike version" -msgstr "" - -#: ../../changelog/1.4.rst:982 41ca638cb9a341a2b6a096ca5a13a8cc -msgid "2022-02-26" -msgstr "" - -#: ../../changelog/1.4.rst:984 d91cb1dda80c43dfb9b2563d6f99cdeb -msgid "" -":vytask:`T4272` (feature): lldp: migrate Python script to use " -"get_config_dict()" -msgstr "" - -#: ../../changelog/1.4.rst:988 ceff51819c7c4b97a6ed8ced07884fd4 -msgid "2022-02-25" -msgstr "" - -#: ../../changelog/1.4.rst:990 392439e699a9442783f2ea672f4efeb6 -msgid "" -":vytask:`T4269` (feature): node.def generator should automatically add " -"default values" -msgstr "" - -#: ../../changelog/1.4.rst:994 567f1e168e484df6a72fa749cd2fbf1c -msgid "2022-02-24" -msgstr "" - -#: ../../changelog/1.4.rst:996 49587d98392b479db24fa5dd7cd55af9 -msgid ":vytask:`T4267` (bug): Error - Missing required \"ip key\" parameter" -msgstr "" - -#: ../../changelog/1.4.rst:1000 ff5e01058e234f4ab3bb478c1937587e -msgid "2022-02-23" -msgstr "" - -#: ../../changelog/1.4.rst:1002 b90c94b816244af3b23181197fcd24be -msgid ":vytask:`T4194` (bug): prefix-list no check for duplicate entries" -msgstr "" - -#: ../../changelog/1.4.rst:1003 cd3e8db4f4ef48c3abc58c6ddc5d07dc -msgid "" -":vytask:`T4264` (bug): vxlan: interface is destroyed and rebuild on " -"description change" -msgstr "" - -#: ../../changelog/1.4.rst:1004 7e155be49d4d46ed82b27117ef4e851c -msgid "" -":vytask:`T4263` (bug): vyos.util.leaf_node_changed() dos not honor valueLess" -" nodes" -msgstr "" - -#: ../../changelog/1.4.rst:1008 29a3aaa558d645c3b24e6a46ae95b25c -msgid "2022-02-21" -msgstr "" - -#: ../../changelog/1.4.rst:1010 08b351a1b055437e9c759b68ca939058 -msgid "" -":vytask:`T4120` (feature): [VXLAN] add ability to set multiple unicast-" -"remotes" -msgstr "" - -#: ../../changelog/1.4.rst:1014 2e97720d18c5468592d7c549736b8552 -msgid "2022-02-20" -msgstr "" - -#: ../../changelog/1.4.rst:1016 5a83201413f04cb08f37d423739b33d9 -msgid "" -":vytask:`T4254` (feature): VPN IPSec charon add options cisco_flexvpn and " -"install_virtual_ip_on" -msgstr "" - -#: ../../changelog/1.4.rst:1017 46c44e08d60145c1a217cdd5b5614b53 -msgid "" -":vytask:`T4249` (feature): Add support for device mapping in containers" -msgstr "" - -#: ../../changelog/1.4.rst:1018 0700e719f21e4fb1a0d7f15081bb0a84 -msgid ":vytask:`T3617` (bug): IPSec 1.4 generate invalid configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1019 f3ecb3e5103e4cafba61dcd61e193b1d -msgid ":vytask:`T4261` (feature): MACsec: add DHCP client support" -msgstr "" - -#: ../../changelog/1.4.rst:1020 34b47a7d928b45c38716908008078c93 -msgid "" -":vytask:`T4203` (bug): Reconfigure DHCP client interface causes brief " -"outages" -msgstr "" - -#: ../../changelog/1.4.rst:1024 61799306459e40cc912176579b71be21 -msgid "2022-02-19" -msgstr "" - -#: ../../changelog/1.4.rst:1026 3f853428f7c947399416e41560680c22 -msgid ":vytask:`T4258` (bug): [DHCP-SERVER] error parameter on Failover" -msgstr "" - -#: ../../changelog/1.4.rst:1030 5a141c8fd41246e6b24376b8f0fc3003 -msgid "2022-02-17" -msgstr "" - -#: ../../changelog/1.4.rst:1032 af9a9432644145f28963be766e696904 -msgid ":vytask:`T4255` (bug): Unexpected print of dict bridge on delete" -msgstr "" - -#: ../../changelog/1.4.rst:1033 cfbe5e725a9c4937b3a22994128fd76c -msgid ":vytask:`T4240` (bug): Cannot add wlan0 to bridge via configure" -msgstr "" - -#: ../../changelog/1.4.rst:1034 081573c415da45e29e239b1e9ccd3b29 -msgid "" -":vytask:`T4154` (bug): Error add second gre tunnel with the same source " -"interface" -msgstr "" - -#: ../../changelog/1.4.rst:1038 98496fad4dd4484d845281e7e6d5b294 -msgid "2022-02-16" -msgstr "" - -#: ../../changelog/1.4.rst:1040 d70525021d9d4aa2ad2310c112839ca1 -msgid "" -":vytask:`T4237` (bug): Conntrack-sync error - error adding listen-address " -"command" -msgstr "" - -#: ../../changelog/1.4.rst:1044 9dfcaded1cfc4831ad91bdbc116958dd -msgid "2022-02-15" -msgstr "" - -#: ../../changelog/1.4.rst:1046 97f6d6501fd84667baf49a83e7e55621 -msgid "" -":vytask:`T4160` (bug): Firewall - Error in rules that matches everything " -"except something" -msgstr "" - -#: ../../changelog/1.4.rst:1047 c088035e700d4d94846a3e503a6392b3 -msgid ":vytask:`T3006` (bug): Accel-PPP & vlan-mon config get invalid VLAN" -msgstr "" - -#: ../../changelog/1.4.rst:1048 478ee26481f2458e85e76d93ada94de7 -msgid ":vytask:`T3494` (bug): DHCPv6 leases traceback when PD using" -msgstr "" - -#: ../../changelog/1.4.rst:1049 69a4719db9d744e889e563ef21dfad5c -msgid ":vytask:`T1292` (bug): Issues while deleting all rules from a firewall" -msgstr "" - -#: ../../changelog/1.4.rst:1053 63f30055f9164a5ea21f089942b47e29 -msgid "2022-02-13" -msgstr "" - -#: ../../changelog/1.4.rst:1055 bbefddd7b90341ce8835465dd11d7484 -msgid "" -":vytask:`T4242` (bug): ethernet speed/duplex can never be switched back to " -"auto/auto" -msgstr "" - -#: ../../changelog/1.4.rst:1056 b7cc8a1b318547d382e4a322ba1433ba -msgid ":vytask:`T4191` (bug): Lost access to host after VRF re-creating" -msgstr "" - -#: ../../changelog/1.4.rst:1060 058045002a424369a772f7c8225fe402 -msgid "2022-02-11" -msgstr "" - -#: ../../changelog/1.4.rst:1062 b22580f72e434c9083abeba795135e8d -msgid "" -":vytask:`T3872` (feature): Add configurable telegraf monitoring service" -msgstr "" - -#: ../../changelog/1.4.rst:1066 93e183cbf8f64661b630d19ca8c881c2 -msgid "2022-02-08" -msgstr "" - -#: ../../changelog/1.4.rst:1068 8ecbc34237194fc4a4980c528a86b453 -msgid "" -":vytask:`T4227` (bug): Typo in help completion of hello-time option of " -"bridge interface" -msgstr "" - -#: ../../changelog/1.4.rst:1072 46f243eaac4848b9ae2ad3e3462e42fb -msgid "2022-02-07" -msgstr "" - -#: ../../changelog/1.4.rst:1074 69d53c39d20b44d1a6b23c5666ce6b32 -msgid "" -":vytask:`T4233` (bug): ssh: sync regex for allow/deny usernames to \"system " -"login\"" -msgstr "" - -#: ../../changelog/1.4.rst:1078 e43671cec99a4f8ca6ca9858cd6b364d -msgid "2022-02-06" -msgstr "" - -#: ../../changelog/1.4.rst:1080 34c0f4b182f24cde9636dbed3d46822b -msgid "" -":vytask:`T4223` (bug): policy route cannot have several entries with the " -"same table" -msgstr "" - -#: ../../changelog/1.4.rst:1081 426fbf26931948b4a45a264807b29ad4 -msgid "" -":vytask:`T4216` (bug): Firewall: can't use negated groups in firewall rules" -msgstr "" - -#: ../../changelog/1.4.rst:1082 b3cacd8851a84a7cadcb32a232229df0 -msgid ":vytask:`T4178` (bug): policy based routing tcp flags issue" -msgstr "" - -#: ../../changelog/1.4.rst:1083 d3f587a87a89451698ec842f56d784f0 -msgid "" -":vytask:`T4164` (bug): PBR: network groups (as well as address and port " -"groups) don't resolve in `nftables_policy.conf`" -msgstr "" - -#: ../../changelog/1.4.rst:1084 15a7b97da5d741f78eb27190aa730440 -msgid "" -":vytask:`T3970` (feature): Add support for op-mode PKI direct install into " -"an active config session" -msgstr "" - -#: ../../changelog/1.4.rst:1085 47087580c21349748341362077590407 -msgid "" -":vytask:`T3828` (bug): ipsec: Subtle change in \"pfs enable\" behavior from " -"equuleus -> sagitta" -msgstr "" - -#: ../../changelog/1.4.rst:1089 747053ff76d74282b5056d4d2269e746 -msgid "2022-02-05" -msgstr "" - -#: ../../changelog/1.4.rst:1091 2a4afabcc38148b28985d4bd7865a6b9 -msgid "" -":vytask:`T4226` (bug): VRRP transition-script does not work for groups name " -"which contains -(minus) sign" -msgstr "" - -#: ../../changelog/1.4.rst:1095 d2c5ea38e89c4106b857aa92193b48ec -msgid "2022-02-04" -msgstr "" - -#: ../../changelog/1.4.rst:1097 57e50e8397314fe09e349ab92df7592d -msgid "" -":vytask:`T4196` (bug): DHCP server client-prefix-length parameter results in" -" non-functional leases" -msgstr "" - -#: ../../changelog/1.4.rst:1101 6beb2714bb1243faaee192c6c3fd23fa -msgid "2022-02-03" -msgstr "" - -#: ../../changelog/1.4.rst:1103 07a19f3356c1485c9f53761abf0ab74e -msgid "" -":vytask:`T4218` (bug): firewall: rule name is not allowed to start with a " -"number" -msgstr "" - -#: ../../changelog/1.4.rst:1104 2a11be1c07bb482ca099155865b1aec8 -msgid "" -":vytask:`T3643` (bug): show vpn ipsec sa doesn't show tunnels in \"down\" " -"state" -msgstr "" - -#: ../../changelog/1.4.rst:1108 6e190371788d4a778e6913bc92f918df -msgid "2022-02-01" -msgstr "" - -#: ../../changelog/1.4.rst:1110 92900a456ecd46b9a0544eb45f506633 -msgid "" -":vytask:`T4224` (bug): Ethernet interfaces configured for DHCP not working " -"on latest rolling snapshot (vyos-1.4-rolling-202201291849-amd64.iso)" -msgstr "" - -#: ../../changelog/1.4.rst:1111 c06370441dc04a8b8e546232f66f3d1c -msgid "" -":vytask:`T4225` (bug): Performance degration with latest rolling release" -msgstr "" - -#: ../../changelog/1.4.rst:1112 28bd26fa8e6d49d18470a575305b0082 -msgid "" -":vytask:`T4220` (bug): Commit broke dhclient " -"78b247b724f74bdabab0706aaa7f5b00e5809bc1" -msgstr "" - -#: ../../changelog/1.4.rst:1113 437d4e7a56834e10b1b51d2f46333907 -msgid "" -":vytask:`T4138` (bug): NAT configuration allows to set incorrect port range " -"and invalid port" -msgstr "" - -#: ../../changelog/1.4.rst:1117 dd39f943342c4b799b2abaa198090e9d -msgid "2022-01-29" -msgstr "" - -#: ../../changelog/1.4.rst:1119 7b5aa0e0d7b54452ae4852b159b72f2f -msgid ":vytask:`T4153` (bug): Monitor bandwidth-test initiate not working" -msgstr "" - -#: ../../changelog/1.4.rst:1123 0caeb36f19ba4232a4e57ebc35f54ee0 -msgid "2022-01-28" -msgstr "" - -#: ../../changelog/1.4.rst:1125 2f2fcc1d656b49018c508590640e80e6 -msgid "" -":vytask:`T4184` (bug): NTP allow-clients address doesn't work it allows to " -"use ntp server for all addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1126 28205701d30d4cffb3b89791ba2ae7a1 -msgid "" -":vytask:`T4217` (bug): firewall: port-group requires protocol to be set - " -"but not in VyOS 1.3" -msgstr "" - -#: ../../changelog/1.4.rst:1130 bcc72250a88b4464a936a90c68f471c5 -msgid "2022-01-27" -msgstr "" - -#: ../../changelog/1.4.rst:1132 c8c79433ef294396b7a43c60d0e5059f -msgid ":vytask:`T4213` (default): ipv6 policy routing not working anymore" -msgstr "" - -#: ../../changelog/1.4.rst:1133 9bab94afa6b44a669b35d7af8f8fce82 -msgid ":vytask:`T4188` (bug): Firewall does not correctly handle conntracking" -msgstr "" - -#: ../../changelog/1.4.rst:1134 fd3334c640784b9c983d9f9db3c9f423 -msgid "" -":vytask:`T3762` (feature): Support network and address groups for policy " -"ipv6-route" -msgstr "" - -#: ../../changelog/1.4.rst:1135 d86da89c20c14feea82b2528047dea27 -msgid ":vytask:`T3560` (feature): Ability to create groups of MAC addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1136 d2aa00c6757048a683f8a43a009412a8 -msgid ":vytask:`T3495` (feature): Modernising port/protocol definitions" -msgstr "" - -#: ../../changelog/1.4.rst:1140 23841881ff754772815600298654324d -msgid "2022-01-25" -msgstr "" - -#: ../../changelog/1.4.rst:1142 80ba9bdd8c364ce59a0e3dacf263ec3e -msgid "" -":vytask:`T4205` (feature): Disable Debian Version in SSH (DebianBanner->no)" -msgstr "" - -#: ../../changelog/1.4.rst:1143 d654398037d844939c7f71a6b64371f8 -msgid ":vytask:`T4131` (bug): Show firewall group incorrect format members" -msgstr "" - -#: ../../changelog/1.4.rst:1147 6127227df6254619bda2e55901a2856b -msgid "2022-01-24" -msgstr "" - -#: ../../changelog/1.4.rst:1149 e8f99906a59e4e60a5369ad5f849a8a4 -msgid ":vytask:`T4204` (feature): Update Accel-PPP to a newer revision" -msgstr "" - -#: ../../changelog/1.4.rst:1150 118975de0a5a4c389d281f3ad95ab44f -msgid ":vytask:`T1795` (default): Commit rollback by timeout" -msgstr "" - -#: ../../changelog/1.4.rst:1154 5024e1af3e7f4bb3bd1a024f0e8aa401 -msgid "2022-01-23" -msgstr "" - -#: ../../changelog/1.4.rst:1156 9d05750daa024b8f8ea754c9a7fcde1d -msgid "" -":vytask:`T4186` (bug): Firewall icmp type - Offered options not supported" -msgstr "" - -#: ../../changelog/1.4.rst:1157 b8598f7020b047e3bf12248bddb369c8 -msgid "" -":vytask:`T4181` (bug): Firewall ipv6-network-group - incorrect description " -"on helper" -msgstr "" - -#: ../../changelog/1.4.rst:1161 8c7aebaeb2fa433595d9645186f00c27 -msgid "2022-01-22" -msgstr "" - -#: ../../changelog/1.4.rst:1163 86e370be3d7a4d4cabfd46ff3cf4b0db -msgid "" -":vytask:`T4173` (bug): Wan Load Balancing - Error on firewall NAT rules" -msgstr "" - -#: ../../changelog/1.4.rst:1167 ac206a126bab4aecb0454ce2f75265b3 -msgid "2022-01-21" -msgstr "" - -#: ../../changelog/1.4.rst:1169 6602d6211d084c35aba4dde4ab062cac -msgid "" -":vytask:`T4200` (bug): Assigning ipv6-name to interface is not generating " -"nftables rules" -msgstr "" - -#: ../../changelog/1.4.rst:1170 d462effd14ce47c789bbc64a220505a4 -msgid ":vytask:`T4144` (bug): Firewall address-group - Improve error messages" -msgstr "" - -#: ../../changelog/1.4.rst:1171 fa515fad003c43c783b4b48da0a95e0c -msgid "" -":vytask:`T4137` (bug): Firewall group configuration allows to set incorrect " -"port range and invalid port" -msgstr "" - -#: ../../changelog/1.4.rst:1172 69ee1782afce42dabea7f0cd249a82c1 -msgid "" -":vytask:`T4133` (bug): Firewall network group error with zone-based firewall" -" rules" -msgstr "" - -#: ../../changelog/1.4.rst:1176 90f6e6ab271c4b4b834e5a50b5c7fd84 -msgid "2022-01-20" -msgstr "" - -#: ../../changelog/1.4.rst:1178 8808984778494e879447976f4b88b286 -msgid "" -":vytask:`T4171` (bug): Interface config migration error on 1.2.8 -> 1.4 " -"upgrade" -msgstr "" - -#: ../../changelog/1.4.rst:1182 bac921731a6f4580ad8142e464dcc3e5 -msgid "2022-01-19" -msgstr "" - -#: ../../changelog/1.4.rst:1184 7464b906dd614df0879676593028adde -msgid ":vytask:`T4195` (feature): [OSPF-ECMP]enable set maximun-path" -msgstr "" - -#: ../../changelog/1.4.rst:1188 e88a150f4ecb4d8488e3bf0c03b3f7ef -msgid "2022-01-18" -msgstr "" - -#: ../../changelog/1.4.rst:1190 d59909fb705f4aa08878bfdd01e11833 -msgid "" -":vytask:`T4159` (bug): Empty firewall group (address, network & port) " -"generates invalid nftables config, commit fails" -msgstr "" - -#: ../../changelog/1.4.rst:1191 59cb0b64f1104b269dd99c538e0c717a -msgid "" -":vytask:`T4155` (bug): PBR: `set table main` fails in `firewall.py` with " -"newer rolling releases" -msgstr "" - -#: ../../changelog/1.4.rst:1192 73e725a291d24d4e80a54e0f80efbaaa -msgid "" -":vytask:`T3873` (feature): Zone based Firewall - Filter traffic in same zone" -msgstr "" - -#: ../../changelog/1.4.rst:1193 e1a91e3f881a4c058f017ec24a01bfbe -msgid "" -":vytask:`T3286` (feature): Switch the firewall from iptables to nftables" -msgstr "" - -#: ../../changelog/1.4.rst:1194 82bee1f350c34351a261827ad4b41d2e -msgid ":vytask:`T292` (feature): [ZBF] Allow filtering intra zone traffic" -msgstr "" - -#: ../../changelog/1.4.rst:1198 cff2b21a3b77445884145b7269bb044e -msgid "2022-01-17" -msgstr "" - -#: ../../changelog/1.4.rst:1200 25904445dd894778be363304007fa4cb -msgid "" -":vytask:`T3164` (bug): console-server ssh does not work with RADIUS PAM auth" -msgstr "" - -#: ../../changelog/1.4.rst:1204 d26ff5ac277c4d5998a91447daca2bc4 -msgid "2022-01-15" -msgstr "" - -#: ../../changelog/1.4.rst:1206 32788b59cdcc425481feff1057ee1b48 -msgid "" -":vytask:`T4183` (feature): IPv6 link-local address not accepted as wireguard" -" peer" -msgstr "" - -#: ../../changelog/1.4.rst:1207 716d7836b98d42dcae5c22ea22e32a86 -msgid ":vytask:`T4150` (bug): VRRP with conntrack-sync does not work" -msgstr "" - -#: ../../changelog/1.4.rst:1208 063d18b955774f0190ab36a112af5254 -msgid "" -":vytask:`T4110` (feature): [IPV6-SSH/DNS} enable IPv6 link local adresses " -"as listen-address %eth0" -msgstr "" - -#: ../../changelog/1.4.rst:1212 a149c9c4fac8443fa493dfcd3bcce77e -msgid "2022-01-14" -msgstr "" - -#: ../../changelog/1.4.rst:1214 3ae43ed56aaa4c3491decd9347c8b5ac -msgid ":vytask:`T4182` (bug): Show vrrp if vrrp not configured bug" -msgstr "" - -#: ../../changelog/1.4.rst:1215 3a843f4555a14bd5b0fd4eec826ba2fc -msgid "" -":vytask:`T4179` (feature): Add op-mode CLI for show high-availability " -"virtual-server" -msgstr "" - -#: ../../changelog/1.4.rst:1216 f908517ef7fc4f479f2c8d071531a5b3 -msgid "" -":vytask:`T4177` (bug): Strip-private doesn't work for service monitoring" -msgstr "" - -#: ../../changelog/1.4.rst:1220 b3f90fe06d8948288c90a14fca3eb1d0 -msgid "2022-01-13" -msgstr "" - -#: ../../changelog/1.4.rst:1222 1824a23787ad4a35a334886a9bc9e6bc -msgid ":vytask:`T4175` (bug): BGP configuration failed" -msgstr "" - -#: ../../changelog/1.4.rst:1223 7ea7440897cb43e4bb6fb1b35191d3b1 -msgid "" -":vytask:`T4109` (feature): Extend high-availability/keepalived for support " -"virtual-server lb" -msgstr "" - -#: ../../changelog/1.4.rst:1227 94a84ec48e214f28820f5eae8a015693 -msgid "2022-01-12" -msgstr "" - -#: ../../changelog/1.4.rst:1229 350dbde112444c1cb1d0bfe7eda30281 -msgid "" -":vytask:`T4174` (bug): Validation fails when entering port range with upper " -"port 65535" -msgstr "" - -#: ../../changelog/1.4.rst:1230 1a003f2c678c4c8991e78c3e6025fe33 -msgid "" -":vytask:`T4162` (bug): VPN ipsec ike-group - Incorrect value help for " -"ikev2-reauth" -msgstr "" - -#: ../../changelog/1.4.rst:1231 ea78d6be118f4e76a0b93bbb59626ed0 -msgid "" -":vytask:`T4161` (bug): Policy route-map - Incorrect value help for local " -"preference" -msgstr "" - -#: ../../changelog/1.4.rst:1232 0e7a83253daf4e90832c8ffffc914677 -msgid ":vytask:`T4152` (bug): NHRP shortcut-target holding-time does not work" -msgstr "" - -#: ../../changelog/1.4.rst:1236 7ceb5112d2574833a1ed38f9e57a700a -msgid "2022-01-11" -msgstr "" - -#: ../../changelog/1.4.rst:1238 b8787941f0ec448fa2a4c5b2e2224160 -msgid "" -":vytask:`T4149` (bug): [Firewall-IPV6] Error delete Fw rules on VIF/INT" -msgstr "" - -#: ../../changelog/1.4.rst:1239 59950c5764d54667b2471500f8a5cbbd -msgid ":vytask:`T3950` (bug): CLI backtrace on update if DNS not defined" -msgstr "" - -#: ../../changelog/1.4.rst:1240 2483b24b04d947fc83bfef0a998aef53 -msgid "" -":vytask:`T4166` (bug): Debug output missing when frr.py called under vyos-" -"configd" -msgstr "" - -#: ../../changelog/1.4.rst:1244 18f5e0e3fe7b42389a48d2c199e054ff -msgid "2022-01-10" -msgstr "" - -#: ../../changelog/1.4.rst:1246 b9eff408e0b34b2cbe50a325c665eae0 -msgid "" -":vytask:`T3299` (bug): Allow the web proxy service to listen on all IP " -"addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1247 1903b7750edd45c88e764485f9c549aa -msgid "" -":vytask:`T3115` (feature): Add support for firewall on L3 VIF bridge " -"interface" -msgstr "" - -#: ../../changelog/1.4.rst:1251 65088f1b6c4f4f8aad31d212f9081147 -msgid "2022-01-09" -msgstr "" - -#: ../../changelog/1.4.rst:1253 229ff658dea549e892d563a27aae02c3 -msgid ":vytask:`T4142` (bug): Input ifbX interfaces not displayed in op-mode" -msgstr "" - -#: ../../changelog/1.4.rst:1254 bf9f274077924e9080b60aa8fecc1b0c -msgid "" -":vytask:`T3914` (bug): VRRP rfc3768-compatibility doesn't work with unicast " -"peers" -msgstr "" - -#: ../../changelog/1.4.rst:1258 ba13b1840f5848248bd9beb795d953b3 -msgid "2022-01-08" -msgstr "" - -#: ../../changelog/1.4.rst:1260 2b0b21fcc9ca4a488e6aeb4acb1d5ae0 -msgid "" -":vytask:`T4116` (bug): Webproxy/Squid not working with IPv6 listen-address" -msgstr "" - -#: ../../changelog/1.4.rst:1264 9d790ca09d6741faa947db96896646d9 -msgid "2022-01-07" -msgstr "" - -#: ../../changelog/1.4.rst:1266 18f4361ee12a45fa91153d28a938816d -msgid ":vytask:`T3924` (bug): VRRP stops working with VRF" -msgstr "" - -#: ../../changelog/1.4.rst:1270 fc10506a117040ddbc420c97d3c9b383 -msgid "2022-01-06" -msgstr "" - -#: ../../changelog/1.4.rst:1272 ef4994ca3a65478faf1e42abe93dfe76 -msgid "" -":vytask:`T4135` (bug): Declare zone policy firewall without local zone " -"errors" -msgstr "" - -#: ../../changelog/1.4.rst:1273 178896cc002d4ba6945a1d944c974bda -msgid ":vytask:`T4130` (bug): Firewall state policy errors chain" -msgstr "" - -#: ../../changelog/1.4.rst:1274 4d7e8aefe4e54673a560708a7ccbfd99 -msgid "" -":vytask:`T4141` (bug): Set high-availability vrrp sync-group without members" -" error" -msgstr "" - -#: ../../changelog/1.4.rst:1278 38ca8f1afb594454a34ad7679b3d90f8 -msgid "2022-01-04" -msgstr "" - -#: ../../changelog/1.4.rst:1280 39d1d37d970c4e10bb9fd6b7fbf85042 -msgid "" -":vytask:`T4134` (bug): Incorrect firewall protocol completion help uppercase" -" and duplicates" -msgstr "" - -#: ../../changelog/1.4.rst:1281 e319f1c5c9a8456a949cec2c5618815b -msgid ":vytask:`T4132` (bug): Impossible to show a specific firewall group" -msgstr "" - -#: ../../changelog/1.4.rst:1285 1b4e308706b048d4978458c263a9f636 -msgid "2022-01-03" -msgstr "" - -#: ../../changelog/1.4.rst:1287 101562aa0dad44828c4439601d6c2b63 -msgid "" -":vytask:`T4126` (feature): Ability to set priority to site to site IPSec vpn" -" tunnels" -msgstr "" - -#: ../../changelog/1.4.rst:1288 2123c93546204c2cb4151f63f2fbad29 -msgid "" -":vytask:`T4052` (bug): Validator return traceback on VRRP configuration with" -" the script path not in config dir" -msgstr "" - -#: ../../changelog/1.4.rst:1289 7e878576991d427a93979a7f4da93804 -msgid ":vytask:`T4128` (bug): keepalived: Upgrade package to add VRF support" -msgstr "" - -#: ../../changelog/1.4.rst:1293 afa1cd1e89b5471c824d1ed0f5db0f73 -msgid "2021-12-31" -msgstr "" - -#: ../../changelog/1.4.rst:1295 d446a70af6144c8db6bee591a6f0e811 -msgid "" -":vytask:`T4081` (bug): VRRP health-check script stops working when setting " -"up a sync group" -msgstr "" - -#: ../../changelog/1.4.rst:1299 b02af27de8df4d76a594abe4d0d1951e -msgid "2021-12-30" -msgstr "" - -#: ../../changelog/1.4.rst:1301 b6e99c7e58e3401fa90c6367594082ab -msgid ":vytask:`T4124` (feature): snmp: migrate to get_config_dict()" -msgstr "" - -#: ../../changelog/1.4.rst:1305 fec680ee4e4d466381eca158a11f1008 -msgid "2021-12-29" -msgstr "" - -#: ../../changelog/1.4.rst:1307 3a2a112bd2bf4672aff31abcddfca0b1 -msgid "" -":vytask:`T4111` (bug): IPSec generates wrong configuration colons for IPv6 " -"peers" -msgstr "" - -#: ../../changelog/1.4.rst:1308 e6fed669449443dab727a9ce31bd081a -msgid ":vytask:`T4023` (feature): Add grepcidr or similar functionality" -msgstr "" - -#: ../../changelog/1.4.rst:1309 d0f5a819c1a54f6a8b6e8883dcc36bb3 -msgid "" -":vytask:`T4086` (default): system login banner is not removed on deletion." -msgstr "" - -#: ../../changelog/1.4.rst:1313 af7a0874a16e40d7b6e83a26d8b875b1 -msgid "2021-12-28" -msgstr "" - -#: ../../changelog/1.4.rst:1315 ed6dbbeb78c84d85b671b880866c5ad4 -msgid ":vytask:`T3380` (bug): \"show vpn ike sa\" does not display IPv6 peers" -msgstr "" - -#: ../../changelog/1.4.rst:1319 274dc312f8394e5196ecb67cfaf29d86 -msgid "2021-12-27" -msgstr "" - -#: ../../changelog/1.4.rst:1321 e5c80d20901742fc8c704f7c1146c0c3 -msgid ":vytask:`T3979` (bug): vyos-hostd unable to hostfile-update" -msgstr "" - -#: ../../changelog/1.4.rst:1322 def09c42843d4aaa972d5838294c5887 -msgid ":vytask:`T2566` (bug): sstp not able to run tunnels ipv6 only" -msgstr "" - -#: ../../changelog/1.4.rst:1323 0d408453ff0242d38cd5d903c48b151a -msgid ":vytask:`T4093` (bug): SNMPv3 snmpd.conf generation bug" -msgstr "" - -#: ../../changelog/1.4.rst:1324 1448d365b1ef45ad845eddd48b61f6ef -msgid ":vytask:`T2764` (enhancment): Increase maximum number of NAT rules" -msgstr "" - -#: ../../changelog/1.4.rst:1328 658d395b719f452ca116d0cbe57bf776 -msgid "2021-12-26" -msgstr "" - -#: ../../changelog/1.4.rst:1330 d4b3082faae64be6a6c7ca1036f43c1a -msgid "" -":vytask:`T4104` (bug): RAID1: \"add raid md0 member sda1\" does not restore " -"boot sector" -msgstr "" - -#: ../../changelog/1.4.rst:1331 68292f3e7baa49f4837a338e640d6400 -msgid ":vytask:`T4108` (default): OSPFv3: add support for auto-cost parameter" -msgstr "" - -#: ../../changelog/1.4.rst:1332 d52e56fa76004789b722bdb12b340ba2 -msgid "" -":vytask:`T4107` (default): OSPFv3: add support for \"default-information " -"originate\"" -msgstr "" - -#: ../../changelog/1.4.rst:1336 5b08a86ba8054bb1b86ea7dbaef37833 -msgid "2021-12-25" -msgstr "" - -#: ../../changelog/1.4.rst:1338 c49870fa691e423d80c136b78f25b566 -msgid "" -":vytask:`T4101` (bug): commit-archive: Use of uninitialized value " -"$source_address in concatenation" -msgstr "" - -#: ../../changelog/1.4.rst:1339 f185bcb0e4e24a57ab93d76fa62a2a19 -msgid "" -":vytask:`T4099` (feature): flow-accounting: sync \"source-ip\" and \"source-" -"address\" between netflow and sflow ion CLI" -msgstr "" - -#: ../../changelog/1.4.rst:1340 c0b247c56ae64017a7a085528b701c7d -msgid "" -":vytask:`T4097` (feature): flow-accounting: migrate implementation to " -"get_config_dict()" -msgstr "" - -#: ../../changelog/1.4.rst:1341 21dab199005a4f79aaa5f81ea1538c45 -msgid "" -":vytask:`T4105` (feature): flow-accounting: drop \"sflow agent-address " -"auto\"" -msgstr "" - -#: ../../changelog/1.4.rst:1342 5959c7c9c65d4bdeb962518edde6d1ae -msgid "" -":vytask:`T4106` (feature): flow-accounting: support specification of capture" -" packet lenght" -msgstr "" - -#: ../../changelog/1.4.rst:1343 58a5e755ad9942309dbe18fc25d16ded -msgid ":vytask:`T4102` (feature): OSPFv3: add support for NSSA area-type" -msgstr "" - -#: ../../changelog/1.4.rst:1344 35ea14b380cf4c51bb3bf15cb31e55d4 -msgid ":vytask:`T4055` (feature): Add VRF support for HTTP(S) API service" -msgstr "" - -#: ../../changelog/1.4.rst:1348 9fe48c19ec17454d82e6ad76dd67c0fa -msgid "2021-12-24" -msgstr "" - -#: ../../changelog/1.4.rst:1350 6be0cd69b5f74ca8b7e08347cc8358f8 -msgid ":vytask:`T3854` (bug): Missing op-mode commands for conntrack-sync" -msgstr "" - -#: ../../changelog/1.4.rst:1354 df5adbcb383e480b96fe664b8cdcc099 -msgid "2021-12-23" -msgstr "" - -#: ../../changelog/1.4.rst:1356 fc18d42f92724fe9ab06f417e1ccbb66 -msgid "" -":vytask:`T3354` (default): Convert strip-private script from Perl to Python" -msgstr "" - -#: ../../changelog/1.4.rst:1360 621281f975a7446cb53a92f6cc91b94d -msgid "2021-12-22" -msgstr "" - -#: ../../changelog/1.4.rst:1362 66d4616f9eeb453ca537f4370cbad3b1 -msgid "" -":vytask:`T3678` (bug): VyOS 1.4: Invalid error message while deleting ipsec " -"vpn configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1363 3ccad55c7c5e41338c300042b598ef1a -msgid ":vytask:`T3356` (feature): Script for remote file transfers" -msgstr "" - -#: ../../changelog/1.4.rst:1367 6745254ee1d44f44bbfa14c24566abe0 -msgid "2021-12-21" -msgstr "" - -#: ../../changelog/1.4.rst:1369 9f5134750a3149d989a25dc26bb0adb3 -msgid "" -":vytask:`T4083` (bug): Cluster heartbeat doesn't start b.c lack of directory" -" /run/heartbeat/" -msgstr "" - -#: ../../changelog/1.4.rst:1370 fab3e7851d644cb5a364491f7ca59fe9 -msgid ":vytask:`T4070` (bug): NATv4 : inbound-interface type \"any\" is missing." -msgstr "" - -#: ../../changelog/1.4.rst:1371 c058279d6f6440fd9f93740211fc6421 -msgid "" -":vytask:`T4053` (bug): VRRP impossible to set scripts out of the /config " -"directory" -msgstr "" - -#: ../../changelog/1.4.rst:1372 8d169eb435194bfeb36010e2c825b33d -msgid ":vytask:`T3931` (bug): SSTP doesn't work after rewriting to PKI" -msgstr "" - -#: ../../changelog/1.4.rst:1376 1e08e797336b45209badba9ae0d28582 -msgid "2021-12-20" -msgstr "" - -#: ../../changelog/1.4.rst:1378 44fb34e167e84aad8ee9a42cf48525f4 -msgid ":vytask:`T4088` (default): Fix typo in login banner" -msgstr "" - -#: ../../changelog/1.4.rst:1382 aaec404b6f0441c098119efc6b647bd9 -msgid "2021-12-19" -msgstr "" - -#: ../../changelog/1.4.rst:1384 5db7e263297c45beadde8183a10b507e -msgid "" -":vytask:`T3912` (default): Use a more informative default post-login banner" -msgstr "" - -#: ../../changelog/1.4.rst:1388 f849e3a1fe9c4fddacae48bd9dbb9646 -msgid "2021-12-17" -msgstr "" - -#: ../../changelog/1.4.rst:1390 856c65429be3412594b1c796bf1dde5e -msgid "" -":vytask:`T4059` (bug): VRRP sync-group transition script does not persist " -"after reboot" -msgstr "" - -#: ../../changelog/1.4.rst:1394 817124288136485a9fc0d67f85f74560 -msgid "2021-12-16" -msgstr "" - -#: ../../changelog/1.4.rst:1396 7d97ccc42a254683b310a89656f86b22 -msgid ":vytask:`T4046` (feature): Sflow - Add Source address parameter" -msgstr "" - -#: ../../changelog/1.4.rst:1397 5f9b011eabd346e88b861af1103b6386 -msgid ":vytask:`T3556` (bug): Commit-archive via scp causes 100% CPU on boot" -msgstr "" - -#: ../../changelog/1.4.rst:1398 685a0c4df4f544669a9a2406541319fe -msgid ":vytask:`T4076` (enhancment): Allow setting CORS options in HTTP API" -msgstr "" - -#: ../../changelog/1.4.rst:1399 86fc5d56a7ce4c6c8f5222a8f5a05d9e -msgid ":vytask:`T4037` (default): HTTP transfers do not follow redirects" -msgstr "" - -#: ../../changelog/1.4.rst:1400 f172eddd0aef4df1b9e513c0a54a0f8d -msgid ":vytask:`T4029` (default): Broken SFTP uploads" -msgstr "" - -#: ../../changelog/1.4.rst:1404 37018116196645c2b16593187d27fecf -msgid "2021-12-15" -msgstr "" - -#: ../../changelog/1.4.rst:1406 6348e51e6b0346f99f76b13e66f9130b -msgid "" -":vytask:`T4077` (bug): op-mode: bfd: drop \"show protocols bfd\" in favour " -"of \"show bfd\"" -msgstr "" - -#: ../../changelog/1.4.rst:1407 ad96fc6255b44517af16416f91926b2d -msgid "" -":vytask:`T4073` (bug): \"show protocols bfd peer <>\" shows incorrect peer " -"information." -msgstr "" - -#: ../../changelog/1.4.rst:1411 e0693591e25b49b398e923fe0c530066 -msgid "2021-12-14" -msgstr "" - -#: ../../changelog/1.4.rst:1413 ef2bdd6e9b3a4d6b9f61078e63e4a647 -msgid "" -":vytask:`T4071` (feature): Allow HTTP API to bind to unix domain socket" -msgstr "" - -#: ../../changelog/1.4.rst:1417 5206304e8520473084dbb36a730bbdef -msgid "2021-12-12" -msgstr "" - -#: ../../changelog/1.4.rst:1419 1af18c37ca8b4f4790c25215fbe7d7bf -msgid "" -":vytask:`T4069` (feature): BGP: add additional available parameters to VyOS " -"CLI" -msgstr "" - -#: ../../changelog/1.4.rst:1420 c56108453b174cfea45f677e369320dc -msgid "" -":vytask:`T4036` (bug): VXLAN incorrect raiseError if set multicast network " -"instead of singe address" -msgstr "" - -#: ../../changelog/1.4.rst:1424 f444701b052643a7b830b3517298b2ac -msgid "2021-12-10" -msgstr "" - -#: ../../changelog/1.4.rst:1426 852359f7ee964cf1a82e33b49a90e119 -msgid "" -":vytask:`T4068` (feature): Python: ConfigError should insert line breaks " -"into the error message" -msgstr "" - -#: ../../changelog/1.4.rst:1430 15a4dffbc5c2474cb6d1d5dcffefb85d -msgid "2021-12-09" -msgstr "" - -#: ../../changelog/1.4.rst:1432 19dbc22b2d6849708ad6cad5517f7c74 -msgid ":vytask:`T4033` (bug): VRRP - Error security when setting scripts" -msgstr "" - -#: ../../changelog/1.4.rst:1433 b4a812d52d4348ffb8fedf0a6fa86c3c -msgid "" -":vytask:`T4064` (bug): IP address for vif is not removed from the system " -"when deleted in configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1434 5b812b474b874ab7b6522465c296dbbd -msgid "" -":vytask:`T4060` (enhancment): Extend configquery for use before boot " -"configuration is complete" -msgstr "" - -#: ../../changelog/1.4.rst:1435 6de2fa514a614e12b9bcf1f057bd7321 -msgid ":vytask:`T4058` (bug): BFD: add BGP and OSPF \"bfd profile\" support" -msgstr "" - -#: ../../changelog/1.4.rst:1436 1ea15e76bfe74ce797814efc7a395ee2 -msgid ":vytask:`T4054` (bug): BFD profiles configuration incorrect behavior." -msgstr "" - -#: ../../changelog/1.4.rst:1440 803298e290b5412d9f77e1648b812b11 -msgid "2021-12-07" -msgstr "" - -#: ../../changelog/1.4.rst:1442 f93c156cbb3540cfb96da0be165b175c -msgid "" -":vytask:`T4041` (servicerequest): \"transition-script\" doesn't work on " -"\"sync-group\"" -msgstr "" - -#: ../../changelog/1.4.rst:1446 15d79452d831476dad325329531afcac -msgid "2021-12-06" -msgstr "" - -#: ../../changelog/1.4.rst:1448 0ef6ea68ea02460795f41d5f8eb813e6 -msgid ":vytask:`T4012` (feature): Add VRF support for TFTP" -msgstr "" - -#: ../../changelog/1.4.rst:1452 33259e303008449598599386962074ce -msgid "2021-12-04" -msgstr "" - -#: ../../changelog/1.4.rst:1454 6faba6f685e04aea89712b99866f9b6a -msgid "" -":vytask:`T4049` (feature): support command-style output with compare command" -msgstr "" - -#: ../../changelog/1.4.rst:1455 72d53475c64245078d210553a7d16419 -msgid ":vytask:`T4047` (bug): Wrong regex validation in XML definitions" -msgstr "" - -#: ../../changelog/1.4.rst:1456 ad1964cbf2774bc7ba762935ee2acc80 -msgid ":vytask:`T4042` (bug): BGP L2VPN / EVPN and RD type 0 set" -msgstr "" - -#: ../../changelog/1.4.rst:1457 decdff8315204104a16d1b2ab93a0b56 -msgid "" -":vytask:`T4048` (bug): BGP: L2VPN/EVPN and individual RD and RT settings for" -" each VNI" -msgstr "" - -#: ../../changelog/1.4.rst:1458 0e5f23971a0440d1a16a32724cce9204 -msgid ":vytask:`T4045` (bug): Unable to \"format disk <new> like <old>\"" -msgstr "" - -#: ../../changelog/1.4.rst:1459 ef3dcb932be6453f935e5ab688c8189b -msgid ":vytask:`T4044` (feature): BFD: add vrf support" -msgstr "" - -#: ../../changelog/1.4.rst:1460 a34b2445226b46b593643fc5bb4b792c -msgid ":vytask:`T4043` (feature): BFD: add support for passive mode" -msgstr "" - -#: ../../changelog/1.4.rst:1464 34c2788d424d49dfb5f5ad14efad5f4b -msgid "2021-12-02" -msgstr "" - -#: ../../changelog/1.4.rst:1466 49740bce370046bfbe7badc65aa04ef9 -msgid "" -":vytask:`T4035` (bug): Geneve interfaces aren't displayed by operational " -"mode commands" -msgstr "" - -#: ../../changelog/1.4.rst:1470 2f5a3d1c31754d51abf18b89d9c53c98 -msgid "2021-12-01" -msgstr "" - -#: ../../changelog/1.4.rst:1472 2a50df0d900944acaf1f64c8a75c6663 -msgid "" -":vytask:`T3695` (bug): OpenConnect reports commit success when ocserv fails " -"to start due to SSL cert/key file issues" -msgstr "" - -#: ../../changelog/1.4.rst:1476 5b54335658634b7aa4942821ccf36d12 -msgid "2021-11-30" -msgstr "" - -#: ../../changelog/1.4.rst:1478 b3efb0ca632c4d54b06cdf8fc913d5eb -msgid "" -":vytask:`T4010` (bug): DMVPN generates incorrect configuration life_time for" -" swanctl.conf" -msgstr "" - -#: ../../changelog/1.4.rst:1479 bf949371c39c4829a820a0c3fdf2db23 -msgid ":vytask:`T3725` (feature): show configuration in json format" -msgstr "" - -#: ../../changelog/1.4.rst:1483 6c44cda367a94a5a90ee5cb5b2c3a9e3 -msgid "2021-11-29" -msgstr "" - -#: ../../changelog/1.4.rst:1485 d5cdce9e030b497fb039792199946873 -msgid "" -":vytask:`T3946` (enhancment): Automatically resize the root partition if the" -" drive has extra space" -msgstr "" - -#: ../../changelog/1.4.rst:1489 c2d0fc8e3ca840e2a102553b3cbd6074 -msgid "2021-11-28" -msgstr "" - -#: ../../changelog/1.4.rst:1491 2ccf1b6180fc4b0bb12465acc858d9d0 -msgid ":vytask:`T3999` (bug): show lldp neighbor Traceback error" -msgstr "" - -#: ../../changelog/1.4.rst:1492 faedd8c68dc8435f851ec48848a3f770 -msgid ":vytask:`T3928` (feature): Add OSPFv3 VRF support" -msgstr "" - -#: ../../changelog/1.4.rst:1496 80d916c73a244f4591de2cd9cd957fba -msgid "2021-11-27" -msgstr "" - -#: ../../changelog/1.4.rst:1498 5c16f252f791409698e6dc738db8cc14 -msgid "" -":vytask:`T3755` (feature): ospf: adjust to new FRR 8 syntax where \"no " -"passive-interface \" moved to interface section" -msgstr "" - -#: ../../changelog/1.4.rst:1499 b4b5f00d089a45098730e8afda53f2c9 -msgid ":vytask:`T3753` (feature): frr: upgrade to stable/8.1 release train" -msgstr "" - -#: ../../changelog/1.4.rst:1503 33af4a4a484d47dfa7e6268c38696f51 -msgid "2021-11-26" -msgstr "" - -#: ../../changelog/1.4.rst:1505 f7eaee99aff740b9b5696a3a1ccd701c -msgid "" -":vytask:`T3978` (bug): containers add network without declaring prefix raise" -" ConfigError" -msgstr "" - -#: ../../changelog/1.4.rst:1509 f375b96da6b24983bde08b71199f02ac -msgid "2021-11-25" -msgstr "" - -#: ../../changelog/1.4.rst:1511 d76bd3e17de14f4f9c7b280c3f060afa -msgid "" -":vytask:`T4006` (default): Add additional Linux capabilities to container " -"configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1512 41b7c11eb7004e22b65b263e2bc762df -msgid "" -":vytask:`T3986` (bug): Incorrect description for vpn ipsec site-to-site " -"authentication and connection" -msgstr "" - -#: ../../changelog/1.4.rst:1516 07f4b206bea849238a721f60f9ca2786 -msgid "2021-11-24" -msgstr "" - -#: ../../changelog/1.4.rst:1518 db7793f4e691402dbb8f3e3ae0fd3d8e -msgid ":vytask:`T4015` (feature): Update Accel-PPP to a newer revision" -msgstr "" - -#: ../../changelog/1.4.rst:1519 f20db2f245a54fb4ab6e11de90936b89 -msgid "" -":vytask:`T3865` (bug): loadkey command help text missing escape sequence" -msgstr "" - -#: ../../changelog/1.4.rst:1520 c58e178d5228487d80d1cfe7d9cc0c2b -msgid "" -":vytask:`T1083` (feature): Implement persistent/random address and port " -"mapping options for NAT rules" -msgstr "" - -#: ../../changelog/1.4.rst:1524 8b4ca669003c4e2695645e20e0dded83 -msgid "2021-11-23" -msgstr "" - -#: ../../changelog/1.4.rst:1526 fc7db67790cb406583f6f01778fb310a -msgid "" -":vytask:`T3990` (bug): WATCHFRR: crashlog and per-thread log buffering " -"unavailable (due to files left behind in /var/tmp/frr/ after reboot)" -msgstr "" - -#: ../../changelog/1.4.rst:1530 9c8f91895ed946bfa778039f6a22ce04 -msgid "2021-11-20" -msgstr "" - -#: ../../changelog/1.4.rst:1532 373a14d555b7412aa1b050e79f2633b4 -msgid ":vytask:`T3998` (bug): route-target completion incorrect description" -msgstr "" - -#: ../../changelog/1.4.rst:1536 6d9c1670ef2f4710821f8d75409dbb2f -msgid "2021-11-19" -msgstr "" - -#: ../../changelog/1.4.rst:1538 79a8ec91f52a4f83a60c85b1374f29a3 -msgid "" -":vytask:`T4003` (bug): API for \"show interfaces ethernet\" does not include" -" the interface description" -msgstr "" - -#: ../../changelog/1.4.rst:1539 737eaa29f75441fdb010deef395ce917 -msgid "" -":vytask:`T4011` (bug): ethernet: deleting interface should place interface " -"in admin down state" -msgstr "" - -#: ../../changelog/1.4.rst:1543 d77eb1f722dd49ea9b73d64caa21d7f9 -msgid "2021-11-18" -msgstr "" - -#: ../../changelog/1.4.rst:1545 2abd7a54c36f4cc9b6912595350a65d7 -msgid ":vytask:`T3612` (bug): IPoE Server address pool issues." -msgstr "" - -#: ../../changelog/1.4.rst:1546 c283a93f98584e8182a885bf041b4488 -msgid "" -":vytask:`T3995` (feature): OpenVPN: do not stop/start service on " -"configuration change" -msgstr "" - -#: ../../changelog/1.4.rst:1547 35a918d1a0774864be9d70671d918789 -msgid ":vytask:`T3680` (bug): Static routes with dhcp-interface are flaky" -msgstr "" - -#: ../../changelog/1.4.rst:1548 975dd16825114552b673bc9a3edb8729 -msgid "" -":vytask:`T4008` (feature): dhcp: change client retry interval form 300 -> 60" -" seconds" -msgstr "" - -#: ../../changelog/1.4.rst:1549 59594444a8ae4f7694d46392c5856d7b -msgid "" -":vytask:`T3795` (bug): WWAN: issues with non connected interface / no signal" -msgstr "" - -#: ../../changelog/1.4.rst:1550 836418bbfe7243afb51c05dbe14e577c -msgid ":vytask:`T3510` (bug): RADIUS usersname is not shown on CLI" -msgstr "" - -#: ../../changelog/1.4.rst:1554 44179b7654b84c5cad61f109695d3b79 -msgid "2021-11-17" -msgstr "" - -#: ../../changelog/1.4.rst:1556 1384b45cbf944d23b1801ec05206f23b -msgid ":vytask:`T3350` (bug): OpenVPN config file generation broken" -msgstr "" - -#: ../../changelog/1.4.rst:1557 84265a62cc304ba5949c176c7eb19e74 -msgid ":vytask:`T3996` (bug): SNMP service error in log" -msgstr "" - -#: ../../changelog/1.4.rst:1561 4d172d4f3d6e432983083132af9b12ef -msgid "2021-11-15" -msgstr "" - -#: ../../changelog/1.4.rst:1563 efc12199080f40aaa80a536f7263b771 -msgid "" -":vytask:`T3994` (bug): VRF: unable to delete vrf when name contains numbers," -" hyphen or underscore" -msgstr "" - -#: ../../changelog/1.4.rst:1564 0fb9b7959391482b9cfa129ceeb5eac6 -msgid ":vytask:`T3960` (bug): FRR Misconfig when using multiple VRF VNI" -msgstr "" - -#: ../../changelog/1.4.rst:1565 cca824ad63c14e9b9c6065a7cb3eac90 -msgid "" -":vytask:`T3724` (feature): Allow setting host-name in l2tp section of accel-" -"ppp" -msgstr "" - -#: ../../changelog/1.4.rst:1566 4f3e4bcaa936444b8b4a0a4237fe95cc -msgid ":vytask:`T645` (feature): Allow multiple prefixes in ipsec tunnel" -msgstr "" - -#: ../../changelog/1.4.rst:1570 db69994831fa46fd9cf9c4aa427b2c86 -msgid "2021-11-10" -msgstr "" - -#: ../../changelog/1.4.rst:1572 8f2cf888a155440da9abffeb79c28605 -msgid ":vytask:`T3966` (default): OpenVPN fix the smoketests" -msgstr "" - -#: ../../changelog/1.4.rst:1573 5c57bc5739ac47d28d0243c4c5f647bf -msgid "" -":vytask:`T3834` (default): [OPENVPN] Support for Two Factor Authentication " -"totp." -msgstr "" - -#: ../../changelog/1.4.rst:1574 2860ca780be146ca9b62296c4b77d09e -msgid "" -":vytask:`T3982` (bug): DHCP server commit fails if static-mapping contains +" -" or ." -msgstr "" - -#: ../../changelog/1.4.rst:1578 9b1fc1a2ba33498fb9104051996c36a0 -msgid "2021-11-09" -msgstr "" - -#: ../../changelog/1.4.rst:1580 3af20db391e7431899dee42938ecffdd -msgid ":vytask:`T3962` (bug): Image cannot be built without open-vm-tools" -msgstr "" - -#: ../../changelog/1.4.rst:1584 fcbb65d6e1894b52a227621a03127dd3 -msgid "2021-11-07" -msgstr "" - -#: ../../changelog/1.4.rst:1586 ae096a6bc53c435fa4cb2703796a5f00 -msgid ":vytask:`T3626` (bug): Configuring and disabling DHCP Server" -msgstr "" - -#: ../../changelog/1.4.rst:1590 e3c902b5bc724dba80974f93943bfec9 -msgid "2021-11-06" -msgstr "" - -#: ../../changelog/1.4.rst:1592 d53b23fa07e442c694c671a472cd4fcf -msgid ":vytask:`T3514` (bug): NIC flap at any interface change" -msgstr "" - -#: ../../changelog/1.4.rst:1596 8f4cbe939fbd435db4e6b50eb2195515 -msgid "2021-11-05" -msgstr "" - -#: ../../changelog/1.4.rst:1598 1857ef4a5b9c4a6fa6c86ef163e4ed8f -msgid ":vytask:`T3972` (bug): Removing vif-c interface raises KeyError" -msgstr "" - -#: ../../changelog/1.4.rst:1602 62e233589df7468193a2e2cda5574bc1 -msgid "2021-11-04" -msgstr "" - -#: ../../changelog/1.4.rst:1604 40f3918e93bc4ab2aee81f8bf6b2a304 -msgid "" -":vytask:`T3969` (bug): Container incorrect raiseError format if network " -"doesn't exist" -msgstr "" - -#: ../../changelog/1.4.rst:1605 823a5723235a49efad0abb5cc34dac6e -msgid ":vytask:`T3662` (bug): Container configuration upgrade destroys system" -msgstr "" - -#: ../../changelog/1.4.rst:1606 0bd2c7a4555d46d9ad1200739fd48382 -msgid "" -":vytask:`T3964` (bug): SSTP: local-user static-ip CLI node accepts invalid " -"IPv4 addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1610 1821545349e44014b23e74078c94d455 -msgid "2021-11-03" -msgstr "" - -#: ../../changelog/1.4.rst:1612 4d69f99af58e481c967f08e548dc27aa -msgid ":vytask:`T3952` (default): Add sh bgp ipv4/ipv6 vpn command" -msgstr "" - -#: ../../changelog/1.4.rst:1613 1ec00861b2f442539ddc0c9e6aafe860 -msgid "" -":vytask:`T3610` (bug): DHCP-Server creation for not primary IP address fails" -msgstr "" - -#: ../../changelog/1.4.rst:1617 9a06e092c200420b87b14704ce1b235b -msgid "2021-11-01" -msgstr "" - -#: ../../changelog/1.4.rst:1619 88359c1beee948c4833d7eed077c4506 -msgid ":vytask:`T3958` (default): OpenVPN breaks the smoketests" -msgstr "" - -#: ../../changelog/1.4.rst:1620 a33e3ea96d494180acc4fce2b5e61fed -msgid "" -":vytask:`T3956` (bug): GRE tunnel - unable to move from source-interface to " -"source-address, commit error" -msgstr "" - -#: ../../changelog/1.4.rst:1624 44ccf19f9c514bf58172fae8e36020f0 -msgid "2021-10-31" -msgstr "" - -#: ../../changelog/1.4.rst:1626 5a925ec8c31749ea99dd58b34aa2b0fe -msgid ":vytask:`T3945` (feature): Add route-map for bgp aggregate-address" -msgstr "" - -#: ../../changelog/1.4.rst:1627 c74f8867367f457db032456e9ecd021a -msgid "" -":vytask:`T3954` (bug): FTDI cable makes VyOS sagitta latest hang, " -"/dev/serial unpopulated, config system error" -msgstr "" - -#: ../../changelog/1.4.rst:1628 6f76f0f9090141b8b97f143a29154d62 -msgid "" -":vytask:`T3943` (bug): \"netflow source-ip\" prevents image upgrades if IP " -"address does not exist locally" -msgstr "" - -#: ../../changelog/1.4.rst:1632 b6a085fb20f44ba8907d91379ed0dda0 -msgid "2021-10-29" -msgstr "" - -#: ../../changelog/1.4.rst:1634 1f64d63cc8c7496a9ebd723ee0fad98e -msgid ":vytask:`T3942` (feature): Generate IPSec debug archive from op-mode" -msgstr "" - -#: ../../changelog/1.4.rst:1638 1acbfe8d7e7a417ea8aa1c57c4b7820f -msgid "2021-10-28" -msgstr "" - -#: ../../changelog/1.4.rst:1640 090bc08b7b5b4b46b678c1d0b1a606a0 -msgid "" -":vytask:`T3951` (bug): After resetting vti ipsec tunnel old child SA still " -"active" -msgstr "" - -#: ../../changelog/1.4.rst:1641 0ecdf36cc0044fe4b03e897c24d21295 -msgid "" -":vytask:`T3941` (bug): \"show vpn ipsec sa\" shows established time of " -"parent SA not child SA's" -msgstr "" - -#: ../../changelog/1.4.rst:1642 ad3a9686b6f74356942c4580212da496 -msgid "" -":vytask:`T3916` (feature): Add additional Linux capabilities to container " -"configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1646 b4aea54fed9a419ebc3602f4777678cf -msgid "2021-10-27" -msgstr "" - -#: ../../changelog/1.4.rst:1648 ed41c9d2e4c341f5a0024914fa5289aa -msgid ":vytask:`T3944` (bug): VRRP fails over when adding new group to master" -msgstr "" - -#: ../../changelog/1.4.rst:1652 8c33c5abae5a4601a6772ebc5215ee47 -msgid "2021-10-22" -msgstr "" - -#: ../../changelog/1.4.rst:1654 c562d43e42834e65bc888d4f30170b2c -msgid "" -":vytask:`T3897` (feature): Dynamic DNS doesn't work with IPv6 addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1655 6e4f35bd2a0f41a48dc2aa5eb04d3869 -msgid "" -":vytask:`T3832` (feature): Allow to set DHCP client-id in hexadecimal format" -msgstr "" - -#: ../../changelog/1.4.rst:1656 b5bc6c539a9c422d8bcbffee1a095d65 -msgid "" -":vytask:`T3188` (bug): Tunnel local-ip to dhcp-interface Change Fails to " -"Update" -msgstr "" - -#: ../../changelog/1.4.rst:1657 9e1ff00d0fe743ce96dc64bd57996ef7 -msgid ":vytask:`T3917` (default): Use Avahi as mDNS repeater for IPv6 support" -msgstr "" - -#: ../../changelog/1.4.rst:1661 d8d9e23d833f4fc094de7cb901f5b9f2 -msgid "2021-10-21" -msgstr "" - -#: ../../changelog/1.4.rst:1663 9a9c43e5c1664b9b8658b092ff7e373b -msgid "" -":vytask:`T3926` (bug): strip-private does not sanitize \"cisco-" -"authentication\" from NHRP configuration" -msgstr "" - -#: ../../changelog/1.4.rst:1664 887cc2bb67434cf79d50ef33487f7c41 -msgid "" -":vytask:`T3925` (feature): Tunnel: dhcp-interface not implemented - use " -"source-interface instead" -msgstr "" - -#: ../../changelog/1.4.rst:1665 e20e8d46a01b48e19dc2e35807a6b7ec -msgid "" -":vytask:`T3923` (feature): Kernel: Enable TLS/IPSec offload support for " -"Mellanox ConnectX NICs" -msgstr "" - -#: ../../changelog/1.4.rst:1666 984cffe3c6194652910639144f7f6cfa -msgid "" -":vytask:`T3927` (feature): Kernel: Enable kernel support for HW offload of " -"the TLS protocol" -msgstr "" - -#: ../../changelog/1.4.rst:1670 a25792a8fbd94bd79482a1c511382d74 -msgid "2021-10-20" -msgstr "" - -#: ../../changelog/1.4.rst:1672 985a666571154a959f1489c397c5c777 -msgid ":vytask:`T3918` (bug): DHCPv6 prefix delegation incorrect verify error" -msgstr "" - -#: ../../changelog/1.4.rst:1673 71739d01ebe9422ba99fc3a25a0bada0 -msgid ":vytask:`T3921` (bug): tunnel: KeyError when using dhcp-interface" -msgstr "" - -#: ../../changelog/1.4.rst:1677 b585996dd55c4e8f9f0f6bd160f9bfc4 -msgid "2021-10-19" -msgstr "" - -#: ../../changelog/1.4.rst:1679 9f727de6db5f4b9998f5e3cdf4bf4fb8 -msgid "" -":vytask:`T3396` (bug): syslog can't be configured with an ipv6 literal " -"destination in 1.2.x" -msgstr "" - -#: ../../changelog/1.4.rst:1683 fdea3ccb520f4c13947e8e0a2b5f1d7a -msgid "2021-10-18" -msgstr "" - -#: ../../changelog/1.4.rst:1685 54c62e49dc4646bc96d5a8e4dab62f32 -msgid "" -":vytask:`T3002` (default): VRRP change on IPSec interface causes packet " -"routing issues" -msgstr "" - -#: ../../changelog/1.4.rst:1689 bfe880b6c6494069b1750796e1cdfea6 -msgid "2021-10-17" -msgstr "" - -#: ../../changelog/1.4.rst:1691 4c4b2c48b11f48caa3390fdb2e8fb6f9 -msgid ":vytask:`T3786` (bug): GRE tunnel source address 0.0.0.0 error" -msgstr "" - -#: ../../changelog/1.4.rst:1692 7f10d2dcca994170a8b67e9135e3cafb -msgid ":vytask:`T3217` (default): Save FRR configuration on each commit" -msgstr "" - -#: ../../changelog/1.4.rst:1693 7e57f03739e14128a05282df9ecdb614 -msgid ":vytask:`T3381` (bug): Change GRE tunnel failed" -msgstr "" - -#: ../../changelog/1.4.rst:1694 c61189b3b4c4458e915d0dd86e454858 -msgid "" -":vytask:`T3254` (bug): Dynamic DNS status shows incorrect last update time" -msgstr "" - -#: ../../changelog/1.4.rst:1695 76f95987c5a24c568e05a91ac364e2e7 -msgid ":vytask:`T1243` (bug): BGP local-as accept wrong values" -msgstr "" - -#: ../../changelog/1.4.rst:1696 d9cf14f007a24de6b5a39cceda20684c -msgid ":vytask:`T697` (bug): Clean up and sanitize package dependencies" -msgstr "" - -#: ../../changelog/1.4.rst:1697 cb0d684bc6194190a3e4caa3dffed9bb -msgid ":vytask:`T578` (feature): Support Linux Container" -msgstr "" - -#: ../../changelog/1.4.rst:1701 1c438a13f2f94e7eb2a6aa604aa81137 -msgid "2021-10-16" -msgstr "" - -#: ../../changelog/1.4.rst:1703 2f2d5eb7b6cd4670a801e7d6f57db961 -msgid "" -":vytask:`T3879` (bug): GPG key verification fails when upgrading from a 1.3 " -"beta version" -msgstr "" - -#: ../../changelog/1.4.rst:1707 91a6a690bea347008397ab1eeabfda34 -msgid "2021-10-15" -msgstr "" - -#: ../../changelog/1.4.rst:1709 d0731764891445e6bba545d1c4a78bea -msgid ":vytask:`T3748` (bug): Container deletion bug" -msgstr "" - -#: ../../changelog/1.4.rst:1710 ef9e07542e1e42df8d22d9671e5e0194 -msgid "" -":vytask:`T3693` (feature): ISIS Route redistribution ipv6 support missing" -msgstr "" - -#: ../../changelog/1.4.rst:1711 507555afcc8c4b70acc5731cb7269503 -msgid ":vytask:`T3676` (feature): Container option to add Linux capabilities" -msgstr "" - -#: ../../changelog/1.4.rst:1712 d04799dbc9b542c59b4c830fdd3f01a2 -msgid "" -":vytask:`T3613` (feature): Selectors for route-based IPsec tunnel (vti)" -msgstr "" - -#: ../../changelog/1.4.rst:1713 cd33769c3aa6419786af0aa83b173699 -msgid ":vytask:`T3692` (bug): VyOS build failing due to repo.saltstack.com" -msgstr "" - -#: ../../changelog/1.4.rst:1714 eb439180cfe64a5aab81582079c66b3d -msgid ":vytask:`T3673` (feature): BGP large-community del operation missing" -msgstr "" - -#: ../../changelog/1.4.rst:1718 52afa81b1ead48cdba2616cf25c6e44f -msgid "2021-10-14" -msgstr "" - -#: ../../changelog/1.4.rst:1720 026439311d7341c598d585c0d52ab1d0 -msgid ":vytask:`T3811` (bug): NAT (op_mode): NAT op_mode command fails." -msgstr "" - -#: ../../changelog/1.4.rst:1721 de3dd6306ff34f13b8d76c9990c4390f -msgid "" -":vytask:`T3801` (feature): containers: do not use podman CLI to create " -"container networks" -msgstr "" - -#: ../../changelog/1.4.rst:1725 a79ed605b3f84bbda2289df30c87a9c1 -msgid "2021-10-13" -msgstr "" - -#: ../../changelog/1.4.rst:1727 c8edaf2db75b4dfeb7d71c35a154cee0 -msgid ":vytask:`T3904` (bug): NTP pool associations silently fail" -msgstr "" - -#: ../../changelog/1.4.rst:1728 a50e46282466482bb2b09e88754120b0 -msgid ":vytask:`T3277` (feature): DNS Forwarding - reverse zones" -msgstr "" - -#: ../../changelog/1.4.rst:1732 18d527b78d93409cae7b70a13bd7f877 -msgid "2021-10-12" -msgstr "" - -#: ../../changelog/1.4.rst:1734 b55ffc16f3e644bda817013356c93a2d -msgid "" -":vytask:`T3216` (bug): Removal of restricted-shell broke configure mode for " -"RADIUS users" -msgstr "" - -#: ../../changelog/1.4.rst:1735 a0994c3d501f49e496db416faeea7b9b -msgid ":vytask:`T3881` (bug): Wrong description for container section restart" -msgstr "" - -#: ../../changelog/1.4.rst:1736 4987df223e1e4781a5ecd8f1a3aadf71 -msgid "" -":vytask:`T3868` (bug): Regex and/or wildcard not accepted with large-" -"community-list" -msgstr "" - -#: ../../changelog/1.4.rst:1737 714d79a5e2924ac08d10062a0b7831e0 -msgid "" -":vytask:`T3701` (bug): ipoe server fails to start when configuring radius " -"dynamic-author on ipoe" -msgstr "" - -#: ../../changelog/1.4.rst:1741 b9172094dea2488c8dfc96ebf896d2f2 -msgid "2021-10-10" -msgstr "" - -#: ../../changelog/1.4.rst:1743 e9c7e93c502f48c08b1ed2d64d6d56cb -msgid "" -":vytask:`T3750` (bug): pdns-recursor 4.4 issue with dont-query and private " -"DNS servers" -msgstr "" - -#: ../../changelog/1.4.rst:1744 7bc683bdef3e47fcbe03cfea20ac1e94 -msgid "" -":vytask:`T3885` (default): dhcpv6-pd: randomly generated DUID is not " -"persisted" -msgstr "" - -#: ../../changelog/1.4.rst:1745 7ac7918e9da94bc79219f0f3328bc55b -msgid ":vytask:`T3899` (enhancment): Add support for hd44780 LCD displays" -msgstr "" - -#: ../../changelog/1.4.rst:1749 b5baf6b0cfd746aaade1ba30ed0b64e2 -msgid "2021-10-09" -msgstr "" - -#: ../../changelog/1.4.rst:1751 25c9262ba3344ba9848c828b3629f8a6 -msgid "" -":vytask:`T3894` (bug): Tunnel Commit Failed if system does not have `eth0`" -msgstr "" - -#: ../../changelog/1.4.rst:1755 f1fba962aaee4708b38c140ae9c2f718 -msgid "2021-10-08" -msgstr "" - -#: ../../changelog/1.4.rst:1757 7ca700a9d7ec4b35a0a946bf33bb368a -msgid "" -":vytask:`T3893` (bug): MGRE Tunnel commit crash If sit tunnel available" -msgstr "" - -#: ../../changelog/1.4.rst:1761 50117b9c01d14dd9a88ba3335084155a -msgid "2021-10-05" -msgstr "" - -#: ../../changelog/1.4.rst:1763 f65948aa8610450db11b7bd3e1e229a2 -msgid ":vytask:`T3741` (feature): [BGP] default no-ipv4-unicast - by default" -msgstr "" - -#: ../../changelog/1.4.rst:1767 256206d93da74b4ab8111f8e75d8686b -msgid "2021-10-04" -msgstr "" - -#: ../../changelog/1.4.rst:1769 08fe120aed054a8593ec91e03c59f0ca -msgid "" -":vytask:`T3888` (bug): Incorrect warning when poweroff command executed from" -" configure mode." -msgstr "" - -#: ../../changelog/1.4.rst:1770 60ef81c741474ee59ac6b77041a3e3fc -msgid "" -":vytask:`T3890` (feature): dhcp(v6): provide op-mode commands to retrieve " -"both server and client logfiles" -msgstr "" - -#: ../../changelog/1.4.rst:1771 d56dff99da1c4d50b77b1a44227b630a -msgid "" -":vytask:`T3889` (feature): Migrate to journalctl when reading daemon logs" -msgstr "" - -#: ../../changelog/1.4.rst:1775 5fc1ba09481b449a9d3d118910b80a3c -msgid "2021-10-03" -msgstr "" - -#: ../../changelog/1.4.rst:1777 f2d9a799e90646db9394749180072620 -msgid ":vytask:`T3880` (bug): EFI boot shows error on display" -msgstr "" - -#: ../../changelog/1.4.rst:1781 2b6d7b2a1be44489a2385645bfed3a57 -msgid "2021-10-02" -msgstr "" - -#: ../../changelog/1.4.rst:1783 9d6a481c373745b68f0bed24af3a50c8 -msgid ":vytask:`T3882` (feature): Upgrade PowerDNs recursor to 4.5 series" -msgstr "" - -#: ../../changelog/1.4.rst:1784 8d3d7bff1bc74b7b81158dc57dad1ffa -msgid ":vytask:`T3883` (bug): VRF - Delette vrf config on interface" -msgstr "" - -#: ../../changelog/1.4.rst:1788 125621f9069e4b649d7c456fbdf16ddc -msgid "2021-09-30" -msgstr "" - -#: ../../changelog/1.4.rst:1790 fd1f6964e2bd450cb4516189eae63ab8 -msgid ":vytask:`T3874` (bug): D-Link Ethernet Interface not working." -msgstr "" - -#: ../../changelog/1.4.rst:1791 c25e5c860efe42948c383f3df51a61f7 -msgid "" -":vytask:`T3869` (default): Rewrite vyatta_net_name/vyatta_interface_rescan " -"in Python" -msgstr "" - -#: ../../changelog/1.4.rst:1795 40dff7d9fcd74f90ba7f390a2981b597 -msgid "2021-09-28" -msgstr "" - -#: ../../changelog/1.4.rst:1797 a387663723034142bf3bb0b6771b6863 -msgid "" -":vytask:`T3853` (default): nat66 rules gets deleted on reboot in " -"1.4-rolling-202109240217" -msgstr "" - -#: ../../changelog/1.4.rst:1801 7c4a09654e3e4d0798d5e174c9bfbf6a -msgid "2021-09-27" -msgstr "" - -#: ../../changelog/1.4.rst:1803 7ca9fa66c20b45d3b2edd0a3763e4120 -msgid "" -":vytask:`T3863` (default): nat66: commit fails/hangs on non existing " -"interface" -msgstr "" - -#: ../../changelog/1.4.rst:1807 b183557a273641a5860d420222e59915 -msgid "2021-09-26" -msgstr "" - -#: ../../changelog/1.4.rst:1809 a4062619adea455aa20833157cbc1b45 -msgid "" -":vytask:`T3860` (bug): Error on pppoe, tunnel and wireguard interfaces for " -"IPv6 EUI64 addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1810 bd8391b0624243c48196e961f7589505 -msgid "" -":vytask:`T3857` (feature): reboot: send wall message to all users for " -"information" -msgstr "" - -#: ../../changelog/1.4.rst:1811 8a7cd099eebf4b30a396f06af44241ba -msgid ":vytask:`T3867` (bug): vxlan: multicast group address is not validated" -msgstr "" - -#: ../../changelog/1.4.rst:1812 2ac681cd86894f3e84ebd1933da33305 -msgid ":vytask:`T3859` (bug): Add \"log-adjacency-changes\" to ospfv3 process" -msgstr "" - -#: ../../changelog/1.4.rst:1813 bd386d88ea83433c86e4a795b21fc996 -msgid "" -":vytask:`T3826` (bug): PKI: op-mode - do input validation when listing " -"certificates" -msgstr "" - -#: ../../changelog/1.4.rst:1817 a4d253e92ce148828ec4d852cb4e0c3d -msgid "2021-09-25" -msgstr "" - -#: ../../changelog/1.4.rst:1819 8fefde0595fa496aa13a356fa38d11a7 -msgid "" -":vytask:`T3657` (default): BGP neighbors ipv6 not able to establish with " -"IPv6 link-local addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1823 b57a31f3a53c4c378ce517565719491c -msgid "2021-09-23" -msgstr "" - -#: ../../changelog/1.4.rst:1825 ac3d0ad98ed44fb78846220f1fa0b03c -msgid "" -":vytask:`T3850` (bug): Dots are no longer allowed in SSH public key names" -msgstr "" - -#: ../../changelog/1.4.rst:1829 8662e6ffa8e440eca326e3a9e8bf512b -msgid "2021-09-21" -msgstr "" - -#: ../../changelog/1.4.rst:1831 dd7877b321ee46a3b9b6fed0dd1f1fab -msgid "" -":vytask:`T3847` (feature): keepalived/vrrp: migrate to get_config_dict() - " -"cleanup" -msgstr "" - -#: ../../changelog/1.4.rst:1835 9af0fe5267a149998bbc8219758bea78 -msgid "2021-09-20" -msgstr "" - -#: ../../changelog/1.4.rst:1837 bfe6c229569b41eca8d9849600f52536 -msgid "" -":vytask:`T3823` (bug): strip-private does not filter public IPv6 addresses" -msgstr "" - -#: ../../changelog/1.4.rst:1841 ff9c3f47c56442c494de10bcdf8e048e -msgid "2021-09-19" -msgstr "" - -#: ../../changelog/1.4.rst:1843 2c11b9c5b0fa458f87bde6c58463b325 -msgid ":vytask:`T3841` (feature): dhcp-server: add ping-check option to CLI" -msgstr "" - -#: ../../changelog/1.4.rst:1844 00f1cfab52cc4a97895e19b1473fb8fe -msgid "" -":vytask:`T2738` (bug): Modifying configuration in the \"interfaces\" section" -" from VRRP transition scripts causes configuration lockup and high CPU " -"utilization" -msgstr "" - -#: ../../changelog/1.4.rst:1845 a5f5ea9a1b9141bd9019a2013acfe93c -msgid "" -":vytask:`T3840` (feature): dns forwarding: Cache size should allow values > " -"10k" -msgstr "" - -#: ../../changelog/1.4.rst:1846 bf32f9c8dd7d429dbea0b47436c742dd -msgid "" -":vytask:`T3672` (bug): DHCP-FO with multiple subnets results in invalid/non-" -"functioning dhcpd.conf configuration file output" -msgstr "" - -#: ../../changelog/1.4.rst:1850 e4012eed39234ac39eb1e4a0be43b840 -msgid "2021-09-18" -msgstr "" - -#: ../../changelog/1.4.rst:1852 405678c600a1454d9f629e90331724ab -msgid "" -":vytask:`T3831` (bug): External traffic stops routing when IPSEC tunnel " -"comes up with interface vti0" -msgstr "" - -#: ../../changelog/1.4.rst:1853 0b36c9657d0d4df2844b292ca932b14f -msgid ":vytask:`T1968` (default): Allow multiple static routes in dhcp-server" -msgstr "" - -#: ../../changelog/1.4.rst:1854 714bbccd6e3340288fd342f2ac778dbd -msgid "" -":vytask:`T3838` (feature): dhcp-server - sync cli for name-servers to other " -"subsystems" -msgstr "" - -#: ../../changelog/1.4.rst:1855 017f006590cf4ec786881240e511a6fb -msgid "" -":vytask:`T3839` (feature): dhcp-server: Allow configuration of a DNS server " -"and domain name on the shared-network level" -msgstr "" - -#: ../../changelog/1.4.rst:1859 740116798da943918fb4465b94365c8c -msgid "2021-09-17" -msgstr "" - -#: ../../changelog/1.4.rst:1861 0a69fbcad60f4fe5aea5a0b7fabcc633 -msgid "" -":vytask:`T3830` (bug): ipsec: remote-id no longer included in IKE AUTH if " -"not explicitly specified" -msgstr "" - -#: ../../changelog/1.4.rst:1865 146866d545744a5d8e9e5ab0390ee6b9 -msgid "2021-09-11" -msgstr "" - -#: ../../changelog/1.4.rst:1867 bfc333a2935a41e780ef87269aa5f5c7 -msgid "" -":vytask:`T3402` (feature): Add VyOS programming library for operational " -"level commands" -msgstr "" - -#: ../../changelog/1.4.rst:1868 d9a25a88a06743f6a948ad5a9bbd2345 -msgid ":vytask:`T3275` (default): Disable conntrack helpers by default" -msgstr "" - -#: ../../changelog/1.4.rst:1872 9e4d85c63dee40e5bb8480a0c66f2229 -msgid "2021-09-10" -msgstr "" - -#: ../../changelog/1.4.rst:1874 8922db2fb54443deb5f545485c767bef -msgid "" -":vytask:`T3802` (bug): Commit fails if ethernet interface doesn't support " -"flow control" -msgstr "" - -#: ../../changelog/1.4.rst:1875 f2085d96448c45e185f0e54e943411b8 -msgid ":vytask:`T3819` (bug): Upgrade Salt Stack 3002.3 -> 3003 release train" -msgstr "" - -#: ../../changelog/1.4.rst:1876 96a0d82b0ea44890a8bc1672c87fe331 -msgid ":vytask:`T915` (feature): MPLS Support" -msgstr "" - -#: ../../changelog/1.4.rst:1880 232dacf651e648a58d670f9aca848806 -msgid "2021-09-09" -msgstr "" - -#: ../../changelog/1.4.rst:1882 4d35f40a98ce4af2a401846f73568742 -msgid ":vytask:`T3812` (bug): Vyos and frr route-map config out of sync" -msgstr "" - -#: ../../changelog/1.4.rst:1883 e833483c97064a5a90950036f82a5f1e -msgid "" -":vytask:`T3814` (bug): wireguard: commit error showing incorrect peer name " -"from the configured name" -msgstr "" - -#: ../../changelog/1.4.rst:1884 4bd32768bf1f492fad03bcdb7f4a9b94 -msgid "" -":vytask:`T3805` (bug): OpenVPN insufficient privileges for rtnetlink when " -"closing TUN/TAP interface" -msgstr "" - -#: ../../changelog/1.4.rst:1885 55cad370be5b4807a9bad49e57ba764e -msgid "" -":vytask:`T3815` (bug): pki : the file command 'generate pki wireguard key-" -"pair file' is not working" -msgstr "" - -#: ../../changelog/1.4.rst:1889 1ba59d1b3bb1493abff95a56c51df857 -msgid "2021-09-07" -msgstr "" - -#: ../../changelog/1.4.rst:1891 08d5d2c33fc648ec984ac39c77912d70 -msgid "" -":vytask:`T1894` (bug): FRR config not loaded after daemons segfault or " -"restart" -msgstr "" - -#: ../../changelog/1.4.rst:1892 05df6c6bd892420682799020f7b08b42 -msgid "" -":vytask:`T3807` (bug): Op Command \"show interfaces wireguard\" does not " -"show the output" -msgstr "" - -#: ../../changelog/1.4.rst:1896 dc05b0afe4a740088c12dced0b10a634 -msgid "2021-09-06" -msgstr "" - -#: ../../changelog/1.4.rst:1898 dc0563e8bf8e429f8403c4d14326e063 -msgid "" -":vytask:`T3806` (bug): Don't set link local ipv6 address if MTU less then " -"1280" -msgstr "" - -#: ../../changelog/1.4.rst:1899 6f485eeba1bc4f7b8b3da06808cb441c -msgid ":vytask:`T3803` (default): Add source-address option to the ping CLI" -msgstr "" - -#: ../../changelog/1.4.rst:1900 1b2f54dd22884bd69c6f4533b8594083 -msgid ":vytask:`T3431` (bug): Show version all bug" -msgstr "" - -#: ../../changelog/1.4.rst:1901 9f1ee7c126eb4eae857f8f6eea4a2c33 -msgid "" -":vytask:`T2920` (bug): Commit crash when adding the second mGRE tunnel with " -"the same key" -msgstr "" - -#: ../../changelog/1.4.rst:1905 37157e76c6b54384b8dfdd2e54037eff -msgid "2021-09-05" -msgstr "" - -#: ../../changelog/1.4.rst:1907 a45e81c932fa4ac8b47340c3cce4abf7 -msgid "" -":vytask:`T3804` (feature): cli: Migrate and merge \"system name-servers-" -"dhcp\" into \"system name-server\"" -msgstr "" - -#: ../../changelog/1.4.rst:1911 03e08d817a1d471b96fde71e2794e9fb -msgid "2021-09-04" -msgstr "" - -#: ../../changelog/1.4.rst:1913 0163627336184001b01421518e9fe9de -msgid "" -":vytask:`T3619` (bug): Performance Degradation 1.2 --> 1.3 | High ksoftirqd " -"CPU usage" -msgstr "" - -#: ../../changelog/1.4.rst:1917 4ca1c3bf01b94cbba8f0da6097cdf0e0 -msgid "2021-09-03" -msgstr "" - -#: ../../changelog/1.4.rst:1919 5fc9006827664eb8aba9321a204507ac -msgid ":vytask:`T3788` (bug): Keys are not allowed with ipip and sit tunnels" -msgstr "" - -#: ../../changelog/1.4.rst:1920 83229b0c901344759aad4d1bd8d6d82c -msgid "" -":vytask:`T3634` (feature): Add op command option for ping for do not " -"fragment bit to be set" -msgstr "" - -#: ../../changelog/1.4.rst:1921 42ebcb7d8b7b425aa577d020b6f07389 -msgid "" -":vytask:`T3798` (feature): bgp: add support for \"neighbor <X> local-as " -"replace-as\" option" -msgstr "" - -#: ../../changelog/1.4.rst:1925 62e5ecd7246c4620a76b5916dfe6e6ab -msgid "2021-09-02" -msgstr "" - -#: ../../changelog/1.4.rst:1927 db08e293250d4687866e33ff62ef4e44 -msgid "" -":vytask:`T3792` (bug): login: A hypen present in a username from \"system " -"login user\" is replaced by an underscore" -msgstr "" - -#: ../../changelog/1.4.rst:1928 19f8b37a88294c31989fbff0f38c4b4f -msgid "" -":vytask:`T3790` (bug): Does not possible to configure PPTP static ip-address" -" to users" -msgstr "" - -#: ../../changelog/1.4.rst:1929 76f1b91322c0417e989442606b34d0da -msgid "" -":vytask:`T2947` (bug): Nat translation many-many with prefix does not map " -"1-1." -msgstr "" - -#: ../../changelog/1.4.rst:1933 51b8456f7c2c4fbe87e06fbb63ea77ff -msgid "2021-08-31" -msgstr "" - -#: ../../changelog/1.4.rst:1935 59fae2c2fdac4519ba7848d6bc13e3bf -msgid "" -":vytask:`T3789` (feature): Add custom validator for base64 encoded CLI data" -msgstr "" - -#: ../../changelog/1.4.rst:1936 b2195503131140ad84512a2980a49c36 -msgid "" -":vytask:`T3782` (default): Ingress Shaping with IFB No Longer Functional " -"with 1.3" -msgstr "" - -#: ../../changelog/1.4.rst:1940 6b3619bd337a4b80a337cfec30946007 -msgid "2021-08-30" -msgstr "" - -#: ../../changelog/1.4.rst:1942 3a53ccbbab5448afa80d7ea61077d68b -msgid ":vytask:`T3768` (default): Remove early syntaxVersion implementation" -msgstr "" - -#: ../../changelog/1.4.rst:1943 df6450d1f65a41f398c6b4296504943e -msgid "" -":vytask:`T2941` (default): Using a non-ASCII character in the description " -"field causes UnicodeDecodeError in configsource.py" -msgstr "" - -#: ../../changelog/1.4.rst:1944 e956670bb2324d4ea80ec526defcc555 -msgid "" -":vytask:`T3787` (bug): Remove deprecated UDP fragmentation offloading option" -msgstr "" - -#: ../../changelog/1.4.rst:1948 85cde0bcc4c445cdb9fa097204fbafbd -msgid "2021-08-29" -msgstr "" - -#: ../../changelog/1.4.rst:1950 87c4a20a221348179c738db8abcaafb5 -msgid ":vytask:`T3708` (bug): isisd and gre-bridge commit error" -msgstr "" - -#: ../../changelog/1.4.rst:1951 0c51e1399b67433dbd7f7a573c29bb80 -msgid "" -":vytask:`T3783` (bug): \"set protocols isis spf-delay-ietf\" is not working" -msgstr "" - -#: ../../changelog/1.4.rst:1952 5d54e9b0e4c84dcd9e169775b628b756 -msgid ":vytask:`T2750` (default): Use m4 as a template processor" -msgstr "" - -#: ../../changelog/1.4.rst:1956 9d7ae45b14314add90f320d24967773f -msgid "2021-08-28" -msgstr "" - -#: ../../changelog/1.4.rst:1958 8a16bee8e2c546ccbe48f86c61231b76 -msgid "" -":vytask:`T3743` (bug): l2tp doesn't work after reboot if outside-address not" -" 0.0.0.0" -msgstr "" - -#: ../../changelog/1.4.rst:1962 5edea07ac2fe4b30aae4c25cb9d40e7c -msgid "2021-08-27" -msgstr "" - -#: ../../changelog/1.4.rst:1964 71b0c500dddb4003bd6aff931526b4b6 -msgid ":vytask:`T3182` (bug): Main blocker Task for FRR 7.4/7.5 series update" -msgstr "" - -#: ../../changelog/1.4.rst:1965 3ee03a1f19654932a2aa88cc546d8a90 -msgid ":vytask:`T3568` (feature): Add XML for firewall conf-mode" -msgstr "" - -#: ../../changelog/1.4.rst:1966 01dc28e12de8412abb80a06208215bf6 -msgid "" -":vytask:`T2108` (default): Use minisign/signify instead of GPG for release " -"signing" -msgstr "" - -#: ../../changelog/1.4.rst:1970 bc6ad445fba342879442988b0a3075c4 -msgid "2021-08-26" -msgstr "" - -#: ../../changelog/1.4.rst:1972 e8687106311742acb7db5e102c2ff1df -msgid ":vytask:`T3776` (default): Rename FRR daemon restart op-mode commands" -msgstr "" - -#: ../../changelog/1.4.rst:1973 51aac3b400fc4b20b9168610835c6ef3 -msgid ":vytask:`T3739` (feature): policy: route-map: add EVPN match support" -msgstr "" - -#: ../../changelog/1.4.rst:1977 59ee0987f8d0446ca9aac9c3326ce4f9 -msgid "2021-08-25" -msgstr "" - -#: ../../changelog/1.4.rst:1979 c596820773634bf285c0a4f723ebc5a0 -msgid "" -":vytask:`T3773` (bug): Delete the \"show system integrity\" command (to " -"prepare for a re-implementation)" -msgstr "" - -#: ../../changelog/1.4.rst:1980 5363a1da660f4f8aa3c8eea84e658a3c -msgid ":vytask:`T3775` (bug): Typo in generated Strongswan VPN-config" -msgstr "" - -#: ../../changelog/1.4.rst:1984 1e7b929727124a93a3e968f1c71b3150 -msgid "2021-08-24" -msgstr "" - -#: ../../changelog/1.4.rst:1986 d5383a2222384fd48da8186bc2e83fc5 -msgid "" -":vytask:`T3772` (bug): VRRP virtual interfaces are not shown in show " -"interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:1990 fd99d54333ff40a0a4e7ea10b04f0425 -msgid "2021-08-23" -msgstr "" - -#: ../../changelog/1.4.rst:1992 dbd02383096d49c394510a94255ebf8a -msgid ":vytask:`T3769` (feature): Containers: Network Bridging" -msgstr "" - -#: ../../changelog/1.4.rst:1996 621e5d74b7dd46568b75b3c23e7dcda4 -msgid "2021-08-22" -msgstr "" - -#: ../../changelog/1.4.rst:1998 ceb502dd8d2f4ffb927b066dff8f626d -msgid "" -":vytask:`T3090` (feature): Move 'adjust-mss' firewall options to the " -"interface section." -msgstr "" - -#: ../../changelog/1.4.rst:1999 8dc38f62612440c3946b0b2762c78006 -msgid ":vytask:`T3765` (default): container: additional op-mode commands" -msgstr "" - -#: ../../changelog/1.4.rst:2003 b85fb82d445b4769b7bd7676417c7f53 -msgid "2021-08-20" -msgstr "" - -#: ../../changelog/1.4.rst:2005 e052268e79864d9f9cac0ab6a4c0da44 -msgid "" -":vytask:`T1950` (default): Store VyOS configuration syntax version data in " -"JSON file" -msgstr "" - -#: ../../changelog/1.4.rst:2009 a85cee57e99348ada91c97775c684240 -msgid "2021-08-19" -msgstr "" - -#: ../../changelog/1.4.rst:2011 85624bffcfc14bc581f3128e2f9b4405 -msgid ":vytask:`T3751` (bug): pki generate ca add new line after passphrase" -msgstr "" - -#: ../../changelog/1.4.rst:2012 1bf242d41f1248c5a29945c05f667afe -msgid ":vytask:`T3764` (bug): Unconfigurable IKE and ESP lifetime" -msgstr "" - -#: ../../changelog/1.4.rst:2013 1b6399471cad45efbd0f755451cc62a6 -msgid "" -":vytask:`T3234` (bug): multi_to_list fails in certain cases, with root cause" -" an element redundancy in XML interface-definitions" -msgstr "" - -#: ../../changelog/1.4.rst:2014 681bfb60adcf43248ba4362cd62fc547 -msgid "" -":vytask:`T3732` (feature): override-default helper should support adding " -"defaultValues to default less nodes" -msgstr "" - -#: ../../changelog/1.4.rst:2015 6efab03dae0046229f8e295c5b9c782e -msgid "" -":vytask:`T3574` (default): Add constraintGroup for combining validators with" -" logical AND" -msgstr "" - -#: ../../changelog/1.4.rst:2016 ff1b574628834b49a8c413439caa8715 -msgid ":vytask:`T3759` (default): [L3VPN] VPNv4/VPNv6 add commands" -msgstr "" - -#: ../../changelog/1.4.rst:2020 e94f7e7c20fe4149b33cb87b3c64d59d -msgid "2021-08-18" -msgstr "" - -#: ../../changelog/1.4.rst:2022 aa50702b7aa1406ab6fd3066c4d18470 -msgid "" -":vytask:`T3752` (bug): generate pki certificate file xxx doesn't touch file" -msgstr "" - -#: ../../changelog/1.4.rst:2026 2ea67792c05745ae8fa5e813374b02db -msgid "2021-08-16" -msgstr "" - -#: ../../changelog/1.4.rst:2028 7b6a9da8a9bf4a14b9658f9ed1ad1300 -msgid "" -":vytask:`T3738` (default): openvpn fails if server and authentication are " -"configured" -msgstr "" - -#: ../../changelog/1.4.rst:2029 d05759f24aab490590dae79216764f1d -msgid ":vytask:`T1594` (bug): l2tpv3 error on IPv6 local-ip" -msgstr "" - -#: ../../changelog/1.4.rst:2033 3e086be0fb534a65a2f1219dc721aa44 -msgid "2021-08-15" -msgstr "" - -#: ../../changelog/1.4.rst:2035 f938acdc726b4de88a13478db0e7f59f -msgid "" -":vytask:`T3756` (default): VyOS generates invalid QR code for wireguard " -"clients" -msgstr "" - -#: ../../changelog/1.4.rst:2036 a94c9d13763440a89283b5f6a80b673f -msgid "" -":vytask:`T3757` (default): OSPF: add support to configure the area at an " -"interface level" -msgstr "" - -#: ../../changelog/1.4.rst:2040 c9983cfbf31549319f82519329011c92 -msgid "2021-08-14" -msgstr "" - -#: ../../changelog/1.4.rst:2042 662ef937c3684f0594bfa2bbabd8fd84 -msgid ":vytask:`T3745` (feature): op-mode IPSec show vpn ipse sa sorting" -msgstr "" - -#: ../../changelog/1.4.rst:2046 2cf969c7cac847749ba031452ede59ae -msgid "2021-08-13" -msgstr "" - -#: ../../changelog/1.4.rst:2048 2f5b238fdd214c2fa65bd761846124a4 -msgid "" -":vytask:`T3749` (bug): V4/V6 Counters in network container validation aren't" -" being reset" -msgstr "" - -#: ../../changelog/1.4.rst:2049 5331b8b5931940cab914b2da09b233f0 -msgid ":vytask:`T3728` (bug): FRR not respect configured RD and RT for L3VNI" -msgstr "" - -#: ../../changelog/1.4.rst:2050 763257c76f2d449f852c843532fd1127 -msgid "" -":vytask:`T3727` (bug): VPN IPsec ESP proposal and ESP presented in config " -"missmatch" -msgstr "" - -#: ../../changelog/1.4.rst:2051 316ab7fad2e34a56ae5d5ee52f920466 -msgid ":vytask:`T3740` (bug): HTTPs API breaks when the address is IPv6" -msgstr "" - -#: ../../changelog/1.4.rst:2055 50fa266218ad424bae610547a4c83e35 -msgid "2021-08-12" -msgstr "" - -#: ../../changelog/1.4.rst:2057 128e05a512ca49f3b192006723c5acc5 -msgid "" -":vytask:`T3731` (bug): verify_accel_ppp_base_service return wrong config " -"error for SSP" -msgstr "" - -#: ../../changelog/1.4.rst:2058 7de559034c2f4673a1c247058a0dcb87 -msgid ":vytask:`T3405` (feature): PPPoE server unit-cache" -msgstr "" - -#: ../../changelog/1.4.rst:2059 d3df1602f1fb49d7ab27e4da9a401d4d -msgid "" -":vytask:`T2432` (default): dhcpd: Can't create new lease file: Permission " -"denied" -msgstr "" - -#: ../../changelog/1.4.rst:2060 f19bc5d89061408193bb883f071ee15d -msgid "" -":vytask:`T3746` (feature): Inform users logging into the system about a " -"pending reboot" -msgstr "" - -#: ../../changelog/1.4.rst:2061 53750c1be6744fbe8ca04eb54dff3089 -msgid "" -":vytask:`T3744` (default): Dns forwarding statistics formatting missing a " -"new line" -msgstr "" - -#: ../../changelog/1.4.rst:2065 1ab4a7fd10a646bdb0ec74b009fcd86c -msgid "2021-08-11" -msgstr "" - -#: ../../changelog/1.4.rst:2067 53fed2f4a1a345e995592987364176fe -msgid "" -":vytask:`T3709` (feature): Snmp: Allow enable MIDs/OIDs ipCidrRouteTable" -msgstr "" - -#: ../../changelog/1.4.rst:2071 a920a33329d4408b89ce8c81dfea0c79 -msgid "2021-08-09" -msgstr "" - -#: ../../changelog/1.4.rst:2073 d53818f12bfc47a8ad8b692e98b29028 -msgid "" -":vytask:`T3720` (bug): IPSec set vti secondary address cause interface " -"disable" -msgstr "" - -#: ../../changelog/1.4.rst:2077 7be9e0b3a1a24bbfa9aad5d766068968 -msgid "2021-08-08" -msgstr "" - -#: ../../changelog/1.4.rst:2079 58831d995dfa44c8ab67d9b60f1229b8 -msgid "" -":vytask:`T3705` (bug): IPSec: VTI interface does not honor default-esp-group" -msgstr "" - -#: ../../changelog/1.4.rst:2080 f221488d523d4fe3955970f1f1cffee6 -msgid "" -":vytask:`T2027` (bug): get_config_dict is failing when the configuration " -"section is empty/missing" -msgstr "" - -#: ../../changelog/1.4.rst:2084 6c5bcb4e1bc4409199757f598cfa5e32 -msgid "2021-08-05" -msgstr "" - -#: ../../changelog/1.4.rst:2086 2f69478aa77c49888ab5981f3aef76e3 -msgid ":vytask:`T3719` (bug): Restart vpn shows some missed files" -msgstr "" - -#: ../../changelog/1.4.rst:2090 2fb812692ff349798afc2f423def1a89 -msgid "2021-08-04" -msgstr "" - -#: ../../changelog/1.4.rst:2092 b39499a3dbf8427c9c7bf44767121752 -msgid "" -":vytask:`T3704` (feature): Add ability to interact with Areca RAID adapers" -msgstr "" - -#: ../../changelog/1.4.rst:2093 22fbc207aee94c9d8c91e7959c04a8d8 -msgid "" -":vytask:`T3718` (bug): VPN IPsec IKE group by default not use DH-group 2" -msgstr "" - -#: ../../changelog/1.4.rst:2097 4cc12ac719c24fb293dfae54ad12662c -msgid "2021-08-02" -msgstr "" - -#: ../../changelog/1.4.rst:2099 e6042b10d2e74a27bca6d526f3c00f30 -msgid "" -":vytask:`T3601` (default): Error in ssh keys for vmware cloud-init if ssh " -"keys is left empty." -msgstr "" - -#: ../../changelog/1.4.rst:2103 24b0ceda7f404148b5593d18f152e10e -msgid "2021-08-01" -msgstr "" - -#: ../../changelog/1.4.rst:2105 9c312a178a0e4e719754add218f3d9fd -msgid ":vytask:`T3707` (bug): Ping incorrect ip host checks" -msgstr "" - -#: ../../changelog/1.4.rst:2109 be65c4ac28b144d68fe095d9b743bae2 -msgid "2021-07-31" -msgstr "" - -#: ../../changelog/1.4.rst:2111 bb401ab222c84f059b3d1f1b1c79af36 -msgid "" -":vytask:`T3716` (feature): Linux kernel parameters " -"ignore_routes_with_link_down- ignore disconnected routing connections" -msgstr "" - -#: ../../changelog/1.4.rst:2115 ae7c6f5ee03e4f41b3d4c56af8e4fecc -msgid "2021-07-30" -msgstr "" - -#: ../../changelog/1.4.rst:2117 fb56dce8a138408ab088318d8a500831 -msgid ":vytask:`T1176` (default): FRR - BGP replicating routes" -msgstr "" - -#: ../../changelog/1.4.rst:2118 922c34fa2a7e467b88b5b27a2e1c0cc1 -msgid ":vytask:`T1210` (feature): About IKEv2 IPSec VPN remote access" -msgstr "" - -#: ../../changelog/1.4.rst:2122 8a2e4944f4e0435b87c5d8c106a6e0d9 -msgid "2021-07-23" -msgstr "" - -#: ../../changelog/1.4.rst:2124 0e16bd80e01040d69edf8915f14cfc91 -msgid "" -":vytask:`T3699` (bug): login: verify selected \"system login user\" name is " -"not already used by the base system." -msgstr "" - -#: ../../changelog/1.4.rst:2125 d9baa8af66764badb2cf7c429147876f -msgid ":vytask:`T3698` (default): Support bridge monitoring" -msgstr "" - -#: ../../changelog/1.4.rst:2129 69e5395cee2e43229afa3f5485dbaf7c -msgid "2021-07-13" -msgstr "" - -#: ../../changelog/1.4.rst:2131 36db7ff3b7a54887948ada13ace33119 -msgid "" -":vytask:`T3679` (default): Point the unexpected exception message link to " -"the new rolling release location" -msgstr "" - -#: ../../changelog/1.4.rst:2135 a07377c737ad4272b7f9a2414973b94e -msgid "2021-07-11" -msgstr "" - -#: ../../changelog/1.4.rst:2137 9c3ee076ab294751a203f84431af5817 -msgid "" -":vytask:`T3665` (bug): Missing VRF support for VxLAN but already documented" -msgstr "" - -#: ../../changelog/1.4.rst:2141 7301470883ce4d9796aba91226bfc49c -msgid "2021-07-10" -msgstr "" - -#: ../../changelog/1.4.rst:2143 bce098dc6cf14f3882b61d890a341b9a -msgid ":vytask:`T3636` (feature): SSTP / L2TP ipv6 support broken" -msgstr "" - -#: ../../changelog/1.4.rst:2147 b49a825ae8ea4ffdade6e9531eb63ca0 -msgid "2021-07-09" -msgstr "" - -#: ../../changelog/1.4.rst:2149 4bd593a236e04f3d8f51e68f28ac8f7a -msgid ":vytask:`T3667` (bug): brctl is damaged" -msgstr "" - -#: ../../changelog/1.4.rst:2153 5eae7388a7f84a1a9bb4f4e9066435c9 -msgid "2021-07-06" -msgstr "" - -#: ../../changelog/1.4.rst:2155 0b20f1de418c417086ab07261fc148db -msgid "" -":vytask:`T3660` (feature): Conntrack-Sync configuration command to specify " -"destination udp port for peer" -msgstr "" - -#: ../../changelog/1.4.rst:2159 ba00804a9b9a4798b15ee92eec86d29a -msgid "2021-07-03" -msgstr "" - -#: ../../changelog/1.4.rst:2161 fd8c05ff5bd84dbfb0a511e7823d9e5d -msgid "" -":vytask:`T57` (enhancment): Make it possible to disable the entire IPsec " -"peer" -msgstr "" - -#: ../../changelog/1.4.rst:2165 ee5ac790a47b4966a9e1f498aeb48fc4 -msgid "2021-07-01" -msgstr "" - -#: ../../changelog/1.4.rst:2167 4338dd9357c946c8a4db0042269c4aeb -msgid ":vytask:`T3658` (feature): Add support for dhcpdv6 fixed-prefix6" -msgstr "" - -#: ../../changelog/1.4.rst:2168 fab8fe99831a41eaa9a824582b44d118 -msgid "" -":vytask:`T2035` (bug): Executing vyos-smoketest multiple times makes ssh " -"test fail on execution" -msgstr "" - -#: ../../changelog/1.4.rst:2172 5a7b529cc2f5462a8044fde11c539382 -msgid "2021-06-29" -msgstr "" - -#: ../../changelog/1.4.rst:2174 f264612441c14f39bc5a96232b6e98d1 -msgid ":vytask:`T3593` (bug): PPPoE server called-sid format does not work" -msgstr "" - -#: ../../changelog/1.4.rst:2175 ee1f2177f36b4ae998e5c736f703f63e -msgid ":vytask:`T1441` (feature): Add support for IPSec XFRM interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:2179 2f350de07ddd451c9f87092a03d2391d -msgid "2021-06-25" -msgstr "" - -#: ../../changelog/1.4.rst:2181 9b925f87351241bf8698d0376e56669f -msgid "" -":vytask:`T3641` (feature): Upgrade base system from Debian Buster -> Debian " -"Bullseye" -msgstr "" - -#: ../../changelog/1.4.rst:2182 14e84eb8e9f1455388bb7ce7116e2b18 -msgid ":vytask:`T3649` (feature): Add bonding additional hash-policy" -msgstr "" - -#: ../../changelog/1.4.rst:2186 42c3744b5ac24cabaa03d64a400e0c89 -msgid "2021-06-23" -msgstr "" - -#: ../../changelog/1.4.rst:2188 a6d00ae44e1649b388e094fc73cc07f3 -msgid "" -":vytask:`T3647` (feature): Bullseye: gcc defaults to passing --as-needed to " -"linker" -msgstr "" - -#: ../../changelog/1.4.rst:2192 53f4e5e37601432793a0a13a21a4c545 -msgid "2021-06-22" -msgstr "" - -#: ../../changelog/1.4.rst:2194 6b5de19e71314d9fa68cc671ab07b73f -msgid ":vytask:`T3629` (bug): IPoE server shifting address in the range" -msgstr "" - -#: ../../changelog/1.4.rst:2195 185482a5662445fbb9b0a5d8948520fd -msgid "" -":vytask:`T3645` (feature): Bullseye: ethtool changed output for ring-buffer " -"information" -msgstr "" - -#: ../../changelog/1.4.rst:2199 59dbae31bb6d45939eb5d6e5757c46fc -msgid "2021-06-21" -msgstr "" - -#: ../../changelog/1.4.rst:2201 fdc2eaad6f3c4114b0ecc43d83c5d0b1 -msgid "" -":vytask:`T3563` (default): commit-archive breaks with IPv6 source addresses" -msgstr "" - -#: ../../changelog/1.4.rst:2205 43374db4c2194dcd9ccb86716775aca1 -msgid "2021-06-20" -msgstr "" - -#: ../../changelog/1.4.rst:2207 0189a962e4924ef0aae34a53a261a1ec -msgid ":vytask:`T3637` (bug): vrf: bind-to-all didn't work properly" -msgstr "" - -#: ../../changelog/1.4.rst:2208 49932da4dc0d4f8cb458d25e6bdd269b -msgid ":vytask:`T3639` (default): GCC preprocessor clobbers C comments" -msgstr "" - -#: ../../changelog/1.4.rst:2212 43ceb331dd6143e9b224471785fcd41c -msgid "2021-06-19" -msgstr "" - -#: ../../changelog/1.4.rst:2214 5f6a0359e2324e168cb43a76604c2775 -msgid ":vytask:`T3633` (feature): Add LRO offload for interface ethernet" -msgstr "" - -#: ../../changelog/1.4.rst:2218 fe8a808d4e7240318ee9a17c1a6021cc -msgid "2021-06-18" -msgstr "" - -#: ../../changelog/1.4.rst:2220 a51b721c18b34f43aa5ef6671a44c31e -msgid ":vytask:`T3599` (default): Migrate NHRP to XML/Python" -msgstr "" - -#: ../../changelog/1.4.rst:2224 76632780d24f40aba19c554983aa1a4b -msgid "2021-06-17" -msgstr "" - -#: ../../changelog/1.4.rst:2226 04a3ee334ba24439a187aa44b52ea18f -msgid "" -":vytask:`T3624` (feature): BGP: add support for extended community bandwidth" -" definition" -msgstr "" - -#: ../../changelog/1.4.rst:2230 9cc09c5575344c2a84a73121e100b5d8 -msgid "2021-06-16" -msgstr "" - -#: ../../changelog/1.4.rst:2232 0ec98b69d5544cdaa386119955be9070 -msgid "" -":vytask:`T3623` (default): Fix for dummy interface option in the operational" -" command \"clear interfaces dummy\"" -msgstr "" - -#: ../../changelog/1.4.rst:2233 2fd6d776532941f5bb8013daf699591e -msgid ":vytask:`T3630` (feature): op-mode: add \"show version kernel\" command" -msgstr "" - -#: ../../changelog/1.4.rst:2237 7b09d54f21064b9abaf18dbaa79a7b44 -msgid "2021-06-13" -msgstr "" - -#: ../../changelog/1.4.rst:2239 a206ad8c663b4c4a924abee274b2e645 -msgid "" -":vytask:`T3620` (feature): Rename WWAN interface from wirelessmodem to wwan " -"to use QMI interface" -msgstr "" - -#: ../../changelog/1.4.rst:2240 2ca072c407344ee2995ef6d2e3e418d5 -msgid "" -":vytask:`T2173` (feature): Add the ability to use VRF on VTI interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:2241 5c825fc46e6944afbe364acb4afddc25 -msgid ":vytask:`T3622` (feature): WWAN: add support for APN authentication" -msgstr "" - -#: ../../changelog/1.4.rst:2242 ae4a106205f34887960289edda98d3c9 -msgid ":vytask:`T3606` (bug): SNMP unknown notification OID" -msgstr "" - -#: ../../changelog/1.4.rst:2243 40df295113ee4cfab3243b90f6921073 -msgid "" -":vytask:`T3621` (bug): PPPoE interface does not validate if password is " -"supplied when username is set" -msgstr "" - -#: ../../changelog/1.4.rst:2247 cd3eb3f3d0c0443d886ec551252be6fa -msgid "2021-06-12" -msgstr "" - -#: ../../changelog/1.4.rst:2249 5b9551abe88b425e9e334de953cf4455 -msgid "" -":vytask:`T3611` (bug): WWAN interface (MC7710) no longer works on Kernel " -"5.10" -msgstr "" - -#: ../../changelog/1.4.rst:2250 17f4c3d69ffd4767958c5666e7927329 -msgid ":vytask:`T1534` (bug): IPSec w/ IKEv2 Invalid local-address \"any\"" -msgstr "" - -#: ../../changelog/1.4.rst:2251 d6ac23d90acd4d92ba24866bff3823f5 -msgid "" -":vytask:`T3616` (bug): Update to FastAPI causes regression in vyos-http-api-" -"server" -msgstr "" - -#: ../../changelog/1.4.rst:2255 76ff5e44b3824ce0a02f8d1f480826d4 -msgid "2021-06-11" -msgstr "" - -#: ../../changelog/1.4.rst:2257 7a79e847d045411ea46c03204a87eb56 -msgid ":vytask:`T3614` (bug): Container network name with hyphen fail" -msgstr "" - -#: ../../changelog/1.4.rst:2261 b798913afa2f4f97b2402edd87564069 -msgid "2021-06-10" -msgstr "" - -#: ../../changelog/1.4.rst:2263 9e57a218248c420688f592b75b949c81 -msgid ":vytask:`T3250` (bug): PPPoE server: wrong local usernames" -msgstr "" - -#: ../../changelog/1.4.rst:2264 5f09b48bb66f4b30ba0988aa350a33b6 -msgid "" -":vytask:`T3138` (bug): ddclient improperly updated when apply rfc2136 config" -msgstr "" - -#: ../../changelog/1.4.rst:2265 b9d4532989df4a2b8f9c76450b884e0e -msgid "" -":vytask:`T2645` (default): Editing route-map action requires adding a new " -"rule" -msgstr "" - -#: ../../changelog/1.4.rst:2269 d80260a029cb4a1f8e5253dfcae0b63f -msgid "2021-06-08" -msgstr "" - -#: ../../changelog/1.4.rst:2271 4a0af091cdcb4c1a9023baad4c8fcd16 -msgid "" -":vytask:`T3605` (default): Allow to set prefer-global for ipv6-next-hop" -msgstr "" - -#: ../../changelog/1.4.rst:2272 fc670f3b7a6745f2aa5d1720573d5b69 -msgid ":vytask:`T3607` (feature): [route-map] set ipv6 next-hop prefer-global" -msgstr "" - -#: ../../changelog/1.4.rst:2273 ce9dcffc1ab64e5f8ceb4397b4078cb9 -msgid ":vytask:`T3289` (bug): No description for node \"service\" conf-mode" -msgstr "" - -#: ../../changelog/1.4.rst:2277 8159a8efcaf2446db31b1b729e2b0f5f -msgid "2021-06-07" -msgstr "" - -#: ../../changelog/1.4.rst:2279 5ce34e420db6479c89d0d5e98c612922 -msgid ":vytask:`T3461` (bug): OpenConnect Server redundancy check" -msgstr "" - -#: ../../changelog/1.4.rst:2280 4a7a7229a2f44610ab60d185d1621d90 -msgid ":vytask:`T3455` (bug): system users can not be added in \"edit\"" -msgstr "" - -#: ../../changelog/1.4.rst:2281 3a5d4229039f4ad79ec3acb59e6d122b -msgid "" -":vytask:`T3588` (default): IPSec: migrate no longer available options from " -"CLI which are now hardcoded/enabled in strongSwan" -msgstr "" - -#: ../../changelog/1.4.rst:2285 b3a036656586432fbecd5de766265d03 -msgid "2021-06-06" -msgstr "" - -#: ../../changelog/1.4.rst:2287 b430f29e1b0b4200bb6fd4a505b51ec2 -msgid "" -":vytask:`T842` (feature): Adopt VyOS CLI to latest StrongSwan options and " -"deprecated Keywords" -msgstr "" - -#: ../../changelog/1.4.rst:2291 8150ef6f35f84629a39729cd66284c76 -msgid "2021-06-04" -msgstr "" - -#: ../../changelog/1.4.rst:2293 30ed260e13564559a6167fc7615f8b7a -msgid ":vytask:`T3595` (default): Cannot create new VTI interface" -msgstr "" - -#: ../../changelog/1.4.rst:2294 abc29975c80442378ed71db44348605d -msgid ":vytask:`T3592` (feature): Set default TTL 64 for tunnels" -msgstr "" - -#: ../../changelog/1.4.rst:2298 1c45438b9f6b4ec3a7b9aca2d511d500 -msgid "2021-06-03" -msgstr "" - -#: ../../changelog/1.4.rst:2300 6108f5eed5ee4258a0d9f29ee149a8d1 -msgid ":vytask:`T3384` (feature): Support UDP bandwidth testing" -msgstr "" - -#: ../../changelog/1.4.rst:2304 0931dcb8af0e4637b56915348bf7e3a4 -msgid "2021-06-02" -msgstr "" - -#: ../../changelog/1.4.rst:2306 9a8459ab42f24dd88cf38e446c2ef3ae -msgid ":vytask:`T3233` (bug): Interface redirect to dum0" -msgstr "" - -#: ../../changelog/1.4.rst:2310 e5495934567c436bbc87c63bf7d669d1 -msgid "2021-06-01" -msgstr "" - -#: ../../changelog/1.4.rst:2312 bcd1604af76241bcbcc84181a77fb6db -msgid "" -":vytask:`T3585` (default): Fix NHRP module for updated interfaces tunnel " -"syntax" -msgstr "" - -#: ../../changelog/1.4.rst:2313 e662de4ac6f040c8af4c96d6da0d9cf3 -msgid ":vytask:`T3594` (bug): Disable by default service strongswan-starter" -msgstr "" - -#: ../../changelog/1.4.rst:2317 47e160e19cf74bee9652a50022031a7c -msgid "2021-05-30" -msgstr "" - -#: ../../changelog/1.4.rst:2319 4f65e0f160594096b85e5c8fd94847cf -msgid ":vytask:`T3518` (bug): Warning messages when using SCP commit-archive" -msgstr "" - -#: ../../changelog/1.4.rst:2320 ae973970e0cc40929401653c1c5a8db7 -msgid ":vytask:`T3093` (default): Add xml for vpn ipsec" -msgstr "" - -#: ../../changelog/1.4.rst:2321 c4549bbf5d754003b54743a384af02ae -msgid "" -":vytask:`T1866` (bug): Commit archive over SFTP doesn't work with non-" -"standard ports" -msgstr "" - -#: ../../changelog/1.4.rst:2322 703b09eeeca8477fbd0479541e73d672 -msgid "" -":vytask:`T3590` (feature): bgp: add option for limiting maximum number of " -"prefixes to be sent to a peer" -msgstr "" - -#: ../../changelog/1.4.rst:2323 8c0564122ec4436da5003648943e4fe0 -msgid "" -":vytask:`T3589` (feature): op-mode: support clearing out logfiles from CLI" -msgstr "" - -#: ../../changelog/1.4.rst:2324 1a6353e8d914498fa85f99be8addcc3c -msgid "" -":vytask:`T2641` (feature): Rewrite vpn ipsec OP commands in new style XML " -"syntax" -msgstr "" - -#: ../../changelog/1.4.rst:2325 376f350d249a4393a95cf581f9639bcf -msgid "" -":vytask:`T3351` (feature): Installer checking MD5 checksums on the ISO image" -msgstr "" - -#: ../../changelog/1.4.rst:2329 90b28fe875734507bda675a5a60b3f97 -msgid "2021-05-29" -msgstr "" - -#: ../../changelog/1.4.rst:2331 416e06ef6c7f469ca87cc1796ecb7098 -msgid "" -":vytask:`T1944` (bug): FRR: Invalid route in BGP causes update storm, memory" -" leak, and failure of Zebra" -msgstr "" - -#: ../../changelog/1.4.rst:2332 44f918a82ab04cc490c6b0adf37a4a25 -msgid ":vytask:`T1888` (feature): Update to StrongSwan 5.9.1" -msgstr "" - -#: ../../changelog/1.4.rst:2336 e1d8de8a1bdc40e8b979c5233a73ae58 -msgid "2021-05-27" -msgstr "" - -#: ../../changelog/1.4.rst:2338 b24e037f78094705908a43e17a23585f -msgid "" -":vytask:`T3561` (feature): router-advert: support advertising specific " -"routes" -msgstr "" - -#: ../../changelog/1.4.rst:2339 bcd325908bed4002a870175be41ea68c -msgid ":vytask:`T2669` (bug): DHCP-server overlapping ranges." -msgstr "" - -#: ../../changelog/1.4.rst:2343 e7875a1d6338434b91442352d2b74426 -msgid "2021-05-26" -msgstr "" - -#: ../../changelog/1.4.rst:2345 747da268d5b54cb4b846b1f6c356b6d7 -msgid "" -":vytask:`T3540` (bug): Keepalived memory utilisation issue when constantly " -"getting its state in JSON format" -msgstr "" - -#: ../../changelog/1.4.rst:2349 4e4b6d4ab4004e27897de8cf884d248e -msgid "2021-05-24" -msgstr "" - -#: ../../changelog/1.4.rst:2351 efc8a0eeaf8946328f94fee88bb4780b -msgid "" -":vytask:`T3575` (bug): pseudo-ethernet: must check source-interface MTU" -msgstr "" - -#: ../../changelog/1.4.rst:2352 4a40d919a4af4b469bc0fe1d4668a2ca -msgid ":vytask:`T3571` (bug): Broken Show Tab Complete" -msgstr "" - -#: ../../changelog/1.4.rst:2353 f6bb6563dbab4d5c832a5049202b6bf6 -msgid "" -":vytask:`T3555` (bug): GRE TAP tunnel does not silent fragment packets / " -"kernel fix available" -msgstr "" - -#: ../../changelog/1.4.rst:2354 b28df4854c634defb19c2b382fcd81a2 -msgid ":vytask:`T3576` (bug): ISIS does not support IPV6" -msgstr "" - -#: ../../changelog/1.4.rst:2358 c751007cdbda45e6b3594e947930c7c1 -msgid "2021-05-23" -msgstr "" - -#: ../../changelog/1.4.rst:2360 e6898954ded5495baaf7fe19211dd653 -msgid "" -":vytask:`T3570` (default): Prevent setting of a larger MTU on child " -"interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:2361 483c8c557cd0495ca826a128643c5665 -msgid ":vytask:`T3573` (bug): as-path-prepend Description Invalid" -msgstr "" - -#: ../../changelog/1.4.rst:2362 79a724fc30724867a0f85d321b28c3b8 -msgid ":vytask:`T3572` (feature): Basic Drive Diagnostic Tools" -msgstr "" - -#: ../../changelog/1.4.rst:2366 a42790b45748454891933ac894b7b579 -msgid "2021-05-22" -msgstr "" - -#: ../../changelog/1.4.rst:2368 caffe83aeb7b472ca7c3bb735afbe2bf -msgid "" -":vytask:`T3564` (default): Multiple BGP Confederation Peers Not Allowed" -msgstr "" - -#: ../../changelog/1.4.rst:2372 8ef37d39732d4da78e0a694e022bbd09 -msgid "2021-05-21" -msgstr "" - -#: ../../changelog/1.4.rst:2374 ba9fa80b60ea46f8bd0590519b841faf -msgid ":vytask:`T3551` (bug): QoS control failure of VLAN sub interface" -msgstr "" - -#: ../../changelog/1.4.rst:2378 238994300481439b80c67179a0356198 -msgid "2021-05-20" -msgstr "" - -#: ../../changelog/1.4.rst:2380 123a1824956c4fa2ae22c319954b75a1 -msgid ":vytask:`T3554` (feature): Add area-type stub for ospfv3" -msgstr "" - -#: ../../changelog/1.4.rst:2381 7e0b2f35da7c45da8985d80fe59053f2 -msgid "" -":vytask:`T3565` (feature): sysctl: rewrite in XML and Python and drop from " -"vyatta-cfg-system" -msgstr "" - -#: ../../changelog/1.4.rst:2385 20ff2fcb843a4f398559ab28436f0b38 -msgid "2021-05-19" -msgstr "" - -#: ../../changelog/1.4.rst:2387 c2377c7b469a4ac1b49aa9f570572e44 -msgid ":vytask:`T3562` (feature): Update Accel-PPP to a newer revision" -msgstr "" - -#: ../../changelog/1.4.rst:2388 c416d48a0bad445f8a10477b62c6c2cd -msgid "" -":vytask:`T3559` (feature): Add restart op-command for OpenConnect Server" -msgstr "" - -#: ../../changelog/1.4.rst:2392 4490c910acc04fddb14088567c1d1a96 -msgid "2021-05-18" -msgstr "" - -#: ../../changelog/1.4.rst:2394 be753854bcaa4774814754591a3ca3a7 -msgid ":vytask:`T3525` (default): VMWare resume script syntax errors" -msgstr "" - -#: ../../changelog/1.4.rst:2398 63b5e18837f44a978d82bf946e8f9183 -msgid "2021-05-15" -msgstr "" - -#: ../../changelog/1.4.rst:2400 441bc0b9a76b4a3cbcd8cedf2eb1dc61 -msgid "" -":vytask:`T3549` (bug): DHCPv6 \"service dhcpv6-server global-parameters " -"name-server\" is not correctly exported to dhcpdv6.conf when multiple name-" -"server entries are present" -msgstr "" - -#: ../../changelog/1.4.rst:2401 1b952e77a71b4a6b92c6579f9357e874 -msgid "" -":vytask:`T3532` (bug): Not possible to change ethertype after interface " -"creation" -msgstr "" - -#: ../../changelog/1.4.rst:2402 0883eb317c58419d9ace0329c4b6a08f -msgid ":vytask:`T3550` (bug): Router-advert completion typo" -msgstr "" - -#: ../../changelog/1.4.rst:2403 62a20a33092d4df7a7f47a3a3c3c3dc4 -msgid "" -":vytask:`T3547` (feature): conntrackd: remove deprecated config options" -msgstr "" - -#: ../../changelog/1.4.rst:2404 a1ccf77559d4477e9533c498eeb830ca -msgid "" -":vytask:`T3535` (feature): Rewrite vyatta-conntrack-sync in new XML and " -"Python flavor" -msgstr "" - -#: ../../changelog/1.4.rst:2408 20cf1de108414d64b71da3e85c9d98f0 -msgid "2021-05-14" -msgstr "" - -#: ../../changelog/1.4.rst:2410 95ef005bdd1b47b18a76e2962586788c -msgid "" -":vytask:`T3346` (bug): nat 4-to-5 migration script fails when a 'source' or " -"'destination' node exists but there are no rules" -msgstr "" - -#: ../../changelog/1.4.rst:2411 05d8e55df95d4dad9a2b4371185af136 -msgid "" -":vytask:`T3248` (default): Deal with VRRP mode-force command that exists in " -"1.2 but not in 1.3" -msgstr "" - -#: ../../changelog/1.4.rst:2412 88a3371468ec43b793b8fa0158f28358 -msgid "" -":vytask:`T3426` (default): add support for script arguments to vyos-configd" -msgstr "" - -#: ../../changelog/1.4.rst:2416 6d0eb0d47a5148c4ba6aa4d9ddf360e6 -msgid "2021-05-13" -msgstr "" - -#: ../../changelog/1.4.rst:2418 3d67a8a275ff4cb5aa4ae10634b322d3 -msgid ":vytask:`T3539` (bug): Typo in RPKI interface definition" -msgstr "" - -#: ../../changelog/1.4.rst:2419 c2a3542585bd41d0a00b8d0260ab1c4b -msgid ":vytask:`T439` (feature): local PBR support" -msgstr "" - -#: ../../changelog/1.4.rst:2420 1a7e19d098614c8e97e394d9f0dec882 -msgid "" -":vytask:`T3544` (feature): DHCP server should validate configuration before " -"applying it" -msgstr "" - -#: ../../changelog/1.4.rst:2421 16e24ee5bbe847fa8fbc887b25d9a480 -msgid "" -":vytask:`T3543` (feature): Support for setting lacp_rate on LACP bonded " -"interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:2425 d6e4a70805ec4935979ae0c69f68aff3 -msgid "2021-05-12" -msgstr "" - -#: ../../changelog/1.4.rst:2427 5042deb9293c4a0aac2e5d767201d745 -msgid "" -":vytask:`T3302` (default): Make vyos-configd relay stdout from scripts to " -"the user's console" -msgstr "" - -#: ../../changelog/1.4.rst:2428 1e19f48c965d46a5823ebcecf64170f8 -msgid "" -":vytask:`T3542` (bug): udev net.rules not installed in image since may 2nd" -msgstr "" - -#: ../../changelog/1.4.rst:2432 ccb0ddad4cd4458688dc4a4b564d31a4 -msgid "2021-05-10" -msgstr "" - -#: ../../changelog/1.4.rst:2434 528f8c6dd6d14c7191b5994ff45fef35 -msgid ":vytask:`T3374` (bug): IPv6 GRE Tunnel issues" -msgstr "" - -#: ../../changelog/1.4.rst:2438 4bdbb165baa24e0b84af50adad9607d4 -msgid "2021-05-09" -msgstr "" - -#: ../../changelog/1.4.rst:2440 c1d8fae7c3e243bfa7152dec7857db8b -msgid ":vytask:`T3530` (bug): BGP peer-group can't contain a hyphen" -msgstr "" - -#: ../../changelog/1.4.rst:2444 d8ac7b581114411592d268eac3231f53 -msgid "2021-05-06" -msgstr "" - -#: ../../changelog/1.4.rst:2446 d12cd5c6d9bc42e18ca032a6d27e39f6 -msgid ":vytask:`T3523` (bug): VRF BGP daemon route-map command missing" -msgstr "" - -#: ../../changelog/1.4.rst:2447 9609f23705654bc7aceb85f2a2f5952a -msgid ":vytask:`T3519` (bug): Cannot add / assign L2TPv3 to vrf" -msgstr "" - -#: ../../changelog/1.4.rst:2451 2a259611a9074a7d92bd2e9c643abd9f -msgid "2021-05-05" -msgstr "" - -#: ../../changelog/1.4.rst:2453 3c886e9bfe714023b52020c061644171 -msgid ":vytask:`T3520` (bug): Cannot add tunnel interface to isis within vrf" -msgstr "" - -#: ../../changelog/1.4.rst:2454 d370e9a25a1649688f691a044b7b712d -msgid ":vytask:`T3335` (bug): Some OSPFv3 show commands do not work" -msgstr "" - -#: ../../changelog/1.4.rst:2458 05cc3957d920441389a32d162f84250b -msgid "2021-05-04" -msgstr "" - -#: ../../changelog/1.4.rst:2460 d6c7e769a3524dbebae6493c2dfeacbe -msgid ":vytask:`T3504` (feature): BGP Per Peer Graceful Restart" -msgstr "" - -#: ../../changelog/1.4.rst:2464 550cb8ce67cd4d7f91b9d9fddd267533 -msgid "2021-05-02" -msgstr "" - -#: ../../changelog/1.4.rst:2466 42c0f49dabdb4250afa5cdba6c3f5a1f -msgid "" -":vytask:`T3511` (bug): Update libnss-mapuser and libpam-radius packages from" -" CUMULUS Linux" -msgstr "" - -#: ../../changelog/1.4.rst:2470 5f7ec7bb0e8341fb845c97f70c2d1a69 -msgid "2021-05-01" -msgstr "" - -#: ../../changelog/1.4.rst:2472 0b4622ce1ecf48fb93969e0b87fdec2c -msgid "" -":vytask:`T3379` (feature): Add global-parameters name-server for " -"dhcpv6-server" -msgstr "" - -#: ../../changelog/1.4.rst:2473 f9fac8485f134cc99cbc3d1e8efd2fc0 -msgid ":vytask:`T3491` (default): Change Kernel HZ to 1000" -msgstr "" - -#: ../../changelog/1.4.rst:2477 f98477eaa2414e438af2bb033974b982 -msgid "2021-04-29" -msgstr "" - -#: ../../changelog/1.4.rst:2479 484551ac71cd4d04aa46c82e7437bfdd -msgid "" -":vytask:`T3503` (bug): \"route-reflector-client\" fails when \"remote-as\" " -"is \"internal\"" -msgstr "" - -#: ../../changelog/1.4.rst:2480 4cd911fd83da4c29868b35c8091af833 -msgid ":vytask:`T3502` (bug): \"system ip multipath layer4-hashing\" doesn't work" -msgstr "" - -#: ../../changelog/1.4.rst:2484 6e0c257635654767af5b05e3e595c395 -msgid "2021-04-28" -msgstr "" - -#: ../../changelog/1.4.rst:2486 6778b060590a4f348b555826b49ca4e6 -msgid ":vytask:`T3473` (bug): IPSec op-mode show sa error" -msgstr "" - -#: ../../changelog/1.4.rst:2490 65030bc33da249f5b05bd424ea9f7f83 -msgid "2021-04-27" -msgstr "" - -#: ../../changelog/1.4.rst:2492 515e2ea582b74603a0c4e0cbbe9b0335 -msgid "" -":vytask:`T2946` (bug): Calling 'stty_size' causes show interfaces API to " -"fail" -msgstr "" - -#: ../../changelog/1.4.rst:2496 c218f87b5177492f9ecba0debe6d0763 -msgid "2021-04-25" -msgstr "" - -#: ../../changelog/1.4.rst:2498 1fad506cee634770b237d303487975f8 -msgid "" -":vytask:`T3490` (bug): priority inversion on PBR \"policy route\" create, " -"breaks default route from dhcp (live iso)" -msgstr "" - -#: ../../changelog/1.4.rst:2499 c316f313140d470dac52abaded5c2da4 -msgid "" -":vytask:`T3468` (bug): Tunnel interfaces aren't suggested as being available" -" for bridging (regression)" -msgstr "" - -#: ../../changelog/1.4.rst:2500 ebfe727f791a403eb59d27d135f8aa16 -msgid "" -":vytask:`T3497` (bug): Prefix list with rule containing only action is not " -"detected as error during parse" -msgstr "" - -#: ../../changelog/1.4.rst:2501 062d774b92d84494a0a0953da83aeb06 -msgid "" -":vytask:`T3492` (bug): BGP Configuration Migration failed (badly!) from " -"rolling 202102240218 to rolling 202104221210" -msgstr "" - -#: ../../changelog/1.4.rst:2502 f2fc3f37167c4f90b0507bdf87bf8a6c -msgid ":vytask:`T1802` (feature): Wireguard QR code in cli for mobile devices" -msgstr "" - -#: ../../changelog/1.4.rst:2506 8c7774b3c49c43c4badb9b1846d04c6d -msgid "2021-04-24" -msgstr "" - -#: ../../changelog/1.4.rst:2508 339040d77f104a648956bb8db2f49ca6 -msgid ":vytask:`T3472` (bug): commit-confirm script not found" -msgstr "" - -#: ../../changelog/1.4.rst:2509 ef67afa300884081b131f6129beefbe3 -msgid ":vytask:`T3439` (bug): Commit-archive location not working for scp" -msgstr "" - -#: ../../changelog/1.4.rst:2513 55acbf0d812e494a9f030b4e1b337052 -msgid "2021-04-23" -msgstr "" - -#: ../../changelog/1.4.rst:2515 e93ccb2f9b91431e9c8b976a6ae94383 -msgid ":vytask:`T3395` (bug): WAN load-balancing fails with nexthop dhcp" -msgstr "" - -#: ../../changelog/1.4.rst:2516 c3f76ac64f7a4e8b9f2a14f040e5ccd2 -msgid ":vytask:`T3290` (bug): Disabling GRE conntrack module fails" -msgstr "" - -#: ../../changelog/1.4.rst:2520 6371ce58d18e40cb9d9bbe3d68c29374 -msgid "2021-04-20" -msgstr "" - -#: ../../changelog/1.4.rst:2522 e4c20b56ea2e4566ac9804b378117638 -msgid "" -":vytask:`T3488` (bug): Specifying an invalid \"interface address\" like " -"dhcph leads to commit error" -msgstr "" - -#: ../../changelog/1.4.rst:2526 8099884c27a84c1ab7bf55e332257e52 -msgid "2021-04-18" -msgstr "" - -#: ../../changelog/1.4.rst:2528 bc713a1da272459995b2572986c65f4a -msgid ":vytask:`T3481` (default): Exclude tag node values from key mangling" -msgstr "" - -#: ../../changelog/1.4.rst:2529 7f3a058878ca4fdc9160e4632a48de7a -msgid "" -":vytask:`T3475` (bug): XML dictionary cache unable to process syntaxVersion " -"elements" -msgstr "" - -#: ../../changelog/1.4.rst:2533 7f4500eaa78a411786a6509185f745a2 -msgid "2021-04-17" -msgstr "" - -#: ../../changelog/1.4.rst:2535 2496d7b0a30e4dbaadb5785939117a80 -msgid ":vytask:`T3470` (bug): as-override isn't applied to frr" -msgstr "" - -#: ../../changelog/1.4.rst:2539 b120c1df4d074425967dd6ca93c9559b -msgid "2021-04-15" -msgstr "" - -#: ../../changelog/1.4.rst:2541 57d426beeeb0474c821ea85590f3a552 -msgid "" -":vytask:`T3386` (bug): PPPoE-server don't start with local authentication" -msgstr "" - -#: ../../changelog/1.4.rst:2542 6667dc58124b4b0fbe58eb011713e2c4 -msgid "" -":vytask:`T3190` (feature): Unable to subtract value from local-preference in" -" route-map" -msgstr "" - -#: ../../changelog/1.4.rst:2546 93906e471c424d07a987ed8fd516eca1 -msgid "2021-04-14" -msgstr "" - -#: ../../changelog/1.4.rst:2548 11c3a5af9b30437d994f62f53db46ad3 -msgid ":vytask:`T3398` (bug): Can't commit" -msgstr "" - -#: ../../changelog/1.4.rst:2549 e66b04c287744251bc8f4d56b9b66054 -msgid "" -":vytask:`T3055` (bug): op-mode incorrect naming for ipsec policy-based " -"tunnels" -msgstr "" - -#: ../../changelog/1.4.rst:2553 132cd098cdba4ba3bfabdab91259acd7 -msgid "2021-04-13" -msgstr "" - -#: ../../changelog/1.4.rst:2555 5d9470e82df5452fac83417632abcd77 -msgid ":vytask:`T3436` (feature): Refactoring ospf op-mode for support vrf" -msgstr "" - -#: ../../changelog/1.4.rst:2556 a3ecefce03f245d7bef6ad1c6e47c0ee -msgid ":vytask:`T3434` (feature): Refactoring bgp op-mode for support vrf" -msgstr "" - -#: ../../changelog/1.4.rst:2560 bf3d05427029459a9af0098c26f6bc3b -msgid "2021-04-12" -msgstr "" - -#: ../../changelog/1.4.rst:2562 e8455c29eeec4c2885a2f3902efe5b17 -msgid ":vytask:`T3454` (enhancment): dhclient reject option" -msgstr "" - -#: ../../changelog/1.4.rst:2563 e3f177ea24284e818e611e43d6d12dd0 -msgid ":vytask:`T3328` (bug): Bgp not possible to delete bgp route-map" -msgstr "" - -#: ../../changelog/1.4.rst:2567 c8faefd143cf467f9c9d9a99220030ed -msgid "2021-04-10" -msgstr "" - -#: ../../changelog/1.4.rst:2569 04b3690494cc4626a38ecaa5d8a8d7e2 -msgid "" -":vytask:`T3460` (bug): bgp, Configuration FRR failed while commiting code" -msgstr "" - -#: ../../changelog/1.4.rst:2573 62090744d2134fc7852a6110be2e1dbb -msgid "2021-04-09" -msgstr "" - -#: ../../changelog/1.4.rst:2575 5be8063d6ec54273935ffaaf128f1b81 -msgid "" -":vytask:`T3464` (bug): OSPF: route-map names containing a hypen are not " -"\"found\"" -msgstr "" - -#: ../../changelog/1.4.rst:2579 05b07e92ad7449cba156683b330cf49a -msgid "2021-04-08" -msgstr "" - -#: ../../changelog/1.4.rst:2581 a9ac25aef4634b7390156f06e8f91f52 -msgid ":vytask:`T3462` (default): show ipv6 bgp -- missing" -msgstr "" - -#: ../../changelog/1.4.rst:2582 140156db274843a98434a52736ecc3a4 -msgid ":vytask:`T3463` (bug): Prevent IPv4 Route exchange with IPv6 neighbors" -msgstr "" - -#: ../../changelog/1.4.rst:2586 2f2db128fa394105a5f0efbd55310a2b -msgid "2021-04-05" -msgstr "" - -#: ../../changelog/1.4.rst:2588 e24bd6658325420ba1d805c606e6b4dd -msgid "" -":vytask:`T3438` (bug): VRF: removing vif which belongs to a vrf, will delete" -" the entire vrf from the operating system" -msgstr "" - -#: ../../changelog/1.4.rst:2589 50d9423434ee4eaca45b5771144dbc69 -msgid "" -":vytask:`T3418` (bug): BGP: system wide known interface can not be used as " -"neighbor" -msgstr "" - -#: ../../changelog/1.4.rst:2593 5d309e188a5149d9b5519128d75f4b11 -msgid "2021-04-04" -msgstr "" - -#: ../../changelog/1.4.rst:2595 46abbd4f4018477baa1dcb38e2c35754 -msgid "" -":vytask:`T3457` (feature): Output the \"monitor log\" command in a colorful " -"way" -msgstr "" - -#: ../../changelog/1.4.rst:2599 4cfdeee5bbbb421189440378a20ea4a3 -msgid "2021-03-31" -msgstr "" - -#: ../../changelog/1.4.rst:2601 7bc845cf8a2e4a01b399ab133403e1d6 -msgid ":vytask:`T3445` (bug): vyos-1x build include not all nodes" -msgstr "" - -#: ../../changelog/1.4.rst:2605 fff230f39fa849d891a33815d95dd078 -msgid "2021-03-30" -msgstr "" - -#: ../../changelog/1.4.rst:2607 4afda71e225c4a119a3099d2bed5b9f9 -msgid "" -":vytask:`T3448` (bug): Loading vyos on a system without xdp installed fails" -msgstr "" - -#: ../../changelog/1.4.rst:2611 c277bb5dbfa64258867e82c4216c4fba -msgid "2021-03-29" -msgstr "" - -#: ../../changelog/1.4.rst:2613 2e1cff366135448982bca77110c96b90 -msgid "" -":vytask:`T3415` (feature): bridge: add support for isolated interfaces " -"(private-vlan)" -msgstr "" - -#: ../../changelog/1.4.rst:2614 486821a4d60a4e84adb812b52eb85640 -msgid "" -":vytask:`T1711` (feature): BGP - migrate from tagNode to node (remove ASN " -"from tagNode)" -msgstr "" - -#: ../../changelog/1.4.rst:2618 d91f84b3c0594f22b40d4dd749747c67 -msgid "2021-03-28" -msgstr "" - -#: ../../changelog/1.4.rst:2620 d9cbd37e92fa4e84ac332972b9baa38c -msgid "" -":vytask:`T3440` (bug): HTTP API: give uvicorn time to initialize before " -"restarting Nginx proxy" -msgstr "" - -#: ../../changelog/1.4.rst:2624 fc6a8c79545a4584925c578f0fbb06b7 -msgid "2021-03-27" -msgstr "" - -#: ../../changelog/1.4.rst:2626 f9f1e976ed3a4de38d1a9674047a5fc9 -msgid "" -":vytask:`T3423` (bug): Cannot create ipv4 static route for default gateway " -"in vrf" -msgstr "" - -#: ../../changelog/1.4.rst:2630 6aae4cd89a3e480fa19748310d39831a -msgid "2021-03-26" -msgstr "" - -#: ../../changelog/1.4.rst:2632 4f7b593dc32443b1947dadfc0c8e89e9 -msgid ":vytask:`T3412` (default): HTTP API: move to FastAPI as web framework" -msgstr "" - -#: ../../changelog/1.4.rst:2633 0fb9b336615249d19b5fc7462c064d12 -msgid ":vytask:`T2397` (feature): HTTP API: export OpenAPI definition" -msgstr "" - -#: ../../changelog/1.4.rst:2637 2886395eeb5346239666a9a57533bf35 -msgid "2021-03-24" -msgstr "" - -#: ../../changelog/1.4.rst:2639 957b6c5b5adb459d975c6fa39cb5f524 -msgid ":vytask:`T3419` (bug): show interfaces | strip-private fails" -msgstr "" - -#: ../../changelog/1.4.rst:2643 92153f69183047338595a0583cb7d1a1 -msgid "2021-03-22" -msgstr "" - -#: ../../changelog/1.4.rst:2645 50ea9ffe4bc245a7820224568db9b205 -msgid "" -":vytask:`T3284` (bug): merge/load fail silently if unable to resolve host" -msgstr "" - -#: ../../changelog/1.4.rst:2649 1d6e12c576254905b44d570d4000a0a3 -msgid "2021-03-21" -msgstr "" - -#: ../../changelog/1.4.rst:2651 932d368633ea4032b0170647b5a200ac -msgid ":vytask:`T3417` (default): ISIS: provide per VRF instance support" -msgstr "" - -#: ../../changelog/1.4.rst:2652 36860f7ed00841d9af074cbed11facd0 -msgid "" -":vytask:`T3416` (bug): NTP: when running inside a VRF op-mode commands do " -"not work" -msgstr "" - -#: ../../changelog/1.4.rst:2656 f6eb075d95bc40be8ad73c85d7dade16 -msgid "2021-03-20" -msgstr "" - -#: ../../changelog/1.4.rst:2658 876e4e22165440cabfb682d28b022e4f -msgid "" -":vytask:`T3392` (bug): vrrp over dhcp default route bug (unexpected vrf)" -msgstr "" - -#: ../../changelog/1.4.rst:2659 67dd18d488ef428eb000aebdedccf2e1 -msgid ":vytask:`T3373` (feature): Upgrade to SaltStack version 3002.5" -msgstr "" - -#: ../../changelog/1.4.rst:2660 11b3720aa56b46dbb42452b2904ffd21 -msgid "" -":vytask:`T3329` (default): \"system conntrack ignore\" rules can no longer " -"be created due to an iptables syntax change" -msgstr "" - -#: ../../changelog/1.4.rst:2661 5da1e1a65c8b4e25bc19b40ad495feca -msgid ":vytask:`T3300` (feature): Add DHCP default route distance" -msgstr "" - -#: ../../changelog/1.4.rst:2662 d6fda3405c4049a381a27f855f0396dd -msgid "" -":vytask:`T3306` (feature): Extend set route-map aggregator as to 4 Bytes" -msgstr "" - -#: ../../changelog/1.4.rst:2666 66f39089cb4a4ecbaad160ecdde7d24b -msgid "2021-03-18" -msgstr "" - -#: ../../changelog/1.4.rst:2668 bb9ac4f8298d40b790c036123c2ea883 -msgid "" -":vytask:`T3411` (default): Extend the redirect_stdout context manager in " -"vyos-configd to redirect stdout from subprocesses" -msgstr "" - -#: ../../changelog/1.4.rst:2669 6d6d72a202df4775b3eb87caa96eed2b -msgid ":vytask:`T3271` (bug): qemu-kvm grub issue" -msgstr "" - -#: ../../changelog/1.4.rst:2673 83504f262c8e42c9bac121425ea2afdc -msgid "2021-03-17" -msgstr "" - -#: ../../changelog/1.4.rst:2675 9051d711941f4d35bfb4406ff3a23919 -msgid "" -":vytask:`T3413` (bug): Configuring invalid IPv6 EUI64 address results in " -"\"OSError: illegal IP address string passed to inet_pton\"" -msgstr "" - -#: ../../changelog/1.4.rst:2679 82cceecb102848658d54b020cd8fb17a -msgid "2021-03-14" -msgstr "" - -#: ../../changelog/1.4.rst:2681 2d95774c5da1444f9e27473a86a63f45 -msgid ":vytask:`T3345` (default): BGP: add per VRF instance support" -msgstr "" - -#: ../../changelog/1.4.rst:2682 2665806c79ef4d07b068601a71c5679a -msgid ":vytask:`T3344` (default): Per VRF dynamic routing support" -msgstr "" - -#: ../../changelog/1.4.rst:2683 1164bac0284549d3a843aaafacad0932 -msgid ":vytask:`T3325` (bug): Bgp listen-range wrong commit message" -msgstr "" - -#: ../../changelog/1.4.rst:2684 e1d8911b4fd343e8be4b7087bdd07183 -msgid "" -":vytask:`T1513` (default): Move OSPF and RIP interface configuration under " -"protocols" -msgstr "" - -#: ../../changelog/1.4.rst:2688 f19501424e0646459af6d4d806771e04 -msgid "2021-03-13" -msgstr "" - -#: ../../changelog/1.4.rst:2690 cc96a16586a34127b6ee60171983d50a -msgid "" -":vytask:`T3406` (bug): tunnel: interface no longer supports specifying " -"encaplimit none - or migrator is missing" -msgstr "" - -#: ../../changelog/1.4.rst:2691 a26bb2301cab4cbaafe02dac1a389deb -msgid "" -":vytask:`T3407` (bug): console-server: do not allow to spawn a console-" -"server session on serial port used by \"system console\"" -msgstr "" - -#: ../../changelog/1.4.rst:2695 4d006b052f474105afe2821188f9acaa -msgid "2021-03-11" -msgstr "" - -#: ../../changelog/1.4.rst:2697 6a56c8a24bd54af88a76d69feba8768e -msgid "" -":vytask:`T3305` (bug): Ingress qdisc does not work anymore in " -"1.3-rolling-202101 snapshot" -msgstr "" - -#: ../../changelog/1.4.rst:2698 6a27092896f649e5977ff3768c5ac82b -msgid "" -":vytask:`T2927` (bug): isc-dhcpd release and expiry events never execute" -msgstr "" - -#: ../../changelog/1.4.rst:2702 5e9ec949b4cf4c23a07c783464980155 -msgid "2021-03-09" -msgstr "" - -#: ../../changelog/1.4.rst:2704 fc419ee06d854046b1dfad311b7c3191 -msgid ":vytask:`T3382` (bug): Error creating Console Server" -msgstr "" - -#: ../../changelog/1.4.rst:2708 d3594b6cd304406689f218b35a418ec0 -msgid "2021-03-08" -msgstr "" - -#: ../../changelog/1.4.rst:2710 ffb372a39d234b1f9c0eb2584338d8e8 -msgid ":vytask:`T3387` (bug): Command \"Monitor vpn ipsec\" is not working" -msgstr "" - -#: ../../changelog/1.4.rst:2714 dc4468492ebc443f806b4d902922527f -msgid "2021-03-07" -msgstr "" - -#: ../../changelog/1.4.rst:2716 ede553cd00784a1d909a55b77d79e65a -msgid ":vytask:`T3388` (bug): show interfaces doesn't display pppoeX" -msgstr "" - -#: ../../changelog/1.4.rst:2717 566fa4301ace4a60b7d974a05203c57e -msgid "" -":vytask:`T3211` (feature): ability to redistribute ISIS into other routing " -"protocols" -msgstr "" - -#: ../../changelog/1.4.rst:2721 4301d374a89b4d65aed6d6df61b04c20 -msgid "2021-03-04" -msgstr "" - -#: ../../changelog/1.4.rst:2723 a01ac3c183964ed2bcd428290c6efd48 -msgid ":vytask:`T3377` (bug): show interfaces throws error" -msgstr "" - -#: ../../changelog/1.4.rst:2727 6816bfe45d954cf7b280bd59a2942bb2 -msgid "2021-03-02" -msgstr "" - -#: ../../changelog/1.4.rst:2729 aa1b6fd92cdf48828735adb9ca017305 -msgid ":vytask:`T3375` (bug): Interface becomes up at boot even when disabled" -msgstr "" - -#: ../../changelog/1.4.rst:2733 9c648b67b25a4b87a61e0d81469ff050 -msgid "2021-02-28" -msgstr "" - -#: ../../changelog/1.4.rst:2735 4e7f1925ddc946d7885faa6ba9129c82 -msgid ":vytask:`T3370` (bug): dhcp: Invalid domain name \"private\"" -msgstr "" - -#: ../../changelog/1.4.rst:2736 c43c6aabc032417bb1f102a1b05e99ad -msgid ":vytask:`T3369` (feature): VXLAN: add IPv6 underlay support" -msgstr "" - -#: ../../changelog/1.4.rst:2737 cd0b5bf492d046a8b62f0cb6655b8f0e -msgid ":vytask:`T3363` (bug): VyOS-Build interactive prompt when using Podman" -msgstr "" - -#: ../../changelog/1.4.rst:2738 e4d632c49d114441a58e679252e9e48c -msgid ":vytask:`T3320` (bug): Bgp neighbor peer-group without peer-group fail" -msgstr "" - -#: ../../changelog/1.4.rst:2742 7c79b16fd7f24b91bda8743c846965fe -msgid "2021-02-27" -msgstr "" - -#: ../../changelog/1.4.rst:2744 164db35f55054ed1a041b46b652ac676 -msgid ":vytask:`T3365` (bug): Bgp neighbor interface ordering for remote-as" -msgstr "" - -#: ../../changelog/1.4.rst:2745 fae44be7bc844ccbbdd09ce131ed343f -msgid "" -":vytask:`T3225` (bug): Adding a BGP neighbor with an address on a local " -"interface throws a vyos.frr.CommitError: Configuration FRR failed while " -"committing code: ''" -msgstr "" - -#: ../../changelog/1.4.rst:2746 94fb61e597a64d75ace0cde20a66540e -msgid ":vytask:`T3368` (feature): macsec: add support for gcm-aes-256 cipher" -msgstr "" - -#: ../../changelog/1.4.rst:2747 2a1dee9b1c4e47158f91990c2bf5cafc -msgid "" -":vytask:`T3173` (feature): Need 'nopmtudisc' option for tunnel interface" -msgstr "" - -#: ../../changelog/1.4.rst:2751 cfbf629f57314d42a750e0f4be65773c -msgid "2021-02-26" -msgstr "" - -#: ../../changelog/1.4.rst:2753 3d19664ecd5a49f6b020af67ba52a666 -msgid ":vytask:`T3324` (bug): Bgp space in the password" -msgstr "" - -#: ../../changelog/1.4.rst:2754 903325720409489e83933151b72ff199 -msgid "" -":vytask:`T3357` (default): HTTP-API redirect from http correct https port" -msgstr "" - -#: ../../changelog/1.4.rst:2755 f7fe2c1b0b704fb296fcf43c1c2a2c64 -msgid ":vytask:`T3323` (bug): Bgp ttl-security and ebgp-multihop fail" -msgstr "" - -#: ../../changelog/1.4.rst:2759 ff8f8aee9aaf43ddac72e3d6f602d995 -msgid "2021-02-24" -msgstr "" - -#: ../../changelog/1.4.rst:2761 e18b307b329348349d91deb8438b64c2 -msgid ":vytask:`T3303` (feature): Change welcome message on boot" -msgstr "" - -#: ../../changelog/1.4.rst:2765 82926cf5e18842fb856cf9372c957381 -msgid "2021-02-22" -msgstr "" - -#: ../../changelog/1.4.rst:2767 7ec2980320114bbfb2251d36fe67834c -msgid ":vytask:`T3322` (bug): Bgp neighbor timers not applyed to FRR config" -msgstr "" - -#: ../../changelog/1.4.rst:2768 9ab5634df0714cfebbf868ddc613b413 -msgid ":vytask:`T3327` (bug): OSPFv3: Cannot add dummy interface" -msgstr "" - -#: ../../changelog/1.4.rst:2772 ea5a5cb1c69b46ba84bd79772c39db46 -msgid "2021-02-21" -msgstr "" - -#: ../../changelog/1.4.rst:2774 437ba428237e4e17a151c8efa0b01ff3 -msgid ":vytask:`T3331` (bug): Bgp unsuppress-map should be as \"value leafNode\"" -msgstr "" - -#: ../../changelog/1.4.rst:2775 4b10beef2665403f9e93c9e3876699d4 -msgid ":vytask:`T3330` (bug): Bgp capability orf prefix-list fail" -msgstr "" - -#: ../../changelog/1.4.rst:2776 f69bcd9046ad479ca2a147cff66a2985 -msgid "" -":vytask:`T3163` (feature): ethernet ring-buffer can be set with an invalid " -"value" -msgstr "" - -#: ../../changelog/1.4.rst:2780 563b10ade23544a895609b38a5b040b9 -msgid "2021-02-19" -msgstr "" - -#: ../../changelog/1.4.rst:2782 cab2916c64b54e4790daad7dfbcf70ab -msgid ":vytask:`T3326` (bug): OSPFv3: Cannot add L2TPv3 interface" -msgstr "" - -#: ../../changelog/1.4.rst:2783 e9292a62c6114825a45b3c3023e4fa84 -msgid "" -":vytask:`T3332` (bug): BGP unnumbered - UnboundLocalError: local variable " -"'peer_group' referenced before assignment" -msgstr "" - -#: ../../changelog/1.4.rst:2787 db256c8e24d74ba49da13cd2a4e7be9f -msgid "2021-02-18" -msgstr "" - -#: ../../changelog/1.4.rst:2789 45a381cb65fb43f49e8918cfcfed385f -msgid "" -":vytask:`T3259` (default): many dnat rules makes the vyos http api crash, " -"even showConfig op timeouts" -msgstr "" - -#: ../../changelog/1.4.rst:2793 95fab50444d640d9bf7d5d303343fddf -msgid "2021-02-17" -msgstr "" - -#: ../../changelog/1.4.rst:2795 2dc6845d2ed242f68fd3ca305367eb89 -msgid ":vytask:`T3312` (feature): SolarFlare NICs support" -msgstr "" - -#: ../../changelog/1.4.rst:2799 216345e4f3ca4f7ea7f9f2994551bcdb -msgid "2021-02-16" -msgstr "" - -#: ../../changelog/1.4.rst:2801 13320faeec6844fcb551e2ad8fe17795 -msgid ":vytask:`T3313` (bug): ospfv3 interface missing options" -msgstr "" - -#: ../../changelog/1.4.rst:2802 37404567c0b84089905944dd7dfab8b8 -msgid ":vytask:`T3318` (feature): Update Linux Kernel to v5.4.208 / 5.10.142" -msgstr "" - -#: ../../changelog/1.4.rst:2806 85eda340364943798644ec1d338aee62 -msgid "2021-02-15" -msgstr "" - -#: ../../changelog/1.4.rst:2808 a669aa8eb63f48f58959863d88f43caf -msgid "" -":vytask:`T3311` (bug): BGP Error: Remote AS must be set for neighbor or " -"peer-group" -msgstr "" - -#: ../../changelog/1.4.rst:2812 d94bfaf833a84dac8d9e938d2cfe2e4e -msgid "2021-02-14" -msgstr "" - -#: ../../changelog/1.4.rst:2814 ddb14f60279448bbaa37caac96d2b4f7 -msgid ":vytask:`T2848` (feature): bgp-add-path configuration options" -msgstr "" - -#: ../../changelog/1.4.rst:2815 956a1e1e36f242229c438bf8532a0201 -msgid "" -":vytask:`T1875` (feature): Add the ability to use network address as BGP " -"neighbor (bgp listen range)" -msgstr "" - -#: ../../changelog/1.4.rst:2819 5c2138fbcc574d86b77bbe3bcf0509d4 -msgid "2021-02-12" -msgstr "" - -#: ../../changelog/1.4.rst:2821 8280cdf59f55407e8f0dfaf6fecc6f4e -msgid "" -":vytask:`T3301` (bug): Wrong format and valueHelp for policy as-path-list " -"regex" -msgstr "" - -#: ../../changelog/1.4.rst:2825 ef5dd7a868464106a33e6bf2305c261d -msgid "2021-02-11" -msgstr "" - -#: ../../changelog/1.4.rst:2827 69e6dedb258347b084a33b48d6be7d2c -msgid "" -":vytask:`T3281` (default): Rewrite protocol RIPng [conf-mode] to new " -"XML/Python style" -msgstr "" - -#: ../../changelog/1.4.rst:2828 0b5d14608c2a4705b5d54838945ab022 -msgid ":vytask:`T3282` (default): Add XML for [conf-mode] RIPng" -msgstr "" - -#: ../../changelog/1.4.rst:2829 13fe1b98911a4dbdaddbb674289385e5 -msgid "" -":vytask:`T3279` (default): Rewrite protocol STATIC [op-mode] to new " -"XML/Python style" -msgstr "" - -#: ../../changelog/1.4.rst:2830 654f4c5e2ba649a19411528dd8ee488a -msgid ":vytask:`T3297` (bug): Optimize irrelevant error stack hints" -msgstr "" - -#: ../../changelog/1.4.rst:2834 16ae38c5e1f9453382379ea615681fb9 -msgid "2021-02-08" -msgstr "" - -#: ../../changelog/1.4.rst:2836 c8019d62b22e4e8e95edd1694909d582 -msgid ":vytask:`T3295` (feature): Update Linux Kernel to v5.4.96 / 5.10.14" -msgstr "" - -#: ../../changelog/1.4.rst:2840 45a347da02504f5bb3408f8619c28d53 -msgid "2021-02-05" -msgstr "" - -#: ../../changelog/1.4.rst:2842 c3668f97c1944fe59a912d55f35989d0 -msgid ":vytask:`T3030` (feature): Support ERSPAN Tunnel Protocol" -msgstr "" - -#: ../../changelog/1.4.rst:2846 0fba9ffae7cc48f89306be276bba8059 -msgid "2021-02-04" -msgstr "" - -#: ../../changelog/1.4.rst:2848 6fad1509f024485d9f215ca874b034c2 -msgid ":vytask:`T3283` (feature): Support for IPv4 neigh tables" -msgstr "" - -#: ../../changelog/1.4.rst:2849 32114fafe608423eb9a694546749dfd9 -msgid ":vytask:`T3280` (default): Add XML for [conf-mode] STATIC" -msgstr "" - -#: ../../changelog/1.4.rst:2853 f75e96ff32a349869c8054c90828d1cd -msgid "2021-02-03" -msgstr "" - -#: ../../changelog/1.4.rst:2855 1a33ec0dceb94612a3a61929cb8eea7a -msgid ":vytask:`T3278` (feature): Add XML for \"protocols vrf\" [conf-mode]" -msgstr "" - -#: ../../changelog/1.4.rst:2856 e16a07ce01b64459b322c1bce672d370 -msgid "" -":vytask:`T3239` (default): XML: override 'defaultValue' for mtu of certain " -"interfaces; remove workarounds" -msgstr "" - -#: ../../changelog/1.4.rst:2857 c20278505ff94bc38c109c19f2fc25b1 -msgid "" -":vytask:`T2910` (feature): XML: generator should support override of " -"variables" -msgstr "" - -#: ../../changelog/1.4.rst:2861 ed17f234bd4a47878c9a852130217470 -msgid "2021-02-02" -msgstr "" - -#: ../../changelog/1.4.rst:2863 b55adb41f7fd4d3c8ab6c734690599f5 -msgid "" -":vytask:`T3018` (bug): Unclear behaviour when configuring vif and vif-s " -"interfaces" -msgstr "" - -#: ../../changelog/1.4.rst:2864 528ac6d211c5487c873c4e7533dbf5c6 -msgid "" -":vytask:`T3255` (default): Rewrite protocol RPKI to new XML/Python style" -msgstr "" - -#: ../../changelog/1.4.rst:2865 7c61fa9b12e5419cadb045005bb5f304 -msgid ":vytask:`T3263` (feature): OSPF Hello subsecond timer" -msgstr "" - -#: ../../changelog/1.4.rst:2869 653ea6aea34b4cf9b4fad6b6e9426529 -msgid "2021-01-31" -msgstr "" - -#: ../../changelog/1.4.rst:2871 90b7ddc6858943dfb9b0693ab5605293 -msgid ":vytask:`T3276` (feature): Update Linux Kernel to v5.4.94 / 5.10.12" -msgstr "" - -#: ../../changelog/1.4.rst:2875 d09624a739a94d73ae30b4c00ad1ab62 -msgid "2021-01-30" -msgstr "" - -#: ../../changelog/1.4.rst:2877 c1a43b901dba4069b8300dc5a4e8de66 -msgid ":vytask:`T3240` (feature): Support per-interface DHCPv6 DUIDs" -msgstr "" - -#: ../../changelog/1.4.rst:2878 591e8439f8db4d6fa4a96b594063b57a -msgid "" -":vytask:`T3273` (default): PPPoE static default-routes deleted on interface " -"down when not added by interface up" -msgstr "" - -#: ../../changelog/1.4.rst:2882 583b707f6a67433a8e33bf6191f78924 -msgid "2021-01-29" -msgstr "" - -#: ../../changelog/1.4.rst:2884 d0c976bffa1c4851947b0de611d50253 -msgid "" -":vytask:`T3261` (bug): Does not possible to disable pppoe client interface." -msgstr "" - -#: ../../changelog/1.4.rst:2885 76f03d3fe3ea42578ed869a501cf6344 -msgid ":vytask:`T3272` (default): OSPF: interface config is not removed" -msgstr "" - -#: ../../changelog/1.4.rst:2889 91f54b14166e444ebd08e0b28fedae91 -msgid "2021-01-27" -msgstr "" - -#: ../../changelog/1.4.rst:2891 ca9c7e719de44c97aad12591f30dd2b2 -msgid ":vytask:`T3257` (feature): tcpdump supporting complete protocol" -msgstr "" - -#: ../../changelog/1.4.rst:2892 35ed6a336a5f4e24a72eef7b96a85a79 -msgid "" -":vytask:`T3244` (default): Rewrite protocol OSPFv3 to new XML/Python style" -msgstr "" - -#: ../../changelog/1.4.rst:2896 c69956d60acd4011ac5fd793494135ce -msgid "2021-01-26" -msgstr "" - -#: ../../changelog/1.4.rst:2898 41f34a9c0d084384a0f3a6e2cefc35e9 -msgid "" -":vytask:`T3251` (bug): PPPoE client trying to authorize with the wrong " -"username" -msgstr "" - -#: ../../changelog/1.4.rst:2899 7a72d87f97e44bbd95917f7742907fb1 -msgid ":vytask:`T3256` (default): Add XML for protocol RPKI [conf-mode]" -msgstr "" - -#: ../../changelog/1.4.rst:2903 419e079d601340b2aebdafab1a6e6a3b -msgid "2021-01-25" -msgstr "" - -#: ../../changelog/1.4.rst:2905 ca3e6784f6f549109e60c2bebb0a7723 -msgid "" -":vytask:`T3249` (feature): Support operation mode forwarding table output" -msgstr "" - -#: ../../changelog/1.4.rst:2909 d6a23309b42e4fb5a5fb846656a7453d -msgid "2021-01-24" -msgstr "" - -#: ../../changelog/1.4.rst:2911 bb467821d8b240319f339efb80a50d63 -msgid ":vytask:`T3227` (bug): Latest releases don't work with RPKI (crash)" -msgstr "" - -#: ../../changelog/1.4.rst:2912 c3b40eb8590e48e4be614471244d21b7 -msgid ":vytask:`T3230` (bug): RPKI can't be deleted" -msgstr "" - -#: ../../changelog/1.4.rst:2913 1172d0abb40a4a95a12ff1a5f2509c5c -msgid ":vytask:`T3221` (bug): FRR config" -msgstr "" - -#: ../../changelog/1.4.rst:2914 85cb16af288848a783c2fcfd8ffb2fda -msgid ":vytask:`T3245` (default): Add XML for protocol ospfv3 [conf-mode]" -msgstr "" - -#: ../../changelog/1.4.rst:2918 2a0513db54e543f2930d024572bd24e7 -msgid "2021-01-23" -msgstr "" - -#: ../../changelog/1.4.rst:2920 5f0d20d864c4454c8c5969af2a644fa2 -msgid ":vytask:`T3236` (default): Add XML for [conf-mode] OSPF" -msgstr "" - -#: ../../changelog/1.4.rst:2924 3763b1759a7b41bda5e8aa82a215d0b8 -msgid "2021-01-17" -msgstr "" - -#: ../../changelog/1.4.rst:2926 3511d67354dd416fb06ddc2be589fbd2 -msgid ":vytask:`T3222` (bug): Typo in BGP dampening description" -msgstr "" - -#: ../../changelog/1.4.rst:2927 0d8ecf938ded460ebb344c667fb5b436 -msgid ":vytask:`T3226` (bug): Repair bridge smoke test damage" -msgstr "" - -#: ../../changelog/1.4.rst:2931 de09b65b506c40b3a05e3c9898980628 -msgid "2021-01-16" -msgstr "" - -#: ../../changelog/1.4.rst:2933 a58ce80757504e30ac982ac05a66207c -msgid ":vytask:`T3215` (bug): Operational command \"show ipv6 route\" is broken" -msgstr "" - -#: ../../changelog/1.4.rst:2934 68e7caab16fc4fe4b9f6f71287fe1549 -msgid "" -":vytask:`T3157` (bug): salt-minion fails to start due to permission error " -"accessing /root/.salt/minion.log" -msgstr "" - -#: ../../changelog/1.4.rst:2935 e8b15e040185458db4e54920e2813005 -msgid "" -":vytask:`T3137` (feature): Let VLAN aware bridge approach the behavior of " -"professional equipment" -msgstr "" - -#: ../../changelog/1.4.rst:2939 108faad343244e57ac91ff202da724d7 -msgid "2021-01-15" -msgstr "" - -#: ../../changelog/1.4.rst:2941 89f855f9e28e4b59ab493f05ae79bf9a -msgid ":vytask:`T3210` (feature): ISIS three-way-handshake" -msgstr "" - -#: ../../changelog/1.4.rst:2942 34953e3acd23471fad36b39eb945ad77 -msgid ":vytask:`T3184` (feature): Add correct desctiptions for BGP neighbors" -msgstr "" - -#: ../../changelog/1.4.rst:2946 40cbefbf5630447a91e372214a132b32 -msgid "2021-01-14" -msgstr "" - -#: ../../changelog/1.4.rst:2948 6a17d6ed96d7435c805cbae394d66a0a -msgid ":vytask:`T3213` (bug): show interface command python error" -msgstr "" - -#: ../../changelog/1.4.rst:2952 c7a10604415047179bf229758a6b3af3 -msgid "2021-01-12" -msgstr "" - -#: ../../changelog/1.4.rst:2954 7f14e34ad2b645a296c7ca32c1b5a3ad -msgid "" -":vytask:`T3205` (bug): Does not possible to configure tunnel mode gre-bridge" -msgstr "" - -#: ../../changelog/1.4.rst:2958 cab1b13b074445eeaf9c60200d588052 -msgid "2020-12-20" -msgstr "" - -#: ../../changelog/1.4.rst:2960 b43da8f2295942fd9d70b7003d4add13 -msgid ":vytask:`T3132` (feature): Enable egress flow accounting" -msgstr "" - -#: ../../changelog/1.4.rst:2964 7270bccd95f247b399c764b2f0d161a8 -msgid "2020-11-29" -msgstr "" - -#: ../../changelog/1.4.rst:2966 e194516abcbf41d4a92c898ebdb1b7d6 -msgid ":vytask:`T2297` (feature): NTP add support for pool configuration" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/changelog/index.po b/docs/_locale/de_DE/LC_MESSAGES/changelog/index.po deleted file mode 100644 index 98e3cd35..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/changelog/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../changelog/index.rst:6 529936d0c3b6409db1590c78cdb9ab74 -msgid "Changelog" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/cli.po b/docs/_locale/de_DE/LC_MESSAGES/cli.po deleted file mode 100644 index 0d1a2107..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/cli.po +++ /dev/null @@ -1,638 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:54+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../cli.rst:5 21120cf0a35e462896221ba7d3955dbe -msgid "Command Line Interface" -msgstr "" - -#: ../../cli.rst:7 c4c8616f9aa64506ba32a918e751ba09 -msgid "" -"The VyOS :abbr:`CLI (Command-Line Interface)` comprises an operational and a" -" configuration mode." -msgstr "" - -#: ../../cli.rst:11 636d7ebd8bda4c32a2f48642143d3a7a -msgid "Operational Mode" -msgstr "" - -#: ../../cli.rst:13 057dab6dbd964a17bce2e139dc2c72e2 -msgid "" -"Operational mode allows for commands to perform operational system tasks and" -" view system and service status, while configuration mode allows for the " -"modification of system configuration." -msgstr "" - -#: ../../cli.rst:17 974e4e76b1454a4e8ca19c0f850b2a84 -msgid "" -"The CLI provides a built-in help system. In the CLI the ``?`` key may be " -"used to display available commands. The ``TAB`` key can be used to auto-" -"complete commands and will present the help system upon a conflict or " -"unknown value." -msgstr "" - -#: ../../cli.rst:21 d1bbdf92bf8348de9e475c14fe95c9dd -msgid "" -"For example typing ``sh`` followed by the ``TAB`` key will complete to " -"``show``. Pressing ``TAB`` a second time will display the possible sub-" -"commands of the ``show`` command." -msgstr "" - -#: ../../cli.rst:30 2bc6da04f33d4eb8be20b26bd6726241 -msgid "Example showing possible show commands:" -msgstr "" - -#: ../../cli.rst:58 4ca86db4c84640a29821d88b0735f98a -msgid "" -"You can scroll up with the keys ``[Shift]+[PageUp]`` and scroll down with " -"``[Shift]+[PageDown]``." -msgstr "" - -#: ../../cli.rst:61 5973ef10ccfb4177baf6e3b7334a657e -msgid "" -"When the output of a command results in more lines than can be displayed on " -"the terminal screen the output is paginated as indicated by a ``:`` prompt." -msgstr "" - -#: ../../cli.rst:72 d728194e036c4716a3e5df62b26a6f0d -msgid "When viewing in page mode the following commands are available:" -msgstr "" - -#: ../../cli.rst:65 f156509bc7f441369c63114c298f5567 -msgid "``q`` key can be used to cancel output" -msgstr "" - -#: ../../cli.rst:66 d1da597d959e479faf7ae04e966bb225 -msgid "``space`` will scroll down one page" -msgstr "" - -#: ../../cli.rst:67 e1b5265ce5ee42d7bec396e8f923aaa9 -msgid "``b`` will scroll back one page" -msgstr "" - -#: ../../cli.rst:68 40182dbf44634a399c48c2cd47d56462 -msgid "``return`` will scroll down one line" -msgstr "" - -#: ../../cli.rst:69 64033505e1fc4e56bcb38f0a59d8bd65 -msgid "" -"``up-arrow`` and ``down-arrow`` will scroll up or down one line at a time " -"respectively" -msgstr "" - -#: ../../cli.rst:71 313c1a098e59429bab5c553f35b29f59 -msgid "" -"``left-arrow`` and ``right-arrow`` can be used to scroll left or right in " -"the event that the output has lines which exceed the terminal size." -msgstr "" - -#: ../../cli.rst:75 d66ecd7309114d0c860911540edfc345 -msgid "Configuration Mode" -msgstr "" - -#: ../../cli.rst:77 76e2cb38ca4b4644bbb92ea0bbc81ad1 -msgid "To enter configuration mode use the ``configure`` command:" -msgstr "" - -#: ../../cli.rst:85 e03339907b6346f895084097041d4c51 -msgid "" -"Prompt changes from ``$`` to ``#``. To exit configuration mode, type " -"``exit``." -msgstr "" - -#: ../../cli.rst:94 ad7485be1ea34472bf1e5e77f0989a1c -msgid "" -"See the configuration section of this document for more information on " -"configuration mode." -msgstr "" - -#: ../../cli.rst:102 7dfc482dbadc4882a2e417a29ab5cbf7 -msgid "Configuration Overview" -msgstr "" - -#: ../../cli.rst:104 4bd2c0e5d42f4b0f86b7985adb949dc8 -msgid "" -"VyOS makes use of a unified configuration file for the entire system's " -"configuration: ``/config/config.boot``. This allows easy template creation, " -"backup, and replication of system configuration. A system can thus also be " -"easily cloned by simply copying the required configuration files." -msgstr "" - -#: ../../cli.rst:111 187a65db793741b58ce69646d651efb6 -msgid "Terminology" -msgstr "" - -#: ../../cli.rst:113 1512f1014e654ba39a66f114f90cd01b -msgid "A live VyOS system has three major types of configurations:" -msgstr "" - -#: ../../cli.rst:115 b8195128e71541ef922ea1d13eb5291d -msgid "" -"**Active** or **running configuration** is the system configuration that is " -"loaded and currently active (used by VyOS). Any change in the configuration" -" will have to be committed to belong to the active/running configuration." -msgstr "" - -#: ../../cli.rst:120 f868599712844158b1d899b814a51c48 -msgid "" -"**Working configuration** is the one that is currently being modified in " -"configuration mode. Changes made to the working configuration do not go into" -" effect until the changes are committed with the :cfgcmd:`commit` command. " -"At which time the working configuration will become the active or running " -"configuration." -msgstr "" - -#: ../../cli.rst:126 e5573c12df9943adae64cd8bba01d9b4 -msgid "" -"**Saved configuration** is the one saved to a file using the :cfgcmd:`save` " -"command. It allows you to keep safe a configuration for future uses. There " -"can be multiple configuration files. The default or \"boot\" configuration " -"is saved and loaded from the file ``/config/config.boot``." -msgstr "" - -#: ../../cli.rst:133 414f4b2d94054beda99ee34d4c6cddf8 -msgid "Seeing and navigating the configuration" -msgstr "" - -#: ../../cli.rst:137 f2187452b1574497be64b5979ae7096e -msgid "" -"View the current active configuration, also known as the running " -"configuration, from the operational mode." -msgstr "" - -#: ../../cli.rst:193 1ac505b1896f4525a8a35db2da65c3f8 -msgid "" -"By default, the configuration is displayed in a hierarchy like the above " -"example, this is only one of the possible ways to display the configuration." -" When the configuration is generated and the device is configured, changes " -"are added through a collection of :cfgcmd:`set` and :cfgcmd:`delete` " -"commands." -msgstr "" - -#: ../../cli.rst:201 f305d616417e436eb6d9c3d134502654 -msgid "" -"Get a collection of all the set commands required which led to the running " -"configuration." -msgstr "" - -#: ../../cli.rst:221 d63b2f797bf045f48fc49417c906c3a9 -msgid "" -"Both these ``show`` commands should be executed when in operational mode, " -"they do not work directly in configuration mode. There is a special way on " -"how to :ref:`run_opmode_from_config_mode`." -msgstr "" - -#: ../../cli.rst:225 f2d3dc3b3cf5403c83a82d444c1a069c -msgid "" -"Use the ``show configuration commands | strip-private`` command when you " -"want to hide private data. You may want to do so if you want to share your " -"configuration on the `forum`_." -msgstr "" - -#: ../../cli.rst:233 03f09d2c45bb4f86adc9eede7fffdaf9 -msgid "View the current active configuration in JSON format." -msgstr "" - -#: ../../cli.rst:241 2d3d5eacec064a2392c692c31e9a79d1 -msgid "View the current active configuration in readable JSON format." -msgstr "" - -#: ../../cli.rst:338 177ac8bf938e4b8f8801b35cacae5e30 -msgid "The config mode" -msgstr "" - -#: ../../cli.rst:340 cfe4a5e07e254f808e1a35ab07b7b9e9 -msgid "" -"When entering the configuration mode you are navigating inside a tree " -"structure, to enter configuration mode enter the command :opcmd:`configure` " -"when in operational mode." -msgstr "" - -#: ../../cli.rst:351 30efd4da83d5459db163be96f3d962f5 -msgid "" -"When going into configuration mode, prompt changes from ``$`` to ``#``." -msgstr "" - -#: ../../cli.rst:355 5566a21e9dbe4083bf97b8cae1e30904 -msgid "" -"All commands executed here are relative to the configuration level you have " -"entered. You can do everything from the top level, but commands will be " -"quite lengthy when manually typing them." -msgstr "" - -#: ../../cli.rst:359 7ff733c108854732841a6ede3f81a49d -msgid "" -"The current hierarchy level can be changed by the :cfgcmd:`edit` command." -msgstr "" - -#: ../../cli.rst:370 3e1937e3dd54420bbdd56f60079a09ef -msgid "" -"You are now in a sublevel relative to ``interfaces ethernet eth0``, all " -"commands executed from this point on are relative to this sublevel. Use " -"eithe the :cfgcmd:`top` or :cfgcmd:`exit` command to go back to the top of " -"the hierarchy. You can also use the :cfgcmd:`up` command to move only one " -"level up at a time." -msgstr "" - -#: ../../cli.rst:378 8f7965edb6714d02a6b695b2db020ee9 -msgid "" -"The :cfgcmd:`show` command within configuration mode will show the working " -"configuration indicating line changes with ``+`` for additions, ``>`` for " -"replacements and ``-`` for deletions." -msgstr "" - -#: ../../cli.rst:382 96f7016a82594c3a91d2972ea7c1a806 -msgid "**Example:**" -msgstr "" - -#: ../../cli.rst:413 14395d359ccd4f09835d9c9a7ceb89b3 -msgid "" -"It is also possible to display all `set` commands within configuration mode " -"using :cfgcmd:`show | commands`" -msgstr "" - -#: ../../cli.rst:422 4379bd3c11e1471e984e477f3776de26 -msgid "" -"These commands are also relative to the level you are inside and only " -"relevant configuration blocks will be displayed when entering a sub-level." -msgstr "" - -#: ../../cli.rst:433 f280fe6780114f6bb14fbfc79974a6a6 -msgid "" -"Exiting from the configuration mode is done via the :cfgcmd:`exit` command " -"from the top level, executing :cfgcmd:`exit` from within a sub-level takes " -"you back to the top level." -msgstr "" - -#: ../../cli.rst:447 264cd6422a324d2aa97de4518ae5e725 -msgid "Editing the configuration" -msgstr "" - -#: ../../cli.rst:449 114c539fc9bd4b95a193332bb9875f86 -msgid "" -"The configuration can be edited by the use of :cfgcmd:`set` and " -":cfgcmd:`delete` commands from within configuration mode." -msgstr "" - -#: ../../cli.rst:454 b628dfa48fca49c0a0e09812e0efc07e -msgid "" -"Use this command to set the value of a parameter or to create a new element." -msgstr "" - -#: ../../cli.rst:457 8f3ee422c03c423ab83ea00d2cbcef8a -msgid "" -"Configuration commands are flattened from the tree into 'one-liner' commands" -" shown in :opcmd:`show configuration commands` from operation mode. Commands" -" are relative to the level where they are executed and all redundant " -"information from the current level is removed from the command entered." -msgstr "" - -#: ../../cli.rst:475 48ed6b56b27b48b691ba9d45dd4414f6 -msgid "" -"These two commands above are essentially the same, just executed from " -"different levels in the hierarchy." -msgstr "" - -#: ../../cli.rst:480 299391b2c4624c48a25d5bd67d613dbb -msgid "" -"To delete a configuration entry use the :cfgcmd:`delete` command, this also " -"deletes all sub-levels under the current level you've specified in the " -":cfgcmd:`delete` command. Deleting an entry will also result in the element " -"reverting back to its default value if one exists." -msgstr "" - -#: ../../cli.rst:493 f63691ef1fc44ce29633e2b7b3fef591 -msgid "" -"Any change you do on the configuration, will not take effect until committed" -" using the :cfgcmd:`commit` command in configuration mode." -msgstr "" - -#: ../../cli.rst:508 7ca29c616aca49a9b661173a26e82f20 -msgid "" -"Use this command to preserve configuration changes upon reboot. By default " -"it is stored at */config/config.boot*. In the case you want to store the " -"configuration file somewhere else, you can add a local path, a SCP address, " -"a FTP address or a TFTP address." -msgstr "" - -#: ../../cli.rst:535 bc85992170124de0b767b8248cd55508 -msgid "" -"Configuration mode can not be exited while uncommitted changes exist. To " -"exit configuration mode without applying changes, the :cfgcmd:`exit discard`" -" command must be used." -msgstr "" - -#: ../../cli.rst:539 848cecddb2ec4673bfeb45247cd46f7b -msgid "All changes in the working config will thus be lost." -msgstr "" - -#: ../../cli.rst:552 ef753ddae18c488a9b84cf835728ac5d -msgid "" -"Use this command to temporarily commit your changes and set the number of " -"minutes available for validation. ``confirm`` must be entered within those " -"minutes, otherwise the system will reboot into the previous configuration. " -"The default value is 10 minutes." -msgstr "" - -#: ../../cli.rst:558 119b474b2099422aa174b2c6bc91c7f7 -msgid "" -"What if you are doing something dangerous? Suppose you want to setup a " -"firewall, and you are not sure there are no mistakes that will lock you out " -"of your system. You can use confirmed commit. If you issue the ``commit-" -"confirm`` command, your changes will be commited, and if you don't issue " -"the ``confirm`` command in 10 minutes, your system will reboot into previous" -" config revision." -msgstr "" - -#: ../../cli.rst:576 d67fd3690dd748e2a517f447aebf3d99 -msgid "" -"A reboot because you did not enter ``confirm`` will not take you necessarily" -" to the *saved configuration*, but to the point before the unfortunate " -"commit." -msgstr "" - -#: ../../cli.rst:583 6591ff7781ce4c219aac0152b516f86f -msgid "Copy a configuration element." -msgstr "" - -#: ../../cli.rst:585 3005c44d1bba423898370647ead0582f -msgid "" -"You can copy and remove configuration subtrees. Suppose you set up a " -"firewall ruleset ``FromWorld`` with one rule that allows traffic from " -"specific subnet. Now you want to setup a similar rule, but for different " -"subnet. Change your edit level to ``firewall name FromWorld`` and use ``copy" -" rule 10 to rule 20``, then modify rule 20." -msgstr "" - -#: ../../cli.rst:616 d4bc2b2f4cb247f2a542d660c4d15b06 -msgid "Rename a configuration element." -msgstr "" - -#: ../../cli.rst:618 b4568f35db6745d19ea4ffc2b9812507 -msgid "You can also rename config subtrees:" -msgstr "" - -#: ../../cli.rst:627 929db380162e483db7f0e824e917f84a -msgid "" -"Note that ``show`` command respects your edit level and from this level you " -"can view the modified firewall ruleset with just ``show`` with no " -"parameters." -msgstr "" - -#: ../../cli.rst:651 fee0c71cd0f54c3e9db781d686ca07d9 -msgid "Add comment as an annotation to a configuration node." -msgstr "" - -#: ../../cli.rst:653 87025547a81e4a7c86ddccbee2e1d7f2 -msgid "" -"The ``comment`` command allows you to insert a comment above the ``<config " -"node>`` configuration section. When shown, comments are enclosed with ``/*``" -" and ``*/`` as open/close delimiters. Comments need to be commited, just " -"like other config changes." -msgstr "" - -#: ../../cli.rst:658 e408cab2d1c44990985e546091a55da8 -msgid "" -"To remove an existing comment from your current configuration, specify an " -"empty string enclosed in double quote marks (``\"\"``) as the comment text." -msgstr "" - -#: ../../cli.rst:662 f4f32c52be714bd1ba68aab1ef4e93c0 -msgid "Example:" -msgstr "" - -#: ../../cli.rst:676 dd7cbd1d1e6a4e0b9139c4d8f76a1c9a -msgid "" -"An important thing to note is that since the comment is added on top of the " -"section, it will not appear if the ``show <section>`` command is used. With " -"the above example, the `show firewall` command would return starting after " -"the ``firewall {`` line, hiding the comment." -msgstr "" - -#: ../../cli.rst:690 a70b770a4a1648c29883265dfaa1d0ce -msgid "Access opmode from config mode" -msgstr "" - -#: ../../cli.rst:692 f3c6588821924287ba297b1d64fe8274 -msgid "" -"When inside configuration mode you are not directly able to execute " -"operational commands." -msgstr "" - -#: ../../cli.rst:697 68ff26c8c2564460a9fd8ebd24e166e7 -msgid "" -"Access to these commands are possible through the use of the ``run " -"[command]`` command. From this command you will have access to everything " -"accessible from operational mode." -msgstr "" - -#: ../../cli.rst:701 7d68211d96144d49b588c53b2f626905 -msgid "" -"Command completion and syntax help with ``?`` and ``[tab]`` will also work." -msgstr "" - -#: ../../cli.rst:714 e747f3137f9c464c8c33893aba78ea9a -msgid "Managing configurations" -msgstr "" - -#: ../../cli.rst:716 2819f3d0832b475eb4165e5ef25c3260 -msgid "" -"VyOS comes with an integrated versioning system for the system " -"configuration. It automatically maintains a backup of every previous " -"configuration which has been committed to the system. The configurations are" -" versioned locally for rollback but they can also be stored on a remote host" -" for archiving/backup reasons." -msgstr "" - -#: ../../cli.rst:723 2236c75f85514bb38f672cd59756bc1b -msgid "Local Archive" -msgstr "" - -#: ../../cli.rst:725 891345c94d15435ba7630ec7a30cac79 -msgid "" -"Revisions are stored on disk. You can view, compare and rollback them to any" -" previous revisions if something goes wrong." -msgstr "" - -#: ../../cli.rst:730 0dc22fad77084db89ce2f40e4005861f -msgid "View all existing revisions on the local system." -msgstr "" - -#: ../../cli.rst:747 503fef0c5d8f4225abc6e58896c4b348 -msgid "" -"You can specify the number of revisions stored on disk. N can be in the " -"range of 0 - 65535. When the number of revisions exceeds the configured " -"value, the oldest revision is removed. The default setting for this value is" -" to store 100 revisions locally." -msgstr "" - -#: ../../cli.rst:754 198087cd084f4fbdad0394f5501dbaec -msgid "Compare configurations" -msgstr "" - -#: ../../cli.rst:756 351345bd9aeb421d9ee0a147299255b7 -msgid "VyOS lets you compare different configurations." -msgstr "" - -#: ../../cli.rst:760 0a1afe6b5de948a6accb87224583e888 -msgid "" -"Use this command to spot what the differences are between different " -"configurations." -msgstr "" - -#: ../../cli.rst:784 7921c3a125324f148f82df7eb01980b9 -msgid "" -"The command :cfgcmd:`compare` allows you to compare different type of " -"configurations. It also lets you compare different revisions through the " -":cfgcmd:`compare N M` command, where N and M are revision numbers. The " -"output will describe how the configuration N is when compared to M " -"indicating with a plus sign (``+``) the additional parts N has when compared" -" to M, and indicating with a minus sign (``-``) the lacking parts N misses " -"when compared to M." -msgstr "" - -#: ../../cli.rst:810 bfe635c8c3e94e09a98d7ddc32ce788f -msgid "Show commit revision difference." -msgstr "" - -#: ../../cli.rst:813 4f906beed751459d8bc34a3445e1e74b -msgid "" -"The command above also lets you see the difference between two commits. By " -"default the difference with the running config is shown." -msgstr "" - -#: ../../cli.rst:824 db6c957f421a444496f8784b79699171 -msgid "" -"This means four commits ago we did ``set system ipv6 disable-forwarding``." -msgstr "" - -#: ../../cli.rst:828 9c2de0768c6e4f16854f38b5f889a83f -msgid "Rollback Changes" -msgstr "" - -#: ../../cli.rst:830 e67c1d21f51e49a18387fd9d8cd0f8a6 -msgid "" -"You can rollback configuration changes using the rollback command. This will" -" apply the selected revision and trigger a system reboot." -msgstr "" - -#: ../../cli.rst:835 759a6ee824774d68b313f9a431d58e08 -msgid "Rollback to revision N (currently requires reboot)" -msgstr "" - -#: ../../cli.rst:850 285d97e1809e4a8daa89be4dd398a4c9 -msgid "Remote Archive" -msgstr "" - -#: ../../cli.rst:852 970b578f48a74395bff8817fd16af559 -msgid "" -"VyOS can upload the configuration to a remote location after each call to " -":cfgcmd:`commit`. You will have to set the commit-archive location. TFTP, " -"FTP, SCP and SFTP servers are supported. Every time a :cfgcmd:`commit` is " -"successfull the ``config.boot`` file will be copied to the defined " -"destination(s). The filename used on the remote host will be ``config.boot-" -"hostname.YYYYMMDD_HHMMSS``." -msgstr "" - -#: ../../cli.rst:861 20a82b39f3594b408c46d14465c3f059 -msgid "" -"Specify remote location of commit archive as any of the below :abbr:`URI " -"(Uniform Resource Identifier)`" -msgstr "" - -#: ../../cli.rst:864 62cfe72cc99a445bb4fdde3d267d526e -msgid "``scp://<user>:<passwd>@<host>:/<dir>``" -msgstr "" - -#: ../../cli.rst:865 0ced9798781d45e7b88341ad48889798 -msgid "``sftp://<user>:<passwd>@<host>/<dir>``" -msgstr "" - -#: ../../cli.rst:866 15c574cb9b51484eb2a5bb2c8d549560 -msgid "``ftp://<user>:<passwd>@<host>/<dir>``" -msgstr "" - -#: ../../cli.rst:867 fcb0ee5aba23487a981a1b78d5dea8a0 -msgid "``tftp://<host>/<dir>``" -msgstr "" - -#: ../../cli.rst:869 3d3ee415428c40999ddcbf8e003c8080 -msgid "The number of revisions don't affect the commit-archive." -msgstr "" - -#: ../../cli.rst:871 b6d77c3086db492687bb9376b10093d5 -msgid "" -"You may find VyOS not allowing the secure connection because it cannot " -"verify the legitimacy of the remote server. You can use the workaround below" -" to quickly add the remote host's SSH fingerprint to your " -"``~/.ssh/known_hosts`` file:" -msgstr "" - -#: ../../cli.rst:881 d517ea3bf3a541c68d04542637086726 -msgid "Saving and loading manually" -msgstr "" - -#: ../../cli.rst:883 20be23aacb3b490aa9e2ff0908360d2a -msgid "" -"You can use the ``save`` and ``load`` commands if you want to manually " -"manage specific configuration files." -msgstr "" - -#: ../../cli.rst:886 51b922b90d7f41b8890f4720cf931423 -msgid "" -"When using the save_ command, you can add a specific location where to store" -" your configuration file. And, when needed it, you will be able to load it " -"with the ``load`` command:" -msgstr "" - -#: ../../cli.rst:892 234408e9886440fe8e8b9ab63f96736d -msgid "" -"Use this command to load a configuration which will replace the running " -"configuration. Define the location of the configuration file to be loaded. " -"You can use a path to a local file, an SCP address, an SFTP address, an FTP " -"address, an HTTP address, an HTTPS address or a TFTP address." -msgstr "" - -#: ../../cli.rst:914 b416e5fa71104e75978dcefda0ac7fe6 -msgid "Restore Default" -msgstr "" - -#: ../../cli.rst:916 cb77dda7a9464a1d88ead879c5b011ed -msgid "" -"In the case you want to completely delete your configuration and restore the" -" default one, you can enter the following command in configuration mode:" -msgstr "" - -#: ../../cli.rst:924 2d6d4d7065c24114957b9d91223f7996 -msgid "" -"You will be asked if you want to continue. If you accept, you will have to " -"use :cfgcmd:`commit` if you want to make the changes active." -msgstr "" - -#: ../../cli.rst:927 9f9c7cb332794ad780df77618ded6502 -msgid "" -"Then you may want to :cfgcmd:`save` in order to delete the saved " -"configuration too." -msgstr "" - -#: ../../cli.rst:930 4a703606ba2d421f9f3a49ad90bbf71d -msgid "" -"If you are remotely connected, you will lose your connection. You may want " -"to copy first the config, edit it to ensure connectivity, and load the " -"edited config." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po deleted file mode 100644 index 78dd752d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po +++ /dev/null @@ -1,108 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:3 -#: b6d67f49feb24b3fa122917d1713c0ba -msgid "DHCP Relay trough GRE-Bridge" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:6 -#: 1d016bc7120144c1a698121e631b88ce -msgid "Testdate: 2022-10-09" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:7 -#: 6e048b6b5d1e4ed6b4f25e94edecf47b -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:10 -#: 127597ad8c8f4e5eb5d2b85948c155dd -msgid "" -"This simple structure shows how to configure a DHCP Relay over a GRE Bridge " -"interface." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:15 -#: 836e04717d9b453d93aa06d489e25a0d -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:17 -#: 153ef16cb87c40c29370123457b2278c -msgid "" -"The topology has 3 VyOS routers and one client. Between the DHCP Server and " -"the DHCP Relay is a GRE tunnel. The `transport` VyOS represent a large " -"Network." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rstNone -#: e3f84da3f42e4d51862669dd2cb899b2 -msgid "Ansible Example topology image" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:26 -#: 78c31c77e3374b9287e0f46c5547ff07 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:28 -#: 85735f69fefc4e47a6eeb0a79631ea61 -msgid "First, we configure the transport network and the Tunnel interface." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:31 -#: 635c882d632a43dc83f0f02362c57f56 -msgid "Transport:" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:37 -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:55 -#: e87f4b14b9ae4bfda9bbf5436e2580ee cd57953b80374d54ae35108ce6357ed2 -msgid "DHCP-Server" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:44 -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:62 -#: 379e70552a164cfe986786970522535d 77e16e1cf47f416d9877c94023f07a85 -msgid "DHCP-Relay" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:51 -#: d6c3ef6fe4d84842af6b47146a6bf09d -msgid "" -"After this, we need the DHCP-Server and Relay configuration. To get a " -"testable result, we just have one IP in the DHCP range. Expand it as you " -"need it." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:71 -#: cf696a295396415b829948546d904674 -msgid "Test the result" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:73 -#: 1c9009bcb8ef4063a0dbc89927cb394e -msgid "Ping the Client from the DHCP Server." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:90 -#: 7deadd4f386f48b48429ebd1d788fbf9 -msgid "And show all DHCP Leases" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po deleted file mode 100644 index 9584018f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po +++ /dev/null @@ -1,248 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:4 -#: dca7066243a64ac9bb911c232c07a55c -msgid "L3VPN EVPN with VyOS" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:6 -#: 40009f7cec44488b973f2aa05da6cf76 -msgid "Testdate: 2022-10-10" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:7 -#: 259b38aa4a6447c4bd22d3d881ef6445 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:9 -#: a18b811d628d480a83d2d5a41fa905db -msgid "" -"I spun up a new lab in EVE-NG, which represents this as the \"Foo Bar - " -"Service Provider Inc.\" that has 3 points of presence (PoP) in random " -"datacenters/sites named PE1, PE2, and PE3. Each PoP aggregates at least two " -"customers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:14 -#: c847a6183ba6486095e722083c3f7a6d -msgid "" -"I named the customers blue, red and green which is common practice in VRF " -"(Virtual Routing and Forwarding) documentation scenarios." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:17 -#: 59b7c95414774841abc20f1e2f4202d2 -msgid "" -"PE1 is located in an industrial area that holds multiple office buildings. " -"All customers have a site in this area." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:19 -#: 6fffa1cde14c4de0a3264303ddab2209 -msgid "" -"PE2 is located in a smaller area where by coincidence two customers (blue " -"and red) share an office building." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:21 -#: 84cea04906cc4f6cafbb0a5b05df5eb8 -msgid "" -"PE3 is located in a smaller area where by coincidence two customers (blue " -"and green) are located." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:26 -#: 2984bd561ad44a85b369de655fc4c04f -msgid "Management VRF" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:28 -#: e0c8580baf144bec8f6652c6226fa5d5 -msgid "" -"A brief excursion into VRFs: This has been one of the longest-standing " -"feature requests of VyOS (dating back to 2016) which can be described as \"a" -" VLAN for layer 2 is what a VRF is for layer 3\". With VRFs, a router/system" -" can hold multiple, isolated routing tables on the same system. If you " -"wonder what's the difference between multiple tables that people used for " -"policy-based routing since forever, it's that a VRF also isolates connected " -"routes rather than just static and dynamically learned routes, so it allows " -"NICs in different VRFs to use conflicting network ranges without issues." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:38 -#: 1a678edb2c814554987d969567cb843d -msgid "" -"VyOS 1.3 added initial support for VRFs (including IPv4/IPv6 static routing)" -" and VyOS 1.4 now enables full dynamic routing protocol support for OSPF, " -"IS-IS, and BGP for individual VRFs." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:42 -#: 8308ef8d3eef4bf583ba6ae20941f9e5 -msgid "" -"The lab I built is using a VRF (called **mgmt**) to provide out-of-band SSH " -"access to the PE (Provider Edge) routers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:52 -#: eba9ea05ad7841849983d2705c9410d6 -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:54 -#: e2986d31e7ee4bffa5b2e115a952b7ae -msgid "We use the following network topology in this example:" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rstNone -#: cec7142cd4c146bf944e487d1c071124 -msgid "L3VPN EVPN with VyOS topology image" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:62 -#: dc04d5ec28614dd58ed11e537c255941 -msgid "Core network" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:64 -#: 79db8a2ac0774a52805405daab666a6e -msgid "" -"I chose to run OSPF as the IGP (Interior Gateway Protocol). All required BGP" -" sessions are established via a dummy interfaces (similar to the loopback, " -"but in Linux you can have only one loopback, while there can be many dummy " -"interfaces) on the PE routers. In case of a link failure, traffic is " -"diverted in the other direction in this triangle setup and BGP sessions will" -" not go down. One could even enable BFD (Bidirectional Forwarding Detection)" -" on the links for a faster failover and resilience in the network." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:73 -#: c03653c3a768410a8ba4e3f35a9df6f8 -msgid "" -"Regular VyOS users will notice that the BGP syntax has changed in VyOS 1.4 " -"from even the prior post about this subject. This is due to T1711, where it " -"was finally decided to get rid of the redundant BGP ASN (Autonomous System " -"Number) specification on the CLI and move it to a single leaf node (set " -"protocols bgp local-as)." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:79 -#: b54e76d59f2a4879ad57e4d751f44534 -msgid "" -"It's important to note that all your existing configurations will be " -"migrated automatically on image upgrade. Nothing to do on your side." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:82 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:123 -#: 778bcf8867dd4742b90af58c3c2974f9 03e0d184dd814620b0ebf2066fe5cd54 -msgid "PE1" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:88 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:129 -#: feca16238d384858bde862fcffc4f668 e764ab9f7c1c464fb6b8ad766e9a97da -msgid "PE2" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:94 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:135 -#: 418db537cb7e4646b396025335c225fb 34e53a71b2a6421992ee83f3d458883a -msgid "PE3" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:103 -#: 5a2fa388fab34210972487efc12cc05f -msgid "Tenant networks (VRFs)" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:105 -#: 54d85baae8274726b442dabf00d643bc -msgid "" -"Once all routers can be safely remotely managed and the core network is " -"operational, we can now setup the tenant networks." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:108 -#: d1d790f73bb545edbcb20f8ded69e5f7 -msgid "" -"Every tenant is assigned an individual VRF that would support overlapping " -"address ranges for customers blue, red and green. In our example, we do not " -"use overlapping ranges to make it easier when showing debug commands." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:112 -#: 6e4c009e66714b06982495a718d7bed4 -msgid "Thus you can easily match it to one of the devices/networks below." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:114 -#: 8eda9841785d48eaa53e33b241c5dfb6 -msgid "" -"Every router that provides access to a customer network needs to have the " -"customer network (VRF + VNI) configured. To make our own lives easier, we " -"utilize the same VRF table id (local routing table number) and VNI (Virtual " -"Network Identifier) per tenant on all our routers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:119 -#: 5acd5a7623b2476d9e2e2c66ccb740b4 -msgid "blue uses local routing table id and VNI 2000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:120 -#: c79bdaa44fb94e9284a8043361262dde -msgid "red uses local routing table id and VNI 3000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:121 -#: 2afb2d9e933344099bf7b103aa2f4187 -msgid "green uses local routing table id and VNI 4000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:143 -#: 6cefa7e52add4fe1a75562495292efe0 -msgid "Testing and debugging" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:145 -#: 4be9bdc170984b6ab7e3ee7e60617ff4 -msgid "" -"You managed to come this far, now we want to see the network and routing " -"tables in action." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:148 -#: c5321083829e4286b93d550d75d5060f -msgid "Show routes for all VRFs" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:189 -#: 4b9a7dc8ae3849178c5061f8c9e40b00 -msgid "Information about Ethernet Virtual Private Networks" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:236 -#: 0464a050fc0e428bbf2d160f31fa2225 -msgid "" -"If we need to retrieve information about a specific host/network inside the " -"EVPN network we need to run" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po deleted file mode 100644 index 5f469405..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po +++ /dev/null @@ -1,120 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:3 -#: 1112b498492f4f97b47ca5315651543c -msgid "Wireguard" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:6 -#: cad83059fc954e2f9797528e77ae3265 -msgid "Testdate: 2022-10-09" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:7 -#: b8317168f5c34dacac426bbf160099c2 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:10 -#: ff88b0392e1342eda89e21f06001f593 -msgid "" -"This simple structure show how to connect two offices. One remote branch and" -" the central office." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:15 -#: fa805f515da84e8eae724617bc7f6a2b -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:17 -#: 7954fa9a77a346759a5b29c935061602 -msgid "" -"The topology have a central and a branch VyOS router and one client, to " -"test, in each site." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rstNone -#: 2fb68483c1724b5ab8b9fd6d3929e5f3 -msgid "Ansible Example topology image" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:25 -#: 13f50b70eced428b8cf14ab4dbf1569d -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:27 -#: 762f0d7725dd4ddcb4c8f6abd1cd7185 -msgid "" -"Set the local subnet on eth2 and the public ip address eth1 on each site." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:29 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:55 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:71 -#: 5b82506aea5a4d4383ed66f8751497e5 c06020215f594cdf94351ebe8149581e -#: 56ed8089bd3a4ece8b90b56a21269698 -msgid "Central" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:35 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:61 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:77 -#: 958fa8e6ae9742c4a8c9f7000989d8f0 08cfff8b32b744379d8d6526dfd47ec1 -#: 4ba49eec7bc4436d8d4841fb437ee866 -msgid "Branch" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:42 -#: 37eddc3053d14cbf9fcf84a5e2e47bff -msgid "" -"Next thing to do, is to create a wireguard keypair on each side. After this," -" the public key can be displayed, to save for later." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:52 -#: 898c59cc02ef490a88ddd78faaeeb42e -msgid "After you have each public key. The wireguard interfaces can be setup." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:68 -#: 403a421f999b4d2b99e5a45f8fcc58bb -msgid "" -"To reach the network, a route must be set on each VyOS host. In this " -"structure, a static interface route will fit the requirements." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:85 -#: 75c272fbdcdb40028fb502ba388339e7 -msgid "Testing and debugging" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:87 -#: fcbab0e2725d4fd3b59226ef41192888 -msgid "" -"After all is done and commit, let's take a look if the Wireguard interface " -"is up and running." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:99 -#: 1f323a79c53143b7b93f62946f16329c -msgid "And ping the Branch PC from your central router to check the response." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po deleted file mode 100644 index 14accc87..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po +++ /dev/null @@ -1,282 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:5 -#: e858d6875b1c46cbaece3f265eebe9cb -msgid "Tunnelbroker.net (IPv6)" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:7 -#: 43c9e137b1d64397b43509cefc6afbde -msgid "Testdate: 2022-10-10" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:8 -#: 1f2dc4f37d04432da5f6c54a33f566d7 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:10 -#: 0e33bf12fa6a4b59bff76e91b4f74173 -msgid "" -"This guide walks through the setup of https://www.tunnelbroker.net/ for an " -"IPv6 Tunnel." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:14 -#: 4510e8e67ecf46b48da0836bd31fdfd7 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:16 -#: e4f40532bb684bddae9a98badaa6f494 -msgid "" -"A public, routable IPv4 address. This does not necessarily need to be " -"static, but you will need to update the tunnel endpoint when/if your IP " -"address changes, which can be done with a script and a scheduled task." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:19 -#: bf9411243d594a209d8e5233a911faca -msgid "Account at https://www.tunnelbroker.net/" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:20 -#: 3384e179dd6b47fbb4bbcc549b558601 -msgid "" -"Requested a \"Regular Tunnel\". You want to choose a location that is " -"closest to your physical location for the best response time." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:26 -#: 4beeca87d8534dbaaa908be33faa6199 -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:28 -#: 1fae284fcce641af8a51074758c69698 -msgid "" -"The example topology has 2 VyOS routers. One as The WAN Router and on as a " -"Client, to test a single LAN setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rstNone -#: bb725568726e4e059b23a99e4c66a6cd -msgid "Tunnelbroker topology image" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:37 -#: 30329a3d8a1c4912965057dbcf802832 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:39 -#: bae83b5f1ac1460ea11b8864f65ffd79 -msgid "First, we configure the ``vyos-wan`` interface to get a DHCP address." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:45 -#: 51ab034c5a6a42ce821332f22f016579 -msgid "Now we are able to setup the tunnel interface." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:51 -#: a07ed24d74054c0d9c83a9f732ddd57e -msgid "Setup the ipv6 default route to the tunnel interface" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:57 -#: 2a5666024df949d2b4235f6df9bbeb54 -msgid "Now you should be able to ping a public IPv6 Address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:74 -#: b35fbadb6df74e5b83c5e1416d1afede -msgid "" -"Assuming the pings are successful, you need to add some DNS servers. Some " -"options:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:81 -#: aeed9b7f61534e3f95b805dde17b42dd -msgid "You should now be able to ping something by IPv6 DNS name:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:100 -#: a736ca5cd747403e8c14e673245d821e -msgid "LAN Configuration" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:102 -#: 1112b0d0ef1d4918a7ebca59efac58e4 -msgid "" -"At this point, your VyOS install should have full IPv6, but now your LAN " -"devices need access." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:105 -#: 1a65570c0367426c9a4f873d63f4942e -msgid "With Tunnelbroker.net, you have two options:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:107 -#: 3c6a7c5ec4ea449fa91711d03dac4c3b -msgid "" -"Routed /64. This is the default assignment. In IPv6-land, it's good for a " -"single \"LAN\", and is somewhat equivalent to a /24." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:110 -#: 29591255e2fd43a8b7fa1644284d59e1 -msgid "" -"Routed /48. This is something you can request by clicking the \"Assign /48\"" -" link in the Tunnelbroker.net tunnel config. It allows you to have up to 65k" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:113 -#: 67cd1fd9c371469c86c53c680bb79daf -msgid "" -"Unlike IPv4, IPv6 is really not designed to be broken up smaller than /64. " -"So if you ever want to have multiple LANs, VLANs, DMZ, etc, you'll want to " -"ignore the assigned /64, and request the /48 and use that." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:119 -#: 4f74d70dd2874430ae4b1614cd2d2739 -msgid "Single LAN Setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:121 -#: 2df56212558149feb9fd81bb336775fa -msgid "" -"Single LAN setup where eth2 is your LAN interface. Use the Tunnelbroker " -"Routed /64 prefix:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:128 -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:195 -#: 13574cf1c9174aa6b9237ea264787b9a 1c15190bf24244529f6ed886c2ef9c2e -msgid "" -"Please note, 'autonomous-flag' and 'on-link-flag' are enabled by default, " -"'valid-lifetime' and 'preferred-lifetime' are set to default values of 30 " -"days and 4 hours respectively." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:132 -#: 023eef0d8ac74055a7706a8605b9a7eb -msgid "" -"And the ``client`` to receive an IPv6 address with stateless autoconfig." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:137 -#: f83b8f3084da425dbc98cb5a735692d9 -msgid "This accomplishes a few things:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:139 -#: 10c4928833d54de2905620ff414d3954 -msgid "Sets your LAN interface's IP address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:140 -#: 49ca773f9de54f74b956dae477d7e0a8 -msgid "" -"Enables router advertisements. This is an IPv6 alternative for DHCP (though " -"DHCPv6 can still be used). With RAs, Your devices will automatically find " -"the information they need for routing and DNS." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:144 -#: b7b7e14f124c43be8e51f03ad82aaff1 -msgid "Now the Client is able to ping a public IPv6 address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:162 -#: d73b8a6e7c8a47b8a0b44b9542eb3945 -msgid "Multiple LAN/DMZ Setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:164 -#: 17df49416ec247fdb8f8862ec2ec8dc3 -msgid "" -"That's how you can expand the example above. Use the `Routed /48` " -"information. This allows you to assign a different /64 to every interface, " -"LAN, or even device. Or you could break your network into smaller chunks " -"like /56 or /60." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:169 -#: e4872a8b039f4965ba7db797feb6ce70 -msgid "The format of these addresses:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:171 -#: a680481984ce4e3cba3147ace39339f2 -msgid "" -"`2001:470:xxxx::/48`: The whole subnet. xxxx should come from Tunnelbroker." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:172 -#: 8811a6910f0d41029f75986a4051e439 -msgid "`2001:470:xxxx:1::/64`: A subnet suitable for a LAN" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:173 -#: 0be6cdcfbf9b494d972beb120cbff231 -msgid "`2001:470:xxxx:2::/64`: Another subnet" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:174 -#: 048263091af848179c2b55a901b94f6f -msgid "`2001:470:xxxx:ffff:/64`: The last usable /64 subnet." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:176 -#: 1544240be6e040c3b2316d2bb28a83b9 -msgid "" -"In the above examples, 1,2,ffff are all chosen by you. You can use 1-ffff " -"(1-65535)." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:179 -#: 9555909b8f964a02a14bf995b7370a81 -msgid "" -"So, when your LAN is eth1, your DMZ is eth2, your cameras are on eth3, etc:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:200 -#: 79d2a568ce054e6f82dcd8208b682cd4 -msgid "Firewall" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:202 -#: bdb36fc61be6473681e2d4013d05cc20 -msgid "" -"Finally, don't forget the :ref:`firewall`. The usage is identical, except " -"for instead of `set firewall name NAME`, you would use `set firewall " -"ipv6-name NAME`." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:206 -#: 45493d140daa4adb80535f448eebc499 -msgid "" -"Similarly, to attach the firewall, you would use `set interfaces ethernet " -"eth0 firewall in ipv6-name` or `set firewall zone LOCAL from WAN firewall " -"ipv6-name`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po deleted file mode 100644 index 78b45e28..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po +++ /dev/null @@ -1,179 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/azure-vpn-bgp.rst:6 f83fa44add8c41fab8110d1f2e321206 -msgid "Route-Based Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:8 534f72f752e84afb8b770ad8a53a1bd5 -msgid "" -"This guide shows an example of a route-based IKEv2 site-to-site VPN to Azure" -" using VTI and BGP for dynamic routing updates." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:11 049d04f68cd44accb87923158043df03 -msgid "" -"For redundant / active-active configurations see :ref:`examples-azure-vpn-" -"dual-bgp`" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:16 54fc3df452904c5ea43d99c856544676 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:18 abec6e0963af4d7fbe1c1162390d4a60 -msgid "" -"A pair of Azure VNet Gateways deployed in active-passive configuration with " -"BGP enabled." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:21 22aeb09e6d9344c4be9e08c70c779758 -msgid "" -"A local network gateway deployed in Azure representing the Vyos device, " -"matching the below Vyos settings except for address space, which only " -"requires the Vyos private IP, in this example 10.10.0.5/32" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:26 e6783a61f8d54c33a95e58407aea2c46 -msgid "" -"A connection resource deployed in Azure linking the Azure VNet gateway and " -"the local network gateway representing the Vyos device." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:31 f6198f4f4b574ab7b36ae8f6ee5dc732 -msgid "Example" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:34 cc5a2912e07c44bfb396b9262365fc92 -msgid "WAN Interface" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:34 df85aea4568748798a33025246e4f9ff -msgid "eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:36 20ce51d06a40433d84365d4573b1c4bd -msgid "On-premises address space" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:36 46b911f0e0634cd99a4106fb467df923 -msgid "10.10.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:38 e7d5f286aec147fcaee08602adc1d133 -msgid "Azure address space" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:38 69d765b32e0f4434ab5158857004439d -msgid "10.0.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:40 806362f58c034acbb2ccd5390bfa3a3f -msgid "Vyos public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:40 a09e867c84484ac0b7c657ce599b4d76 -msgid "198.51.100.3" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:42 6680466007f8459b8859bba84a6ef5f0 -msgid "Vyos private IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:42 05581a563fb248cfbce55b48fc9b516c -msgid "10.10.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:44 ab851443a7a74c0dbd76a3d9c2b741ae -msgid "Azure VNet Gateway public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:44 76422c1c147445248b6990ab012ca135 -msgid "203.0.113.2" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:46 aca3077ca2d946bbb13bfe1d5bc3b9fd -msgid "Azure VNet Gateway BGP IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:46 4d0cb52280314731a2b791c9ac669e5f -msgid "10.0.0.4" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:48 4170c65ca13340a49596468c75bfeb01 -msgid "Pre-shared key" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:48 240e9cc921f447b897bdbf946b707747 -msgid "ch00s3-4-s3cur3-psk" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:50 4eb2ac883ece41aa9e8d90fb835c8f29 -msgid "Vyos ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:50 f19b0284d6d747f1abea3cd22b340a78 -msgid "64499" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:52 7592137fa3bf405d9bc5c9a66d0c91ec -msgid "Azure ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:52 1a542064bc174d668ec6c1701490a076 -msgid "65540" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:56 bca5f6372b374ec19f70a3d2ec0ca67e -msgid "Vyos configuration" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:58 e2d8a5f4046240d0a23ca4e3fd684639 -msgid "" -"Configure the IKE and ESP settings to match a subset of those supported by " -"Azure:" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:80 6d547d6d1fa14ccc8948bceef68615b4 -msgid "Enable IPsec on eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:86 62b5ee4ee0924f2cab8739de17862612 -msgid "Configure a VTI with a dummy IP address" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:93 75d6082877044b21a8352a52d5887883 -msgid "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:99 3a6c4bc871fe4c048e7ead2f2d1eda9a -msgid "Configure the VPN tunnel" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:115 f49b5c5e37e24e1689dddc469c4608ea -msgid "**Important**: Add an interface route to reach Azure's BGP listener" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:121 7714f19656884885a022c6df481adf48 -msgid "Configure your BGP settings" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:131 a3b60878de2a436a895eac195a191428 -msgid "**Important**: Disable connected check \\" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po deleted file mode 100644 index c734bab6..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po +++ /dev/null @@ -1,222 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:6 -#: 9b9db6fa09124662b2a7c3335dbc144a -msgid "Route-Based Redundant Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:8 -#: 759fb45f3bf44f8fa56771e2b1d8299f -msgid "" -"This guide shows an example of a redundant (active-active) route-based IKEv2" -" site-to-site VPN to Azure using VTI and BGP for dynamic routing updates." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:13 -#: 73abec87c3ca4f83b32d667d2263bfa1 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:15 -#: 18c0980f9b09457f82b75d3473ff7764 -msgid "" -"A pair of Azure VNet Gateways deployed in active-active configuration with " -"BGP enabled." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:18 -#: 5c5653cb683f464fb3b5880c79c617ac -msgid "" -"A local network gateway deployed in Azure representing the Vyos device, " -"matching the below Vyos settings except for address space, which only " -"requires the Vyos private IP, in this example 10.10.0.5/32" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:23 -#: bbfc8956ac7443eba627417fdf67d024 -msgid "" -"A connection resource deployed in Azure linking the Azure VNet gateway and " -"the local network gateway representing the Vyos device." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:28 -#: e6ff621563b042338d4425002ae8a78b -msgid "Example" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:31 -#: 716721a06b7f4669a9b2409eb2aac65d -msgid "WAN Interface" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:31 -#: dfcb3352016049a98f1d3c0b0be32998 -msgid "eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:33 -#: 5d959b80a81f430f9d86a26a9ad19c3e -msgid "On-premises address space" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:33 -#: a3ceef7fc78c48949eb6c0eeae0b667a -msgid "10.10.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:35 -#: 80e725a06e004cc69f8ee875fcc6dfa8 -msgid "Azure address space" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:35 -#: 6d16c5efb5d745cf95e8ff423757616b -msgid "10.0.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:37 -#: ee5c0ac6e9014725a3fd16837ae0e288 -msgid "Vyos public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:37 -#: fc806f5176d946a9805e3f7baf40c7ce -msgid "198.51.100.3" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:39 -#: e846499ba5d248af818ff80cd6910265 -msgid "Vyos private IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:39 -#: 5e6a6539cd5e45ac9e8f1f9b07c0fc86 -msgid "10.10.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:41 -#: 90a33f04bce84814be2fb2de47ee9af5 -msgid "Azure VNet Gateway 1 public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:41 -#: 0559c71d81a6400fb5029149976df8d7 -msgid "203.0.113.2" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:43 -#: b834b0cd721542aba5842057601df99e -msgid "Azure VNet Gateway 2 public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:43 -#: 494e561c165342a995c23b36a38b97f4 -msgid "203.0.113.3" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:45 -#: 801eca976a174615b5cd752c1646d5b6 -msgid "Azure VNet Gateway BGP IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:45 -#: 1dd2e30409cb4e1da1af32da8e2ef380 -msgid "10.0.0.4,10.0.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:47 -#: 500be57e62db42f5a73ba13af5f90661 -msgid "Pre-shared key" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:47 -#: f4e179a9bbd249d0b23c6d6e252a1365 -msgid "ch00s3-4-s3cur3-psk" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:49 -#: 16b7665d8270452080540cc94e6ee8fa -msgid "Vyos ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:49 -#: 9250aa14f188401d9e4778537e44a36d -msgid "64499" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:51 -#: 4f57f84278e84e15af808cd47888d74c -msgid "Azure ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:51 -#: c583b170be9e4aeaaff113835ebee4e1 -msgid "65540" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:55 -#: 58d06a64237740d5921366d353c0cc2e -msgid "Vyos configuration" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:57 -#: 8752f9b33a9745629c606f160f9f2e18 -msgid "" -"Configure the IKE and ESP settings to match a subset of those supported by " -"Azure:" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:79 -#: f91c7ac88fd64a51afaa2497ea5c97a0 -msgid "Enable IPsec on eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:85 -#: b00fe5e7ffe24f7caf9c9ec2145cf006 -msgid "Configure two VTIs with a dummy IP address each" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:95 -#: c78f7df8e90f48d398ddfdf6f25403a1 -msgid "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:102 -#: 6bad30973bc846639ab878dcf67cbb4f -msgid "Configure the VPN tunnels" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:130 -#: 44e9904045894f43baea76edb6326273 -msgid "" -"**Important**: Add an interface route to reach both Azure's BGP listeners" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:137 -#: e86362b48b914a9285d07293c4dfc900 -msgid "Configure your BGP settings" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:152 -#: 8eff32668c1d4fef849d705526783f9d -msgid "" -"**Important**: Disable connected check, otherwise the routes learned from " -"Azure will not be imported into the routing table." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po deleted file mode 100644 index d6106abd..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po +++ /dev/null @@ -1,50 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:7 -#: d09ae8126681462993e92d093899abfd -msgid "BGP IPv6 unnumbered with extended nexthop" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:9 -#: 32a43eae8561459abb680e6c4ed1e083 -msgid "General information can be found in the :ref:`routing-bgp` chapter." -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:12 -#: 79b61cb0a1b049fdbe7cd106aeefbc98 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:14 -#: ../../configexamples/bgp-ipv6-unnumbered.rst:57 -#: 4cec5409b9554b65a3f193999725cc79 4e82bbee18eb49fca04f67464cd968e1 -msgid "Router A:" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:34 -#: ../../configexamples/bgp-ipv6-unnumbered.rst:118 -#: 56a2def17e61479c80767f815f9c2c34 4a9918e9212a49ca8899c41058c15724 -msgid "Router B:" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:55 -#: 4abe7ac3ae0b4dd79f948dc26d129037 -msgid "Results" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po deleted file mode 100644 index 0bcd885d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po +++ /dev/null @@ -1,598 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/ha.rst:7 6635636e1b2848cdaff0110647b1a93a -msgid "High Availability Walkthrough" -msgstr "" - -#: ../../configexamples/ha.rst:9 328dc19e47f3451c94a92ab9fd1d91be -msgid "" -"This document walks you through a complete HA setup of two VyOS machines. " -"This design is based on a VM as the primary router and a physical machine as" -" a backup, using VRRP, BGP, OSPF, and conntrack sharing." -msgstr "" - -#: ../../configexamples/ha.rst:13 f3fa38c6974646a1bee041f198e3bc34 -msgid "" -"This document aims to walk you through setting everything up, so at a point " -"where you can reboot any machine and not lose more than a few seconds worth " -"of connectivity." -msgstr "" - -#: ../../configexamples/ha.rst:18 cd75d9827a5e47f0b243e5ac7c9c1526 -msgid "Design" -msgstr "" - -#: ../../configexamples/ha.rst:20 e7dd91e9f3b84f5f8b058f7ec1f550e3 -msgid "" -"This is based on a real-life production design. One of the complex issues is" -" ensuring you have redundant data INTO your network. We do this with a pair " -"of Cisco Nexus switches and using Virtual PortChannels that are spanned " -"across them. As a bonus, this also allows for complete switch failure " -"without an outage. How you achieve this yourself is left as an exercise to " -"the reader. But our setup is documented here." -msgstr "" - -#: ../../configexamples/ha.rst:28 a8c9be49e8834a5989d661c13939f74d -msgid "Walkthrough suggestion" -msgstr "" - -#: ../../configexamples/ha.rst:30 5107a6fd819845d6bfe5da4bbc5cd410 -msgid "" -"The ``commit`` command is implied after every section. If you make an error," -" ``commit`` will warn you and you can fix it before getting too far into " -"things. Please ensure you commit early and commit often." -msgstr "" - -#: ../../configexamples/ha.rst:34 9b466ae1e3084c2487fa455690176700 -msgid "" -"If you are following through this document, it is strongly suggested you " -"complete the entire document, ONLY doing the virtual router1 steps, and then" -" come back and walk through it AGAIN on the backup hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:38 45de19cee0d54c2b8dcc4e176eb9cf7a -msgid "" -"This ensures you don't go too fast or miss a step. However, it will make " -"your life easier to configure the fixed IP address and default route now on " -"the hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:43 4ff61bf6bb484462be110aba531c24ad -msgid "Example Network" -msgstr "" - -#: ../../configexamples/ha.rst:45 e5762566a37b47e9956fce030e9219eb -msgid "" -"In this document, we have been allocated 203.0.113.0/24 by our upstream " -"provider, which we are publishing on VLAN100." -msgstr "" - -#: ../../configexamples/ha.rst:48 f8c62807293d4310af27b812215c71eb -msgid "" -"They want us to establish a BGP session to their routers on 192.0.2.11 and " -"192.0.2.12 from our routers 192.0.2.21 and 192.0.2.22. They are AS 65550 and" -" we are AS 65551." -msgstr "" - -#: ../../configexamples/ha.rst:52 f5c58c9d490245f8a4a137b7e716a599 -msgid "" -"Our routers are going to have a floating IP address of 203.0.113.1, and use " -".2 and .3 as their fixed IPs." -msgstr "" - -#: ../../configexamples/ha.rst:55 858e51844e7a46ae8f90e89347793ba7 -msgid "" -"We are going to use 10.200.201.0/24 for an 'internal' network on VLAN201." -msgstr "" - -#: ../../configexamples/ha.rst:57 ad0d8fa61ad84a79bcda13f5c24035f6 -msgid "" -"When traffic is originated from the 10.200.201.0/24 network, it will be " -"masqueraded to 203.0.113.1" -msgstr "" - -#: ../../configexamples/ha.rst:60 8c41661f7f0d47909e9cd9b41488f2fb -msgid "" -"For connection between sites, we are running a WireGuard link to two REMOTE " -"routers and using OSPF over those links to distribute routes. That remote " -"site is expected to send traffic from anything in 10.201.0.0/16" -msgstr "" - -#: ../../configexamples/ha.rst:65 61fe940554c040708bee57444169fa8e -msgid "VLANs" -msgstr "" - -#: ../../configexamples/ha.rst:67 8e8acb9d0feb48a48864e4d5a334b49c -msgid "These are the vlans we will be using:" -msgstr "" - -#: ../../configexamples/ha.rst:69 1d1fdf6d8f2248ee80b33f9c4156323b -msgid "50: Upstream, using the 192.0.2.0/24 network allocated by them." -msgstr "" - -#: ../../configexamples/ha.rst:70 1c606178267146308a748c1680340a5b -msgid "100: 'Public' network, using our 203.0.113.0/24 network." -msgstr "" - -#: ../../configexamples/ha.rst:71 ceb5aa6290cb496e8862dbdc9810eeed -msgid "201: 'Internal' network, using 10.200.201.0/24" -msgstr "" - -#: ../../configexamples/ha.rst:74 ed3303e4df4f47a6a44b1c4e563eef9f -msgid "Hardware" -msgstr "" - -#: ../../configexamples/ha.rst:76 6c8cc0e1d2ba4e068a9a56edab17035e -msgid "switch1 (Nexus 10gb Switch)" -msgstr "" - -#: ../../configexamples/ha.rst:77 2b8ca1bfc14b4f889f6250d8bb9cefd1 -msgid "switch2 (Nexus 10gb Switch)" -msgstr "" - -#: ../../configexamples/ha.rst:78 24ba0c7bad77467fa78e8b78dc3e6511 -msgid "compute1 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:79 cb94b9b3258a4e499cc77606f027e53e -msgid "compute2 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:80 e8bfef4d8cf744f785f31e6fab83f0e2 -msgid "compute3 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:81 3201e0706ae44014a8c66fbcdf98396d -msgid "router2 (Random 1RU machine with 4 NICs)" -msgstr "" - -#: ../../configexamples/ha.rst:83 1fcc6ca17f1c43c7a8f06987e57f9b0e -msgid "Note that router1 is a VM that runs on one of the compute nodes." -msgstr "" - -#: ../../configexamples/ha.rst:86 0de10057e9b6488e829ed5a52d9ddbc9 -msgid "Network Cabling" -msgstr "" - -#: ../../configexamples/ha.rst:88 c635e244c7954a5b9a920bb7d5eee4ff -msgid "" -"From Datacenter - This connects into port 1 on both switches, and is tagged " -"as VLAN 50" -msgstr "" - -#: ../../configexamples/ha.rst:90 3db2a959fe2b43c389856f9ec845c94a -msgid "Cisco VPC Crossconnect - Ports 39 and 40 bonded between each switch" -msgstr "" - -#: ../../configexamples/ha.rst:91 887ffd05a80d4ed3b8237e0937efd045 -msgid "Hardware Router - Port 8 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:92 dbcb6bca65914da7828f17d1cd0012cb -msgid "compute1 - Port 9 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:93 58f7491bce3049d4b855c840bbd278c2 -msgid "compute2 - Port 10 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:94 67b8ad69203a49f6a1f3f51db1340ba0 -msgid "compute3 - Port 11 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:96 922733c2845c439281cf4ae28367406d -msgid "" -"This is ignoring the extra Out-of-band management networking, which should " -"be on totally different switches, and a different feed into the rack, and is" -" out of scope of this." -msgstr "" - -#: ../../configexamples/ha.rst:100 ff780c97cb90413796269eb194ae6b07 -msgid "" -"Our implementation uses VMware's Distributed Port Groups, which allows " -"VMware to use LACP. This is a part of the ENTERPRISE licence, and is not " -"available on a free licence. If you are implementing this and do not have " -"access to DPGs, you should not use VMware, and use some other virtualization" -" platform instead." -msgstr "" - -#: ../../configexamples/ha.rst:108 a84f52e0e1d64b0aa9fc5a0c773d7602 -msgid "Basic Setup (via console)" -msgstr "" - -#: ../../configexamples/ha.rst:110 200c203631fd4a4b8aaebed5bf35b9fb -msgid "" -"Create your router1 VM. So it can withstand a VM Host failing or a network " -"link failing. Using VMware, this is achieved by enabling vSphere DRS, " -"vSphere Availability, and creating a Distributed Port Group that uses LACP." -msgstr "" - -#: ../../configexamples/ha.rst:114 56302a6a7a91496b8b2812c697f399f2 -msgid "" -"Many other Hypervisors do this, and I'm hoping that this document will be " -"expanded to document how to do this for others." -msgstr "" - -#: ../../configexamples/ha.rst:117 16738dc1523d4c9d89cd0721071045e1 -msgid "" -"Create an 'All VLANs' network group, that passes all trunked traffic through" -" to the VM. Attach this network group to router1 as eth0." -msgstr "" - -#: ../../configexamples/ha.rst:120 c95508528a7b44baa796c0145a6f1c82 -msgid "" -"VMware: You must DISABLE SECURITY on this Port group. Make sure that " -"``Promiscuous Mode``\\ , ``MAC address changes`` and ``Forged transmits`` " -"are enabled. All of these will be done as part of failover." -msgstr "" - -#: ../../configexamples/ha.rst:125 e73697b70e1146d895921faf43c2af71 -msgid "Bonding on Hardware Router" -msgstr "" - -#: ../../configexamples/ha.rst:127 ddaaa893a69f44cb984a0c51e15a6e5f -msgid "" -"Create a LACP bond on the hardware router. We are assuming that eth0 and " -"eth1 are connected to port 8 on both switches, and that those ports are " -"configured as a Port-Channel." -msgstr "" - -#: ../../configexamples/ha.rst:141 169cb700875f4be98c4dce46ffa51ca5 -msgid "Assign external IP addresses" -msgstr "" - -#: ../../configexamples/ha.rst:143 968533e09d8e4ff2a10eced097e77e09 -msgid "" -"VLAN 100 and 201 will have floating IP addresses, but VLAN50 does not, as " -"this is talking directly to upstream. Create our IP address on vlan50." -msgstr "" - -#: ../../configexamples/ha.rst:146 66ee1b962118455aa159df42da77deb1 -msgid "" -"For the hardware router, replace ``eth0`` with ``bond0``. As (almost) every " -"command is identical, this will not be specified unless different things " -"need to be performed on different hosts." -msgstr "" - -#: ../../configexamples/ha.rst:154 59a6738568c540f1949fe02d4fcf34cc -msgid "In this case, the hardware router has a different IP, so it would be" -msgstr "" - -#: ../../configexamples/ha.rst:161 3e40d84c53a04d9eb0d6809ccc20b7b2 -msgid "Add (temporary) default route" -msgstr "" - -#: ../../configexamples/ha.rst:163 de5087605cf546c68ee58e5687e5f92a -msgid "" -"It is assumed that the routers provided by upstream are capable of acting as" -" a default router, add that as a static route." -msgstr "" - -#: ../../configexamples/ha.rst:174 a79c996cc6f64b5eb9fbdee8f7a226cf -msgid "Enable SSH" -msgstr "" - -#: ../../configexamples/ha.rst:176 551ce6f349f647d2b9d4ea9deff17487 -msgid "" -"Enable SSH so you can now SSH into the routers, rather than using the " -"console." -msgstr "" - -#: ../../configexamples/ha.rst:184 fada2faa8d5046bd96ca04b615f816b3 -msgid "" -"At this point, you should be able to SSH into both of them, and will no " -"longer need access to the console (unless you break something!)" -msgstr "" - -#: ../../configexamples/ha.rst:189 874f028d74c2487e872a241eedb25679 -msgid "VRRP Configuration" -msgstr "" - -#: ../../configexamples/ha.rst:191 5cb0eca9555b466eb78c771fbec62eba -msgid "" -"We are setting up VRRP so that it does NOT fail back when a machine returns " -"into service, and it prioritizes router1 over router2." -msgstr "" - -#: ../../configexamples/ha.rst:195 134f86480d6846d19b2a5c475d9a09f9 -msgid "Internal Network" -msgstr "" - -#: ../../configexamples/ha.rst:197 f5ecaa7e6a99408cbc48e6191f936e12 -msgid "" -"This has a floating IP address of 10.200.201.1/24, using virtual router ID " -"201. The difference between them is the interface name, hello-source-" -"address, and peer-address." -msgstr "" - -#: ../../configexamples/ha.rst:201 ../../configexamples/ha.rst:237 -#: ../../configexamples/ha.rst:366 ../../configexamples/ha.rst:540 -#: 024e10c2ef1d45538b14d1441b2aba12 4ff23649975144ea8761a1f0db9fc38b -#: ead03513ccf349d69a72ad719341ccc0 3b0bc4b0e37242ea9b06d4a5fd523b51 -msgid "**router1**" -msgstr "" - -#: ../../configexamples/ha.rst:215 ../../configexamples/ha.rst:250 -#: ../../configexamples/ha.rst:581 64a85b10ff4940fe834992340e3d79e9 -#: d5a58d53fb57403a93d109ea8f0499b8 b0c10d042e1b4aa7aebd7cbbb4359cff -msgid "**router2**" -msgstr "" - -#: ../../configexamples/ha.rst:230 c02ad28f7389436488aa2f0667a4c92a -msgid "Public Network" -msgstr "" - -#: ../../configexamples/ha.rst:232 6ba11351d94e405ca551816733f5d6a7 -msgid "" -"This has a floating IP address of 203.0.113.1/24, using virtual router ID " -"113. The virtual router ID is just a random number between 1 and 254, and " -"can be set to whatever you want. Best practices suggest you try to keep them" -" unique enterprise-wide." -msgstr "" - -#: ../../configexamples/ha.rst:265 5cc83f7b616a4ba094220576cb889002 -msgid "Create VRRP sync-group" -msgstr "" - -#: ../../configexamples/ha.rst:267 7ecafb24ca98488b8f1415f33752a416 -msgid "" -"The sync group is used to replicate connection tracking. It needs to be " -"assigned to a random VRRP group, and we are creating a sync group called " -"``sync`` using the vrrp group ``int``." -msgstr "" - -#: ../../configexamples/ha.rst:276 ../../configexamples/ha.rst:337 -#: 0c50ea68a8144106bada8d98ee2c0b35 ce7487619dbe4873a0e344be20f23baf -msgid "Testing" -msgstr "" - -#: ../../configexamples/ha.rst:278 8bfcd793743d4ff0a4b8de2e4d72977d -msgid "" -"At this point, you should be able to see both IP addresses when you run " -"``show interfaces``\\ , and ``show vrrp`` should show both interfaces in " -"MASTER state (and SLAVE state on router2)." -msgstr "" - -#: ../../configexamples/ha.rst:292 0fb62e4241214eb89230fb03c7372d34 -msgid "You should be able to ping to and from all the IPs you have allocated." -msgstr "" - -#: ../../configexamples/ha.rst:295 aa72fecb45c44884a1139c0375451e82 -msgid "NAT and conntrack-sync" -msgstr "" - -#: ../../configexamples/ha.rst:297 eded51367628479d8b4117240d6478eb -msgid "" -"Masquerade Traffic originating from 10.200.201.0/24 that is heading out the " -"public interface." -msgstr "" - -#: ../../configexamples/ha.rst:300 5451f8ac48d346bda205c19c2c4691bd -msgid "" -"We explicitly exclude the primary upstream network so that BGP or OSPF " -"traffic doesn't accidentally get NAT'ed." -msgstr "" - -#: ../../configexamples/ha.rst:312 5d204005a8004750afc2d562b5dc1a33 -msgid "Configure conntrack-sync and enable helpers" -msgstr "" - -#: ../../configexamples/ha.rst:314 43870f92ca894847be0108d6643fdbf0 -msgid "" -"Conntrack helper modules are enabled by default, but they tend to cause more" -" problems than they're worth in complex networks. You can disable all of " -"them at one go." -msgstr "" - -#: ../../configexamples/ha.rst:322 f38092677ae4464187fe29eda38f2ae8 -msgid "" -"Now enable replication between nodes. Replace eth0.201 with bond0.201 on the" -" hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:339 2860f289aac74a5687ebd85c0487d8e9 -msgid "" -"The simplest way to test is to look at the connection tracking stats on the " -"standby hardware router with the command ``show conntrack-sync statistics``." -" The numbers should be very close to the numbers on the primary router." -msgstr "" - -#: ../../configexamples/ha.rst:343 2754bcacb8b141ffb07a28ac712e5f0f -msgid "" -"When you have both routers up, you should be able to establish a connection " -"from a NAT'ed machine out to the internet, reboot the active machine, and " -"that connection should be preserved, and will not drop out." -msgstr "" - -#: ../../configexamples/ha.rst:348 7926537525124f4ba89416e2b9c2b296 -msgid "OSPF Over WireGuard" -msgstr "" - -#: ../../configexamples/ha.rst:350 eb10c0fc01ad4eadbd69a27512fa8cff -msgid "" -"Wireguard doesn't have the concept of an up or down link, due to its design." -" This complicates AND simplifies using it for network transport, as for " -"reliable state detection you need to use SOMETHING to detect when the link " -"is down." -msgstr "" - -#: ../../configexamples/ha.rst:354 34792be20b6a4dc2a479d4fd1eb38c5a -msgid "" -"If you use a routing protocol itself, you solve two problems at once. This " -"is only a basic example, and is provided as a starting point." -msgstr "" - -#: ../../configexamples/ha.rst:358 07fe314c1d244c58918fbec62add102c -msgid "Configure Wireguard" -msgstr "" - -#: ../../configexamples/ha.rst:360 79d18f239c9d47e89a9ea9d3e6c8b7d6 -msgid "" -"There is plenty of instructions and documentation on setting up Wireguard. " -"The only important thing you need to remember is to only use one WireGuard " -"interface per OSPF connection." -msgstr "" - -#: ../../configexamples/ha.rst:364 6e2c049a5e2b4d6b9c9de79ba7dcfcc3 -msgid "We use small /30's from 10.254.60/24 for the point-to-point links." -msgstr "" - -#: ../../configexamples/ha.rst:368 6313ed08caa34dfa8dc53630ad69e9cb -msgid "" -"Replace the 203.0.113.3 with whatever the other router's IP address is." -msgstr "" - -#: ../../configexamples/ha.rst:389 82b6b6db1dc44350b4cbc8e8a314eae6 -msgid "**offsite1**" -msgstr "" - -#: ../../configexamples/ha.rst:391 b355d228c62349df8cff68502b2d1b29 -msgid "This is connecting back to the STATIC IP of router1, not the floating." -msgstr "" - -#: ../../configexamples/ha.rst:412 d625b918b5054ea1be331cc13b37e9f2 -msgid "Test WireGuard" -msgstr "" - -#: ../../configexamples/ha.rst:414 79ca90a7810649a39de3f4757d54fe5f -msgid "Make sure you can ping 10.254.60.1 and .2 from both routers." -msgstr "" - -#: ../../configexamples/ha.rst:417 ea2eda10fd404f6eb09c00f3a56609d1 -msgid "Create Export Filter" -msgstr "" - -#: ../../configexamples/ha.rst:419 1781368cc3fb4fa8a7fef2ca50fd2238 -msgid "" -"We only want to export the networks we know. Always do a whitelist on your " -"route filters, both importing and exporting. A good rule of thumb is **'If " -"you are not the default router for a network, don't advertise it'**. This " -"means we explicitly do not want to advertise the 192.0.2.0/24 network (but " -"do want to advertise 10.200.201.0 and 203.0.113.0, which we ARE the default " -"route for). This filter is applied to ``redistribute connected``. If we WERE" -" to advertise it, the remote machines would see 192.0.2.21 available via " -"their default route, establish the connection, and then OSPF would say " -"'192.0.2.0/24 is available via this tunnel', at which point the tunnel would" -" break, OSPF would drop the routes, and then 192.0.2.0/24 would be reachable" -" via default again. This is called 'flapping'." -msgstr "" - -#: ../../configexamples/ha.rst:448 3fa81ded7b2b4191977371b88e9c359c -msgid "Create Import Filter" -msgstr "" - -#: ../../configexamples/ha.rst:450 3908a1799dea49648304c5e91a236abf -msgid "" -"We only want to import networks we know. Our OSPF peer should only be " -"advertising networks in the 10.201.0.0/16 range. Note that this is an " -"INVERSE MATCH. You deny in access-list 100 to accept the route." -msgstr "" - -#: ../../configexamples/ha.rst:470 0d63d8b7e349423689b890c3fbe79241 -msgid "Enable OSPF" -msgstr "" - -#: ../../configexamples/ha.rst:472 9d6650db6fd84a4b91a026c32f4cb9fd -msgid "" -"Every router **must** have a unique router-id. The 'reference-bandwidth' is " -"used because when OSPF was originally designed, the idea of a link faster " -"than 1gbit was unheard of, and it does not scale correctly." -msgstr "" - -#: ../../configexamples/ha.rst:489 6ebb88d1d9ca46488180f5a76ef013d9 -msgid "Test OSPF" -msgstr "" - -#: ../../configexamples/ha.rst:491 812917c76e66417e8eb1ae6a4a48b711 -msgid "" -"When you have enabled OSPF on both routers, you should be able to see each " -"other with the command ``show ip ospf neighbour``. The state must be 'Full' " -"or '2-Way'. If it is not, then there is a network connectivity issue between" -" the hosts. This is often caused by NAT or MTU issues. You should not see " -"any new routes (unless this is the second pass) in the output of ``show ip " -"route``" -msgstr "" - -#: ../../configexamples/ha.rst:498 fc0e4249dc1449e2b16c6ed4d2970097 -msgid "Advertise connected routes" -msgstr "" - -#: ../../configexamples/ha.rst:500 30a19b02b06842b5854ddffa7b0f3ad9 -msgid "" -"As a reminder, only advertise routes that you are the default router for. " -"This is why we are NOT announcing the 192.0.2.0/24 network, because if that " -"was announced into OSPF, the other routers would try to connect to that " -"network over a tunnel that connects to that network!" -msgstr "" - -#: ../../configexamples/ha.rst:511 fdefb152353a413e8238054e3c158d8e -msgid "" -"You should now be able to see the advertised network on the other host." -msgstr "" - -#: ../../configexamples/ha.rst:514 76e146cffb1a47fdaae34f9c1a74d2a7 -msgid "Duplicate configuration" -msgstr "" - -#: ../../configexamples/ha.rst:516 9af13c626127489190a5475e554d0027 -msgid "" -"At this point, you now need to create the X link between all four routers. " -"Use amdifferent /30 for each link." -msgstr "" - -#: ../../configexamples/ha.rst:520 44602b1155fc4647a8d3de483e9f37c5 -msgid "Priorities" -msgstr "" - -#: ../../configexamples/ha.rst:522 bb7300e02c254e0bbae13bf9e5106d59 -msgid "" -"Set the cost on the secondary links to be 200. This means that they will not" -" be used unless the primary links are down." -msgstr "" - -#: ../../configexamples/ha.rst:531 9fe545f2929b484f83077b7c0a5c3a5e -msgid "This will be visible in 'show ip route'." -msgstr "" - -#: ../../configexamples/ha.rst:534 114fb5790b9c49fb8133c2a9fd5d2465 -msgid "BGP" -msgstr "" - -#: ../../configexamples/ha.rst:536 ec4424a0b26f40e985a844767d8916ee -msgid "" -"BGP is an extremely complex network protocol. An example is provided here." -msgstr "" - -#: ../../configexamples/ha.rst:538 db63ce80f3a14d99914fc0eeff1d8c29 -msgid "Router id's must be unique." -msgstr "" - -#: ../../configexamples/ha.rst:543 0d5527a10ee54fea8be1fd010b1b3af8 -msgid "" -"The ``redistribute ospf`` command is there purely as an example of how this " -"can be expanded. In this walkthrough, it will be filtered by BGPOUT rule " -"10000, as it is not 203.0.113.0/24." -msgstr "" - -#: ../../configexamples/ha.rst:583 569496a685d24d70a371a91381b90bf3 -msgid "" -"This is identical, but you use the BGPPREPENDOUT route-map to advertise the " -"route with a longer path." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po deleted file mode 100644 index ecf47379..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po +++ /dev/null @@ -1,74 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/index.rst:4 221cdd3e723548398440f0bbb733d7d3 -msgid "Configuration Blueprints" -msgstr "" - -#: ../../configexamples/index.rst:6 af362a0bbe0343efb3c18e916f6eb5fa -msgid "This chapter contains various configuration examples:" -msgstr "" - -#: ../../configexamples/index.rst:24 6078e9736f7a4bf3871932455e83b281 -msgid "Configuration Blueprints (autotest)" -msgstr "" - -#: ../../configexamples/index.rst:26 7356a0291dfd4eef8b3548ffe16c6c3d -msgid "The next pages contains automatic full tested configuration examples." -msgstr "" - -#: ../../configexamples/index.rst:28 76e850e3a0b149f79fd0256fa46bd4b2 -msgid "" -"Each lab will build an test from an external script. The page content will " -"generate, so changes will not take an effect." -msgstr "" - -#: ../../configexamples/index.rst:31 d07c374b439e49e3bc9896a7315fe837 -msgid "" -"A host ``vyos-oobm`` will use as a ssh proxy. This host is just necessary " -"for the Lab test." -msgstr "" - -#: ../../configexamples/index.rst:34 886c86ce28bc41d8911370caa26d877f -msgid "The process will do the following steps:" -msgstr "" - -#: ../../configexamples/index.rst:36 5856e3be60d54e04bed197f4afccdd20 -msgid "create the lab on a eve-ng server" -msgstr "" - -#: ../../configexamples/index.rst:37 d942be2969a045e5a2a68b24d7ffccbe -msgid "configure each host in the lab" -msgstr "" - -#: ../../configexamples/index.rst:38 cc5afea66c11467fb2d0f65f86aeb8f3 -msgid "do some defined tests" -msgstr "" - -#: ../../configexamples/index.rst:39 c416622bee5e41aa82b6eaaef4d3ca15 -msgid "optional do an upgrade to a higher version and do step 3 again." -msgstr "" - -#: ../../configexamples/index.rst:40 448ae7b0c859456f81c549a1cf2e3a78 -msgid "generate the documentation and include files" -msgstr "" - -#: ../../configexamples/index.rst:41 50da447b745c4d14a81d72608448b992 -msgid "shutdown and destroy the lab, if there is no error" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po deleted file mode 100644 index dc6efef0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po +++ /dev/null @@ -1,575 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:3 -#: eb41ae1b116f44aca5187f22bd6e3c38 -msgid "Inter-VRF Routing over VRF Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:5 -#: f0616081b9784167ab9c07a7350cb12c -msgid "" -"**Virtual Routing and Forwarding** is a technology that allow multiple " -"instance of a routing table to exist within a single device. One of the key " -"aspect of **VRFs** is that do not share the same routes or interfaces, " -"therefore packets are forwarded between interfaces that belong to the same " -"VRF only." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:10 -#: ea59f5e8a5e6486d80e4e4d65d0de34c -msgid "" -"Any information related to a VRF is not exchanged between devices -or in the" -" same device- by default, this is a technique called **VRF-Lite**." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:13 -#: ac294973fcec422ea2769beb2f586a5d -msgid "" -"Keep networks isolated is -in general- a good principle, but there are cases" -" where you might need that some network can access other in a different VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:16 -#: 8b47e55fd64d400b96bd14a41ba2f2cd -msgid "" -"The scope of this document is to cover such cases in a dynamic way without " -"the use of MPLS-LDP." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:19 -#: 0a4d0fe3ed8948c685128f24ac43b5e2 -msgid "" -"General information about L3VPNs can be found in the " -":ref:`configuration/vrf/index:L3VPN VRFs` chapter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:23 -#: 4c8919e0683e407e853338762e005b73 -msgid "Overview" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:25 -#: 4649bebe3b9c452a983b440677eef8ef -msgid "Let’s say we have a requirement to have multiple networks." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:27 -#: 4adf12c76e3042d1aa0615aa93f6c028 -msgid "LAN 1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:28 -#: 2bb42d1b9104415db47557052928d2e8 -msgid "LAN 2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:29 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:727 -#: 9e0ca4a0df5f4fb88e8aeb21241714a2 7eecdf4e5fe844e39ce8c9bd6e275a30 -#: e12f1fbf318148dda9a8468e462ec0f0 9da4873cd37c45d2a1e9e6c8cce272f7 -msgid "Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:30 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: c81a9b48a8c045e2aed48642d26b13ab 091224a1afed4eac89b75bb783b866c4 -msgid "Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:32 -#: 99888ffd849e412cbad21c08b326160e -msgid "" -"Both LANs have to be able to route between each other, both will have " -"managed devices through a dedicated management network and both will need " -"Internet access yet the LAN2 will need access to some set of outside " -"networks, not all. The management network will need access to both LANs but " -"cannot have access to/from the outside." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:38 -#: 0f23fd96749846889ded22c066ef1961 -msgid "" -"This scenario could be a nightmare applying regular routing and might need " -"filtering in multiple interfaces." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:41 -#: 6ab38930088d40d7828f23898bd381d1 -msgid "" -"A simple solution could be using different routing tables, or VRFs for all " -"the networks so we can keep the routing restrictions. But for us to route " -"between the different VRFs we would need a cable or a logical connection " -"between each other:" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:46 -#: 5a813032fce9458eb29d0498989614da -msgid "One cable/logical connection between LAN1 and LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:47 -#: ef9bfefcf4104ea0b95f1a3b7a9ee796 -msgid "One cable/logical connection between LAN1 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:48 -#: 6462901ab71c4c9ba3bdd5ed60994278 -msgid "One cable/logical connection between LAN2 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:49 -#: d3f6c4a564e741508c3095bd738b4e0b -msgid "One cable/logical connection between LAN1 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:50 -#: 50efd8066bcb420fbf4f3e43a4b2ac4a -msgid "One cable/logical connection between LAN2 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:52 -#: 12a6f2d5993647ca884f54b7ea65424d -msgid "As we can see this is unpractical." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:54 -#: 86964e2fdcfe42b1acef7ebe5f6be8e7 -msgid "" -"To address this scenario we will use to our advantage an extension of the " -"BGP routing protocol that will help us in the “Export” between VRFs without " -"the need for MPLS." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:58 -#: 67c99502bfe344c18b2772fead0bfdef -msgid "" -"MP-BGP or MultiProtocol BGP introduces two main concepts to solve this " -"limitation: - Route Distinguisher (RD): Is used to distinguish between " -"different VRFs –called VPNs- inside the BGP Process. The RD is appended to " -"each IPv4 Network that is advertised into BGP for that VPN making it a " -"unique VPNv4 route. - Route Target (RT): This is an extended BGP community " -"append to the VPNv4 route in the Import/Export process. When a route passes " -"from the VRF routing table into the BGP process it will add the configured " -"export extended community(ies) for that VPN. When that route needs to go " -"from BGP into the VRF routing table will only pass if that given VPN import " -"policy matches any of the appended community(ies) into that prefix." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:72 -#: de34231c61084297b36ddb578477b67d -msgid "Topology" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rstNone -#: cdc1520b038842a68babb2a9a2525fc4 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:82 -#: 16f28c31e1f143c5986ab85cc840b32b -msgid "IP Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 40ae6d91025b43babf6a28156ac7500b -msgid "Device-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: c35074ba59f949b8a2a46f3811869080 -msgid "Device-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: bc3f51095ca3484f863d2762794aa0f8 -msgid "IPv4 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 72b11e54e57a4b439f2b75faa92ce102 -msgid "IPv6 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:616 -#: 3f41e5bfa21947be87ec7081d7ee8ba2 b54901e4a8b249f89f67b364fa24663d -#: 19cc658588fd4ebf9502ea26ea498d7a 02ad5c6d77bf461396340263ef2d3420 -#: 900ff739e58e4f79bf99a1f561c405b4 -msgid "Core" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:701 -#: 56574650a4194ff79d5645140cf03d6b f25b32ec296c44b7aa3458a0f9b44760 -#: 9b5243427ba34f7cbf9939103226d9b1 -msgid "LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: 2d1e1dc89c1f40318ed9748de6273f9f -msgid "10.1.1.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: cbe4082191094f4bab8916aef6f9a5c0 -msgid "2001:db8::/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:713 -#: 65ddfdbbfa3b4c349173b73a2fa3356f b7f31fe8dd854681bb11900e87d1f179 -#: 5734149a4be547639059a2cdd24050e8 -msgid "LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: b7c3c79b8c4842cca5336eb1b94dff85 -msgid "172.16.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: f4007f87de1f4bada7ce0e55633d427b -msgid "2001:db8::2/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1daaf01c8340423d93f96757bf6041ed -msgid "192.168.3.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1b4913f318a04b02a17c852a5f28e312 -msgid "2001:db8::4/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:739 -#: f9c8ebe5ce5f46d5ae5f6a311ec9ce1c 1a78a58c2a3d41d8aa2f998dc8bfa291 -msgid "ISP" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: e5138de5b6844fb4bc208ad2d66aec94 -msgid "10.2.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: c048ed3059334c8c964fc7c9595d8062 -msgid "2001:db8::6/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:97 -#: a4c3a66971e240858d9343a409da32e9 -msgid "RD & RT Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 129b297c60754ac498ec18058a07dcee -msgid "VRF" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 935cb9b1a2e0495fb580d674e4a9e3d0 -msgid "RD" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: edb2eabdd1284a7dbe82d4544b8616b6 -msgid "RT" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: 79ca3a7d0fa14923bfca6af65dff61e9 b49d97869905413e8df40c8e1abb1b3b -msgid "64496:1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: 81afc720df0d48a0b9df047a6543aeea 0e1ffef8c627472daa211f00b436b220 -msgid "64496:2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: 471376839df44e6a98853fbe83f8c302 3b9f6979c3374fb7a754201c21604f75 -msgid "64496:50" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: 901fb99798914a7ba27ae0b4e7e2af72 c22fb6bacd9f4f178ebc8d64e28967fe -msgid "64496:100" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:113 -#: 37b3b1695a5142b8b4eb0f4eda8e9392 -msgid "Configurations" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:115 -#: 8fcddacdabb347938fdddd5df33ef082 -msgid "" -"We use a static route configuration in between the Core and each LAN and " -"Management router, and BGP between the Core router and the ISP router but " -"any dynamic routing protocol can be used." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:120 -#: d0ba532920c146b58e8609eeb52a9351 -msgid "Remote Networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:122 -#: 2370f525c998496dae1e93ecb14ef1d2 -msgid "" -"The following template configuration can be used in each remote router based" -" in our topology." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:134 -#: a3a69aba21694a54945c258e54511f4c -msgid "Core Router" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:137 -#: 1d698f00b16644879ae215618bc43467 -msgid "Step 1: VRF and Configurations to remote networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:139 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:231 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:290 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:774 -#: e37f8f84308849c193ca0456b07b9e12 7a85dc42dbe8467c93d1259f5c8a2831 -#: 00c29f4758af4aa6bdb6ae7100df73c1 2b99ef8b24734d5ca80591ca6fdd5b75 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:143 -#: 9d83ffd71ed3407584a88fe68993f486 -msgid "" -"Set the VRF name and Table ID, set interface address and bind it to the VRF." -" Last add the static route to the remote network." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:160 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:248 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:320 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:829 -#: 3aba84af46df47cc9fd2ae84f9b503da da748005d3874b4480b7bbd9d591e27a -#: 1ecb9ec20cdc4c2893ee6fca2ee51358 a280fb687cdc40178d509af90951189b -msgid "Verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:164 -#: 37ce0e67288f45fe9ef9c08369138fb2 -msgid "" -"Checking the routing table of the VRF should reveal both static and " -"connected entries active. A PING test between the Core and remote router is " -"a way to validate connectivity within the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:228 -#: c75588c0d4934b26bc2191593d95078c -msgid "Step 2: BGP Configuration for VRF-Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:235 -#: 1b8331d7180b4c1fa784335dc8a73fb7 -msgid "" -"Setting BGP global local-as as well inside the VRF. Redistribute static " -"routes to inject configured networks into the BGP process but still inside " -"the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:252 -#: 23fba5b0b23849658c56bfe042cba29a -msgid "" -"Check the BGP VRF table and verify if the static routes are injected showing" -" the correct next-hop information." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:287 -#: 43ff822c83a548f1bfc03261deb495b8 -msgid "Step 3: VPN Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:293 -#: c4ae33aea35c4a3f9deaff43b955090e -msgid "" -"Within the VRF we set the Route-Distinguisher (RD) and Route-Targets (RT), " -"then we enable the export/import VPN." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:312 -#: 4186090c0eb4432aa7763a11232d7c73 -msgid "" -"A key point to understand is that if we need two VRFs to communicate between" -" each other EXPORT rt from VRF1 has to be in the IMPORT rt list from VRF2. " -"But this is only in ONE direction, to complete the communication the EXPORT " -"rt from VRF2 has to be in the IMPORT rt list from VRF1." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:317 -#: dbff84d09cf543e78ef3bedf22f4cce0 -msgid "" -"There are some cases where this is not needed -for example, in some DDoS " -"appliance- but most inter-vrf routing designs use the above configurations." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:324 -#: 20333d5d9494441a974b2c7b031c3620 -msgid "" -"After configured all the VRFs involved in this topology we take a deeper " -"look at both BGP and Routing table for the VRF LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:417 -#: 50932524836549ed803143fff7ca704a -msgid "" -"As we can see in the BGP table any imported route has been injected with a " -"\"@\" followed by the VPN id; In the routing table of the VRF, if the route " -"was installed, we can see -between round brackets- the exported VRF table." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:422 -#: 040c2e2ba85b4694b54fc037d8e22e62 -msgid "Step 4: End to End verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:425 -#: 56ca70dcbe824d18ad0daeed1283e2cb -msgid "Now we perform some end-to-end testing" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:427 -#: 5f0852ffedff48d0b4b2996888183b7a -msgid "From Management to LAN1/LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:469 -#: 6ce8210eb4d24cceb40d4b8940231d99 -msgid "From Management to Outside (fails as intended)" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:520 -#: c1d07bc3b8de4706bd224c06ee17dbbe -msgid "LAN1 to Outside" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:571 -#: 3db16afd744a4f0bb44dfcf01987a098 -msgid "" -"we are using \"source-address\" option cause we are not redistributing " -"connected interfaces into BGP on the Core router hence there is no comeback " -"route and ping will fail." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:575 -#: cfb5c05281f242db8863602ddb0693f9 -msgid "LAN1 to LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:601 -#: bf275914b4ec4567b5fecc55c805c298 -msgid "Conclusions" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:603 -#: 066850a20fcf43a8a9f17c58e2038810 -msgid "" -"Inter-VRF routing is a well-known solution to address complex routing " -"scenarios that enable -in a dynamic way- to leak routes between VRFs. Is " -"recommended to take special consideration while designing route-targets and " -"its application as it can minimize future interventions while creating a new" -" VRF will automatically take the desired effect in its propagation." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:611 -#: 8683a9d3f2104a9db49b0a0907555f32 -msgid "Appendix-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:614 -#: 5abc7d4aebac4e02af6886aac14cf1ce -msgid "Full configuration from all devices" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:764 -#: 41e37392648b4e2da99de7267631749e -msgid "Appendix-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:767 -#: 8f882d02b8fa437f87c5f3e7520c95c5 -msgid "Route-Filtering" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:770 -#: bf9c4776ac3e43c180cf5abb70bfa7aa -msgid "" -"When importing routes using MP-BGP it is possible to filter a subset of them" -" before are injected in the BGP table. One of the most common case is to use" -" a route-map with an prefix-list." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:778 -#: 68fcdc98c6d246099510635b49afe34e -msgid "We create a prefix-list first and add all the routes we need to." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:803 -#: e7a748ac55dc4c02b90fea5c37b64b9b -msgid "" -"Then add a route-map and reference to above prefix. Consider that the " -"actions taken inside the prefix will MATCH the routes that will be affected " -"by the actions inside the rules of the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:815 -#: 1bb8831212be41398444370636f0f441 -msgid "" -"We are using a \"white list\" approach by allowing only what is necessary. " -"In case that need to implement a \"black list\" approach then you will need " -"to change the action in the route-map for a deny BUT you need to add a rule " -"that permits the rest due to the implicit deny in the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:820 -#: 384686127eda49c39439e379043fd224 -msgid "" -"Then we need to attach the policy to the BGP process. This needs to be under" -" the import statement in the vrf we need to filter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:853 -#: e9beeb420b0e42cf8fe71412b1255dc0 -msgid "" -"As we can see even if both VRF LAN1 and LAN2 has the same import RTs we are " -"able to select which routes are effectively imported and installed." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po deleted file mode 100644 index 5f113413..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po +++ /dev/null @@ -1,588 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:4 -#: 998a7d4fc7604358b63c64b7e10c9256 -msgid "L3VPN for Hub-and-Spoke connectivity with VyOS" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:6 -#: 686abf9e6407494ea9f8adb1e6a38ba4 -msgid "" -"IP/MPLS technology is widely used by various service providers and large " -"enterprises in order to achieve better network scalability, manageability " -"and flexibility. It also provides the possibility to deliver different " -"services for the customers in a seamless manner. Layer 3 VPN (L3VPN) is a " -"type of VPN mode that is built and delivered through OSI layer 3 networking " -"technologies. Often the border gateway protocol (BGP) is used to send and " -"receive VPN-related data that is responsible for the control plane. L3VPN " -"utilizes virtual routing and forwarding (VRF) techniques to receive and " -"deliver user data as well as separate data planes of the end-users. It is " -"built using a combination of IP- and MPLS-based information. Generally, " -"L3VPNs are used to send data on back-end VPN infrastructures, such as for " -"VPN connections between data centres, HQs and branches." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:20 -#: 890e7aea999d499bbcd0cdf856d99266 -msgid "" -"An L3VPN consists of multiple access links, multiple VPN routing and " -"forwarding (VRF) tables, and multiple MPLS paths or multiple P2MP LSPs. An " -"L3VPN can be configured to connect two or more customer sites. In hub-and-" -"spoke MPLS L3VPN environments, the spoke routers need to have unique Route " -"Distinguishers (RDs). In order to use the hub site as a transit point for " -"connectivity in such an environment, the spoke sites export their routes to " -"the hub. Spokes can talk to hubs, but never have direct paths to other " -"spokes. All traffic between spokes is controlled and delivered over the hub " -"site." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:31 -#: e546c7fa938240fbb028a21e16cd21bd -msgid "" -"To deploy a Layer3 VPN with MPLS on VyOS, we should meet a couple " -"requirements in order to properly implement the solution. We'll use the " -"following nodes in our LAB environment:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:35 -#: 98565fe6ffb947e09692e9b7b1fb9912 -msgid "2 x Route reflectors (VyOS-RRx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:36 -#: 56560e4d5b514b569eb498d80ccfd796 -msgid "4 x Provider routers (VyOS-Px)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:37 -#: 29e234d5eff54c03b262f561d6ba4308 -msgid "3 x Provider Edge (VyOs-PEx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:38 -#: b6d0c34166be4ebeb304f7da74c8fedf -msgid "3 x Customer Edge (VyOS-CEx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:40 -#: 95ddfbd9c6d14f0284add13b0b318aeb -msgid "The following software was used in the creation of this document:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:42 -#: 2e1ff92ea1d34b3380b4735f9231bbaa -msgid "Operating system: VyOS" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:43 -#: 1a1845ca31364523ac85c14afed17a6b -msgid "Version: 1.4-rolling-202110310317" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:44 -#: be17aee6c8e24d0a9c81a719c92b962c -msgid "Image name: vyos-1.4-rolling-202110310317-amd64.iso" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:46 -#: 94e4d99e94914c41b8f5a501b90a9c1a -msgid "" -"**NOTE:** VyOS Router (tested with VyOS 1.4-rolling-202110310317) – The " -"configurations below are specifically for VyOS 1.4.x." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:49 -#: cf278ef398a348f19de9082189238ad3 -msgid "" -"General information can be found in the :ref:`configuration/vrf/index:L3VPN " -"VRFs` chapter." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:55 -#: b78300c0062d4f20adb7a5a718366771 -msgid "Topology" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rstNone -#: 1f165bb067114d18877f62c65d93df63 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:65 -#: 8a0c9d1b570c4c7cbe2de877527a2c8d -msgid "How does it work?" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:67 -#: cb4349ce8fa34bd391aeef02ba55c8c9 -msgid "" -"As we know the main assumption of L3VPN “Hub and Spoke” is, that the traffic" -" between spokes have to pass via hub, in our scenario VyOS-PE2 is the Hub PE" -" and the VyOS-CE1-HUB is the central customer office device that is " -"responsible for controlling access between all spokes and announcing its " -"network prefixes (10.0.0.100/32). VyOS-PE2 has the main VRF (its name is " -"BLUE_HUB), its own Route-Distinguisher(RD) and route-target import/export " -"lists. Multiprotocol-BGP(MP-BGP) delivers L3VPN related control-plane " -"information to the nodes across network where PEs Spokes import the route-" -"target 60535:1030 (this is export route-target of vrf BLUE_HUB) and export " -"its own route-target 60535:1011(this is vrf BLUE_SPOKE export route-target)." -" Therefore, the Customer edge nodes can only learn the network prefixes of " -"the HUB site [10.0.0.100/32]. For this example VyOS-CE1 has network prefixes" -" [10.0.0.80/32] / VyOS-CE2 has network prefixes [10.0.0.90/32]. Route-" -"Reflector devices VyOS-RR1 and VyOS-RR2 are used to simplify network routes " -"exchange and minimize iBGP peerings between devices." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:83 -#: 60dd546b31004b06af47f4a1ce701957 -msgid "L3VPN configuration parameters table:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 565d53c1b26a4de38feaa86b567c6b4e -msgid "Node" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 34eba7825ea54979a42f178e9dcd15bf -msgid "Role" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: b89d4c69529d4488b011d8e8db5aa4b4 -msgid "VRF" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: f55441b962624fd6b5c1538290091f7e -msgid "RD" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 6e72edabaf07419ea0abb13bb7789540 -msgid "RT import" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: e547d56f80ca46f1ac625b270ab02628 -msgid "RT export" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: ea3d4c4a18ec433b8c7f3ac03981f8c2 -msgid "VyOS-PE2" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 55bc9c2598064d92a3b9fae0fc6a1154 -msgid "Hub" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 1291d942846d4c6cae1e8833e139cb5d -msgid "BLUE_HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 27596f3bee3d43f28a16a42174e74667 -msgid "10.80.80.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: a4ca55dd19b14bd9a3b02fddeaf7eb11 -msgid "65035:1011 65035:1030" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 21adc69cf2bf4575ae4476a8cb6d056c 4862295b4bae4ea1baac2124700b1236 -#: 5a80925f27574dddb9d476febf102516 -msgid "65035:1030" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: a0fdcadaac2946a1bad9533989517a9c -msgid "VyOS-PE1" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: b4744ce92c634f65b6558eb37e536454 c98d8778bb984c8eab3202150c36d157 -msgid "Spoke" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: bce236afe7fb4c15b1adff31ccdaeea6 b1801511514c4b169d55b38e25b0a021 -msgid "BLUE_SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: cc8eb3ef69e94ebf81b298848a74f246 -msgid "10.50.50.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: b234869593f9450bb4866570315fb225 93a1e9117a7041a4ab0ec98cdde1a35d -msgid "65035:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 60fdfd315f2a4711a0f2b53299b51566 -msgid "VyOS-PE3" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 23c8e2bb64ab41d593c0e2aa6e921fbe -msgid "10.60.60.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:100 -#: 9e879fff2f324772adfe0bc310edc4a4 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:105 -#: 7477a6ffa308480fbee1b135a33ae15a -msgid "Step-1: Configuring IGP and enabling MPLS LDP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:107 -#: 15b715d0ed4248cf9593d4c8c72bc20c -msgid "" -"At the first step we need to configure the IP/MPLS backbone network using " -"OSPF as IGP protocol and LDP as label-switching protocol for the base " -"connectivity between **P** (rovider), **P** (rovider) **E** (dge) and **R** " -"(oute) **R** (eflector) nodes:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:112 -#: 0fdd2f02198142519dfa1b13c7a87d43 -msgid "VyOS-P1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:142 -#: 6fa7d00718fa44eea0355cfc8d67d9af -msgid "VyOS-P2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:168 -#: 405ddfb3d90241e6b9791a694e8c02fc -msgid "VyOS-P3:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:194 -#: f214a604b9194bceb30e7ad4dcc9cc04 -msgid "VyOS-P4:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:224 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:362 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:413 -#: ed57672a54e540168ca1cb343c953144 91ace2d281b24fd5b0ea37e1876978bc -#: de90bc4f836b493cad00b4ef434ed1ee -msgid "VyOS-PE1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:241 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:376 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:435 -#: 2b0b8e09b36c4192905fd8fcadb3317e a4e9cf5d0fbb4537addb56d6ecff66e3 -#: b6016d3b47a549e0bcfba58d5fa86717 -msgid "VyOS-PE2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:262 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:390 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:457 -#: dc7cd8343e6743a0815e02f3d65df79a 0d769e475d9c4846ae32e22f5bf3d91c -#: 77fe05eee30a4adf9df916a5462cd9a5 -msgid "VyOS-PE3:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:279 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:328 -#: 61d86fc34fbd4aed98036cf60f0dd615 fd431069d9f24c3084c24124059724d4 -msgid "VyOS-RR1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:299 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:345 -#: 55304b8d06834fc69cdb07738e63e625 f8923e269249490fa37cc90c7b1342ec -msgid "VyOS-RR2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:322 -#: 2e846b31f9c44dfbab01271d60e398c6 -msgid "Step-2: Configuring iBGP for L3VPN control-plane" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:324 -#: 7b89e4318dec4188b74b6b3f5dab7b59 -msgid "" -"At this step we are going to enable iBGP protocol on MPLS nodes and Route " -"Reflectors (two routers for redundancy) that will deliver IPv4 VPN (L3VPN) " -"routes between them:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:407 -#: 58d3377a35da4d30a1cdb7229a5fe29c -msgid "Step-3: Configuring L3VPN VRFs on PE nodes" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:409 -#: fe4e7c69c7424e24888c3f3706d8c8b0 -msgid "" -"This section provides configuration steps for setting up VRFs on our PE " -"nodes including CE facing interfaces, BGP, rd and route-target import/export" -" based on the pre-defined parameters." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:482 -#: fc9f63f8aca0444da7ec55ff854e4676 -msgid "Step-4: Configuring CE nodes" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:484 -#: 925625dcfa774f7f9934408b8214a7f1 -msgid "" -"Dynamic routing used between CE and PE nodes and eBGP peering established " -"for the route exchanging between them. All routes received by PEs are then " -"exported to L3VPN and delivered from Spoke sites to Hub and vise-versa based" -" on previously configured L3VPN parameters." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:490 -#: 47a7f4d1ffeb4def9c259e4e6e629cd2 -msgid "VyOS-CE1-SPOKE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:507 -#: 8f961af78f9b4d888bd12c34cf65ec60 -msgid "VyOS-CE1-HUB:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:525 -#: a41c0ae5954a4760acf3b56323072447 -msgid "VyOS-CE2-SPOKE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:545 -#: 4c4149624eba4d5b903a371d003f6dba -msgid "Step-5: Verification" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:547 -#: a82f92d1466d41e994f0679d05553320 -msgid "" -"This section describes verification commands for MPLS/BGP/LDP protocols and " -"L3VPN related routes as well as diagnosis and reachability checks between CE" -" nodes." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:551 -#: d87f385db4c442eea1c679e29862e55f -msgid "" -"Let’s check IPv4 routing and MPLS information on provider nodes (same " -"procedure for all P nodes):" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:554 -#: 387768aa305a4d89bf9504179b279283 -msgid "“show ip ospf neighbor” for checking ospf relationship" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:567 -#: 14d1985bcdcc43e4a9381ab7d746af1f -msgid "“show mpls ldp neighbor “ for checking ldp neighbors" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:579 -#: 14f7b630eb854181a68a201cd4ff573b -msgid "“show mpls ldp binding” for checking mpls label assignment" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:636 -#: 9f0c750511f44cac99373cc626930b21 -msgid "" -"Now we’re checking iBGP status and routes from route-reflector nodes to " -"other devices:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:639 -#: 27aef0ad05464cc59458e0f4d7785462 -msgid "“show bgp ipv4 vpn summary” for checking BGP VPNv4 neighbors:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:658 -#: dc50a484ccb14f9ca7e7dec858073973 -msgid "“show bgp ipv4 vpn” for checking all VPNv4 prefixes information:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:698 -#: fc808be9ede24f739e02e5129eba3963 -msgid "" -"“show bgp ipv4 vpn x.x.x.x/x” for checking best path selected for specific " -"VPNv4 destination" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:716 -#: 528fe8121f4640fb96768623ce8ca51d -msgid "" -"Also we can verify how PE devices receives VPNv4 networks from the RRs and " -"installing them to the specific customer VRFs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:719 -#: ef0c4185fb5d4547b3e2c790769f104d -msgid "" -"“show bgp ipv4 vpn summary” for checking iBGP neighbors against route-" -"reflector devices:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 -#: 1f1dbb0745cc43278c22ba38335200df -msgid "“show bgp vrf all” for checking all the prefix learning on BGP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 -#: 3705f8a528294628a4b27fa3913af275 -msgid "within VRFs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 -#: c668ee5332604c59a958d6d9565e2cfe -msgid "“show bgp vrf BLUE_SPOKE summary” for checking EBGP neighbor" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 -#: 82b64c97c93a4f7c901153092449c801 -msgid "information between PE and CE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:784 -#: 0ca40736901446fcad91df434b158fb5 -msgid "“show ip route vrf BLUE_SPOKE” for viewing the RIB in our Spoke PE." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:783 -#: 388ba3e42cfb453682eff0522884b664 -msgid "" -"Using this command we are also able to check the transport and customer " -"label (inner/outer) for Hub network prefix (10.0.0.100/32):" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:807 -#: df85772519284579bf2097c0313d76b2 -msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking the best-path to the" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:806 -#: 3ded1eaa580b4d75a1aebdd4248776fe -msgid "" -"specific VPNv4 destination including extended community and remotelabel " -"information. This procedure is the same on all Spoke nodes:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:831 -#: dbb5f2aa2caa4f5aa52ca697597e0f4c -msgid "Now, let’s check routing information on out Hub PE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 -#: 1e4f350b52274f58ae7a54adaff0b412 -msgid "“show bgp ipv4 vpn summary” for checking iBGP neighbors again" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 -#: 8a347810b376407ba2c69b3f23fce640 -msgid "VyOS-RR1/RR2" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:851 -#: 9bc7d0b71fba42b281873b8a1be783d8 -msgid "“show bgp vrf all” for checking all the prefixes learning on BGP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 -#: 118b9f4e005f4e04b1632e4589ddfa17 -msgid "“show bgp vrf BLUE_HUB summary” for checking EBGP neighbor" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 -#: 93c455e1b8874441adba6171d4381d59 -msgid "CE Hub device" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:909 -#: 0137b1e74074467495469f4604661c56 -msgid "“show ip route vrf BLUE_HUB” to view the RIB in our Hub PE." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:907 -#: 54511e5d16824c21a9eeb419cf668caa -msgid "" -"With this command we are able to check the transport and customer label " -"(inner/outer) for network spokes prefixes 10.0.0.80/32 - 10.0.0.90/32" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 -#: 0e7f267bff6140e598dee3231a8eadc5 -msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking best-path," -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 -#: 2d0e3c0fc3c74b058df139a5fb208aa0 -msgid "extended community and remote label of specific destination" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:985 -#: 3d25f766a7a743f289fdb81b7bbe3168 -msgid "Finally, let’s check the reachability between CEs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:987 -#: 08b5c6d6886144fa86ad19ea63c1afb2 -msgid "VyOS-CE1-SPOKE -----> VyOS-CE-HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1025 -#: 9cbd876b3f4d48b78595fcb0300221cf -msgid "VyOS-CE-HUB -------> VyOS-CE1-SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1026 -#: 368f34ba9eb84e7ebeca0b2dafdff68a -msgid "VyOS-CE-HUB -------> VyOS-CE2-SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1085 -#: 17a80175953c4e24916458908f8443e1 -msgid "VyOS-CE2-SPOKE -------> VyOS-CE-HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1123 -#: 062bae083b9c48369539bf248ef35b6f -msgid "" -"**Note:** At the moment, trace mpls doesn’t show labels/paths. So we’ll see " -"* * * for the transit routers of the mpls backbone." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po deleted file mode 100644 index df1aa330..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po +++ /dev/null @@ -1,48 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/ospf-unnumbered.rst:7 29d634a6af9c469eb9fd48424a9f3d5c -msgid "OSPF unnumbered with ECMP" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:9 c3072bd445424325bf17c2296e1d44e1 -msgid "General information can be found in the :ref:`routing-ospf` chapter." -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:12 -#: 9aa3a8a8aff941979fa7396c8509d31c -msgid "Configuration" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:14 -#: ../../configexamples/ospf-unnumbered.rst:52 -#: f9990c6209254eddae5cf323b898db68 7615801deebe40a6b1b55c8cd441ef0e -msgid "Router A:" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:31 -#: ../../configexamples/ospf-unnumbered.rst:87 -#: a6c539b6f0ad42d7ae958feb6f19b9b3 9cb799c9efc549b0a72113e8514dc7b6 -msgid "Router B:" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:50 -#: a5b67b9fc6ba4a79a42835e8a06ea49c -msgid "Results" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po deleted file mode 100644 index e49e10f8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po +++ /dev/null @@ -1,172 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/pppoe-ipv6-basic.rst:7 -#: d01a18dec1a142a8855a0bc03a82e72d -msgid "PPPoE IPv6 Basic Setup for Home Network" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:9 -#: 9ef7b0d68dd9494faf9502d86502f352 -msgid "" -"This document is to describe a basic setup using PPPoE with DHCPv6-PD + " -"SLAAC to construct a typical home network. The user can follow the steps " -"described here to quickly setup a working network and use this as a starting" -" point to further configure or fine-tune other settings." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:14 -#: 1bc45c10d4a248f6998a8a90665ee73a -msgid "" -"To achieve this, your ISP is required to support DHCPv6-PD. If you're not " -"sure, please contact your ISP for more information." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:18 -#: e57a18b57aac4b5ebe79cd1b5a249be4 -msgid "Network Topology" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rstNone -#: 7d29b5deb46f4dd5ba8c411ff15c3580 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:26 -#: 9b4e35fc5bf949f6a08a601e0f85b41f -msgid "Configurations" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:29 -#: e2264f3deb0f48e3be8d824b4558bdf6 -msgid "PPPoE Setup" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:38 -#: 0fb2a3f4a82946bc801f42aea42116a9 -msgid "" -"Fill ``password`` and ``user`` with the credential provided by your ISP." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:39 -#: 37defbee2b744b67a69c4393ca546d72 -msgid "``service-name`` can be an arbitrary string." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:42 -#: 5ae65ec790db46bbbfe7d471f2f7ebd2 -msgid "DHCPv6-PD Setup" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:44 -#: 0abfd09ecb7a423196d7010533a9eef5 -msgid "" -"During address configuration, in addition to assigning an address to the WAN" -" interface, ISP also provides a prefix to allow the router to configure " -"addresses of LAN interface and other nodes connecting to LAN, which is " -"called prefix delegation (PD)." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:54 -#: f09a5ec22ab24c12907d90a279d89a13 -msgid "" -"Here we use the prefix to configure the address of eth1 (LAN) to form " -"``<prefix>::64``, where ``64`` is hexadecimal of address 100." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:56 -#: 1f554d13466d467d9d8a1aa4480dec52 -msgid "" -"For home network users, most of time ISP only provides /64 prefix, hence " -"there is no need to set SLA ID and prefix length. See :ref:`pppoe-interface`" -" for more information." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:61 -#: 37a4fe866ce44dd6a82988da55311a6a -msgid "Router Advertisement" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:63 -#: 5d74e570a4be470e951a4fe806442c2d -msgid "" -"We need to enable router advertisement for LAN network so that PC can " -"receive the prefix and use SLAAC to configure the address automatically." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:72 -#: 1922e24702884c2289071ab9cc0053e5 -msgid "Set MTU in advertisement to 1492 because of PPPoE header overhead." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:73 -#: 4efc1c1477cf49399f430202782675f3 -msgid "" -"Set DNS server address in the advertisement so that clients can obtain it by" -" using RDNSS option. Most operating systems (Windows, Linux, Mac) should " -"already support it." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:76 -#: ba3687f3d52e4e0dad78491c4827825e -msgid "" -"Here we set the prefix to ``::/64`` to indicate advertising any /64 prefix " -"the LAN interface is assigned." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:78 -#: ed8c9fcabb584dd28037b2deb6954f8e -msgid "" -"Since some ISPs disconnects continuous connection for every 2~3 days, we set" -" ``valid-lifetime`` to 2 days to allow PC for phasing out old address." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:82 -#: 7de4b4c573da4409bceb27abd04c4063 -msgid "Basic Firewall" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:84 -#: bbe045c3a1fb403385b959777dfdfe8c -msgid "" -"To have basic protection while keeping IPv6 network functional, we need to:" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:86 -#: 9cb07d9a5372428d883056ccd6073d79 -msgid "Allow all established and related traffic for router and LAN" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:87 -#: f98467c842b64dbc948d17d120011d65 -msgid "Allow all icmpv6 packets for router and LAN" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:88 -#: a6cc69dd5a304905844a5ff7218dca13 -msgid "Allow DHCPv6 packets for router" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:111 -#: b101c4ec16274088a7a102a7ebe1bb82 -msgid "" -"Note to allow the router to receive DHCPv6 response from ISP. We need to " -"allow packets with source port 547 (server) and destination port 546 " -"(client)." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po deleted file mode 100644 index 976e43a8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po +++ /dev/null @@ -1,219 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/wan-load-balancing.rst:8 -#: 9f05f08a64a4424292daad78fad5a6e2 -msgid "WAN Load Balancer examples" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:12 -#: ced8dacc57da404fb3d767a8fa5f199b -msgid "Example 1: Distributing load evenly" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:14 -#: 71129440d8fa4e80958dde7df43ed1db -msgid "The setup used in this example is shown in the following diagram:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rstNone -#: ../../configexamples/wan-load-balancing.rstNone -#: eef518f424234b9e877063b444e4715e 36a842a81f0e40eb8491f2b78a82b3d0 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:23 -#: ../../configexamples/wan-load-balancing.rst:75 -#: ../../configexamples/wan-load-balancing.rst:104 -#: ../../configexamples/wan-load-balancing.rst:135 -#: f84efa18552041ddb93b10d114806dbc c05f3e6b75614f619891c902ea58dad2 -#: 290135d81ebf4d28a6c79ac052c171f6 cf186aa1226e49a38af1fbfe6ba85e1b -msgid "Overview" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:24 -#: d6df93a47c7f48b5b195b2f219a88bb3 -msgid "" -"All traffic coming in through eth2 is balanced between eth0 and eth1 on the " -"router." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:26 -#: 9cbde66a8bff45f2b23af438df71dd36 -msgid "" -"Pings will be sent to four targets for health testing (33.44.55.66, " -"44.55.66.77, 55.66.77.88 and 66.77.88.99)." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:28 -#: 77ed08f8b1454a09ad8eeffdefdf17b2 -msgid "" -"All outgoing packets are assigned the source address of the assigned " -"interface (SNAT)." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:30 -#: 08426bfc131c48d6bc2162479ec7b56d -msgid "" -"eth0 is set to be removed from the load balancer's interface pool after 5 " -"ping failures, eth1 will be removed after 4 ping failures." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:34 -#: 11f1d3c652c54f049e9af334fa38a106 -msgid "Create static routes to ping targets" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:35 -#: f973a670c56346c2926c9be556660bd4 -msgid "" -"Create static routes through the two ISPs towards the ping targets and " -"commit the changes:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:46 -#: a9cb47e088ac44c19325a69295109a9d -msgid "Configure the load balancer" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:47 -#: d5f35bfbdbb9448e9082c8598285675e -msgid "Configure the WAN load balancer with the parameters described above:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:68 -#: 384337b95dcc4f60ad417e0e7fc93f82 -msgid "Example 2: Failover based on interface weights" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:70 -#: f414970795f740d49d837fe9561c7d72 -msgid "This example uses the failover mode." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:76 -#: a14f9000d16c4cf2a6dc8db548872845 -msgid "" -"In this example, eth0 is the primary interface and eth1 is the secondary " -"interface. To provide simple failover functionality. If eth0 fails, eth1 " -"takes over." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:81 -#: a709f9da975d434d83d8d1ecccfae31f -msgid "Create interface weight based configuration" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:82 -#: 122b99f9d9274c83b31f16ac0ddf7f07 -msgid "" -"The configuration steps are the same as in the previous example, except rule" -" 10. So we keep the configuration, remove rule 10 and add a new rule for the" -" failover mode:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:95 -#: 9470dd8d60da4a6fb676059fc12c2e1c -msgid "Example 3: Failover based on rule order" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:97 -#: c32d2814f74240a1807a5295a10b21de -msgid "" -"The previous example used the failover command to send traffic through eth1 " -"if eth0 fails. In this example, failover functionality is provided by rule " -"order." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:105 -#: 855bce2604b44db0be549937bd437e78 -msgid "" -"Two rules will be created, the first rule directs traffic coming in from " -"eth2 to eth0 and the second rule directs the traffic to eth1. If eth0 fails " -"the first rule is bypassed and the second rule matches, directing traffic to" -" eth1." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:111 -#: 2825af09d2bb40deb7ab2b0b4425a37f -msgid "Create rule order based configuration" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:112 -#: 42e71205c1374e30b236fd3c33d88d07 -msgid "" -"We keep the configuration from the previous example, delete rule 10 and " -"create the two new rules as described:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:124 -#: f4162881a62d48769911ff1fec82ee95 -msgid "Example 4: Failover based on rule order - priority traffic" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:126 -#: ../../configexamples/wan-load-balancing.rst:136 -#: e3e9af1e73994f4ab2d38a9e67a7fdf5 2888de594abc4c1ebea9fd2c1b3189bf -msgid "" -"A rule order for prioritizing traffic is useful in scenarios where the " -"secondary link has a lower speed and should only carry high priority " -"traffic. It is assumed for this example that eth1 is connected to a slower " -"connection than eth0 and should prioritize VoIP traffic." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:142 -#: c255dbcebfcd4beaac19f746a4516531 -msgid "Create rule order based configuration with low speed secondary link" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:143 -#: dd2df2f8dbc3418b8a56fccef4db961f -msgid "" -"We keep the configuration from the previous example, delete rule 20 and " -"create a new rule as described:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:156 -#: a16b4fa634b5462eb57dac3d1700cffe -msgid "Example 5: Exclude traffic from load balancing" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:158 -#: fc3846b150314a348e795d7bffdfbcea -msgid "" -"In this example two LAN interfaces exist in different subnets instead of one" -" like in the previous examples:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:167 -#: d3071c91cb44411f98bf1f4db5206a4f -msgid "Adding a rule for the second interface" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:169 -#: c06ffdabeef740e182701946afb4b6ec -msgid "" -"Based on the previous example, another rule for traffic from the second " -"interface eth3 can be added to the load balancer. However, traffic meant to " -"flow between the LAN subnets will be sent to eth0 and eth1 as well. To " -"prevent this, another rule is required. This rule excludes traffic between " -"the local subnets from the load balancer. It also excludes locally-sources " -"packets (required for web caching with load balancing). eth+ is used as an " -"alias that refers to all ethernet interfaces:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po deleted file mode 100644 index 7ae4c684..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po +++ /dev/null @@ -1,323 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/zone-policy.rst:6 3c76f26421954ac884480d0cffe55150 -msgid "Zone-Policy example" -msgstr "" - -#: ../../configexamples/zone-policy.rst:8 b000af62a2ff45e3bea0983ff08c6ca9 -msgid "" -"In :vytask:`T2199` the syntax of the zone configuration was changed. The " -"zone configuration moved from ``zone-policy zone <name>`` to ``firewall zone" -" <name>``." -msgstr "" - -#: ../../configexamples/zone-policy.rst:13 518ed4192332498b988ad701dbe4ae94 -msgid "Native IPv4 and IPv6" -msgstr "" - -#: ../../configexamples/zone-policy.rst:15 e785499caee9483ebbfa8fea63bd3f60 -msgid "We have three networks." -msgstr "" - -#: ../../configexamples/zone-policy.rst:24 d5184c69966f41c5acd57ba576316df4 -msgid "" -"**This specific example is for a router on a stick, but is very easily " -"adapted for however many NICs you have**:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:28 dc181a02a98a45da8888bc017de3ea1f -msgid "Internet - 192.168.200.100 - TCP/80" -msgstr "" - -#: ../../configexamples/zone-policy.rst:29 4e066389682c40048d57dec2c83a5aae -msgid "Internet - 192.168.200.100 - TCP/443" -msgstr "" - -#: ../../configexamples/zone-policy.rst:30 99c22b93805b4a9d97c17590c0d1ff93 -msgid "Internet - 192.168.200.100 - TCP/25" -msgstr "" - -#: ../../configexamples/zone-policy.rst:31 98671bd795584e58ab09f67a17c41bf1 -msgid "Internet - 192.168.200.100 - TCP/53" -msgstr "" - -#: ../../configexamples/zone-policy.rst:32 132e6aa544e14ab68d588186821b0cf1 -msgid "VyOS acts as DHCP, DNS forwarder, NAT, router and firewall." -msgstr "" - -#: ../../configexamples/zone-policy.rst:33 378d3439fdd441d0b598dee31369da95 -msgid "" -"192.168.200.200/2001:0DB8:0:BBBB::200 is an internal/external DNS, web and " -"mail (SMTP/IMAP) server." -msgstr "" - -#: ../../configexamples/zone-policy.rst:35 45a4384bc0fc4bd1a25c98a27c2a81ce -msgid "" -"192.168.100.10/2001:0DB8:0:AAAA::10 is the administrator's console. It can " -"SSH to VyOS." -msgstr "" - -#: ../../configexamples/zone-policy.rst:37 5cc8e033a70c48bcbc424e36c169c4af -msgid "LAN and DMZ hosts have basic outbound access: Web, FTP, SSH." -msgstr "" - -#: ../../configexamples/zone-policy.rst:38 7345f3e3a5874d65b6922d88f3117ecd -msgid "LAN can access DMZ resources." -msgstr "" - -#: ../../configexamples/zone-policy.rst:39 2413bb4e87ee4a92922530672b633c3c -msgid "DMZ cannot access LAN resources." -msgstr "" - -#: ../../configexamples/zone-policy.rst:40 604e13042cc6421fa69f297748ae55ab -msgid "Inbound WAN connect to DMZ host." -msgstr "" - -#: ../../configexamples/zone-policy.rstNone c296c8f6b6874d18872c119a8cc8ee57 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/zone-policy.rst:47 8aacd45be8534832803d7d08a1a8b19d -msgid "" -"The VyOS interface is assigned the .1/:1 address of their respective " -"networks. WAN is on VLAN 10, LAN on VLAN 20, and DMZ on VLAN 30." -msgstr "" - -#: ../../configexamples/zone-policy.rst:50 5e0f72b4b2db4789ac8dd371ba669517 -msgid "It will look something like this:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:79 74742cf5724e4f2cb3049240b8b10f52 -msgid "Zones Basics" -msgstr "" - -#: ../../configexamples/zone-policy.rst:81 634e5b24c3f749cc9428984dd8206b28 -msgid "" -"Each interface is assigned to a zone. The interface can be physical or " -"virtual such as tunnels (VPN, PPTP, GRE, etc) and are treated exactly the " -"same." -msgstr "" - -#: ../../configexamples/zone-policy.rst:85 6224d85ed139427b8bec0f53015beeb3 -msgid "" -"Traffic flows from zone A to zone B. That flow is what I refer to as a zone-" -"pair-direction. eg. A->B and B->A are two zone-pair-destinations." -msgstr "" - -#: ../../configexamples/zone-policy.rst:88 8cfb35f32511467cb39a75b1d6cd9548 -msgid "Ruleset are created per zone-pair-direction." -msgstr "" - -#: ../../configexamples/zone-policy.rst:90 ab2f3b9301084a50ac3c4342abfc2cfa -msgid "" -"I name rule sets to indicate which zone-pair-direction they represent. eg. " -"ZoneA-ZoneB or ZoneB-ZoneA. LAN-DMZ, DMZ-LAN." -msgstr "" - -#: ../../configexamples/zone-policy.rst:93 c7c352c3ba8341ee9563ded10b507dd9 -msgid "" -"In VyOS, you have to have unique Ruleset names. In the event of overlap, I " -"add a \"-6\" to the end of v6 rulesets. eg. LAN-DMZ, LAN-DMZ-6. This allows " -"for each auto-completion and uniqueness." -msgstr "" - -#: ../../configexamples/zone-policy.rst:97 c0ee89a6de5b40e8b7b1f41327938ce7 -msgid "" -"In this example we have 4 zones. LAN, WAN, DMZ, Local. The local zone is the" -" firewall itself." -msgstr "" - -#: ../../configexamples/zone-policy.rst:100 25d67004a0b34f2d80fe07eb586b31eb -msgid "" -"If your computer is on the LAN and you need to SSH into your VyOS box, you " -"would need a rule to allow it in the LAN-Local ruleset. If you want to " -"access a webpage from your VyOS box, you need a rule to allow it in the " -"Local-LAN ruleset." -msgstr "" - -#: ../../configexamples/zone-policy.rst:105 074031ebe23742cf9ab553c1d3c89851 -msgid "" -"In rules, it is good to keep them named consistently. As the number of rules" -" you have grows, the more consistency you have, the easier your life will " -"be." -msgstr "" - -#: ../../configexamples/zone-policy.rst:123 36212be96d234f809e3aa0635b224e23 -msgid "" -"The first two rules are to deal with the idiosyncrasies of VyOS and " -"iptables." -msgstr "" - -#: ../../configexamples/zone-policy.rst:126 cdaf927567ba470a843b6daed8e148a5 -msgid "" -"Zones and Rulesets both have a default action statement. When using Zone-" -"Policies, the default action is set by the zone-policy statement and is " -"represented by rule 10000." -msgstr "" - -#: ../../configexamples/zone-policy.rst:130 b923769f3fa648cabd265468da6f0ed8 -msgid "" -"It is good practice to log both accepted and denied traffic. It can save you" -" significant headaches when trying to troubleshoot a connectivity issue." -msgstr "" - -#: ../../configexamples/zone-policy.rst:134 8cdbfa157d0c40c5aaa5ce98e2e10eba -msgid "To add logging to the default rule, do:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:141 8370b1669e3244a6a370ab9344a5e114 -msgid "" -"By default, iptables does not allow traffic for established sessions to " -"return, so you must explicitly allow this. I do this by adding two rules to " -"every ruleset. 1 allows established and related state packets through and " -"rule 2 drops and logs invalid state packets. We place the " -"established/related rule at the top because the vast majority of traffic on " -"a network is established and the invalid rule to prevent invalid state " -"packets from mistakenly being matched against other rules. Having the most " -"matched rule listed first reduces CPU load in high volume environments. " -"Note: I have filed a bug to have this added as a default action as well." -msgstr "" - -#: ../../configexamples/zone-policy.rst:152 b98728b4c0444251a8ddd9aae0061313 -msgid "" -"''It is important to note, that you do not want to add logging to the " -"established state rule as you will be logging both the inbound and outbound " -"packets for each session instead of just the initiation of the session. Your" -" logs will be massive in a very short period of time.''" -msgstr "" - -#: ../../configexamples/zone-policy.rst:157 5731588a00a1445aae957e1dfca6f6a9 -msgid "" -"In VyOS you must have the interfaces created before you can apply it to the " -"zone and the rulesets must be created prior to applying it to a zone-policy." -msgstr "" - -#: ../../configexamples/zone-policy.rst:161 214fa70e97f947ecb6bcb6ee8a95f7d7 -msgid "" -"I create/configure the interfaces first. Build out the rulesets for each " -"zone-pair-direction which includes at least the three state rules. Then I " -"setup the zone-policies." -msgstr "" - -#: ../../configexamples/zone-policy.rst:165 ff4bfdb0fea6403bbb05ec6ea9fa65b7 -msgid "" -"Zones do not allow for a default action of accept; either drop or reject. It" -" is important to remember this because if you apply an interface to a zone " -"and commit, any active connections will be dropped. Specifically, if you are" -" SSH’d into VyOS and add local or the interface you are connecting through " -"to a zone and do not have rulesets in place to allow SSH and established " -"sessions, you will not be able to connect." -msgstr "" - -#: ../../configexamples/zone-policy.rst:172 217de4fa5abe448d8c381c002f97e539 -msgid "" -"The following are the rules that were created for this example (may not be " -"complete), both in IPv4 and IPv6. If there is no IP specified, then the " -"source/destination address is not explicit." -msgstr "" - -#: ../../configexamples/zone-policy.rst:226 68c0c6d0b20b468f99608f851ae72f5f -msgid "Since we have 4 zones, we need to setup the following rulesets." -msgstr "" - -#: ../../configexamples/zone-policy.rst:243 5b84e1b04a934648956fa3d46c7d7ab3 -msgid "" -"Even if the two zones will never communicate, it is a good idea to create " -"the zone-pair-direction rulesets and set enable-default-log. This will allow" -" you to log attempts to access the networks. Without it, you will never see " -"the connection attempts." -msgstr "" - -#: ../../configexamples/zone-policy.rst:248 633e0ef63aa44eb68b1f92674e715140 -msgid "This is an example of the three base rules." -msgstr "" - -#: ../../configexamples/zone-policy.rst:272 617108f6e8a04def8d089d3373c5fdc4 -msgid "Here is an example of an IPv6 DMZ-WAN ruleset." -msgstr "" - -#: ../../configexamples/zone-policy.rst:345 a17a13e6dca3416fb9c3d5fa95aff51b -msgid "" -"Once you have all of your rulesets built, then you need to create your zone-" -"policy." -msgstr "" - -#: ../../configexamples/zone-policy.rst:348 2570cdfd598542d4ab4b7e38b8fb7d1e -msgid "Start by setting the interface and default action for each zone." -msgstr "" - -#: ../../configexamples/zone-policy.rst:355 ac4dd0fd6ee24b81a3d208db070b0029 -msgid "" -"In this case, we are setting the v6 ruleset that represents traffic sourced " -"from the LAN, destined for the DMZ. Because the zone-policy firewall syntax " -"is a little awkward, I keep it straight by thinking of it backwards." -msgstr "" - -#: ../../configexamples/zone-policy.rst:364 ded641d51758415e9f0cf27ae1e9b3c4 -msgid "" -"DMZ-LAN policy is LAN-DMZ. You can get a rhythm to it when you build out a " -"bunch at one time." -msgstr "" - -#: ../../configexamples/zone-policy.rst:367 f3adf536211a4f12817bf30695b1b65f -msgid "" -"In the end, you will end up with something like this config. I took out " -"everything but the Firewall, Interfaces, and zone-policy sections. It is " -"long enough as is." -msgstr "" - -#: ../../configexamples/zone-policy.rst:373 d4a2cf9526ec4602822a592145060277 -msgid "IPv6 Tunnel" -msgstr "" - -#: ../../configexamples/zone-policy.rst:375 44a092c185cb4956b7b4bec83f6da9b6 -msgid "" -"If you are using a IPv6 tunnel from HE.net or someone else, the basis is the" -" same except you have two WAN interfaces. One for v4 and one for v6." -msgstr "" - -#: ../../configexamples/zone-policy.rst:378 a9091d4fcd5b424088a2352f008d5947 -msgid "" -"You would have 5 zones instead of just 4 and you would configure your v6 " -"ruleset between your tunnel interface and your LAN/DMZ zones instead of to " -"the WAN." -msgstr "" - -#: ../../configexamples/zone-policy.rst:382 eb7fd578bb60426f8d96fd0016a0d005 -msgid "LAN, WAN, DMZ, local and TUN (tunnel)" -msgstr "" - -#: ../../configexamples/zone-policy.rst:384 c4c7ca9af6244fcf9b0b9ff4ad49cd10 -msgid "v6 pairs would be:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:401 28572036af8b4fd4b48436a393b06d90 -msgid "Notice, none go to WAN since WAN wouldn't have a v6 address on it." -msgstr "" - -#: ../../configexamples/zone-policy.rst:403 0c5f292540b24741a12114027008fe61 -msgid "" -"You would have to add a couple of rules on your wan-local ruleset to allow " -"protocol 41 in." -msgstr "" - -#: ../../configexamples/zone-policy.rst:406 36b65f4c07e644a7b2d18c4ca8639c83 -msgid "Something like:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/container/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/container/index.po deleted file mode 100644 index 62c1f1f4..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/container/index.po +++ /dev/null @@ -1,242 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/container/index.rst:5 039191360057464e976739d9e11140a7 -msgid "Container" -msgstr "" - -#: ../../configuration/container/index.rst:7 2adeecef2073485caa7ef731dbb1d908 -msgid "" -"The VyOS container implementation is based on `Podman<https://podman.io/>` " -"as a deamonless container engine." -msgstr "" - -#: ../../configuration/container/index.rst:12 f9eb9622fe284115804f9ad094eade74 -msgid "Configuration" -msgstr "" - -#: ../../configuration/container/index.rst:16 390adaa195084fa68cae2d52ff202ad7 -msgid "Sets the image name in the hub registry" -msgstr "" - -#: ../../configuration/container/index.rst:22 7196e6ef2f7a4a2ea97dd7ae1da5b649 -msgid "" -"If a registry is not specified, Docker.io will be used as the container " -"registry unless an alternative registry is specified using **set container " -"registry <name>** or the registry is included in the image name" -msgstr "" - -#: ../../configuration/container/index.rst:32 ac1d6dc699ee4f358bf2e07e812cd642 -msgid "" -"Allow host networking in a container. The network stack of the container is " -"not isolated from the host and will use the host IP." -msgstr "" - -#: ../../configuration/container/index.rst:35 980d056cd7e0458abe3286ffc8a64d27 -msgid "" -"The following commands translate to \"--net host\" when the container is " -"created" -msgstr "" - -#: ../../configuration/container/index.rst:38 97b53a0d18d34c6da2f1cdf99aeb89e6 -msgid "**allow-host-networks** cannot be used with **network**" -msgstr "" - -#: ../../configuration/container/index.rst:42 4fd9ffd52de941db9660bcb5f873f4a4 -msgid "" -"Attaches user-defined network to a container. Only one network must be " -"specified and must already exist." -msgstr "" - -#: ../../configuration/container/index.rst:47 bbfe5816cb1c48d88f6e3f56ed3364f4 -msgid "" -"Optionally set a specific static IPv4 or IPv6 address for the container. " -"This address must be within the named network prefix." -msgstr "" - -#: ../../configuration/container/index.rst:50 6816d1315c4241b49438860816340bcc -msgid "" -"The first IP in the container network is reserved by the engine and cannot " -"be used" -msgstr "" - -#: ../../configuration/container/index.rst:54 2720022ba5334a1f956445669de184ad -msgid "Set a container description" -msgstr "" - -#: ../../configuration/container/index.rst:58 c25b427ae981495d93759ad78e5582be -msgid "" -"Add custom environment variables. Multiple environment variables are " -"allowed. The following commands translate to \"-e key=value\" when the " -"container is created." -msgstr "" - -#: ../../configuration/container/index.rst:74 d329f77f29fa42a894b89f54f2ccda7c -msgid "Publish a port for the container." -msgstr "" - -#: ../../configuration/container/index.rst:85 dfc93c6334374953a75c7386a5a943bb -msgid "Mount a volume into the container" -msgstr "" - -#: ../../configuration/container/index.rst:94 6318eb3b475341418dd4c65c5d3c20f4 -msgid "Set the restart behavior of the container." -msgstr "" - -#: ../../configuration/container/index.rst:96 07c65a65f29645a9a0780d34ef675cb7 -msgid "**no**: Do not restart containers on exit" -msgstr "" - -#: ../../configuration/container/index.rst:97 b249af827afc4afc923cd011aaab9ed9 -msgid "" -"**on-failure**: Restart containers when they exit with a non-zero exit code," -" retrying indefinitely (default)" -msgstr "" - -#: ../../configuration/container/index.rst:98 9b0a646b45844cc5ae8d4c625596b4c4 -msgid "" -"**always**: Restart containers when they exit, regardless of status, " -"retrying indefinitely" -msgstr "" - -#: ../../configuration/container/index.rst:102 -#: d612314ec5cd44dd929dc534a648f847 -msgid "Constrain the memory available to the container." -msgstr "" - -#: ../../configuration/container/index.rst:104 -#: bc1ef74797fd4d528a29e534fa671fdf -msgid "Default is 512 MB. Use 0 MB for unlimited memory." -msgstr "" - -#: ../../configuration/container/index.rst:109 -#: 315b006060874c30bb96a7e10e7ed673 -msgid "Add a host device to the container." -msgstr "" - -#: ../../configuration/container/index.rst:113 -#: 68632205e8c14e2eb2e188544cc9cc1d -msgid "Set container capabilities or permissions." -msgstr "" - -#: ../../configuration/container/index.rst:115 -#: 4636681f9c7445f7a0234b1de814965f -msgid "" -"**net-admin**: Network operations (interface, firewall, routing tables)" -msgstr "" - -#: ../../configuration/container/index.rst:116 -#: 900bfc609b30441d952a332c2b40663e -msgid "" -"**net-bind-service**: Bind a socket to privileged ports (port numbers less " -"than 1024)" -msgstr "" - -#: ../../configuration/container/index.rst:117 -#: 54e552def9f14bc099a5d16c416c0ab2 -msgid "**net-raw**: Permission to create raw network sockets" -msgstr "" - -#: ../../configuration/container/index.rst:118 -#: a9b1dde39dde4cfdbcba244fea22ec14 -msgid "**setpcap**: Capability sets (from bounded or inherited set)" -msgstr "" - -#: ../../configuration/container/index.rst:119 -#: 16481be21dd94a39b62496569d592513 -msgid "" -"**sys-admin**: Administation operations (quotactl, mount, sethostname, " -"setdomainame)" -msgstr "" - -#: ../../configuration/container/index.rst:120 -#: 35d062351a9c4f458c94edeb90811e76 -msgid "**sys-time**: Permission to set system clock" -msgstr "" - -#: ../../configuration/container/index.rst:124 -#: 75cec34f8e2e4be1b12848644132cb12 -msgid "Disable a container." -msgstr "" - -#: ../../configuration/container/index.rst:128 -#: 59b8016c6dcf458e8e69abaed6bf76b7 -msgid "Creates a named container network" -msgstr "" - -#: ../../configuration/container/index.rst:132 -#: 5d93d01648af4dc99bf915f6f753c024 -msgid "" -"Adds registry to list of unqualified-search-registries. By default, for any " -"image that does not include the registry in the image name, Vyos will use " -"docker.io as the container registry." -msgstr "" - -#: ../../configuration/container/index.rst:139 -#: bf7c9cb9a093403aaf0ba43d3ad430b6 -msgid "Operation Commands" -msgstr "" - -#: ../../configuration/container/index.rst:143 -#: 3d2536dc92ba40f0baf7e8726d54160c -msgid "Pull a new image for container" -msgstr "" - -#: ../../configuration/container/index.rst:147 -#: d618ade17b804e44bbb2757823e436b7 -msgid "Show the list of all active containers." -msgstr "" - -#: ../../configuration/container/index.rst:151 -#: 5840b9c48a224101a8903db05b4e813f -msgid "Show the local container images." -msgstr "" - -#: ../../configuration/container/index.rst:155 -#: 17533e28c8c2408d9f2b2eb1a6005e47 -msgid "Show logs from a given container" -msgstr "" - -#: ../../configuration/container/index.rst:159 -#: a5c84a11b819436f845bf518ee80377f -msgid "Show a list available container networks" -msgstr "" - -#: ../../configuration/container/index.rst:163 -#: 9de0d2a828e04bf99ce8d3b8f05fd969 -msgid "Restart a given container" -msgstr "" - -#: ../../configuration/container/index.rst:167 -#: 53faa3642cfa4df5a91cbf68624159f8 -msgid "Update container image" -msgstr "" - -#: ../../configuration/container/index.rst:173 -#: b08858a996954ab9af8501e0779aa6cc -msgid "Example Configuration" -msgstr "" - -#: ../../configuration/container/index.rst:175 -#: adb87bc9114347ed9f9620182be87309 -msgid "" -"For the sake of demonstration, `example #1 in the official documentation " -"<https://www.zabbix.com/documentation/current/manual/installation/containers>`_" -" to the declarative VyOS CLI syntax." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/general.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/general.po deleted file mode 100644 index db74142d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/general.po +++ /dev/null @@ -1,703 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/firewall/general.rst:7 facda9eb148246a2846c50c633b112f9 -msgid "Firewall" -msgstr "" - -#: ../../configuration/firewall/general.rst:11 -#: aceb51461c424017811ef9c3ea4048f5 -msgid "Overview" -msgstr "" - -#: ../../configuration/firewall/general.rst:13 -#: ca220acdd7534a4e83ef13b14ae719ce -msgid "" -"VyOS makes use of Linux `netfilter <https://netfilter.org/>`_ for packet " -"filtering." -msgstr "" - -#: ../../configuration/firewall/general.rst:16 -#: 8d0be6e7960b49c6bf07b480d571be5d -msgid "" -"The firewall supports the creation of groups for ports, addresses, and " -"networks (implemented using netfilter ipset) and the option of interface or " -"zone based firewall policy." -msgstr "" - -#: ../../configuration/firewall/general.rst:20 -#: a15c763d1f6e46319f5f684a5f8713d6 -msgid "" -"**Important note on usage of terms:** The firewall makes use of the terms " -"`in`, `out`, and `local` for firewall policy. Users experienced with " -"netfilter often confuse `in` to be a reference to the `INPUT` chain, and " -"`out` the `OUTPUT` chain from netfilter. This is not the case. These instead" -" indicate the use of the `FORWARD` chain and either the input or output " -"interface. The `INPUT` chain, which is used for local traffic to the OS, is " -"a reference to as `local` with respect to its input interface." -msgstr "" - -#: ../../configuration/firewall/general.rst:32 -#: 298968df02e44fd09d9c3b204af151cc -msgid "Global settings" -msgstr "" - -#: ../../configuration/firewall/general.rst:34 -#: b5f6dfb8c8fe4b0baaf5790d838398eb -msgid "" -"Some firewall settings are global and have an affect on the whole system." -msgstr "" - -#: ../../configuration/firewall/general.rst:38 -#: 35b1850e49ef4d4bb6d587fcda347576 -msgid "" -"By default, when VyOS receives an ICMP echo request packet destined for " -"itself, it will answer with an ICMP echo reply, unless you avoid it through " -"its firewall." -msgstr "" - -#: ../../configuration/firewall/general.rst:42 -#: 0e87c692d83c48ec92ae6070ddf48ff8 -msgid "" -"With the firewall you can set rules to accept, drop or reject ICMP in, out " -"or local traffic. You can also use the general **firewall all-ping** " -"command. This command affects only to LOCAL (packets destined for your VyOS " -"system), not to IN or OUT traffic." -msgstr "" - -#: ../../configuration/firewall/general.rst:47 -#: 76673288caa94ded99da45cd22decf21 -msgid "" -"**firewall all-ping** affects only to LOCAL and it always behaves in the " -"most restrictive way" -msgstr "" - -#: ../../configuration/firewall/general.rst:54 -#: 8a184bad84f14f0eba6912256d9f94dd -msgid "" -"When the command above is set, VyOS will answer every ICMP echo request " -"addressed to itself, but that will only happen if no other rule is applied " -"dropping or rejecting local echo requests. In case of conflict, VyOS will " -"not answer ICMP echo requests." -msgstr "" - -#: ../../configuration/firewall/general.rst:63 -#: 628e4a7363f246988b1f8a0d1516ef46 -msgid "" -"When the command above is set, VyOS will answer no ICMP echo request " -"addressed to itself at all, no matter where it comes from or whether more " -"specific rules are being applied to accept them." -msgstr "" - -#: ../../configuration/firewall/general.rst:69 -#: d794be6514794b079a541d68fe0986e2 -msgid "" -"This setting enable or disable the response of icmp broadcast messages. The " -"following system parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:72 -#: abe9ce167df74de084ce9fb279ab694f -msgid "``net.ipv4.icmp_echo_ignore_broadcasts``" -msgstr "" - -#: ../../configuration/firewall/general.rst:77 -#: 3a6696ea227b491da06f8e42f4d33912 -msgid "" -"This setting handle if VyOS accept packets with a source route option. The " -"following system parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:80 -#: c39fbd4fbb8f4bcd96292cf321380077 -msgid "``net.ipv4.conf.all.accept_source_route``" -msgstr "" - -#: ../../configuration/firewall/general.rst:81 -#: bf4508a2f284414b816c07e50bd5cd94 -msgid "``net.ipv6.conf.all.accept_source_route``" -msgstr "" - -#: ../../configuration/firewall/general.rst:86 -#: b5afe069c3ff4b1fabb3dda8191dde3c -msgid "" -"enable or disable of ICMPv4 or ICMPv6 redirect messages accepted by VyOS. " -"The following system parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:89 -#: 21aa25c284bd4b6b9a1d6d6c8788d366 -msgid "``net.ipv4.conf.all.accept_redirects``" -msgstr "" - -#: ../../configuration/firewall/general.rst:90 -#: c814ace417b94a43a399195fdca0523a -msgid "``net.ipv6.conf.all.accept_redirects``" -msgstr "" - -#: ../../configuration/firewall/general.rst:94 -#: e45406d59c154498a13efdc0db18a6b9 -msgid "" -"enable or disable ICMPv4 redirect messages send by VyOS The following " -"system parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:97 -#: a36420053b9c44c4b54f6a729e7df994 -msgid "``net.ipv4.conf.all.send_redirects``" -msgstr "" - -#: ../../configuration/firewall/general.rst:101 -#: 0ecb9e02759749a8b99f3a85c8c2c6f7 -msgid "" -"enable or disable the logging of martian IPv4 packets. The following system " -"parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:104 -#: db95ca7571774c0cb4f969382d6aa03e -msgid "``net.ipv4.conf.all.log_martians``" -msgstr "" - -#: ../../configuration/firewall/general.rst:108 -#: cc79cd7b42b34bda9853eea2ca4e2e9e -msgid "" -"Set the IPv4 source validation mode. The following system parameter will be " -"altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:111 -#: bbbdbbf914be44648e2f6a934ca195b7 -msgid "``net.ipv4.conf.all.rp_filter``" -msgstr "" - -#: ../../configuration/firewall/general.rst:115 -#: 3188c681545246dbaf9c2066daa982ac -msgid "" -"Enable or Disable if VyOS use IPv4 TCP SYN Cookies. The following system " -"parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:118 -#: 735347352834482cace8aafee8fa444e -msgid "``net.ipv4.tcp_syncookies``" -msgstr "" - -#: ../../configuration/firewall/general.rst:122 -#: 8efed673f5664290b4229930a12b9ff8 -msgid "" -"Enable or Disable VyOS to be :rfc:`1337` conform. The following system " -"parameter will be altered:" -msgstr "" - -#: ../../configuration/firewall/general.rst:125 -#: fe6b1ca3e46e4d9ca143df6ab2a452ad -msgid "``net.ipv4.tcp_rfc1337``" -msgstr "" - -#: ../../configuration/firewall/general.rst:132 -#: 72af8d6f48aa4d14a8ee04617607ec80 -msgid "Set the global setting for an established connection." -msgstr "" - -#: ../../configuration/firewall/general.rst:138 -#: d2a0302b9c85484fabaa1f0cde5405e5 -msgid "Set the global setting for invalid packets." -msgstr "" - -#: ../../configuration/firewall/general.rst:144 -#: ae97bd44d2274ef0a30d56787251f49a -msgid "Set the global setting for related connections." -msgstr "" - -#: ../../configuration/firewall/general.rst:149 -#: a7e9b84524f644339caafb416bca1d47 -msgid "Groups" -msgstr "" - -#: ../../configuration/firewall/general.rst:151 -#: bc99d552d610455aab5eb6b4836740af -msgid "" -"Firewall groups represent collections of IP addresses, networks, or ports. " -"Once created, a group can be referenced by firewall rules as either a source" -" or destination. Members can be added or removed from a group without " -"changes to, or the need to reload, individual firewall rules." -msgstr "" - -#: ../../configuration/firewall/general.rst:157 -#: dd713103cf254ccb8dcffe2cbaaa7d57 -msgid "" -"Groups need to have unique names. Even though some contain IPv4 addresses " -"and others contain IPv6 addresses, they still need to have unique names, so " -"you may want to append \"-v4\" or \"-v6\" to your group names." -msgstr "" - -#: ../../configuration/firewall/general.rst:164 -#: 6265d626263442f7848b812a3765dd0f -msgid "Address Groups" -msgstr "" - -#: ../../configuration/firewall/general.rst:166 -#: f00e5e102aaa478ba25e6cbd5ce869a1 -msgid "" -"In an **address group** a single IP address or IP address ranges are " -"defined." -msgstr "" - -#: ../../configuration/firewall/general.rst:173 -#: 98947547bac64502994fa7d94fa5cc30 -msgid "Define a IPv4 or a IPv6 address group" -msgstr "" - -#: ../../configuration/firewall/general.rst:184 -#: 8f3dda4c071f44ec8de0a04166a5df4e -msgid "Provide a IPv4 or IPv6 address group description" -msgstr "" - -#: ../../configuration/firewall/general.rst:188 -#: a864cc2e72a644019ae7a8c7115569c0 -msgid "Network Groups" -msgstr "" - -#: ../../configuration/firewall/general.rst:190 -#: c86eacf4462b4530b70c206938b906dc -msgid "" -"While **network groups** accept IP networks in CIDR notation, specific IP " -"addresses can be added as a 32-bit prefix. If you foresee the need to add a " -"mix of addresses and networks, the network group is recommended." -msgstr "" - -#: ../../configuration/firewall/general.rst:198 -#: 34121fa5d124402b8f18899cec821a31 -msgid "Define a IPv4 or IPv6 Network group." -msgstr "" - -#: ../../configuration/firewall/general.rst:209 -#: 493d17c76a364daa877d8573a7a4f715 -msgid "Provide a IPv4 or IPv6 network group description." -msgstr "" - -#: ../../configuration/firewall/general.rst:213 -#: f6835c4043314465b684752615c3f00e -msgid "Port Groups" -msgstr "" - -#: ../../configuration/firewall/general.rst:215 -#: 96ecef3d7725410ea5132e9b2bf7a73d -msgid "" -"A **port group** represents only port numbers, not the protocol. Port groups" -" can be referenced for either TCP or UDP. It is recommended that TCP and UDP" -" groups are created separately to avoid accidentally filtering unnecessary " -"ports. Ranges of ports can be specified by using `-`." -msgstr "" - -#: ../../configuration/firewall/general.rst:224 -#: 63eaa704285c4f3b90f855084f507860 -msgid "" -"Define a port group. A port name can be any name defined in /etc/services. " -"e.g.: http" -msgstr "" - -#: ../../configuration/firewall/general.rst:235 -#: 26aada148f9f4a938f5f30b9c49f8c47 -msgid "Provide a port group description." -msgstr "" - -#: ../../configuration/firewall/general.rst:240 -#: 123938033ee0482ca04359691035f20c -msgid "Rule-Sets" -msgstr "" - -#: ../../configuration/firewall/general.rst:242 -#: 573e2361d6be443fa9b9b9ef1134653c -msgid "" -"A rule-set is a named collection of firewall rules that can be applied to an" -" interface or a zone. Each rule is numbered, has an action to apply if the " -"rule is matched, and the ability to specify the criteria to match. Data " -"packets go through the rules from 1 - 999999, at the first match the action " -"of the rule will be executed." -msgstr "" - -#: ../../configuration/firewall/general.rst:251 -#: 0bdc6e4fb0f54cdc9569e4da34ad48cc -msgid "Provide a rule-set description." -msgstr "" - -#: ../../configuration/firewall/general.rst:257 -#: ddd70472446348c7a8fd28cd7166c77b -msgid "" -"This set the default action of the rule-set if no rule matched a packet " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:263 -#: d5e1808f6f2a4a1db69cf784e93d7fc3 -msgid "Use this command to enable the logging of the default action." -msgstr "" - -#: ../../configuration/firewall/general.rst:270 -#: b0397e84921f4a6aa7fc63b293138faf -msgid "This required setting defines the action of the current rule." -msgstr "" - -#: ../../configuration/firewall/general.rst:275 -#: 2776dbf09b174d7fabfd98be4df00e60 -msgid "Provide a description for each rule." -msgstr "" - -#: ../../configuration/firewall/general.rst:281 -#: 29b80b71d6a64be08d7b6df16ec342bb -msgid "Enable or disable logging for the matched packet." -msgstr "" - -#: ../../configuration/firewall/general.rst:288 -#: 9dcfd8dc1e484f6b901aee3f189f9acb -msgid "Define log-level. Only applicable if rule log is enable." -msgstr "" - -#: ../../configuration/firewall/general.rst:293 -#: 6a350042b33a416a990ed5c6a0706952 -msgid "If you want to disable a rule but let it in the configuration." -msgstr "" - -#: ../../configuration/firewall/general.rst:296 -#: 2b58304d911642fdbde93cbf19aa4119 -msgid "Matching criteria" -msgstr "" - -#: ../../configuration/firewall/general.rst:298 -#: 0de1da37a0f14a22b37fcebc07d88607 -msgid "" -"There are a lot of matching criteria against which the package can be " -"tested." -msgstr "" - -#: ../../configuration/firewall/general.rst:305 -#: 8e9386bd9d5245f6895aad11486bbfb1 -msgid "Match criteria based on nat connection status." -msgstr "" - -#: ../../configuration/firewall/general.rst:316 -#: 444c3ff082e04598b27d9466e62a4d2e -msgid "" -"This is similar to the network groups part, but here you are able to negate " -"the matching addresses." -msgstr "" - -#: ../../configuration/firewall/general.rst:342 -#: 9641ccf10ee64769a8ea9dd6b4f3c63b -msgid "" -"Match IP addresses based on its geolocation. More info: `geoip matching " -"<https://wiki.nftables.org/wiki-nftables/index.php/GeoIP_matching>`_." -msgstr "" - -#: ../../configuration/firewall/general.rst:346 -#: a2681cdb81194806ac5dda4e311574d8 -msgid "Use inverse-match to match anything except the given country-codes." -msgstr "" - -#: ../../configuration/firewall/general.rst:348 -#: 0f888cea51f94d15bfc01fd41bd8388e -msgid "" -"Data is provided by DB-IP.com under CC-BY-4.0 license. Attribution required," -" permits redistribution so we can include a database in images(~3MB " -"compressed). Includes cron script (manually callable by op-mode update " -"geoip) to keep database and rules updated." -msgstr "" - -#: ../../configuration/firewall/general.rst:358 -#: cbd5e1eea66547d996d118aca4b351e1 -msgid "Only in the source criteria, you can specify a mac-address." -msgstr "" - -#: ../../configuration/firewall/general.rst:374 -#: 4bc70e0727e44362b2b5dbb88b85b850 -msgid "" -"A port can be set with a port number or a name which is here defined: " -"``/etc/services``." -msgstr "" - -#: ../../configuration/firewall/general.rst:383 -#: a8f2c47ad17d47cd881715958dc77ab3 -msgid "" -"Multiple source ports can be specified as a comma-separated list. The whole " -"list can also be \"negated\" using '!'. For example:" -msgstr "" - -#: ../../configuration/firewall/general.rst:399 -#: 53d8497a74db4f6faadad9b2e629a0a5 -msgid "" -"Use a specific address-group. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:411 -#: 622b2b59cf64487782287392cff6baca -msgid "" -"Use a specific network-group. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:423 -#: 2b958fd6bd5a49a282cd63a0e02938bd -msgid "" -"Use a specific port-group. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:435 -#: a7b1012b364d453bb4aeddbd76a67144 -msgid "" -"Use a specific domain-group. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:447 -#: 5600afb8b39648a7bf4ffbdb058408e9 -msgid "" -"Use a specific mac-group. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:455 -#: 982f10bd288a4508a2d3aa5af778bc8e -msgid "Match based on fragment criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:462 -#: d782cd89fcf54acfb8e171306cc308ad -msgid "Match based on icmp|icmpv6 code and type." -msgstr "" - -#: ../../configuration/firewall/general.rst:468 -#: 4c36fbfb88fe4d1eb3e4cb2597e6da90 -msgid "" -"Match based on icmp|icmpv6 type-name criteria. Use tab for information about" -" what **type-name** criteria are supported." -msgstr "" - -#: ../../configuration/firewall/general.rst:476 -#: 241005b1326f4c9bba2d2dd707495aab -msgid "Match based on ipsec criteria." -msgstr "" - -#: ../../configuration/firewall/general.rst:483 -#: 8c27b7eaf6154f03ad9a4ccfd62b7c8c -msgid "" -"Match based on the maximum number of packets to allow in excess of rate." -msgstr "" - -#: ../../configuration/firewall/general.rst:490 -#: 8d69de7f11ec4e8a92fec23e89e83fd5 -msgid "" -"Match based on the maximum average rate, specified as **integer/unit**. For " -"example **5/minutes**" -msgstr "" - -#: ../../configuration/firewall/general.rst:502 -#: bbb0d89917294eb09ef6a46cb0ca8074 -msgid "" -"Match based on packet length criteria. Multiple values from 1 to 65535 and " -"ranges are supported." -msgstr "" - -#: ../../configuration/firewall/general.rst:510 -#: 31e6f9370baf4ba0b249cb334bdb0d25 -msgid "" -"Match a protocol criteria. A protocol number or a name which is here " -"defined: ``/etc/protocols``. Special names are ``all`` for all protocols and" -" ``tcp_udp`` for tcp and udp based packets. The ``!`` negate the selected " -"protocol." -msgstr "" - -#: ../../configuration/firewall/general.rst:528 -#: 16fd1e887fd6420b9de1317ca2588722 -msgid "Match bases on recently seen sources." -msgstr "" - -#: ../../configuration/firewall/general.rst:533 -#: 43e403011b5c4119a3ff6a1f9bdeac5a -msgid "" -"Allowed values fpr TCP flags: ``SYN``, ``ACK``, ``FIN``, ``RST``, ``URG``, " -"``PSH``, ``ALL`` When specifying more than one flag, flags should be comma " -"separated. The ``!`` negate the selected protocol." -msgstr "" - -#: ../../configuration/firewall/general.rst:548 -#: 73c574adcac14c45b9f02aa1182c5f33 -msgid "Match against the state of a packet." -msgstr "" - -#: ../../configuration/firewall/general.rst:561 -#: 962efaa3df214ee9ad60d44f42b806ce -msgid "Time to match the defined rule." -msgstr "" - -#: ../../configuration/firewall/general.rst:565 -#: 7e03a09636ee46ad9a9b0cbb8870b7b0 -msgid "" -"Match time to live parameter, where 'eq' stands for 'equal'; 'gt' stands for" -" 'greater than', and 'lt' stands for 'less than'." -msgstr "" - -#: ../../configuration/firewall/general.rst:571 -#: a95df0ad07844417920d2d8b76667e80 -msgid "" -"Match hop-limit parameter, where 'eq' stands for 'equal'; 'gt' stands for " -"'greater than', and 'lt' stands for 'less than'." -msgstr "" - -#: ../../configuration/firewall/general.rst:581 -#: 6f7029a7ec47442fa643950ec6abc017 -msgid "" -"Match when 'count' amount of connections are seen within 'time'. These " -"matching criteria can be used to block brute-force attempts." -msgstr "" - -#: ../../configuration/firewall/general.rst:586 -#: df75fba3d7b247a99ccc3f46392e0092 -msgid "Applying a Rule-Set to an Interface" -msgstr "" - -#: ../../configuration/firewall/general.rst:588 -#: dcf78ea0ed0949cb80f5244d09d25eb4 -msgid "A Rule-Set can be applied to every interface:" -msgstr "" - -#: ../../configuration/firewall/general.rst:590 -#: ad45626da9714083b35cc8d80c737990 -msgid "``in``: Ruleset for forwarded packets on an inbound interface" -msgstr "" - -#: ../../configuration/firewall/general.rst:591 -#: 66b0977f8c2649618fd2e1436b6519db -msgid "``out``: Ruleset for forwarded packets on an outbound interface" -msgstr "" - -#: ../../configuration/firewall/general.rst:592 -#: 6ad207f09245467d9cc9b2cc31a3e700 -msgid "``local``: Ruleset for packets destined for this router" -msgstr "" - -#: ../../configuration/firewall/general.rst:598 -#: 5a943940b6374473a10f0cf1f197aac4 -msgid "Here are some examples for applying a rule-set to an interface" -msgstr "" - -#: ../../configuration/firewall/general.rst:608 -#: 7fa4610e2fad4d3fa60821ff2e70ad18 -msgid "" -"As you can see in the example here, you can assign the same rule-set to " -"several interfaces. An interface can only have one rule-set per chain." -msgstr "" - -#: ../../configuration/firewall/general.rst:613 -#: 7c13e8863c38495abd4f8007838b76c0 -msgid "Operation-mode Firewall" -msgstr "" - -#: ../../configuration/firewall/general.rst:616 -#: 561e72c9e2b643be8e8554f61eeb0ea7 -msgid "Rule-set overview" -msgstr "" - -#: ../../configuration/firewall/general.rst:620 -#: 2263ec044f8a4a06bff2947cacc36c0d -msgid "This will show you a basic firewall overview" -msgstr "" - -#: ../../configuration/firewall/general.rst:686 -#: ac5a8cd3bbf44d6bb76bc578352a48fd -msgid "This will show you a summary of rule-sets and groups" -msgstr "" - -#: ../../configuration/firewall/general.rst:735 -#: dfb494ea440449f8adfba984fd4f4bb6 -msgid "This will show you a statistic of all rule-sets since the last boot." -msgstr "" - -#: ../../configuration/firewall/general.rst:739 -#: 7565359384b3452da861ae9152f3d4eb -msgid "This command will give an overview of a rule in a single rule-set" -msgstr "" - -#: ../../configuration/firewall/general.rst:743 -#: fb9f15ae8f9e4c8f8cb68bdeef942141 -msgid "" -"Overview of defined groups. You see the type, the members, and where the " -"group is used." -msgstr "" - -#: ../../configuration/firewall/general.rst:767 -#: d0668ab595134a74a7044c97f56de8c2 -msgid "This command will give an overview of a single rule-set." -msgstr "" - -#: ../../configuration/firewall/general.rst:771 -#: aa9896f9c09e4e92ae4797c245bdf2b3 -msgid "This will show you a rule-set statistic since the last boot." -msgstr "" - -#: ../../configuration/firewall/general.rst:775 -#: 3ad4f2e340244329a0b6874a4fe94b32 -msgid "This command will give an overview of a rule in a single rule-set." -msgstr "" - -#: ../../configuration/firewall/general.rst:779 -#: 365492b986654422a24c09b6da767f30 -msgid "Zone-Policy Overview" -msgstr "" - -#: ../../configuration/firewall/general.rst:783 -#: f2e84b43686a497bb9b1c21a3b14d472 -msgid "Use this command to get an overview of a zone." -msgstr "" - -#: ../../configuration/firewall/general.rst:800 -#: 9cab45c84f154c46a6c4902f96b8bd28 -msgid "Show Firewall log" -msgstr "" - -#: ../../configuration/firewall/general.rst:804 -#: 20309ec504fa4730a68e27d18ec18831 -msgid "Show the logs of a specific Rule-Set." -msgstr "" - -#: ../../configuration/firewall/general.rst:807 -#: 2682d60a4cf041eabc29452db7c982c0 -msgid "" -"At the moment it not possible to look at the whole firewall log with VyOS " -"operational commands. All logs will save to ``/var/logs/messages``. For " -"example: ``grep '10.10.0.10' /var/log/messages``" -msgstr "" - -#: ../../configuration/firewall/general.rst:814 -#: 30acfdb389ca4dc1a7591daa6378cfda -msgid "Example Partial Config" -msgstr "" - -#: ../../configuration/firewall/general.rst:885 -#: a1a7b42d8cbd4b608237d2622c4e8c99 -msgid "Update geoip database" -msgstr "" - -#: ../../configuration/firewall/general.rst:889 -#: 44b5c290f6ec4cb5aa3a9360d648da79 -msgid "Command used to update GeoIP database and firewall sets." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/index.po deleted file mode 100644 index d8e12dc3..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/firewall/index.rst:3 83da7a4aa24d433bb28aa381e98308e0 -msgid "Firewall" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/zone.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/zone.po deleted file mode 100644 index 6d688598..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/firewall/zone.po +++ /dev/null @@ -1,137 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/firewall/zone.rst:7 5d28a2195d14466baed1010a0a168f55 -msgid "Zone Based Firewall" -msgstr "" - -#: ../../configuration/firewall/zone.rst:9 b2437dbbf0fb48408613fe98c6a2832d -msgid "" -"In zone-based policy, interfaces are assigned to zones, and inspection " -"policy is applied to traffic moving between the zones and acted on according" -" to firewall rules. A Zone is a group of interfaces that have similar " -"functions or features. It establishes the security borders of a network. A " -"zone defines a boundary where traffic is subjected to policy restrictions as" -" it crosses to another region of a network." -msgstr "" - -#: ../../configuration/firewall/zone.rst:16 3ce50b7a632d4644aeca6f3dd6669d2f -msgid "Key Points:" -msgstr "" - -#: ../../configuration/firewall/zone.rst:18 c6a82db982e4460d89e0327e7638c991 -msgid "" -"A zone must be configured before an interface is assigned to it and an " -"interface can be assigned to only a single zone." -msgstr "" - -#: ../../configuration/firewall/zone.rst:20 f278728404e24c00b87a4316efcc3bc7 -msgid "All traffic to and from an interface within a zone is permitted." -msgstr "" - -#: ../../configuration/firewall/zone.rst:21 3250a916b149435da22a5da5c8348d1b -msgid "All traffic between zones is affected by existing policies" -msgstr "" - -#: ../../configuration/firewall/zone.rst:22 3a4e10156f8b40d6aa04d9de0359dd51 -msgid "" -"Traffic cannot flow between zone member interface and any interface that is " -"not a zone member." -msgstr "" - -#: ../../configuration/firewall/zone.rst:24 6bf7b896b0ce4f32be0df6d583e216d5 -msgid "" -"You need 2 separate firewalls to define traffic: one for each direction." -msgstr "" - -#: ../../configuration/firewall/zone.rst:26 60d79f43c53d412199a05a4a7df7599c -msgid "" -"In :vytask:`T2199` the syntax of the zone configuration was changed. The " -"zone configuration moved from ``zone-policy zone <name>`` to ``firewall zone" -" <name>``." -msgstr "" - -#: ../../configuration/firewall/zone.rst:32 dcb705c4a157435e9a5a284250fc6d53 -msgid "Configuration" -msgstr "" - -#: ../../configuration/firewall/zone.rst:34 67d48c8cf5b94192a1f0d5f632a7c7b8 -msgid "" -"As an alternative to applying policy to an interface directly, a zone-based " -"firewall can be created to simplify configuration when multiple interfaces " -"belong to the same security zone. Instead of applying rule-sets to " -"interfaces, they are applied to source zone-destination zone pairs." -msgstr "" - -#: ../../configuration/firewall/zone.rst:39 041eb6555f584b6dadfb1829286ac3e4 -msgid "" -"An basic introduction to zone-based firewalls can be found `here " -"<https://support.vyos.io/en/kb/articles/a-primer-to-zone-based-firewall>`_, " -"and an example at :ref:`examples-zone-policy`." -msgstr "" - -#: ../../configuration/firewall/zone.rst:44 a8184b0664a44b21bae1a29e218e3778 -msgid "Define a Zone" -msgstr "" - -#: ../../configuration/firewall/zone.rst:46 b670d82911e546da85e9ffce53a07e3c -msgid "To define a zone setup either one with interfaces or a local zone." -msgstr "" - -#: ../../configuration/firewall/zone.rst:50 be3602e936ca413db078eb0a5e9158ad -msgid "" -"Set interfaces to a zone. A zone can have multiple interfaces. But an " -"interface can only be a member in one zone." -msgstr "" - -#: ../../configuration/firewall/zone.rst:55 1f12fe538ab5463781231da8e7e156ae -msgid "" -"Define the zone as a local zone. A local zone has no interfaces and will be " -"applied to the router itself." -msgstr "" - -#: ../../configuration/firewall/zone.rst:60 07aa100c1d8a41eab684f1ac8a662b15 -msgid "Change the default-action with this setting." -msgstr "" - -#: ../../configuration/firewall/zone.rst:64 d1b1278ff64a4c40be25e661d0e4a8a0 -msgid "Set a meaningful description." -msgstr "" - -#: ../../configuration/firewall/zone.rst:67 6b49f9abba254393a18d78dac2eb1f2d -msgid "Applying a Rule-Set to a Zone" -msgstr "" - -#: ../../configuration/firewall/zone.rst:69 c2f1603c68894d989b0eca018fc7bf33 -msgid "" -"Before you are able to apply a rule-set to a zone you have to create the " -"zones first." -msgstr "" - -#: ../../configuration/firewall/zone.rst:72 530102046b7a49c1a53bc8f6e93a5508 -msgid "" -"It helps to think of the syntax as: (see below). The 'rule-set' should be " -"written from the perspective of: *Source Zone*-to->*Destination Zone*" -msgstr "" - -#: ../../configuration/firewall/zone.rst:84 fa380c6499fc44f586738b5ba60f0786 -msgid "" -"You apply a rule-set always to a zone from an other zone, it is recommended " -"to create one rule-set for each zone pair." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/highavailability/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/highavailability/index.po deleted file mode 100644 index 298af9ca..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/highavailability/index.po +++ /dev/null @@ -1,423 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/highavailability/index.rst:6 -#: e7d0067351e5444ca36c8cb4d93c5af9 -msgid "High availability" -msgstr "" - -#: ../../configuration/highavailability/index.rst:8 -#: fee9f33470d64631bc8e70e402dbfe36 -msgid "" -"VRRP (Virtual Router Redundancy Protocol) provides active/backup redundancy " -"for routers. Every VRRP router has a physical IP/IPv6 address, and a virtual" -" address. On startup, routers elect the master, and the router with the " -"highest priority becomes the master and assigns the virtual address to its " -"interface. All routers with lower priorities become backup routers. The " -"master then starts sending keepalive packets to notify other routers that " -"it's available. If the master fails and stops sending keepalive packets, the" -" router with the next highest priority becomes the new master and takes over" -" the virtual address." -msgstr "" - -#: ../../configuration/highavailability/index.rst:17 -#: 25a3e62efb7c4d2183b983047c244baa -msgid "" -"VRRP keepalive packets use multicast, and VRRP setups are limited to a " -"single datalink layer segment. You can setup multiple VRRP groups (also " -"called virtual routers). Virtual routers are identified by a VRID (Virtual " -"Router IDentifier). If you setup multiple groups on the same interface, " -"their VRIDs must be unique if they use the same address family, but it's " -"possible (even if not recommended for readability reasons) to use duplicate " -"VRIDs on different interfaces." -msgstr "" - -#: ../../configuration/highavailability/index.rst:26 -#: 50e07d38d6674c60bfc4d8afce18e577 -msgid "Basic setup" -msgstr "" - -#: ../../configuration/highavailability/index.rst:28 -#: bcccc3691f5b49a3acf383f0c3378d1b -msgid "" -"VRRP groups are created with the ``set high-availability vrrp group " -"$GROUP_NAME`` commands. The required parameters are interface, vrid, and " -"address." -msgstr "" - -#: ../../configuration/highavailability/index.rst:32 -#: dbb9b6dd1a6d4235ad7fc110fb6e49f2 -msgid "minimal config" -msgstr "" - -#: ../../configuration/highavailability/index.rst:40 -#: 92dfa1aaaa8142208503b6f301266196 -msgid "" -"You can verify your VRRP group status with the operational mode ``run show " -"vrrp`` command:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:51 -#: 017b3a53fe81487ebe2dc8259ff7f4d2 -msgid "IPv6 support" -msgstr "" - -#: ../../configuration/highavailability/index.rst:53 -#: 36bcb7945b3a4bd6915096bb3147bff3 -msgid "" -"The ``address`` parameter can be either an IPv4 or IPv6 address, but you can" -" not mix IPv4 and IPv6 in the same group, and will need to create groups " -"with different VRIDs specially for IPv4 and IPv6. If you want to use IPv4 + " -"IPv6 address you can use option ``excluded-address``" -msgstr "" - -#: ../../configuration/highavailability/index.rst:59 -#: 44bb40746b9d4d8fb2fd126ed64cce44 -msgid "Address" -msgstr "" - -#: ../../configuration/highavailability/index.rst:60 -#: 35c31ebae84a417f8703e10a214721f5 -msgid "" -"The ``address`` can be configured either on the VRRP interface or on not " -"VRRP interface." -msgstr "" - -#: ../../configuration/highavailability/index.rst:70 -#: 476c3ac4b65646cf8d5e725c978fc0e8 -msgid "Disabling a VRRP group" -msgstr "" - -#: ../../configuration/highavailability/index.rst:72 -#: 54daaf1c6d0b442898fdb59362e44ed6 -msgid "You can disable a VRRP group with ``disable`` option:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:78 -#: 12373c26525c47faab9e90599a8fcc14 -msgid "" -"A disabled group will be removed from the VRRP process and your router will " -"not participate in VRRP for that VRID. It will disappear from operational " -"mode commands output, rather than enter the backup state." -msgstr "" - -#: ../../configuration/highavailability/index.rst:83 -#: b82e411c327644279cd48efbd5a70bdb -msgid "Exclude address" -msgstr "" - -#: ../../configuration/highavailability/index.rst:85 -#: 819ce5a5641945a797a4ddc43a813e2c -msgid "" -"Exclude IP addresses from ``VRRP packets``. This option ``excluded-address``" -" is used when you want to set IPv4 + IPv6 addresses on the same virtual " -"interface or when used more than 20 IP addresses." -msgstr "" - -#: ../../configuration/highavailability/index.rst:96 -#: c4a6f6333ae64f5ca601b3549e7bc407 -msgid "Setting VRRP group priority" -msgstr "" - -#: ../../configuration/highavailability/index.rst:98 -#: 95b3436ef1f24d21abd13275933a2224 -msgid "VRRP priority can be set with ``priority`` option:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:104 -#: 765d297e220b41e2bedd1df69a1d379f -msgid "" -"The priority must be an integer number from 1 to 255. Higher priority value " -"increases router's precedence in the master elections." -msgstr "" - -#: ../../configuration/highavailability/index.rst:108 -#: fe4a11d3fdbf46e5a2e5f4f389d7bd28 -msgid "Sync groups" -msgstr "" - -#: ../../configuration/highavailability/index.rst:110 -#: 9f19a839f9c84fbba9c2318dd41e3f8b -msgid "A sync group allows VRRP groups to transition together." -msgstr "" - -#: ../../configuration/highavailability/index.rst:118 -#: a7e01366f1c14a5a861873456eda1b59 -msgid "" -"In the following example, when VLAN9 transitions, VLAN20 will also " -"transition:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:142 -#: fdd8c618b0fa4d12a948061883f450ac -msgid "" -"All items in a sync group should be similarly configured. If one VRRP group " -"is set to a different preemption delay or priority, it would result in an " -"endless transition loop." -msgstr "" - -#: ../../configuration/highavailability/index.rst:148 -#: ab27c891a1f6448ea2df6cb6d3df34b1 -msgid "Preemption" -msgstr "" - -#: ../../configuration/highavailability/index.rst:150 -#: 6a37e5389a064e748629b73dec803da4 -msgid "" -"VRRP can use two modes: preemptive and non-preemptive. In the preemptive " -"mode, if a router with a higher priority fails and then comes back, routers " -"with lower priority will give up their master status. In non-preemptive " -"mode, the newly elected master will keep the master status and the virtual " -"address indefinitely." -msgstr "" - -#: ../../configuration/highavailability/index.rst:155 -#: b7bb9c1034a444a5956033355527158e -msgid "" -"By default VRRP uses preemption. You can disable it with the \"no-preempt\" " -"option:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:162 -#: d0e96e3976a94e7d89cd3fd1e3dec53f -msgid "" -"You can also configure the time interval for preemption with the \"preempt-" -"delay\" option. For example, to set the higher priority router to take over " -"in 180 seconds, use:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:171 -#: 49fe606e3aa84de4a52c96006a543d55 -msgid "Track" -msgstr "" - -#: ../../configuration/highavailability/index.rst:173 -#: ed3d8925bc214126bd79ea2546fe5e65 -msgid "" -"Track option to track non VRRP interface states. VRRP changes status to " -"``FAULT`` if one of the track interfaces in state ``down``." -msgstr "" - -#: ../../configuration/highavailability/index.rst:181 -#: 56ecfbe000a1440da35b09aeec7d2c12 -msgid "Ignore VRRP main interface faults" -msgstr "" - -#: ../../configuration/highavailability/index.rst:188 -#: a8d83d134f684d2783d8edbb8b544a60 -msgid "Unicast VRRP" -msgstr "" - -#: ../../configuration/highavailability/index.rst:190 -#: 2c4a6cc88ea7489b94a8de86f6931799 -msgid "" -"By default VRRP uses multicast packets. If your network does not support " -"multicast for whatever reason, you can make VRRP use unicast communication " -"instead." -msgstr "" - -#: ../../configuration/highavailability/index.rst:200 -#: 52449fa8f2ab4390a89a9e18401cabcb -msgid "rfc3768-compatibility" -msgstr "" - -#: ../../configuration/highavailability/index.rst:202 -#: 2c4ff3cabdde4c89ac827d7870a88a38 -msgid "" -"RFC 3768 defines a virtual MAC address to each VRRP virtual router. This " -"virtual router MAC address will be used as the source in all periodic VRRP " -"messages sent by the active node. When the rfc3768-compatibility option is " -"set, a new VRRP interface is created, to which the MAC address and the " -"virtual IP address is automatically assigned." -msgstr "" - -#: ../../configuration/highavailability/index.rst:212 -#: 8ec5cf8bd8ee4af2b3c5e9c34ad72d2a -msgid "Verification" -msgstr "" - -#: ../../configuration/highavailability/index.rst:224 -#: cb133a4a167f4939a19cf39c6dcb430b -msgid "Scripting" -msgstr "" - -#: ../../configuration/highavailability/index.rst:226 -#: 8891db909c754134b972d1b43111e2f8 -msgid "" -"VRRP functionality can be extended with scripts. VyOS supports two kinds of " -"scripts: health check scripts and transition scripts. Health check scripts " -"execute custom checks in addition to the master router reachability. " -"Transition scripts are executed when VRRP state changes from master to " -"backup or fault and vice versa and can be used to enable or disable certain " -"services, for example." -msgstr "" - -#: ../../configuration/highavailability/index.rst:233 -#: 1b16230ec9dd4b17b36e4e54f77e7320 -msgid "Health check scripts" -msgstr "" - -#: ../../configuration/highavailability/index.rst:235 -#: b21c8fbc7a644edbbf03c53b4a8d0af0 -msgid "" -"This setup will make the VRRP process execute the ``/config/scripts/vrrp-" -"check.sh script`` every 60 seconds, and transition the group to the fault " -"state if it fails (i.e. exits with non-zero status) three times:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:247 -#: 187a8c6f9d84432ebb272eab2ca267b4 -msgid "Transition scripts" -msgstr "" - -#: ../../configuration/highavailability/index.rst:249 -#: c2516ea16d1e4ab28d54feff178a1c9e -msgid "" -"Transition scripts can help you implement various fixups, such as starting " -"and stopping services, or even modifying the VyOS config on VRRP transition." -" This setup will make the VRRP process execute the ``/config/scripts/vrrp-" -"fail.sh`` with argument ``Foo`` when VRRP fails, and the " -"``/config/scripts/vrrp-master.sh`` when the router becomes the master:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:261 -#: 4e011f89b21d4a0e9620cad9c40917cb -msgid "" -"To know more about scripting, check the :ref:`command-scripting` section." -msgstr "" - -#: ../../configuration/highavailability/index.rst:264 -#: 08f7855239604db8b1f19272c6775811 -msgid "Virtual-server" -msgstr "" - -#: ../../_include/need_improvement.txt:11 c945c68683964cb98e4925c4d9d7c722 -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 0cc892ecba514bbb91d33ffea746268c -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/highavailability/index.rst:267 -#: 5f47de8f78064bebae45e0b39db5512e -msgid "" -"Virtual Server allows to Load-balance traffic destination virtual-" -"address:port between several real servers." -msgstr "" - -#: ../../configuration/highavailability/index.rst:271 -#: 28705ad5afd34698b67f0973c60741d0 -msgid "Algorithm" -msgstr "" - -#: ../../configuration/highavailability/index.rst:272 -#: af6c518e0f944e45bab41e7214045c83 -msgid "Load-balancing schedule algorithm:" -msgstr "" - -#: ../../configuration/highavailability/index.rst:274 -#: 23d7ad76dbfc473e80ef1cc50955bcf8 -msgid "round-robin" -msgstr "" - -#: ../../configuration/highavailability/index.rst:275 -#: 4e346244fd4a4f6a8d8dabce29c927bb -msgid "weighted-round-robin" -msgstr "" - -#: ../../configuration/highavailability/index.rst:276 -#: 232c91c0283e4e12a88438382a30a995 -msgid "least-connection" -msgstr "" - -#: ../../configuration/highavailability/index.rst:277 -#: 2f5a374ab4cf45059a2f5a83e9fa59fa -msgid "weighted-least-connection" -msgstr "" - -#: ../../configuration/highavailability/index.rst:278 -#: c9024d7dc4e9428387069b7d398fb8c0 -msgid "source-hashing" -msgstr "" - -#: ../../configuration/highavailability/index.rst:279 -#: aa052642dff74d0abcfdd761b1994f7e -msgid "destination-hashing" -msgstr "" - -#: ../../configuration/highavailability/index.rst:280 -#: f6c4fbbe8745473d9d08729f77c60b58 -msgid "locality-based-least-connection" -msgstr "" - -#: ../../configuration/highavailability/index.rst:287 -#: 64ea694d5b9942d9915efb108850b6f1 -msgid "Forward method" -msgstr "" - -#: ../../configuration/highavailability/index.rst:288 -#: 5a9334aad7df44c6aab7219fb87d8b6d -msgid "NAT" -msgstr "" - -#: ../../configuration/highavailability/index.rst:289 -#: 53cf91eddb564854a44a0b4b97c4302e -msgid "direct" -msgstr "" - -#: ../../configuration/highavailability/index.rst:290 -#: 9fe0a2533e6846d8b10795af938dfb5e -msgid "tunnel" -msgstr "" - -#: ../../configuration/highavailability/index.rst:298 -#: b239f52802a940bf9bcfeb06f95e0ce7 -msgid "Real server" -msgstr "" - -#: ../../configuration/highavailability/index.rst:299 -#: f743bcaf5d254b53814b81b02a9c313c -msgid "Real server IP address and port" -msgstr "" - -#: ../../configuration/highavailability/index.rst:307 -#: 1f0f3fabb3cb420195438fc6a358aad4 -msgid "Example" -msgstr "" - -#: ../../configuration/highavailability/index.rst:308 -#: cfe751288bbf4d7bb235ceff4a52dc0e -msgid "" -"Virtual-server can be configured with VRRP virtual address or without VRRP." -msgstr "" - -#: ../../configuration/highavailability/index.rst:310 -#: 3e1ddf07fc1c4e26bdc35f56a086fcf5 -msgid "" -"In the next example all traffic destined to ``203.0.113.1`` and port " -"``8280`` protocol TCP is balanced between 2 real servers ``192.0.2.11`` and " -"``192.0.2.12`` to port ``80``" -msgstr "" - -#: ../../configuration/highavailability/index.rst:314 -#: 7c81fb7780c546b392f62a9add692246 -msgid "Real server is auto-excluded if port check with this server fail." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/index.po deleted file mode 100644 index 9cd739c9..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/index.po +++ /dev/null @@ -1,26 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/index.rst:3 9b38201e769b4a2b948f146166059dab -msgid "Configuration Guide" -msgstr "" - -#: ../../configuration/index.rst:5 532e00ffea094ea8ab1bfadcbffefafe -msgid "The following structure respresent the cli structure." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bonding.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bonding.po deleted file mode 100644 index 21b04313..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bonding.po +++ /dev/null @@ -1,1375 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/bonding.rst:7 -#: 76c30b2032ea44f6a647524d3489445f -msgid "Bond / Link Aggregation" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:9 -#: 08a3246e05c849af9e2e01977f95a843 -msgid "" -"The bonding interface provides a method for aggregating multiple network " -"interfaces into a single logical \"bonded\" interface, or LAG, or ether-" -"channel, or port-channel. The behavior of the bonded interfaces depends upon" -" the mode; generally speaking, modes provide either hot standby or load " -"balancing services. Additionally, link integrity monitoring may be " -"performed." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:17 -#: 46ebcd7baaa147babb4e040dbe2e9a8d -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:20 -#: bac17b22fc7a4fb1a6d175169591d363 -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: b47532a855a8467a9a59cef58410bea0 b6738fd2f9dd41a1920076163ebc93a5 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: a2058e4e630d4e1a9671468f1b17bf05 e1d4e4bb3abd4a12bd0e8b4eb2303faf -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: 41d2d53e76da4cc88a828734e031c5f1 60c5a7930f8841429b45c104ff0fa1db -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: 2aa77ef855f840beae04b509f1d83527 b44a9b1f512b4a76bd501d75f0769848 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-xdp.txt:28 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: 05be1096c9114ad1a1dbb7fef87007d0 65014601dc8142fe9072f9882b562358 -#: b365ea7c08f84890843cefc1de884df2 5ac661fbfd284dfb879908b37507a982 -#: 93389c0a0f3c4246949260310c268818 da02ac4d953747af87f0823b67583cd5 -#: 9f9b9e5530324ed891dc11436cb1b07a 9277cace9d8d42ba82a0917d1c56dbad -#: e413ff1a05b24df0bcef07fa5f28a9df 772ad7a6c56b41b0b2b612869837e647 -#: 6d51c35dff7544d3a776b678b78b007c bcde83e7129f4e1688f2c6cb07f01a82 -#: 3504c90680b44749b6c9134de46bfbf1 5ee3b42b2e894d8faf3a7ed92333e597 -#: 9d40daa3f3b549b4b611838fd7e0dd68 e6298915a7f24b26a791942e0e2493a6 -#: 9aa8bac92852482c9be4eb38bbed8857 209775d96dc54160991bc8284bc9f292 -#: cc1337f5cd7a41c1bef992b086eefd58 bb905ffb7f7c4c8fb2d061dc267df4d9 -#: f1eaec34d53d488895a414b1a91f17a2 389b1794f4094c198c45012c176a3326 -#: ec5462ff808a44899afda72977ee307f 2c9102dea6f04fc981ca480fa6c8d776 -#: 54e1900a17974cf1a7c04aabdc75d6be d89ba1058ead43ba968ec400bea4855f -#: 947fd5c558834fb7a3e20689a7841f98 46b45e1e47034258a2c09daef09e4cd7 -#: 3caa0f97c878430290edb4bcf7a84185 75fdad7746f64679a77c7f8780d37110 -#: 815f3c3c16f8412780cbe4bf5314c8a8 004d23bea3e642388180b8381cba6acf -#: 869efca81cd5413593fee5c3ea6cad76 f3cfe624007242a185e296217cda246f -#: e5ff2171aafd4fccb29e4ddc28a0aa58 6e13a1e7338d461cbe44a395a4378b3e -#: 75c5e6875ba94dd5b762b50d81d56f69 628b2d125ff247268ec79801a5773779 -#: 96621e3b965b456bbbfa072a20d5c5c8 3844e1b7a54f455b8b3be2ced96ebd14 -#: 8c504c05acf24fa886dad15c57256a27 35989e8bc4684a059c4c0faa2c16aaff -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 722c4749ece7437d803f5268d4391e69 -#: c6e614b5e74249e0aacc2f5341932c4e -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 3b111625993443cf8eb9bda50ad9858b -#: b750a8a7ce2e4d6184b1849d1657c632 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: b3bc5bf6a9334b0cb8e5b81c10237e00 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 878e78e9d90d45389ed59efecdbff023 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 981623cb9a9f4ccda3b2b391b375dffa -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: 007cd8a96b7d4ad9b5610acdcef26ed0 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: f00a293137f04c7ba9716152074deacb e5c6a8ea019d41058715a7832fcd9f33 -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: b3fcbdda93244d8e9604804047c384f5 0ca8a7e1dd914075b15864da02167053 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 ../../_include/interface-mac.txt:4 -#: 27db113586a24fa3a77a4b706d527627 9359715f04844701ab58bfe76eedc72f -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 ../../_include/interface-mtu.txt:4 -#: 09fc4b10ed9d40249b33592a1c3b43e6 c61bec5b424c4a44956f53d8d53a0328 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 124872415f6547e7890db1dbfdb910a7 c85b92b925204a57b7b69f711ad39860 -#: b175d1a61f104595b9c932f950a8c011 534110737a4c407e8124c183a39c728b -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 ../../_include/interface-ip.txt:9 -#: ee4161aa9cd64fe38b8bc939b53e58a4 89f11c54f7184167865697f6e1b925c9 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ../../_include/interface-ip.txt:12 -#: 2e7e2c3ac4f146409b23a9639413ec21 1e437effac2d48ca85f0f6251b6be325 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 4fc5c984451d464d9847161a60b164b3 c6add590b80046daa9c55fa445f3541b -#: cce90567767f4200a7e831b55b43f2d1 4dbb0afcd1604e8cb6f9db883e4e786d -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 ../../_include/interface-ip.txt:21 -#: d1c3a29694264dd4b8098039bf9764e2 03c304f524fd457cb4179d1edd2a5f9b -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 ../../_include/interface-ip.txt:25 -#: d4746e6c931d40f1998023b3a3e0d790 33ffb140ec7645869119a0e2901c95dd -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ../../_include/interface-ip.txt:36 -#: 1cfd6f6dd65849e681efca941c558e64 def8f6e576a94db9b294e7e57a918987 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ../../_include/interface-ip.txt:42 -#: aa92cbe78cd044afb5f40c68840087ab 3ab8e5fb825b4b8ca7761b03eea0dc59 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 ../../_include/interface-ip.txt:47 -#: bde72b202b554ee4bbb248a938d9d77c da62174099534647a2a42bad7782f59c -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 6c25624f40e9484b9ab296a6f50ec141 1e0feefc97fe4625986e718d97a0f587 -#: 9fec11468656499094cea30dbc2f21f9 3e9ff08d61374d28af5dc870aeadd425 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ../../_include/interface-ip.txt:69 -#: b0ec94abb82f461d8817580ab4811781 da768f7026934467bb53c82eba148406 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 ../../_include/interface-ip.txt:72 -#: 93706fe0afc74077b1c06268201e16f8 82d60d80392c4fba933bcfe31d6a6116 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 ../../_include/interface-ip.txt:75 -#: 5c8df09338fa4c56acd560ce9422a9d6 c7eee58dd1a14ab9844cea39c9c737e3 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 ../../_include/interface-ip.txt:85 -#: 929796e428094b51bc1afa6a17df318b 9325ed6cf15c4e62bd5626aee38c1f5c -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 ../../_include/interface-ip.txt:88 -#: f64b991f6a4b4cbf9c24a230180869c6 b7956e94b8974b849558a8fa9f4c1279 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 ../../_include/interface-ip.txt:91 -#: 94e905454b454cbea68d0c7d59e19b41 4a628df655a649efbf99d560f59d2345 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 ../../_include/interface-ip.txt:101 -#: 10acbe002566461e9e997cde24018b7a 4e6c6e0476424fd9b777c13f1b1795e3 -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ../../_include/interface-ip.txt:104 -#: d8d2802c19024e70ad6fda2e667e6b48 f4dab6008b9b46d0b5fb8ad41e4711b4 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 ../../_include/interface-ip.txt:106 -#: fcb1d73bb42c4e9dbee3aeded9f41830 9aeea2a3bffd46f3bc53b22fb5eaa47d -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 ../../_include/interface-ip.txt:121 -#: 281c852249664c45bb273d907835925c 493a4c5be26949a587616b3b4a4ee0c4 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 ../../_include/interface-ip.txt:124 -#: 665c313ac9c54563bbe7e7102f49682f 8aa399e2c1794dfe866b34f2cec77218 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 ../../_include/interface-ip.txt:127 -#: 15cc7ffddbe44d318c99f72273717b24 13c6a63f1a65456c89be59adce4e677b -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 ../../_include/interface-ip.txt:137 -#: 6ab5647369e94dc6850637103cfad474 f5ad54001d464338b3fd8f7277c30d55 -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 ../../_include/interface-ip.txt:153 -#: 2d5d9cbe0bb14407aa6cc55c0773447b 105c68b054664435bc35b1ae520dcd61 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 ../../_include/interface-ip.txt:156 -#: 0ae8254e9a5e4d62aab6c82a036758d2 274b9ad46f8240d78b9e70dd90376168 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 ../../_include/interface-ip.txt:162 -#: ae865e05b7854ec5b48c53f1bd48592d b16b5aa5a0034522b37aa13ed05cf30a -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 ../../_include/interface-ip.txt:164 -#: 4a3f4effb51a40c5829d112acb9ce265 51fae18217b8479e925231a78d5240a3 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 ../../_include/interface-ip.txt:166 -#: 8a2009da56864d788cc1ef539a0b06b2 935870bb94ff435795f4fb131589b266 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ../../_include/interface-ip.txt:168 -#: 61ad13fdab5246f4a224d8561c8e0a7d 4544317ff4ff48c4ab887165dfcfd1d0 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 ../../_include/interface-ip.txt:170 -#: 7417e14401f5489aa04b462a6f520bb0 e9555c0170b04d83be6facbba94a45db -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ../../_include/interface-ip.txt:172 -#: 10e0c730e37e4ffc805a103085574dc6 cf7015e78e074bf292c6868d13db5b0c -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 ../../_include/interface-ip.txt:177 -#: 95c6ea4d07ae49e0b96cfad5e69ffc2f d57324411c3b427cbab66df4842bd14d -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 ../../_include/interface-ip.txt:182 -#: c9157754899e40bfafd9e21baf4ed154 b4b52d71e28c4625ae34a14b4dc3b978 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 ../../_include/interface-ip.txt:186 -#: 7bcdb81169eb43af87aeb47241a5d421 f5194cfd784d49448bc0c48c540cffbf -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 ../../_include/interface-ip.txt:190 -#: 36606099cbac4e6b86dd0c83ca2ef7c5 f68169b3a26f440da64f10d09cb0723a -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 ../../_include/interface-ipv6.txt:4 -#: 57539f5d8d97499d83b1c1003b3d73ea 0f6620f3db2b401b97d5618d139424ed -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ../../_include/interface-ipv6.txt:12 -#: c95078465c664d1da426d4d6f2d158e5 6dde8f9e381b4c018133c2387bcca65b -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 ../../_include/interface-ipv6.txt:25 -#: 101278884e344f2096da043eaa3bcba3 7b271b5ea6bc4de5a559afd35437faa7 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ../../_include/interface-ipv6.txt:37 -#: 5240320a1b0c42ef958093d719f04276 b55b71fc46714faca7725c29ff134aa3 -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 ../../_include/interface-ipv6.txt:65 -#: b97188abb2ae48ddad4f5887dcff29b7 f969b3e0d4d44bf7b6cdd560f290a82c -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 ../../_include/interface-ipv6.txt:68 -#: c2e091c1b4ee45a0bf7c160cc24149cd 955d4427b0994b7285a3965820721d43 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 ../../_include/interface-vrf.txt:4 -#: a35fee0532ea4d9cae04506d7ebd4fdf 72dfa7b744cd4308abb40eff113ce3cf -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 ../../_include/interface-vrf.txt:6 -#: 907a15d7d0f14bebab1e95fcda7e01e7 9c22c933d4ed4e3cb353c5e4ed7c14ad -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: ../../_include/interface-vlan-8021q.txt:97 1899082656c146c09755a0d6ffc9546c -#: d38c7fecd49c4281b3215e366877dbf3 -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: bed1fb48a10c4eb49998d3f9da4d79ae e20429f1da0441b1aee3aa207f7214a4 -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: aa4e4f8eb23243779d146defc20f64f2 b1372afb224343dbaf87094346bceee8 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: b6c21c78029c492ea1ba170ff36817f6 ce8f43b8e7e143588439b2f1f70073ec -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: 6e9700460f0242dc8dcd243813ac2d2b ed111482dac04caa9294c6e61e0b2a1b -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: c240c7705f354596ad094df8c1038838 868de428670d4bbd8758cc2cce15e712 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: 67affdcc6d1344efb2045de35f818023 4c44f0c0603947bbb0738101b4c8ed84 -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: 67d52ad9dfd540cfb43f75d9ea3b662f 92f48bbbcdef4206946f24700ad1c7a4 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: f3ac17b4463f4c44ae8b958c1b79c24f 54cfb04f5144476ca5a2ce7861c0c824 -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: d48dde6ceef241efb4a7e05381cdaa6d c1df25c4bf5f422cb51621a5f8059d82 -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: d5f724d3bd114194b6094f9044ee9141 d59ae504601e4c2c98df05eee9d8d475 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: 0f3c1b7a255242288cdd70af378bb7fb b30540ff96094edeacf470e7412d8fe2 -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 10c3df34f0a144bd9b286e7a17093d20 95e82422d89b4d4e949ed49c9cbc5158 -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 6c5460065ff14417917248b88a06c68f f259ee9ffff747f78a142b5ac845f5d5 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: 34cee5a662bf42f492d5aa2e47bbcc57 01e2ddf417bf4f0ebba55fa37e12d0fe -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: d3a6dcb548d64ef483c3d823db6b66ba e22b2a1995a747aca7249b70ea8ef75e -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: 1f00e7abf9e740d197a1bdf21187db6a e2b5b179f6be40e79d7ac3b9ccdb064a -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: 5db152f8cc8e4f7c8c84070df3106115 22c2f2ed77654f6889118b3af7f88554 -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: 01580901992c4b43a3115a1e9b2e4938 50a817a4aaf642ebb3227499475be6f2 -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 73156f52553b477996262ec2ad4ef6c7 28b45ff5be5f482bb5f82ac484d6b0f9 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: f3db635ba3144cf89a195d417b1183de cb67e64a19d846ca94a7e835f9ba1b63 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: a97f52ef2d024fea9108074bb20059b6 eca30b371e4e468aa677491780840de6 -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:27 -#: f8b0fa4c8f8243659e7d29e59f7045c3 -msgid "Member Interfaces" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:31 -#: cca219832c6d4a2c81b20b66da85c472 -msgid "Enslave `<member>` interface to bond `<interface>`." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:34 -#: 6108c4e960234f63b15e0b1035d6be8b -msgid "Bond options" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:40 -#: e42ddbf0023e46968e028e7656f5b3d1 -msgid "" -"Specifies one of the bonding policies. The default is 802.3ad. Possible " -"values are:" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:43 -#: ac95e6884e634da2acd8b3e2cf5921c4 -msgid "" -"``802.3ad`` - IEEE 802.3ad Dynamic link aggregation. Creates aggregation " -"groups that share the same speed and duplex settings. Utilizes all slaves in" -" the active aggregator according to the 802.3ad specification." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:47 -#: 0e68f2749a824934b413e7368c16dce1 -msgid "" -"Slave selection for outgoing traffic is done according to the transmit hash " -"policy, which may be changed from the default simple XOR policy via the " -":cfgcmd:`hash-policy` option, documented below." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:51 -#: 6f400561679042ca84d10c68669a9bca -msgid "" -"Not all transmit policies may be 802.3ad compliant, particularly in regards " -"to the packet misordering requirements of section 43.2.4 of the 802.3ad " -"standard." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:55 -#: 6d1f9261ee9b4b479fb8105fd4f655fc -msgid "" -"``active-backup`` - Active-backup policy: Only one slave in the bond is " -"active. A different slave becomes active if, and only if, the active slave " -"fails. The bond's MAC address is externally visible on only one port " -"(network adapter) to avoid confusing the switch." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:60 -#: 74aab1b8f8484a968bec78f02c46080b -msgid "" -"When a failover occurs in active-backup mode, bonding will issue one or more" -" gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for" -" the bonding master interface and each VLAN interfaces configured above it, " -"provided that the interface has at least one IP address configured. " -"Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate " -"VLAN id." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:67 -#: b1ac3ef33c154eeda597ab479db60a87 -msgid "" -"This mode provides fault tolerance. The :cfgcmd:`primary` option, documented" -" below, affects the behavior of this mode." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:70 -#: 88237849a0b74ad9b56f6cb7cc7c53af -msgid "" -"``broadcast`` - Broadcast policy: transmits everything on all slave " -"interfaces." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:73 -#: 815fd210a4db474a9123dadf9ff8a387 -msgid "This mode provides fault tolerance." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:75 -#: 8740f21f0d0a4a77854e14b27ffc2066 -msgid "" -"``round-robin`` - Round-robin policy: Transmit packets in sequential order " -"from the first available slave through the last." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:78 -#: ../../configuration/interfaces/bonding.rst:125 -#: c7c8c917df334ce9bc5790f0042ac7a0 0275e451693342bf9735656f9c650b49 -msgid "This mode provides load balancing and fault tolerance." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:80 -#: c4974c145cce4c78855dc0ff41280208 -msgid "" -"``transmit-load-balance`` - Adaptive transmit load balancing: channel " -"bonding that does not require any special switch support." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:83 -#: c4976ed5d9b2415783cc639ae1c5cb91 -msgid "" -"Incoming traffic is received by the current slave. If the receiving slave " -"fails, another slave takes over the MAC address of the failed receiving " -"slave." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:87 -#: 4cbd7042423341568fef7e7360dfe926 -msgid "" -"``adaptive-load-balance`` - Adaptive load balancing: includes transmit-load-" -"balance plus receive load balancing for IPV4 traffic, and does not require " -"any special switch support. The receive load balancing is achieved by ARP " -"negotiation. The bonding driver intercepts the ARP Replies sent by the local" -" system on their way out and overwrites the source hardware address with the" -" unique hardware address of one of the slaves in the bond such that " -"different peers use different hardware addresses for the server." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:96 -#: 7bbef070df7a41ca8a43ebfb2a936eff -msgid "" -"Receive traffic from connections created by the server is also balanced. " -"When the local system sends an ARP Request the bonding driver copies and " -"saves the peer's IP information from the ARP packet. When the ARP Reply " -"arrives from the peer, its hardware address is retrieved and the bonding " -"driver initiates an ARP reply to this peer assigning it to one of the slaves" -" in the bond. A problematic outcome of using ARP negotiation for balancing " -"is that each time that an ARP request is broadcast it uses the hardware " -"address of the bond. Hence, peers learn the hardware address of the bond and" -" the balancing of receive traffic collapses to the current slave. This is " -"handled by sending updates (ARP Replies) to all the peers with their " -"individually assigned hardware address such that the traffic is " -"redistributed. Receive traffic is also redistributed when a new slave is " -"added to the bond and when an inactive slave is re-activated. The receive " -"load is distributed sequentially (round robin) among the group of highest " -"speed slaves in the bond." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:112 -#: 84ca820d44eb466aa2f7c740967761e2 -msgid "" -"When a link is reconnected or a new slave joins the bond the receive traffic" -" is redistributed among all active slaves in the bond by initiating ARP " -"Replies with the selected MAC address to each of the clients. The updelay " -"parameter (detailed below) must be set to a value equal or greater than the " -"switch's forwarding delay so that the ARP Replies sent to the peers will not" -" be blocked by the switch." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:119 -#: 0661022ed9b74497ae7078eeaea7669d -msgid "" -"``xor-hash`` - XOR policy: Transmit based on the selected transmit hash " -"policy. The default policy is a simple [(source MAC address XOR'd with " -"destination MAC address XOR packet type ID) modulo slave count]. Alternate " -"transmit policies may be selected via the :cfgcmd:`hash-policy` option, " -"described below." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:129 -#: e407195338e746dfaa85ab6aee7bc30a -msgid "" -"Specifies the minimum number of links that must be active before asserting " -"carrier. It is similar to the Cisco EtherChannel min-links feature. This " -"allows setting the minimum number of member ports that must be up (link-up " -"state) before marking the bond device as up (carrier on). This is useful for" -" situations where higher level services such as clustering want to ensure a " -"minimum number of low bandwidth links are active before switchover." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:136 -#: ../../configuration/interfaces/bonding.rst:151 -#: ec5a96198d7645cd9043db8fe8424af4 0cb63840446b40deba576cc6d0a3a6b2 -msgid "This option only affects 802.3ad mode." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:138 -#: ecd281cea4ca447d93abc73235212604 -msgid "" -"The default value is 0. This will cause the carrier to be asserted (for " -"802.3ad mode) whenever there is an active aggregator, regardless of the " -"number of available links in that aggregator." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:142 -#: 08d708971c7b4af78c94a3ad8120bb75 -msgid "" -"Because an aggregator cannot be active without at least one available link, " -"setting this option to 0 or to 1 has the exact same effect." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:148 -#: 1648b65cb2134c78bfa57ec92207716a -msgid "" -"Option specifying the rate in which we'll ask our link partner to transmit " -"LACPDU packets in 802.3ad mode." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:153 -#: aaf23777b1c44e2db37e2ad48e09a579 -msgid "slow: Request partner to transmit LACPDUs every 30 seconds" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:155 -#: b0ea0457e26e45ac94c076508b5c914b -msgid "fast: Request partner to transmit LACPDUs every 1 second" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:157 -#: 6b3e131205a24d458eeaa91e8f5286e3 -msgid "The default value is slow." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:161 -#: d99cfa461fa84857af85e2efde0d1088 -msgid "" -"**layer2** - Uses XOR of hardware MAC addresses and packet type ID field to " -"generate the hash. The formula is" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:169 -#: 1f8acb300eb8427eaad8e197b1def2d1 -msgid "" -"This algorithm will place all traffic to a particular network peer on the " -"same slave." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:172 -#: ../../configuration/interfaces/bonding.rst:198 -#: 8a512314180f431f94b24ccfec93bdcf 3f8ec78f6c6140a190af0872e2e7b085 -msgid "This algorithm is 802.3ad compliant." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:174 -#: 540e8a2c87fb4256bdd3440b7c9db797 -msgid "" -"**layer2+3** - This policy uses a combination of layer2 and layer3 protocol " -"information to generate the hash. Uses XOR of hardware MAC addresses and IP " -"addresses to generate the hash. The formula is:" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:185 -#: ../../configuration/interfaces/bonding.rst:214 -#: 284d683b0bce48e8891a5e2e9f533cb0 cbf6f56775d04a2e8b82384305a2261b -msgid "And then hash is reduced modulo slave count." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:187 -#: ../../configuration/interfaces/bonding.rst:216 -#: e249b4c8cb0149119c21a9d18b893636 1f07f607f3d84f26b218307458f2b984 -msgid "" -"If the protocol is IPv6 then the source and destination addresses are first " -"hashed using ipv6_addr_hash." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:190 -#: 4551f6faedf34fe39416d8536861aa15 -msgid "" -"This algorithm will place all traffic to a particular network peer on the " -"same slave. For non-IP traffic, the formula is the same as for the layer2 " -"transmit hash policy." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:194 -#: b350b179ebe14466ba5ba8050183f050 -msgid "" -"This policy is intended to provide a more balanced distribution of traffic " -"than layer2 alone, especially in environments where a layer3 gateway device " -"is required to reach most destinations." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:200 -#: fc62ce931bd84cc4a58b7720c4b0516c -msgid "" -"**layer3+4** - This policy uses upper layer protocol information, when " -"available, to generate the hash. This allows for traffic to a particular " -"network peer to span multiple slaves, although a single connection will not " -"span multiple slaves." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:205 -#: 5268345fcf6f4b24a1fcec780767d90c -msgid "The formula for unfragmented TCP and UDP packets is" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:219 -#: 8901973c77eb4a079a4ecdb5c2a371fb -msgid "" -"For fragmented TCP or UDP packets and all other IPv4 and IPv6 protocol " -"traffic, the source and destination port information is omitted. For non-IP " -"traffic, the formula is the same as for the layer2 transmit hash policy." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:224 -#: 56e03e1bdbf8443d944f9f882bfd926c -msgid "" -"This algorithm is not fully 802.3ad compliant. A single TCP or UDP " -"conversation containing both fragmented and unfragmented packets will see " -"packets striped across two interfaces. This may result in out of order " -"delivery. Most traffic types will not meet these criteria, as TCP rarely " -"fragments traffic, and most UDP traffic is not involved in extended " -"conversations. Other implementations of 802.3ad may or may not tolerate this" -" noncompliance." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:234 -#: 342974c22e88453db96df0708c2a359a -msgid "" -"An `<interface>` specifying which slave is the primary device. The specified" -" device will always be the active slave while it is available. Only when the" -" primary is off-line will alternate devices be used. This is useful when one" -" slave is preferred over another, e.g., when one slave has higher throughput" -" than another." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:240 -#: 759d7fbe5e42429f8e7366a95692b5db -msgid "" -"The primary option is only valid for active-backup, transmit-load-balance, " -"and adaptive-load-balance mode." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:245 -#: 97f08bc72a3642a59e12b359b121d089 -msgid "Specifies the ARP link monitoring `<time>` in seconds." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:247 -#: 507598bead264974af207ba7221ad9b9 -msgid "" -"The ARP monitor works by periodically checking the slave devices to " -"determine whether they have sent or received traffic recently (the precise " -"criteria depends upon the bonding mode, and the state of the slave). Regular" -" traffic is generated via ARP probes issued for the addresses specified by " -"the :cfgcmd:`arp-monitor target` option." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:253 -#: 2066c92d3a9d4c36ba093cb27685f4a3 -msgid "" -"If ARP monitoring is used in an etherchannel compatible mode (modes round-" -"robin and xor-hash), the switch should be configured in a mode that evenly " -"distributes packets across all links. If the switch is configured to " -"distribute the packets in an XOR fashion, all replies from the ARP targets " -"will be received on the same link which could cause the other team members " -"to fail." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:260 -#: 40cab5bb143b4e71a7dcdb47bdfaf1a7 -msgid "A value of 0 disables ARP monitoring. The default value is 0." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:264 -#: 2de519691bab4e969b5755b926de5369 -msgid "" -"Specifies the IP addresses to use as ARP monitoring peers when :cfgcmd:`arp-" -"monitor interval` option is > 0. These are the targets of the ARP request " -"sent to determine the health of the link to the targets." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:268 -#: d8ea98752d5a4bdf878933031012038d -msgid "" -"Multiple target IP addresses can be specified. At least one IP address must " -"be given for ARP monitoring to function." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:271 -#: 0c8b136236c34e09975fe495d42d04c9 -msgid "" -"The maximum number of targets that can be specified is 16. The default value" -" is no IP address." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:275 -#: a4ef448105144c4581189bd451c9fe81 -msgid "Offloading" -msgstr "" - -#: ../../_include/interface-xdp.txt:3 0d2e0da1bc6f41d5b71d5e5b795953ca -msgid "" -"Enable support for Linux :abbr:`XDP (eXpress Data Path)` on recent 1.4 " -"rolling releases. You must enable it for every interface which should " -"participate in the XDP forwarding." -msgstr "" - -#: ../../_include/interface-xdp.txt:7 e6439e72d41642ac8a2517647b248223 -msgid "" -"XDP is an eBPF based high performance data path merged in the Linux kernel " -"since version 4.8. The idea behind XDP is to add an early hook in the RX " -"path of the kernel, and let a user supplied eBPF program decide the fate of " -"the packet. The hook is placed in the NIC driver just after the interrupt " -"processing, and before any memory allocation needed by the network stack " -"itself, because memory allocation can be an expensive operation." -msgstr "" - -#: ../../_include/interface-xdp.txt:14 fd96ecdb190d4e609b8108018ff9305e -msgid "This is highly experimental!" -msgstr "" - -#: ../../_include/interface-xdp.txt:16 ac2922ba0ff94167ac387f3afa0440a8 -msgid "" -"Enabling this feature will break any form of NAT or Firewalling on this " -"interface, as XDP is handled way earlier in the driver then iptables/ " -"nftables." -msgstr "" - -#: ../../_include/interface-xdp.txt:20 e6f712bc564b42e89e2f5b69663c0298 -msgid "" -"Enabling this feature will only load the XDP router code as described here:" -msgstr "" - -#: ../../_include/interface-xdp.txt:24 87ab14172b2f4fe7901e7bc8590683cf -msgid "" -"https://blog.apnic.net/2020/04/30/how-to-build-an-xdp-based-bgp-peering-" -"router/" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:282 -#: 9365135035e14693b098e0d7824acf40 -msgid "VLAN" -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:1 632d5dd85213465bada73f09f466c581 -msgid "" -"IEEE 802.1q_, often referred to as Dot1q, is the networking standard that " -"supports virtual LANs (VLANs) on an IEEE 802.3 Ethernet network. The " -"standard defines a system of VLAN tagging for Ethernet frames and the " -"accompanying procedures to be used by bridges and switches in handling such " -"frames. The standard also contains provisions for a quality-of-service " -"prioritization scheme commonly known as IEEE 802.1p and defines the Generic " -"Attribute Registration Protocol." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:9 fd02176d8548493287104969f9f84c34 -msgid "" -"Portions of the network which are VLAN-aware (i.e., IEEE 802.1q_ conformant)" -" can include VLAN tags. When a frame enters the VLAN-aware portion of the " -"network, a tag is added to represent the VLAN membership. Each frame must be" -" distinguishable as being within exactly one VLAN. A frame in the VLAN-aware" -" portion of the network that does not contain a VLAN tag is assumed to be " -"flowing on the native VLAN." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:16 54cbdce57640413194de31d39313368e -msgid "" -"The standard was developed by IEEE 802.1, a working group of the IEEE 802 " -"standards committee, and continues to be actively revised. One of the " -"notable revisions is 802.1Q-2014 which incorporated IEEE 802.1aq (Shortest " -"Path Bridging) and much of the IEEE 802.1d standard." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:21 f681dc41e4884f4aab3066eca00ae988 -msgid "" -"802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. " -"The term used for this is ``vif``." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:26 43b9621fc1a84ef5851a434e9ea9ee84 -msgid "" -"Create a new VLAN interface on interface `<interface>` using the VLAN number" -" provided via `<vlan-id>`." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:29 bc7a59da8d3d4d028249fab54c77dab1 -msgid "" -"You can create multiple VLAN interfaces on a physical interface. The VLAN ID" -" range is from 0 to 4094." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:32 7cc4ebc2ccc540b6a45f9223f11a01eb -msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:289 -#: 99b9b26cf91d4dca94b552a8aff2f97e -msgid "Port Mirror (SPAN)" -msgstr "" - -#: ../../_include/interface-mirror.txt:1 1b823f14a5054e41b6d8e43dfe71fbdf -msgid "" -"SPAN port mirroring can copy the inbound/outbound traffic of the interface " -"to the specified interface, usually the interface can be connected to some " -"special equipment, such as behavior control system, intrusion detection " -"system and traffic collector, and can copy all related traffic from this " -"port" -msgstr "" - -#: ../../_include/interface-mirror.txt:6 79fcb04909e94daeb721f993452fe424 -msgid "" -"VyOS uses the `mirror` option to configure port mirroring. The configuration" -" is divided into 2 different directions. Destination ports should be " -"configured for different traffic directions." -msgstr "" - -#: ../../_include/interface-mirror.txt:13 ba6a5443ac7c4dac9f2348f22dfa8ffc -msgid "" -"Configure port mirroring for `interface` inbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:16 97eec744336e493ba1e5eaa967eb4fae -msgid "Example: Mirror the inbound traffic of `bond1` port to `eth3`" -msgstr "" - -#: ../../_include/interface-mirror.txt:25 81ceaaba001a4594a58f5a18a993c514 -msgid "" -"Configure port mirroring for `interface` outbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:28 021d2588c1b64be9b7d3c6bfcf704096 -msgid "Example: Mirror the outbound traffic of `bond1` port to `eth3`" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:298 -#: 6b33ce6237d4421ca3d9933d4fcf6221 -msgid "Example" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:300 -#: f391423ac6bd4e7d9d700e8b5e708ceb -msgid "" -"The following configuration on VyOS applies to all following 3rd party " -"vendors. It creates a bond with two links and VLAN 10, 100 on the bonded " -"interfaces with a per VIF IPv4 address." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:319 -#: a2506aa51c804c4fa350faa265a2cb7e -msgid "" -"If you happen to run this in a virtual environment like by EVE-NG you need " -"to ensure your VyOS NIC is set to use the e1000 driver. Using the default " -"``virtio-net-pci`` or the ``vmxnet3`` driver will not work. ICMP messages " -"will not be properly processed. They are visible on the virtual wire but " -"will not make it fully up the networking stack." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:325 -#: 18918b6d7d934046a0499d5a8d002445 -msgid "" -"You can check your NIC driver by issuing :opcmd:`show interfaces ethernet " -"eth0 physical | grep -i driver`" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:329 -#: 8fcdf89f69334165b87e577f4f150561 -msgid "Cisco Catalyst" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:331 -#: 8d47d69681294d97b598ab57384bedc5 -msgid "Assign member interfaces to PortChannel" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:344 -#: ad3f4d5770a74ffea9687da800bd8fea -msgid "" -"A new interface becomes present ``Port-channel1``, all configuration like " -"allowed VLAN interfaces, STP will happen here." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:359 -#: d08dc2691589426686efda33001c3759 -msgid "Juniper EX Switch" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:361 -#: 72b1d10cf0be46bd8e80185ea58977f3 -msgid "" -"For a headstart you can use the below example on how to build a bond with " -"two interfaces from VyOS to a Juniper EX Switch system." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:388 -#: 01c625e2189a4a25a9f3a0aca05c35d2 -msgid "Aruba/HP" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:390 -#: 1bf5f0461e3747b290b15620b01c336c -msgid "" -"For a headstart you can use the below example on how to build a bond,port-" -"channel with two interfaces from VyOS to a Aruba/HP 2510G switch." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:403 -#: d0071fe56fcd46f9a49425cd81f53e07 -msgid "Arista EOS" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:405 -#: c7b93a2faee54f22882fa6afbabf5bb9 -msgid "" -"When utilizing VyOS in an environment with Arista gear you can use this blue" -" print as an initial setup to get an LACP bond / port-channel operational " -"between those two devices." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:409 -#: 62afc7bb745c474ebcb19402cb53ee33 -msgid "Lets assume the following topology:" -msgstr "" - -#: ../../configuration/interfaces/bonding.rstNone -#: 0ebeb644434e480bbaf9fd3a82a24624 -msgid "VyOS Arista EOS setup" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:414 -#: 52690e6eaacb422ebee60e1a00618a1b -msgid "**R1**" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:432 -#: 542afa84d3f1499c8a5bc61c6b1ebaaa -msgid "**R2**" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:450 -#: b45ca26604594326b5d05670aa2b9aae -msgid "**SW1**" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:481 -#: 85666e1bc8f1437083514992979701f2 -msgid "**SW2**" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:512 -#: a865012ac267460494ac8c967869b8ce -msgid "" -"When using EVE-NG to lab this environment ensure you are using e1000 as the " -"desired driver for your VyOS network interfaces. When using the regular " -"virtio network driver no LACP PDUs will be sent by VyOS thus the port-" -"channel will never become active!" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:519 -#: b76686bf96234ac3b0f46916cca566d0 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:523 -#: 7cc8c9c02fbc48f7844ea7668ed95ab4 -msgid "Show brief interface information." -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:538 -#: dcd978123ddc4c14b6562d987e5f0fe7 -msgid "Show detailed information on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/bonding.rst:555 -#: f2d43c66ed214161b4e3dac35627f80b -msgid "" -"Show detailed information about the underlaying physical links on given bond" -" `<interface>`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bridge.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bridge.po deleted file mode 100644 index 316b52f7..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/bridge.po +++ /dev/null @@ -1,1078 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/bridge.rst:7 -#: 0fef91177829425bb487fb2dd73ad37b -msgid "Bridge" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:9 -#: 171d65d0310e4e05ba4209b0ee9b1c82 -msgid "" -"A Bridge is a way to connect two Ethernet segments together in a protocol " -"independent way. Packets are forwarded based on Ethernet address, rather " -"than IP address (like a router). Since forwarding is done at Layer 2, all " -"protocols can go transparently through a bridge. The Linux bridge code " -"implements a subset of the ANSI/IEEE 802.1d standard." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:16 -#: d5067ff367bd4be6ad12c60c4d9b3873 -msgid "" -"Spanning Tree Protocol is not enabled by default in VyOS. :ref:`stp` can be " -"easily enabled if needed." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:21 -#: dd7628b671734fa0bb5ca8333d884ca0 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:24 -#: 56c7a45be808409cacd217409d18bf38 -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: 3a7f37f11466446398339b32ca446469 81637e0e841d4ea883bd43ac080230fa -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: a3770ad4a2854ca8bbc77d247c86ed29 3769d8eaf41e47818f709f31307efe08 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: 1a2c482baabd4c3b8959e5c77c58bf50 afe9de97fc074ec497d29c2426d554ca -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: dff3f33b3134459d86ffe1aed4e2e0c4 90fa75575bae484a9725c23bd7634c67 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: 04d019ea93cf4fef8d423770836dd75e bce61a262021425d839c568ec0958ce8 -#: 5e33aadd18f9469980027cba738a8f96 7e9e74c5735347e3ae4d315a3eebb65c -#: e8de0f4f02964466b0f617d81c5e1ba3 d2d190be874144eaa2c9eec964b08866 -#: 9cd22f52b54f419fbee5a0e97e7e478a 39a32ce4b33a4176a75e7d1e0945fda9 -#: 6bc49b69690f40c2b7e9206234d7f2bc 3129970c406e418a90821400cd71c46e -#: ccc6738ab6444f439b42c95be9d75fe2 2c3234f22a934fbb822b67e5a5345e7f -#: c7f4da4a77324fd0986e2c5dc55b81c8 86dbc23f9cb6449b95f2f117df5eafb5 -#: 723b507bbfd34bad96cd5c9d1780fca6 140fa8f6c0dc4403b280e8c398e7138e -#: 4003c686be5d48fda0fe95dbb868123a 7b928fb8c2274c09a1aa76fd7c8c396e -#: b1e36aa05f8e4d8487b7aa887b1a0c5b 107b040ca0194feb9cdd78bdc3eeb919 -#: a4af93e41cc946b491f0d0d8e4896aac 927395059ea9400b8d25e9fe7346dcd2 -#: fdd348ef4da54c7d915489303d5fed1b 6c73d5d53d0b473489bd98c44fb5ade4 -#: 8d9d11886619436094b4da073657c358 de54bcb237e94937af596a676252f670 -#: f8a7795aa25945e496bb11604f2dff04 55158fe4cd874bc8b92d24c35c609576 -#: f624838845dd4701a709c51fe33f3b0c 814757d3842f480c9102fce52703c80b -#: ce223182cdd740e4a098848710b094f2 6df91f98df1e4a699039e2888ce31741 -#: 0fd78c2234fb42659800b7db47ee5e19 0fa51c1077dd49e88878236369a1b205 -#: 6519c3f2a70f47fcbbe1dcb127fa0899 496671c25fec4c24a47c691752ce937b -#: 08430c8583f5455897a061fe5ad86a38 f714748d2117406091be58c1bef1089c -#: b7c445e6f46f4b38aa70576365aabcf2 75f6eec976d74c95af6e86b52d1574ce -#: 5846b66d5e8d45968cf39ae4d4c9e83d -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 766f3b41eb4140f6a54279473fe2edb9 -#: 70ee68a7e8c743a08ee75b0ce38a39e5 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 d88d7ebd3778469fb5def47511a38689 -#: 0393c46c37ac4d8eb9cd19d2657ed025 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: 0f751d731bfe4bfb9dd536fa1c066290 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 28be68ed9fbf48c08368fb09799ec8fc -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 109c71d8136e4193abfa73e178a13c08 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: 9caaad4444ab448f901a8d6324d1ea15 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: 10ff8d078aaa42a998bed4f1b1b086f8 c08e8bc216254cabb516421e7effc2c5 -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: 88703ed44588451b8f80f19fdf8b1068 22be7192844f4bddb796c0b631823b48 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 ../../_include/interface-mac.txt:4 -#: 09e532facde84c94a3c797fa0b873f2b ac90d072655749b799eb5573442092b2 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 ../../_include/interface-mtu.txt:4 -#: 14c482f370bc48f1b1279c063ea242eb 57ecf97bc1b3499ba7ced10e292009db -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 058aa5aa7c68403294fa2b20ac929406 6d1871e571524f44a79cc657d6d1a7f7 -#: 253952a7af664bd3bec6e3c5e57330dc 65ba915afea0413385f2eb1fd3f456de -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 ../../_include/interface-ip.txt:9 -#: 65981a0d22724aa8bc221d3b2a16f07a 23cde527f2504f2983a2365cc6d6eb76 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ../../_include/interface-ip.txt:12 -#: 505e1df10dc44c0c99e6ccc1685e4a33 be08cb09b64a4d6da45ff2fac007928f -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 50f727bb629e4e0eaa5acb3e830ffe0a f6218da06ed349219325622b22d91e26 -#: a9a9a9a9f8e24f51a1bf273041b9e2c3 35bc65e06abf4c739bc7221df9487cba -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 ../../_include/interface-ip.txt:21 -#: f14b06e7bc744114b349750752a36c51 9fab3a8d23754e34993c7ca67f19d016 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 ../../_include/interface-ip.txt:25 -#: ed8760db211b4fd68cf0a8c3e9b47b1f b5008d2f4c4a4d8788255cee37a5a57d -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ../../_include/interface-ip.txt:36 -#: 1694797371c046dc836690d5f598c4af 6f5b539f51b946ceb690d1849ab5704e -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ../../_include/interface-ip.txt:42 -#: c5cc65a332ea4dc6be505fe20cc1bf01 fa7028ef3b7c4faa849bffdae53b7b7b -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 ../../_include/interface-ip.txt:47 -#: 48d75974a48544948e74cf7343bd0b13 39a9e7448c1347bb94ebf3a96091e1e1 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 6e9610b952e445d7bb05f1c81982bfc6 ea0e7540f5dd4be0a0cbf13c29a8f25e -#: f160b0728b11475ea3f4c1f119ee293c 3692cfdd123147acb3f7f8f3cd5909a9 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ../../_include/interface-ip.txt:69 -#: 5e72fd28110842a0b57061d842c37251 63fe93356459488fb8842adf6b845e25 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 ../../_include/interface-ip.txt:72 -#: 6b247ad167ac4f9b9d4ad075627033f5 9e4dbc102d05403b84f7dfe3cea026c9 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 ../../_include/interface-ip.txt:75 -#: 8496a2043b87465e9c981593a1fc8f1a 11f6a8d5bea3462189cf80301d0a1b17 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 ../../_include/interface-ip.txt:85 -#: 1743c3643ba447bfa12ed367b6cc22ae 29be36b2faca41d2a105010bd39cdaac -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 ../../_include/interface-ip.txt:88 -#: 2b0e7c8c28fe4c1395e16429417f92a0 af6535195b5d4300aab37e0f1d1475a0 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 ../../_include/interface-ip.txt:91 -#: bf59f6b9e8244738adf65cdf8f35f404 5ba76094665e4942add4664a3e04da9d -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 ../../_include/interface-ip.txt:101 -#: 169a0c36b3064437867ac1e3d684a86f 64d48559412f475fb394d78878df8b7f -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ../../_include/interface-ip.txt:104 -#: ec005558b31c40269cdd2d040eb75a38 546e836ab6fc492ab07d24411350b8d8 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 ../../_include/interface-ip.txt:106 -#: 257981a3e5cd436693a2fe9275237456 f4fc80ca2c754b069bff43925199308e -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 ../../_include/interface-ip.txt:121 -#: dd92a8c8ee784e0089c252ef02f4ed5e 85bb8339928e4823b457682b839e1d65 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 ../../_include/interface-ip.txt:124 -#: da50e49c7d1346118db365c89372829e 27c2699b99374b5a9ea30f81a0988322 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 ../../_include/interface-ip.txt:127 -#: c7d456a0a62c440f80a3d9a441747220 da0be5c12d76461993ddde65881d7c00 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 ../../_include/interface-ip.txt:137 -#: 752c8765ca1c4525a6a77a6ea27dcb3b 5da28bbd7f2247ca886d0610acf3567b -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 ../../_include/interface-ip.txt:153 -#: c7f57f5f4d1447e68e37b2aa9f99526e 717c7665fc8549c19bade0f726e77d61 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 ../../_include/interface-ip.txt:156 -#: cdd1c06a12bc42dbab24a7ed7b28759b f1cac7913e1b487eab499efcdb399360 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 ../../_include/interface-ip.txt:162 -#: a07b0773df40415f8e575e7b8fa8704a 99db66f5a4dd4e53ac9410f5d3212c83 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 ../../_include/interface-ip.txt:164 -#: 0e55dc1a0d974a3b8e1b13c70e6b5205 1fb303129c21445b9acf0e858dc4c5c6 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 ../../_include/interface-ip.txt:166 -#: 34f76f90fdce46e3b07d7992d1bd9239 2fa4895f6dd64da788124a2c94982793 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ../../_include/interface-ip.txt:168 -#: ecb6726628464f8b8f53fac66c8cfadb 58eca80874b04685b7d778fa7f1cedaf -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 ../../_include/interface-ip.txt:170 -#: 365a4097588c4b20b956620b4e343b4d d08a374308fa4e43a687fef678c08fed -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ../../_include/interface-ip.txt:172 -#: 198ea493bfab45c390ca9dc6722a9fb8 80bcd7eabcc547899f73d02144e27012 -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 ../../_include/interface-ip.txt:177 -#: 588403949de34c62bf1fc7a0d16ab0e7 0e062c7e30fc480991d757635d44a669 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 ../../_include/interface-ip.txt:182 -#: 0b88abcc1a984b9b93937206acef1467 9755d39e635247f397a167498e601f91 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 ../../_include/interface-ip.txt:186 -#: ef6d23a5efa844d485bd644bb19f3c52 7d43017794194f1585dc9f36f9d2368b -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 ../../_include/interface-ip.txt:190 -#: d518f982351d4319a0048d78959d7944 e85c96ac04bf4e478bdf190383c492a9 -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 ../../_include/interface-ipv6.txt:4 -#: 436d1123a21740deac39298cff58f074 3bb0bc16e9d346b9934242bfd861efb7 -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ../../_include/interface-ipv6.txt:12 -#: 3097341f9db5421285dab1c0a12ec6fc d0c9300d9bf04876b855d524cb8b8fe8 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 ../../_include/interface-ipv6.txt:25 -#: 5c4bda6a860340038f07b7bae8d1160b 396d846bd6594b3394d4721c81a96ce1 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ../../_include/interface-ipv6.txt:37 -#: 4ac79d06bb114cfdbf6476429a3db147 ee693abdc31e4e44beb538e1a9257cfd -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 ../../_include/interface-ipv6.txt:65 -#: 6bf9c40c9451472babc6cb5a6ac3eef0 ab7ecc47e9ba4018bad53ae5aad6d49f -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 ../../_include/interface-ipv6.txt:68 -#: c4c8f0f8e5ef439799ca5780c0fd9537 f91247afdbc84ddcaa61ea1822076bb4 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 ../../_include/interface-vrf.txt:4 -#: 19612181976d4b68bd5b81ecbe0c934b 842b94ac21f44453a4c9d32f856926a4 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 ../../_include/interface-vrf.txt:6 -#: 671378ba3a3440cfa0b488b743cb21f1 6a3c4a68be7346388ff2df8bbc066fbd -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: ../../_include/interface-vlan-8021q.txt:97 4368c57ff7bc4b22beb8f808485d7ccb -#: 191d4602f63d46d2a2c3d043e92ec0d3 -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: 550dfb1ec79a4ee7b4be7e2020272e04 39c2c6f9d5134a738bac414c4aa15e8b -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: da7a4fcfae634ea7b4bb20e12973944c 6d61466b266c498aa26b67a3a55257a1 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: d6f1de91fbf840138803702cbe695f2c 44f325ef031d46a4903bcdd7acedcae0 -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: e2bec1f2a06d4b2091176c10df4ab154 563309b9fb194915aeda12d1587d8229 -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: d6122e0704074a8d821310c98fe6914e 6d4109460d2047abb26ffabfd8876c33 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: 5515022411d64370b501ff6f1f72206d b0767ecfbdac41d3bded732ad866a9d8 -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: 7f95631f8c9945cd81ee7db7b2024df4 69aadba2c2a140a9b7234dcf155c9d83 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: 673e3dd831ca4ab3b42029fe506f33d4 a97ddd68960142d68018d772afe87cfb -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: 366f8b456c4840b49b6c0cb68c77fe4d 9fd7e91fa96b46d8b091e060ce6fd41e -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: b74be6fe363445fc8e0759d7e74fe63a 9c5971ba74e4418291cbaf57c2faa8ff -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: 0e841483fcaf41aeb84996e332b23722 00ca8ea16602453ba07085b13efbef9e -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 99b0e2d638cb484f8cb5bdd57ffa4f8c 2ff36b5ea1bd43f293d48f417ece3be6 -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 65bef82dfb314998ad0350018b408bce 5996c192c41e458883fc397ba44e3cb6 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: 847bf249a7e549b8bbe9c62c0653a2da 982826eb667c4be6ae22f026f0740e3e -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: d2fdebd62ef8421aa7f0cf601a20738f 158643fd84d74b14a0468c4af852c4a0 -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: d94f50422d384f34bba4ee7e565c0461 bd9a5dd42fc64a929e0e93ecffcae27d -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: cd5446b2450c41bebe5a461a1e2b6499 80d8c485fa334df7a214dc46cd9e4d3b -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: 8da6cf9e97e14bd1a83446aba85ff924 6dfda2c6e560450ab0fac8c9a7936224 -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: f4f6f6a375b6479f8975e519f3145c60 8a9680e5d436464ba6e362e2bee776e7 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: e8f4f22f273e4a2d916e440e9bfd61ce ee6950ad48ad4f6b9b697ef738580e35 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: 1480dd234fd841fa9f0fccf9db8bbc2a 3f441af8bced49149310ea4ab1603ada -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:31 -#: 063096fe082f4bffb6851f0e25e74b5f -msgid "Member Interfaces" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:35 -#: ae7847deb8074373b52446f6b9ce5b2d -msgid "" -"Assign `<member>` interface to bridge `<interface>`. A completion helper " -"will help you with all allowed interfaces which can be bridged. This " -"includes :ref:`ethernet-interface`, :ref:`bond-interface`, " -":ref:`l2tpv3-interface`, :ref:`openvpn`, :ref:`vxlan-interface`, " -":ref:`wireless-interface`, :ref:`tunnel-interface` and :ref:`geneve-" -"interface`." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:46 -#: dc4b275bdbf54149b312fe0cf05aab46 -msgid "Configure individual bridge port `<priority>`." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:48 -#: e4a69e0d2f3946f8b619b05a317ae3fd -msgid "" -"Each bridge has a relative priority and cost. Each interface is associated " -"with a port (number) in the STP code. Each has a priority and a cost, that " -"is used to decide which is the shortest path to forward a packet. The lowest" -" cost path is always used unless the other path is down. If you have " -"multiple bridges and interfaces then you may need to adjust the priorities " -"to achieve optimum performance." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:60 -#: 8482b1a892f943c3921d364428d1fa41 -msgid "" -"Path `<cost>` value for Spanning Tree Protocol. Each interface in a bridge " -"could have a different speed and this value is used when deciding which link" -" to use. Faster interfaces should have lower costs." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:66 -#: d6322c288a4d48a482873c817557f0a9 -msgid "Bridge Options" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:70 -#: 72e72b57bfda44b0a44000f8691f3dd1 -msgid "MAC address aging `<time`> in seconds (default: 300)." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:74 -#: 551e0f3439bd457a8d5829480534d4ce -msgid "Bridge maximum aging `<time>` in seconds (default: 20)." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:76 -#: 12ba0e1c3d614651b8dd9a0e64864c99 -msgid "" -"If an another bridge in the spanning tree does not send out a hello packet " -"for a long period of time, it is assumed to be dead." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:81 -#: 9b611c0afee248ab84b65a48c4e83d48 -msgid "Enable IGMP and MLD querier." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:85 -#: 7a48432759904dcc9b5de1d624fb23ad -msgid "Enable IGMP and MLD snooping." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:90 -#: 14c7c1fd1bdf4b8bb14b19262b2a9a87 -msgid "STP Parameter" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:92 -#: af25c661e7604bc09686af05348ee8e7 -msgid "" -":abbr:`STP (Spanning Tree Protocol)` is a network protocol that builds a " -"loop-free logical topology for Ethernet networks. The basic function of STP " -"is to prevent bridge loops and the broadcast radiation that results from " -"them. Spanning tree also allows a network design to include backup links " -"providing fault tolerance if an active link fails." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:100 -#: 7bf77386122a48fbb75e076736dcb597 -msgid "Enable spanning tree protocol. STP is disabled by default." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:105 -#: 9ed86865916b465c83f5f76fa0d20ec3 -msgid "Spanning Tree Protocol forwarding `<delay>` in seconds (default: 15)." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:107 -#: b29f77875b444e7da477db2846b33986 -msgid "" -"The forwarding delay time is the time spent in each of the listening and " -"learning states before the Forwarding state is entered. This delay is so " -"that when a new bridge comes onto a busy network it looks at some traffic " -"before participating." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:115 -#: df28c843df3d4711a09f90f774c0b579 -msgid "" -"Spanning Tree Protocol hello advertisement `<interval>` in seconds (default:" -" 2)." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:118 -#: 5dfc6bfbf61d485aa75199b74d9dd108 -msgid "" -"Periodically, a hello packet is sent out by the Root Bridge and the " -"Designated Bridges. Hello packets are used to communicate information about " -"the topology throughout the entire Bridged Local Area Network." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:123 -#: 77663f56d77b4c5cbeec0a89dd089560 -msgid "VLAN" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:126 -#: 7ea69c4dd48e45069a10fa532de1208a -msgid "Enable VLAN-Aware Bridge" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:130 -#: ac6df26ea214422f89d62a945badb68a -msgid "" -"To activate the VLAN aware bridge, you must activate this setting to use " -"VLAN settings for the bridge" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:134 -#: 1af6deb0b69c40629618693d5b8d9273 -msgid "VLAN Options" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:136 -#: ec001a2953fe4f21b8e7a5b9618e61c1 -msgid "" -"It is not valid to use the `vif 1` option for VLAN aware bridges because " -"VLAN aware bridges assume that all unlabeled packets belong to the default " -"VLAN 1 member and that the VLAN ID of the bridge's parent interface is " -"always 1" -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:1 83325facd943448b9110ed8739080bd1 -msgid "" -"IEEE 802.1q_, often referred to as Dot1q, is the networking standard that " -"supports virtual LANs (VLANs) on an IEEE 802.3 Ethernet network. The " -"standard defines a system of VLAN tagging for Ethernet frames and the " -"accompanying procedures to be used by bridges and switches in handling such " -"frames. The standard also contains provisions for a quality-of-service " -"prioritization scheme commonly known as IEEE 802.1p and defines the Generic " -"Attribute Registration Protocol." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:9 c30b4d3f47b64fe198eeb3bfdd756d6b -msgid "" -"Portions of the network which are VLAN-aware (i.e., IEEE 802.1q_ conformant)" -" can include VLAN tags. When a frame enters the VLAN-aware portion of the " -"network, a tag is added to represent the VLAN membership. Each frame must be" -" distinguishable as being within exactly one VLAN. A frame in the VLAN-aware" -" portion of the network that does not contain a VLAN tag is assumed to be " -"flowing on the native VLAN." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:16 26ff9bcd840a4129bca7f5b6f30a0d30 -msgid "" -"The standard was developed by IEEE 802.1, a working group of the IEEE 802 " -"standards committee, and continues to be actively revised. One of the " -"notable revisions is 802.1Q-2014 which incorporated IEEE 802.1aq (Shortest " -"Path Bridging) and much of the IEEE 802.1d standard." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:21 13f225f624d24b3da8f95776ae3b68e7 -msgid "" -"802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. " -"The term used for this is ``vif``." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:26 7501ea6bfb0b400a92466379bb492388 -msgid "" -"Create a new VLAN interface on interface `<interface>` using the VLAN number" -" provided via `<vlan-id>`." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:29 f5ae268d88e3492cbd9af2b9b6bbceb5 -msgid "" -"You can create multiple VLAN interfaces on a physical interface. The VLAN ID" -" range is from 0 to 4094." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:32 321c11bf68534b57952895ac4c459c9f -msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:148 -#: 212df10bbfab4741a14ee30670f26947 -msgid "" -"Set the native VLAN ID flag of the interface. When a data packet without a " -"VLAN tag enters the port, the data packet will be forced to add a tag of a " -"specific vlan id. When the vlan id flag flows out, the tag of the vlan id " -"will be stripped" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:153 -#: 242eb3370d5c434c87b90891fd581007 -msgid "Example: Set `eth0` member port to be native VLAN 2" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:162 -#: a084be3203dc437e8259a0a84a9fcc9d -msgid "" -"Allows specific VLAN IDs to pass through the bridge member interface. This " -"can either be an individual VLAN id or a range of VLAN ids delimited by a " -"hyphen." -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:166 -#: b79f2b7c612548178bfea2daf2ef81a3 -msgid "Example: Set `eth0` member port to be allowed VLAN 4" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:172 -#: fd40c6c0e08845569a712a1f6b71bc9a -msgid "Example: Set `eth0` member port to be allowed VLAN 6-8" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:179 -#: f1cabb6548a5495aa1c093a9645846af -msgid "Port Mirror (SPAN)" -msgstr "" - -#: ../../_include/interface-mirror.txt:1 51e56c4c5c0f49f084d04bdbfc83fced -msgid "" -"SPAN port mirroring can copy the inbound/outbound traffic of the interface " -"to the specified interface, usually the interface can be connected to some " -"special equipment, such as behavior control system, intrusion detection " -"system and traffic collector, and can copy all related traffic from this " -"port" -msgstr "" - -#: ../../_include/interface-mirror.txt:6 e08b25463ff84e4dbfe013796ea9924a -msgid "" -"VyOS uses the `mirror` option to configure port mirroring. The configuration" -" is divided into 2 different directions. Destination ports should be " -"configured for different traffic directions." -msgstr "" - -#: ../../_include/interface-mirror.txt:13 6162e4c30eeb4698af454cf1c30fbd77 -msgid "" -"Configure port mirroring for `interface` inbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:16 0abbe675f27041d7b3d9c8a8fb231f0a -msgid "Example: Mirror the inbound traffic of `br1` port to `eth3`" -msgstr "" - -#: ../../_include/interface-mirror.txt:25 457736ed92a947c185ee39fbada69bc2 -msgid "" -"Configure port mirroring for `interface` outbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:28 4797054806924bdc90532de5bcbed57c -msgid "Example: Mirror the outbound traffic of `br1` port to `eth3`" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:187 -#: 299939702f864a5d929679ec965ea0df -msgid "Examples" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:190 -#: e27daf9e22754f4aadaae153e8a783a4 -msgid "Create a basic bridge" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:192 -#: dcfb955cac1841d69803025353e38f94 -msgid "" -"Creating a bridge interface is very simple. In this example, we will have:" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:195 -#: ../../configuration/interfaces/bridge.rst:229 -#: e6fcabaa8da04d928f8971fb8f46c906 7b73641751f24e97a3c9ace89a013691 -msgid "A bridge named `br100`" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:196 -#: 92c95e2627554912a3f0ceb0b26437ae -msgid "Member interfaces `eth1` and VLAN 10 on interface `eth2`" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:197 -#: ../../configuration/interfaces/bridge.rst:232 -#: 312dd7e4cdac497aaf5de6349f39bce0 8bfbbec9a23144508f393d09641ca957 -msgid "Enable STP" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:198 -#: ../../configuration/interfaces/bridge.rst:233 -#: 74ccc185fc294ebf9baa9b1fc7fd94dc 4480ccd7cecd4458bd15ff766e7c030a -msgid "Bridge answers on IP address 192.0.2.1/24 and 2001:db8::ffff/64" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:208 -#: ../../configuration/interfaces/bridge.rst:244 -#: 5077f1d9c179402fb814c9c5e02b36e9 d63ec3ea604742b2ada43fbd722f0d99 -msgid "This results in the active configuration:" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:225 -#: a3edca518ba1431db25ab3b5a202c3d1 -msgid "Using VLAN aware Bridge" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:227 -#: ed668f48fc5344e6be119d071a4c15e6 -msgid "An example of creating a VLAN-aware bridge is as follows:" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:230 -#: afc67f990eb04b19b6fd6fc06642f696 -msgid "The member interface `eth1` is a trunk that allows VLAN 10 to pass" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:231 -#: 3d7924acca324e36a41d311e5bd23f66 -msgid "VLAN 10 on member interface `eth2` (ACCESS mode)" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:266 -#: 85148e762b684e72b8838d252b62f6bb -msgid "Using the operation mode command to view Bridge Information" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:270 -#: 69b1295c7bcb4990afa6f9a5bca6827b -msgid "" -"The `show bridge` operational command can be used to display configured " -"bridges:" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:283 -#: bc4ed225de5a434293fa85b5cb137f79 -msgid "Show bridge `<name>` fdb displays the current forwarding table:" -msgstr "" - -#: ../../configuration/interfaces/bridge.rst:310 -#: e66bebc635474676a1582f5fe841ecdc -msgid "" -"Show bridge `<name>` mdb displays the current multicast group membership " -"table.The table is populated by IGMP and MLD snooping in the bridge driver " -"automatically." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/dummy.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/dummy.po deleted file mode 100644 index 95a904ab..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/dummy.po +++ /dev/null @@ -1,116 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/dummy.rst:7 225fa9192f7245189c47d69a79d66d35 -msgid "Dummy" -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:9 25f653d5461546308795a9dcab143c7f -msgid "" -"The dummy interface is really a little exotic, but rather useful " -"nevertheless. Dummy interfaces are much like the :ref:`loopback-interface` " -"interface, except you can have as many as you want." -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:13 -#: 1e72c2b3315f45928e90e8d30d1923cc -msgid "" -"Dummy interfaces can be used as interfaces that always stay up (in the same " -"fashion to loopbacks in Cisco IOS), or for testing purposes." -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:16 -#: 0f78a91330de49e681900b47a31bb411 -msgid "" -"On systems with multiple redundant uplinks and routes, it's a good idea to " -"use a dedicated address for management and dynamic routing protocols. " -"However, assigning that address to a physical link is risky: if that link " -"goes down, that address will become inaccessible. A common solution is to " -"assign the management address to a loopback or a dummy interface and " -"advertise that address via all physical links, so that it's reachable " -"through any of them. Since in Linux-based systems, there can be only one " -"loopback interface, it's better to use a dummy interface for that purpose, " -"since they can be added, removed, and taken up and down independently." -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:28 -#: 363d47c14c71419298141b7209551463 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:31 -#: 78a0f0518d1045deacbfcb071ee33aad -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 becfa4c0c1e144a1abe948450867a0c7 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 70bcc023c96441598cb38b8a42113441 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 ../../_include/interface-vrf.txt:9 -#: 9cdcd75236bd4c819652a8d43bba01e4 c9f9403a597241718822a3225fd4362e -#: c7334a858dfc41798672ae98c0a8fd32 0f64c4e6d05e4c7baf2324c07653d633 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 a58ea870199b4693b3eda69fc63aa369 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 cd74f2aaff3849ae895c4d86a920159b -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 fb2a2814c8f7412f8070882df988f433 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 28a05cc94e584988b99c98e85556c00a -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:51 -#: 97699624680d4972a9ddf3fb1f96ee89 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:55 -#: 20d8ebe4f85e4f73b50f10134b157bf5 -msgid "Show brief interface information." -msgstr "" - -#: ../../configuration/interfaces/dummy.rst:67 -#: d9802ea9a0f04566bfe1ee1265121260 -msgid "Show detailed information on given `<interface>`" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/ethernet.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/ethernet.po deleted file mode 100644 index 23e9e511..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/ethernet.po +++ /dev/null @@ -1,1281 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/ethernet.rst:7 -#: 09058f27e87a4735b60ec19a5544dd7f -msgid "Ethernet" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:9 -#: 7088575c59db45a48ddce28572a8956d -msgid "" -"This will be the most widely used interface on a router carrying traffic to " -"the real world." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:14 -#: 265aeecb70c4482281dfd9a11cd7e002 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:17 -#: 9e969beca4d14d5fba24a8c555ccd22d -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: 661365f07b1c4b3da8a2588a0ab6d438 ee0bfab5d99243fba38e02c9041d62ba -#: cb46c82171d0411aa10bf1b8f140d8ec -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: 8eda8dd16d3046239aea806771d9ef6f 36bbe89603864bc98f34fa6e5b6e69c8 -#: f896a6e132984774aa169171417ccca9 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: 6b0c439dd80d4f599e7dd4ae1ab20966 dc4702b7c84947569ae0aeec93a254e8 -#: 526234f21eb74b68a7308c7afbb077b8 -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: 9385c3eec6264af4ae53598b1464d3b0 e5eb96b123084237b0720b073646127f -#: 52cbb89552a5464a96b6dbefb3bef3a9 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../configuration/interfaces/ethernet.rst:65 -#: ../../_include/interface-xdp.txt:28 ../../_include/interface-eapol.txt:18 -#: ../../_include/interface-eapol.txt:33 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: 0ee9bc49a2a04b318eb0120f5a2019f7 3f2bd7cbc7c241f49892bdf6d38083a8 -#: abcc6421f19b428eb4ba4d42f78c73e1 3c0fc3aed22340748598ee597d428186 -#: 516f69c241424837a60a4caa41e08158 42337226d96e4f93934e7cf86653f243 -#: 13e993039b9e412094dc8687d11f1294 0ac230043d5a4fff931387c0c2811be8 -#: 3a3f12ae6021484bbe77ff9d73e8357b 616b5d2df9a041e389dbfd43701b6921 -#: be1c8d82aa72408f87a26e1c2c83a395 d5b468cc2b5a408c9ee658f5dadcbb10 -#: 0cfd83795a52482a94361d04ce29bba9 dcd8d402df9149d0a8f0d32333797bba -#: 72a086529577470081dfc040911eb190 de6bc256a68b4ee98702b3d995b845b8 -#: 26396abe682e418f9356a332b069874d 1bdca9db0cc1434f8ff828d2632cdc07 -#: eed69f93008f41e591fc1bc8e93daee1 0254bcd1cd0d43b3b7a22d5836ca3d0c -#: 4341fb23537a44399c391fa9f5eaeaa3 68031f5f931c4f61b654382d7b0ee907 -#: 80df6b9659794c9a8f1d986d6c4ebcec ccc5d8eeacd742e4883d7722e143027d -#: eba13c57c03c413b9171995c87109710 5a6b876178d64a7796ac7c1d20c3e4f5 -#: 8f70e844450f4cec8ce9f3a61345f243 81ad121033f4428e8dbd78462bb6831b -#: bc04113d55344610b3a5ffe7ea168312 ff98c39f5c804bf1a637ced01af8ae96 -#: 1cb0e5ed4f0e4c89a00a62150dcf54e2 17021300636b4f89b441fea58965e101 -#: 7e31837966774f759606e7e4d7cf0592 68429e2de6d34516a56f9a83b477f80c -#: 2e4c904554cf444e83065a4186743406 cabfe75a8bf44c6bb8b8c84b1a2d079c -#: 9189cdafabf2408caf1e2dd5de83d66a d0c2d148b6ad461b88b13914fe6f8c53 -#: ee5a4b67f7974091a1486930cb91a78b d2aeaa32f47546a0a22b7e2e3b5d7e1f -#: 03d61cc322164b329315ed54c0e59200 d6ce6fd22f174fdf92ddf67cfe5f7642 -#: c409c552de41421fa196baaf7f4dd9e5 a8b5b9d2f54e4a6ca213b303bca40603 -#: 27585a25ce4c4900b146854a35b2044c c0fd3539a6324b62b7d42f02f2b869e0 -#: 83c53e7ba1184d2490a14720b4dbca35 3885ccbb840b4ade8a1059e78fb38810 -#: fbff9913f250497ca3f23e300bc08b9d d9d6832ca2264a5187300ec087265aa1 -#: 7b746cb25e0043148ad67b3c08fdb22c 8a8a3e31a6fd4089b64246d3251f77ca -#: f9a2c02cf0954e19a231a6ffeb197495 e8c49b77144a4ab2827eeaa4309b6c4d -#: 0daeb7e609d948e0a7be1fb6892f3bc6 24421163210d4eed8f109f5f575dc76b -#: 25150fd68c374529a5c76db31af52c57 7383ac28a5b94bfcb8c155e1af8d6605 -#: 78442d648a2440a890b9d4946293834f d77c00be6e5e4b85bbdcd90e0b986b6c -#: b1fbe4de75e745cd8ebf8c4ffd6ac181 808789f715f9448293717804b6b2b74f -#: f201b61df6124d3aae7ecfc1da9906b2 5d93cd4727c44817b6e7a07553bf7bcb -#: ab9e9ce88b054a3480b542571fd90aaf -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 14128adb5cab4891bf9dd4fb72397793 -#: a3c20fe0e10b4e13861cec9b40af0276 55b45d7de6da48f8ac174f049ae5772e -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 7382837394fc4e9b97544d5d96c48e2a -#: cbaaf8f2663b4bbbaaf8592f3ae43836 f3adf99f83e94b0f904c55ad2b5e074e -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: 6d0ccf7ef33140708b51d8729c712e6f -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 6002aedc2b884dc1963c3da978e0f683 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 9e27d83442624e65913c0f368bc591f4 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: 155fe49b5de6409ba2e72667bb58f5d1 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: 9fff277d5c704b2895bfd26a8f18c638 054cc7368a1c4b75b05e0880f4fbd595 -#: cb86d47970dd4531b847f225f5735cad -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: eb96c73290254572adbc02dc2054f265 4435a097e3b14573b2751b19a59df10f -#: d5c0fbbfc9084af28532ecd2c79d7518 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 ../../_include/interface-mac.txt:4 -#: ../../_include/interface-mac.txt:4 312a286d11a44d57853b0e268f294c6e -#: de9532735c804e69ab179ca98533e945 1e89dbeffcf84317848faed31a237b36 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 ../../_include/interface-mtu.txt:4 -#: ../../_include/interface-mtu.txt:4 172868eca6c04952a606651dd9b47148 -#: b2a6e77c4f344333bd4d6554873c03cd 6beac53ee9c94f8790c2c97e22d1ca34 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 72bc496e2ef9432ca91f0cfb35ab1511 c0db694d396a4769b320bd0d9da42d1b -#: a232239bba8a4e9e9c96d65c22019760 972cdb8293fb418ba5770245fe416cc1 -#: 0e338bf5aecc45698da92a4d9d57bf72 7f13bb5cd6b244efb46e8d858bcce263 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 ../../_include/interface-ip.txt:9 -#: ../../_include/interface-ip.txt:9 44aedc55cd9448a4b4e5bcc1724e68c4 -#: c3e2026cc59c4e6aabe64db1f2599679 e63ca5ae7fd24da4b9c73cda8e8263e2 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ../../_include/interface-ip.txt:12 -#: ../../_include/interface-ip.txt:12 a9fdfbba3a184978972153a397dba4a4 -#: 4e6bf0a9a4d14655bae72d51f4f3655b 82108355302e4086ae5d4f22153aca1a -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 9f60f9caf2e848fd95eeae178ff06e0f 87b3482d743b484f980e45f3c5814a99 -#: 40887b2b494e4c1e93768bb6604dfaa3 398d8ccabea64767bb9cd3e50d7613e2 -#: 23c5b67e99354ff9b826de5c0b35debb 03ac7b1c78444f17aa82e488349afdf4 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 ../../_include/interface-ip.txt:21 -#: ../../_include/interface-ip.txt:21 f308a8e0a95047d6ab9e0e78846f5358 -#: 89f1c9f0d7884421a025ed2194c14a38 57162637f5a94101bf7c1d3ef8394c0b -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 ../../_include/interface-ip.txt:25 -#: ../../_include/interface-ip.txt:25 67aab97dee9043afa28987dde0945db4 -#: 0949bd0960474dfca922ad669739f100 20763cfcd73e480bbc61acefccadecd2 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ../../_include/interface-ip.txt:36 -#: ../../_include/interface-ip.txt:36 1fa53ded48a143c6adfa743b9d0a4f64 -#: bdc049166179490caabc81ba55028614 44846d410cf44487aaf06fea583cca9a -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ../../_include/interface-ip.txt:42 -#: ../../_include/interface-ip.txt:42 cf2fc43e73aa4209a3a40a483a9025be -#: 6f171ca798ae4d6db5f7d8d14ce7ca86 6dd2351a8f914428981bb6a70bc107f2 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 ../../_include/interface-ip.txt:47 -#: ../../_include/interface-ip.txt:47 79ecc2c4a49e4db89051624b678de40b -#: e0cb06a77aaa4b6fb085efddf7c6f8d0 26a7e34e859445e18d27fd47db6e1a3b -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: c056634b087c407f80f058a38fdbcd6c b12fc9bf6f6e432ca01edd2f895d509d -#: 1e9deb5bb47c4b33be37366f5c696773 538e65b9666947619d2361de2ce70691 -#: cb06916ca8124ea1a0eacfe250cb6c52 ad3924218c804824a66c91d3a0a4f29e -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ../../_include/interface-ip.txt:69 -#: ../../_include/interface-ip.txt:69 37dfd493f4524835a3fe84734fd82683 -#: ae7e15e524fc48d3bff56901d8a6ac7d 5f4fba92b0d5463ba00c424f8e3778d7 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 ../../_include/interface-ip.txt:72 -#: ../../_include/interface-ip.txt:72 cca035d64d2a4560a1046231d318234d -#: 07ce1fa76aa84a63ae0f23f49d63104a b2966c5b6ecf4008beefcaacba2e59b2 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 ../../_include/interface-ip.txt:75 -#: ../../_include/interface-ip.txt:75 d7dbbadc7f1340d3891c736fca1cf610 -#: c176885ed6fe497e95547acce6d61c53 21eb22764c12485eb854d6dd0b24d5db -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 ../../_include/interface-ip.txt:85 -#: ../../_include/interface-ip.txt:85 9be03ededc784d52a6453d76effb7fb5 -#: 54779bbe19954b1b9a05f0f5743b4f44 cba0e7f0af644a05b55b601dd6e22dae -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 ../../_include/interface-ip.txt:88 -#: ../../_include/interface-ip.txt:88 394ce6b4fce1449188b1996cf3a076c0 -#: 1ec617faa2164728a4f0965bcf789120 178ec702cb9c406bb7c3b668428c715b -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 ../../_include/interface-ip.txt:91 -#: ../../_include/interface-ip.txt:91 6b2ef01fb36c46ee9871cae1d42f677e -#: 83326ef4d3b34fc99b5300c7e5c16a4b 019141e4865f4ff3a7508731330c72de -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 ../../_include/interface-ip.txt:101 -#: ../../_include/interface-ip.txt:101 6eedebffcea642af99787a5dd421331e -#: 596f8e12689e47a88b90a6b5da071f85 54945adf7b014d36a69777120b8d82da -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ../../_include/interface-ip.txt:104 -#: ../../_include/interface-ip.txt:104 9c99e43fda3440119462ecaa031a6613 -#: 3bee220789d9494790a617695c3610a5 ba7f9e58a214417e98e3fc59bb6ef47a -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 ../../_include/interface-ip.txt:106 -#: ../../_include/interface-ip.txt:106 bd9bb66d1ca841c6be7478785d40f1eb -#: 1cc82a6c45e142e0ab03b7f0c771bfa4 a12f76ae29b940b2922352c8370c6656 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 ../../_include/interface-ip.txt:121 -#: ../../_include/interface-ip.txt:121 643cfa95293744b3825d75b83a5b9a42 -#: c0bbf8635b63427bae4693c074b0362a ece8136189df44a08209adc12b94852d -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 ../../_include/interface-ip.txt:124 -#: ../../_include/interface-ip.txt:124 2c8890fc9bb5410cb03a7527641c22fe -#: 92f19a28b81e4b7caa000a958e2083bd 75c62aa22cbb4936b868ced0fdbb0fdb -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 ../../_include/interface-ip.txt:127 -#: ../../_include/interface-ip.txt:127 fc7050e1a53f4b4d9a65c55c63fae330 -#: a51158921efa48e3b5791a545d31085d 1153a90d5ff447f08e6c192d38922eb4 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 ../../_include/interface-ip.txt:137 -#: ../../_include/interface-ip.txt:137 c089d376ab59406d8fb57ddf79e794fd -#: e3d88034f6d1430eab265cff3e0bc7c2 0030b1a847724832bc95bc4d2d97d539 -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 ../../_include/interface-ip.txt:153 -#: ../../_include/interface-ip.txt:153 2beac4ae43c14bcc92f832001ce073fd -#: f887e0d591994a648379f7bec128987d 4c42e1da216e4a71a9a19bdeb7a6e5cd -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 ../../_include/interface-ip.txt:156 -#: ../../_include/interface-ip.txt:156 a798e18f7d0b45be873b494a1119a81a -#: 9606c60661d344c48b390d87afd800ea 57786847354a43f999e9b9706e22484f -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 ../../_include/interface-ip.txt:162 -#: ../../_include/interface-ip.txt:162 bab3a18b6b0147048eb7c215fa51b89b -#: 5c64a6eb313b4965aa411286c97d21c8 290905b03c8b4ac994315f4241f7cdb1 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 ../../_include/interface-ip.txt:164 -#: ../../_include/interface-ip.txt:164 a74451ff11694c82ab315238997c4e74 -#: 5e113fb6e2754154b09d35da61d11727 32c1ccb37bb148028a36b2a77f41cb6f -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 ../../_include/interface-ip.txt:166 -#: ../../_include/interface-ip.txt:166 5dab8d5bb6cc4e12a1e42ced9c5ea378 -#: cfa9c50b984c4be2a4fbb420395cdb6b a80a43c4003146b7933fa7aee1aa37d1 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ../../_include/interface-ip.txt:168 -#: ../../_include/interface-ip.txt:168 7f6a2819687640c6b3029c011af9e2b9 -#: 688521c6ed864f8b8788f6ce9968779b a494f5df4ff944b09d5add5e72ae3f96 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 ../../_include/interface-ip.txt:170 -#: ../../_include/interface-ip.txt:170 838eed1d9a274302afe7383c1422f0cc -#: ee555bd63ef949f7bfba8f779dccac2d 06600fb26348418e90590547a32b8e8d -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ../../_include/interface-ip.txt:172 -#: ../../_include/interface-ip.txt:172 ebf31bafb44048d0851dfbe640dfe738 -#: a907c6ce3c7b461698f18632d840ae7f f1c47dfc1f2d4f82a04fe21b6806f4b1 -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 ../../_include/interface-ip.txt:177 -#: ../../_include/interface-ip.txt:177 9b3bee051014452dbe16d58e87b75371 -#: 21e20a80e585462caf2f5a862cc549a1 1b99da5892f94e2b9e9b63e1a4486a49 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 ../../_include/interface-ip.txt:182 -#: ../../_include/interface-ip.txt:182 5d27ea12840a4fcf8d08f5baaccae5d6 -#: 0f4234a9759b41e3b09bf57300930206 51749f80a1f843e1a88bb4d7a96e060a -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 ../../_include/interface-ip.txt:186 -#: ../../_include/interface-ip.txt:186 5b5758bf9a02499d9363f79038377076 -#: 7a88c962a23e44bfbc30de94fa30488a fb6010e98a644c30b443d3838adc6b2e -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 ../../_include/interface-ip.txt:190 -#: ../../_include/interface-ip.txt:190 6250e8c4fb1d4437aebff950b9cf949f -#: 9a3baace32384791a2f2b6b09a8e2291 8d2fd6072af848f08cbd98972e366e76 -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 ../../_include/interface-ipv6.txt:4 -#: ../../_include/interface-ipv6.txt:4 87d1de32b1ae4427afd7a4d64ae813a8 -#: d2bfe576ebe14c6081a64d43243cc1cd abdf8aa1b82041b0876a4f36a35615cc -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ../../_include/interface-ipv6.txt:12 -#: ../../_include/interface-ipv6.txt:12 0aebe44661874547bd729ebe0a563c04 -#: 96f805eae10c4fef85e7a2efa2e9846c 4244513de78f4f68b8bf9003c9671372 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 ../../_include/interface-ipv6.txt:25 -#: ../../_include/interface-ipv6.txt:25 8555056d226d45d69d2eadbd03e95a61 -#: e95415b53eda4d16b968c98ed3f88fc0 9f3afd18911549bdade3d707dff88604 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ../../_include/interface-ipv6.txt:37 -#: ../../_include/interface-ipv6.txt:37 5d4b8475bed345b582460dbff38f9af2 -#: 9d890adfb1474b4a87ab56925e3bd29d 22b51adc8501402aba48e33e33cab817 -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 ../../_include/interface-ipv6.txt:65 -#: ../../_include/interface-ipv6.txt:65 5b6a74eb6e7245c491d6d4079a19bff9 -#: 192a703a4cc44f7daaed7b14855bd92b 5a8c381c6a374523bdfef39722383fc7 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 ../../_include/interface-ipv6.txt:68 -#: ../../_include/interface-ipv6.txt:68 3fd34f571b054f24a14b87ffd86cebf2 -#: fb947f6bf2f641aa931c41c0a7a68f1e a1f49668d8bf4654a761c893f8b8f6a1 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 ../../_include/interface-vrf.txt:4 -#: ../../_include/interface-vrf.txt:4 ad99f4bc95f64c0990f0e157afd9b924 -#: 59a2880ffece4c87bd19e8e05b67e373 19ff2275ca5f48f797a2151c00c381ca -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 ../../_include/interface-vrf.txt:6 -#: ../../_include/interface-vrf.txt:6 e07ef745829b4cbc91cc04d2eeabe1d9 -#: 87a444dc404b4d19ad334429794459db c8b719b89148467a917ec8040b8a91d6 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: ../../_include/interface-vlan-8021q.txt:97 -#: ../../_include/interface-vlan-8021ad.txt:121 -#: 07bcd06c9c4b452fadae92d031d0bbe9 67e9521362ee416994d353730d4ef715 -#: be553b4f54914345ac1fa09c15353974 -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: 3e4547b1de824b0f903ef9eeebe4dfcf e516bd5bebcb43cbadf72762134214e2 -#: ec5b420e7da546b08d8114bf0254d69d -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: 14725c12a6ec4a5f8c7afe1156f9c691 dc9e95d62f8b483badb5662db1875011 -#: 7b2b096d395049b3880c4b87ef3e68aa -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: eb8f4256291b48bc949e3bbd8a27f0de ad94dae15d0240d28a8550faea333cec -#: f9f16f032adc474dbd182f929aaa3129 -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: 9f881ac8e56e4569b7d5ea5666fbec41 18374c082d4f43d4b364a90172f443e5 -#: 7bdc3d4da9844cba862857c72b2f3f6c -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: ab5c8236a9c5489c96bb11bbf4a6a3a4 2a69df8c3aad4a8a9cb0fa34f21e2f8c -#: 68e3dff44d0f41e898040209f31eb2d5 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: 498c40590419428b9b17336925c272f5 1ff76ca1fc8f4569bb47d851109e7a28 -#: e203a26f382041d0885544524830bf24 -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: 031119c55aad457199be6cc84ee1aaba 7ea67a378deb457ebb554c46cdf548dc -#: 5dc5dcf283404f6c9543658368b3f4c6 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: e1cb0e3267d5433f82c91253d1e33c6e 9ff28faeba204659a333352ea8e9a238 -#: 91cf7d77cbef4c0b8eed41d7dd9728bd -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: 0aa3e5ea8ee44608bfba74aca406d450 5e2afb5103114e1d8e2f286ae43b270b -#: 78ba12b7e9604aa29f2f6054238d63bd -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: a0f70c7740e04bc9bb97e4cc3ec69258 b077fcdc9cc54f81835a47387910d04b -#: 95f920c709204459adbcace0e2c5c3b6 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ca23cbbfe65e4aa88732fdfe7462da38 45b17eddff814e8db81b30a742008064 -#: a5a4717044244f09be6c057804fe92da -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ef1f1476dcf54d46866fc6f9234e866e bb7c4875e4ec482fbec099197d3d49ac -#: 2d29f6510fde4462871397cdd5f6826e -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 5bed90102b4147be987c934c79860c2a 27a90f05959e465eaa6d5d082516001a -#: 937fdd0df3724f909177ae1aa0b28429 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: de1b158ca93a41d3811c0a30161b3d90 fb811164682247508ad049e706be3c07 -#: 32bdf48630364598a14d47e8b1a7dfb1 -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: 21d684c5da60470296a01b2a0e9f8413 141cabb6291a4117bae7d8d4af37a7ef -#: 9ad1ee3695d441d5bdfdd9f90633241c -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: d779f313d027468d8a00b676d38532ad f7a3280f0dcb464ea5ca9c7eb2a0d354 -#: cf322f47036641deb2d100824d46b399 -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: 09c9185b4f194154a3d775e2d5a56a5d afea00ada8d948208c865ca4f9aa8def -#: f28830fa4f1c4f5b99ff13038e52485a -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: 7e39ef3db5834eb1a0a46026b66ce275 f38d1f09f5704e8ba67d5f28d35f8af6 -#: 83a584f270414f549b0649ae658bae4d -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: f5caa7b0b0f14c808d8133720ee4e09b 9b067d1771984d20afdb8973fa623d08 -#: e1505a5b411c4e2aa42dabd06c9994ad -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: 8fcb650c15194e13a7640c2cb1290c3a 1694409e9ae64098aa805cdea538fa5c -#: c8e5bff456e747cdb106c2ab81b61d4a -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: 583d5dc3f92e4e2b840494ede0b2ef89 85e13877aa374db2bd45bb38c41c4987 -#: c6905c0c519241b994ce8decb5797ba8 -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:24 -#: 2d758cdadf0a4e629d689efabb05d7a0 -msgid "Ethernet options" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:28 -#: f373d9fab46d4c77b56ce4b07825cb78 -msgid "Configure physical interface duplex setting." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:30 -#: cc9177a73aaa476d896f4ce254dc1a08 -msgid "auto - interface duplex setting is auto-negotiated" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:31 -#: f3af44ab0644407ebb5003aa3269ee39 -msgid "full - always use full-duplex" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:32 -#: d063ba2f8eca4621b46434d3d0f425ba -msgid "half - always use half-duplex" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:34 -#: ../../configuration/interfaces/ethernet.rst:53 -#: dbece41b4ca645cf96f8f12e090ccac5 1f98c26ad802483c89d3a7830a75f158 -msgid "VyOS default will be `auto`." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:39 -#: b7a9a08879a74d20adc4be641d3bab5f -msgid "Configure physical interface speed setting." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:41 -#: 1b445199459346d094792d0cd2d0dedc -msgid "auto - interface speed is auto-negotiated" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:42 -#: 783123d0d9ad4695b037b78e65345052 -msgid "10 - 10 MBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:43 -#: a504936515ef4a4c88f76be049de39a5 -msgid "100 - 100 MBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:44 -#: 5da71e16f5e54e0d8df094dc09114cc8 -msgid "1000 - 1 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:45 -#: b28a18b89ca5461ba0e5ea9911a838b8 -msgid "2500 - 2.5 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:46 -#: 9823cbeda72d47f0b345c96aad385082 -msgid "5000 - 5 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:47 -#: bdd707c6284b49d6958358b79966415e -msgid "10000 - 10 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:48 -#: f4fa422f2ae3437b8b5fbfadeb4ad9d1 -msgid "25000 - 25 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:49 -#: 28737074bf384a6ea9050297f48c148a -msgid "40000 - 40 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:50 -#: 5af6cc0ec4954dcda84ff4402185584a -msgid "50000 - 50 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:51 -#: 40b9eca23846431c85d962765d551db0 -msgid "100000 - 100 GBit/s" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:58 -#: 1a627f2289494457b840175181879b1a -msgid "" -"Use this command to mirror the inbound traffic from one Ethernet interface " -"to another interface. This feature is typically used to provide a copy of " -"traffic inbound on one interface to a system running a monitoring or IPS " -"application on another interface. The benefit of mirroring the traffic is " -"that the application is isolated from the source traffic and so application " -"processing does not affect the traffic or the system performance." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:72 -#: 7736a035cf55403ab8a4d5d21213373c -msgid "Offloading" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:77 -#: 82f2342c6f6c4d57a25b2401a404710e -msgid "Enable different types of hardware offloading on the given NIC." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:79 -#: cccb4aabc45b47aeb02e91af4a4e8117 -msgid "" -":abbr:`GSO (Generic Segmentation Offload)` is a pure software offload that " -"is meant to deal with cases where device drivers cannot perform the offloads" -" described above. What occurs in GSO is that a given skbuff will have its " -"data broken out over multiple skbuffs that have been resized to match the " -"MSS provided via skb_shinfo()->gso_size." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:85 -#: 3178743667114d4e82b9f2ebf033928b -msgid "" -"Before enabling any hardware segmentation offload a corresponding software " -"offload is required in GSO. Otherwise it becomes possible for a frame to be " -"re-routed between devices and end up being unable to be transmitted." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:89 -#: 960af2c4d9b54ad695a13005013b6e98 -msgid "" -":abbr:`GRO (Generic receive offload)` is the complement to GSO. Ideally any " -"frame assembled by GRO should be segmented to create an identical sequence " -"of frames using GSO, and any sequence of frames segmented by GSO should be " -"able to be reassembled back to the original by GRO. The only exception to " -"this is IPv4 ID in the case that the DF bit is set for a given IP header. If" -" the value of the IPv4 ID is not sequentially incrementing it will be " -"altered so that it is when a frame assembled via GRO is segmented via GSO." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:97 -#: 7b56a858d43e4d41a6e3346c41f605ab -msgid "" -":abbr:`RPS (Receive Packet Steering)` is logically a software implementation" -" of :abbr:`RSS (Receive Side Scaling)`. Being in software, it is necessarily" -" called later in the datapath. Whereas RSS selects the queue and hence CPU " -"that will run the hardware interrupt handler, RPS selects the CPU to perform" -" protocol processing above the interrupt handler. This is accomplished by " -"placing the packet on the desired CPU's backlog queue and waking up the CPU " -"for processing. RPS has some advantages over RSS:" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:105 -#: 3fcad7523ce5443aac1e7051e6f65d05 -msgid "it can be used with any NIC," -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:106 -#: ad5e537670d042c790304cfbbd450267 -msgid "software filters can easily be added to hash over new protocols," -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:107 -#: 6924eb6f887b4b78bbb7b7604268a1a2 -msgid "" -"it does not increase hardware device interrupt rate (although it does " -"introduce inter-processor interrupts (IPIs))." -msgstr "" - -#: ../../_include/interface-xdp.txt:3 ecf4e5dfd4d0401a95782e9fde09215b -msgid "" -"Enable support for Linux :abbr:`XDP (eXpress Data Path)` on recent 1.4 " -"rolling releases. You must enable it for every interface which should " -"participate in the XDP forwarding." -msgstr "" - -#: ../../_include/interface-xdp.txt:7 2d8d9c08456a46a398aac217918a8e5a -msgid "" -"XDP is an eBPF based high performance data path merged in the Linux kernel " -"since version 4.8. The idea behind XDP is to add an early hook in the RX " -"path of the kernel, and let a user supplied eBPF program decide the fate of " -"the packet. The hook is placed in the NIC driver just after the interrupt " -"processing, and before any memory allocation needed by the network stack " -"itself, because memory allocation can be an expensive operation." -msgstr "" - -#: ../../_include/interface-xdp.txt:14 6595e51d6c1b45c58ca2d01a0acd0c02 -msgid "This is highly experimental!" -msgstr "" - -#: ../../_include/interface-xdp.txt:16 c3302a9950ad4e6a9860bf2630dfbea9 -msgid "" -"Enabling this feature will break any form of NAT or Firewalling on this " -"interface, as XDP is handled way earlier in the driver then iptables/ " -"nftables." -msgstr "" - -#: ../../_include/interface-xdp.txt:20 7281710c88ef41a1b6bda094d2ab4d11 -msgid "" -"Enabling this feature will only load the XDP router code as described here:" -msgstr "" - -#: ../../_include/interface-xdp.txt:24 88c1b4deaec84fa8ae500f042b6561b8 -msgid "" -"https://blog.apnic.net/2020/04/30/how-to-build-an-xdp-based-bgp-peering-" -"router/" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:116 -#: d10a9365cce0463ba28cd8b906a72cf2 -msgid "Authentication (EAPoL)" -msgstr "" - -#: ../../_include/interface-eapol.txt:1 a15a1ab99ac64435a2d104e284646d34 -msgid "" -":abbr:`EAP (Extensible Authentication Protocol)` over LAN (EAPoL) is a " -"network port authentication protocol used in IEEE 802.1X (Port Based Network" -" Access Control) developed to give a generic network sign-on to access " -"network resources." -msgstr "" - -#: ../../_include/interface-eapol.txt:6 3f49b8a8a8ec4f0f94bf5f3453556d8b -msgid "" -"EAPoL comes with an identify option. We automatically use the interface MAC " -"address as identity parameter." -msgstr "" - -#: ../../_include/interface-eapol.txt:12 f15512f3f797418b81a5c4c18181f600 -msgid "" -"Set the name of the SSL :abbr:`CA (Certificate Authority)` PKI entry used " -"for authentication of the remote side. If an intermediate CA certificate is " -"specified, then all parent CA certificates that exist in the PKI, such as " -"the root CA or additional intermediate CAs, will automatically be used " -"during certificate validation to ensure that the full chain of trust is " -"available." -msgstr "" - -#: ../../_include/interface-eapol.txt:29 50963c1bdb3e494bb149a7997ee4811d -msgid "" -"Set the name of the x509 client keypair used to authenticate against the " -"802.1x system. All parent CA certificates of the client certificate, such as" -" intermediate and root CAs, will be sent as part of the EAP-TLS handshake." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:124 -#: c6831cc65ce44a509e9cb3ce531dce60 -msgid "VLAN" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:127 -#: 069a96b30aca40f3ba3ad568b645c487 -msgid "Regular VLANs (802.1q)" -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:1 6219e33c56cc4139ae7a07874103814b -msgid "" -"IEEE 802.1q_, often referred to as Dot1q, is the networking standard that " -"supports virtual LANs (VLANs) on an IEEE 802.3 Ethernet network. The " -"standard defines a system of VLAN tagging for Ethernet frames and the " -"accompanying procedures to be used by bridges and switches in handling such " -"frames. The standard also contains provisions for a quality-of-service " -"prioritization scheme commonly known as IEEE 802.1p and defines the Generic " -"Attribute Registration Protocol." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:9 ab75f226d37042e3b0b08adaaaf83070 -msgid "" -"Portions of the network which are VLAN-aware (i.e., IEEE 802.1q_ conformant)" -" can include VLAN tags. When a frame enters the VLAN-aware portion of the " -"network, a tag is added to represent the VLAN membership. Each frame must be" -" distinguishable as being within exactly one VLAN. A frame in the VLAN-aware" -" portion of the network that does not contain a VLAN tag is assumed to be " -"flowing on the native VLAN." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:16 165034dde5624ceba1d2f7b2b9c2ba97 -msgid "" -"The standard was developed by IEEE 802.1, a working group of the IEEE 802 " -"standards committee, and continues to be actively revised. One of the " -"notable revisions is 802.1Q-2014 which incorporated IEEE 802.1aq (Shortest " -"Path Bridging) and much of the IEEE 802.1d standard." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:21 2fc81ad16c104e8c93740c6da9764c79 -msgid "" -"802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. " -"The term used for this is ``vif``." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:26 e3a0ff05b9e94a41a60fd2b2008ec779 -msgid "" -"Create a new VLAN interface on interface `<interface>` using the VLAN number" -" provided via `<vlan-id>`." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:29 3abdc1a4f9254146b560b28e3bc2c4ea -msgid "" -"You can create multiple VLAN interfaces on a physical interface. The VLAN ID" -" range is from 0 to 4094." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:32 0dd1381b842c4318a4eb76bba21b0b11 -msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:134 -#: c587c6e88f074a658738e0028280fea4 -msgid "QinQ (802.1ad)" -msgstr "" - -#: ../../_include/need_improvement.txt:11 1d84fcf5f183415885672bf973640313 -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 6a2a314ccdb141948437c5eb4d419d1e -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:3 25717d0a60f44f119c1db8d97999649e -msgid "" -"IEEE 802.1ad_ was an Ethernet networking standard informally known as QinQ " -"as an amendment to IEEE standard 802.1q VLAN interfaces as described above. " -"802.1ad was incorporated into the base 802.1q_ standard in 2011. The " -"technique is also known as provider bridging, Stacked VLANs, or simply QinQ " -"or Q-in-Q. \"Q-in-Q\" can for supported devices apply to C-tag stacking on " -"C-tag (Ethernet Type = 0x8100)." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:10 -#: 4fa28700b7024f18afa866d5288bb37e -msgid "" -"The original 802.1q_ specification allows a single Virtual Local Area " -"Network (VLAN) header to be inserted into an Ethernet frame. QinQ allows " -"multiple VLAN tags to be inserted into a single frame, an essential " -"capability for implementing Metro Ethernet network topologies. Just as QinQ " -"extends 802.1Q, QinQ itself is extended by other Metro Ethernet protocols." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:16 -#: 90fcad3f700a4f12bd0962b7e2d41e4f -msgid "" -"In a multiple VLAN header context, out of convenience the term \"VLAN tag\" " -"or just \"tag\" for short is often used in place of \"802.1q_ VLAN header\"." -" QinQ allows multiple VLAN tags in an Ethernet frame; together these tags " -"constitute a tag stack. When used in the context of an Ethernet frame, a " -"QinQ frame is a frame that has 2 VLAN 802.1q_ headers (double-tagged)." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:22 -#: 727cea9d32d245a5b05a13c8a229c905 -msgid "" -"In VyOS the terms ``vif-s`` and ``vif-c`` stand for the ethertype tags that " -"are used." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:25 -#: f4b7266a17344261a90073d74b4e289a -msgid "" -"The inner tag is the tag which is closest to the payload portion of the " -"frame. It is officially called C-TAG (customer tag, with ethertype 0x8100). " -"The outer tag is the one closer/closest to the Ethernet header, its name is " -"S-TAG (service tag with Ethernet Type = 0x88a8)." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:141 -#: ae7bd6d3ab1046f0a4dc0656649e0736 -msgid "Port Mirror (SPAN)" -msgstr "" - -#: ../../_include/interface-mirror.txt:1 11a17100702f410db323e7efdbfb760a -msgid "" -"SPAN port mirroring can copy the inbound/outbound traffic of the interface " -"to the specified interface, usually the interface can be connected to some " -"special equipment, such as behavior control system, intrusion detection " -"system and traffic collector, and can copy all related traffic from this " -"port" -msgstr "" - -#: ../../_include/interface-mirror.txt:6 3f9db384eca74560a46fb145111b7b8c -msgid "" -"VyOS uses the `mirror` option to configure port mirroring. The configuration" -" is divided into 2 different directions. Destination ports should be " -"configured for different traffic directions." -msgstr "" - -#: ../../_include/interface-mirror.txt:13 5f79058e8f034f8eb92d6e4b513c84f7 -msgid "" -"Configure port mirroring for `interface` inbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:16 2aab909aa60e47c996236fcec753b240 -msgid "Example: Mirror the inbound traffic of `eth1` port to `eth3`" -msgstr "" - -#: ../../_include/interface-mirror.txt:25 1cc17e57e4b74bdb940817570183742d -msgid "" -"Configure port mirroring for `interface` outbound traffic and copy the " -"traffic to `monitor-interface`" -msgstr "" - -#: ../../_include/interface-mirror.txt:28 7fde09dcf26147e4941f382164d5d4da -msgid "Example: Mirror the outbound traffic of `eth1` port to `eth3`" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:149 -#: 4622f2d460674fcda52627d89af0026f -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:153 -#: 20d2dd9b87b04d29a052da49e2304d97 -msgid "Show brief interface information." -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:167 -#: 229f9a1b17b146e6833082411da1734c -msgid "Show detailed information on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:186 -#: 85176122830a4f3ea117391dd001bd54 -msgid "Show information about physical `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:227 -#: 68fd1830fbce40d4ab41a425f6d5081d -msgid "Show available offloading functions on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:259 -#: 40d23968c4064059970f596d6f8bba0a -msgid "Show transceiver information from plugin modules, e.g SFP+, QSFP" -msgstr "" - -#: ../../configuration/interfaces/ethernet.rst:296 -#: e4ce58406b8d45b996ed216c74b661c3 -msgid "Display XDP forwarding statistics" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/geneve.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/geneve.po deleted file mode 100644 index 3c185434..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/geneve.po +++ /dev/null @@ -1,457 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/geneve.rst:7 -#: 45b4ec6af6be411187dee6623bb1b8f3 -msgid "GENEVE" -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:9 -#: a5ca4b4496264335baf8827148c96ddf -msgid "" -":abbr:`GENEVE (Generic Network Virtualization Encapsulation)` supports all " -"of the capabilities of :abbr:`VXLAN (Virtual Extensible LAN)`, :abbr:`NVGRE " -"(Network Virtualization using Generic Routing Encapsulation)`, and " -":abbr:`STT (Stateless Transport Tunneling)` and was designed to overcome " -"their perceived limitations. Many believe GENEVE could eventually replace " -"these earlier formats entirely." -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:16 -#: 99a59ee4244f4c0883054721bb4c0748 -msgid "" -"GENEVE is designed to support network virtualization use cases, where " -"tunnels are typically established to act as a backplane between the virtual " -"switches residing in hypervisors, physical switches, or middleboxes or other" -" appliances. An arbitrary IP network can be used as an underlay although " -"Clos networks - A technique for composing network fabrics larger than a " -"single switch while maintaining non-blocking bandwidth across connection " -"points. ECMP is used to divide traffic across the multiple links and " -"switches that constitute the fabric. Sometimes termed \"leaf and spine\" or " -"\"fat tree\" topologies." -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:25 -#: 00c4bae64e2147aab606950605503588 -msgid "Geneve Header:" -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:39 -#: 78bede1ec9ef4deea9b7e5670d56b113 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:42 -#: eecd0a480145411a9aed6f6743c06cff -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 0bd1260575664a28a98b7395129f1aa2 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 5f3f55bec0b5466cad218f980e2f9edf -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: 5ff9c096088447b78f34acf3ec9da03d 0d3a22874f754d7da0ce4f056e7bc1ba -#: 8c72f6882b6d48b79af833bc031b654a d31543e329e340d285af99a5acddf8f6 -#: 36c1cd4eb1eb4e68a428e156149c5d7e b56d141c7edd49bd9d4cb588c5769c8f -#: 1f7a8b05e6714c8c9b01e29a970a3ee6 1b15a161400e4d84a98c5614cde7ac54 -#: 26c1f3ae54cb4352afac06a96dd80446 df61e3d8c62847efb3942c22877919e0 -#: 3b485d8a7cdc430eb545ab2d35341ad2 9053c615aeab4a5fa4068a2f2d80eac2 -#: 452615d4373f41c393a6b703597a720c 3e0d7093f2fe432a8168c4e63e7d5031 -#: c25cac76452d4380b2b582e4b6c2c41e -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 dd909e7c98a84d5ba1be6cb97ed6af12 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 92693613cc1f4ba2a20453bfa091a52c -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: 6098809a41a74db1b0ea66957bd88975 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 94f184f12b1740e7a2761a975100231d -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 5f640d13ac97483199d96591970e4791 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: b181651d8f42471fa8e9ed0fd6fc2773 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: 02b60a2dbbd145be9a468d1c427f36cf -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: e80745aa6b9e41f5bdbef0a9cc66f0ca -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 526bbd540da242e9a5ed0da7a58bd373 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 c8a30d7447164b86ba0ce6bfa5fb76b0 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: cb7d40339f684194b92a3858927474bb ae789a739dfc49b3aec9de3c776b994f -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 65057095dc9745fcb9263045afa1d934 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 60fb2d61b5114149a04ab14d59258642 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 0f2cd078626040c8ac69bbfb78601a3f eb605f7e65d2421db06a443e1a24686c -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 65f6ed70d35f476b9942a753870c4ab5 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 031a9bbf13644af398d293a3c35cd0f0 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 1f42962643a84d0297e691d1db6a3a1e -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 422f719f999046fba17d05d8b76c7f72 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 533c54b53f6b4b4eabde1ece11e3c087 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 31b9942079c944f384444a699ec20fc0 6af2fe7715584f82b886c0f0a39d53be -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 d363d626596e4469b613a645ddb88f26 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 8be6aad2ae50429c86dd1cd823da40a7 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 4f006dcf0b05439f8f4bce16d097e08d -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 2a833dcdf79c4f27b411e1f3ba5c2c5f -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 7bd4cd3b2c6d4ed9b1b8220b7be38aab -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 dad407b4fd70478a8c4117d21b852586 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 2968819d0f72417fb5f7d8e83d0a6ead -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 94051b647f6744de8404f9fa5cd1c038 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 190779bcaa6a4443aa44f14f337a960f -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 9794fa87412541a2a8bcb7bd960f886c -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 d8f64bde988046a6b13e5d593fa1cb43 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 9afcc57695994e32a9ace37efa6ce907 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 a898f51b5a5549a0a928c3a6a5699be0 -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 6d72ad7a000a4ee388652bf980338fe5 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 292655601ca341119b46cf186d3619a7 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 0c42fe8715f14991a2938afb72eeb3ee -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 5fdd8bb881f842aa9cf6e1295c09320d -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 b4d56acb38754eae870f7681ca3d61ef -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 3afb9c16a0d54368b5003d4b762dba09 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 93459971979c4e8d99852189ff9f367a -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 6439a622b49a439f9824724b5b24eb0f -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 1641933a0b36450dbaaf123cf7b8cda1 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 da59d7685f3d4a0e8426f61b70a14dbb -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 d696fba5987240c787add034c366ffcd -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 a738f2d490f444c5b2092d32970bc76e -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 73943e917da84e298a26879f4fa1db4f -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 83c3ef51d3ad470dbefec7d2e6c915e5 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 f6441bd659e8494cb8d21032804f9a58 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ae818d0f1d024af4b344bcef6f3999fa -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 8cc686e77a784579bd8b80ccdbca673e -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 422932b961684d54a019d464df13e008 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 8b529a66b32a4916806f909b25fcb69d -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 29c798fb8a5d4c34bbce96cd4c808852 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:49 -#: 19a525dd9d7e4a82b88790638f21b301 -msgid "GENEVE options" -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:53 -#: 714bf1023a974187bd62fa685f82a1ba -msgid "Configure GENEVE tunnel far end/remote tunnel endpoint." -msgstr "" - -#: ../../configuration/interfaces/geneve.rst:57 -#: d8c9d5a189d7425e803af2c35e998cb2 -msgid "" -":abbr:`VNI (Virtual Network Identifier)` is an identifier for a unique " -"element of a virtual network. In many situations this may represent an L2 " -"segment, however, the control plane defines the forwarding semantics of " -"decapsulated packets. The VNI MAY be used as part of ECMP forwarding " -"decisions or MAY be used as a mechanism to distinguish between overlapping " -"address spaces contained in the encapsulated packet when load balancing " -"across CPUs." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/index.po deleted file mode 100644 index de23a87a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/index.rst:3 ab9a70daf6804d80807e63d01d94250f -msgid "Interfaces" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/l2tpv3.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/l2tpv3.po deleted file mode 100644 index 17f9bdf2..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/l2tpv3.po +++ /dev/null @@ -1,580 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../_include/need_improvement.txt:11 dac5eab4a62649579e9185de834b69b6 -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 071e7ddff14e4ba8b11b2c7f4ad5fd72 -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:9 -#: 80a5f3ff52de494784fa6451a877bfda -msgid "L2TPv3" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:11 -#: 2bf52e340b274dbb85ac0969b5e243c1 -msgid "" -"Layer 2 Tunnelling Protocol Version 3 is an IETF standard related to L2TP " -"that can be used as an alternative protocol to :ref:`mpls` for encapsulation" -" of multiprotocol Layer 2 communications traffic over IP networks. Like " -"L2TP, L2TPv3 provides a pseudo-wire service but is scaled to fit carrier " -"requirements." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:16 -#: 216d69c5f641482eb036c69e29e2332f -msgid "" -"L2TPv3 can be regarded as being to MPLS what IP is to ATM: a simplified " -"version of the same concept, with much of the same benefit achieved at a " -"fraction of the effort, at the cost of losing some technical features " -"considered less important in the market." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:21 -#: 0e315d62f88649fb94136e727d13132a -msgid "" -"In the case of L2TPv3, the features lost are teletraffic engineering " -"features considered important in MPLS. However, there is no reason these " -"features could not be re-engineered in or on top of L2TPv3 in later " -"products." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:25 -#: 8b3d6d6ceae4443988d8a858efb7cc76 -msgid "" -"The protocol overhead of L2TPv3 is also significantly bigger than MPLS." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:27 -#: 09dcef77322249d6af4e20b9d9181480 -msgid "L2TPv3 is described in :rfc:`3921`." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:31 -#: 951b0e5015c5404c84f7938e83c7a3b1 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:34 -#: 53bce1a1d575491895ac3971b1847dfd -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 13557021f7714f29ade0991d84b3c218 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 ae162220fd0d434894a00c3b2a952cb1 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: afbf098123304ddb965c36cf484f762b 29300d566a8e4409aaad04523d51b3e9 -#: 86f8e7fdd7814842940850cfca7eaa1e abebefba11ab4a48b68223304d2bd911 -#: 18aaebc9558f47e897c5ee1d4519536d 74fefa37e8ea45f7bcf7a28c1ba0de13 -#: f7301e227ffe428fbeacaa810f2bbc9c 14dd6f6e15dd449ea6972ddf00c953bd -#: 72b582717cf44fcabc90f936a60aca2b 6479d4af762d4496a56200bdf09f22c9 -#: 2909f91a4730450198de33f4b47f42b2 7481645a67ba41e5863759c0da7e2823 -#: 852a18cd45be455c94431939d42dbd55 5fef7a7859564e8fbfe0dc27988b289b -#: 70eaf5a1e7454bacb00e71312ac33106 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 012103d50444459c8666e360b3a4ee12 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 c61357b8ff7b4ad0b8914576e4de9e08 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: c513b326250c487cb9b646f3ccd2f4db -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 476ba4b12d384c20b6bff637b967328d -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 3322f3b3908243e5aa9733d09f5b233b -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: ab684d4842654a70ad523f94a5fe59bf -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: 5f8fcb112b984d5da992d07edf3956ac -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: 124fcb56a97847cc8782c10fa6701c75 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 bff4a06d0cfc44f0bb8c9089c76f7410 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 1dbc58521cd74a27b6f7fbc68da706fc -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 9387dacadb164835992002a875ac9b48 30a6d9eacb2f4fcb8257278ce4c0bc90 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 95a1b2e32dcf45739425deefbc695991 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 5987b8980526411b94948ce0c2e2380b -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 973ad0d54ee84a1ebe2fbcd7679476f2 85448214c03f4f9989a83c897efa16d3 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 3d3a5ace69d847078d19754826ab1c56 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 13a3b17ddd2a43c7887cbf5ded0b1493 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ba800bef1df04ca0be66e8f990395de1 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 1a884453bc3f4677b7e9f29a6e42b3bd -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 a0708a24cf3746df8083206d06a6b0ae -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 456a7407877643a58c8e4b325bd0bdf0 cd1ead00693c46049ed0da7f7bdf2483 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ddbcb5ca85564306bf295473762325bf -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 5b3597d7c156434f8a8a33f769e27b74 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 78a38ccdebaa404bb72b2d2424fecbb3 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 bd6dc03be05c4c719341e32545491d5d -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 7cda99f59f4c4c8a92d7a69e92110165 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 526574e9cd814565a961af6d64a173f5 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 bbd3a35fa55043e1a701b7311bc7235f -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ae6007ef432f44c58faa2cacf1ee0a3d -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 164a392dd5ce4fb78902dea939863c43 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 e83d949b2a4d4e1c9e52ffe79eb39fdd -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 c6d21f7f12af468495c7e7e4ca0e92df -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 b87a4a5f245e43f0a104c9a5d871fbff -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 1769d9bb67e84d2baed91e871bcf203c -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 54b6d73f53484ca385c7d4c0d8bf6346 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 f12e3c9892164e1abd0d84a792bef125 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 71b5abe710f9417abe718324e558571a -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 4f78c6f9ca1c40ffbd8b6989644b2082 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 11d4c72e6ec7449fac379d34377debc0 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ac84a9aeb69a450bb22813c03909f368 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 e3f4b1e106444b8eaf9bd7f830f725a5 -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 911ea297c97341d4966b9d4cff837f1c -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 cbbbdb2c2b3946cab9a40c8f8acb9b77 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 7700f2a8fa7240ff824903e4dff23d9c -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 c0143891bc134edabbdcc0a78be348c2 -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 cc2275903b3a4186bbaccd0902bde73c -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 521f27630ece4e259c0a5fcaa1a7c752 -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 dd3974c16c034d66bb5e7ca10146e28c -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 fd2213b4663e474d9bbaa870b0ad11c2 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 3ce57f1c84814f48b1b67a4b2a720feb -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 f085c79681904d8bab80bdff2777d466 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 4219dd2456994dc395ec71dca16afcd4 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 4a34e9b11fa44afd925bcf52a7f82b78 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 4676b07efb6f494b99975c985855a52d -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:41 -#: 18a6be25898f4db5a7717f929bb48040 -msgid "L2TPv3 options" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:45 -#: 9bc626a7ab75448694af2d36560829f8 -msgid "" -"Set the encapsulation type of the tunnel. Valid values for encapsulation " -"are: udp, ip." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:48 -#: 2da504259ec446f0b458bb38483e80d4 -msgid "This defaults to UDP" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:52 -#: 336d351066eb47e98e478410d30a0528 -msgid "Set the IP address of the local interface to be used for the tunnel." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:54 -#: dffb149d4a1943e3be5693211485f68e -msgid "" -"This address must be the address of a local interface. It may be specified " -"as an IPv4 address or an IPv6 address." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:59 -#: 443629a545b2426d9b51246454b2085c -msgid "" -"Set the IP address of the remote peer. It may be specified as an IPv4 " -"address or an IPv6 address." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:64 -#: 97ecc068147d42169f97590f08382641 -msgid "" -"Set the session id, which is a 32-bit integer value. Uniquely identifies the" -" session being created. The value used must match the peer_session_id value " -"being used at the peer." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:70 -#: 8bad611ba2c345168c39053947c551f6 -msgid "" -"Set the peer-session-id, which is a 32-bit integer value assigned to the " -"session by the peer. The value used must match the session_id value being " -"used at the peer." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:76 -#: ../../configuration/interfaces/l2tpv3.rst:81 -#: ab4120f9461a4eb6876dafb5b12913bb 6c450221982941e583041a1368f41d0d -msgid "" -"Set the tunnel id, which is a 32-bit integer value. Uniquely identifies the " -"tunnel into which the session will be created." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:86 -#: 56b231ed8c3143d49555db70fdd7bc3f -msgid "Example" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:89 -#: 5e39b2768e4a4771b457b24f537a94c4 -msgid "Over IP" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:105 -#: 7d268ef3a29c44a594f5686f0febe4e8 -msgid "The inverse configuration has to be applied to the remote side." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:108 -#: f0985c4e7e7c451980ba11f5b3ce3bb2 -msgid "Over UDP" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:110 -#: d364aaf5fda74874a570fa02c19cb0de -msgid "UDP mode works better with NAT:" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:112 -#: 3059e0525fb649a4b0f6a74448414ca8 -msgid "Set source-address to your local IP (LAN)." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:113 -#: c7b584f9e86a4242887e0ad4e5900cf9 -msgid "Add a forwarding rule matching UDP port on your internet router." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:131 -#: 650f57ef5adf4994b1dba720ee409a19 -msgid "To create more than one tunnel, use distinct UDP ports." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:135 -#: 65bd503a18ff4579ad81e37d7b21c096 -msgid "Over IPSec, L2 VPN (bridge)" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:137 -#: 074562e9f51941d69ab5372475e487c3 -msgid "" -"This is the LAN extension use case. The eth0 port of the distant VPN peers " -"will be directly connected like if there was a switch between them." -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:140 -#: 053c02da02e34ab0a45904846c00a873 -msgid "IPSec:" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:168 -#: f453f04187964087880cfa6c7e02f12c -msgid "Bridge:" -msgstr "" - -#: ../../configuration/interfaces/l2tpv3.rst:179 -#: c145c0fc701d4685bb3527fdabc35cd3 -msgid "L2TPv3:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/loopback.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/loopback.po deleted file mode 100644 index 5e298549..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/loopback.po +++ /dev/null @@ -1,97 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/loopback.rst:7 -#: 55644a7b018b4f9e83697cb41a249931 -msgid "Loopback" -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:9 -#: f8adf4b7ba95412ca5a6a589f2222521 -msgid "" -"The loopback networking interface is a virtual network device implemented " -"entirely in software. All traffic sent to it \"loops back\" and just targets" -" services on your local machine." -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:13 -#: 230f7e52cc1b4dc8ba555f239060522f -msgid "" -"There can only be one loopback ``lo`` interface on the system. If you need " -"multiple interfaces, please use the :ref:`dummy-interface` interface type." -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:17 -#: 6445f25853924a4a9dd23f3b0ea43cf5 -msgid "" -"A lookback interface is always up, thus it could be used for management " -"traffic or as source/destination for and :abbr:`IGP (Interior Gateway " -"Protocol)` like :ref:`routing-bgp` so your internal BGP link is not " -"dependent on physical link states and multiple routes can be chosen to the " -"destination. A :ref:`dummy-interface` Interface should always be preferred " -"over a :ref:`loopback-interface` interface." -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:26 -#: c40cbdedadf64b698cc2b823e8487c41 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:29 -#: 88e688f5abae46e29d7b189e2d698eb8 -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 04883830808f47caa328da33c3f772a0 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 04fa13d37f734c538cd652110c898d9a -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 599d98cdcccc464e834e86b57f9e82e9 -#: 097adbe514f84a78be84b483863f1e1d -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 c9994bbc256a4c019fe16ea0a0f56cc6 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:41 -#: fb00faeea21a47909b9ae10b814c8f90 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:45 -#: dac70a23e95241bbbeae30a23a14d3d7 -msgid "Show brief interface information." -msgstr "" - -#: ../../configuration/interfaces/loopback.rst:58 -#: 0a4d8bbfb8614138839fc7e44ecfb175 -msgid "Show detailed information on the given loopback interface `lo`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/macsec.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/macsec.po deleted file mode 100644 index ea7db0f8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/macsec.po +++ /dev/null @@ -1,755 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/macsec.rst:7 -#: 2e5055bbbd0f42c8a64518d17a882b53 -msgid "MACsec" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:9 -#: d73b98a748ba49febca474314dab4942 -msgid "" -"MACsec is an IEEE standard (IEEE 802.1AE) for MAC security, introduced in " -"2006. It defines a way to establish a protocol independent connection " -"between two hosts with data confidentiality, authenticity and/or integrity, " -"using GCM-AES-128. MACsec operates on the Ethernet layer and as such is a " -"layer 2 protocol, which means it's designed to secure traffic within a layer" -" 2 network, including DHCP or ARP requests. It does not compete with other " -"security solutions such as IPsec (layer 3) or TLS (layer 4), as all those " -"solutions are used for their own specific use cases." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:20 -#: 0e4d47c6be1a43ad89535ec3835c9df9 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:23 -#: 3486851fad2442d5afc94c3ca4aee1e9 -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: 8751d316a248448b97a8f28caa3abd2f -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: 4ea434d98ae141e9867ec3059b3f4237 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: e622f6317ea843c5b0fe08abce9d2dae -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: d5721cb99cbf4e6ca2e29a9b8785d506 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: 06437c2f4cfe408c9e84a4331de8bbbf 269dc6daef1f412ebd797ba5cecb8aff -#: 87a8b9c2d52c4762a5cb361d079eb3ff e03300e3f4f649d0ba411c4811eac739 -#: 0dc3cb15bc99417abd58bd8b33c2f549 a6aa5027bcd6401abddb0b980e27846f -#: 067416b2c533473f874006de24383dba 04e1740c282b4ac8b8cda6f4059387e5 -#: 7cd21bf76fe3429c9f9a356cf24f8c7c 374d7f584bf34bfba10784e551745f73 -#: a154d5ee25fe4b0ab2dd3e92c072afee 7b11e439aacb4ba283d6706cf513cf60 -#: 3e530deec81940d8a0d2778f18998b99 a532ac8d2a034c1c9ce2a2fa0621c7db -#: 0ae78fa4d7d343d6a0aa41fba2849bea 2c960c765f3a4900b2602c454c90d14d -#: 3a609c8e2c6b4681a10873ad5c35c2d8 f329577b845e49a2a1f111b81146b39e -#: 05843c35c6da4e4b8a62479371eba9c1 ad21fe06540f4d7cb90b4e68818ad898 -#: 916661fdbdf5473a85c0c3f329bfe949 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 22afef3c31b44127956c70209e89c213 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 528a19d4df23464bad7387d43230fd91 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: 78e3477e120944f2b37ab1051345d113 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: e2f1af4fa63646dba21c300c9622a239 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 160166919805423894abcb6b9eeba549 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: d4a317b5616a4dcb92e163661cdae93a -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: 1add1e20c2714f5188e90613c86bca44 -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: 570e5cd17bfc4c5c9a3d37602ec6352d -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 d5b3cd87e2784e14adf67f1e66bc7e5d -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 db34ce847b9d442e979b0eb727555539 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 21d19e9d7a4a4d868d446ffb45ad8541 5401986e67d84490acdecfea223726f4 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 1a612625c0554742888b94bd97ab7c19 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 1af15ba0bc70411a9b6d3fe2ec9d1329 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 93e252c0f7fa42508aace215ab27e4ef eb13c2a11ca24eed84398dc2f8ce5aca -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 a505747ae7fe4a00b034e86c4a2c7b37 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 a24873a9225342f2a50988e131ab27fb -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 77d963b11efb4666a7dbda53be1fb66a -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ba187fb38181491ba4df460f48f18540 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 29f3677deb3944c784c8c2f8ac3e4893 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 46580566b44340e180e1c8ff6654dfca 5e227fc000824cc390ec435ddd6abed4 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 734a03a9c9d445479c741bf414cc765d -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 b63043f49c7b460a90661cf0c68c1590 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 159589d1bc404019a3b9899fa9284c19 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 af7cc3c458a44e35acd9de1db3ec2a1c -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 de1558e075e84322b426407576c69c70 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 12c38373e4b54cf48721b9a27fe497ca -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 378a427e7c374d33944b96027d9910ec -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 fa61304409294a93a95bd32624eaab7d -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 4fd0b026f881413895bb1384fcd71350 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 e024f2ac17c1495d81149bc9f94ad374 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 d789fa8f75634057b829f85f67d003fe -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 b2eef40be6374f81b54869e2b41f0bea -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 2ea3ef2222594abeaf1d3180b79ceb6d -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 8d5284157e70416ea393a5281c21a677 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 f497f36ffbec4465b5b74dab8767fa86 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 43892dd27cfe436daf260c4fae43a926 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 07ff120cb9484682b53103be3cc89ac7 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 94e426aa727c4672b91b5156043d8a5b -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 70606918dbfc4d668fefa2a58fbb0c8a -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 351974b6df6c45bca221101cd497febe -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ea6233a921d844fca468596715013d3b -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 84fafe4541ac4ecfad407e4a81574a5f -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 0411b4d24983486b9aee22041df9842c -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 d348c799b88445208300675801f4ae9b -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 e8474f2419544aa5908e89e436a83810 -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 80f45edf9dfc49a9bb5f46058c9a92ac -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ace3f3fa32604d78abd7010e1b9cdeed -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 5bbb09d0b14c41648b95900cadba40b1 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 22229373557b481080e294ba5eb23a3b -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 4f6d0b65061243e691ba12f9a7429264 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 9932c01917f94c91a6cdb69a6c4f9e77 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 071ce023f4c74493b4d59b66d526aa11 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 0e55454b89ff467199c3ce3c971be684 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: 5648a890403d4783872c22980ff917bd -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: e11aabb27ee845e99189b9aab87e66a9 -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: bf2b6dee7ff648ddad300c38ae4df749 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: f5a2003de78145c781a18e67d1d0f23c -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: 1e8f1cc4cf9340a48bd7ae8da278d69e -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: 07a7c11083d4461a9cba42bdbad72846 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: 5628888167354514897413213275f049 -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: e431d22b4e5140138f01e26ecc21e51d -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: a1f44b38db70478bafd74d8ad59d11a5 -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: 3f0dfb732df244e4a2552cac26168716 -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: 304aa980a5bc41519efd9226fe2cace7 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: b05b3017f8ce49fb999f3010d88a8412 -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 891e4c1bdac042c5b5812d91ea44bbc2 -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 565b0a36d3294d1292c3aa1a75995850 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: 89b4f6dc97654604a8c145da2457fd8a -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: 3009eb83996b443ba1a0abfadb1f2c83 -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: a2e7662a772841a0ab67356f3bc2282c -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: 9a640ad9e4ac47fc80607e18143b9338 -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: aa52a825eec6448097f16fabbfa72e74 -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 83da7580f03d40d094eb536a65218e03 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: a8e6407d4ec047c18679917baf7f9c0b -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: 824ba646f74c4647b6a12ee920c3a31c -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:30 -#: 28e43e4c2347477e8aedeffa0eeb283c -msgid "MACsec options" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:34 -#: 6e6ea53962fa40dc95fbea88bb89c8f3 -msgid "" -"Select cipher suite used for cryptographic operations. This setting is " -"mandatory." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:39 -#: 980c197f21d54ede9f33e94ae960d9ac -msgid "" -"MACsec only provides authentication by default, encryption is optional. This" -" command will enable encryption for all outgoing packets." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:44 -#: 81ae2e7401c244c5b8cbb9151ec7b128 -msgid "" -"A physical interface is required to connect this MACsec instance to. Traffic" -" leaving this interface will now be authenticated/encrypted." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:48 -#: e43d4cf09b6846d39b37d9b3103547d7 -msgid "Key Management" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:50 -#: 105a3fe45bfd4c258668c4bb300e79ce -msgid "" -":abbr:`MKA (MACsec Key Agreement protocol)` is used to synchronize keys " -"between individual peers." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:55 -#: 55c4d4cd0a0c4de18bccdae3f25a923a -msgid "" -"IEEE 802.1X/MACsec pre-shared key mode. This allows configuring MACsec with " -"a pre-shared key using a :abbr:`CAK (MACsec connectivity association key)` " -"and :abbr:`CKN (MACsec connectivity association name)` pair." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:61 -#: 0285c48be69c433292ed76f4a50d1475 -msgid ":abbr:`CKN (MACsec connectivity association name)` key" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:65 -#: eefa15dec5604ccdb56c037c43c4794b -msgid "" -"The peer with lower priority will become the key server and start " -"distributing SAKs." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:69 -#: fb1f4822b75843caa708ff6a59edc8f0 -msgid "Replay protection" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:73 -#: ce3ecb05a5e04e0ebfe34699c579170c -msgid "" -"IEEE 802.1X/MACsec replay protection window. This determines a window in " -"which replay is tolerated, to allow receipt of frames that have been " -"misordered by the network." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:77 -#: 51ac299d65e64cc28206e7d43d6994ff -msgid "``0``: No replay window, strict check" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:78 -#: d2c2a2c9df8143f8a3ecf728454d888b -msgid "``1-4294967295``: Number of packets that could be misordered" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:82 -#: 8d20b736031e439ea73a8741c61bdab6 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:86 -#: 9c25c3f946c24608994c201237df822d -msgid "" -"Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key 128 or 256 " -"bits." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:95 -#: 46bc8631094e42499b94c12a1d2153f7 -msgid "Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:104 -#: d31d415763a7452395fe592d870ac863 -msgid "List all MACsec interfaces." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:118 -#: 4235e0d04b1f4853a2e6182df25d9c86 -msgid "Show specific MACsec interface information" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:129 -#: ced335e1a9394ae7893be1481e04e087 -msgid "Examples" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:131 -#: 2649b8b5966c4936bec7f88b2a831c83 -msgid "Two routers connected both via eth1 through an untrusted switch" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:132 -#: 2383a835685440f49157408ebe6b782d -msgid "R1 has 192.0.2.1/24 & 2001:db8::1/64" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:133 -#: 254f4d17217c475ab070b2467aaadcfe -msgid "R2 has 192.0.2.2/24 & 2001:db8::2/64" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:135 -#: 0d435b68f5104bcd9ccca68dbcb4057c -msgid "**R1**" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:147 -#: 0d287f9e8ee74d538ec16fd0afbaf75d -msgid "**R2**" -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:159 -#: 4cc62649c7654b7b925bff23a92c3ad7 -msgid "" -"Pinging (IPv6) the other host and intercepting the traffic in ``eth1`` will " -"show you the content is encrypted." -msgstr "" - -#: ../../configuration/interfaces/macsec.rst:175 -#: fd620090261d4cc4992b6d8cdaa15ec8 -msgid "" -"Disabling the encryption on the link by removing ``security encrypt`` will " -"show the unencrypted but authenticated content." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/openvpn.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/openvpn.po deleted file mode 100644 index 4672d90c..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/openvpn.po +++ /dev/null @@ -1,616 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/openvpn.rst:7 -#: 49a4e313af8b47da8d0c2c000d721255 -msgid "OpenVPN" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:9 -#: 24c641c02ee1432b85457380d5a9442e -msgid "" -"Traditionally hardware routers implement IPsec exclusively due to relative " -"ease of implementing it in hardware and insufficient CPU power for doing " -"encryption in software. Since VyOS is a software router, this is less of a " -"concern. OpenVPN has been widely used on UNIX platform for a long time and " -"is a popular option for remote access VPN, though it's also capable of site-" -"to-site connections." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:16 -#: 8705ef07eb7c4133898d4093647e1e6e -msgid "Advantages of OpenVPN are:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:18 -#: 700f4b6c11f74f3aadff507e7d8fa925 -msgid "" -"It uses a single TCP or UDP connection and does not rely on packet source " -"addresses, so it will work even through a double NAT: perfect for public " -"hotspots and such" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:22 -#: 698154b399704e69872d5e27747d0c47 -msgid "It's easy to setup and offers very flexible split tunneling" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:24 -#: 79100fbc787946c29e00895de9a6cce2 -msgid "There's a variety of client GUI frontends for any platform" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:26 -#: e023bf4ba8eb42e2a917425162c2fb05 -msgid "Disadvantages are:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:28 -#: c03b6c6fdace492db97013b65896e7ff -msgid "" -"It's slower than IPsec due to higher protocol overhead and the fact it runs " -"in user mode while IPsec, on Linux, is in kernel mode" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:31 -#: 1f713d3a0e7745159c65166081a76f37 -msgid "" -"None of the operating systems have client software installed by default" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:33 -#: 6285fb18d721436593aa4e1da721f476 -msgid "" -"In the VyOS CLI, a key point often overlooked is that rather than being " -"configured using the `set vpn` stanza, OpenVPN is configured as a network " -"interface using `set interfaces openvpn`." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:39 -#: ed41362196c84a52b4a00426cb2ea4d7 -msgid "Site-to-Site" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:43 -#: a42219859326463ebc9da64095f2cade -msgid "" -"While many are aware of OpenVPN as a Client VPN solution, it is often " -"overlooked as a site-to-site VPN solution due to lack of support for this " -"mode in many router platforms." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:47 -#: b35c1ae6e30441548999d4badacc81bb -msgid "" -"Site-to-site mode supports x.509 but doesn't require it and can also work " -"with static keys, which is simpler in many cases. In this example, we'll " -"configure a simple site-to-site OpenVPN tunnel using a 2048-bit pre-shared " -"key." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:51 -#: d9b2fd8cf2a24b1f9b5e3c8259826240 -msgid "" -"First, one of the systems generate the key using the :ref:`generate pki " -"openvpn shared-secret<configuration/pki/index:pki>` command. Once generated," -" you will need to install this key on the local system, then copy and " -"install this key to the remote router." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:55 -#: 2ea4c91c77e94f3e9c0972c6550484e1 -msgid "" -"In our example, we used the key name ``openvpn-1`` which we will reference " -"in our configuration." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:58 -#: ae8ce996d0764647b187fa432ab5da73 -msgid "" -"The public IP address of the local side of the VPN will be 198.51.100.10." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:59 -#: fd9f2b1633cf4882b0fe035111d5015d -msgid "" -"The public IP address of the remote side of the VPN will be 203.0.113.11." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:60 -#: 8fb58cd1d9e54b9f84f450766236f4b1 -msgid "" -"The tunnel will use 10.255.1.1 for the local IP and 10.255.1.2 for the " -"remote." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:61 -#: 2f7dd832268b45b8978f378358855280 -msgid "The local site will have a subnet of 10.0.0.0/16." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:62 -#: e7fd5219fca14a3c921fd7865e877a2b -msgid "The remote site will have a subnet of 10.1.0.0/16." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:63 -#: cda1b065f9ae40b29f5ab53a0575ee26 -msgid "" -"Static Routing or other dynamic routing protocols can be used over the vtun " -"interface" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:64 -#: 59ba809b2f984230860ef133ce4431d2 -msgid "" -"OpenVPN allows for either TCP or UDP. UDP will provide the lowest latency, " -"while TCP will work better for lossy connections; generally UDP is preferred" -" when possible." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:67 -#: 2645ab57ec6949ed8728b1215eb4ed0d -msgid "" -"The official port for OpenVPN is 1194, which we reserve for client VPN; we " -"will use 1195 for site-to-site VPN." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:69 -#: 761526d038c44f7cbe439eca6cf24a95 -msgid "" -"The ``persistent-tunnel`` directive will allow us to configure tunnel-" -"related attributes, such as firewall policy as we would on any normal " -"network interface." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:72 -#: b18e504b82d446169c94dd325823b185 -msgid "" -"If known, the IP of the remote router can be configured using the ``remote-" -"host`` directive; if unknown, it can be omitted. We will assume a dynamic IP" -" for our remote router." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:77 -#: ../../configuration/interfaces/openvpn.rst:189 -#: cab68ffde37744b59d4cd0a1e0f0d850 422a662d43c6473daa8e0d2cf92dc34e -msgid "Local Configuration:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:96 -#: db11f80ff5394719aa58ffe0dd9a501b -msgid "Local Configuration - Annotated:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:120 -#: ../../configuration/interfaces/openvpn.rst:195 -#: b7a3e0e2c3e543bb8d8eff8dd7d5e827 340bb3b25c7a4fce958d9e3fb4444318 -msgid "Remote Configuration:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:137 -#: e65f707bda204e099463092bf0f8c303 -msgid "Remote Configuration - Annotated:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:157 -#: 53eb821bc2c3458cb52668c7de2a18ec -msgid "Firewall Exceptions" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:159 -#: 385eabf716fc469cb21a61b025282f1e -msgid "" -"For the OpenVPN traffic to pass through the WAN interface, you must create a" -" firewall exception." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:175 -#: 7a1560761c4e4744a421fd7c5e03c7f0 -msgid "" -"You should also ensure that the OUTISDE_LOCAL firewall group is applied to " -"the WAN interface and a direction (local)." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:183 -#: 12bceb7181f6434bb48414f2e893a3e2 -msgid "Static Routing:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:185 -#: 2940b3f164b34fccbe2ed317b8aae081 -msgid "" -"Static routes can be configured referencing the tunnel interface; for " -"example, the local router will use a network of 10.0.0.0/16, while the " -"remote has a network of 10.1.0.0/16:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:201 -#: 66ff84e8e5e34de0b0c132a7dff8cf1f -msgid "" -"The configurations above will default to using 256-bit AES in GCM mode for " -"encryption (if both sides support NCP) and SHA-1 for HMAC authentication. " -"SHA-1 is considered weak, but other hashing algorithms are available, as are" -" encryption algorithms:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:206 -#: 0b31ab06453141d3b6ba4c441611568c -msgid "For Encryption:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:208 -#: 86ee9217a4a140728b9e88421d7d86d1 -msgid "" -"This sets the cipher when NCP (Negotiable Crypto Parameters) is disabled or " -"OpenVPN version < 2.4.0." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:226 -#: 7b9425a5391b45ee88f872989ebcebbc -msgid "" -"This sets the accepted ciphers to use when version => 2.4.0 and NCP is " -"enabled (which is the default). Default NCP cipher for versions >= 2.4.0 is " -"aes256gcm. The first cipher in this list is what server pushes to clients." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:243 -#: daaa5904c30b4f09bc8fbaa49b7f42a9 -msgid "For Hashing:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:254 -#: 14ce402c4f214056990108c250a7089e -msgid "" -"If you change the default encryption and hashing algorithms, be sure that " -"the local and remote ends have matching configurations, otherwise the tunnel" -" will not come up." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:259 -#: 66053eddf2e6491c8f739135a27ce02a -msgid "" -"Firewall policy can also be applied to the tunnel interface for `local`, " -"`in`, and `out` directions and functions identically to ethernet interfaces." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:262 -#: 5bb0689956194c29a85595b417e6f716 -msgid "" -"If making use of multiple tunnels, OpenVPN must have a way to distinguish " -"between different tunnels aside from the pre-shared-key. This is either by " -"referencing IP address or port number. One option is to dedicate a public IP" -" to each tunnel. Another option is to dedicate a port number to each tunnel " -"(e.g. 1195,1196,1197...)." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:268 -#: be7b2b4173ad4394a99d325856c10d8c -msgid "" -"OpenVPN status can be verified using the `show openvpn` operational " -"commands. See the built-in help for a complete list of options." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:273 -#: e60ff00a9fdf4f2f81f109d6e3ad2d68 -msgid "Server" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:275 -#: 09af881109e046fca4c58f1633df9d69 -msgid "" -"Multi-client server is the most popular OpenVPN mode on routers. It always " -"uses x.509 authentication and therefore requires a PKI setup. Refer this " -"topic :ref:`configuration/pki/index:pki` to generate a CA certificate, a " -"server certificate and key, a certificate revocation list, a Diffie-Hellman " -"key exchange parameters file. You do not need client certificates and keys " -"for the server setup." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:282 -#: f37e123fc5194cb19176aa1503a58ab2 -msgid "" -"In this example we will use the most complicated case: a setup where each " -"client is a router that has its own subnet (think HQ and branch offices), " -"since simpler setups are subsets of it." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:286 -#: e837488cac2d48ef82c0c2e27488c653 -msgid "" -"Suppose you want to use 10.23.1.0/24 network for client tunnel endpoints and" -" all client subnets belong to 10.23.0.0/20. All clients need access to the " -"192.168.0.0/16 network." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:290 -#: 8dfced3dc81d4ffab1643fdf9b8f15a6 -msgid "" -"First we need to specify the basic settings. 1194/UDP is the default. The " -"``persistent-tunnel`` option is recommended, it prevents the TUN/TAP device " -"from closing on connection resets or daemon reloads." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:294 -#: 29480370e25846f3ad3820a8d19f0b45 -msgid "" -"Using **openvpn-option -reneg-sec** can be tricky. This option is used to " -"renegotiate data channel after n seconds. When used at both server and " -"client, the lower value will trigger the renegotiation. If you set it to 0 " -"on one side of the connection (to disable it), the chosen value on the other" -" side will determine when the renegotiation will occur." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:307 -#: 57b1113e85e24c5dbae5ca745935c57b -msgid "" -"Then we need to generate, add and specify the names of the cryptographic " -"materials. Each of the install command should be applied to the " -"configuration and commited before using under the openvpn interface " -"configuration." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:333 -#: 756b20926c26490bb8249155d68b413e -msgid "" -"Now we need to specify the server network settings. In all cases we need to " -"specify the subnet for client tunnel endpoints. Since we want clients to " -"access a specific network behind our router, we will use a push-route option" -" for installing that route on clients." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:343 -#: abac85d1dbfd4f75aca8ae2ec0d8817a -msgid "" -"Since it's a HQ and branch offices setup, we will want all clients to have " -"fixed addresses and we will route traffic to specific subnets through them. " -"We need configuration for each client to achieve this." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:347 -#: 7479a7ab758f42569c8c44c4b9529576 -msgid "" -"Clients are identified by the CN field of their x.509 certificates, in this " -"example the CN is ``client0``:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:355 -#: d5b2801f47644e74a5b916d60c828783 -msgid "" -"OpenVPN **will not** automatically create routes in the kernel for client " -"subnets when they connect and will only use client-subnet association " -"internally, so we need to create a route to the 10.23.0.0/20 network " -"ourselves:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:363 -#: e5c52c8f69554323bdaf973188ccc9f7 -msgid "" -"Additionally, each client needs a copy of ca cert and its own client key and" -" cert files. The files are plaintext so they may be copied either manually " -"from the CLI. Client key and cert files should be signed with the proper ca " -"cert and generated on the server side." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:368 -#: 29182698394c4432aee0199abc60a1e6 -msgid "" -"HQ's router requires the following steps to generate crypto materials for " -"the Branch 1:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:376 -#: a554a86bd32a4c0784d62d3ec50adc1c -msgid "Branch 1's router might have the following lines:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:388 -#: 17b4887e99374bc88d6fce86f4597621 -msgid "Client Authentication" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:391 -#: 038d555a70b04bdaa7ae87f8bf995ef2 -msgid "LDAP" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:393 -#: 5130e1cebbb64b4ba444fc9787f21e10 -msgid "" -"Enterprise installations usually ship a kind of directory service which is " -"used to have a single password store for all employees. VyOS and OpenVPN " -"support using LDAP/AD as single user backend." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:397 -#: e8644bf4cc7a47b1a409d1d182f8ce5b -msgid "" -"Authentication is done by using the ``openvpn-auth-ldap.so`` plugin which is" -" shipped with every VyOS installation. A dedicated configuration file is " -"required. It is best practise to store it in ``/config`` to survive image " -"updates" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:406 -#: 38b8b68dc305461d9b94b4333ba7a068 -msgid "The required config file may look like this:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:431 -#: ee85ab9fe267488d88f9b2600b6b5704 -msgid "Active Directory" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:433 -#: a33ecf0d70df4755838c5f71752619f4 -msgid "Despite the fact that AD is a superset of LDAP" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:466 -#: 82ab9b1c8177477face38193289304c3 -msgid "" -"If you only want to check if the user account is enabled and can " -"authenticate (against the primary group) the following snipped is " -"sufficient:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:486 -#: 8f3869732b8e4cf9b4591d6ca13d3019 -msgid "" -"A complete LDAP auth OpenVPN configuration could look like the following " -"example:" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:518 -#: 1e0aabccc72f4098bfcb6523647e7c17 -msgid "Client" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:520 -#: 0b1a28801b7143179e523d004c3a857e -msgid "" -"VyOS can not only act as an OpenVPN site-to-site or server for multiple " -"clients. You can indeed also configure any VyOS OpenVPN interface as an " -"OpenVPN client connecting to a VyOS OpenVPN server or any other OpenVPN " -"server." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:524 -#: 13dabeeafa784b0aa98cdd5dbf5f8c31 -msgid "" -"Given the following example we have one VyOS router acting as OpenVPN server" -" and another VyOS router acting as OpenVPN client. The server also pushes a " -"static client IP address to the OpenVPN client. Remember, clients are " -"identified using their CN attribute in the SSL certificate." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:532 -#: 2c6ec6c8ba11405e8461a988a327f20b -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:535 -#: c00ac5ce2f5b4682b9673b07cf934904 -msgid "Server Side" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:561 -#: f312f23678d542d49dc29fe8450f29b3 -msgid "Client Side" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:578 -#: 4fedcc73e58942e3828a272f9e3fa7ee -msgid "Options" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:580 -#: 31005d6f9b9e458e8c083b953b5c4035 -msgid "" -"We do not have CLI nodes for every single OpenVPN option. If an option is " -"missing, a feature request should be opened at Phabricator_ so all users can" -" benefit from it (see :ref:`issues_features`)." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:584 -#: 03ab237055d04a219aa83a19cac07c45 -msgid "" -"If you are a hacker or want to try on your own we support passing raw " -"OpenVPN options to OpenVPN." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:589 -#: 6dbea9b586f14267ac370fa56a7804e7 -msgid "" -"Will add ``persistent-key`` at the end of the generated OpenVPN " -"configuration. Please use this only as last resort - things might break and " -"OpenVPN won't start if you pass invalid options/syntax." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:596 -#: 34f3fbe8e4694912bcad8926f2ead50d -msgid "Will add ``push \"keepalive 1 10\"`` to the generated OpenVPN config file." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:598 -#: 284f24a2c99b4c14b28c475cc994e2c3 -msgid "" -"Sometimes option lines in the generated OpenVPN configuration require " -"quotes. This is done through a hack on our config generator. You can pass " -"quotes using the ``"`` statement." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:604 -#: 55725e1e11cd4fad85c13e48ab226eba -msgid "Troubleshooting" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:606 -#: a2ed69794d954f78af215653514b9e26 -msgid "VyOS provides some operational commands on OpenVPN." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:609 -#: f927ebdf8c6f4e92924f5a0217e5f83f -msgid "Check status" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:611 -#: 2525426e9a4844e4b47378ebf5fc6df3 -msgid "The following commands let you check tunnel status." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:615 -#: a440cc7591184a83b546cb32682bcc18 -msgid "" -"Use this command to check the tunnel status for OpenVPN client interfaces." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:619 -#: 1ffd21f37b644e5582d05a98d86b7d07 -msgid "" -"Use this command to check the tunnel status for OpenVPN server interfaces." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:623 -#: 545e3d4311594d858c3ce957784e1eb3 -msgid "" -"Use this command to check the tunnel status for OpenVPN site-to-site " -"interfaces." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:628 -#: b815ea96d89c452aaa7b1d2f14102780 -msgid "Reset OpenVPN" -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:630 -#: 75698dec800d40c5a8feb3bc9e05a4eb -msgid "The following commands let you reset OpenVPN." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:634 -#: 43f4e02ebf12449d84b4b2dd81e2c681 -msgid "Use this command to reset the specified OpenVPN client." -msgstr "" - -#: ../../configuration/interfaces/openvpn.rst:638 -#: f4620017a238485c9f6e21a5ef43663f -msgid "Use this command to reset the OpenVPN process on a specific interface." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pppoe.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pppoe.po deleted file mode 100644 index 34c2d3a6..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pppoe.po +++ /dev/null @@ -1,568 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/pppoe.rst:7 d53d4b6baa8f44edb70ccf76be15b863 -msgid "PPPoE" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:9 6abb75ee77db4427ad8ac8beef0923cd -msgid "" -":abbr:`PPPoE (Point-to-Point Protocol over Ethernet)` is a network protocol " -"for encapsulating PPP frames inside Ethernet frames. It appeared in 1999, in" -" the context of the boom of DSL as the solution for tunneling packets over " -"the DSL connection to the :abbr:`ISPs (Internet Service Providers)` IP " -"network, and from there to the rest of the Internet. A 2005 networking book " -"noted that \"Most DSL providers use PPPoE, which provides authentication, " -"encryption, and compression.\" Typical use of PPPoE involves leveraging the " -"PPP facilities for authenticating the user with a username and password, " -"predominately via the PAP protocol and less often via CHAP." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:21 -#: 9721c90abdef4f86a951abef8c4ea4aa -msgid "Operating Modes" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:23 -#: 82ff5d414c124c64b356619926f5fa1d -msgid "" -"VyOS supports setting up PPPoE in two different ways to a PPPoE internet " -"connection. This is because most ISPs provide a modem that is also a " -"wireless router." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:28 -#: 5902b3f8635d49379a76467ff5a8836f -msgid "Home Users" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:30 -#: 00431be2df4c4c6fbdbeb474e80bcdbf -msgid "" -"In this method, the DSL Modem/Router connects to the ISP for you with your " -"credentials preprogrammed into the device. This gives you an :rfc:`1918` " -"address, such as ``192.168.1.0/24`` by default." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:34 -#: 4c9e9aa580c64e22a0d67f1ceffeed37 -msgid "" -"For a simple home network using just the ISP's equipment, this is usually " -"desirable. But if you want to run VyOS as your firewall and router, this " -"will result in having a double NAT and firewall setup. This results in a few" -" extra layers of complexity, particularly if you use some NAT or tunnel " -"features." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:41 -#: 1dd23f7efa6940d8bf16457d59d026fd -msgid "Business Users" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:43 -#: 184d373652de4d7b8d6320520367cb01 -msgid "" -"In order to have full control and make use of multiple static public IP " -"addresses, your VyOS will have to initiate the PPPoE connection and control " -"it. In order for this method to work, you will have to figure out how to " -"make your DSL Modem/Router switch into a Bridged Mode so it only acts as a " -"DSL Transceiver device to connect between the Ethernet link of your VyOS and" -" the phone cable. Once your DSL Transceiver is in Bridge Mode, you should " -"get no IP address from it. Please make sure you connect to the Ethernet Port" -" 1 if your DSL Transceiver has a switch, as some of them only work this way." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:52 -#: bafd015de35c47bb9fa736466f6682ae -msgid "" -"Once you have an Ethernet device connected, i.e. `eth0`, then you can " -"configure it to open the PPPoE session for you and your DSL Transceiver " -"(Modem/Router) just acts to translate your messages in a way that vDSL/aDSL " -"understands." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:59 -#: 85df608d39764692838250e06c716eda -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:62 -#: f11e711898cc43be83e421ca5ef672a2 -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-description.txt:4 05c178fc8deb475381ffda9e8b09ff52 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 ../../_include/interface-vrf.txt:9 -#: ../../configuration/interfaces/pppoe.rst:123 -#: ../../configuration/interfaces/pppoe.rst:136 -#: 4aa038e69164485d8ee4cc35b98ed61f 8e65d13e53674944a1a8a5efb0d1ceb6 -#: dc8b06eb678a4679b77efe2dae4f670a c2ab4fe4c94346c194248ea60aa1e5e0 -#: 17ab7b57f3a2452292f867055755e308 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-disable.txt:4 8f9974b14a3442e3b675cf81f2448745 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 84df64f631e64ae0b83f76b7d11ed90d -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 714a85d74a9c4d1e9d8518f97da03dbd -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:77 -#: 4378b4cf2fa945449829bd518424a4ce -msgid "PPPoE options" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:81 -#: f9b3aaabbe5b4754a4231472dfb08bc2 -msgid "" -"Use this command to restrict the PPPoE session on a given access " -"concentrator. Normally, a host sends a PPPoE initiation packet to start the " -"PPPoE discovery process, a number of access concentrators respond with offer" -" packets and the host selects one of the responding access concentrators to " -"serve this session." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:87 -#: c7e63e8b326947069aaa600dac853945 -msgid "" -"This command allows you to select a specific access concentrator when you " -"know the access concentrators `<name>`." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:92 -#: 200175b74f814d189822d5add21fb81a -msgid "" -"Use this command to set the username for authenticating with a remote PPPoE " -"endpoint. Authentication is optional from the system's point of view but " -"most service providers require it." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:98 -#: 99a36b3415994c51a936eefc84960a0c -msgid "" -"Use this command to set the password for authenticating with a remote PPPoE " -"endpoint. Authentication is optional from the system's point of view but " -"most service providers require it." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:104 -#: 0b0b2ec10f824c35a09ebc8c9bf8537c -msgid "When set the interface is enabled for \"dial-on-demand\"." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:106 -#: dc0b11ee560642e1865dfd6aee442087 -msgid "" -"Use this command to instruct the system to establish a PPPoE connection " -"automatically once traffic passes through the interface. A disabled on-" -"demand connection is established at boot time and remains up. If the link " -"fails for any reason, the link is brought back up immediately." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:111 -#: 7eed5581b05449aa8b1851e2a20c59b7 -msgid "" -"Enabled on-demand PPPoE connections bring up the link only when traffic " -"needs to pass this link. If the link fails for any reason, the link is " -"brought back up automatically once traffic passes the interface again. If " -"you configure an on-demand PPPoE connection, you must also configure the " -"idle timeout period, after which an idle PPPoE link will be disconnected. A " -"non-zero idle timeout will never disconnect the link after it first came up." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:120 -#: 1ff41a77925a4989a978fd62d9844bb4 -msgid "" -"Only request an address from the PPPoE server but do not install any default" -" route." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:129 -#: 2963d8c432354fe89658b6a6c33a2865 -msgid "" -"This command got added in VyOS 1.4 and inverts the logic from the old " -"``default-route`` CLI option." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:134 -#: 84705c4c189744e182b5724ee1354489 -msgid "Set the distance for the default gateway sent by the PPPoE server." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:144 -#: 45970db8743b445f88b01f88d5c1d195 -msgid "" -"Use this command to set the idle timeout interval to be used with on-demand " -"PPPoE sessions. When an on-demand connection is established, the link is " -"brought up only when traffic is sent and is disabled when the link is idle " -"for the interval specified." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:149 -#: cc58dc123af648fead7716ed2ac16e6e -msgid "" -"If this parameter is not set or 0, an on-demand link will not be taken down " -"when it is idle and after the initial establishment of the connection. It " -"will stay up forever." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:155 -#: c0ac8dabbfa34951b877e348c435e01c -msgid "" -"Use this command to set the IP address of the local endpoint of a PPPoE " -"session. If it is not set it will be negotiated." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:160 -#: 58ddff7e5def4669a30de42918d22f73 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:165 -#: b18a94e8f57d4fdea0c511ef5d4911b7 -msgid "" -"Use this command to not install advertised DNS nameservers into the local " -"system." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:170 -#: 4632203180c64f6c82ebbe12e3675b74 -msgid "" -"Use this command to set the IP address of the remote endpoint of a PPPoE " -"session. If it is not set it will be negotiated." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:175 -#: ef2ad700020243c1a4aeff284e6645a5 -msgid "" -"Use this command to specify a service name by which the local PPPoE " -"interface can select access concentrators to connect with. It will connect " -"to any access concentrator if not set." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:181 -#: 9af7057126c342de886a45d8c25d1fae -msgid "" -"Use this command to link the PPPoE connection to a physical interface. Each " -"PPPoE connection must be established over a physical interface. Interfaces " -"can be regular Ethernet interfaces, VIFs or bonding interfaces/VIFs." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:187 -#: ../../configuration/interfaces/pppoe.rst:233 -#: fa776ec02764490d9f46195e7e7e56f6 1805241e56fe4d188b38bb1753f06c18 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:192 -#: ../../configuration/interfaces/pppoe.rst:238 -#: 13f51b67aee44b7db6073ee1717d24e1 9a3d6b4478d7474bb2c07642d17b9e36 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:195 -#: ../../configuration/interfaces/pppoe.rst:241 -#: 3df76abfe8194781b12374bd33272b12 d3f745666fc041b4873bee4819b553eb -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:198 -#: ../../configuration/interfaces/pppoe.rst:244 -#: bdaedb8ebb5a4b88bd278b1ffff3f33a 4f1b52acfea644358ca0631ccec7584d -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:203 -#: ../../configuration/interfaces/pppoe.rst:249 -#: c1711d0754714423b79ea4d7f2474754 ad78c955d45745318d299f3097ef1d04 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:208 -#: e4a7328d92664fdfacc40053a416bba1 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:213 -#: 198a7f0e5db24ab5a310e1ddba5e3a8a -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:217 -#: c0702ab6da574f2a986c201ee49873df -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:221 -#: c7c5753e81c04e389a51ddeb9220c3a7 -msgid "disable: No source validation" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:224 -#: 05928bbc69a04b78b578a51147592185 -msgid "IPv6" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:228 -#: f46e116bf45c49cd8bf4fed6fd7b3d36 -msgid "" -"Use this command to enable acquisition of IPv6 address using stateless " -"autoconfig (SLAAC)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 1cae9ddad8054c99b058b049f52c5726 -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: d63453587a724517a9317e56a4ced137 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: 29b449e1c8db4d53a2c82693ababc842 -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: 1512a42baaab4db28963062b1a5778a6 -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: 0b47d3dc4ca044e494ddd1e3fab83da6 -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: d870182fe29744a99b68048d3808be96 -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: 7c4d122355644d9e897e2403168efa1e -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 973d2e33b8c54c759440ba03e8a98d84 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: c0f68a9157fa445bad915bfa2389b6e9 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: 6e9261341b384bf79e31e05131e18dae -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:258 -#: 8a0a2a6e166240288019af568b290651 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:262 -#: e91a9e557113422691f8093b4080f8c3 -msgid "Show detailed information on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:279 -#: 4316e751ea6641e2834fa8212eb33d25 -msgid "Displays queue information for a PPPoE interface." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:289 -#: aa2eda29f5054d5faf3dc0597c2e193d -msgid "Connect/Disconnect" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:293 -#: 76532e8dafd844e3b1732db45beb6d72 -msgid "" -"Test disconnecting given connection-oriented interface. `<interface>` can be" -" ``pppoe0`` as the example." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:298 -#: fce1b4b4eeb34b36b1cd8c909b55353d -msgid "" -"Test connecting given connection-oriented interface. `<interface>` can be " -"``pppoe0`` as the example." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:303 -#: 88982933d6f44e53b727fdfa0818fe6f -msgid "Example" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:305 -#: 98117828f7174b8da41ecfcbffcfbb81 -msgid "Requirements:" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:307 -#: b6c27fdc2e274128bb72538c47c261ac -msgid "Your ISPs modem is connected to port ``eth0`` of your VyOS box." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:308 -#: b4dbd28b8a864ad6a209f756fb929270 -msgid "No VLAN tagging required by your ISP." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:309 -#: c6545685b5f54fb59868cded7e27e928 -msgid "" -"You need your PPPoE credentials from your DSL ISP in order to configure " -"this. The usual username is in the form of name@host.net but may vary " -"depending on ISP." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:312 -#: 6cb996a4363f4097aa5919015932b1c1 -msgid "" -"The largest MTU size you can use with DSL is 1492 due to PPPoE overhead. If " -"you are switching from a DHCP based ISP like cable then be aware that things" -" like VPN links may need to have their MTU sizes adjusted to work within " -"this limit." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:316 -#: d5e1f9fdb134472cbd3a39ed4803b5c7 -msgid "" -"With the ``name-server`` option set to ``none``, VyOS will ignore the " -"nameservers your ISP sends you and thus you can fully rely on the ones you " -"have configured statically." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:320 -#: 0be62b44fac04649baee90229ecc0fa8 -msgid "" -"Syntax has changed from VyOS 1.2 (crux) and it will be automatically " -"migrated during an upgrade." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:323 -#: bc624d59618c40ee8722ce3b1c27810a -msgid "" -"A default route is automatically installed once the interface is up. To " -"change this behavior use the ``no-default-route`` CLI option." -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:333 -#: ef0b2fc91fb64e49a4a47350f437ae10 -msgid "" -"You should add a firewall to your configuration above as well by assigning " -"it to the pppoe0 itself as shown here:" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:343 -#: b28f2e92947b42908e1f5d3a6d006c8a -msgid "VLAN Example" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:345 -#: e124b13f8606492eabb44c9f1d407323 -msgid "" -"Some recent ISPs require you to build the PPPoE connection through a VLAN " -"interface. One of those ISPs is e.g. Deutsche Telekom in Germany. VyOS can " -"easily create a PPPoE session through an encapsulated VLAN interface. The " -"following configuration will run your PPPoE connection through VLAN7 which " -"is the default VLAN for Deutsche Telekom:" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:359 -#: 479be4afdc7448229fb6ee819f8521d1 -msgid "IPv6 DHCPv6-PD Example" -msgstr "" - -#: ../../configuration/interfaces/pppoe.rst:363 -#: 074a53774fa347db8d5848ff452f7129 -msgid "" -"The following configuration will assign a /64 prefix out of a /56 delegation" -" to eth0. The IPv6 address assigned to eth0 will be <prefix>::ffff/64. If " -"you do not know the prefix size delegated to you, start with sla-len 0." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pseudo-ethernet.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pseudo-ethernet.po deleted file mode 100644 index c905d531..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/pseudo-ethernet.po +++ /dev/null @@ -1,827 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:7 -#: a1b5ff090a4a4e61aafb8e3a611c9ba8 -msgid "MACVLAN - Pseudo Ethernet" -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:9 -#: e39ce485204b4e41953be6052434c89f -msgid "" -"Pseudo-Ethernet or MACVLAN interfaces can be seen as subinterfaces to " -"regular ethernet interfaces. Each and every subinterface is created a " -"different media access control (MAC) address, for a single physical Ethernet" -" port. Pseudo- Ethernet interfaces have most of their application in " -"virtualized environments," -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:14 -#: dc124108d228495db8e23f3929b5efb8 -msgid "" -"By using Pseudo-Ethernet interfaces there will be less system overhead " -"compared to running a traditional bridging approach. Pseudo-Ethernet " -"interfaces can also be used to workaround the general limit of 4096 virtual " -"LANs (VLANs) per physical Ethernet port, since that limit is with respect to" -" a single MAC address." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:20 -#: 40d72daa9d854110b37ef2cdbcbffd5d -msgid "" -"Every Virtual Ethernet interfaces behaves like a real Ethernet interface. " -"They can have IPv4/IPv6 addresses configured, or can request addresses by " -"DHCP/ DHCPv6 and are associated/mapped with a real ethernet port. This also " -"makes Pseudo-Ethernet interfaces interesting for testing purposes. A Pseudo-" -"Ethernet device will inherit characteristics (speed, duplex, ...) from its " -"physical parent (the so called link) interface." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:27 -#: 40b1f81b20a7412b9871fc3e71b81dec -msgid "" -"Once created in the system, Pseudo-Ethernet interfaces can be referenced in " -"the exact same way as other Ethernet interfaces. Notes about using Pseudo- " -"Ethernet interfaces:" -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:31 -#: 3c8c50d3304a4b998ca69064d20f7868 -msgid "" -"Pseudo-Ethernet interfaces can not be reached from your internal host. This " -"means that you can not try to ping a Pseudo-Ethernet interface from the host" -" system on which it is defined. The ping will be lost." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:34 -#: 9f0f08c4078442a9af4e46a9c99a697b -msgid "" -"Loopbacks occurs at the IP level the same way as for other interfaces, " -"ethernet frames are not forwarded between Pseudo-Ethernet interfaces." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:36 -#: 6bb81cffea774a2c835132a39142fece -msgid "" -"Pseudo-Ethernet interfaces may not work in environments which expect a " -":abbr:`NIC (Network Interface Card)` to only have a single address. This " -"applies to: - VMware machines using default settings - Network switches with" -" security settings allowing only a single MAC address - xDSL modems that try" -" to learn the MAC address of the NIC" -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:45 -#: 192799865dac4f92b5d0f77f59787cfc -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:48 -#: 20df90402556415bb1ccc0c7d90bd1de -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: c1254388fbda4649b9a9e75084114709 7e7119bed8b74dfbafae498d9d849389 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: a452d156ef284953992423c7b64d9483 7f0b7794f21c4be7bacc05aa185aecf3 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: 3374df8696a8446883571826dd72d2f6 f4e08d4038f4470c8790d6ea80ff8f51 -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: 50b0bedf515c408c9dfed55712cb4c11 d4ee9160a3a948749d285bdc74acc8a6 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: 0be7c7166acf4e5eb8a8b57cfc483552 3c4c8b649d424e68a160e948e05f6acd -#: fd09086b5bed4e58af49570e8850e277 95f268309b2c42d3936f29c4a70e8bdf -#: 18b279643a8b467488e6b8401081997e b36426baaa2f436d89a1b4796145d1e2 -#: 1dccf35e33674e5b8af782f242ef9572 c2ec5a74e20543728a5eabebc75e68c1 -#: 088b581aff2841039a5c0ebeea28175c 9790eba2a61d4a31a65c439db93f811e -#: 698d18bba3e64ce8b21f8685a2a9efd4 966fd7669f954e2eacd0e2a3f3f058ba -#: 6cd868d272654f309c8f5f2577074aac 841d715b73364f84b9bc610de818ef4d -#: 14247af93f6f40a5ad188836ef00fe22 4d06aba027704b2ab493a0a32c5e9b25 -#: 2ff2fb3afc8e46eea46f4e43482765b8 b58f7594208247be8f2cc45d300f5aa4 -#: b8991d3ec8874a3a94a56daa9de4c03f 34c510b91cf04184b086cee39292f2da -#: 468539132eea4126bdbeba3338743c15 dc9bcaa929414656bb84371186805b40 -#: 8e0d9bc008134381a8872422a97cd9a4 ad369bd537c04dcea5f4ae0d500c2363 -#: 3b522e8f7ce743b29df7121a69e8c1f3 46dce806082e4190a09826dd6cb90564 -#: 34cca74f6e7e404aa4f0e34ce58b1cf7 f27cbbcc7ac64be2ad43894c7f487d1b -#: c6d1620813b740abb895c49a405bdc5c a41e7a06ee61484f99ba3b672e37d5ce -#: 57dea7a63cde454c984a627286074a5e 01315c3fdb434ef3aabea6d484d22e4b -#: 1947b7927a7a4cbab7cd9f0b19d8bb3e a13e1e194a494ece8760b158fbcf7dc3 -#: 8565c26323614cc9820727eba9f60358 a92056b1d6d446a4b1e9e7427ee50e61 -#: 1c3a9d289a8e4389b03454e6076c6515 6c2ebf684c0d4f2d86fe31348fc61e51 -#: c47d59158d814e5686532703bb698c54 55df8d495289452fb2d8c56471a44281 -#: d49225e7d9184946b560f18add21bc0d -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 6650dde0eaf347e0958d0a8e0109a629 -#: d381917960fd42a2a141e9db86786760 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 7a82ce23397a49ba9ff366f0567c666f -#: b1137acd6e54407fa15b0153821844e9 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: 7c8a7ea4ed3b4b5ab4bf6c4b2eba652b -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 97aee86078ed4d9b99056d74824f9541 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: b544fcacc84e4756aa51d13951060260 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: 0b9cc540a0e14c1fb42b4c0dfae6e982 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: af28860b0b6f4630961412fdef50c9cb dcb828c09523467580212b6f251380c5 -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: 564f05bedef74615856ac1636d72f376 926baf20767546e48900c301f8e490bc -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 ../../_include/interface-mac.txt:4 -#: d62824132ac54b38910d355e29f661ff 9584164dae4746eab6d6fd78ed1ff846 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 ../../_include/interface-mtu.txt:4 -#: 786fe39c22a844a3aedf9cac007c3601 3b36fa7a16e8435eae2c2044a45c5148 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 4daaab9f21984923a7da57f82d501604 c181269ca88249b680902948b5df7f66 -#: 7a31630c519245bc87a88e6ffb4d387a bd615d0ca69e45faa753393e69272183 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 ../../_include/interface-ip.txt:9 -#: d5e0e123cb4c4f3d828d3c343287c40e 2ef6f3843b6b4bc7857c090f19eb0dc4 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ../../_include/interface-ip.txt:12 -#: 61977cd808724dd985372456629267b3 4d18b6a453c946ffb08cee28c7a58487 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: f875c1c0b05d4201aa38f948deb2cd7c 70cb41c2b398493188e31ffe646e636b -#: 02c79026b8db42e3a620194b78d25ff0 b3a38bccbd4d418d9bae2cd10d16a9f6 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 ../../_include/interface-ip.txt:21 -#: 57499582a38648078eff45448eddd72e ec2da7f69c0d4b7d9058636e2c52984a -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 ../../_include/interface-ip.txt:25 -#: 87ae26b4149a4c1ba4f517121b61f421 82beaad393d448919dcd56903cea9b58 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ../../_include/interface-ip.txt:36 -#: 55e69c14e9f345708f29509a967960e9 098c5319c84048a0b140c452023d7500 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ../../_include/interface-ip.txt:42 -#: f11b0234314f4b8eb885c1cadcf2613d 4f9d162daa764e5e946a5be285bd3f42 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 ../../_include/interface-ip.txt:47 -#: 5ca884aebab74dcd846d83e00c1451f6 cf7bee41ca1f42039e9de905506d695f -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 9f747ba0d8504f2889dfb5903ddd4cb3 c0c1346c81c843ddb07e53ac62a57af2 -#: f78faaf72a1144f6887b7ac00db38cf9 a449b6a189b94b48ab40dd58b06b0347 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ../../_include/interface-ip.txt:69 -#: d45c7bde4b71432aa951b2879b335014 fde3035bb93b473c8de5debd7749accd -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 ../../_include/interface-ip.txt:72 -#: 96694acba5cc48c9b45473a08677c844 bd7c50468e19409d926b69b311735761 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 ../../_include/interface-ip.txt:75 -#: de22bfd2c60342d8ad06c7dce5fc24e1 3c55655b023e4c52b8cea1c0b5f5c2eb -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 ../../_include/interface-ip.txt:85 -#: 3f82ba7e32f14c439e8fa1bc4f111307 567e0de264064b219c9fd0daff427572 -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 ../../_include/interface-ip.txt:88 -#: 06282db4270649b8880a005cf67bb9bf 02d76906725c459dafff8657a0e0bd8e -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 ../../_include/interface-ip.txt:91 -#: 47343c4d811142889024c792e78f8284 9e9f35d8c7a341479e38f00628cfe801 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 ../../_include/interface-ip.txt:101 -#: 88f62ff75f1041888b90b1c4b1df887e e71ac0ece8934ffb8285eff6e669e22b -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ../../_include/interface-ip.txt:104 -#: 929f85a3b5384f6dbbba2ef901984abf f51918699efa41f4847e552de896f946 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 ../../_include/interface-ip.txt:106 -#: aa99bc339051400bad3398d366929c57 f2e2fc224db94ffb920a3e6c014515c4 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 ../../_include/interface-ip.txt:121 -#: ebc7cfa384eb4863baaac62b9ebfe268 7e81645780f04579833d19ad8e0323eb -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 ../../_include/interface-ip.txt:124 -#: 6be442ff158f4e18b9c26f7c19562151 5c10056f2dc346dc879f07a5ff1b2266 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 ../../_include/interface-ip.txt:127 -#: d4d29a570a124afeaaccd739a291395e 4d247b75f48c445a8ea8da06c22aac82 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 ../../_include/interface-ip.txt:137 -#: ee5823179b5946db9a13ec472a9384b5 30800ed6723f4c558f051136b3869bee -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 ../../_include/interface-ip.txt:153 -#: 023a3e6fb9114baa9f1c79015e4077b1 71552688dd2243fa967a78252efa23ea -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 ../../_include/interface-ip.txt:156 -#: 5cf6d6be3b2b4d8f8ebf04e8165c2c13 b7de9522f83f48d89057e0769523120f -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 ../../_include/interface-ip.txt:162 -#: 7e7ccbaf9ee94f4990b69323a8c4eb68 f666ec4afbe94270bf92bd1a2bd349ce -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 ../../_include/interface-ip.txt:164 -#: a1768d47f14941b899394305acf4e5e4 0a6f0d087ef94e2cbbff549935f57e6a -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 ../../_include/interface-ip.txt:166 -#: b19113cd237a44d79951463de9b564a3 1934229f8db9488baa6b379ece2ab71b -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ../../_include/interface-ip.txt:168 -#: 70da481dc30745c3a726314c5b18c8d4 44d3c5b72a7347a2b11e4a9f78f51c61 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 ../../_include/interface-ip.txt:170 -#: fe0aca5ac5c449f6a890bde4123a2d42 de7081a446284d129e78fd76839fef5b -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ../../_include/interface-ip.txt:172 -#: c36ebe2f67874d339d62e9733932a072 d18a28e6f0ce4530b5faa873e266fc1c -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 ../../_include/interface-ip.txt:177 -#: a90a189e97bc4e0fbf8eaa46d2d50205 3c4b52ad28244916a5a428ffa0a440f5 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 ../../_include/interface-ip.txt:182 -#: 31c937346f8c4643931dbb6d1107af89 797fb32aad7b42e88bb52fa9f20a2549 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 ../../_include/interface-ip.txt:186 -#: f946dafeaf0345729a498f5cca2c10a9 3295b647a82643d593c3cb7303310432 -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 ../../_include/interface-ip.txt:190 -#: c69401da56a748fa831c14b33617451c f0cb79f81352458a815a9b9ca920c53b -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 ../../_include/interface-ipv6.txt:4 -#: f519afaef56a45b4b24c9bffc7be1e24 4c838e8e6e204ab8a5807beb79ce4bce -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ../../_include/interface-ipv6.txt:12 -#: dea40b23a3a741c2a04ad9df593248a3 b1f54346c8df4093a8f032d87a6e0235 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 ../../_include/interface-ipv6.txt:25 -#: 28d3701f8b594638936e2df8b722bbcb a588ed52bb504e24952476296a8d52b5 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ../../_include/interface-ipv6.txt:37 -#: c1d4381c6815441880f7912765dbc121 7fd52f1b75ef44bbbca96365b47e3785 -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 ../../_include/interface-ipv6.txt:65 -#: bb0863b7e22b4d79a9750f8a8939860a 46957e59968844f5a127bfa154c32b73 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 ../../_include/interface-ipv6.txt:68 -#: e852ec677f6f469c93a3fc70930e6553 b12c6b304a08479fa22e1b0f08cf3a96 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 ../../_include/interface-vrf.txt:4 -#: c8a69cb9357640f4a8602f9fa4df52b6 ec070c6f4d484c0eab9cf66ebf8017b0 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 ../../_include/interface-vrf.txt:6 -#: 537a415289f64ada99c725f02b33d24d dcebb4990d5c467ab5e71fc01f2651ae -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: ../../_include/interface-vlan-8021q.txt:97 de8b10ad411c4bdf987e1d36e6fa3481 -#: 5d9ec421cee94d5a87880963d6135876 -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: fd91ebe76cfe414380e86707df4aad86 401c362649544c7086304981542e2677 -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: 4fd57858a87548648e85e5e2504d4aec ea8dc3c12cfa4a89afbfdb1519d00e21 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: 42319a6f21504f948ab9fd476834b509 7a8006e442024679ad4485b31b99d0f4 -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: 0e03cce0542d4962ab2a16fd5457e141 d15341df42674b5580e94c00157d9f96 -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: da09cd3271c546468690961cb6b2c0b7 e9d20901b9a64b0f89d5448b36b210da -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: 3feb5fb7dc14432a8be841938534cbe4 c245b00e2315471ea88d042a70dd111e -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: 0c1d37506dc849629b55167268c715bf 8889335254c946e0a6e63539a7556a91 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: 1b78e660ac5e445d87a85a95a7aa416e 5c79bfe4ffd24bb9bd06ca0129028d43 -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: e8dbb2e8941945b89b5f2545dbf38186 3d9fcba12e1b48b6a9d5474131fea9eb -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: cd1f0f3893034ea289db7e6b9a90b737 1fbb8cba5fbc47c38af0b2954ce5eac4 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: f2dea25cbdfb4b54bd81427bf326217a 9139d58fe3834354a0abbf8cf3fed94a -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: a64c6d0f95794d8688ae7ec5045e90da 4345138d20dd4b8c98c582958ba46fda -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: a6b0be84becb47328ad353297b268df4 35a45ef978f24f54aa6e96eebaaa3732 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: 055fd101e7334add85176db58b68689c e7360afdde954b058798b419de4c8340 -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: 9a6af50ed8e541d8929f0006e6ae6d23 8c640e2c7979431e8cc7181c3ea6d8bf -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: 033128aaaa534f7fb55db579acfcc595 30c0d81bb3ea47da9c44dbaa952e3fc2 -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: d2432ac18e904befb4853954fcb49740 7bbc79be4c8748dfbbc8edd88c48fa68 -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: c73ce44bbee7423682377ba2d5489e66 ebe53d7fcb3748b49807a602daab7b48 -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 42131f95164f497c909fbb296ba65310 062c492206c141c391d27610211da623 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: 6827c9a19e1747568ba888f8bf12b05f 69b6dacc22cc4492846fc10adeafcb07 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: d4d741f2f5c147ca90d879280e1d659b 4b4c89a922e842ca912f695e6fd3486e -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:55 -#: d1d7e1d1ef1f4234837fbfb355d23d6a -msgid "Pseudo Ethernet/MACVLAN options" -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:59 -#: 1f634d1a772643688cf6163aa78fe8d2 -msgid "" -"Specifies the physical `<ethX>` Ethernet interface associated with a Pseudo " -"Ethernet `<interface>`." -msgstr "" - -#: ../../configuration/interfaces/pseudo-ethernet.rst:63 -#: eef1ecf9aa1d40398f7e7bd42d95a334 -msgid "VLAN" -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:1 34a2d574ded24fa8aaf097f9c9d32bff -msgid "" -"IEEE 802.1q_, often referred to as Dot1q, is the networking standard that " -"supports virtual LANs (VLANs) on an IEEE 802.3 Ethernet network. The " -"standard defines a system of VLAN tagging for Ethernet frames and the " -"accompanying procedures to be used by bridges and switches in handling such " -"frames. The standard also contains provisions for a quality-of-service " -"prioritization scheme commonly known as IEEE 802.1p and defines the Generic " -"Attribute Registration Protocol." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:9 46f01b05e1174be8b1cd12f6c88b802d -msgid "" -"Portions of the network which are VLAN-aware (i.e., IEEE 802.1q_ conformant)" -" can include VLAN tags. When a frame enters the VLAN-aware portion of the " -"network, a tag is added to represent the VLAN membership. Each frame must be" -" distinguishable as being within exactly one VLAN. A frame in the VLAN-aware" -" portion of the network that does not contain a VLAN tag is assumed to be " -"flowing on the native VLAN." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:16 6ede5fa0f97c4bab8a8897de4ff517a6 -msgid "" -"The standard was developed by IEEE 802.1, a working group of the IEEE 802 " -"standards committee, and continues to be actively revised. One of the " -"notable revisions is 802.1Q-2014 which incorporated IEEE 802.1aq (Shortest " -"Path Bridging) and much of the IEEE 802.1d standard." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:21 24f8504f28894257b4653fea906dffcf -msgid "" -"802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. " -"The term used for this is ``vif``." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:26 8022ccd3290d4d039827ad0a6b7142ed -msgid "" -"Create a new VLAN interface on interface `<interface>` using the VLAN number" -" provided via `<vlan-id>`." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:29 7cc4fff7645b4fa38d58ca2bbaba8944 -msgid "" -"You can create multiple VLAN interfaces on a physical interface. The VLAN ID" -" range is from 0 to 4094." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:32 5f825f2be8f54643a0cbfd3cbfe14bad -msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/tunnel.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/tunnel.po deleted file mode 100644 index 2e097aaf..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/tunnel.po +++ /dev/null @@ -1,637 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/tunnel.rst:6 -#: 4f65d335c87743e98057873277a1353a -msgid "Tunnel" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:8 -#: c8de9a02576d461f97bec190d3ea93ed -msgid "This article touches on 'classic' IP tunneling protocols." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:10 -#: 254b46d5f7664473b8b2e92dff2baef1 -msgid "" -"GRE is often seen as a one size fits all solution when it comes to classic " -"IP tunneling protocols, and for a good reason. However, there are more " -"specialized options, and many of them are supported by VyOS. There are also " -"rather obscure GRE options that can be useful." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:15 -#: e90d161e9e8947c1b0d5514fa3272b58 -msgid "" -"All those protocols are grouped under ``interfaces tunnel`` in VyOS. Let's " -"take a closer look at the protocols and options currently supported by VyOS." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:19 -#: c2b0d5af1476473b9189223164608f4e -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 5078f639ddbc492a87eeba14c59b2c45 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 574477bca2cf4d8282ce4b1787a2a68f -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mtu.txt:7 ../../_include/interface-ip.txt:27 -#: ../../_include/interface-ip.txt:50 ../../_include/interface-ip.txt:144 -#: ../../_include/interface-ipv6.txt:15 ../../_include/interface-ipv6.txt:28 -#: ../../_include/interface-ipv6.txt:39 ../../_include/interface-ipv6.txt:51 -#: ../../_include/interface-vrf.txt:9 e32a7dc8f2b54a8783033f5847a6e560 -#: a16a333daf7b49368def81a80ebdf599 dc0ed264fd4d47a8b381055995e313b1 -#: a166201dc0d1423fb673992999338c08 3607747f82cd4b159f126f5f06714797 -#: 47fcc3dc1bca4db8a0531db39cee7703 6003414eb6ef4e81932ae206316bb0f8 -#: f2ac87e6ebdf4072a6a9033e8c33bd60 4f07be30ced545538b6afb92a88b3ffb -#: b06b839165f64bc18c3ba29baff3785b 3650174d32ae46ca95f7fcb863c28b3d -#: 80f59ffaead947df9f31ecfbaf167140 8f735bc8814d4df6b651de20c7ee75cd -#: c0adda6294a54a7b9ced05325f955c03 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 a89a6d99fce647b594ddbdbeead413bf -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 b81dffd58eb34a7e9064268a6ae98051 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: c2a7d65177f64b69851492fb28b07312 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 93a595e71513427ca7fe9030a5878f29 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: c2fe745650374aacaa665e483550c1b5 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: be42ddb31ef840d08bfd0a919d876bf3 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: 0174b489a8294100b875271096104dbb -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ac6d5213881040789a52c9c81bc90024 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 c20cf181fa5848bfbe01f9f5edc12f3a -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 0c8e00cdcca74ecba7e8947d893256fb e91350f7e593470abaeec0777c262c31 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 bc1fa0cdb29b4cc8b3553ff689c2d224 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 b56d7dd7185a46e0a67700105e42a068 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 2531ac25a34a4f3dacd8408997b2c67f b0a1a2371dc84cab99cab059bf377749 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 c2c51b5241e641b0baf0a07650976111 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 7068bf0b709d4b5f8b47742aaaadaa19 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 e1908d3d12eb426e8972ec3f80942337 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 4a87915fcbc5487581424881375fa1e1 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 210d512fb473413d82bc7a7b6b470000 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 008d8655ebe14f308f2fbedf2e6770f2 6f8bfdf8d200454d96098626c48e5c57 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 82fecab14aee4ae9b1c359caaa80fd45 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 069ba34e0b794788b59f7abe9b97f478 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 2e7bb96c51054b989214f107b47dfc71 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 3414eea84d064891b529936ab0fcd72a -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 8933130461a64fd489419f5959fb9d33 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 dc32c4ffa55941d2b4f6c668ead08239 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 72ef11bef45a41a6bed39241dca769e8 -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 0fbfe686bcab45e7931c6aeef83a6226 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 e3c428c696b64bfab4f023d4f13ad399 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 f884754de2f448ec999d582831ea715d -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 6706378a4a6b4048bbfcba401575f936 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 75e6f3280f6e45b9b48e7d616f199aa9 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 9cc3195a6aba44ffb05f0c5f0d6e08fc -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 9608fcb29a4e41d6a8fbb434ee251740 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 a68720ed4ae4451fa2459bfe1c9fee43 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 d6fbcfcd005547d98dd26cbe4dc94e05 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 92b9deb750ab47af985dedad621a5d87 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 6b7e3692bbcf42f2a7913c4afdb87126 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 865143eadfe946ed9de7a7688b4db18d -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 b8f2e24d41e04ff6b8a32f7bdc88f846 -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 57979fee60934e7f8a4f4ff1330fb20d -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 491c0319f4f9467fb28492e46e88225a -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 85ca42bc6a90437c96b5aed70a94c171 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 6a96c1e3a70b4f9ea16eca7ac0f8f5ae -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 9572b20ad99441f3905611c2c8a0f671 -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 454d991eb872406d9a96ed1762d87fd6 -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 91f461ed80284ce4ab95b3145fa91a74 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 205268030ea749aaaca8b72e866c6265 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 99a02475a4474823ac102454de9289a3 -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 7b46299131ff4d61808a97837bf1c890 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 d8485d9a6af643a090b50a06260822a9 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 311c5e81f671403d81d7908edea0e5c1 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 693baabf7fd54e8dbbb1a7be6f989ee2 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:26 -#: b151193fb3e047eda14032e737c63650 -msgid "IPIP" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:28 -#: 87f65e55a8c542b99ade1a324e7f7d4e -msgid "" -"This is one of the simplest types of tunnels, as defined by :rfc:`2003`. It " -"takes an IPv4 packet and sends it as a payload of another IPv4 packet. For " -"this reason, there are no other configuration options for this kind of " -"tunnel." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:32 -#: ../../configuration/interfaces/tunnel.rst:50 -#: ../../configuration/interfaces/tunnel.rst:67 -#: ../../configuration/interfaces/tunnel.rst:89 -#: ../../configuration/interfaces/tunnel.rst:190 -#: b0e45f41c8894e9bbb1f55a2c075bd2e fc25967bdf544064b9aeb81cb54d4121 -#: 9666fb00460f47dc8239a1b66fc234f8 c539c4fae01a4f66a175044565fe35e9 -#: 67bf0165317c478fa9148d5f6c4c2a37 -msgid "An example:" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:42 -#: a33ee07355864ac89d93072f15290ac1 -msgid "IP6IP6" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:44 -#: 46829db2f10f428bbd41bdab5bddaaa4 -msgid "" -"This is the IPv6 counterpart of IPIP. I'm not aware of an RFC that defines " -"this encapsulation specifically, but it's a natural specific case of IPv6 " -"encapsulation mechanisms described in :rfc:2473`." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:48 -#: 6a86b1681089405199bd21b2491928e6 -msgid "" -"It's not likely that anyone will need it any time soon, but it does exist." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:60 -#: d4082a24ca0f40e2aea8a4ff9e98a14b -msgid "IPIP6" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:62 -#: 8af75c3f876745e5a57d117e22f8c0ef -msgid "" -"In the future this is expected to be a very useful protocol (though there " -"are `other proposals`_)." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:65 -#: 5b5b87809f134e35866ff347936c1430 -msgid "" -"As the name implies, it's IPv4 encapsulated in IPv6, as simple as that." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:77 -#: 580cdc6604024dabb40d8bd50a6260ba -msgid "6in4 (SIT)" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:79 -#: 89cd5ab44db34879b0a9b5e09f8866b4 -msgid "" -"6in4 uses tunneling to encapsulate IPv6 traffic over IPv4 links as defined " -"in :rfc:`4213`. The 6in4 traffic is sent over IPv4 inside IPv4 packets whose" -" IP headers have the IP protocol number set to 41. This protocol number is " -"specifically designated for IPv6 encapsulation, the IPv4 packet header is " -"immediately followed by the IPv6 packet being carried. The encapsulation " -"overhead is the size of the IPv4 header of 20 bytes, therefore with an MTU " -"of 1500 bytes, IPv6 packets of 1480 bytes can be sent without fragmentation." -" This tunneling technique is frequently used by IPv6 tunnel brokers like " -"`Hurricane Electric`_." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:98 -#: 49e85b13242c4e4f96775899e1cf2153 -msgid "" -"A full example of a Tunnelbroker.net config can be found at :ref:`here " -"<examples-tunnelbroker-ipv6>`." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:102 -#: f2c54aca23964dbc942b5b0697982295 -msgid "Generic Routing Encapsulation (GRE)" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:104 -#: c35d2f4103684f20945db93745927ae5 -msgid "" -"A GRE tunnel operates at layer 3 of the OSI model and is represented by IP " -"protocol 47. The main benefit of a GRE tunnel is that you are able to carry " -"multiple protocols inside the same tunnel. GRE also supports multicast " -"traffic and supports routing protocols that leverage multicast to form " -"neighbor adjacencies." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:110 -#: 4ed5edc555254668b0d1c10924f7e947 -msgid "" -"A VyOS GRE tunnel can carry both IPv4 and IPv6 traffic and can also be " -"created over either IPv4 (gre) or IPv6 (ip6gre)." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:115 -#: d77c25d6de8a425bb6a51c71cfebcc3b -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:117 -#: 07bffabda4d34ea09b0eb92554b1365b -msgid "" -"A basic configuration requires a tunnel source (source-address), a tunnel " -"destination (remote), an encapsulation type (gre), and an address " -"(ipv4/ipv6). Below is a basic IPv4 only configuration example taken from a " -"VyOS router and a Cisco IOS router. The main difference between these two " -"configurations is that VyOS requires you explicitly configure the " -"encapsulation type. The Cisco router defaults to GRE IP otherwise it would " -"have to be configured as well." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:124 -#: ../../configuration/interfaces/tunnel.rst:145 -#: 3cf14ec500bd46a98866a89cb689a9da d6e123bd798b44d4884c82afadcd21cc -msgid "**VyOS Router:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:133 -#: c8155402a6b94f518b29ca18ca78749e -msgid "**Cisco IOS Router:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:142 -#: 5398a448d41849e7a83855e8feec7d00 -msgid "" -"Here is a second example of a dual-stack tunnel over IPv6 between a VyOS " -"router and a Linux host using systemd-networkd." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:155 -#: 4fc76f4ce8e24167bd9ade89d0ae5faa -msgid "**Linux systemd-networkd:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:157 -#: b0fa4795150641768523fd6308d0244d -msgid "" -"This requires two files, one to create the device (XXX.netdev) and one to " -"configure the network on the device (XXX.network)" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:183 -#: e804245ca1fc4347b511dadc9525bd5f -msgid "Tunnel keys" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:185 -#: da2f4c93f18647d88f21a8600f0168f4 -msgid "" -"GRE is also the only classic protocol that allows creating multiple tunnels " -"with the same source and destination due to its support for tunnel keys. " -"Despite its name, this feature has nothing to do with security: it's simply " -"an identifier that allows routers to tell one tunnel from another." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:207 -#: fa7ebf37e9924485bfd9744aeb5b8474 -msgid "GRETAP" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:209 -#: 39358377fd2b42188b44d431c0e9df2c -msgid "" -"While normal GRE is for layer 3, GRETAP is for layer 2. GRETAP can " -"encapsulate Ethernet frames, thus it can be bridged with other interfaces to" -" create datalink layer segments that span multiple remote sites." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:223 -#: b6d9e3b53b9c42f49b2ff33be81e3f5d -msgid "Troubleshooting" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:225 -#: 3c0e0d048ed54015b343703077997c69 -msgid "" -"GRE is a well defined standard that is common in most networks. While not " -"inherently difficult to configure there are a couple of things to keep in " -"mind to make sure the configuration performs as expected. A common cause for" -" GRE tunnels to fail to come up correctly include ACL or Firewall " -"configurations that are discarding IP protocol 47 or blocking your " -"source/destination traffic." -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:231 -#: 7b67e03351864c5699f2478972a613b8 -msgid "" -"**1. Confirm IP connectivity between tunnel source-address and remote:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:246 -#: f8b2cf1dfdc84a868398121ad64528fe -msgid "**2. Confirm the link type has been set to GRE:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:263 -#: 912de8d676d84372b9a85d5c935ffc0e -msgid "**3. Confirm IP connectivity across the tunnel:**" -msgstr "" - -#: ../../configuration/interfaces/tunnel.rst:278 -#: 902dcd77a85a4bcb9ffbe77538581461 -msgid "" -"There is also a GRE over IPv6 encapsulation available, it is called: " -"``ip6gre``." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vti.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vti.po deleted file mode 100644 index 2c79e051..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vti.po +++ /dev/null @@ -1,52 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/vti.rst:5 ece3b9b5ceb44dd48b2eef45d29161c2 -msgid "VTI - Virtual Tunnel Interface" -msgstr "" - -#: ../../configuration/interfaces/vti.rst:7 d9210025e3454777853ff821a4f702e7 -msgid "Set Virtual Tunnel Interface" -msgstr "" - -#: ../../configuration/interfaces/vti.rst:14 5fae19d0ae2e49e2ae0607d9e7756b87 -msgid "Results in:" -msgstr "" - -#: ../../configuration/interfaces/vti.rst:25 5e68df2c354341febdf7628a9c26bed2 -msgid "" -"When using site-to-site IPsec with VTI interfaces, be sure to disable route " -"autoinstall" -msgstr "" - -#: ../../configuration/interfaces/vti.rst:32 9004d665083e497d9c6b279d5298489f -msgid "" -"More details about the IPsec and VTI issue and option disable-route-" -"autoinstall https://blog.vyos.io/vyos-1-dot-2-0-development-news-in-july" -msgstr "" - -#: ../../configuration/interfaces/vti.rst:35 a626cf0aaf8443f5a4484e0295813893 -msgid "" -"The root cause of the problem is that for VTI tunnels to work, their traffic" -" selectors have to be set to 0.0.0.0/0 for traffic to match the tunnel, even" -" though actual routing decision is made according to netfilter marks. Unless" -" route insertion is disabled entirely, StrongSWAN thus mistakenly inserts a " -"default route through the VTI peer address, which makes all traffic routed " -"to nowhere." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vxlan.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vxlan.po deleted file mode 100644 index 27dae9ef..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/vxlan.po +++ /dev/null @@ -1,724 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/vxlan.rst:7 861f5ae599e742f2919b15bfa636a4a6 -msgid "VXLAN" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:9 3c3d329833414a5687c59245dad6694d -msgid "" -":abbr:`VXLAN (Virtual Extensible LAN)` is a network virtualization " -"technology that attempts to address the scalability problems associated with" -" large cloud computing deployments. It uses a VLAN-like encapsulation " -"technique to encapsulate OSI layer 2 Ethernet frames within layer 4 UDP " -"datagrams, using 4789 as the default IANA-assigned destination UDP port " -"number. VXLAN endpoints, which terminate VXLAN tunnels and may be either " -"virtual or physical switch ports, are known as :abbr:`VTEPs (VXLAN tunnel " -"endpoints)`." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:17 -#: 26316c6cfdfa4532bbd34f3570cd0d48 -msgid "" -"VXLAN is an evolution of efforts to standardize an overlay encapsulation " -"protocol. It increases the scalability up to 16 million logical networks and" -" allows for layer 2 adjacency across IP networks. Multicast or unicast with " -"head-end replication (HER) is used to flood broadcast, unknown unicast, and " -"multicast (BUM) traffic." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:23 -#: 79fddbeedccc48119d0e8f371e2eb25d -msgid "" -"The VXLAN specification was originally created by VMware, Arista Networks " -"and Cisco. Other backers of the VXLAN technology include Huawei, Broadcom, " -"Citrix, Pica8, Big Switch Networks, Cumulus Networks, Dell EMC, Ericsson, " -"Mellanox, FreeBSD, OpenBSD, Red Hat, Joyent, and Juniper Networks." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:28 -#: 07da17ff720d453cb1e2d8b3893ca56c -msgid "VXLAN was officially documented by the IETF in :rfc:`7348`." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:30 -#: 312bc701f4ed4e00a097ea0133053efe -msgid "" -"If configuring VXLAN in a VyOS virtual machine, ensure that MAC spoofing " -"(Hyper-V) or Forged Transmits (ESX) are permitted, otherwise forwarded " -"frames may be blocked by the hypervisor." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:34 -#: ab11a1c69bb5470a801fc2a5f242200f -msgid "" -"As VyOS is based on Linux and there was no official IANA port assigned for " -"VXLAN, VyOS uses a default port of 8472. You can change the port on a per " -"VXLAN interface basis to get it working across multiple vendors." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:39 -#: 8c5a8c7c253d4b1895bd2ce80f392531 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:42 -#: 02b83fdbc2f04e53bf3c16732716d50b -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address.txt:3 653c18aa4561494da3ebea0bf45edd5c -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address.txt:6 71bd0c05ea8a4652955b410c91695dd5 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address.txt:9 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: 85c1440ebde046739458cc08b8dc9375 21a27ae41dd0478e8921c4178c3dd960 -#: 1f2088f1d6d44e6c92b7970a0ae6ce60 8e2e4ac8e1274547a54ba61155da6911 -#: 8489c3c9cd2d47eb9b6ef29c3121a2a3 58c30e7dee4a4f1d9083f70b263997ac -#: 3f2ae39087cc4dc38c8db7c826766559 452f33461dce4124b7858a2cddd10acf -#: 19bba869306d490280be69696be1252d e2cb58dc453342899a4ef2b53f3a1bc2 -#: f38c70d59faa4518818be55cdb052165 97c4a321888e4ca5bfa0ed0dd14e982c -#: a6940bfc66f74bd1932c0d4a277cb46f 9bd19c5b8d034647aa83e95f0da0a19b -#: f96c6d0348b642e5846c46d22ae36eb2 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 bd5c089ee1fd4f6388d331df1315b0e8 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 73c54ed5e5544a939383fdd677f37094 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: e23d83c2bce84b57b30e40f2b301ca2d -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: 676d243f0315463aba3a7c35afe47d38 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: fe5cb1e527c24d9eb3fbfee7f33e8f88 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: 489b6f34a79b49ecb8444985b95bec9b -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: 435f0bca1cee488ab6679c6d3881c6df -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: f9dbed0a960040ce883a30d13efb1836 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 77fadc2e085a4ba1abbd89f881fd73c0 -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 553ada5da7ef461fb618c44671d872c8 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: da5725692ac947958eaeb7e09b13c717 8b6801f4e72040a7a5a3b0db8a1e8ce1 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 c13731a10863498ab456d67a41f9bf4c -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ff609c51ef04466d8b56128d61698dcd -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: e6647173df5940febea0a7569406e00d 993cc711f0684e82a1c7c00c9fc22554 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 2f039362e97b434babaa612730aa546a -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 46afb4fa52034043b3cda8fc97a1c8a2 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 d3f58cb3133d4fbabf001760cf98cba1 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 2030c890f148423a9c9c9871641141f5 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 1a49daee52914cb5bb02b9a5ba8f4fa7 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 18f7de617f3c4486aba7e7a1da21463c 598c280233154eef85320c5c51fae210 -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 011e73345e9443e1bc481ffba93c4200 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 f535c0edab444846a03327282fcd46c9 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 92d2ce61725e4bfe8b116714e89974f2 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 e5494815eb8e4cdab930669949a30e29 -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 8719d6792af347dcbf90227f8e9ee7f4 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 0284e8a19c8148d18e9ea7dc23f731db -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 7c37ae8855094bc3afaae4b475cd9cbd -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 a349f62e6831499b8099c5ccff2a96e8 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 4b5ae8e0d3334aabb04ba418872e9036 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 aee5e92031404e79b3cd8257a7c1ccf7 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 a571c97ccb5f4be6bb8edd134685c5e7 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 30d493e68a3f4e4ab00048a2007d3797 -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 51faa1903f8648e58e874cb3c02f0494 -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 80b676f56c784515b2214e5bb2b92492 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 e10e8175f80f4758aff03302083e5867 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 0d9b15c1b3d84918937bc20888c57dd8 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 bef9c002bf4c43b18dd17314f7155b6f -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 c5e66eaa42894b919444ba115db00246 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 139cf4329e5d4b6a833a6b3518a1d828 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 6680ee41c8d14b838f93126ec55533e4 -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 8dfb99a102aa49d6bdb44d25e7b82a28 -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 3e9163776b9d426bbebe7024acd9c6ed -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 90a30406470244ceb8e2010529479723 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 e3efa5b9d49d4495a2bc0a54bd68dd43 -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 d9418e17490c4a22badeebcd573131cb -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 b1f43c681c274734804516e931f6bf1b -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 395b248df78341caadfde30698c7399b -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 81e4b4f9b5e640559321657da11cabe7 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 deec060d699c4d359dbb5ef5186413d5 -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 10c9858d52984653b4ea942cfa5695c1 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 a2b95daa10ba401783fd7434a31bfa3b -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 a9dd6e480e244b208cdd37e605a843b5 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 e04116eef19742b7a60d2774810dd5e5 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:49 -#: 1476323fe1c54f98b88e61e3473e54ca -msgid "VXLAN specific options" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:53 -#: 80dd1b1d972247d99c27e24d530a1401 -msgid "" -"Each VXLAN segment is identified through a 24-bit segment ID, termed the " -":abbr:`VNI (VXLAN Network Identifier (or VXLAN Segment ID))`, This allows up" -" to 16M VXLAN segments to coexist within the same administrative domain." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:59 -#: b064c6b2bebf49c1a0d50f107f200ca3 -msgid "Configure port number of remote VXLAN endpoint." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:61 -#: 88fd9cfc91d74705b8dcf5ee711321cf -msgid "" -"As VyOS is Linux based the default port used is not using 4789 as the " -"default IANA-assigned destination UDP port number. Instead VyOS uses the " -"Linux default port of 8472." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:67 -#: 3f744f355bef4481bb55ddcedaefb933 -msgid "" -"Source IP address used for VXLAN underlay. This is mandatory when using " -"VXLAN via L2VPN/EVPN." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:72 -#: f9f0162c65b54bde997a5a8356580007 -msgid "" -"Specifies whether an external control plane (e.g. BGP L2VPN/EVPN) or the " -"internal FDB should be used." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:77 -#: fcf40ec79f7344a0acbb50e2833219d4 -msgid "" -"Eenables the Generic Protocol extension (VXLAN-GPE). Currently, this is only" -" supported together with the external keyword." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:81 -#: ea8ed064d99842139fb29f1f91a03472 -msgid "Unicast" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:85 -#: 95b19e1341064663a8897744a5ad653f -msgid "" -"IPv4/IPv6 remote address of the VXLAN tunnel. Alternative to multicast, the " -"remote IPv4/IPv6 address can set directly." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:89 -#: 1800ab3e0d314294a45522b960de7903 -msgid "Multicast" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:93 -#: ec86ed7adb54440fbe1f7f47a4402f7e -msgid "" -"Interface used for VXLAN underlay. This is mandatory when using VXLAN via a " -"multicast network. VXLAN traffic will always enter and exit this interface." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:99 -#: d0b716a849e94f3dbced13299e986051 -msgid "" -"Multicast group address for VXLAN interface. VXLAN tunnels can be built " -"either via Multicast or via Unicast." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:102 -#: 9840154fd32c493c910ca16537811da7 -msgid "Both IPv4 and IPv6 multicast is possible." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:105 -#: 37ddf648102d4acdbdc8fd8d8ce0ca5d -msgid "Multicast VXLAN" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:107 -#: b1fcbb04245b46ba90fc2520b4a31896 -msgid "Topology: PC4 - Leaf2 - Spine1 - Leaf3 - PC5" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:109 -#: a86f72f507ce47fda688f8efd3ffc9e4 -msgid "" -"PC4 has IP 10.0.0.4/24 and PC5 has IP 10.0.0.5/24, so they believe they are " -"in the same broadcast domain." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:112 -#: 9e6506a0ad5e47b0bec15a4b12df250f -msgid "" -"Let's assume PC4 on Leaf2 wants to ping PC5 on Leaf3. Instead of setting " -"Leaf3 as our remote end manually, Leaf2 encapsulates the packet into a UDP-" -"packet and sends it to its designated multicast-address via Spine1. When " -"Spine1 receives this packet it forwards it to all other leaves who has " -"joined the same multicast-group, in this case Leaf3. When Leaf3 receives the" -" packet it forwards it, while at the same time learning that PC4 is " -"reachable behind Leaf2, because the encapsulated packet had Leaf2's IP " -"address set as source IP." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:120 -#: 3422507669e04dbeacbf442b9c3475fa -msgid "" -"PC5 receives the ping echo, responds with an echo reply that Leaf3 receives " -"and this time forwards to Leaf2's unicast address directly because it " -"learned the location of PC4 above. When Leaf2 receives the echo reply from " -"PC5 it sees that it came from Leaf3 and so remembers that PC5 is reachable " -"via Leaf3." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:125 -#: 9d0e7a2289144212bc401909e045be60 -msgid "" -"Thanks to this discovery, any subsequent traffic between PC4 and PC5 will " -"not be using the multicast-address between the leaves as they both know " -"behind which Leaf the PCs are connected. This saves traffic as less " -"multicast packets sent reduces the load on the network, which improves " -"scalability when more leaves are added." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:131 -#: 73db07c32dc646808feeb341b0c5dd8f -msgid "" -"For optimal scalability, Multicast shouldn't be used at all, but instead use" -" BGP to signal all connected devices between leaves. Unfortunately, VyOS " -"does not yet support this." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:136 -#: 926a7f86dd7949dfa2c603aaabb8b49e -msgid "Example" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:138 -#: 107ad2c3a2ba4decbceb11f7dd0a6dbf -msgid "The setup is this: Leaf2 - Spine1 - Leaf3" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:140 -#: 916193a4d6204668be8a32c031dd5d13 -msgid "" -"Spine1 is a Cisco IOS router running version 15.4, Leaf2 and Leaf3 is each a" -" VyOS router running 1.2." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:143 -#: f9e58e6df40e4d6a811315fbc570286d -msgid "This topology was built using GNS3." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:145 -#: 8058a20e78a74ed597ac686040016dad -msgid "Topology:" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:161 -#: 2dce7611b99741e5adbfef04c2aefcec -msgid "**Spine1 Configuration:**" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:179 -#: 691055343fbb44bb9fbb82905b0925c7 -msgid "" -"Multicast-routing is required for the leaves to forward traffic between each" -" other in a more scalable way. This also requires PIM to be enabled towards " -"the leaves so that the Spine can learn what multicast groups each Leaf " -"expects traffic from." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:184 -#: 458b3a86f34348e598277ab8179fd711 -msgid "**Leaf2 configuration:**" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:209 -#: 4534495a3a3b476e9de8ff22e94caf20 -msgid "**Leaf3 configuration:**" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:234 -#: fde246b1b0164d30aba06fe4fd8edb92 -msgid "" -"As you can see, Leaf2 and Leaf3 configuration is almost identical. There are" -" lots of commands above, I'll try to into more detail below, command " -"descriptions are placed under the command boxes:" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:242 -#: c9be86b1405540a68f8843486e0b8001 -msgid "" -"This commands creates a bridge that is used to bind traffic on eth1 vlan 241" -" with the vxlan241-interface. The IP address is not required. It may however" -" be used as a default gateway for each Leaf which allows devices on the vlan" -" to reach other subnets. This requires that the subnets are redistributed by" -" OSPF so that the Spine will learn how to reach it. To do this you need to " -"change the OSPF network from '10.0.0.0/8' to '0.0.0.0/0' to allow " -"172.16/12-networks to be advertised." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:255 -#: 0e61439579354d8d9a45de2547e2c10b -msgid "" -"Binds eth1.241 and vxlan241 to each other by making them both member " -"interfaces of the same bridge." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:262 -#: 6489cee9f7ae49cbac8fe1b2ba49d79e -msgid "" -"The multicast-group used by all leaves for this vlan extension. Has to be " -"the same on all leaves that has this interface." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:269 -#: 2066c6b7213242ce8331e2645c575637 -msgid "" -"Sets the interface to listen for multicast packets on. Could be a loopback, " -"not yet tested." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:276 -#: f94113b900fe4be9a24425630b69055d -msgid "" -"Sets the unique id for this vxlan-interface. Not sure how it correlates with" -" multicast-address." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:283 -#: 668dbcb7aaa54add97365968915bfcae -msgid "" -"The destination port used for creating a VXLAN interface in Linux defaults " -"to its pre-standard value of 8472 to preserve backward compatibility. A " -"configuration directive to support a user-specified destination port to " -"override that behavior is available using the above command." -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:289 -#: aba21afdabbc4e148e4c30cab03dc66d -msgid "Unicast VXLAN" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:291 -#: f30d134ae72442c8b1a589d0886f64aa -msgid "" -"Alternative to multicast, the remote IPv4 address of the VXLAN tunnel can be" -" set directly. Let's change the Multicast example from above:" -msgstr "" - -#: ../../configuration/interfaces/vxlan.rst:306 -#: d870be0823214e3aa5ee2fdd008decec -msgid "" -"The default port udp is set to 8472. It can be changed with ``set interface " -"vxlan <vxlanN> port <port>``" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireguard.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireguard.po deleted file mode 100644 index 4acec936..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireguard.po +++ /dev/null @@ -1,372 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/wireguard.rst:7 -#: a1bee5f5221a453aaf1cd16cb00b6129 -msgid "WireGuard" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:9 -#: 710bfba9877a436bb50b7c27cde335f7 -msgid "" -"WireGuard is an extremely simple yet fast and modern VPN that utilizes " -"state-of-the-art cryptography. See https://www.wireguard.com for more " -"information." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:15 -#: 3435bf602fee482387028b79743e9eab -msgid "Site to Site VPN" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:17 -#: d6aa2700e90143f287d2a94c1cf3b1d6 -msgid "" -"This diagram corresponds with the example site to site configuration below." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:23 -#: ec99e10935ac4c93bc66cbce754ebdc6 -msgid "Keypairs" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:25 -#: d04e0d6124264156a0220815965a0f2b -msgid "" -"WireGuard requires the generation of a keypair, which includes a private key" -" to decrypt incoming traffic, and a public key for peer(s) to encrypt " -"traffic." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:29 -#: c8be0ca19d684d8a889a10e4f1d3f3a9 -msgid "Generate Keypair" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:33 -#: 13d45a18444e45aa86f39e1417764b47 -msgid "" -"It generates the keypair, which includes the public and private parts. The " -"key is not stored on the system - only a keypair is generated." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:44 -#: 0272e272bba34e2aaaaa9ff6b27f2d35 -msgid "" -"Generates a keypair, which includes the public and private parts, and build " -"a configuration command to install this key to ``interface``." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:57 -#: ../../configuration/interfaces/wireguard.rst:120 -#: 31f23ec215da437aa4e8356459455d6c 3f2023b9d9ee4ebc943bef15afb2bf6a -msgid "" -"If this command is invoked from configure mode with the ``run`` prefix the " -"key is automatically installed to the appropriate interface:" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:77 -#: 9f257b81f6504655a735155401277302 -msgid "Retrieve public key portion from configured WIreGuard interface." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:86 -#: f2af224a811e4c4c92b9df55aa527e0a -msgid "Optional" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:90 -#: b00f9a26c713415792790e3eae8c3430 -msgid "" -"An additional layer of symmetric-key crypto can be used on top of the " -"asymmetric crypto." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:93 -#: ../../configuration/interfaces/wireguard.rst:107 -#: f2116c1a9f2f4ffc82656d101b7dcdf1 675df37fb69747e3955e2a707047f583 -msgid "This is optional." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:103 -#: f0fff0ae537549ab86505d1a104b35b1 -msgid "" -"An additional layer of symmetric-key crypto can be used on top of the " -"asymmetric crypto. This command automatically creates for you the required " -"CLI command to install this PSK for a given peer." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:126 -#: 7c99f5758f9c457a9212343271e4b987 -msgid "Interface configuration" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:128 -#: 24a42de74dfd456eb95e6a0dd6b1c53a -msgid "" -"The next step is to configure your local side as well as the policy based " -"trusted destination addresses. If you only initiate a connection, the listen" -" port and address/port is optional; however, if you act like a server and " -"endpoints initiate the connections to your system, you need to define a port" -" your clients can connect to, otherwise the port is randomly chosen and may " -"make connection difficult with firewall rules, since the port may be " -"different each time the system is rebooted." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:136 -#: 0deee65bec00410eafa271fb1247fdcb -msgid "" -"You will also need the public key of your peer as well as the network(s) you" -" want to tunnel (allowed-ips) to configure a WireGuard tunnel. The public " -"key below is always the public key from your peer, not your local one." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:140 -#: ba5550371dcf4d778767b5ab35a38b0a -msgid "**local side - commands**" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:142 -#: 4d65a076c1194586a18aa696727290fe -msgid "WireGuard interface itself uses address 10.1.0.1/30" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:143 -#: 769476a44da940689a48ce04125ad8a6 -msgid "We only allow the 192.168.2.0/24 subnet to travel over the tunnel" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:144 -#: 4b962d4e32fc4719a0e6e1d8c9422db0 -msgid "" -"Our remote end of the tunnel for peer `to-wg02` is reachable at 192.0.2.1 " -"port 51820" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:146 -#: aaea26c9ecba457b8a3bfc95acd32fb7 -msgid "" -"The remote peer `to-wg02` uses XMrlPykaxhdAAiSjhtPlvi30NVkvLQliQuKP7AI7CyI= " -"as its public key portion" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:148 -#: 384cc95688fe4980b69440e39bb8681d -msgid "We listen on port 51820" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:149 -#: 730b88fad94646b5a9f9f81a42d71455 -msgid "" -"We route all traffic for the 192.168.2.0/24 network to interface `wg01`" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:163 -#: 6f4ee13223c14b94a51a25a20db46d19 -msgid "" -"The last step is to define an interface route for 192.168.2.0/24 to get " -"through the WireGuard interface `wg01`. Multiple IPs or networks can be " -"defined and routed. The last check is allowed-ips which either prevents or " -"allows the traffic." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:168 -#: 333629b161c34847a2a56c56143833f4 -msgid "" -"You can not assign the same allowed-ips statement to multiple WireGuard " -"peers. This a design decision. For more information please check the " -"`WireGuard mailing list`_." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:174 -#: 5ce51b439ec347768b4f74bb19cec70e -msgid "" -"Associates the previously generated private key to a specific WireGuard " -"interface. The private key can be generate via the command :opcmd:`generate " -"pki wireguard key-pair`." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:182 -#: 28863acf61374fa4898e36969aeea933 -msgid "" -"The command :opcmd:`show interfaces wireguard wg01 public-key` will then " -"show the public key, which needs to be shared with the peer." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:185 -#: 0070cb42879e45c18f19f855a89af73c -msgid "**remote side - commands**" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:201 -#: 216ca950a66847a8b152b646cb9a35ea -msgid "Firewall Exceptions" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:203 -#: e892a0980c394747a411659ab5bb5618 -msgid "" -"For the WireGuard traffic to pass through the WAN interface, you must create" -" a firewall exception." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:219 -#: 1e9c996c042748aeb8d5b73959b61342 -msgid "" -"You should also ensure that the OUTISDE_LOCAL firewall group is applied to " -"the WAN interface and a direction (local)." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:226 -#: 878579387eb849d1b7740e5b814fd244 -msgid "" -"Assure that your firewall rules allow the traffic, in which case you have a " -"working VPN using WireGuard." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:241 -#: 2962f488240a4e05b65a2cf2912a3708 -msgid "" -"An additional layer of symmetric-key crypto can be used on top of the " -"asymmetric crypto. This is optional." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:249 -#: 44ee94bee28443cd92075862639cc18b -msgid "" -"Copy the key, as it is not stored on the local filesystem. Because it is a " -"symmetric key, only you and your peer should have knowledge of its content. " -"Make sure you distribute the key in a safe manner," -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:261 -#: 8e6f16c2d425421f949bb875bbfc15ef -msgid "Remote Access \"RoadWarrior\" Example" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:263 -#: 5b103c21987d42a1a8999ad95bd9dfbf -msgid "" -"With WireGuard, a Road Warrior VPN config is similar to a site-to-site VPN. " -"It just lacks the ``address`` and ``port`` statements." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:266 -#: 17a313f0dc7646e59fd0a552d16f5757 -msgid "" -"In the following example, the IPs for the remote clients are defined in the " -"peers. This allows the peers to interact with one another. In comparison to " -"the site-to-site example the ``persistent-keepalive`` flag is set to 15 " -"seconds to assure the connection is kept alive. This is mainly relevant if " -"one of the peers is behind NAT and can't be connected to if the connection " -"is lost. To be effective this value needs to be lower than the UDP timeout." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:295 -#: 25cf7f28ebd74991a17c92edf42ca10c -msgid "" -"The following is the config for the iPhone peer above. It's important to " -"note that the ``AllowedIPs`` wildcard setting directs all IPv4 and IPv6 " -"traffic through the connection." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:312 -#: b0aecf335b6a4073ae9dd69c800e64dd -msgid "" -"However, split-tunneling can be achieved by specifying the remote subnets. " -"This ensures that only traffic destined for the remote site is sent over the" -" tunnel. All other traffic is unaffected." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:331 -#: 964f1ba345564dbabe3008c96efd1e88 -msgid "Operational Commands" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:334 -#: b9cfaeb7547c4c40963e6702a11566cd -msgid "Status" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:338 -#: 2211de4664e4433ab4e4bed8ebb59bf0 -msgid "" -"Show info about the Wireguard service. It also shows the latest handshake." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:357 -#: 4daa4d6d12654c81b93ee6e4218007d4 -msgid "Get a list of all wireguard interfaces" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:369 -#: d21be5b2fffc448596ed14ca4b478572 -msgid "Show general information about specific WireGuard interface" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:387 -#: 7564628d39d84223ae0163f5bf633cd4 -msgid "Remote Access \"RoadWarrior\" clients" -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:389 -#: ccf0c6ec8d3949c3b619991d0c0a97b1 -msgid "" -"Some users tend to connect their mobile devices using WireGuard to their " -"VyOS router. To ease deployment one can generate a \"per mobile\" " -"configuration from the VyOS CLI." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:393 -#: 3830e59d42034f69adc601a57fac3846 -msgid "" -"From a security perspective, it is not recommended to let a third party " -"create and share the private key for a secured connection. You should create" -" the private portion on your own and only hand out the public key. Please " -"keep this in mind when using this convenience feature." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:401 -#: 4aaf366a8434463885eb6c386837abb4 -msgid "" -"Using this command, you will create a new client configuration which can " -"connect to ``interface`` on this router. The public key from the specified " -"interface is automatically extracted and embedded into the configuration." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:405 -#: ee4f0857baa449ceb1212c77e5a21807 -msgid "" -"The command also generates a configuration snipped which can be copy/pasted " -"into the VyOS CLI if needed. The supplied ``<name>`` on the CLI will become " -"the peer name in the snippet." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:409 -#: c5728006d4fa435eb2be15a7683d6aac -msgid "" -"In addition you will specifiy the IP address or FQDN for the client where it" -" will connect to. The address parameter can be used up to two times and is " -"used to assign the clients specific IPv4 (/32) or IPv6 (/128) address." -msgstr "" - -#: ../../configuration/interfaces/wireguard.rst:0 -#: c602b15c70a844c1b9d77f134396f260 -msgid "WireGuard Client QR code" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireless.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireless.po deleted file mode 100644 index b94fa2d9..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wireless.po +++ /dev/null @@ -1,1572 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/wireless.rst:7 -#: 20115b15c5c645bea759c2601c38514b -msgid "WLAN/WIFI - Wireless LAN" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:9 -#: e529c649b2a04616af0b5f31a9fdf7c9 -msgid "" -":abbr:`WLAN (Wireless LAN)` interface provide 802.11 (a/b/g/n/ac) wireless " -"support (commonly referred to as Wi-Fi) by means of compatible hardware. If " -"your hardware supports it, VyOS supports multiple logical wireless " -"interfaces per physical device." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:14 -#: 50064d15971c4d5b9e5c9ee68cc7ff8a -msgid "There are three modes of operation for a wireless interface:" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:16 -#: 5b8df8d4acaf483b9cca233de479e192 -msgid "" -":abbr:`WAP (Wireless Access-Point)` provides network access to connecting " -"stations if the physical hardware supports acting as a WAP" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:19 -#: a9bd389b390c49ce9f5404460a88e6de -msgid "" -"A station acts as a Wi-Fi client accessing the network through an available " -"WAP" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:22 -#: d7add0b075854fada71bbfb9aa49230b -msgid "Monitor, the system passively monitors any kind of wireless traffic" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:24 -#: dc7e79b4145b4c14b7ac4b3de6a6007b -msgid "" -"If the system detects an unconfigured wireless device, it will be " -"automatically added the configuration tree, specifying any detected settings" -" (for example, its MAC address) and configured to run in monitor mode." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:30 -#: 548c76a6090149309972d31ab082e81b -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:33 -#: 43e109ec036348bc90aa19197046175a -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: ../../_include/interface-address-with-dhcp.txt:5 -#: 64e735ebabbc466cb52033a2a082d264 57246a96ef5d497899bcc84172bfff6f -#: 3453c0b1a3e54883ae4f96a4e5acf68a -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: ../../_include/interface-address-with-dhcp.txt:7 -#: faf9c99a90e14410bba71dd33d0f7c2b a9f3d099fcf54607a4dd0a52d2bfe1c9 -#: 301c94dea49d4ade922d327f4ea3095d -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: ../../_include/interface-address-with-dhcp.txt:9 -#: 99022064010c415fbdab012ab2c3717b e6d7474943cf4be3a8161f46332c3eff -#: 80098fc524274a0faaabfa0442f7190f -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: ../../_include/interface-address-with-dhcp.txt:11 -#: 30ae2f9731094d9aa1f37bdcee8d885c ad5650ad75764e0a886b949b60e20f65 -#: 55331c68164a4374806c0dba56e9abd9 -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-flow-control.txt:19 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mac.txt:7 ../../_include/interface-mtu.txt:7 -#: ../../_include/interface-ip.txt:27 ../../_include/interface-ip.txt:50 -#: ../../_include/interface-ip.txt:144 ../../_include/interface-ipv6.txt:15 -#: ../../_include/interface-ipv6.txt:28 ../../_include/interface-ipv6.txt:39 -#: ../../_include/interface-ipv6.txt:51 ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: d075f8db40c5418ea4c1a1704cef6e81 988edef453e3480a810923d8d2bcc92d -#: 8cfe009b5b634fd0b068fb6e52528497 cca08a922abc41f592773032b9b6b82f -#: a43c4d4d979c43c498172e526c4d7887 eb8815eb4b0b42c389042a973dd6973f -#: fa6408bdb6fc4a27ae9487925dc8449d aaf82d9b1b624dd9b3beb53995329719 -#: 02e7e3548d8d414098ee34fbff3cdc6f 4abc7f81cab441bdafb0d8ea664fc278 -#: 0140ef4bb509470b832a1be2008c8446 6eee9dee1c324fe59635d284c0e6c0e3 -#: 49fa76506cff49f9b66a6efbf7cfb52a c2a4b54d20214562ab3233d2fb5ee8c8 -#: 53c11aec868649c0a8e90205edf4f3ed 2c024d4b4e1c45289462454257eda919 -#: 87ec30c119944aea949576fbb979b312 57f099a0cdc9414e810d156a0dc45795 -#: 72c13d0ffa8a40b79d41f89bc8e96236 83202428ee4b40bb9566a4eef0c56dc2 -#: 1d2211629c4f4226a338d5fb5804712a 247372958c3548a2b2e34a830721daa5 -#: 24d512ffd7df401c9b353e819bd1b121 cd79b3b34de04efcbdba01a3e87d5e70 -#: 46cdeb1cd32c4a889e0487fc978ba073 26a2d3ccd36f43d0a23efd91eb837a6f -#: a22f76e775df4fe3aa0fbd5ba8e2b467 05dabf01a2af4eee978d0b311c6949a8 -#: e946a9404cb54954bc2e0c41cbec94dd 1892051b92284d259973d9a12e432c82 -#: 86c53fd0f4634409bde12b7a88a1d46c 3df471d1a6394e81aa22cb0413fa6630 -#: b74685e1843d46658140a9bde59a3960 f226ac4aaaea4ea4b762ce2f95b3d5ce -#: fb184aa1935f42ff8f30d59d59dee3fb b3f0ab95287f46fbbebc4121d39eddaf -#: 18bbffc4efdb4d0da0d4da34c36ef653 8b0092835fc546088690310c5fdfd5ae -#: a1d7c12738c24411bf8866b734bf454c 40f49e482a204755b38aa2499b346323 -#: b96778269ecd4bcca0b97b9de464be9d f376d894ed514da9bb17b1c87fe88f81 -#: 0d5dd990535948f7be021b6b45071604 695662cd03e542a2b74731f8e63901db -#: dc4f93b9a1144c9cb40321227219f116 6168bf3874474e88abec4467c5de3b08 -#: bb043b1c32af457786e985b06dd392e2 d68ebc833ff5418cb667cbf73a6a2094 -#: 7e52ba614fb0404d8e7638be6b8125d5 ad5d9162f27043b992c5199ccd288542 -#: ec9c428a47764e81a3d11a4141e1c3e1 69424404178742b7b3cd7e6d34907797 -#: e3a3cb65e1d74dcea992f92b7507fb95 e31e5834ffb7405a925f4ff742d6c2d6 -#: fd14f99be9254cbd80b99f727715dcb8 75d0c545272a465e848e2d09532b6ef1 -#: 7b4d426c9fb741d9a1133904366cdff1 2f2887262c894886957062f197d9868e -#: 8ed81633f76d43d5843f36ce9c57c52a b7e2945689cd499ba96b92a93b63c8a9 -#: 6b4c42cf10de4e00b9ad94cd2f897dbf -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 -#: ../../_include/interface-description.txt:4 b9c4fce4eb7641329335e71fa231642e -#: 3c7404858f26425f90050f4a6b55b9cf 7287c6ec7eb4480e971fedb60892e2e4 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 -#: ../../_include/interface-disable.txt:4 2c71155c633441c7ab6e11fe696e996f -#: a1466ef612fb4ee196ee3c87781e683a 5eee8f3c01b849e6a72472b1f9b7b5b7 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:4 -#: ec74d93ce97f46bf85f30e4cc4ee4062 -msgid "" -"Ethernet flow control is a mechanism for temporarily stopping the " -"transmission of data on Ethernet family computer networks. The goal of this " -"mechanism is to ensure zero packet loss in the presence of network " -"congestion." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:8 -#: c4e5bb7639634f9f8bd6fe58638d3966 -msgid "" -"The first flow control mechanism, the pause frame, was defined by the IEEE " -"802.3x standard." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:11 -#: 5b7757e131ec427d9f0beaa4db45a908 -msgid "" -"A sending station (computer or network switch) may be transmitting data " -"faster than the other end of the link can accept it. Using flow control, the" -" receiving station can signal the sender requesting suspension of " -"transmissions until the receiver catches up." -msgstr "" - -#: ../../_include/interface-disable-flow-control.txt:16 -#: e8b99801c6a9491d8d3d9ed85b1d47b2 -msgid "" -"Use this command to disable the generation of Ethernet flow control (pause " -"frames)." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: ../../_include/interface-disable-link-detect.txt:4 -#: f390c8577952437988612b684bf15254 e83632b9c4804bc18e9268b8039b0df4 -#: 0918f0c4d9864630a811c77d2083960f -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: ../../_include/interface-disable-link-detect.txt:7 -#: a51d2c64cd224900bc4ab653707616a0 51a7029e2e824e7e9f19b1058c26e4cc -#: c4ff527da37f40dc8e6614864fe9294e -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mac.txt:4 ../../_include/interface-mac.txt:4 -#: ../../_include/interface-mac.txt:4 e72eb5bab64f42889fb75b2bda69e198 -#: 93572c9687ea4575bfbdad90689f89a9 264b1049a70f4dfe8874346c20263e5f -msgid "" -"Configure user defined :abbr:`MAC (Media Access Control)` address on given " -"`<interface>`." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 ../../_include/interface-mtu.txt:4 -#: ../../_include/interface-mtu.txt:4 f83f2cc7608647ae82ae7730bbb795d3 -#: 6ba11578219b46e9961d7fcae21e65d6 8f92e31c2d644004aa6f0ff5265b1d64 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 3dabef798955488c9753c6201e5bbfe4 63f88e9e6cfe4c28a49dc1cd6db3f479 -#: 1b0cfc5cee2d462b8e067511b03e3405 f1a7432a5fe548cf8cc4160df068214a -#: 261e09d5c0f944efa625b870fb341a4f 663f02baaa0b4de39741ada3b6f966fb -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 ../../_include/interface-ip.txt:9 -#: ../../_include/interface-ip.txt:9 f9e7d65a37464cf7ad165fb694b067fa -#: e3f8cb9772eb46069938fa5115370b45 451477e166174e62bdb1833d89f8ef34 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 ../../_include/interface-ip.txt:12 -#: ../../_include/interface-ip.txt:12 986151f86163427ba9a0b734dbedc6d6 -#: c8a9c7319d7b4db4a0abb069b1622731 e7490d46b17f41e1bcd0268ef2e59545 -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: 94565b0d27eb437c954a27ae7e940aa5 dc3ff4ad684f4479afb314121db647ea -#: de11dd276a59473693d7bdc6a24a2625 a4efc44607fc415ca512f1ca72e771b0 -#: f685f09511774ffbbbc225989ca53eb7 5c20874f2dca47e5b866db272b3ad5f2 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 ../../_include/interface-ip.txt:21 -#: ../../_include/interface-ip.txt:21 2144bfa77bb34129b375a074907419a0 -#: 6648858a5ae24de185d8e7fb83f7a1ab efdd5438f0874248acfd014aa2aecc54 -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 ../../_include/interface-ip.txt:25 -#: ../../_include/interface-ip.txt:25 d3ae50404503400bb84db7f774e152fa -#: 1bf65df895c948b88c4bb1042073ca1e e550d7b695f844b69e818844a8470ed0 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ../../_include/interface-ip.txt:36 -#: ../../_include/interface-ip.txt:36 037ac34cdbd74c4680e7edf07d25d5ab -#: ab987580917f4e51ba49aee7fd36a20a c5349412c1bf4d43a7f024eac8b78e6f -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 ../../_include/interface-ip.txt:42 -#: ../../_include/interface-ip.txt:42 3948c9fc6b10445b8d197d3534feae3f -#: 53afd2cb95524084a221332a830d2919 e0374d18d6494e61b6f1e5619a57a479 -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 ../../_include/interface-ip.txt:47 -#: ../../_include/interface-ip.txt:47 7d6150450547465fb395db4ae575b1a1 -#: c64abeade4b44298b10c81b674b76217 c8c6952432cb4272b7716fd5d44f9b2e -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: d90b833b8c7142ee821f06f74e02049a 52831c8a3bd445cebe759cc6687b57d4 -#: 2efb82dfd1894597b71f32affca5c42e 37b6a70d2a984ab582b73ab9f1317d8f -#: 13078d67b47a44cb93f9039d062fc472 9182f1d14dac42df8435cc2246e6a46d -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 ../../_include/interface-ip.txt:69 -#: ../../_include/interface-ip.txt:69 5500ab520c22421eae8e05fdae62e87e -#: 8b2bd307e8c74d69be4f3a566fc41025 22ae6c986ee54029838d40c3a958794a -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 ../../_include/interface-ip.txt:72 -#: ../../_include/interface-ip.txt:72 a8786e44bc8c4b8d80b3af1a4523ec33 -#: fd27250ab348426288cc60cddd75a0ac 91d24df457854500a94fa5782a4251e1 -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 ../../_include/interface-ip.txt:75 -#: ../../_include/interface-ip.txt:75 bc455cf9f3fc4658b1caefbb9c85f62a -#: 710ad7a284174bcfb5f0e69ab1cb3c9b 670ff72f01944ee199992917716d07b7 -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 ../../_include/interface-ip.txt:85 -#: ../../_include/interface-ip.txt:85 6770cb49fa4a44218d99965e973f3c3d -#: dd6364e2813e40a39d2047fbf23d4997 18c7c0afd62b41369c84cc0bb9fedb33 -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 ../../_include/interface-ip.txt:88 -#: ../../_include/interface-ip.txt:88 a77e2d47e8bb4bb1b3785702ce1f8916 -#: 37d8810aaa4744059b9aae965a48d378 9b73b144f7964a08b804cce32ba1a7d9 -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 ../../_include/interface-ip.txt:91 -#: ../../_include/interface-ip.txt:91 941a253809f3488a8d6658ecb66d7e0b -#: 0fc1b79aaa3a41d3bb15a647f23a5ca4 f3809e6cb58b4491ada78c2bacd604ac -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 ../../_include/interface-ip.txt:101 -#: ../../_include/interface-ip.txt:101 81fdab42abd14de1a4bdc43cd25fbe60 -#: d561c3c3233849d5a72c5f9eb0a20fce e30e2182322d4a678a40d1b6a3c64fb5 -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 ../../_include/interface-ip.txt:104 -#: ../../_include/interface-ip.txt:104 e82064fe37004627a564e24ce7409c46 -#: 9ecefefb01f94283aa8e9ac3c9593517 be852c86deb042f3a522a370105b90e1 -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 ../../_include/interface-ip.txt:106 -#: ../../_include/interface-ip.txt:106 84c0fb3da89b45e1924ea54c574c69b2 -#: cb5de94b0cd74b89b1ed8cfc61ee6bad e1d3f15d78784ff0897f6507877a67fb -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 ../../_include/interface-ip.txt:121 -#: ../../_include/interface-ip.txt:121 5b6a09daf24e41238d023f9beeff02c0 -#: cf212399b6a64e3a8380ed0e60f1a01b aba21155b15649dfae491c112f1a0467 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 ../../_include/interface-ip.txt:124 -#: ../../_include/interface-ip.txt:124 00f48c5b52284e19b92049d4146b31a0 -#: 7bdf494bff17425cab2f5c911b495058 7821487e2f8842a7845e03d0738976a7 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 ../../_include/interface-ip.txt:127 -#: ../../_include/interface-ip.txt:127 217aafcccbfb45ffb1ff30fffe500c73 -#: e22b3de7c68c464585a2673a553527a0 e3ed46079c4244a59241843930b9efdf -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 ../../_include/interface-ip.txt:137 -#: ../../_include/interface-ip.txt:137 2abef023c8e142ae95bb55a0c6b8b948 -#: 6fc0debe0ce747999e13eb4ee417251b 9591f808f081473592dbca9e3ff77c5b -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 ../../_include/interface-ip.txt:153 -#: ../../_include/interface-ip.txt:153 6ff40b7387a541d5a59f515eb5caac15 -#: f8e03cfbb7f14090883d287b231a6d70 df407ae13ffd4201b4d5890d078de2f9 -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 ../../_include/interface-ip.txt:156 -#: ../../_include/interface-ip.txt:156 6566d360548544c5ab057c171bdb20e5 -#: 1d630fe9739e4d17ae5175599bfdb66a 258268f1669c4be994d5e59991c9be50 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 ../../_include/interface-ip.txt:162 -#: ../../_include/interface-ip.txt:162 c674c0b2d5244322bab313dfe5fb39b9 -#: 8290afa5cecc47f6a42fd62fab173320 c03049d394e1426a97fec7f26899fc9b -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 ../../_include/interface-ip.txt:164 -#: ../../_include/interface-ip.txt:164 5cee7f4e9b2546db98dcd5bf0a54663b -#: 5437f92369d94259917b0af42889b3ec 598ff0eae2884a95882e056140645290 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 ../../_include/interface-ip.txt:166 -#: ../../_include/interface-ip.txt:166 ec50fa214cd640329bc527ee410e540b -#: 8bf18eb6a6b749eca0a9f863e41d0c7b be8dc87660f842ada4fe4ca144f96e5e -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 ../../_include/interface-ip.txt:168 -#: ../../_include/interface-ip.txt:168 328966fc62a5452596aff0a331a1ebd3 -#: cc85541ebb5041e185d485be958ecc5c d901d5be914b478eb3ea45a17a08965a -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 ../../_include/interface-ip.txt:170 -#: ../../_include/interface-ip.txt:170 927a65f9df014b5d925922d6c200d623 -#: 9c33475fffd846ab844779bd6914272a d4c8db8cf4254595aa413c8564c1a828 -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 ../../_include/interface-ip.txt:172 -#: ../../_include/interface-ip.txt:172 1a2f93ca63ca4f7f9883e3ba1098f2ef -#: f7090f549a85492d9bf61c6e7c267062 78b049bd7e42470d97184197ce5aa9b4 -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 ../../_include/interface-ip.txt:177 -#: ../../_include/interface-ip.txt:177 7b52fa61951745bbbf25a19f6bb74683 -#: f710269ad5104b39a21067c2ef97c481 f510d183ee1b41a6b7fea307d4fe62b5 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 ../../_include/interface-ip.txt:182 -#: ../../_include/interface-ip.txt:182 217cd6b7eb7f4ef7ae4f6681c7c3460a -#: 8cc810f77dc849a09d67e2df6be32db7 8172e8762bce44d7881ddfb4714999ae -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 ../../_include/interface-ip.txt:186 -#: ../../_include/interface-ip.txt:186 6e1783bd5c48487f884552181eb8a317 -#: e02339563cbc46c5aee58be4a0d55315 8e86c2929556418c845ac56492354514 -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 ../../_include/interface-ip.txt:190 -#: ../../_include/interface-ip.txt:190 0094eef015b441528293c9e41b26b51a -#: 09c39b62f418441283b4ba7c0810266a bc572e7078a943a4be43ca7bddab005b -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 ../../_include/interface-ipv6.txt:4 -#: ../../_include/interface-ipv6.txt:4 d309b5a2910448bea209d5854ba1c272 -#: 395e18ece1374ca5bd3a4968bc1d79c8 cddac1e8a7ed429eb97ff73583d209eb -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 ../../_include/interface-ipv6.txt:12 -#: ../../_include/interface-ipv6.txt:12 592b945cbe96435884372874c818303e -#: 19978eedc53d462f8bb0c87e931e411f aeecd27d5ef441599290fd4df584a3f3 -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 ../../_include/interface-ipv6.txt:25 -#: ../../_include/interface-ipv6.txt:25 b844a6b2e27b4e94bcb88063f23f9ab6 -#: ec5a93593b1544c3a6a799a69a54b574 a00b6e1d4dc248368447c0d43f5e2a48 -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 ../../_include/interface-ipv6.txt:37 -#: ../../_include/interface-ipv6.txt:37 3aef699886b84a58bb45882560ae9bdb -#: f2dd11c5a34f4569861e14fafc9a4ab7 c9a1bba41787447b82b1b3716593286c -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 ../../_include/interface-ipv6.txt:65 -#: ../../_include/interface-ipv6.txt:65 e3978fdd06894de4bb5703cefadb64c9 -#: d312c4aa9a6b44dcbc3da99d7eaef765 c8194a6be3d548ef9a26b9fff2b7a82d -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 ../../_include/interface-ipv6.txt:68 -#: ../../_include/interface-ipv6.txt:68 baf9a0fd1d504a02a32c8700071556de -#: d41ddc1ca6e747cda009a43ae0c58c03 c44ab8d3e83443479ed01dfd76fa51ff -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 ../../_include/interface-vrf.txt:4 -#: ../../_include/interface-vrf.txt:4 cd57f26baaaf4b73b3805b29327f25a6 -#: d8990f97a6444da1b62b863295f1611d 21174672b3a942bd811ce6bc9a3037e6 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 ../../_include/interface-vrf.txt:6 -#: ../../_include/interface-vrf.txt:6 532a4a0aa25f4060b7c341be595693c2 -#: ff3ec57d98614338b50cfb5a87b5cdda 6243602f9ef84ea794bd84392f2ed47d -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../_include/interface-common-with-dhcp.txt:9 -#: ../../_include/interface-vlan-8021q.txt:97 -#: ../../_include/interface-vlan-8021ad.txt:121 -#: 91ca0741721b4528b64ae5df4c278701 60df64f163a348fe88d06849c07b364a -#: 81c6803f96c24c4e99724a441c40d9c8 -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: ../../_include/interface-dhcp-options.txt:4 -#: 1627339130274da883cf987480edc286 13fc0aedf842496a9dd08336ce58744f -#: a5400995f7ec416487795e173187cf9a -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: ../../_include/interface-dhcp-options.txt:19 -#: d215302d7a194ef495f2fdd950987bde 415832670a8f4dac8729734231a42e7a -#: d8dd93f386fb44559298c6d6d71e1315 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: ../../_include/interface-dhcp-options.txt:31 -#: 3733501e2a094c67a6ade535f8ab5f27 ca7dd184f930474f844b3a14d5d205ef -#: 0f8744b5a5824b4a923782adeee74aa4 -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: ../../_include/interface-dhcp-options.txt:43 -#: 5c85e182b0a44c11988376f8140a8093 8c0ae4d451194befb3bf3d46fc6ed06e -#: f6edf6f2491941849234bcb11f948f6f -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: ../../_include/interface-dhcp-options.txt:55 -#: b3caa7250ee14099bc2fa3ac63ee00ad d993d5f589d74bd4b043bfe300b1b38a -#: 78e4f79854d44e6fb2a087d03f1eb620 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: ../../_include/interface-dhcp-options.txt:66 -#: dfa8ad1494ed40e88ad0f1549db2d6e2 a18cd236c72b46299904fb4c96502a98 -#: c0a047fa222e4bf59ee5684eff3c4afa -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: ../../_include/interface-dhcp-options.txt:69 -#: 23a5646f4954413689ab224d1fc6bd40 73e6feec544841cea3cdfd6ec990e56a -#: 8787cbf325d74d26b5ee0e25749bb7b5 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: ../../_include/interface-dhcpv6-options.txt:4 -#: 63adb4f98f0343549a332b0f9a8c5d5d 3de57dd922d04b9d858d2aafe773a20d -#: c81b18078aba4810a859e03def4d5eb1 -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: ../../_include/interface-dhcpv6-options.txt:17 -#: 1525b5c201694c1cab9bbdfbb0879264 4707b3070d44429fbb2bdf4aaacd1d50 -#: 95868e8da7424e38b76c713b634f455d -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: ../../_include/interface-dhcpv6-options.txt:29 -#: 33f8bd07922d42db88c27b303d51a37d 130812449ba042c086c1bf9934afaf58 -#: c7c1783b806740ff8453f90f06b89535 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: ../../_include/interface-dhcpv6-options.txt:39 -#: 31d5fbc7011b4a6284a8423d329c2b55 6fd9a568f610448aa56a211af2054205 -#: a1bf0349a98f4191b5d8618631916f3a -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 673402fc91ae4d77a6e7903fc9e6a325 4e7375ec296d487083ffa3817c194d53 -#: 858750ab6b334854ba3869d1f9aa217f -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 81d14b60fdf94d43a3a11eacd72dee13 94fe24e1ba0343d6ba6aa2c7d7c962f0 -#: 7627376aaa93472eb6d29f568153b4e2 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: f02c99da86f641da85c8457751b142c7 69b1fe9ad22741359115b63299c8954f -#: a1517a66b67c4c24858618938825f20a -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: eff71a21a83d48c5bdf61caa9e57f008 bd537848961a44c18d3f489ff89fd19f -#: 8e274d206f964bb5aa41460e38f59bae -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: 367ed32258fa485ab24afdb4e5a84d3c be5346a59ada4f5982e3c83645a0f56b -#: 50021d976b7d4ce9ac2632e563a6bcd5 -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: b2b758c76c44428eae88faf7cb1ff454 a20d46d11c884745968755cff18645de -#: 161229481674458d8930155f7f58dffb -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: b2b40ab0d06b436c99dff071746bdcd2 a4ceb15b61da419c96885a7175316ce4 -#: 895d27b083f847f8bc08f045d9da8d49 -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 3de30243ca78487ab9900e6e15b8230b 0714e6fb605d4cc3837c515f6b1b8654 -#: ab59acd12cf4433a9243e47e13839aa8 -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: 21a6a82d8f884a1badeff35f86b436d2 d2a96abf30c34339b636e7dd2012ebc4 -#: 36b33093cc63486181998621cad4c049 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: 1e7bd072a67b4c23b6dc6da365a9efdd 58a84b9a1622478f894d862d1052d615 -#: 42139d0175d94681a552a4c7ba78338d -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:40 -#: 2904640a58f04ae99381ec8c4d111023 -msgid "Wireless options" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:44 -#: de5e875d4b7e47de9ffb2f1d1eeaed04 -msgid "" -"Channel number (IEEE 802.11), for 2.4Ghz (802.11 b/g/n) channels range from " -"1-14. On 5Ghz (802.11 a/h/j/n/ac) channels available are 0, 34 to 173" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:49 -#: 960686dd765c4e52819d0b3d84ba4da2 -msgid "" -"Country code (ISO/IEC 3166-1). Used to set regulatory domain. Set as needed " -"to indicate country in which device is operating. This can limit available " -"channels and transmit power." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:53 -#: 63e994c26dd54916bac711230be1166d -msgid "This option is mandatory in Access-Point mode." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:57 -#: 9a49f2d5bf244133950fb2c4e6ba9df7 -msgid "" -"Send empty SSID in beacons and ignore probe request frames that do not " -"specify full SSID, i.e., require stations to know SSID." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:62 -#: 152bf09c3d7444eba0bbb9604534042c -msgid "" -"Disassociate stations based on excessive transmission failures or other " -"indications of connection loss." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:65 -#: f9e8d6bfca5e4076a454b4ae5f8397b5 -msgid "" -"This depends on the driver capabilities and may not be available with all " -"drivers." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:70 -#: 03f72daca5f0438d86c02bc5b1160174 -msgid "" -"Client isolation can be used to prevent low-level bridging of frames between" -" associated stations in the BSS." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:73 -#: 837a9ae1063040c7b89e55882472cad8 -msgid "By default, this bridging is allowed." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:77 -#: ace4987f3881477fa56ec97bfc4e9dc7 -msgid "" -"Maximum number of stations allowed in station table. New stations will be " -"rejected after the station table is full. IEEE 802.11 has a limit of 2007 " -"different association IDs, so this number should not be larger than that." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:81 -#: 57d42b0dc61e4c13990f8c68ab7d863d -msgid "This defaults to 2007." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:85 -#: 667ed629780c4b5cb7942f90cef97b42 -msgid "Management Frame Protection (MFP) according to IEEE 802.11w" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:89 -#: 661a7810afb04a7a9dfab2ddf6a3d887 -msgid "Operation mode of wireless radio." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:91 -#: b36d05fb10be4fc8a12f5c0d8b4d89eb -msgid "``a`` - 802.11a - 54 Mbits/sec" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:92 -#: 6b2565556eef43cbab6754dc24f1734e -msgid "``b`` - 802.11b - 11 Mbits/sec" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:93 -#: 7d56f145c87d414f80db80b425c47bce -msgid "``g`` - 802.11g - 54 Mbits/sec (default)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:94 -#: 4c978cd4a46d4850b9ee0c7e509fac03 -msgid "``n`` - 802.11n - 600 Mbits/sec" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:95 -#: 7149eab9edba4af6b53fe26f7ec9a6ee -msgid "``ac`` - 802.11ac - 1300 Mbits/sec" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:99 -#: 907aaf6078414aec9a6854e10a8aef9f -msgid "Wireless hardware device used as underlay radio." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:101 -#: e8dae576f9814292a65a02da7c2f66f4 -msgid "This defaults to phy0." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:105 -#: 2d87980d2fde423f910d24dcb47aaa24 -msgid "Add Power Constraint element to Beacon and Probe Response frames." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:107 -#: 69c32eacedb34cf998a6a447b9203ccb -msgid "" -"This option adds Power Constraint element when applicable and Country " -"element is added. Power Constraint element is required by Transmit Power " -"Control." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:110 -#: 1d7f22b53bcb4844bb0dc2a7abc823eb -msgid "Valid values are 0..255." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:114 -#: dfd604eb800f4ed99e12e1d3a98231b7 -msgid "SSID to be used in IEEE 802.11 management frames" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:119 -#: ab56eb74aad744579835a61c403144ab -msgid "Wireless device type for this interface" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:121 -#: 09ffc21424594b6282cac73a2abc4114 -msgid "``access-point`` - Access-point forwards packets between other nodes" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:122 -#: 47bfa075ff2c47efb446c797347e63e5 -msgid "``station`` - Connects to another access point" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:123 -#: 9312201d3b4542c189420b20f43cb76f -msgid "``monitor`` - Passively monitor all packets on the frequency/channel" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:126 -#: 8210f6890bcc4b5fb7aa99abadb7efcf -msgid "PPDU" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:133 -#: 89358b7181664d01b964cc6f4867988f -msgid "HT (High Throughput) capabilities (802.11n)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:137 -#: 466294bae5254d77988b5eafa52bce02 -msgid "" -"Device is incapable of 40 MHz, do not advertise. This sets " -"``[40-INTOLERANT]``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:141 -#: 9a0052639c2943df8c01837b4ec382ca -msgid "WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:146 -#: e3e427d335814be79ec0e2b4e80f95a6 -msgid "Supported channel width set." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:148 -#: 3289b8966b404c1f8a4440ca1260b76b -msgid "" -"``ht40-`` - Both 20 MHz and 40 MHz with secondary channel below the primary " -"channel" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:150 -#: 45a290c6e2be450e963ba2dfc6ac89fe -msgid "" -"``ht40+`` - Both 20 MHz and 40 MHz with secondary channel above the primary " -"channel" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:153 -#: 06bb81a935314c1fa3dc61524053dc54 -msgid "" -"There are limits on which channels can be used with HT40- and HT40+. " -"Following table shows the channels that may be available for HT40- and HT40+" -" use per IEEE 802.11n Annex J:" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:157 -#: 354ca994dd54403d9d84f07e7d5309fe -msgid "" -"Depending on the location, not all of these channels may be available for " -"use!" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:166 -#: f352bb1b31d64d3cb52de330a9d64f93 -msgid "" -"40 MHz channels may switch their primary and secondary channels if needed or" -" creation of 40 MHz channel maybe rejected based on overlapping BSSes. These" -" changes are done automatically when hostapd is setting up the 40 MHz " -"channel." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:174 -#: 0b9c58659a3b438bb32bf2d93355b557 -msgid "Enable HT-delayed Block Ack ``[DELAYED-BA]``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:178 -#: 8d85e5babcba42778ee78dc0ee85f4cf -msgid "DSSS/CCK Mode in 40 MHz, this sets ``[DSSS_CCK-40]``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:182 -#: 1040a873a81044289a2317f7015220a9 -msgid "This enables the greenfield option which sets the ``[GF]`` option" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:186 -#: 9fb4373ea1ce4560b802c459e561a236 -msgid "Enable LDPC coding capability" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:190 -#: 462d22845b394f2bbbdd1a3bdacaaf74 -msgid "Enable L-SIG TXOP protection capability" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:195 -#: d2e50cefa0b949d8a45410468cf58d86 -msgid "Maximum A-MSDU length 3839 (default) or 7935 octets" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:200 -#: 64e2338df6164587911b0e2c3105761a -msgid "Short GI capabilities for 20 and 40 MHz" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:205 -#: 6b739e8822a9425b905e44896467b24d -msgid "Spatial Multiplexing Power Save (SMPS) settings" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:209 -#: ../../configuration/interfaces/wireless.rst:282 -#: cea0d0d68e0842aca071146dcb9735bc d003fa683348471c8eacf3e7fd05bb36 -msgid "Enable receiving PPDU using STBC (Space Time Block Coding)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:213 -#: ../../configuration/interfaces/wireless.rst:286 -#: 93651e52d23c449e915c63463f491d8c afe9e0e6d88f4d0a845a24f5fa6ade2a -msgid "Enable sending PPDU using STBC (Space Time Block Coding)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:216 -#: 2269485b0b764ac8bbf22c8f73839ae3 -msgid "VHT (Very High Throughput) capabilities (802.11ac)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:220 -#: 58d37f65db0540ffaa28c06164466337 -msgid "Number of antennas on this card" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:225 -#: 02e3d636354545f39c4d241a95ebcc82 -msgid "" -"Set if antenna pattern does not change during the lifetime of an association" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:231 -#: b14e3d3926b946798b1ae2396096d424 -msgid "Beamforming capabilities:" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:233 -#: fe37daa2736b4608b5650924ba2b4c2d -msgid "" -"``single-user-beamformer`` - Support for operation as single user beamformer" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:234 -#: fa733a01622b45c1b64d7ca4eaae0362 -msgid "" -"``single-user-beamformee`` - Support for operation as single user beamformee" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:235 -#: b6aff6df70694025ae69a03fa63b1bd0 -msgid "" -"``multi-user-beamformer`` - Support for operation as single user beamformer" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:236 -#: 4087ece5307e489fa131673d3cf0f6ac -msgid "" -"``multi-user-beamformee`` - Support for operation as single user beamformer" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:241 -#: e2838753d9bd4ff4a9db0c188d3fbab8 -msgid "" -"VHT operating channel center frequency - center freq 1 (for use with 80, " -"80+80 and 160 modes)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:244 -#: e4fb37db87f146d5bfe1c66cb37efce0 -msgid "" -"VHT operating channel center frequency - center freq 2 (for use with the " -"80+80 mode)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:247 -#: a3b6f953dcdb47ba95b42b58d193fc7f -msgid "" -"<number> must be from 34 - 173. For 80 MHz channels it should be channel + " -"6." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:252 -#: 0d49a9fe1720490ba7b78119c8ef10ef -msgid "``0`` - 20 or 40 MHz channel width (default)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:253 -#: a8dc10e17daf4b6c8009c376ce962894 -msgid "``1`` - 80 MHz channel width" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:254 -#: 29e018cb7a0f4a9982adc9ea72c365fd -msgid "``2`` - 160 MHz channel width" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:255 -#: 51e6b6a6a9054ad590d22f9f7bf3fd44 -msgid "``3`` - 80+80 MHz channel width" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:259 -#: 4e73700d3f44492498ab22508387ba20 -msgid "Enable LDPC (Low Density Parity Check) coding capability" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:263 -#: 5bffca9bd59c46229ed0779e4bc84e8a -msgid "VHT link adaptation capabilities" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:268 -#: 068c7bb68fe341b8ab28c4e8aa259c72 -msgid "" -"Increase Maximum MPDU length to 7991 or 11454 octets (default 3895 octets)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:273 -#: d02e32a8c53d4a56a220eedfb88d2135 -msgid "" -"Set the maximum length of A-MPDU pre-EOF padding that the station can " -"receive" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:278 -#: 9eb70abf9e624147a7743f13d2e69b1a -msgid "Short GI capabilities" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:290 -#: d019f46d5158472cbc0234dc281c55b0 -msgid "Enable VHT TXOP Power Save Mode" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:294 -#: e65e961671d1455a901dd4e337f54cb3 -msgid "Station supports receiving VHT variant HT Control field" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:297 -#: f246cf2399034369911b9946d054c95f -msgid "Wireless options (Station/Client)" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:299 -#: 23d2db2a50d540a0a602b4722ef7929d -msgid "" -"The example creates a wireless station (commonly referred to as Wi-Fi " -"client) that accesses the network through the WAP defined in the above " -"example. The default physical device (``phy0``) is used." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:310 -#: ../../configuration/interfaces/wireless.rst:362 -#: ../../configuration/interfaces/wireless.rst:563 -#: df416e8caad647179af26a155db80bef b65ce78cbe014e09985322285d4de345 -#: e440bff9d4a94f33b58d5e8965410c13 -msgid "Resulting in" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:328 -#: d008384bf3564837a83c09db702c4901 -msgid "Security" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:330 -#: 6170e700fa8247ff8762b129016c8e5a -msgid "" -":abbr:`WPA (Wi-Fi Protected Access)` and WPA2 Enterprise in combination with" -" 802.1x based authentication can be used to authenticate users or computers " -"in a domain." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:334 -#: b9d23e476a474af892378f42e99e3517 -msgid "" -"The wireless client (supplicant) authenticates against the RADIUS server " -"(authentication server) using an :abbr:`EAP (Extensible Authentication " -"Protocol)` method configured on the RADIUS server. The WAP (also referred " -"to as authenticator) role is to send all authentication messages between the" -" supplicant and the configured authentication server, thus the RADIUS server" -" is responsible for authenticating the users." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:341 -#: ../../configuration/interfaces/wireless.rst:544 -#: 75aedc1e1b8f4840904baa79ae1d9d81 4cd3f5b3094e4439b7cedcd308fbefe5 -msgid "The WAP in this example has the following characteristics:" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:343 -#: ../../configuration/interfaces/wireless.rst:546 -#: 2da58f20e1914b05991a74df45a766d7 3b2e35bfd8cb4f0c90d767c4e7fb68f4 -msgid "IP address ``192.168.2.1/24``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:344 -#: 32519c519d204788a6ebbb19cef77dac -msgid "Network ID (SSID) ``Enterprise-TEST``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:345 -#: ../../configuration/interfaces/wireless.rst:548 -#: efdd8a4beaa04f4cbb80831e557255f5 c69599b2057346ab9c9ee6aded5b774f -msgid "WPA passphrase ``12345678``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:346 -#: ../../configuration/interfaces/wireless.rst:549 -#: 028ed66a0d3f4dceb558199df58b9c99 b8fffe0034fa4a42955bf70866131b8a -msgid "Use 802.11n protocol" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:347 -#: ../../configuration/interfaces/wireless.rst:550 -#: d65e0c8ca7a7499b970edbcee298519a 55fe54836bbe4c578a09940e5fcb48ed -msgid "Wireless channel ``1``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:348 -#: 38b28f4aba4c40dea06c7929d6d87f4a -msgid "RADIUS server at ``192.168.3.10`` with shared-secret ``VyOSPassword``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:395 -#: 87e02c644f9d433b8ee7e590592d3126 -msgid "VLAN" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:398 -#: 942913e6372444a8ade0ea202469c78a -msgid "Regular VLANs (802.1q)" -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:1 7cb91cd5936c4e4f83d732dfeca57dd9 -msgid "" -"IEEE 802.1q_, often referred to as Dot1q, is the networking standard that " -"supports virtual LANs (VLANs) on an IEEE 802.3 Ethernet network. The " -"standard defines a system of VLAN tagging for Ethernet frames and the " -"accompanying procedures to be used by bridges and switches in handling such " -"frames. The standard also contains provisions for a quality-of-service " -"prioritization scheme commonly known as IEEE 802.1p and defines the Generic " -"Attribute Registration Protocol." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:9 96f9519b4c4643bf841863bc3a2a203a -msgid "" -"Portions of the network which are VLAN-aware (i.e., IEEE 802.1q_ conformant)" -" can include VLAN tags. When a frame enters the VLAN-aware portion of the " -"network, a tag is added to represent the VLAN membership. Each frame must be" -" distinguishable as being within exactly one VLAN. A frame in the VLAN-aware" -" portion of the network that does not contain a VLAN tag is assumed to be " -"flowing on the native VLAN." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:16 2096a79443f6462886f2a865ef9f7bf7 -msgid "" -"The standard was developed by IEEE 802.1, a working group of the IEEE 802 " -"standards committee, and continues to be actively revised. One of the " -"notable revisions is 802.1Q-2014 which incorporated IEEE 802.1aq (Shortest " -"Path Bridging) and much of the IEEE 802.1d standard." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:21 dfdc3e6b27fc4e5a8b2336298eba2357 -msgid "" -"802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. " -"The term used for this is ``vif``." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:26 6e92e8826b2d44b59f3ae1f969bb0c42 -msgid "" -"Create a new VLAN interface on interface `<interface>` using the VLAN number" -" provided via `<vlan-id>`." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:29 c5e5fe80d5284efdbde8988e5b6aacd7 -msgid "" -"You can create multiple VLAN interfaces on a physical interface. The VLAN ID" -" range is from 0 to 4094." -msgstr "" - -#: ../../_include/interface-vlan-8021q.txt:32 d4a6659a752541869e7f48113c169252 -msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:405 -#: 8601f7a056e4488997399bc9b2091010 -msgid "QinQ (802.1ad)" -msgstr "" - -#: ../../_include/need_improvement.txt:11 7aa5fbefd01d4aaf9aa1195215e71e5b -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 b8eb64b0da89481cbd9e222f66122854 -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:3 98df441ee34a41dda44a65b35758bc65 -msgid "" -"IEEE 802.1ad_ was an Ethernet networking standard informally known as QinQ " -"as an amendment to IEEE standard 802.1q VLAN interfaces as described above. " -"802.1ad was incorporated into the base 802.1q_ standard in 2011. The " -"technique is also known as provider bridging, Stacked VLANs, or simply QinQ " -"or Q-in-Q. \"Q-in-Q\" can for supported devices apply to C-tag stacking on " -"C-tag (Ethernet Type = 0x8100)." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:10 -#: 38562b04cb7149558881b964aeb7ce79 -msgid "" -"The original 802.1q_ specification allows a single Virtual Local Area " -"Network (VLAN) header to be inserted into an Ethernet frame. QinQ allows " -"multiple VLAN tags to be inserted into a single frame, an essential " -"capability for implementing Metro Ethernet network topologies. Just as QinQ " -"extends 802.1Q, QinQ itself is extended by other Metro Ethernet protocols." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:16 -#: b4a5fa504e8143e594cfcd703d252957 -msgid "" -"In a multiple VLAN header context, out of convenience the term \"VLAN tag\" " -"or just \"tag\" for short is often used in place of \"802.1q_ VLAN header\"." -" QinQ allows multiple VLAN tags in an Ethernet frame; together these tags " -"constitute a tag stack. When used in the context of an Ethernet frame, a " -"QinQ frame is a frame that has 2 VLAN 802.1q_ headers (double-tagged)." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:22 -#: abab830a60564142b407f31daa50178b -msgid "" -"In VyOS the terms ``vif-s`` and ``vif-c`` stand for the ethertype tags that " -"are used." -msgstr "" - -#: ../../_include/interface-vlan-8021ad.txt:25 -#: 550148b534a64b46af854f8165443b3c -msgid "" -"The inner tag is the tag which is closest to the payload portion of the " -"frame. It is officially called C-TAG (customer tag, with ethertype 0x8100). " -"The outer tag is the one closer/closest to the Ethernet header, its name is " -"S-TAG (service tag with Ethernet Type = 0x88a8)." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:413 -#: 78348cbc9de04e8490c820e62d151dcf -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:417 -#: 36d7853ec36e4a39a6307d0bea41d0d9 -msgid "" -"Use this command to view operational status and wireless-specific " -"information about all wireless interfaces." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:428 -#: 3ad2cd0b819e4098961810680a63c934 -msgid "" -"Use this command to view operational status and details wireless-specific " -"information about all wireless interfaces." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:460 -#: c28dfd31b6a74ceb84a7f9446cc98e78 -msgid "" -"This command shows both status and statistics on the specified wireless " -"interface. The wireless interface identifier can range from wlan0 to " -"wlan999." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:481 -#: 59921c40da2d4d74b8427f8be06f6cf2 -msgid "" -"This command gives a brief status overview of a specified wireless " -"interface. The wireless interface identifier can range from wlan0 to " -"wlan999." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:495 -#: aef2b04c0a5f408da3170a78e9aa7e44 -msgid "" -"Use this command to view wireless interface queue information. The wireless " -"interface identifier can range from wlan0 to wlan999." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:508 -#: c769a3d471504c0e9f682d870bfa5e6a -msgid "" -"This command is used to retrieve information about WAP within the range of " -"your wireless interface. This command is useful on wireless interfaces " -"configured in station mode." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:512 -#: 049e2d086d45484aacd9ba45df25aeef -msgid "" -"Scanning is not supported on all wireless drivers and wireless hardware. " -"Refer to your driver and wireless hardware documentation for further " -"details." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:538 -#: d4809008e8484d2c939520859cb20ca0 -msgid "Examples" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:540 -#: 0af1a2a973254ca08811481b7a3bf65a -msgid "" -"The following example creates a WAP. When configuring multiple WAP " -"interfaces, you must specify unique IP addresses, channels, Network IDs " -"commonly referred to as :abbr:`SSID (Service Set Identifier)`, and MAC " -"addresses." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:547 -#: 41f06a5716394f639be9a37499133d69 -msgid "Network ID (SSID) ``TEST``" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:589 -#: 6070b90cc8e046cf886cc42989c26848 -msgid "" -"To get it to work as an access point with this configuration you will need " -"to set up a DHCP server to work with that network. You can - of course - " -"also bridge the Wireless interface with any configured bridge (:ref:`bridge-" -"interface`) on the system." -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:597 -#: a6d311e36c954c849ff4777c9d96a3b8 -msgid "Intel AX200" -msgstr "" - -#: ../../configuration/interfaces/wireless.rst:599 -#: 27f5dca77aa2405b851030ceb0070baa -msgid "" -"The Intel AX200 card does not work out of the box in AP mode, see " -"https://unix.stackexchange.com/questions/598275/intel-ax200-ap-mode. You can" -" still put this card into AP mode using the following configuration:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wwan.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wwan.po deleted file mode 100644 index 71c24111..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/interfaces/wwan.po +++ /dev/null @@ -1,710 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/interfaces/wwan.rst:7 231ad24e31bf4bae9e51fb542ecb65da -msgid "WWAN - Wireless Wide-Area-Network" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:9 992449ad4b314c509e739000f706ad8b -msgid "" -"The Wireless Wide-Area-Network interface provides access (through a wireless" -" modem/wwan) to wireless networks provided by various cellular providers." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:12 6943d09f5e43468691c34c43ef0dd9e8 -msgid "VyOS uses the `interfaces wwan` subsystem for configuration." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:16 9e60f4603c07426d9bb2dad3ac8a9726 -msgid "Configuration" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:19 bb98d42be4c54cb79102d0d9284d154d -msgid "Common interface configuration" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:5 -#: 43eed503a0ab44ea87274b41f64c8040 -msgid "" -"Configure interface `<interface>` with one or more interface addresses." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:7 -#: 00a1d95d696b428ca4bfd0a914fee715 -msgid "" -"**address** can be specified multiple times as IPv4 and/or IPv6 address, " -"e.g. 192.0.2.1/24 and/or 2001:db8::1/64" -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:9 -#: a911e739d0804fee998e1212318a0f47 -msgid "" -"**dhcp** interface address is received by DHCP from a DHCP server on this " -"segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:11 -#: c142efec979e446c9ceb226eb698870f -msgid "" -"**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on " -"this segment." -msgstr "" - -#: ../../_include/interface-address-with-dhcp.txt:14 -#: ../../_include/interface-description.txt:7 -#: ../../_include/interface-disable.txt:7 -#: ../../_include/interface-disable-link-detect.txt:9 -#: ../../_include/interface-mtu.txt:7 ../../_include/interface-ip.txt:27 -#: ../../_include/interface-ip.txt:50 ../../_include/interface-ip.txt:144 -#: ../../_include/interface-ipv6.txt:15 ../../_include/interface-ipv6.txt:28 -#: ../../_include/interface-ipv6.txt:39 ../../_include/interface-ipv6.txt:51 -#: ../../_include/interface-vrf.txt:9 -#: ../../_include/interface-dhcp-options.txt:10 -#: ../../_include/interface-dhcp-options.txt:22 -#: ../../_include/interface-dhcp-options.txt:34 -#: ../../_include/interface-dhcp-options.txt:46 -#: ../../_include/interface-dhcp-options.txt:57 -#: ../../_include/interface-dhcp-options.txt:72 -#: c49654900b14484f964e38d59959c135 d717d1274735424196e53b89855f1fc5 -#: e20c48a9b9d6432c9f04fcf87a2b0ac3 cc255888362948d4899243491dcf537a -#: a17c14c8dced46e48d5609c2771a92e6 5e7fbda40059408c9e70aa1ebca1db2f -#: a6cdab28989b42e592bdafe100defdcd 909400dc3a86408293a2240a0e58b6ee -#: 63308f063926423babd611462d72bae1 776816f619c440b3a73644372e5f6af6 -#: f3c9e2da690a42058d14c869c94e6607 d6e2f7152d66469c97f2feeeeed0fcde -#: 6a0418c49f5045b0b4a44fa4fcb1ddbd c0081bb19f834487814fc0a5b3dea77b -#: e6cdb19e2a1e496481a40ab031363478 42faec2a295b4eefa62a0ea824e24440 -#: b1dcebe389ee48cdbb01212136513773 070010405f644fd1af21f74de8e2f439 -#: 9e722ffd4f3348768e4136d4e584b095 -msgid "Example:" -msgstr "" - -#: ../../_include/interface-description.txt:4 50f9869b06c64e0c9f07b632b7f32e21 -msgid "" -"Set a human readable, descriptive alias for this connection. Alias is used " -"by e.g. the :opcmd:`show interfaces` command or SNMP based monitoring tools." -msgstr "" - -#: ../../_include/interface-disable.txt:4 af43383d8ff84f7aa41dfc27c324adc8 -msgid "" -"Disable given `<interface>`. It will be placed in administratively down " -"(``A/D``) state." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:4 -#: a47e96df9e734941a13794d3fa328172 -msgid "" -"Use this command to direct an interface to not detect any physical state " -"changes on a link, for example, when the cable is unplugged." -msgstr "" - -#: ../../_include/interface-disable-link-detect.txt:7 -#: 75c2510fb55143f49f6d860f24fd4866 -msgid "Default is to detects physical link state changes." -msgstr "" - -#: ../../_include/interface-mtu.txt:4 10b652a4979545eca88554674139bc70 -msgid "" -"Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It" -" is the size (in bytes) of the largest ethernet frame sent on this link." -msgstr "" - -#: ../../_include/interface-ip.txt:4 ../../_include/interface-ipv6.txt:60 -#: 7e9f0242c89640dab2a3b827cf9849b7 b499b697a64846faa35f7707866bd890 -msgid "" -"As Internet wide PMTU discovery rarely works, we sometimes need to clamp our" -" TCP MSS value to a specific value. This is a field in the TCP options part " -"of a SYN packet. By setting the MSS value, you are telling the remote side " -"unequivocally 'do not try to send me packets bigger than this value'." -msgstr "" - -#: ../../_include/interface-ip.txt:9 81e306041aca440f9706787da9df16a5 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss <value>``" -msgstr "" - -#: ../../_include/interface-ip.txt:12 57a7f6b80536429a91a1c296d2b1dc2d -msgid "" -"MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes " -"on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-ip.txt:15 ../../_include/interface-ipv6.txt:71 -#: ddfbfdfbf5ec46ef9bcf241ef73c6118 9b8fda98f7934303a3a5c822aa4dabb6 -msgid "" -"Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to " -"automatically set the proper value." -msgstr "" - -#: ../../_include/interface-ip.txt:21 f0040f44ce3b42f58b3d4a838e2ef93a -msgid "" -"Once a neighbor has been found, the entry is considered to be valid for at " -"least for this specific time. An entry's validity will be extended if it " -"receives positive feedback from higher level protocols." -msgstr "" - -#: ../../_include/interface-ip.txt:25 cc6597faf4b249d4bcd18366956037f4 -msgid "This defaults to 30 seconds." -msgstr "" - -#: ../../_include/interface-ip.txt:36 ea95a6a6be094784bf96ce87b4008272 -msgid "" -"If set the kernel can respond to arp requests with addresses from other " -"interfaces. This may seem wrong but it usually makes sense, because it " -"increases the chance of successful communication. IP addresses are owned by " -"the complete host on Linux, not by particular interfaces. Only for more " -"complex setups like load-balancing, does this behaviour cause problems." -msgstr "" - -#: ../../_include/interface-ip.txt:42 e1b2f19234094227a3462475cc112e1b -msgid "" -"If not set (default) allows you to have multiple network interfaces on the " -"same subnet, and have the ARPs for each interface be answered based on " -"whether or not the kernel would route a packet from the ARP'd IP out that " -"interface (therefore you must use source based routing for this to work)." -msgstr "" - -#: ../../_include/interface-ip.txt:47 5fb3535e049f412e8fca5cb078ae3c47 -msgid "" -"In other words it allows control of which cards (usually 1) will respond to " -"an arp request." -msgstr "" - -#: ../../_include/interface-ip.txt:59 ../../_include/interface-ipv6.txt:48 -#: 2d0bcb8299ba4891997f7b91f5d3ba12 ed8895f1d4f645d0886979c22a58238d -msgid "" -"Configure interface-specific Host/Router behaviour. If set, the interface " -"will switch to host mode and IPv6 forwarding will be disabled on this " -"interface." -msgstr "" - -#: ../../_include/interface-ip.txt:69 9ef7d844460448df8e53f2889d9b20d2 -msgid "" -"Define different modes for IP directed broadcast forwarding as described in " -":rfc:`1812` and :rfc:`2644`." -msgstr "" - -#: ../../_include/interface-ip.txt:72 5f98f57288274f2fa1199334e395a89d -msgid "" -"If configured, incoming IP directed broadcast packets on this interface will" -" be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:75 1c93a73e4b2f4612b8d2050d6baa6d2a -msgid "" -"If this option is unset (default), incoming IP directed broadcast packets " -"will not be forwarded." -msgstr "" - -#: ../../_include/interface-ip.txt:85 420aaa4a8caa449cb241cfaa8c235c03 -msgid "" -"Define behavior for gratuitous ARP frames who's IP is not already present in" -" the ARP table. If configured create new entries in the ARP table." -msgstr "" - -#: ../../_include/interface-ip.txt:88 4c4f518296444c72a56908585d21cfcd -msgid "" -"Both replies and requests type gratuitous arp will trigger the ARP table to " -"be updated, if this setting is on." -msgstr "" - -#: ../../_include/interface-ip.txt:91 81b43184006e4597abb49adbcc2b1677 -msgid "" -"If the ARP table already contains the IP address of the gratuitous arp " -"frame, the arp table will be updated regardless if this setting is on or " -"off." -msgstr "" - -#: ../../_include/interface-ip.txt:101 0b9da423e2c34802a9e3cb1f097a5843 -msgid "" -"Define different restriction levels for announcing the local source IP " -"address from IP packets in ARP requests sent on interface." -msgstr "" - -#: ../../_include/interface-ip.txt:104 3fef637e145a4e36b6c31519a04c1f1e -msgid "Use any local address, configured on any interface if this is not set." -msgstr "" - -#: ../../_include/interface-ip.txt:106 b9cbb256e4de421f88d5d53440db17f7 -msgid "" -"If configured, try to avoid local addresses that are not in the target's " -"subnet for this interface. This mode is useful when target hosts reachable " -"via this interface require the source IP address in ARP requests to be part " -"of their logical network configured on the receiving interface. When we " -"generate the request we will check all our subnets that include the target " -"IP and will preserve the source address if it is from such subnet. If there " -"is no such subnet we select source address according to the rules for level " -"2." -msgstr "" - -#: ../../_include/interface-ip.txt:121 4c001043510b4657b37f667e71f6e0f6 -msgid "" -"Define different modes for sending replies in response to received ARP " -"requests that resolve local target IP addresses:" -msgstr "" - -#: ../../_include/interface-ip.txt:124 8cedabddff8c46b099d7498205adac00 -msgid "" -"If configured, reply only if the target IP address is local address " -"configured on the incoming interface." -msgstr "" - -#: ../../_include/interface-ip.txt:127 56aab1ab16034b2ea055b95e51ec904d -msgid "" -"If this option is unset (default), reply for any local target IP address, " -"configured on any interface." -msgstr "" - -#: ../../_include/interface-ip.txt:137 a0113b8c4af14f6a9628b3eaf5e46612 -msgid "" -"Use this command to enable proxy Address Resolution Protocol (ARP) on this " -"interface. Proxy ARP allows an Ethernet interface to respond with its own " -":abbr:`MAC (Media Access Control)` address to ARP requests for destination " -"IP addresses on subnets attached to other interfaces on the system. " -"Subsequent packets sent to those destination IP addresses are forwarded " -"appropriately by the system." -msgstr "" - -#: ../../_include/interface-ip.txt:153 fcc8686cf0c34219a91c115c589514fb -msgid "" -"Private VLAN proxy arp. Basically allow proxy arp replies back to the same " -"interface (from which the ARP request/solicitation was received)." -msgstr "" - -#: ../../_include/interface-ip.txt:156 10c82886a9fd479ab18c609da348b773 -msgid "" -"This is done to support (ethernet) switch features, like :rfc:`3069`, where " -"the individual ports are NOT allowed to communicate with each other, but " -"they are allowed to talk to the upstream router. As described in " -":rfc:`3069`, it is possible to allow these hosts to communicate through the " -"upstream router by proxy_arp'ing." -msgstr "" - -#: ../../_include/interface-ip.txt:162 f94dc7a593104a938d1e3b39a3d6d0f9 -msgid "Does not need to be used together with proxy_arp." -msgstr "" - -#: ../../_include/interface-ip.txt:164 3c0554f13f61454db9de8d4bf6ce86e8 -msgid "This technology is known by different names:" -msgstr "" - -#: ../../_include/interface-ip.txt:166 0709e9a3c9bc40baad7310fad184e0e3 -msgid "In :rfc:`3069` it is called VLAN Aggregation" -msgstr "" - -#: ../../_include/interface-ip.txt:168 c54d5675f813483181273a1a8efe2d93 -msgid "Cisco and Allied Telesyn call it Private VLAN" -msgstr "" - -#: ../../_include/interface-ip.txt:170 a83194ba2b354d0d9f5848c1e6603041 -msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" -msgstr "" - -#: ../../_include/interface-ip.txt:172 f233bb60fc044a34956b95ab0ea07e02 -msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" -msgstr "" - -#: ../../_include/interface-ip.txt:177 14de387da9d94cb5a2ed52c1ffc30950 -msgid "" -"Enable policy for source validation by reversed path, as specified in " -":rfc:`3704`. Current recommended practice in :rfc:`3704` is to enable strict" -" mode to prevent IP spoofing from DDos attacks. If using asymmetric routing " -"or other complicated routing, then loose mode is recommended." -msgstr "" - -#: ../../_include/interface-ip.txt:182 cf36da1daf8a45a5a1181a7c2ad2cf86 -msgid "" -"strict: Each incoming packet is tested against the FIB and if the interface " -"is not the best reverse path the packet check will fail. By default failed " -"packets are discarded." -msgstr "" - -#: ../../_include/interface-ip.txt:186 26ada7c06b9649ae9fdd8d51852362db -msgid "" -"loose: Each incoming packet's source address is also tested against the FIB " -"and if the source address is not reachable via any interface the packet " -"check will fail." -msgstr "" - -#: ../../_include/interface-ip.txt:190 7eac584eecf6438599b9980fb835acf7 -msgid "disable: No source validation" -msgstr "" - -#: ../../_include/interface-ipv6.txt:4 e8f2ce9363a345ccb0ea12a35014d715 -msgid "" -":abbr:`SLAAC (Stateless Address Autoconfiguration)` :rfc:`4862`. IPv6 hosts " -"can configure themselves automatically when connected to an IPv6 network " -"using the Neighbor Discovery Protocol via :abbr:`ICMPv6 (Internet Control " -"Message Protocol version 6)` router discovery messages. When first connected" -" to a network, a host sends a link-local router solicitation multicast " -"request for its configuration parameters; routers respond to such a request " -"with a router advertisement packet that contains Internet Layer " -"configuration parameters." -msgstr "" - -#: ../../_include/interface-ipv6.txt:12 cd540d2584da421490378bf3e831122e -msgid "" -"This method automatically disables IPv6 traffic forwarding on the interface " -"in question." -msgstr "" - -#: ../../_include/interface-ipv6.txt:25 6f3aa6ae21e040779b6ca6d0fd95865b -msgid "" -":abbr:`EUI-64 (64-Bit Extended Unique Identifier)` as specified in " -":rfc:`4291` allows a host to assign iteslf a unique 64-Bit IPv6 address." -msgstr "" - -#: ../../_include/interface-ipv6.txt:37 661b9d644aaf45fb8dcf2d1aad1897aa -msgid "Do not assign a link-local IPv6 address to this interface." -msgstr "" - -#: ../../_include/interface-ipv6.txt:65 68ccfbe56259486d827279f784960845 -msgid "" -"This command was introduced in VyOS 1.4 - it was previously called: ``set " -"firewall options interface <name> adjust-mss6 <value>``" -msgstr "" - -#: ../../_include/interface-ipv6.txt:68 70e961e874c547d3a2a239fe4cad82d8 -msgid "" -"MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 " -"bytes on a 1492 byte MTU." -msgstr "" - -#: ../../_include/interface-vrf.txt:4 6a36ef03d12f47da8614fe8e817e69d5 -msgid "Place interface in given VRF instance." -msgstr "" - -#: ../../_include/interface-vrf.txt:6 b0ae9521dcd246b69806f893fd1ce7c0 -msgid "" -"There is an entire chapter about how to configure a :ref:`vrf`, please check" -" this for additional information." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:54 be1222941fae4434bb9528104345da7f -msgid "**DHCP(v6)**" -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:4 -#: b6193a92af4946b3bb865520ca8534f0 -msgid "" -":rfc:`2131` states: The client MAY choose to explicitly provide the " -"identifier through the 'client identifier' option. If the client supplies a " -"'client identifier', the client MUST use the same 'client identifier' in all" -" subsequent messages, and the server MUST use that identifier to identify " -"the client." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:19 -#: c047021d3b264227bf2b140808628d47 -msgid "" -"Instead of sending the real system hostname to the DHCP server, overwrite " -"the host-name with this given-value." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:31 -#: 5e8e884d082048d68e3f93a1904f1003 -msgid "" -"The vendor-class-id option can be used to request a specific class of vendor" -" options from the server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:43 -#: a71ea77bb8ae4fff998a21e933fcb752 -msgid "" -"Only request an address from the DHCP server but do not request a default " -"gateway." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:55 -#: 7f4baa304c034d7287c3d5c64fa7fc00 -msgid "Set the distance for the default gateway sent by the DHCP server." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:66 -#: ea1d6d6d35d54df0992662a6ea231c26 -msgid "" -"Reject DHCP leases from a given address or range. This is useful when a " -"modem gives a local IP when first starting." -msgstr "" - -#: ../../_include/interface-dhcp-options.txt:69 -#: 2941f6b5d5ea4265b4ca81a4ff6ec788 -msgid "" -"**address** can be specified multiple times, e.g. 192.168.100.1 and/or " -"192.168.100.0/24" -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:4 -#: 5281378f797f4c51ace9a5c8f60eaf7f -msgid "" -"The DHCP unique identifier (DUID) is used by a client to get an IP address " -"from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length" -" identifier field up to 128 bytes. Its actual length depends on its type. " -"The server compares the DUID with its database and delivers configuration " -"data (address, lease times, DNS servers, etc.) to the client." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:17 -#: 7d0eb274334c44ac8707035db5e42ef0 -msgid "" -"This statement specifies dhcp6c to only exchange informational configuration" -" parameters with servers. A list of DNS server addresses is an example of " -"such parameters. This statement is useful when the client does not need " -"stateful configuration parameters such as IPv6 addresses or prefixes." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:29 -#: 641b4e0060a841d6914310f11739fa00 -msgid "" -"When rapid-commit is specified, dhcp6c will include a rapid-commit option in" -" solicit messages and wait for an immediate reply instead of advertisements." -msgstr "" - -#: ../../_include/interface-dhcpv6-options.txt:39 -#: 38b55a8d8770499488a25ac3d0247f5b -msgid "" -"Request only a temporary address and not form an IA_NA (Identity Association" -" for Non-temporary Addresses) partnership." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 -#: 964d131501d0439bb5582fc387f21aa0 -msgid "**DHCPv6 Prefix Delegation (PD)**" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 -#: 9bebbc60e2554c35ad2fc16b61cad324 -msgid "" -"VyOS 1.3 (equuleus) supports DHCPv6-PD (:rfc:`3633`). DHCPv6 Prefix " -"Delegation is supported by most ISPs who provide native IPv6 for consumers " -"on fixed networks." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 -#: ab9a16df68474805bd0f169876c893dd -msgid "" -"Some ISPs by default only delegate a /64 prefix. To request for a specific " -"prefix size use this option to request for a bigger delegation for this pd " -"`<id>`. This value is in the range from 32 - 64 so you could request up to a" -" /32 prefix (if your ISP allows this) down to a /64 delegation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 -#: a17e2b05141e458db342754e33d86492 -msgid "The default value corresponds to 64." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 -#: 393b4e3ad57844cdbfa33ef246dfb356 -msgid "To request a /56 prefix from your ISP use:" -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 -#: 1f53c131486c4d01a755cd9b36bb1571 -msgid "" -"Specify the interface address used locally on the interface where the prefix" -" has been delegated to. ID must be a decimal integer." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 -#: ed8206eddcc44d5ebf5b04870fb70ded -msgid "" -"It will be combined with the delegated prefix and the sla-id to form a " -"complete interface address. The default is to use the EUI-64 address of the " -"interface." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 -#: 31e8c898b32c44a7be3a896c510aa44f -msgid "" -"Example: Delegate a /64 prefix to interface eth8 which will use a local " -"address on this router of ``<prefix>::ffff``, as the address 65534 will " -"correspond to ``ffff`` in hexadecimal notation." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 -#: 373885c3a2fb41a3a19cc533d689e575 -msgid "" -"Specify the identifier value of the site-level aggregator (SLA) on the " -"interface. ID must be a decimal number greater then 0 which fits in the " -"length of SLA IDs (see below)." -msgstr "" - -#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 -#: b3717515150e4d0d930b5a27b555c60a -msgid "" -"Example: If ID is 1 and the client is delegated an IPv6 prefix " -"2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 " -"prefix, 2001:db8:ffff:1::/64, and will configure the prefix on the specified" -" interface." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:69 315e5e5f9bd940d298bf51260adb99a0 -msgid "WirelessModem (WWAN) options" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:73 afb346a57af6412280fd9917014cbeee -msgid "" -"Every WWAN connection requires an :abbr:`APN (Access Point Name)` which is " -"used by the client to dial into the ISPs network. This is a mandatory " -"parameter. Contact your Service Provider for correct APN." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:80 b6b605d0acd64827aa669538ec3cddd1 -msgid "Operation" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:84 a142e54046e84b668d16364d4dc6b2f3 -msgid "Show detailed information on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:103 -#: 4be1cdcdb94346c78fbc408c3a071941 -msgid "Show detailed information summary on given `<interface>`" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:170 -#: 2554d1c57ec847d9935f1a450939b8ab -msgid "Show WWAN module hardware capabilities." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:185 -#: 32e59af3aee3445ab3208d6aa92769f9 -msgid "Show WWAN module firmware." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:201 -#: c1b838c53f6948c6bd895cae41fd565e -msgid "Show WWAN module IMEI." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:212 -#: b63eaa3f23ee4dd89b497e015f18fd89 -msgid "Show WWAN module IMSI." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:221 -#: e323d5cbe6be49d6ae0ac1ecb74f554a -msgid "Show WWAN module model." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:230 -#: 286e154437444060b11011946f83862f -msgid "Show WWAN module MSISDN." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:239 -#: 6bd9633c1b3f4b73ae1b22f1eb783411 -msgid "Show WWAN module hardware revision." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:248 -#: de452cea54584b3dbd77135e508adf82 -msgid "Show WWAN module signal strength." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:264 -#: 9332150ebb51464fbf27dfd47a82ffb3 -msgid "Show WWAN module SIM card information." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:295 -#: 787dd9a9ffa84ea383b74bc9f8c263ae -msgid "Example" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:297 -#: 7f26d04f336c43c28e578611a22b59a7 -msgid "" -"The following example is based on a Sierra Wireless MC7710 miniPCIe card " -"(only the form factor in reality it runs UBS) and Deutsche Telekom as ISP. " -"The card is assembled into a :ref:`pc-engines-apu4`." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:308 -#: f76ad889f5e5420ebbf0f927a23641de -msgid "Supported Modules" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:310 -#: d6a7cdc8dc6541d39a84f303e029848b -msgid "" -"The following hardware modules have been tested successfully in an :ref:`pc-" -"engines-apu4` board:" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:313 -#: 07727509a31d4182b9b509488028bc19 -msgid "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:314 -#: 0b662895705e4f7bb0b43495db3f4d0b -msgid "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:315 -#: d015c5f5dd7645659acafab0c65d61a3 -msgid "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:316 -#: c0265d6c4c374f988ae7463ec005f516 -msgid "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:317 -#: 1d726fdddfae4f059228ab8bf24847d2 -msgid "Huawei ME909u-521 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:318 -#: 2e2f6d7818df4077974b8168cca0135f -msgid "Huawei ME909s-120 miniPCIe card (LTE)" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:322 -#: 441bc83d707e4052a307f76ac4e1bdb6 -msgid "Firmware Update" -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:324 -#: 62d86826f13d4874ab0542360526c1c1 -msgid "" -"All available WWAN cards have a build in, reprogrammable firmware. Most of " -"the vendors provide a regular update to the firmware used in the baseband " -"chip." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:327 -#: ef6020a1d3854fa18115e9acd98f1c63 -msgid "" -"As VyOS makes use of the QMI interface to connect to the WWAN modem cards, " -"also the firmware can be reprogrammed." -msgstr "" - -#: ../../configuration/interfaces/wwan.rst:330 -#: 25873f16f3d8445fb1bf073788fc370d -msgid "" -"To update the firmware, VyOS also ships the `qmi-firmware-update` binary. To" -" upgrade the firmware of an e.g. Sierra Wireless MC7710 module to the " -"firmware provided in the file " -"``9999999_9999999_9200_03.05.14.00_00_generic_000.000_001_SPKG_MC.cwe`` use " -"the following command:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/loadbalancing/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/loadbalancing/index.po deleted file mode 100644 index e34a7fe1..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/loadbalancing/index.po +++ /dev/null @@ -1,393 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/loadbalancing/index.rst:6 -#: 7568028d69a845c69b1b2d92f392082a -msgid "WAN load balancing" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:8 -#: 831779fbc3a341e5a239a149d09d66e2 -msgid "" -"Outbound traffic can be balanced between two or more outbound interfaces. If" -" a path fails, traffic is balanced across the remaining healthy paths, a " -"recovered path is automatically added back to the routing table and used by " -"the load balancer. The load balancer automatically adds routes for each path" -" to the routing table and balances traffic across the configured interfaces," -" determined by interface health and weight." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:16 -#: 0dd7a9ac1a5d4900b665c3fe1dae4ab0 -msgid "In a minimal configuration, the following must be provided:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:18 -#: 2b30983e9e9247d0b31a2cf1c3976067 -msgid "an interface with a nexthop" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:19 -#: be2e576a1a1941e6be617332eae116a6 -msgid "one rule with a LAN (inbound-interface) and the WAN (interface)." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:21 -#: debcda34477a49b5bd85f423120c45fa -msgid "Let's assume we have two DHCP WAN interfaces and one LAN (eth2):" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:33 -#: 7404c5dbac3a4701b6b59a3a52beb241 -msgid "" -"WAN Load Balacing should not be used when dynamic routing protocol is " -"used/needed. This feature creates customized routing tables and firewall " -"rules, that makes it incompatible to use with routing protocols." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:38 -#: c4c246bf197f4991bacb14b75e41ba61 -msgid "Balancing Rules" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:40 -#: a3c32d78cb8c4f9d997eda1219828b3d -msgid "" -"Interfaces, their weight and the type of traffic to be balanced are defined " -"in numbered balancing rule sets. The rule sets are executed in numerical " -"order against outgoing packets. In case of a match the packet is sent " -"through an interface specified in the matching rule. If a packet doesn't " -"match any rule it is sent by using the system routing table. Rule numbers " -"can't be changed." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:46 -#: da73e3fb4c1340ff80083bec02688c84 -msgid "Create a load balancing rule, it can be a number between 1 and 9999:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:64 -#: 680e9d86d8954ce8bfbc7bb85512db7b -msgid "Interface weight" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:66 -#: 829ea07e43eb41129add9c9472205cd0 -msgid "" -"Let's expand the example from above and add weight to the interfaces. The " -"bandwidth from eth0 is larger than eth1. Per default, outbound traffic is " -"distributed randomly across available interfaces. Weights can be assigned to" -" interfaces to influence the balancing." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:76 -#: 73dfb6b5278e4a0b9a398f2d5ebc11c5 -msgid "66% of traffic is routed to eth0, eth1 gets 33% of traffic." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:79 -#: 306eab57aabb4c16bf2e988a3636abc7 -msgid "Rate limit" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:81 -#: 2684d5aabac54cd7aafcf36cf050eab9 -msgid "" -"A packet rate limit can be set for a rule to apply the rule to traffic above" -" or below a specified threshold. To configure the rate limiting use:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:88 -#: 565368e68c144469be58b56ce8f36ba9 -msgid "" -"``burst``: Number of packets allowed to overshoot the limit within " -"``period``. Default 5." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:90 -#: 75e76fe9a1f544adac8e936aa91cb68a -msgid "" -"``period``: Time window for rate calculation. Possible values: ``second`` " -"(one second), ``minute`` (one minute), ``hour`` (one hour). Default is " -"``second``." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:93 -#: e79cff8d308f4d14b23aff256cff5f79 -msgid "``rate``: Number of packets. Default 5." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:94 -#: cd3881207f2e4efc98fb371fc142eb20 -msgid "``threshold``: ``below`` or ``above`` the specified rate limit." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:97 -#: 42d3358f24004b2b8d02ccde3dc71185 -msgid "Flow and packet-based balancing" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:99 -#: 5e061b435c3b409a9166a8bde7a0d7ca -msgid "" -"Outgoing traffic is balanced in a flow-based manner. A connection tracking " -"table is used to track flows by their source address, destination address " -"and port. Each flow is assigned to an interface according to the defined " -"balancing rules and subsequent packets are sent through the same interface. " -"This has the advantage that packets always arrive in order if links with " -"different speeds are in use." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:106 -#: ab745f4ea74444f49c61da3cb83ed14d -msgid "" -"Packet-based balancing can lead to a better balance across interfaces when " -"out of order packets are no issue. Per-packet-based balancing can be set for" -" a balancing rule with:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:115 -#: d5d06dae4fc24bee9df960b93e3a7ce3 -msgid "Exclude traffic" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:117 -#: be76a1da707d40778a27af8a791c7773 -msgid "" -"To exclude traffic from load balancing, traffic matching an exclude rule is " -"not balanced but routed through the system routing table instead:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:126 -#: ec9e884888ec42a686e6033d6e1d7189 -msgid "Health checks" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:128 -#: 4cf9259df4964df1887489b08ce5bff5 -msgid "" -"The health of interfaces and paths assigned to the load balancer is " -"periodically checked by sending ICMP packets (ping) to remote destinations, " -"a TTL test or the execution of a user defined script. If an interface fails " -"the health check it is removed from the load balancer's pool of interfaces. " -"To enable health checking for an interface:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:143 -#: 7ceb201d025c42f48ddbc23e79a9ff7d -msgid "" -"Specify nexthop on the path to the destination, ``ipv4-address`` can be set " -"to ``dhcp``" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:150 -#: f4134f8e6eb54eaea1ef88105d72e4ca -msgid "" -"Set the number of health check failures before an interface is marked as " -"unavailable, range for number is 1 to 10, default 1. Or set the number of " -"successful health checks before an interface is added back to the interface " -"pool, range for number is 1 to 10, default 1." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:160 -#: 66b7f0a004304beda063ea57212d7ea2 -msgid "" -"Each health check is configured in its own test, tests are numbered and " -"processed in numeric order. For multi target health checking multiple tests " -"can be defined:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:174 -#: d6cba43dbf1242fc99da877ce0edbc6b -msgid "" -"``resp-time``: the maximum response time for ping in seconds. Range 1...30, " -"default 5" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:176 -#: 8c1e19b0548e4feab27eebe31e14eeff -msgid "" -"``target``: the target to be sent ICMP packets to, address can be an IPv4 " -"address or hostname" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:178 -#: 2177b897db4b413aa3e3c337b4daa812 -msgid "" -"``test-script``: A user defined script must return 0 to be considered " -"successful and non-zero to fail. Scripts are located in /config/scripts, for" -" different locations the full path needs to be provided" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:181 -#: 2a21ab9f07e348ed9314596574c08a07 -msgid "" -"``ttl-limit``: For the UDP TTL limit test the hop count limit must be " -"specified. The limit must be shorter than the path length, an ICMP time " -"expired message is needed to be returned for a successful test. default 1" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:184 -#: 56785e8688d0440fa7280788ddb5a940 -msgid "" -"``type``: Specify the type of test. type can be ping, ttl or a user defined " -"script" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:188 -#: e5b8efbb670b49eaa0033d6110b5bca9 -msgid "Source NAT rules" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:190 -#: 5d59554e0d6f4662891a6271f775a42c -msgid "" -"Per default, interfaces used in a load balancing pool replace the source IP " -"of each outgoing packet with its own address to ensure that replies arrive " -"on the same interface. This works through automatically generated source NAT" -" (SNAT) rules, these rules are only applied to balanced traffic. In cases " -"where this behaviour is not desired, the automatic generation of SNAT rules " -"can be disabled:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:202 -#: 39a7bbb7d17b479e9e1b72a772cead9d -msgid "Sticky Connections" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:203 -#: 91da7f59bb7e4418a41836d13bfcc20e -msgid "" -"Inbound connections to a WAN interface can be improperly handled when the " -"reply is sent back to the client." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:211 -#: fbb632606ae2401a9e31fb41f26df32d -msgid "" -"Upon reception of an incoming packet, when a response is sent, it might be " -"desired to ensure that it leaves from the same interface as the inbound one." -" This can be achieved by enabling sticky connections in the load balancing:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:220 -#: ffcede5ef47341309cba8c638209b8ba -msgid "Failover" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:222 -#: 22bb9f5b92e14c1e9c09b138b4c0a808 -msgid "" -"In failover mode, one interface is set to be the primary interface and other" -" interfaces are secondary or spare. Instead of balancing traffic across all " -"healthy interfaces, only the primary interface is used and in case of " -"failure, a secondary interface selected from the pool of available " -"interfaces takes over. The primary interface is selected based on its weight" -" and health, others become secondary interfaces. Secondary interfaces to " -"take over a failed primary interface are chosen from the load balancer's " -"interface pool, depending on their weight and health. Interface roles can " -"also be selected based on rule order by including interfaces in balancing " -"rules and ordering those rules accordingly. To put the load balancer in " -"failover mode, create a failover rule:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:237 -#: c14b0b6e33834c97b4112891ad54156f -msgid "" -"Because existing sessions do not automatically fail over to a new path, the " -"session table can be flushed on each connection state change:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:246 -#: b2398f465a9f47d4b6f59f2784d0cf17 -msgid "" -"Flushing the session table will cause other connections to fall back from " -"flow-based to packet-based balancing until each flow is reestablished." -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:250 -#: 1956ee55d594400892fc1a565f1c09f1 -msgid "Script execution" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:252 -#: 49495379028c4d5084c39d1b7dc5eaf1 -msgid "" -"A script can be run when an interface state change occurs. Scripts are run " -"from /config/scripts, for a different location specify the full path:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:259 -#: 851bc19f9d2247a59080b9c7ea6bcb35 -msgid "Two environment variables are available:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:261 -#: 67add2d32d0f44fab31ba8cfc5863bfb -msgid "``WLB_INTERFACE_NAME=[interfacename]``: Interface to be monitored" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:262 -#: 3c00120d56f6425a8d89838805058f7f -msgid "``WLB_INTERFACE_STATE=[ACTIVE|FAILED]``: Interface state" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:266 -#: 475f317333bd44ff85c2f6901c2aca1e -msgid "" -"Blocking call with no timeout. System will become unresponsive if script " -"does not return!" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:270 -#: 5ae6f839cbea42b081cbd2c2d5e412ab -msgid "Handling and monitoring" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:273 -#: efcebfb9543344069b8365aa4d931abd -msgid "" -"Show WAN load balancer information including test types and targets. A " -"character at the start of each line depicts the state of the test" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:276 -#: 43e0b718d9d24e56a8eec67a31685931 -msgid "``+`` successful" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:277 -#: 4c1dc2cbcdb64116a7bf938941e2557c -msgid "``-`` failed" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:278 -#: 694e1dbfeb2a4017870c3d5d3cd3a70a -msgid "a blank indicates that no test has been carried out" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:299 -#: f117595dd72b4b1280e813a4ac299bc2 -msgid "Show connection data of load balanced traffic:" -msgstr "" - -#: ../../configuration/loadbalancing/index.rst:311 -#: c958cc4741894858b134b203aa00d436 -msgid "Restart" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/index.po deleted file mode 100644 index ce5b212d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/nat/index.rst:5 0be96f1f2c914c17957ec95f65e80e87 -msgid "NAT" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat44.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat44.po deleted file mode 100644 index 63b6bc9f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat44.po +++ /dev/null @@ -1,763 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/nat/nat44.rst:5 1b9e6cdee6d74c85b2e8c45fb9d2eba8 -msgid "NAT44" -msgstr "" - -#: ../../configuration/nat/nat44.rst:7 e08ab3f298144e30953a0e3c994d4757 -msgid "" -":abbr:`NAT (Network Address Translation)` is a common method of remapping " -"one IP address space into another by modifying network address information " -"in the IP header of packets while they are in transit across a traffic " -"routing device. The technique was originally used as a shortcut to avoid the" -" need to readdress every host when a network was moved. It has become a " -"popular and essential tool in conserving global address space in the face of" -" IPv4 address exhaustion. One Internet-routable IP address of a NAT gateway " -"can be used for an entire private network." -msgstr "" - -#: ../../configuration/nat/nat44.rst:17 4ea7c21ae60b4113900fbda6434cc2a4 -msgid "" -"IP masquerading is a technique that hides an entire IP address space, " -"usually consisting of private IP addresses, behind a single IP address in " -"another, usually public address space. The hidden addresses are changed into" -" a single (public) IP address as the source address of the outgoing IP " -"packets so they appear as originating not from the hidden host but from the " -"routing device itself. Because of the popularity of this technique to " -"conserve IPv4 address space, the term NAT has become virtually synonymous " -"with IP masquerading." -msgstr "" - -#: ../../configuration/nat/nat44.rst:26 064330dfcfaf4415b2dd857e44eba2e9 -msgid "" -"As network address translation modifies the IP address information in " -"packets, NAT implementations may vary in their specific behavior in various " -"addressing cases and their effect on network traffic. The specifics of NAT " -"behavior are not commonly documented by vendors of equipment containing NAT " -"implementations." -msgstr "" - -#: ../../configuration/nat/nat44.rst:32 188c9203e52c4f87b21e186cc041ba77 -msgid "" -"The computers on an internal network can use any of the addresses set aside " -"by the :abbr:`IANA (Internet Assigned Numbers Authority)` for private " -"addressing (see :rfc:`1918`). These reserved IP addresses are not in use on " -"the Internet, so an external machine will not directly route to them. The " -"following addresses are reserved for private use:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:38 5212ced1f56e4930828b32f7a923df69 -msgid "10.0.0.0 to 10.255.255.255 (CIDR: 10.0.0.0/8)" -msgstr "" - -#: ../../configuration/nat/nat44.rst:39 2d5f2db6d18f41fb998d13f65e5dff38 -msgid "172.16.0.0 to 172.31.255.255 (CIDR: 172.16.0.0/12)" -msgstr "" - -#: ../../configuration/nat/nat44.rst:40 f79fbe86407c4f9a82a3263e33ebe2e4 -msgid "192.168.0.0 to 192.168.255.255 (CIDR: 192.168.0.0/16)" -msgstr "" - -#: ../../configuration/nat/nat44.rst:43 b533ec1201cc453ba199974450f9eae2 -msgid "" -"If an ISP deploys a :abbr:`CGN (Carrier-grade NAT)`, and uses :rfc:`1918` " -"address space to number customer gateways, the risk of address collision, " -"and therefore routing failures, arises when the customer network already " -"uses an :rfc:`1918` address space." -msgstr "" - -#: ../../configuration/nat/nat44.rst:48 9fddc1b315044164b59dcdd0630f936a -msgid "" -"This prompted some ISPs to develop a policy within the :abbr:`ARIN (American" -" Registry for Internet Numbers)` to allocate new private address space for " -"CGNs, but ARIN deferred to the IETF before implementing the policy " -"indicating that the matter was not a typical allocation issue but a " -"reservation of addresses for technical purposes (per :rfc:`2860`)." -msgstr "" - -#: ../../configuration/nat/nat44.rst:55 5a353c42153f4dc28f86f3131c4db7f5 -msgid "" -"IETF published :rfc:`6598`, detailing a shared address space for use in ISP " -"CGN deployments that can handle the same network prefixes occurring both on " -"inbound and outbound interfaces. ARIN returned address space to the " -":abbr:`IANA (Internet Assigned Numbers Authority)` for this allocation." -msgstr "" - -#: ../../configuration/nat/nat44.rst:61 8c59eb89d7114922b651287c4b7af83a -msgid "The allocated address block is 100.64.0.0/10." -msgstr "" - -#: ../../configuration/nat/nat44.rst:63 4f5eb70128a04ad6bb553fc3557955a2 -msgid "" -"Devices evaluating whether an IPv4 address is public must be updated to " -"recognize the new address space. Allocating more private IPv4 address space " -"for NAT devices might prolong the transition to IPv6." -msgstr "" - -#: ../../configuration/nat/nat44.rst:68 acb039055c4744d2aae41638f29f8a09 -msgid "Overview" -msgstr "" - -#: ../../configuration/nat/nat44.rst:71 c9de3d82b79f48898cbe3419cefc9903 -msgid "Different NAT Types" -msgstr "" - -#: ../../configuration/nat/nat44.rst:76 df02ea558bf54985a36a5057147d9638 -msgid "SNAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:78 3e9b654e733b4fa89541b8e55f094efa -msgid "" -":abbr:`SNAT (Source Network Address Translation)` is the most common form of" -" :abbr:`NAT (Network Address Translation)` and is typically referred to " -"simply as NAT. To be more correct, what most people refer to as :abbr:`NAT " -"(Network Address Translation)` is actually the process of :abbr:`PAT (Port " -"Address Translation)`, or NAT overload. SNAT is typically used by internal " -"users/private hosts to access the Internet - the source address is " -"translated and thus kept private." -msgstr "" - -#: ../../configuration/nat/nat44.rst:89 7671c435d8824bd999ad75a2b0649525 -msgid "DNAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:91 526aabf0ca874bc7b303565df5da12ae -msgid "" -":abbr:`DNAT (Destination Network Address Translation)` changes the " -"destination address of packets passing through the router, while " -":ref:`source-nat` changes the source address of packets. DNAT is typically " -"used when an external (public) host needs to initiate a session with an " -"internal (private) host. A customer needs to access a private service behind" -" the routers public IP. A connection is established with the routers public " -"IP address on a well known port and thus all traffic for this port is " -"rewritten to address the internal (private) host." -msgstr "" - -#: ../../configuration/nat/nat44.rst:104 1b3f7df53053452d88f4462293ba9931 -msgid "Bidirectional NAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:106 6711a061220b4b079980b90200904c6e -msgid "" -"This is a common scenario where both :ref:`source-nat` and " -":ref:`destination-nat` are configured at the same time. It's commonly used " -"when internal (private) hosts need to establish a connection with external " -"resources and external systems need to access internal (private) resources." -msgstr "" - -#: ../../configuration/nat/nat44.rst:113 f27e3be2749344e4b82ce42d2243423a -msgid "NAT, Routing, Firewall Interaction" -msgstr "" - -#: ../../configuration/nat/nat44.rst:115 472103bd3281489ebebf5993395e23e2 -msgid "" -"There is a very nice picture/explanation in the Vyatta documentation which " -"should be rewritten here." -msgstr "" - -#: ../../configuration/nat/nat44.rst:119 175327d574554d8992a0d30949c1a6de -msgid "NAT Ruleset" -msgstr "" - -#: ../../configuration/nat/nat44.rst:121 e77c9d84746d49609c5193ec33db6a52 -msgid "" -":abbr:`NAT (Network Address Translation)` is configured entirely on a series" -" of so called `rules`. Rules are numbered and evaluated by the underlying OS" -" in numerical order! The rule numbers can be changes by utilizing the " -":cfgcmd:`rename` and :cfgcmd:`copy` commands." -msgstr "" - -#: ../../configuration/nat/nat44.rst:126 f326bffbc92f4fc1afde2e0e7f474150 -msgid "" -"Changes to the NAT system only affect newly established connections. Already" -" established connections are not affected." -msgstr "" - -#: ../../configuration/nat/nat44.rst:129 0fb7907e34104640925e6acca4b2633d -msgid "" -"When designing your NAT ruleset leave some space between consecutive rules " -"for later extension. Your ruleset could start with numbers 10, 20, 30. You " -"thus can later extend the ruleset and place new rules between existing ones." -msgstr "" - -#: ../../configuration/nat/nat44.rst:134 a6e7f2a9fee941e4bb4198a776cbae8a -msgid "" -"Rules will be created for both :ref:`source-nat` and :ref:`destination-nat`." -msgstr "" - -#: ../../configuration/nat/nat44.rst:137 2618c8a2f101400480fb728fe4e73623 -msgid "" -"For :ref:`bidirectional-nat` a rule for both :ref:`source-nat` and " -":ref:`destination-nat` needs to be created." -msgstr "" - -#: ../../configuration/nat/nat44.rst:143 fda84449eaaf4d3c8ef8a8ad94087824 -msgid "Traffic Filters" -msgstr "" - -#: ../../configuration/nat/nat44.rst:145 9e5024862eb0413c94ff75269dcad7fb -msgid "" -"Traffic Filters are used to control which packets will have the defined NAT " -"rules applied. Five different filters can be applied within a NAT rule." -msgstr "" - -#: ../../configuration/nat/nat44.rst:149 c6e0d14c6a0f47c79c5ced6da3a6e1d1 -msgid "" -"**outbound-interface** - applicable only to :ref:`source-nat`. It configures" -" the interface which is used for the outside traffic that this translation " -"rule applies to." -msgstr "" - -#: ../../configuration/nat/nat44.rst:153 ../../configuration/nat/nat44.rst:163 -#: ../../configuration/nat/nat44.rst:173 ../../configuration/nat/nat44.rst:187 -#: ../../configuration/nat/nat44.rst:208 ../../configuration/nat/nat44.rst:244 -#: ../../configuration/nat/nat44.rst:266 ../../configuration/nat/nat44.rst:375 -#: 8f7cca53294d42ca80b7561a000afe8b 5101ff4453ec4b7b832b5779c282f637 -#: b74a4cbbfcdb4a37a08e89a649660b99 6c8982cd275644bab2bd4862bc85d844 -#: 8df0bd9f87334b278010991e92e07ba3 84c53e0ab6654cd691db48fbbc9fc46c -#: d97714cdd8d44100bb5adda2342c9ff4 6e7d91b21b9244918197b0e2bbe41b14 -msgid "Example:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:159 ad2e63e18df1494fab3373cbdc3a57de -msgid "" -"**inbound-interface** - applicable only to :ref:`destination-nat`. It " -"configures the interface which is used for the inside traffic the " -"translation rule applies to." -msgstr "" - -#: ../../configuration/nat/nat44.rst:169 a1f9ea8e22504b25a6b43e64b86feaf9 -msgid "" -"**protocol** - specify which types of protocols this translation rule " -"applies to. Only packets matching the specified protocol are NATed. By " -"default this applies to `all` protocols." -msgstr "" - -#: ../../configuration/nat/nat44.rst:175 6070bf12804c4be8b35bd6b990f10d10 -msgid "Set SNAT rule 20 to only NAT TCP and UDP packets" -msgstr "" - -#: ../../configuration/nat/nat44.rst:176 ff73422eded64f289a8663d8c3ecb6e2 -msgid "Set DNAT rule 20 to only NAT UDP packets" -msgstr "" - -#: ../../configuration/nat/nat44.rst:183 57f9664483354005a3d0633b2a2d3597 -msgid "" -"**source** - specifies which packets the NAT translation rule applies to " -"based on the packets source IP address and/or source port. Only matching " -"packets are considered for NAT." -msgstr "" - -#: ../../configuration/nat/nat44.rst:189 2d21e4d475444d1db82fda191a819af2 -msgid "" -"Set SNAT rule 20 to only NAT packets arriving from the 192.0.2.0/24 network" -msgstr "" - -#: ../../configuration/nat/nat44.rst:191 36bcab08bd844a86937d6c5de6081457 -msgid "" -"Set SNAT rule 30 to only NAT packets arriving from the 203.0.113.0/24 " -"network with a source port of 80 and 443" -msgstr "" - -#: ../../configuration/nat/nat44.rst:201 e208f02ee30e435d8e55fc595add37a4 -msgid "" -"**destination** - specify which packets the translation will be applied to, " -"only based on the destination address and/or port number configured." -msgstr "" - -#: ../../configuration/nat/nat44.rst:205 cb4b20fe989b4e0e9d842914dbb6da02 -msgid "" -"If no destination is specified the rule will match on any destination " -"address and port." -msgstr "" - -#: ../../configuration/nat/nat44.rst:210 c5c6152ae64849b2a30413a5a233fa9b -msgid "" -"Configure SNAT rule (40) to only NAT packets with a destination address of " -"192.0.2.1." -msgstr "" - -#: ../../configuration/nat/nat44.rst:219 4c044ee797ff4020b4b2cbb90e387868 -msgid "Address Conversion" -msgstr "" - -#: ../../configuration/nat/nat44.rst:221 8503a24655ee47ec98b883bb6bc3da79 -msgid "" -"Every NAT rule has a translation command defined. The address defined for " -"the translation is the address used when the address information in a packet" -" is replaced." -msgstr "" - -#: ../../configuration/nat/nat44.rst:226 d219b4d17c4343de8debd4c622e3970c -msgid "Source Address" -msgstr "" - -#: ../../configuration/nat/nat44.rst:228 12ce0e9e181d43bc830a57b5022077af -msgid "" -"For :ref:`source-nat` rules the packets source address will be replaced with" -" the address specified in the translation command. A port translation can " -"also be specified and is part of the translation address." -msgstr "" - -#: ../../configuration/nat/nat44.rst:233 c1d4e83917dc48e6a66bf1ed630a10cb -msgid "" -"The translation address must be set to one of the available addresses on the" -" configured `outbound-interface` or it must be set to `masquerade` which " -"will use the primary IP address of the `outbound-interface` as its " -"translation address." -msgstr "" - -#: ../../configuration/nat/nat44.rst:238 ca4921a0d5394ae6830969fb334039d2 -msgid "" -"When using NAT for a large number of host systems it recommended that a " -"minimum of 1 IP address is used to NAT every 256 private host systems. This " -"is due to the limit of 65,000 port numbers available for unique translations" -" and a reserving an average of 200-300 sessions per host system." -msgstr "" - -#: ../../configuration/nat/nat44.rst:246 bdd7ddee321f4842836c3fde41753a00 -msgid "Define a discrete source IP address of 100.64.0.1 for SNAT rule 20" -msgstr "" - -#: ../../configuration/nat/nat44.rst:247 156e1227679e4e1980a2ebdb358e0ddd -msgid "Use address `masquerade` (the interfaces primary address) on rule 30" -msgstr "" - -#: ../../configuration/nat/nat44.rst:248 69ea3491918c4657aa8b29a4cbe32302 -msgid "" -"For a large amount of private machines behind the NAT your address pool " -"might to be bigger. Use any address in the range 100.64.0.10 - 100.64.0.20 " -"on SNAT rule 40 when doing the translation" -msgstr "" - -#: ../../configuration/nat/nat44.rst:261 c8620f18958f47d99f428deb5a097420 -msgid "Destination Address" -msgstr "" - -#: ../../configuration/nat/nat44.rst:263 f98288b5d7694ad4ada23abaa6c279e5 -msgid "" -"For :ref:`destination-nat` rules the packets destination address will be " -"replaced by the specified address in the `translation address` command." -msgstr "" - -#: ../../configuration/nat/nat44.rst:268 d941c70eda8e4c3793070304e575457b -msgid "" -"DNAT rule 10 replaces the destination address of an inbound packet with " -"192.0.2.10" -msgstr "" - -#: ../../configuration/nat/nat44.rst:277 ada6abab816c4f3bbaf3caf3f0cdf0f0 -msgid "Configuration Examples" -msgstr "" - -#: ../../configuration/nat/nat44.rst:279 457ccdc380b948c7808c402be33a51bc -msgid "To setup SNAT, we need to know:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:281 1bccc3b7b7884376952fc1a34916726a -msgid "The internal IP addresses we want to translate" -msgstr "" - -#: ../../configuration/nat/nat44.rst:282 e247747334974c36b5b5f7232f0cb10a -msgid "The outgoing interface to perform the translation on" -msgstr "" - -#: ../../configuration/nat/nat44.rst:283 d94342b41388455abbcad1615c5d3754 -msgid "The external IP address to translate to" -msgstr "" - -#: ../../configuration/nat/nat44.rst:285 b5556ea34ced4762924ec603af4f6bda -msgid "" -"In the example used for the Quick Start configuration above, we demonstrate " -"the following configuration:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:294 680d407c3e6d4e3aa57bacde5ded38ee -msgid "Which generates the following configuration:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:308 954954df84144498b903a234ff57c751 -msgid "" -"In this example, we use **masquerade** as the translation address instead of" -" an IP address. The **masquerade** target is effectively an alias to say " -"\"use whatever IP address is on the outgoing interface\", rather than a " -"statically configured IP address. This is useful if you use DHCP for your " -"outgoing interface and do not know what the external address will be." -msgstr "" - -#: ../../configuration/nat/nat44.rst:315 6c99bebd71e547e68609971eba3e2ba8 -msgid "" -"When using NAT for a large number of host systems it recommended that a " -"minimum of 1 IP address is used to NAT every 256 host systems. This is due " -"to the limit of 65,000 port numbers available for unique translations and a " -"reserving an average of 200-300 sessions per host system." -msgstr "" - -#: ../../configuration/nat/nat44.rst:321 71beae2ecabd4d78816adbfb39f5124b -msgid "" -"Example: For an ~8,000 host network a source NAT pool of 32 IP addresses is " -"recommended." -msgstr "" - -#: ../../configuration/nat/nat44.rst:324 6b60d46443454374affdb730ee4ea314 -msgid "" -"A pool of addresses can be defined by using a hyphen between two IP " -"addresses:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:334 8e8256b4ad1445a48e39d573c74a1a6a -msgid "Avoiding \"leaky\" NAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:336 e2fdb9bfc2424776916452748e036fe8 -msgid "" -"Linux netfilter will not NAT traffic marked as INVALID. This often confuses " -"people into thinking that Linux (or specifically VyOS) has a broken NAT " -"implementation because non-NATed traffic is seen leaving an external " -"interface. This is actually working as intended, and a packet capture of the" -" \"leaky\" traffic should reveal that the traffic is either an additional " -"TCP \"RST\", \"FIN,ACK\", or \"RST,ACK\" sent by client systems after Linux " -"netfilter considers the connection closed. The most common is the additional" -" TCP RST some host implementations send after terminating a connection " -"(which is implementation-specific)." -msgstr "" - -#: ../../configuration/nat/nat44.rst:346 7cce3b9fddb54c1e9436c790e595538b -msgid "" -"In other words, connection tracking has already observed the connection be " -"closed and has transition the flow to INVALID to prevent attacks from " -"attempting to reuse the connection." -msgstr "" - -#: ../../configuration/nat/nat44.rst:350 feeea86cebe9474abddd9a79b67f022f -msgid "" -"You can avoid the \"leaky\" behavior by using a firewall policy that drops " -"\"invalid\" state packets." -msgstr "" - -#: ../../configuration/nat/nat44.rst:353 aef01f16a83b4508815489ac62ce25de -msgid "" -"Having control over the matching of INVALID state traffic, e.g. the ability " -"to selectively log, is an important troubleshooting tool for observing " -"broken protocol behavior. For this reason, VyOS does not globally drop " -"invalid state traffic, instead allowing the operator to make the " -"determination on how the traffic is handled." -msgstr "" - -#: ../../configuration/nat/nat44.rst:362 8d471c879a444d639b27065c50db48ed -msgid "Hairpin NAT/NAT Reflection" -msgstr "" - -#: ../../configuration/nat/nat44.rst:364 fb7d9d3e34df47b8b4e8506c66f9df08 -msgid "" -"A typical problem with using NAT and hosting public servers is the ability " -"for internal systems to reach an internal server using it's external IP " -"address. The solution to this is usually the use of split-DNS to correctly " -"point host systems to the internal address when requests are made " -"internally. Because many smaller networks lack DNS infrastructure, a work-" -"around is commonly deployed to facilitate the traffic by NATing the request " -"from internal hosts to the source address of the internal interface on the " -"firewall." -msgstr "" - -#: ../../configuration/nat/nat44.rst:373 7aee5b5a268b42cbbb2cd32139eb6c7b -msgid "" -"This technique is commonly referred to as NAT Reflection or Hairpin NAT." -msgstr "" - -#: ../../configuration/nat/nat44.rst:377 aaf04de912134e3a8ce45d70500f54b4 -msgid "" -"Redirect Microsoft RDP traffic from the outside (WAN, external) world via " -":ref:`destination-nat` in rule 100 to the internal, private host 192.0.2.40." -msgstr "" - -#: ../../configuration/nat/nat44.rst:381 b72b4bf6d7674f6d9c14aed354fc1476 -msgid "" -"Redirect Microsoft RDP traffic from the internal (LAN, private) network via " -":ref:`destination-nat` in rule 110 to the internal, private host 192.0.2.40." -" We also need a :ref:`source-nat` rule 110 for the reverse path of the " -"traffic. The internal network 192.0.2.0/24 is reachable via interface " -"`eth0.10`." -msgstr "" - -#: ../../configuration/nat/nat44.rst:408 754e7a0d6f634f10b55c714415a5dff5 -msgid "Which results in a configuration of:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:456 6cbf530eaa69427897a772c29ef7515d -msgid "Destination NAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:458 fa9e5a5136f34f1099f3ee0849c197e7 -msgid "" -"DNAT is typically referred to as a **Port Forward**. When using VyOS as a " -"NAT router and firewall, a common configuration task is to redirect incoming" -" traffic to a system behind the firewall." -msgstr "" - -#: ../../configuration/nat/nat44.rst:462 148264ccec934db09a6e9549400b0d75 -msgid "" -"In this example, we will be using the example Quick Start configuration " -"above as a starting point." -msgstr "" - -#: ../../configuration/nat/nat44.rst:465 d94c10098e634f3aa1973110e550246c -msgid "To setup a destination NAT rule we need to gather:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:467 944530186ef448c094dc98d4251586f9 -msgid "The interface traffic will be coming in on;" -msgstr "" - -#: ../../configuration/nat/nat44.rst:468 455af1fdf0df464eb39988b3c488f8de -msgid "The protocol and port we wish to forward;" -msgstr "" - -#: ../../configuration/nat/nat44.rst:469 89e2483d1eb742549d2e23edd4e7c6cf -msgid "The IP address of the internal system we wish to forward traffic to." -msgstr "" - -#: ../../configuration/nat/nat44.rst:471 691a8792db7149d5baa741ac7adb3cfe -msgid "" -"In our example, we will be forwarding web server traffic to an internal web " -"server on 192.168.0.100. HTTP traffic makes use of the TCP protocol on port " -"80. For other common port numbers, see: " -"https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers" -msgstr "" - -#: ../../configuration/nat/nat44.rst:476 e000b785fb1c46f78d5c32d9203513ed -msgid "Our configuration commands would be:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:486 539586cf299344a98612d61ce1a775c0 -msgid "Which would generate the following NAT destination configuration:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:506 d78722b504bc41f394f078e54b94c511 -msgid "" -"If forwarding traffic to a different port than it is arriving on, you may " -"also configure the translation port using `set nat destination rule [n] " -"translation port`." -msgstr "" - -#: ../../configuration/nat/nat44.rst:510 2932fbd4f1d743d98a16fb82490a8726 -msgid "" -"This establishes our Port Forward rule, but if we created a firewall policy " -"it will likely block the traffic." -msgstr "" - -#: ../../configuration/nat/nat44.rst:513 645e0cb73ba447b299902dfcdc6e1473 -msgid "" -"It is important to note that when creating firewall rules that the DNAT " -"translation occurs **before** traffic traverses the firewall. In other " -"words, the destination address has already been translated to 192.168.0.100." -msgstr "" - -#: ../../configuration/nat/nat44.rst:518 f7e05afc9d9d492bbfe0c236ca282cf5 -msgid "" -"So in our firewall policy, we want to allow traffic coming in on the outside" -" interface, destined for TCP port 80 and the IP address of 192.168.0.100." -msgstr "" - -#: ../../configuration/nat/nat44.rst:530 4d9193f3c02f49be82543b7203ceee26 -msgid "This would generate the following configuration:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:548 82c91c25c1df48ce906090e5c15fb12d -msgid "" -"If you have configured the `INSIDE-OUT` policy, you will need to add " -"additional rules to permit inbound NAT traffic." -msgstr "" - -#: ../../configuration/nat/nat44.rst:552 f28c6e32b07f47979b81955e1c8cf89e -msgid "1-to-1 NAT" -msgstr "" - -#: ../../configuration/nat/nat44.rst:554 fca368be80544382a6c637fe9a2d30f7 -msgid "" -"Another term often used for DNAT is **1-to-1 NAT**. For a 1-to-1 NAT " -"configuration, both DNAT and SNAT are used to NAT all traffic from an " -"external IP address to an internal IP address and vice-versa." -msgstr "" - -#: ../../configuration/nat/nat44.rst:558 805394fd501341eea4af52d84406e247 -msgid "" -"Typically, a 1-to-1 NAT rule omits the destination port (all ports) and " -"replaces the protocol with either **all** or **ip**." -msgstr "" - -#: ../../configuration/nat/nat44.rst:561 4283fadfebf847989b5100ff5a569ea1 -msgid "" -"Then a corresponding SNAT rule is created to NAT outgoing traffic for the " -"internal IP to a reserved external IP. This dedicates an external IP address" -" to an internal IP address and is useful for protocols which don't have the " -"notion of ports, such as GRE." -msgstr "" - -#: ../../configuration/nat/nat44.rst:566 2b05c98589c24734880407d0ef556297 -msgid "" -"Here's an extract of a simple 1-to-1 NAT configuration with one internal and" -" one external interface:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:584 df1c6a2d92ef459faa38a2d7dabb46f9 -msgid "" -"Firewall rules are written as normal, using the internal IP address as the " -"source of outbound rules and the destination of inbound rules." -msgstr "" - -#: ../../configuration/nat/nat44.rst:588 96829b0bf05c44ad97bfc28fdb91d203 -msgid "NAT before VPN" -msgstr "" - -#: ../../configuration/nat/nat44.rst:590 4cabb10ca60343f781e3d1354b222e2d -msgid "" -"Some application service providers (ASPs) operate a VPN gateway to provide " -"access to their internal resources, and require that a connecting " -"organisation translate all traffic to the service provider network to a " -"source address provided by the ASP." -msgstr "" - -#: ../../configuration/nat/nat44.rst:596 acc44d1d74074a758329ebc05372f4a9 -msgid "Example Network" -msgstr "" - -#: ../../configuration/nat/nat44.rst:598 0824e6fad83244bca672f714e1e9a958 -msgid "" -"Here's one example of a network environment for an ASP. The ASP requests " -"that all connections from this company should come from 172.29.41.89 - an " -"address that is assigned by the ASP and not in use at the customer site." -msgstr "" - -#: ../../configuration/nat/nat44.rst:607 ../../configuration/nat/nat44.rst:607 -#: 25f9729fb7bc462a9c37a6af6a3834cb 1cf4f6ec216b425fb4fec8263a583511 -msgid "NAT before VPN Topology" -msgstr "" - -#: ../../configuration/nat/nat44.rst:611 04627ca4d6bb440bb38ef5aa99a6d3b9 -msgid "Configuration" -msgstr "" - -#: ../../configuration/nat/nat44.rst:613 6c6a87f12b934f7eba01d03391cdf518 -msgid "The required configuration can be broken down into 4 major pieces:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:615 58671ff2b2494557ab2bda333ea89736 -msgid "A dummy interface for the provider-assigned IP;" -msgstr "" - -#: ../../configuration/nat/nat44.rst:616 dfa45185a3194a88a6ff9c1ea368ae49 -msgid "NAT (specifically, Source NAT);" -msgstr "" - -#: ../../configuration/nat/nat44.rst:617 598cf4b6f28b4b8a94dc1aa6b2c368e7 -msgid "IPSec IKE and ESP Groups;" -msgstr "" - -#: ../../configuration/nat/nat44.rst:618 653ab20b2fd248c987c90cf7bca183c1 -msgid "IPSec VPN tunnels." -msgstr "" - -#: ../../configuration/nat/nat44.rst:622 5bdd6be01a22423f8671b0135131eddc -msgid "Dummy interface" -msgstr "" - -#: ../../configuration/nat/nat44.rst:624 520ce645867d43f7bcc0cc20d1654ec5 -msgid "" -"The dummy interface allows us to have an equivalent of the Cisco IOS " -"Loopback interface - a router-internal interface we can use for IP addresses" -" the router must know about, but which are not actually assigned to a real " -"network." -msgstr "" - -#: ../../configuration/nat/nat44.rst:629 f266510a8ca04bf1948d0676973c522e -msgid "We only need a single step for this interface:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:636 0d6ca0e0ef2543cbb17d107c1005d578 -msgid "NAT Configuration" -msgstr "" - -#: ../../configuration/nat/nat44.rst:652 687002ad2f5b4e5798958dd1cc8db782 -msgid "IPSec IKE and ESP" -msgstr "" - -#: ../../configuration/nat/nat44.rst:654 73105f46766743b099c330d399298987 -msgid "The ASP has documented their IPSec requirements:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:656 72b7839738374482ae1bfc8d11d7b128 -msgid "IKE Phase:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:658 ../../configuration/nat/nat44.rst:663 -#: 2ec91cf9c88946808f60ec1bc429ca30 3ebfaa7080754e529d5765e1389b892a -msgid "aes256 Encryption" -msgstr "" - -#: ../../configuration/nat/nat44.rst:659 ../../configuration/nat/nat44.rst:664 -#: d5ec83da88db4d928df83d6a42822406 20f0a157e78b42b9baa977349facc5c5 -msgid "sha256 Hashes" -msgstr "" - -#: ../../configuration/nat/nat44.rst:661 6c9cd7920eb64d44a47641a298864454 -msgid "ESP Phase:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:665 4d0e7470113648b68b5ce3a0c0811c05 -msgid "DH Group 14" -msgstr "" - -#: ../../configuration/nat/nat44.rst:668 6e61c9be895148e9ac15bacab1bc3b4f -msgid "" -"Additionally, we want to use VPNs only on our eth1 interface (the external " -"interface in the image above)" -msgstr "" - -#: ../../configuration/nat/nat44.rst:690 387869f7511943cc83e9206c2a37b138 -msgid "IPSec VPN Tunnels" -msgstr "" - -#: ../../configuration/nat/nat44.rst:692 a9c5e360993041bb989e51669025a30a -msgid "" -"We'll use the IKE and ESP groups created above for this VPN. Because we need" -" access to 2 different subnets on the far side, we will need two different " -"tunnels. If you changed the names of the ESP group and IKE group in the " -"previous step, make sure you use the correct names here too." -msgstr "" - -#: ../../configuration/nat/nat44.rst:713 8ff3f8957b604941a0b6badb6e319b8c -msgid "Testing and Validation" -msgstr "" - -#: ../../configuration/nat/nat44.rst:715 9f835037c2d841eeab59fa85e714dd4a -msgid "" -"If you've completed all the above steps you no doubt want to see if it's all" -" working." -msgstr "" - -#: ../../configuration/nat/nat44.rst:718 7581fbb9bcd040b5853654740d01f752 -msgid "Start by checking for IPSec SAs (Security Associations) with:" -msgstr "" - -#: ../../configuration/nat/nat44.rst:733 4d4ceca9320b4ec2989ffe456b4fd0a9 -msgid "" -"That looks good - we defined 2 tunnels and they're both up and running." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat66.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat66.po deleted file mode 100644 index 5e624dd5..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/nat/nat66.po +++ /dev/null @@ -1,173 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/nat/nat66.rst:5 ca934164b89d4c82a409d55c28fd8dd6 -msgid "NAT66(NPTv6)" -msgstr "" - -#: ../../configuration/nat/nat66.rst:7 4e2414905e4e4b06a6e46245d87314f0 -msgid "" -":abbr:`NPTv6 (IPv6-to-IPv6 Network Prefix Translation)` is an address " -"translation technology basedon IPv6 networks, used to convert an IPv6 " -"address prefix in an IPv6 message into another IPv6address prefix. We call " -"this address translation method NAT66. Devices that support the NAT66 " -"function are called NAT66 devices, which can provide NAT66 source and " -"destination address translation functions." -msgstr "" - -#: ../../configuration/nat/nat66.rst:15 5e46174927104a45bb1ad2917b27dae5 -msgid "Overview" -msgstr "" - -#: ../../configuration/nat/nat66.rst:18 fdece6d28cd64afdbea2a2461da0b911 -msgid "Different NAT Types" -msgstr "" - -#: ../../configuration/nat/nat66.rst:23 37b55989de1a4fda8155c0b0173e8416 -msgid "SNAT66" -msgstr "" - -#: ../../configuration/nat/nat66.rst:25 d7f452fa32164072bd1be883e919847c -msgid "" -":abbr:`SNPTv6 (Source IPv6-to-IPv6 Network Prefix Translation)` The " -"conversion function is mainly used in the following scenarios:" -msgstr "" - -#: ../../configuration/nat/nat66.rst:28 dc9b6db9a1294771a93cd9585e068bdf -msgid "" -"A single internal network and external network. Use the NAT66 device to " -"connect a single internal network and public network, and the hosts in the " -"internal network use IPv6 address prefixes that only support routing within " -"the local range. When a host in the internal network accesses the external " -"network, the source IPv6 address prefix in the message will be converted " -"into a global unicast IPv6 address prefix by the NAT66 device." -msgstr "" - -#: ../../configuration/nat/nat66.rst:35 aa97d8707d044f35b12f70843edaf49e -msgid "" -"Redundancy and load sharing. There are multiple NAT66 devices at the edge of" -" an IPv6 network to another IPv6 network. The path through the NAT66 device " -"to another IPv6 network forms an equivalent route, and traffic can be load-" -"shared on these NAT66 devices. In this case, you can configure the same " -"source address translation rules on these NAT66 devices, so that any NAT66 " -"device can handle IPv6 traffic between different sites." -msgstr "" - -#: ../../configuration/nat/nat66.rst:42 19c552356f874c6e9a56980ef5bca864 -msgid "" -"Multi-homed. In a multi-homed network environment, the NAT66 device connects" -" to an internal network and simultaneously connects to different external " -"networks. Address translation can be configured on each external network " -"side interface of the NAT66 device to convert the same internal network " -"address into different external network addresses, and realize the mapping " -"of the same internal address to multiple external addresses." -msgstr "" - -#: ../../configuration/nat/nat66.rst:53 951f59b27eb942ccb4f7245775b90c04 -msgid "DNAT66" -msgstr "" - -#: ../../configuration/nat/nat66.rst:55 6b91ae30d11042269e93b9d1bd40f099 -msgid "" -"The :abbr:`DNPTv6 (Destination IPv6-to-IPv6 Network Prefix Translation)` " -"destination address translation function is used in scenarios where the " -"server in the internal network provides services to the external network, " -"such as providing Web services or FTP services to the external network. By " -"configuring the mapping relationship between the internal server address and" -" the external network address on the external network side interface of the " -"NAT66 device, external network users can access the internal network server " -"through the designated external network address." -msgstr "" - -#: ../../configuration/nat/nat66.rst:66 354d68259cab482096cbf018e91dbbad -msgid "Prefix Conversion" -msgstr "" - -#: ../../configuration/nat/nat66.rst:69 0a61dbaeac704e96a17021863013b36b -msgid "Source Prefix" -msgstr "" - -#: ../../configuration/nat/nat66.rst:71 e50390dc638a477c9312fbfc79065e37 -msgid "" -"Every SNAT66 rule has a translation command defined. The prefix defined for " -"the translation is the prefix used when the address information in a packet " -"is replaced.、" -msgstr "" - -#: ../../configuration/nat/nat66.rst:75 2987cee585564527ab449678ea7b8b1a -msgid "" -"The :ref:`source-nat66` rule replaces the source address of the packet and " -"calculates the converted address using the prefix specified in the rule." -msgstr "" - -#: ../../configuration/nat/nat66.rst:78 ../../configuration/nat/nat66.rst:96 -#: 3445a1dea2244401a1d2521e4f6d1f66 91dca61fac3f4db1ad685016b5304b7c -msgid "Example:" -msgstr "" - -#: ../../configuration/nat/nat66.rst:80 cd858083b5044f44a9777d5988124c87 -msgid "" -"Convert the address prefix of a single `fc01::/64` network to `fc00::/64`" -msgstr "" - -#: ../../configuration/nat/nat66.rst:81 da347f39e1fd41d6a043cf92b580aed7 -msgid "Output from `eth0` network interface" -msgstr "" - -#: ../../configuration/nat/nat66.rst:90 7ae1af8cd3f244d5b0cf4c68dd919362 -msgid "Destination Prefix" -msgstr "" - -#: ../../configuration/nat/nat66.rst:92 84d1d27cd0144f32b5190cb5dd7ce1ea -msgid "" -"For the :ref:`destination-nat66` rule, the destination address of the packet" -" isreplaced by the address calculated from the specified address or prefix " -"in the `translation address` command" -msgstr "" - -#: ../../configuration/nat/nat66.rst:98 442f390a7e754e8fa514eb1b354c835e -msgid "" -"Convert the address prefix of a single `fc00::/64` network to `fc01::/64`" -msgstr "" - -#: ../../configuration/nat/nat66.rst:100 c958a94c8d8543f2aaae440f4c3ef62a -msgid "Input from `eth0` network interface" -msgstr "" - -#: ../../configuration/nat/nat66.rst:109 472507579cef4bdf85268aedcfcbf1e7 -msgid "Configuration Examples" -msgstr "" - -#: ../../configuration/nat/nat66.rst:111 68e29a1099e34939a93f53c42c5c0ff3 -msgid "" -"Use the following topology to build a nat66 based isolated network between " -"internal and external networks (dynamic prefix is not supported):" -msgstr "" - -#: ../../configuration/nat/nat66.rstNone 9579e46e32b84f0ba07c75d9747cf078 -msgid "VyOS NAT66 Simple Configure" -msgstr "" - -#: ../../configuration/nat/nat66.rst:118 3ec19efd1e7a4d60934658d55d5cb28d -msgid "R1:" -msgstr "" - -#: ../../configuration/nat/nat66.rst:131 ac9bbe06804e4f588d25df97dd0ce32d -msgid "R2:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/pki/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/pki/index.po deleted file mode 100644 index f34a457e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/pki/index.po +++ /dev/null @@ -1,344 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../_include/need_improvement.txt:11 d0332a79660c4150afb4402f262900a7 -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 9dfc4c15b7e44e8984dcdad15c47b498 -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/pki/index.rst:7 58089a5ee58b4324926b8bd24b5ff911 -msgid "PKI" -msgstr "" - -#: ../../configuration/pki/index.rst:9 d0b85cf4dfbb4d2ba51e707a187dc818 -msgid "" -"VyOS 1.4 changed the way in how encrytion keys or certificates are stored on" -" the system. In the pre VyOS 1.4 era, certificates got stored under /config " -"and every service referenced a file. That made copying a running " -"configuration from system A to system B a bit harder, as you had to copy the" -" files and their permissions by hand." -msgstr "" - -#: ../../configuration/pki/index.rst:15 b0a7c64a5bf34aab8950b7298b7d92f1 -msgid "" -":vytask:`T3642` describes a new CLI subsystem that serves as a \"certstore\"" -" to all services requiring any kind of encryption key(s). In short, public " -"and private certificates are now stored in PKCS#8 format in the regular VyOS" -" CLI. Keys can now be added, edited, and deleted using the regular " -"set/edit/delete CLI commands." -msgstr "" - -#: ../../configuration/pki/index.rst:21 eef1d7f0ff6d4767917d06224fc7728e -msgid "" -"VyOS not only can now manage certificates issued by 3rd party Certificate " -"Authorities, it can also act as a CA on its own. You can create your own " -"root CA and sign keys with it by making use of some simple op-mode commands." -msgstr "" - -#: ../../configuration/pki/index.rst:25 025670e87e634f08b5a9f41a2af37e18 -msgid "" -"Don't be afraid that you need to re-do your configuration. Key " -"transformation is handled, as always, by our migration scripts, so this will" -" be a smooth transition for you!" -msgstr "" - -#: ../../configuration/pki/index.rst:30 d0f578b0203e438290794df00b28fe61 -msgid "Key Generation" -msgstr "" - -#: ../../configuration/pki/index.rst:33 e299cfd97020429b926a835ed10e0bea -msgid "Certificate Authority (CA)" -msgstr "" - -#: ../../configuration/pki/index.rst:35 32f5f0736d0c441dbf6795d6d8d54e31 -msgid "" -"VyOS now also has the ability to create CAs, keys, Diffie-Hellman and other " -"keypairs from an easy to access operational level command." -msgstr "" - -#: ../../configuration/pki/index.rst:40 ../../configuration/pki/index.rst:45 -#: b9b023d4836841338b13189b8d0b7a79 2af4158dc4d948a8ae034b6eaf7e21d8 -msgid "" -"Create a new :abbr:`CA (Certificate Authority)` and output the CAs public " -"and private key on the console." -msgstr "" - -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/pki_cli_import_help.txt:1 -#: ../../configuration/pki/index.rst:144 ../../configuration/pki/index.rst:159 -#: a1e969071930495898a24711d52e6055 ef94468c16044b00994bcb18945ca541 -#: 422af7562b05460f876d46e4319dd824 a2f9760b5a6e4ee881fc30e2df681724 -#: cdff35cdb25940959648c2cfffaa193a e9e5c94e0cc344c2a3003441d81a10f0 -#: 72de69f6ab6c48c8ba0c207e1f1e0b56 a3ed3faad7ae47c8a7071ecd7628a399 -#: 18e7c4de5d1e46989c8704cc6b9ea47c -msgid "" -"In addition to the command above, the output is in a format which can be " -"used to directly import the key into the VyOS CLI by simply copy-pasting the" -" output from op-mode into configuration mode." -msgstr "" - -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: ../../configuration/pki/pki_cli_import_help.txt:5 -#: 7bd63cdab2b643878223df8ddc67c134 9b40e981ee934348918897f4d35e5d5b -#: 052785e5c3d54a4ca20718f3ee0c003a 53cfdafe80b94c6fb8ca182804c93a4c -#: b6bbb6c735cf44fa956e361f74a1b9d3 2d2b16d33cc041b08134705823af343d -#: 45f9ec5324e54cac972831aa3aca8e15 -msgid "" -"``name`` is used for the VyOS CLI command to identify this key. This key " -"``name`` is then used in the CLI configuration to reference the key " -"instance." -msgstr "" - -#: ../../configuration/pki/index.rst:52 0edadd6197464d729bd6d9594f8c9ee4 -msgid "" -"Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it " -"using the private key referenced by `ca-name`." -msgstr "" - -#: ../../configuration/pki/index.rst:57 e5a6fb74f0e54295858157bfa9671ad5 -msgid "" -"Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it " -"using the private key referenced by `name`." -msgstr "" - -#: ../../configuration/pki/index.rst:63 de9390e7a30c46c5b9a9e0e1f5d359ad -msgid "Certificates" -msgstr "" - -#: ../../configuration/pki/index.rst:67 ../../configuration/pki/index.rst:71 -#: 9b9586ce09d94e03ab5f4a7ed4436a69 84c9f6fdff794b11ad02cd8fbb45c617 -msgid "" -"Create a new public/private keypair and output the certificate on the " -"console." -msgstr "" - -#: ../../configuration/pki/index.rst:77 ../../configuration/pki/index.rst:82 -#: 9b39d3bcff154f7291dcb77f8d7d215a 176a891d00084bb3bbdb222edfb4713c -msgid "" -"Create a new self-signed certificate. The public/private is then shown on " -"the console." -msgstr "" - -#: ../../configuration/pki/index.rst:89 ../../configuration/pki/index.rst:94 -#: adc233cfead6434c90bd93c120881184 93f69a80dbfe4db58d2458c3e7ea6d96 -msgid "" -"Create a new public/private keypair which is signed by the CA referenced by " -"`ca-name`. The signed certificate is then output to the console." -msgstr "" - -#: ../../configuration/pki/index.rst:100 c7409b34fbdc42768f0f9e14abfad57c -msgid "Diffie-Hellman parameters" -msgstr "" - -#: ../../configuration/pki/index.rst:104 ../../configuration/pki/index.rst:111 -#: 4c326571fa8b4cc5b19fd035942f687f 60a0519f0f4640e4a436c118138364ac -msgid "" -"Generate a new set of :abbr:`DH (Diffie-Hellman)` parameters. The key size " -"is requested by the CLI and defaults to 2048 bit." -msgstr "" - -#: ../../configuration/pki/index.rst:107 872bd715596f4d2487c85ab89e3c7b20 -msgid "The generated parameters are then output to the console." -msgstr "" - -#: ../../configuration/pki/index.rst:117 b7068f0a5c0044d2b84586de95a352fa -msgid "OpenVPN" -msgstr "" - -#: ../../configuration/pki/index.rst:121 ../../configuration/pki/index.rst:126 -#: cb00c6ce7a224e3a97b5c9d0e1cbb161 b209ff7be86646fb924d53d9cd8dbc6f -msgid "" -"Genearate a new OpenVPN shared secret. The generated secred is the output to" -" the console." -msgstr "" - -#: ../../configuration/pki/index.rst:132 c96236236705496793eb9c00fa34236f -msgid "WireGuard" -msgstr "" - -#: ../../configuration/pki/index.rst:136 ../../configuration/pki/index.rst:141 -#: 7f5e6c564f214a159f1dba0cd285051f 50afb755802a42c880815f69faa88234 -msgid "" -"Generate a new WireGuard public/private key portion and output the result to" -" the console." -msgstr "" - -#: ../../configuration/pki/index.rst:148 47d34653b49740ed8dbbcd853b7e9128 -msgid "" -"``interface`` is used for the VyOS CLI command to identify the WireGuard " -"interface where this private key is to be used." -msgstr "" - -#: ../../configuration/pki/index.rst:153 ../../configuration/pki/index.rst:157 -#: 5a74fd4cd0c445ef9d092cb055a74587 82eb01b20bac49df927a397f1fcd5fd1 -msgid "Generate a WireGuard pre-shared secret used for peers to communicate." -msgstr "" - -#: ../../configuration/pki/index.rst:163 9d3f174f86564528ab1eed7b9181e228 -msgid "" -"``peer`` is used for the VyOS CLI command to identify the WireGuard peer " -"where this secred is to be used." -msgstr "" - -#: ../../configuration/pki/index.rst:167 516304c049c346d9a6a1dccbdb8874d2 -msgid "Key usage (CLI)" -msgstr "" - -#: ../../configuration/pki/index.rst:170 9bedb909ae1a45a0a13129835f7398e5 -msgid "CA (Certificate Authority)" -msgstr "" - -#: ../../configuration/pki/index.rst:174 ff3e925e98474928a7d17726a39147cc -msgid "Add the public CA certificate for the CA named `name` to the VyOS CLI." -msgstr "" - -#: ../../configuration/pki/index.rst:176 ../../configuration/pki/index.rst:219 -#: 911b233ac4814ad1b2283c1988ab7c1d e9ce9e77d16d4017a52caedd19eee31d -msgid "" -"When loading the certificate you need to manually strip the ``-----BEGIN " -"CERTIFICATE-----`` and ``-----END CERTIFICATE-----`` tags. Also, the " -"certificate/key needs to be presented in a single line without line breaks " -"(``\\n``), this can be done using the following shell command:" -msgstr "" - -#: ../../configuration/pki/index.rst:181 aa32708878c146c0b88e466cd71ed744 -msgid "``$ tail -n +2 ca.pem | head -n -1 | tr -d '\\n'``" -msgstr "" - -#: ../../configuration/pki/index.rst:185 0da7c11604174e6daf3d753dea1896ce -msgid "Certificate revocation list in PEM format." -msgstr "" - -#: ../../configuration/pki/index.rst:189 286b10ab627e4d2392bdd6ac4ff59354 -msgid "A human readable description what this CA is about." -msgstr "" - -#: ../../configuration/pki/index.rst:193 4d9267b61e82406eb4101fe18343f364 -msgid "" -"Add the CAs private key to the VyOS CLI. This should never leave the system," -" and is only required if you use VyOS as your certificate generator as " -"mentioned above." -msgstr "" - -#: ../../configuration/pki/index.rst:197 ../../configuration/pki/index.rst:235 -#: 23d3719f7be54a4f93ec3b35b14b11f3 e16474413c02441ea680419546196aea -msgid "" -"When loading the certificate you need to manually strip the ``-----BEGIN " -"KEY-----`` and ``-----END KEY-----`` tags. Also, the certificate/key needs " -"to be presented in a single line without line breaks (``\\n``), this can be " -"done using the following shell command:" -msgstr "" - -#: ../../configuration/pki/index.rst:202 34119b41afde4ce1a4336ebf083b64d1 -msgid "``$ tail -n +2 ca.key | head -n -1 | tr -d '\\n'``" -msgstr "" - -#: ../../configuration/pki/index.rst:206 5983b11095fe4c849a0f0c1eb2ba4acd -msgid "" -"Mark the CAs private key as password protected. User is asked for the " -"password when the key is referenced." -msgstr "" - -#: ../../configuration/pki/index.rst:210 4d3078c5c52b4beb85581847a788bb79 -msgid "Server Certificate" -msgstr "" - -#: ../../configuration/pki/index.rst:212 942b65454b1b42188547e9b6d01a45a3 -msgid "" -"After we have imported the CA certificate(s) we can now import and add " -"certificates used by services on this router." -msgstr "" - -#: ../../configuration/pki/index.rst:217 3adc1d39ccb24bc38b81bee75b32689c -msgid "" -"Add public key portion for the certificate named `name` to the VyOS CLI." -msgstr "" - -#: ../../configuration/pki/index.rst:224 5a4ea3340cce4f4fb04f0bac6d190e63 -msgid "``$ tail -n +2 cert.pem | head -n -1 | tr -d '\\n'``" -msgstr "" - -#: ../../configuration/pki/index.rst:228 075178c064634b7287bb18836609d0f2 -msgid "A human readable description what this certificate is about." -msgstr "" - -#: ../../configuration/pki/index.rst:232 f5ea7285a18945da81673688042c4cd4 -msgid "" -"Add the private key portion of this certificate to the CLI. This should " -"never leave the system as it is used to decrypt the data." -msgstr "" - -#: ../../configuration/pki/index.rst:240 9f9d6db54e72405da82063565cea2cf7 -msgid "``$ tail -n +2 cert.key | head -n -1 | tr -d '\\n'``" -msgstr "" - -#: ../../configuration/pki/index.rst:244 84a9bd12ef7a45d480c65a1ac527d824 -msgid "" -"Mark the private key as password protected. User is asked for the password " -"when the key is referenced." -msgstr "" - -#: ../../configuration/pki/index.rst:249 22b30725d2e24cc383090337d22521f3 -msgid "If CA is present, this certificate will be included in generated CRLs" -msgstr "" - -#: ../../configuration/pki/index.rst:252 159617d83a264c549e09e7309e8618b4 -msgid "Operation" -msgstr "" - -#: ../../configuration/pki/index.rst:254 be9c4115484a42e997e0daa52057c718 -msgid "" -"VyOS operational mode commands are not only available for generating keys " -"but also to display them." -msgstr "" - -#: ../../configuration/pki/index.rst:259 f9e5cb6847b247cdb680b6179bc56873 -msgid "" -"Show a list of installed :abbr:`CA (Certificate Authority)` certificates." -msgstr "" - -#: ../../configuration/pki/index.rst:273 6a0e9fe0f16942168fdcbac485e8a90d -msgid "Show only information for specified Certificate Authority." -msgstr "" - -#: ../../configuration/pki/index.rst:277 8eaff6ce373241cb83fca30ec6ad9651 -msgid "Show a list of installed certificates" -msgstr "" - -#: ../../configuration/pki/index.rst:290 3ae771ed47f84509882ae5fb4eb9e2ce -msgid "Show only information for specified certificate." -msgstr "" - -#: ../../configuration/pki/index.rst:294 34c59f8cae974d68a00f0ae556403c5e -msgid "Show a list of installed :abbr:`CRLs (Certificate Revocation List)`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/access-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/access-list.po deleted file mode 100644 index 23c2d1bd..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/access-list.po +++ /dev/null @@ -1,142 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/access-list.rst:3 -#: e479568cc6894f98a1efae90378d3500 -msgid "Access List Policy" -msgstr "" - -#: ../../configuration/policy/access-list.rst:5 -#: 3eb6473f2ed54c31a3c816a412d84f68 -msgid "" -"Filtering is used for both input and output of the routing information. Once" -" filtering is defined, it can be applied in any direction. VyOS makes " -"filtering possible using acls and prefix lists." -msgstr "" - -#: ../../configuration/policy/access-list.rst:9 -#: e33c2de462be4f539c61d24a4a41b524 -msgid "Basic filtering can be done using access-list and access-list6." -msgstr "" - -#: ../../configuration/policy/access-list.rst:13 -#: 08f3d34471c447e186d35551229b9e7b -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/access-list.rst:16 -#: 9f4ed8d952854a0f813f3ef7e4490396 -msgid "Access Lists" -msgstr "" - -#: ../../configuration/policy/access-list.rst:20 -#: a709dd7898554ee5847187e481419baa -msgid "" -"This command creates the new access list policy, where <acl_number> must be " -"a number from 1 to 2699." -msgstr "" - -#: ../../configuration/policy/access-list.rst:25 -#: c7fb74648417449682ce300ef3846c3a -msgid "Set description for the access list." -msgstr "" - -#: ../../configuration/policy/access-list.rst:30 -#: 568339af5e0143199dbd5ab6711e91ef -msgid "" -"This command creates a new rule in the access list and defines an action." -msgstr "" - -#: ../../configuration/policy/access-list.rst:35 -#: bcf37d6edf8f47118ea1543410674273 -msgid "" -"This command defines matching parameters for access list rule. Matching " -"criteria could be applied to destination or source parameters:" -msgstr "" - -#: ../../configuration/policy/access-list.rst:38 -#: 87caf8ea2d08472a958cf950f5529ea1 -msgid "any: any IP address to match." -msgstr "" - -#: ../../configuration/policy/access-list.rst:39 -#: 806627a8147a42ac9aa5bdd4d1e91093 -msgid "host: single host IP address to match." -msgstr "" - -#: ../../configuration/policy/access-list.rst:40 -#: 9c5e969c7a5244ab89ffd55212de0b3b -msgid "inverse-match: network/netmask to match (requires network be defined)." -msgstr "" - -#: ../../configuration/policy/access-list.rst:41 -#: f130437d04e24bfd97ce12460d53073f -msgid "network: network/netmask to match (requires inverse-match be defined)." -msgstr "" - -#: ../../configuration/policy/access-list.rst:44 -#: 74fbd8b4573645bdb98daaa8106dd902 -msgid "IPv6 Access List" -msgstr "" - -#: ../../configuration/policy/access-list.rst:46 -#: 84feff9b902d494b865574fcbff707e7 -msgid "Basic filtering could also be applied to IPv6 traffic." -msgstr "" - -#: ../../configuration/policy/access-list.rst:50 -#: b19e9022123348cc8a50e7e7bc471d71 -msgid "This command creates the new IPv6 access list, identified by <text>" -msgstr "" - -#: ../../configuration/policy/access-list.rst:54 -#: 9e0689e76b32438dbf550a3bf88823b1 -msgid "Set description for the IPv6 access list." -msgstr "" - -#: ../../configuration/policy/access-list.rst:58 -#: 1b2a549eeaba430e9be0268ce26413a3 -msgid "" -"This command creates a new rule in the IPv6 access list and defines an " -"action." -msgstr "" - -#: ../../configuration/policy/access-list.rst:64 -#: faac3e4b9abb42c8bfe577c070671be9 -msgid "" -"This command defines matching parameters for IPv6 access list rule. Matching" -" criteria could be applied to source parameters:" -msgstr "" - -#: ../../configuration/policy/access-list.rst:67 -#: 186a9394be3f4dcd88da16bd60370dc4 -msgid "any: any IPv6 address to match." -msgstr "" - -#: ../../configuration/policy/access-list.rst:68 -#: 10229d7a7c664e3888f27c9e67eac897 -msgid "exact-match: exact match of the network prefixes." -msgstr "" - -#: ../../configuration/policy/access-list.rst:69 -#: 788b92b7aecd45abb41a8cea35ccf21c -msgid "" -"network: network/netmask to match (requires inverse-match be defined) BUG, " -"NO invert-match option in access-list6" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/as-path-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/as-path-list.po deleted file mode 100644 index 0c35782b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/as-path-list.po +++ /dev/null @@ -1,66 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/as-path-list.rst:3 -#: 36f668e2a2294f829c13016096e01cf3 -msgid "BGP - AS Path Policy" -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:5 -#: 4c64ea2860f6416abec78bd394190bb2 -msgid "" -"VyOS provides policies commands exclusively for BGP traffic filtering and " -"manipulation: **as-path-list** is one of them." -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:10 -#: 2c03d0fbe35c42deab0dcf3f58b499c0 -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:13 -#: 9e713da3bf3e4838a5d49410c0ee3b50 -msgid "policy as-path-list" -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:17 -#: ccec9bad9987459d8bdc3a51c2590936 -msgid "Create as-path-policy identified by name <text>." -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:21 -#: b35f646a389b46f4bf5305dddc969783 -msgid "Set description for as-path-list policy." -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:25 -#: 9fa6662dee864acfa389ff0869361529 -msgid "Set action to take on entries matching this rule." -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:29 -#: 1e58538f91694b799c5b365343e8d3b7 -msgid "Set description for rule." -msgstr "" - -#: ../../configuration/policy/as-path-list.rst:33 -#: 3a0bf49be6184060b30148c89f64a127 -msgid "" -"Regular expression to match against an AS path. For example \"64501 64502\"." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/community-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/community-list.po deleted file mode 100644 index 5087b46f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/community-list.po +++ /dev/null @@ -1,65 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/community-list.rst:3 -#: 99faa93400034781812a3c7e51406eb2 -msgid "BGP - Community List" -msgstr "" - -#: ../../configuration/policy/community-list.rst:5 -#: 4e39feb0c06e4ebf827fd77714776680 -msgid "" -"VyOS provides policies commands exclusively for BGP traffic filtering and " -"manipulation: **community-list** is one of them." -msgstr "" - -#: ../../configuration/policy/community-list.rst:10 -#: bc29289230ce49008e7e60343b4ecdcb -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/community-list.rst:13 -#: 35093ecf03b04987a9933fdc5111ddce -msgid "policy community-list" -msgstr "" - -#: ../../configuration/policy/community-list.rst:17 -#: f015388656fb490b814d3dd52d0940b5 -msgid "Creat community-list policy identified by name <text>." -msgstr "" - -#: ../../configuration/policy/community-list.rst:21 -#: b7b5e959d76e4d18bcc3f477087ec3bb -msgid "Set description for community-list policy." -msgstr "" - -#: ../../configuration/policy/community-list.rst:26 -#: 8e150776ee1a4c078a1d8f8536fe9f80 -msgid "Set action to take on entries matching this rule." -msgstr "" - -#: ../../configuration/policy/community-list.rst:30 -#: cbce67720e674843aba80de00dd91446 -msgid "Set description for rule." -msgstr "" - -#: ../../configuration/policy/community-list.rst:35 -#: 7fdeda325a9a42b69ce5b9d468afadde -msgid "Regular expression to match against a community-list." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/examples.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/examples.po deleted file mode 100644 index e4f9cc21..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/examples.po +++ /dev/null @@ -1,188 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/examples.rst:3 9e55f6ad75a24bcba4b441264559e633 -msgid "BGP Example" -msgstr "" - -#: ../../configuration/policy/examples.rst:5 10034e88d81f49989271f9282aa4d8a8 -msgid "**Policy definition:**" -msgstr "" - -#: ../../configuration/policy/examples.rst:18 ee93fa0f387b429ab3f3e4876822eb16 -msgid "" -"Using 'soft-reconfiguration' we get the policy update without bouncing the " -"neighbor." -msgstr "" - -#: ../../configuration/policy/examples.rst:21 e163f255b4fd4113bcf2a9c5f9be5e2d -msgid "**Routes learned before routing policy applied:**" -msgstr "" - -#: ../../configuration/policy/examples.rst:36 d3295b12ba8440d3bdee51e32060e34f -msgid "**Routes learned after routing policy applied:**" -msgstr "" - -#: ../../configuration/policy/examples.rst:52 237c690d313c4f2ba372efaf3fbe74bf -msgid "You now see the longer AS path." -msgstr "" - -#: ../../configuration/policy/examples.rst:56 e92e85398fdf4b49a01a4f22e36b2abe -msgid "Transparent Proxy" -msgstr "" - -#: ../../configuration/policy/examples.rst:58 2077c9ee3d244b7684ad910ce0fd49cb -msgid "" -"The following example will show how VyOS can be used to redirect web traffic" -" to an external transparent proxy:" -msgstr "" - -#: ../../configuration/policy/examples.rst:67 96b8b9a9f4d4473c965286c1f33816a0 -msgid "" -"This creates a route policy called FILTER-WEB with one rule to set the " -"routing table for matching traffic (TCP port 80) to table ID 100 instead of " -"the default routing table." -msgstr "" - -#: ../../configuration/policy/examples.rst:71 eff8c2f21f7c495a9e2bb91b2b9878da -msgid "" -"To create routing table 100 and add a new default gateway to be used by " -"traffic matching our route policy:" -msgstr "" - -#: ../../configuration/policy/examples.rst:78 37739e639d1041ad8c803f3f25fd1810 -msgid "" -"This can be confirmed using the ``show ip route table 100`` operational " -"command." -msgstr "" - -#: ../../configuration/policy/examples.rst:81 5ad4e670582041db8678bac64a470622 -msgid "" -"Finally, to apply the policy route to ingress traffic on our LAN interface, " -"we use:" -msgstr "" - -#: ../../configuration/policy/examples.rst:90 0cae56ecd4b24377b9af0e0bc8a77b3a -msgid "Multiple Uplinks" -msgstr "" - -#: ../../configuration/policy/examples.rst:92 253b0a5e11e840d399c490ffca8c0a2b -msgid "" -"VyOS Policy-Based Routing (PBR) works by matching source IP address ranges " -"and forwarding the traffic using different routing tables." -msgstr "" - -#: ../../configuration/policy/examples.rst:95 42a14c329d224477908507c501703c12 -msgid "Routing tables that will be used in this example are:" -msgstr "" - -#: ../../configuration/policy/examples.rst:97 3d093a961fbb44a1938479e6cff1dda8 -msgid "``table 10`` Routing table used for VLAN 10 (192.168.188.0/24)" -msgstr "" - -#: ../../configuration/policy/examples.rst:98 9712766ea94a4b1eb0a48effcb60436c -msgid "``table 11`` Routing table used for VLAN 11 (192.168.189.0/24)" -msgstr "" - -#: ../../configuration/policy/examples.rst:99 7ab026dba85f41cdbc1ba0db436a850c -msgid "" -"``main`` Routing table used by VyOS and other interfaces not participating " -"in PBR" -msgstr "" - -#: ../../configuration/policy/examples.rst:106 -#: 8f2646189a294da580e14d0bb6c8da1b -msgid "PBR multiple uplinks" -msgstr "" - -#: ../../configuration/policy/examples.rst:106 -#: 3a38f3e12c9d4797abbbd27a096808b9 -msgid "" -"Policy-Based Routing with multiple ISP uplinks (source " -"./draw.io/pbr_example_1.drawio)" -msgstr "" - -#: ../../configuration/policy/examples.rst:109 -#: b4a4da7aed5c44c1899c1e6a16b94fbc -msgid "Add default routes for routing ``table 10`` and ``table 11``" -msgstr "" - -#: ../../configuration/policy/examples.rst:116 -#: 306522d6ff8141dfbd7d21e0f99a0827 -msgid "Add policy route matching VLAN source addresses" -msgstr "" - -#: ../../configuration/policy/examples.rst:128 -#: 8a47de500c564a928af6e813543fd679 -msgid "Apply routing policy to **inbound** direction of out VLAN interfaces" -msgstr "" - -#: ../../configuration/policy/examples.rst:136 -#: 72234245462c49f7bed17c72f90c0030 -msgid "" -"**OPTIONAL:** Exclude Inter-VLAN traffic (between VLAN10 and VLAN11) from " -"PBR" -msgstr "" - -#: ../../configuration/policy/examples.rst:149 -#: 56cc24934d1240f985376d3171292e7a -msgid "" -"These commands allow the VLAN10 and VLAN11 hosts to communicate with each " -"other using the main routing table." -msgstr "" - -#: ../../configuration/policy/examples.rst:153 -#: 8a697645d6704106ab22fddd87629afd -msgid "Local route" -msgstr "" - -#: ../../configuration/policy/examples.rst:155 -#: 141d084f705c4347b110285e00baf490 -msgid "" -"The following example allows VyOS to use :abbr:`PBR (Policy-Based Routing)` " -"for traffic, which originated from the router itself. That solution for " -"multiple ISP's and VyOS router will respond from the same interface that the" -" packet was received. Also, it used, if we want that one VPN tunnel to be " -"through one provider, and the second through another." -msgstr "" - -#: ../../configuration/policy/examples.rst:161 -#: e6f1de3a0b0646c8bc0ff942ce523e7b -msgid "``203.0.113.254`` IP addreess on VyOS eth1 from ISP1" -msgstr "" - -#: ../../configuration/policy/examples.rst:162 -#: db0c4509ae90489fa53d6c2b9c8a0133 -msgid "``192.168.2.254`` IP addreess on VyOS eth2 from ISP2" -msgstr "" - -#: ../../configuration/policy/examples.rst:163 -#: f3bda5e8641f4f21945e71ce8e702e8e -msgid "``table 10`` Routing table used for ISP1" -msgstr "" - -#: ../../configuration/policy/examples.rst:164 -#: 1c888a1f93db4158a5bf86084729ad19 -msgid "``table 11`` Routing table used for ISP2" -msgstr "" - -#: ../../configuration/policy/examples.rst:176 -#: 7e71d4669a864c4789fa4b2544ca0f46 -msgid "Add multiple source IP in one rule with same priority" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/extcommunity-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/extcommunity-list.po deleted file mode 100644 index f6447d52..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/extcommunity-list.po +++ /dev/null @@ -1,82 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/extcommunity-list.rst:3 -#: 99df285e945b455aac74baeebdfa19b8 -msgid "BGP - Extended Community List" -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:5 -#: a78474bbedf74189be44930fff3cf440 -msgid "" -"VyOS provides policies commands exclusively for BGP traffic filtering and " -"manipulation: **extcommunity-list** is one of them." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:10 -#: fb55866a8e674419bfaf1d452f76da69 -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:13 -#: bac7e289b12a42f88b4943491bfcc21f -msgid "policy extcommunity-list" -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:17 -#: 85cd37c30b044ada853b46d283644265 -msgid "Creat extcommunity-list policy identified by name <text>." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:21 -#: 6a8eeb36e7984816b4cfdf11404cfdcc -msgid "Set description for extcommunity-list policy." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:26 -#: df6922df7a2f4e279f147cd45841fa34 -msgid "Set action to take on entries matching this rule." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:31 -#: c4b71253eef843cfae190abfbca3eee0 -msgid "Set description for rule." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:35 -#: c282f229ca1f4b1fb681af9e4ca4c258 -msgid "" -"Regular expression to match against an extended community list, where text " -"could be:" -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:38 -#: 0122cf06059748dcbb11ae8128739d88 -msgid "<aa:nn:nn>: Extended community list regular expression." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:39 -#: 260ea696362845449118b395771701c4 -msgid "<rt aa:nn:nn>: Route Target regular expression." -msgstr "" - -#: ../../configuration/policy/extcommunity-list.rst:40 -#: 02595e6d80324bb3ba5349a3abb6467a -msgid "<soo aa:nn:nn>: Site of Origin regular expression." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/index.po deleted file mode 100644 index d830b294..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/index.po +++ /dev/null @@ -1,86 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/index.rst:1 17f98f7caf94465491eab10595330f72 -msgid ":lastproofread:2021-07-12" -msgstr "" - -#: ../../_include/need_improvement.txt:11 83c778f38e2947abb7040b5c3dbf130f -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 c3a92eaa553b41f38ca2bb64795d451e -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/policy/index.rst:7 098008c6e2a344e7aeb4d03fd4b0a5f2 -msgid "Policy" -msgstr "" - -#: ../../configuration/policy/index.rst:9 4dad89f4b549474a9eb02657595da63c -msgid "" -"Policies are used for filtering and traffic management. With policies, " -"network administrators could filter and treat traffic according to their " -"needs." -msgstr "" - -#: ../../configuration/policy/index.rst:13 3d810a54116d4aafb3e2226b607b1925 -msgid "" -"There could be a wide range of routing policies. Some examples are listed " -"below:" -msgstr "" - -#: ../../configuration/policy/index.rst:16 bf7fe34299fb422a8754fba1ddc4066c -msgid "Filter traffic based on source/destination address." -msgstr "" - -#: ../../configuration/policy/index.rst:17 70e812e0943a4aa5b65cca2d215e8440 -msgid "Set some metric to routes learned from a particular neighbor." -msgstr "" - -#: ../../configuration/policy/index.rst:18 12e2e58b170a4865ac30ce259a00eff4 -msgid "" -"Set some attributes (like AS PATH or Community value) to advertised routes " -"to neighbors." -msgstr "" - -#: ../../configuration/policy/index.rst:20 f5fcd246e018486491e976df48e3fa80 -msgid "" -"Prefer a specific routing protocol routes over another routing protocol " -"running on the same router." -msgstr "" - -#: ../../configuration/policy/index.rst:23 ae1ee5062c6f4bacbe066dd705abf59f -msgid "" -"Policies, in VyOS, are implemented using FRR filtering and route maps. " -"Detailed information of FRR could be found in http://docs.frrouting.org/" -msgstr "" - -#: ../../configuration/policy/index.rst:28 a1d5b218b3634f95a7112b2cb610e5ce -msgid "Policy Sections" -msgstr "" - -#: ../../configuration/policy/index.rst:46 9b28c406e8e0409a85a724396ae31b1d -msgid "Examples" -msgstr "" - -#: ../../configuration/policy/index.rst:48 e3f737fbcc284fb69b30ee14ce1d6a23 -msgid "Examples of policies usage:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/large-community-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/large-community-list.po deleted file mode 100644 index 4e1ef088..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/large-community-list.po +++ /dev/null @@ -1,65 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/large-community-list.rst:3 -#: e3ebb86dd16b4b129721f5625b96ed7d -msgid "BGP - Large Community List" -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:5 -#: d464ef9bc8854a7b9ea2774bebca71e4 -msgid "" -"VyOS provides policies commands exclusively for BGP traffic filtering and " -"manipulation: **large-community-list** is one of them." -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:10 -#: b3552191def9491fa4f19ed9754e1a3c -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:13 -#: 631c60d44c1342088c4a5664e8bf2bb0 -msgid "policy large-community-list" -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:17 -#: 5b062cd118f244d1bc62febee094f896 -msgid "Creat large-community-list policy identified by name <text>." -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:21 -#: 1182e0e96f0b4ad6b91a9d1810fdb27c -msgid "Set description for large-community-list policy." -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:26 -#: ec96e0a86ee840739aa57dbfe0fcf0ac -msgid "Set action to take on entries matching this rule." -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:31 -#: 9c626939aa0144f7b4d5d8649a1ba4b6 -msgid "Set description for rule." -msgstr "" - -#: ../../configuration/policy/large-community-list.rst:36 -#: 247eacd4c7314c7ea9004bf5164b35ff -msgid "Regular expression to match against a large community list." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/local-route.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/local-route.po deleted file mode 100644 index f82fa9a8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/local-route.po +++ /dev/null @@ -1,67 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/local-route.rst:3 -#: 21c3fc85e567490986c42ebf6f54110a -msgid "Local Route Policy" -msgstr "" - -#: ../../configuration/policy/local-route.rst:5 -#: 92ef96f80f4e47bca2cc30669d5be010 -msgid "Policies for local traffic are defined in this section." -msgstr "" - -#: ../../configuration/policy/local-route.rst:9 -#: e2fc476c2a05442faf693988b4ffeb82 -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/local-route.rst:12 -#: d7ecfa9e58a442f998cd4a96b1b83802 -msgid "Local Route IPv4" -msgstr "" - -#: ../../configuration/policy/local-route.rst:16 -#: ../../configuration/policy/local-route.rst:35 -#: 1da519996f084f2d9d69aa99377bab7f de5dc035a805463296738f3200cc6fec -msgid "Set routing table to forward packet to." -msgstr "" - -#: ../../configuration/policy/local-route.rst:20 -#: ../../configuration/policy/local-route.rst:39 -#: 236093fdd50c4fb0bffc7c6bb8148253 a428322a127e4c8bbcc49ebe7988ef67 -msgid "Set source address or prefix to match." -msgstr "" - -#: ../../configuration/policy/local-route.rst:24 -#: ../../configuration/policy/local-route.rst:43 -#: 5d93a66089c14d08a38188239802b098 c38c5e3071564082be0e927f4bddf286 -msgid "Set destination address or prefix to match." -msgstr "" - -#: ../../configuration/policy/local-route.rst:28 -#: ../../configuration/policy/local-route.rst:47 -#: 2f3012242a81428db86dd84d9230f939 34b19715fec74d1d8c833a0af2c21d3b -msgid "Set inbound interface to match." -msgstr "" - -#: ../../configuration/policy/local-route.rst:31 -#: 56a1eee20b314aa0b5d773d392a9e2e6 -msgid "Local Route IPv6" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/prefix-list.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/prefix-list.po deleted file mode 100644 index d65c6ab5..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/prefix-list.po +++ /dev/null @@ -1,124 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/prefix-list.rst:3 -#: bf1d03a4d5904d4d8a154dffd11dc672 -msgid "Prefix List Policy" -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:5 -#: 5055b1b5d5124c229b6c43a397e65a10 -msgid "" -"Prefix lists provides the most powerful prefix based filtering mechanism. In" -" addition to access-list functionality, ip prefix-list has prefix length " -"range specification." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:9 -#: 6b5d1c856e98414594830bcd449d1289 -msgid "" -"If no ip prefix list is specified, it acts as permit. If ip prefix list is " -"defined, and no match is found, default deny is applied." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:12 -#: f21eb18ab90143dabea5810d68a43103 -msgid "Prefix filtering can be done using prefix-list and prefix-list6." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:16 -#: f8ee72dd7d4042dda9c9a1c055b3f183 -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:19 -#: 6c8d5ddf7dc0455fad8be8c0da75856f -msgid "Prefix Lists" -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:23 -#: cbac6314f17c463688c687b249b3615c -msgid "This command creates the new prefix-list policy, identified by <text>." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:27 -#: 3f03397cf2ab4755ac4faab65e640353 -msgid "Set description for the prefix-list policy." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:31 -#: b87af5dc5f5940808d2161737b1ca662 -msgid "" -"This command creates a new rule in the prefix-list and defines an action." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:35 -#: be668267871f40a4821120d166c03ff8 -msgid "Set description for rule in the prefix-list." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:39 -#: c14a905a54a04166b0fc4e48f12a91ff -msgid "Prefix to match against." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:43 -#: ../../configuration/policy/prefix-list.rst:76 -#: 7f4bad0d40bb45518763845fb7514232 b359bed7b3c94cfe9ca98a6fe553d340 -msgid "Netmask greater than length." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:47 -#: ../../configuration/policy/prefix-list.rst:80 -#: ad1253ea637740bdad2b76c90dd823ef 4f751525b0f94457856df83f196f6a8c -msgid "Netmask less than length" -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:50 -#: a71dce0da0e14cdf8586b5b255a8f35c -msgid "IPv6 Prefix Lists" -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:54 -#: 0ea46f3b7462457f878811cf8281a6ac -msgid "" -"This command creates the new IPv6 prefix-list policy, identified by <text>." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:58 -#: a2d8561db68a42ad9a21f78fde24e230 -msgid "Set description for the IPv6 prefix-list policy." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:62 -#: 1a6641f5eb2b4e40872ab0c020aeb01e -msgid "" -"This command creates a new rule in the IPv6 prefix-list and defines an " -"action." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:67 -#: 7af03ac7d8534053aee14cca7bd2734b -msgid "Set description for rule in IPv6 prefix-list." -msgstr "" - -#: ../../configuration/policy/prefix-list.rst:72 -#: 39fed85fecc942018c7a678c47ed1534 -msgid "IPv6 prefix." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route-map.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route-map.po deleted file mode 100644 index 0644f908..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route-map.po +++ /dev/null @@ -1,500 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/route-map.rst:3 ad8de71ad70c4767bd5091981a05210a -msgid "Route Map Policy" -msgstr "" - -#: ../../configuration/policy/route-map.rst:5 6e0fd980a96140b890a21739a1366bb8 -msgid "" -"Route map is a powerfull command, that gives network administrators a very " -"useful and flexible tool for traffic manipulation." -msgstr "" - -#: ../../configuration/policy/route-map.rst:10 -#: 3e125c07b2cb4904b47b517d29544a52 -msgid "Configuration" -msgstr "" - -#: ../../configuration/policy/route-map.rst:13 -#: 3a2e805f3ec9489593b5334d44e250a1 -msgid "Route Map" -msgstr "" - -#: ../../configuration/policy/route-map.rst:17 -#: 88361b9a7bcf461fb7bdb6dfd7c691f9 -msgid "This command creates a new route-map policy, identified by <text>." -msgstr "" - -#: ../../configuration/policy/route-map.rst:21 -#: c44abec868104cc1b490f976f92a0469 -msgid "Set description for the route-map policy." -msgstr "" - -#: ../../configuration/policy/route-map.rst:25 -#: ebb8a2368e0f4591a4cd72ea3ab4573d -msgid "Set action for the route-map policy." -msgstr "" - -#: ../../configuration/policy/route-map.rst:29 -#: ecfb876cbec9416393f3484638c831db -msgid "Call another route-map policy on match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:33 -#: 0ecf5b437d0342538a3e2cf47ff6dd63 -msgid "Jump to a different rule in this route-map on a match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:37 -#: 54fc7badf5ff415f889b2c1d96d6b03d -msgid "Set description for the rule in the route-map policy." -msgstr "" - -#: ../../configuration/policy/route-map.rst:41 -#: 77fbe45a41f64cd3ab67df8aaa7c78d5 -msgid "BGP as-path list to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:46 -#: a00cd57cd8f84ed48847f4f026486ef9 -msgid "BGP community-list to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:51 -#: cb86ad8630e3406fb4ecb2aefc3f0b53 -msgid "Set BGP community-list to exactly match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:56 -#: bba7c54fa9dd4f6396b5c0c40528a04c -msgid "BGP extended community to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:60 -#: 4d23f6cd8da44a77b1eb9a70cc221273 -msgid "First hop interface of a route to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:65 -#: 90823c49a8b447f4a8a6a96152ca606d -msgid "IP address of route to match, based on access-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:70 -#: 4e12498a04dc445287236d0ce86b9466 -msgid "IP address of route to match, based on prefix-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:75 -#: 56a05d3597f44fd48284a2222b5bd433 -msgid "" -"IP address of route to match, based on specified prefix-length. Note that " -"this can be used for kernel routes only. Do not apply to the routes of " -"dynamic routing protocols (e.g. BGP, RIP, OSFP), as this can lead to " -"unexpected results.." -msgstr "" - -#: ../../configuration/policy/route-map.rst:83 -#: 69f2811da6d143d08033ae7dce8b681e -msgid "IP next-hop of route to match, based on access-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:88 -#: 050d01a045ec42fb962a6fe309b8592d -msgid "IP next-hop of route to match, based on ip address." -msgstr "" - -#: ../../configuration/policy/route-map.rst:93 -#: 98715f0333784647b283d7f02a522bca -msgid "IP next-hop of route to match, based on prefix length." -msgstr "" - -#: ../../configuration/policy/route-map.rst:98 -#: 10637b9a96534fc784975c0de2b27f68 -msgid "IP next-hop of route to match, based on prefix-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:103 -#: 345508b0df1d4d3a800d89e7be2e9ca3 -msgid "IP next-hop of route to match, based on type." -msgstr "" - -#: ../../configuration/policy/route-map.rst:108 -#: 44898638091d44bab5bf8aea621627fe -msgid "IP route source of route to match, based on access-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:113 -#: af05939d992f4c12a1e206175f5b674b -msgid "IP route source of route to match, based on prefix-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:118 -#: 8e233903bb7a4804b9699ad807c1b64d -msgid "IPv6 address of route to match, based on IPv6 access-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:123 -#: 063a8e15bdb94c2fb94c99bdac3c3f60 -msgid "IPv6 address of route to match, based on IPv6 prefix-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:128 -#: 76a46f60854b4e2f8b903566e463209c -msgid "" -"IPv6 address of route to match, based on specified prefix-length. Note that " -"this can be used for kernel routes only. Do not apply to the routes of " -"dynamic routing protocols (e.g. BGP, RIP, OSFP), as this can lead to " -"unexpected results.." -msgstr "" - -#: ../../configuration/policy/route-map.rst:136 -#: 7ef33aa36217404dacdc0f11e8c61c01 -msgid "Nexthop IPv6 address to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:141 -#: 425cc1c3e5b84387ad0792fc680742fa -msgid "Match BGP large communities." -msgstr "" - -#: ../../configuration/policy/route-map.rst:146 -#: 553c19c921c04156b68dd114847db64b -msgid "Match local preference." -msgstr "" - -#: ../../configuration/policy/route-map.rst:150 -#: d2ca7f516f7f4c4185dc76a54a780c88 -msgid "Match route metric." -msgstr "" - -#: ../../configuration/policy/route-map.rst:155 -#: d35025115b3245f7be4de6e12e61fd61 -msgid "Boarder Gateway Protocol (BGP) origin code to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:159 -#: 5a9ddb8ac98d42ed8ddbc95e97872857 -msgid "Peer IP address to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:164 -#: 57058c1439b140368522c4e0b45d4ac0 -msgid "Match RPKI validation result." -msgstr "" - -#: ../../configuration/policy/route-map.rst:168 -#: 4fc418e9ae6f4f1da5798f42d843415a -msgid "Route tag to match." -msgstr "" - -#: ../../configuration/policy/route-map.rst:172 -#: a326612d4b5a43a9b2a0c919110841ef -msgid "Exit policy on match: go to rule <1-65535>" -msgstr "" - -#: ../../configuration/policy/route-map.rst:176 -#: fdbf494dcdaf4dbfaa143b1077522ac7 -msgid "Exit policy on match: go to next sequence number." -msgstr "" - -#: ../../configuration/policy/route-map.rst:181 -#: 491cd5f456c04edf8275b06cb5d70d64 -msgid "BGP aggregator attribute: AS number or IP address of an aggregation." -msgstr "" - -#: ../../configuration/policy/route-map.rst:186 -#: 5661cc0c3b6d4e3092a6131a9ba78f2e -msgid "Drop AS-NUMBER from the BGP AS path." -msgstr "" - -#: ../../configuration/policy/route-map.rst:191 -#: 697f2d4dd1b24584b04bbbc3d5099e84 -msgid "" -"Prepend the given string of AS numbers to the AS_PATH of the BGP path's " -"NLRI." -msgstr "" - -#: ../../configuration/policy/route-map.rst:196 -#: c115807127bf4dd986ae87b4b2d4f25d -msgid "Prepend the existing last AS number (the leftmost ASN) to the AS_PATH." -msgstr "" - -#: ../../configuration/policy/route-map.rst:200 -#: 598971dab68f4775b7d87ec19634d957 -msgid "BGP atomic aggregate attribute." -msgstr "" - -#: ../../configuration/policy/route-map.rst:205 -#: 7352b97327e64d53ab6053c9c782f96c -msgid "" -"Add or replace BGP community attribute in format ``<0-65535:0-65535>`` or " -"from well-known community list" -msgstr "" - -#: ../../configuration/policy/route-map.rst:210 -#: f9c54239101146629a5dfc06b2df0c08 -msgid "Delete all BGP communities" -msgstr "" - -#: ../../configuration/policy/route-map.rst:215 -#: eeeed011b3fc45aba070d4bec8209a8d -msgid "Delete BGP communities matching the community-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:220 -#: 01206d3e7e984539acb20edfa87c7ee2 -msgid "" -"Add or replace BGP large-community attribute in format " -"``<0-4294967295:0-4294967295:0-4294967295>``" -msgstr "" - -#: ../../configuration/policy/route-map.rst:225 -#: 16d21f6ca1b549a4ba6c8798ed1685c2 -msgid "Delete all BGP large-communities" -msgstr "" - -#: ../../configuration/policy/route-map.rst:230 -#: 97acc871eef54d3d9dd24a2a27c44692 -msgid "Delete BGP communities matching the large-community-list." -msgstr "" - -#: ../../configuration/policy/route-map.rst:235 -#: a7169b39be1649dbb1f0230f33380477 -msgid "Set extcommunity bandwidth" -msgstr "" - -#: ../../configuration/policy/route-map.rst:239 -#: f6f99edbaf094c278ca922346f5d22eb -msgid "The link bandwidth extended community is encoded as non-transitive" -msgstr "" - -#: ../../configuration/policy/route-map.rst:244 -#: c916624137bb4b78a2de526a34c14151 -msgid "" -"Set route target value in format ``<0-65535:0-4294967295>`` or " -"``<IP:0-65535>``." -msgstr "" - -#: ../../configuration/policy/route-map.rst:249 -#: 39da491c49684039a8d2769477d6bb74 -msgid "" -"Set site of origin value in format ``<0-65535:0-4294967295>`` or " -"``<IP:0-65535>``." -msgstr "" - -#: ../../configuration/policy/route-map.rst:253 -#: 72a38857eadb43ca86ae8c268288ccd6 -msgid "Clear all BGP extcommunities." -msgstr "" - -#: ../../configuration/policy/route-map.rst:257 -#: fd87fb7ad1134046beb08c88f4399183 -msgid "Locally significant administrative distance." -msgstr "" - -#: ../../configuration/policy/route-map.rst:263 -#: fe58cb11124c400b8f4a0cf2eb9512f2 -msgid "Nexthop IP address." -msgstr "" - -#: ../../configuration/policy/route-map.rst:268 -#: 164f440be5e94bfeab85f9e58431c933 -msgid "" -"Set the next-hop as unchanged. Pass through the route-map without changing " -"its value" -msgstr "" - -#: ../../configuration/policy/route-map.rst:274 -#: ../../configuration/policy/route-map.rst:287 -#: f89e46e41c744c4b9f9cb428c14da0e9 0e029bc9573f49e0973199a4e21b7a74 -msgid "" -"Set the BGP nexthop address to the address of the peer. For an incoming " -"route-map this means the ip address of our peer is used. For an outgoing " -"route-map this means the ip address of our self is used to establish the " -"peering with our neighbor." -msgstr "" - -#: ../../configuration/policy/route-map.rst:282 -#: 365b613d221f412cb0abcd6188aee49e -msgid "Nexthop IPv6 address." -msgstr "" - -#: ../../configuration/policy/route-map.rst:295 -#: 2cafdea846e74809bbbacdcbf7bef7c8 -msgid "" -"For Incoming and Import Route-maps if we receive a v6 global and v6 LL " -"address for the route, then prefer to use the global address as the nexthop." -msgstr "" - -#: ../../configuration/policy/route-map.rst:302 -#: 2f22206c85d94e95bcf532210d7139c3 -msgid "Set BGP local preference attribute." -msgstr "" - -#: ../../configuration/policy/route-map.rst:307 -#: 3a8ec4f778f54940a6ed3e59baea0df7 -msgid "" -"Set destination routing protocol metric. Add or subtract metric, or set " -"metric value." -msgstr "" - -#: ../../configuration/policy/route-map.rst:313 -#: 5cecfa842e32446fa15764205cbf02ea -msgid "Set OSPF external metric-type." -msgstr "" - -#: ../../configuration/policy/route-map.rst:318 -#: b2eec2092fba414984ce8a8d76ed5d7b -msgid "Set BGP origin code." -msgstr "" - -#: ../../configuration/policy/route-map.rst:323 -#: 1ab5d5c7abe14825aa6ac3e8e6b3faed -msgid "Set BGP originator ID attribute." -msgstr "" - -#: ../../configuration/policy/route-map.rst:328 -#: dd6d80b575484c9cb00d36b64537f1f1 -msgid "Set source IP/IPv6 address for route." -msgstr "" - -#: ../../configuration/policy/route-map.rst:332 -#: d6aa91d50064485f96d965e968fa46ac -msgid "Set prefixes to table." -msgstr "" - -#: ../../configuration/policy/route-map.rst:336 -#: d15bac11c5b84e6b9a99158ddc0589e8 -msgid "Set tag value for routing protocol." -msgstr "" - -#: ../../configuration/policy/route-map.rst:341 -#: 01b9621f3e58428eb72a26ef4fc953d6 -msgid "Set BGP weight attribute" -msgstr "" - -#: ../../configuration/policy/route-map.rst:344 -#: 5061ab6655204af8b75cd91eb1ab96fa -msgid "List of well-known communities" -msgstr "" - -#: ../../configuration/policy/route-map.rst:345 -#: 1fbacbb54f33450b9ab947441c373020 -msgid "" -"``local-as`` - Well-known communities value " -"NO_EXPORT_SUBCONFED 0xFFFFFF03" -msgstr "" - -#: ../../configuration/policy/route-map.rst:346 -#: ea6405de4ca24e71a191e15bd0b84d52 -msgid "" -"``no-advertise`` - Well-known communities value NO_ADVERTISE" -" 0xFFFFFF02" -msgstr "" - -#: ../../configuration/policy/route-map.rst:347 -#: ac042b35579a4fb5a8bf8e903143dee1 -msgid "" -"``no-export`` - Well-known communities value NO_EXPORT " -"0xFFFFFF01" -msgstr "" - -#: ../../configuration/policy/route-map.rst:348 -#: 64481c109e2e44a7b2ea10e921b3d8ce -msgid "``internet`` - Well-known communities value 0" -msgstr "" - -#: ../../configuration/policy/route-map.rst:349 -#: fbdd43ebad2b4271989f8c425b37b781 -msgid "" -"``graceful-shutdown`` - Well-known communities value " -"GRACEFUL_SHUTDOWN 0xFFFF0000" -msgstr "" - -#: ../../configuration/policy/route-map.rst:350 -#: 922e1d57e8c044ac88bdd37af1d75e28 -msgid "" -"``accept-own`` - Well-known communities value ACCEPT_OWN " -"0xFFFF0001" -msgstr "" - -#: ../../configuration/policy/route-map.rst:351 -#: a30a597379364f43a614e0d306b95354 -msgid "" -"``route-filter-translated-v4`` - Well-known communities value " -"ROUTE_FILTER_TRANSLATED_v4 0xFFFF0002" -msgstr "" - -#: ../../configuration/policy/route-map.rst:352 -#: aa1ee74520b24f8abb276b342eb991f5 -msgid "" -"``route-filter-v4`` - Well-known communities value " -"ROUTE_FILTER_v4 0xFFFF0003" -msgstr "" - -#: ../../configuration/policy/route-map.rst:353 -#: bb742583460c4db5952b8620246c1d43 -msgid "" -"``route-filter-translated-v6`` - Well-known communities value " -"ROUTE_FILTER_TRANSLATED_v6 0xFFFF0004" -msgstr "" - -#: ../../configuration/policy/route-map.rst:354 -#: d4a7f7d47d5e47a58eec4ebdabf8cb02 -msgid "" -"``route-filter-v6`` - Well-known communities value " -"ROUTE_FILTER_v6 0xFFFF0005" -msgstr "" - -#: ../../configuration/policy/route-map.rst:355 -#: 05d742d29bf148b58fb0b428722eb65f -msgid "" -"``llgr-stale`` - Well-known communities value LLGR_STALE " -"0xFFFF0006" -msgstr "" - -#: ../../configuration/policy/route-map.rst:356 -#: e13dcb9a9a4e493c8aa8608f8f571c78 -msgid "" -"``no-llgr`` - Well-known communities value NO_LLGR " -"0xFFFF0007" -msgstr "" - -#: ../../configuration/policy/route-map.rst:357 -#: 982a4e97bd1d41a0b5e99685b38263fc -msgid "" -"``accept-own-nexthop`` - Well-known communities value accept-own-" -"nexthop 0xFFFF0008" -msgstr "" - -#: ../../configuration/policy/route-map.rst:358 -#: 88ae257c871949cea5f32bbb085d9e3d -msgid "" -"``blackhole`` - Well-known communities value BLACKHOLE " -"0xFFFF029A" -msgstr "" - -#: ../../configuration/policy/route-map.rst:359 -#: 4a687147491e40f6b79504c4e25dfb4b -msgid "" -"``no-peer`` - Well-known communities value NOPEER " -"0xFFFFFF04" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route.po deleted file mode 100644 index 82c406f0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/policy/route.po +++ /dev/null @@ -1,294 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/policy/route.rst:3 12046565db894d5cb54f86e2ebd9a46f -msgid "Route and Route6 Policy" -msgstr "" - -#: ../../configuration/policy/route.rst:5 e7a778fb6c6f4d8ba8c2e2c6e5e10411 -msgid "" -"IPv4 route and IPv6 route policies are defined in this section. These route " -"policies can then be associated to interfaces." -msgstr "" - -#: ../../configuration/policy/route.rst:10 fe3fa542c34a4f40a52444e38b226c7d -msgid "Rule-Sets" -msgstr "" - -#: ../../configuration/policy/route.rst:12 7683b908cc034ce99282d6adfb51b123 -msgid "" -"A rule-set is a named collection of rules that can be applied to an " -"interface. Each rule is numbered, has an action to apply if the rule is " -"matched, and the ability to specify the criteria to match. Data packets go " -"through the rules from 1 - 999999, at the first match the action of the rule" -" will be executed." -msgstr "" - -#: ../../configuration/policy/route.rst:20 2fadb9b8d5704f709886ce1b1c68906c -msgid "Provide a rule-set description." -msgstr "" - -#: ../../configuration/policy/route.rst:25 8c0142822f52485faa39848d43512437 -msgid "Option to log packets hitting default-action." -msgstr "" - -#: ../../configuration/policy/route.rst:30 64141a6b13134149a71e1953b89e3065 -msgid "Provide a description for each rule." -msgstr "" - -#: ../../configuration/policy/route.rst:35 7fb95788f3d84267891f5b1e4b7d2071 -msgid "Option to enable or disable log matching rule." -msgstr "" - -#: ../../configuration/policy/route.rst:38 cffc28a3465448e9be8b69172573f71e -msgid "Matching criteria" -msgstr "" - -#: ../../configuration/policy/route.rst:40 c4c2728c251344838f143a4454a89677 -msgid "" -"There are a lot of matching criteria options available, both for ``policy " -"route`` and ``policy route6``. These options are listed in this section." -msgstr "" - -#: ../../configuration/policy/route.rst:53 1ed5668436044c39b85a140cbc7761e0 -msgid "" -"Set match criteria based on source or destination ipv4|ipv6 address, where " -"<match_criteria> could be:" -msgstr "" - -#: ../../configuration/policy/route.rst:62 eb650d146a7744308ac80f552415c95d -msgid "For ipv4:" -msgstr "" - -#: ../../configuration/policy/route.rst:57 c6e621216a4b40daaff88a7fde897966 -msgid "<x.x.x.x>: IP address to match." -msgstr "" - -#: ../../configuration/policy/route.rst:58 98375a3bba554be59930baf646f3729e -msgid "<x.x.x.x/x>: Subnet to match." -msgstr "" - -#: ../../configuration/policy/route.rst:59 92acdd0900204fa29d7032ae233e9d54 -msgid "<x.x.x.x>-<x.x.x.x>: IP range to match." -msgstr "" - -#: ../../configuration/policy/route.rst:60 686b5704d39e41718d31bba4cee9fbba -msgid "!<x.x.x.x>: Match everything except the specified address." -msgstr "" - -#: ../../configuration/policy/route.rst:61 0f8cd4fac8d64b7a80a36c82131bc67f -msgid "!<x.x.x.x/x>: Match everything except the specified subnet." -msgstr "" - -#: ../../configuration/policy/route.rst:62 bfdb04726e5645289174498e2a62e790 -msgid "!<x.x.x.x>-<x.x.x.x>: Match everything except the specified range." -msgstr "" - -#: ../../configuration/policy/route.rst:71 4507a71f626741f5971311da1d5d0f1c -msgid "And for ipv6:" -msgstr "" - -#: ../../configuration/policy/route.rst:65 3e5626dbef4c4b258977251031228707 -msgid "<h:h:h:h:h:h:h:h>: IPv6 address to match." -msgstr "" - -#: ../../configuration/policy/route.rst:66 5fc7a4cf419b4f6699b6d600e094ca08 -msgid "<h:h:h:h:h:h:h:h/x>: IPv6 prefix to match." -msgstr "" - -#: ../../configuration/policy/route.rst:67 4e5e57d424ed4d2582ad933e03d5cf10 -msgid "<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: IPv6 range to match." -msgstr "" - -#: ../../configuration/policy/route.rst:68 aa06921e939448b291c2cb14023c17ea -msgid "!<h:h:h:h:h:h:h:h>: Match everything except the specified address." -msgstr "" - -#: ../../configuration/policy/route.rst:69 4bfb4b8efc3d4874815eb19134d5b2d8 -msgid "!<h:h:h:h:h:h:h:h/x>: Match everything except the specified prefix." -msgstr "" - -#: ../../configuration/policy/route.rst:70 bc0b878829924ed18aa321f9f13d91ef -msgid "" -"!<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: Match everything except the specified " -"range." -msgstr "" - -#: ../../configuration/policy/route.rst:82 b05ef17b6b7e4e1998134c800991e37f -msgid "" -"Set match criteria based on source or destination groups, where <text> would" -" be the group name/identifier. Prepend character '!' for inverted matching " -"criteria." -msgstr "" - -#: ../../configuration/policy/route.rst:89 d6b58b851d5247ae8911adefd70beecc -msgid "" -"Set match criteria based on destination port, where <match_criteria> could " -"be:" -msgstr "" - -#: ../../configuration/policy/route.rst:92 9a6cd463c3774f8aa53aa2f050899d57 -msgid "<port name>: Named port (any name in /etc/services, e.g., http)." -msgstr "" - -#: ../../configuration/policy/route.rst:93 d830786ca2784f22b920f86b8aee90ba -msgid "<1-65535>: Numbered port." -msgstr "" - -#: ../../configuration/policy/route.rst:94 a87aee014b2b44e18924070d20d5eac5 -msgid "<start>-<end>: Numbered port range (e.g., 1001-1005)." -msgstr "" - -#: ../../configuration/policy/route.rst:96 06f2f1d47e194c00bd3d91edeb3c9d93 -msgid "" -"Multiple destination ports can be specified as a comma-separated list. The " -"whole list can also be \"negated\" using '!'. For example: " -"'!22,telnet,http,123,1001-1005'" -msgstr "" - -#: ../../configuration/policy/route.rst:103 8e9e32c80ad0480482e7935563d2ec0a -msgid "Option to disable rule." -msgstr "" - -#: ../../configuration/policy/route.rst:110 dfe8b9e968364e728f8603ef0ba88923 -msgid "" -"Match based on dscp value criteria. Multiple values from 0 to 63 and ranges " -"are supported." -msgstr "" - -#: ../../configuration/policy/route.rst:118 dfb2a15e9da84a8cb2709354fc301993 -msgid "Set IP fragment match, where:" -msgstr "" - -#: ../../configuration/policy/route.rst:120 89262846895f4c3a9f97f2883a425796 -msgid "match-frag: Second and further fragments of fragmented packets." -msgstr "" - -#: ../../configuration/policy/route.rst:121 9b2bcec1ce7a4724b4dea926a3a916b6 -msgid "match-non-frag: Head fragments or unfragmented packets." -msgstr "" - -#: ../../configuration/policy/route.rst:126 516d8e1137834731bde4ad51ec30219f -msgid "Match based on icmp|icmpv6 code and type." -msgstr "" - -#: ../../configuration/policy/route.rst:131 469b60b6819b4c15a3125a889d742178 -msgid "" -"Match based on icmp|icmpv6 type-name criteria. Use tab for information about" -" what type-name criteria are supported." -msgstr "" - -#: ../../configuration/policy/route.rst:139 8c0680de716b4c7d9f72ead12638e2b3 -msgid "Set IPSec inbound match criterias, where:" -msgstr "" - -#: ../../configuration/policy/route.rst:141 6df96925bad1492c8fe7fcfe41c41156 -msgid "match-ipsec: match inbound IPsec packets." -msgstr "" - -#: ../../configuration/policy/route.rst:142 3f16b8ae02824909b69431a30accd86f -msgid "match-none: match inbound non-IPsec packets." -msgstr "" - -#: ../../configuration/policy/route.rst:147 715651ff1aaa469abef0b8a8c3db485a -msgid "Set maximum number of packets to alow in excess of rate." -msgstr "" - -#: ../../configuration/policy/route.rst:152 02aca6c48ebb4f388f0e5070d3dd63c0 -msgid "" -"Set maximum average matching rate. Format for rate: integer/time_unit, where" -" time_unit could be any one of second, minute, hour or day.For example " -"1/second implies rule to be matched at an average of once per second." -msgstr "" - -#: ../../configuration/policy/route.rst:161 7e49ea28828244cbac07cb55b408e2a3 -msgid "" -"Match a protocol criteria. A protocol number or a name which is defined in: " -"``/etc/protocols``. Special names are ``all`` for all protocols and " -"``tcp_udp`` for tcp and udp based packets. The ``!`` negates the selected " -"protocol." -msgstr "" - -#: ../../configuration/policy/route.rst:171 81296c39572e4c079bfafc2f1cbae4f0 -msgid "" -"Set parameters for matching recently seen sources. This match could be used " -"by seeting count (source address seen more than <1-255> times) and/or time " -"(source address seen in the last <0-4294967295> seconds)." -msgstr "" - -#: ../../configuration/policy/route.rst:180 10a07af3155b40b496564c06623495ee -msgid "Set match criteria based on session state." -msgstr "" - -#: ../../configuration/policy/route.rst:185 7dce446cf9104cc3b08b9fa06398e9bd -msgid "" -"Set match criteria based on tcp flags. Allowed values for TCP flags: SYN ACK" -" FIN RST URG PSH ALL. When specifying more than one flag, flags should be " -"comma-separated. For example : value of 'SYN,!ACK,!FIN,!RST' will only match" -" packets with the SYN flag set, and the ACK, FIN and RST flags unset." -msgstr "" - -#: ../../configuration/policy/route.rst:205 5f6efb8f27c54cf8951b7c6ccaf664f9 -msgid "Time to match the defined rule." -msgstr "" - -#: ../../configuration/policy/route.rst:209 40e408be46854491ba0e1746a712a8c1 -msgid "" -"Match time to live parameter, where 'eq' stands for 'equal'; 'gt' stands for" -" 'greater than', and 'lt' stands for 'less than'." -msgstr "" - -#: ../../configuration/policy/route.rst:214 1d8e701d2da44af290b91322303203e1 -msgid "" -"Match hop-limit parameter, where 'eq' stands for 'equal'; 'gt' stands for " -"'greater than', and 'lt' stands for 'less than'." -msgstr "" - -#: ../../configuration/policy/route.rst:218 6ae39e910670474fb08a549fc24a24dd -msgid "Actions" -msgstr "" - -#: ../../configuration/policy/route.rst:220 443c8888d1754d1fb5a336624176eded -msgid "" -"When mathcing all patterns defined in a rule, then different actions can be " -"made. This includes droping the packet, modifying certain data, or setting a" -" different routing table." -msgstr "" - -#: ../../configuration/policy/route.rst:227 0d8aa41b2b5f46778a17a651731a1bd3 -msgid "Set rule action to drop." -msgstr "" - -#: ../../configuration/policy/route.rst:232 782f6f4e767f45f8b7787968c4a917ec -msgid "" -"Set packet modifications: Packet Differentiated Services Codepoint (DSCP)" -msgstr "" - -#: ../../configuration/policy/route.rst:237 cddc7036de154ee78cbb807465e3b87b -msgid "Set packet modifications: Packet marking" -msgstr "" - -#: ../../configuration/policy/route.rst:242 f03b3093e7444648adcd66758ca8d80d -msgid "Set packet modifications: Routing table to forward packet with." -msgstr "" - -#: ../../configuration/policy/route.rst:247 7109221ecb5f463aadc1d9e558efea48 -msgid "" -"Set packet modifications: Explicitly set TCP Maximum segment size value." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bfd.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bfd.po deleted file mode 100644 index f7ac0c4a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bfd.po +++ /dev/null @@ -1,133 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../_include/need_improvement.txt:11 0680c6dee54d45fb85166f76158e3f1f -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 5b49805092c44344b6084a780cd9eae0 -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/protocols/bfd.rst:9 9ea4b3f19ddf43dea109135a6e380f14 -msgid "BFD" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:11 d2eeb3f2bea4455ca3fbd534010efdf4 -msgid "" -":abbr:`BFD (Bidirectional Forwarding Detection)` is described and extended " -"by the following RFCs: :rfc:`5880`, :rfc:`5881` and :rfc:`5883`." -msgstr "" - -#: ../../configuration/protocols/bfd.rst:14 07c0c0c903f84b59825bd4796c1aa9fc -msgid "" -"In the age of very fast networks, a second of unreachability may equal " -"millions of lost packets. The idea behind BFD is to detect very quickly when" -" a peer is down and take action extremely fast." -msgstr "" - -#: ../../configuration/protocols/bfd.rst:17 2d350fa76fd6418fb8b0996e12362f8d -msgid "" -"BFD sends lots of small UDP packets very quickly to ensures that the peer is" -" still alive." -msgstr "" - -#: ../../configuration/protocols/bfd.rst:19 33bd042555b44e4aa6c720878d6e09cb -msgid "" -"This allows avoiding the timers defined in BGP and OSPF protocol to expires." -msgstr "" - -#: ../../configuration/protocols/bfd.rst:22 03b027d8407348deb63871c0fa121fa6 -msgid "Configure BFD" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:26 8d0a9190d77145bfa0eefbe3e633c1de -msgid "Set BFD peer IPv4 address or IPv6 address" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:30 47acd42b01834f69b778fb65bad6715c -msgid "Enables the echo transmission mode" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:34 d01a4031a50b43b387c76f26853e5754 -msgid "Allow this BFD peer to not be directly connected" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:39 bc060d12f1f848948aa2203a26f7c19f -msgid "Bind listener to specific interface/address, mandatory for IPv6" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:43 12c3caa0be764921a13a1baec6a908b9 -msgid "" -"The minimal echo receive transmission interval that this system is capable " -"of handling" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:48 78e82e9dc53544048d7aebcc97bcb64f -msgid "Remote transmission interval will be multiplied by this value" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:53 f42865681b684474bfdbc7e254153e80 -msgid "Interval in milliseconds" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:57 89eaa85556dd496e8f170b9481407441 -msgid "Disable a BFD peer" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:61 eb155e9bf58f47a0bc78079b46918941 -msgid "Enable BFD in BGP" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:65 16eaf833c7a14716bfb10adba25fdc3a -msgid "Enable BFD on a single BGP neighbor" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:69 1d82b7fb84054999b700d79318c162af -msgid "Enable BFD on a BGP peer group" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:73 35485a2a543e469f9b5129caac64b5b4 -msgid "Enable BFD in OSPF" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:77 6d34bef8daf04d04bae90090b03b6eeb -msgid "Enable BFD for OSPF on an interface" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:81 1d3710e8111c4564a571a4d47c4b83a2 -msgid "Enable BFD for OSPFv3 on an interface" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:85 1b9ffa03ca7346d8be976c6cdf0a5e34 -msgid "Enable BFD in ISIS" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:89 cedccbe5c8f74dbcb29e510f3612741e -msgid "Enable BFD for ISIS on an interface" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:94 0d0b77819d034f41a8caa9210113a36d -msgid "Operational Commands" -msgstr "" - -#: ../../configuration/protocols/bfd.rst:98 78a5725cd8ed4dfe8d4dbf11ef777276 -msgid "Show all BFD peers" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bgp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bgp.po deleted file mode 100644 index 587bc5dd..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/bgp.po +++ /dev/null @@ -1,1343 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/bgp.rst:5 d25122de85c549caba775f0e2c7b73d0 -msgid "BGP" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:7 a24cc260a6f9475bbeb2123bc663ec5a -msgid "" -":abbr:`BGP (Border Gateway Protocol)` is one of the Exterior Gateway " -"Protocols and the de facto standard interdomain routing protocol. The latest" -" BGP version is 4. BGP-4 is described in :rfc:`1771` and updated by " -":rfc:`4271`. :rfc:`2858` adds multiprotocol support to BGP." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:12 4e803a9e21734aa2a1f01583d297891a -msgid "" -"VyOS makes use of :abbr:`FRR (Free Range Routing)` and we would like to " -"thank them for their effort!" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:17 1b171b39e0b441c3ad971aef62477d07 -msgid "Basic Concepts" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:22 0dcd3ed6191142b4b8e48e5b85730cab -msgid "Autonomous Systems" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:24 93bfb6d2229e4485bcf6b32d3c768849 -msgid "From :rfc:`1930`:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:26 f330bf2e15a5458dbd541b56febe1ce2 -msgid "" -"An AS is a connected group of one or more IP prefixes run by one or more " -"network operators which has a SINGLE and CLEARLY DEFINED routing policy." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:29 cc8ce1c73cf44463932e5989b1592686 -msgid "" -"Each :abbr:`AS (Autonomous System)` has an identifying number associated " -"with it called an :abbr:`ASN (Autonomous System Number)`. This is a two " -"octet value ranging in value from 1 to 65535. The AS numbers 64512 through " -"65535 are defined as private AS numbers. Private AS numbers must not be " -"advertised on the global Internet. The 2-byte AS number range has been " -"exhausted. 4-byte AS numbers are specified in :rfc:`6793`, and provide a " -"pool of 4294967296 AS numbers." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:36 542c1905fb13409daf5fdae3f40cf024 -msgid "" -"The :abbr:`ASN (Autonomous System Number)` is one of the essential elements " -"of BGP. BGP is a distance vector routing protocol, and the AS-Path framework" -" provides distance vector metric and loop detection to BGP." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:42 b19ddef7cfd84f4590c13324c3c25286 -msgid "" -"Set local :abbr:`ASN (Autonomous System Number)` that this router " -"represents. This is a a mandatory option!" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:48 e6528def65c44146b74e834d60dafcfb -msgid "Address Families" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:50 ab94c351a2004ddca33b3221d7cf2411 -msgid "" -"Multiprotocol extensions enable BGP to carry routing information for " -"multiple network layer protocols. BGP supports an Address Family Identifier " -"(AFI) for IPv4 and IPv6." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:57 2a57b88f40c843d48556b080da9047f0 -msgid "Route Selection" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:59 09e9f7c1877d4b93b7a278604fcb9045 -msgid "" -"The route selection process used by FRR's BGP implementation uses the " -"following decision criterion, starting at the top of the list and going " -"towards the bottom until one of the factors can be used." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:63 c7cdcae59a59478cb92f4991594bfaa9 -msgid "**Weight check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:65 5943b43206f040119d9ae38baa07db2e -msgid "Prefer higher local weight routes to lower routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:67 e0d0a59bd397447398d5cbc698f5de61 -msgid "**Local preference check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:69 37d9683cd0264c0eaaa8629454b3d164 -msgid "Prefer higher local preference routes to lower." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:71 951ff85a540e439cb8c979bbdc93b107 -msgid "**Local route check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:73 9c0bfe99fcbe4879b6e77dcc6d87b021 -msgid "" -"Prefer local routes (statics, aggregates, redistributed) to received routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:75 8b29c57306404c2cb0cbf34e02a96b87 -msgid "**AS path length check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:77 61ce1bf5b1f8417a979cf1756bb9f3b1 -msgid "Prefer shortest hop-count AS_PATHs." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:79 04145edbebc3460d81bb253c2c5bf0c4 -msgid "**Origin check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:81 39f35e55452c42a19356c9fa1bf4a291 -msgid "" -"Prefer the lowest origin type route. That is, prefer IGP origin routes to " -"EGP, to Incomplete routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:84 189495b3e9a6446998773108b263ab5b -msgid "**MED check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:86 1c38ddc8444d4401b0dc5ea0a1a05f76 -msgid "" -"Where routes with a MED were received from the same AS, prefer the route " -"with the lowest MED." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:89 4c354295954841e286ba52832654943f -msgid "**External check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:91 2d6c21b628584d7a8b35b2675b90565e -msgid "" -"Prefer the route received from an external, eBGP peer over routes received " -"from other types of peers." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:94 af3a29f196a84b75b6850e27dc3d6828 -msgid "**IGP cost check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:96 d856785bed824045a4051ccd07315f66 -msgid "Prefer the route with the lower IGP cost." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:98 918b619a766d42c19f914268b6eb3d90 -msgid "**Multi-path check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:100 2a5644dd2e194a9a8797e1d870b640ab -msgid "" -"If multi-pathing is enabled, then check whether the routes not yet " -"distinguished in preference may be considered equal. If :cfgcmd:`bgp " -"bestpath as-path multipath-relax` is set, all such routes are considered " -"equal, otherwise routes received via iBGP with identical AS_PATHs or routes " -"received from eBGP neighbours in the same AS are considered equal." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:106 1c26e66a52ed44988ef3c25a16f3bae8 -msgid "**Already-selected external check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:108 82710031dace4291afae226caa01eaca -msgid "" -"Where both routes were received from eBGP peers, then prefer the route which" -" is already selected. Note that this check is not applied if :cfgcmd:`bgp " -"bestpath compare-routerid` is configured. This check can prevent some cases " -"of oscillation." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:113 43fb77956bde4a6c8e99218941b32224 -msgid "**Router-ID check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:115 5e71e78092e7468ea05cc30c145f11ea -msgid "" -"Prefer the route with the lowest `router-ID`. If the route has an " -"`ORIGINATOR_ID` attribute, through iBGP reflection, then that router ID is " -"used, otherwise the `router-ID` of the peer the route was received from is " -"used." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:120 8afeaf126d2444de8fd4c4ad244f3188 -msgid "**Cluster-List length check**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:122 0da625ea087b40ea83011acca84455bf -msgid "" -"The route with the shortest cluster-list length is used. The cluster-list " -"reflects the iBGP reflection path the route has taken." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:125 f443755169fb4a4d8551cb173edb4aae -msgid "**Peer address**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:127 a7cf7b2776b24e8dbad44163bb894b7a -msgid "" -"Prefer the route received from the peer with the higher transport layer " -"address, as a last-resort tie-breaker." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:133 -#: ../../configuration/protocols/bgp.rst:228 88f373a1c54f414889446a49d7cc7d01 -#: 09a7053562644b75ab378a62d904dd78 -msgid "Capability Negotiation" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:135 0b6a370eb0094f1f9d3736fac26ae204 -msgid "" -"When adding IPv6 routing information exchange feature to BGP. There were " -"some proposals. :abbr:`IETF (Internet Engineering Task Force)` :abbr:`IDR " -"(Inter Domain Routing)` adopted a proposal called Multiprotocol Extension " -"for BGP. The specification is described in :rfc:`2283`. The protocol does " -"not define new protocols. It defines new attributes to existing BGP. When it" -" is used exchanging IPv6 routing information it is called BGP-4+. When it is" -" used for exchanging multicast routing information it is called MBGP." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:143 35e96e912f60454db28a3617bbcff2c0 -msgid "" -"*bgpd* supports Multiprotocol Extension for BGP. So if a remote peer " -"supports the protocol, *bgpd* can exchange IPv6 and/or multicast routing " -"information." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:146 c3af8a8ce4394b4a80fbcfbb9462a9fb -msgid "" -"Traditional BGP did not have the feature to detect a remote peer's " -"capabilities, e.g. whether it can handle prefix types other than IPv4 " -"unicast routes. This was a big problem using Multiprotocol Extension for BGP" -" in an operational network. :rfc:`2842` adopted a feature called Capability " -"Negotiation. *bgpd* use this Capability Negotiation to detect the remote " -"peer's capabilities. If a peer is only configured as an IPv4 unicast " -"neighbor, *bgpd* does not send these Capability Negotiation packets (at " -"least not unless other optional BGP features require capability " -"negotiation)." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:155 4eac3d6c0c2f443db6ed63c9f847f30e -msgid "" -"By default, FRR will bring up peering with minimal common capability for the" -" both sides. For example, if the local router has unicast and multicast " -"capabilities and the remote router only has unicast capability the local " -"router will establish the connection with unicast only capability. When " -"there are no common capabilities, FRR sends Unsupported Capability error and" -" then resets the connection." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:164 03890f868192418fa99db79e1df2455f -msgid "Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:169 cd1b53f6dd45421396322608cf942179 -msgid "BGP Router Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:171 899f6655c5f547039c861657cbc52bcf -msgid "" -"First of all you must configure BGP router with the :abbr:`ASN (Autonomous " -"System Number)`. The AS number is an identifier for the autonomous system. " -"The BGP protocol uses the AS number for detecting whether the BGP connection" -" is internal or external. VyOS does not have a special command to start the " -"BGP process. The BGP process starts when the first neighbor is configured." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:179 a58c2600300145c6a1bbd0a12e12ad84 -msgid "" -"Set local autonomous system number that this router represents. This is a " -"mandatory option!" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:183 6733aed5005e4d5d961064713b387b38 -msgid "Peers Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:186 862693534e6d41aebe232995f731b350 -msgid "Defining Peers" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:191 7be58608be4a4465bbaaa1f6653cce27 -msgid "" -"This command creates a new neighbor whose remote-as is <nasn>. The neighbor " -"address can be an IPv4 address or an IPv6 address or an interface to use for" -" the connection. The command is applicable for peer and peer group." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:198 670adfdbe1f84a0ab97cb2edfba4fdd5 -msgid "" -"Create a peer as you would when you specify an ASN, except that if the peers" -" ASN is different than mine as specified under the :cfgcmd:`protocols bgp " -"<asn>` command the connection will be denied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:205 be03d424afc24feaa64601de34e3a9b8 -msgid "" -"Create a peer as you would when you specify an ASN, except that if the peers" -" ASN is the same as mine as specified under the :cfgcmd:`protocols bgp " -"<asn>` command the connection will be denied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:211 ecef3733d6764419a8a577c152407998 -msgid "" -"This command disable the peer or peer group. To reenable the peer use the " -"delete form of this command." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:217 48a35ec35a3449fd9d0fd957064aa408 -msgid "Set description of the peer or peer group." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:222 6ae5596783394073822d51f12cca3b6e -msgid "" -"Specify the IPv4 source address to use for the BGP session to this neighbor," -" may be specified as either an IPv4 address directly or as an interface " -"name." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:233 39dd5c3a6156498c836c3117b7ed33ab -msgid "" -"This command would allow the dynamic update of capabilities over an " -"established BGP session." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:239 86e6e5936eb348ea9d698b3151e0de63 -msgid "" -"Allow bgp to negotiate the extended-nexthop capability with it’s peer. If " -"you are peering over a IPv6 Link-Local address then this capability is " -"turned on automatically. If you are peering over a IPv6 Global Address then " -"turning on this command will allow BGP to install IPv4 routes with IPv6 " -"nexthops if you do not have IPv4 configured on interfaces." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:248 f220d209e05c4d9795ef81c7e3802daf -msgid "" -"Suppress sending Capability Negotiation as OPEN message optional parameter " -"to the peer. This command only affects the peer is configured other than " -"IPv4 unicast configuration." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:252 497d713438994d6381a522dcdebe0de4 -msgid "" -"When remote peer does not have capability negotiation feature, remote peer " -"will not send any capabilities at all. In that case, bgp configures the peer" -" with configured capabilities." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:256 0c826a3c23a64d03b7dbd4ca0d95fd58 -msgid "" -"You may prefer locally configured capabilities more than the negotiated " -"capabilities even though remote peer sends capabilities. If the peer is " -"configured by :cfgcmd:`override-capability`, VyOS ignores received " -"capabilities then override negotiated capabilities with configured values." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:261 78bbaeaefcf946258e8f761e7c23d80c -msgid "" -"Additionally you should keep in mind that this feature fundamentally " -"disables the ability to use widely deployed BGP features. BGP unnumbered, " -"hostname support, AS4, Addpath, Route Refresh, ORF, Dynamic Capabilities, " -"and graceful restart." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:269 3f648ca009bd47b3bd6d4046943dc16f -msgid "" -"This command allow override the result of Capability Negotiation with local " -"configuration. Ignore remote peer’s capability value." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:275 a4b6e98c551e432eadb27f80c178f430 -msgid "" -"This command forces strictly compare remote capabilities and local " -"capabilities. If capabilities are different, send Unsupported Capability " -"error then reset connection." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:279 1a876467776442568a35aae0cbad39b4 -msgid "" -"You may want to disable sending Capability Negotiation OPEN message optional" -" parameter to the peer when remote peer does not implement Capability " -"Negotiation. Please use :cfgcmd:`disable-capability-negotiation` command to " -"disable the feature." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:286 a64f5c97f71a4152a6fa271df1e89685 -msgid "Peer Parameters" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:291 a52f50be7ad444c49d40d5950d82ec17 -msgid "" -"This command accept incoming routes with AS path containing AS number with " -"the same value as the current system AS. This is used when you want to use " -"the same AS number in your sites, but you can’t connect them directly." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:296 eed330a1ddb148c4bc3509ade415c5a6 -msgid "" -"The number parameter (1-10) configures the amount of accepted occurences of " -"the system AS number in AS path." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:299 96d04e9e86834885a34ef92240260061 -msgid "" -"This command is only allowed for eBGP peers. It is not applicable for peer " -"groups." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:305 6c1f298b92d547f78036cf243eda7ed6 -msgid "" -"This command override AS number of the originating router with the local AS " -"number." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:308 3709d62f084049aabb0a466d0185c6ee -msgid "" -"Usually this configuration is used in PEs (Provider Edge) to replace the " -"incoming customer AS number so the connected CE ( Customer Edge) can use the" -" same AS number as the other customer sites. This allows customers of the " -"provider network to use the same AS number across their sites." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:314 -#: ../../configuration/protocols/bgp.rst:416 f0ac9303755646ba8878c86334103eea -#: e9f68553cd1f41bba0084ebc39e63df1 -msgid "This command is only allowed for eBGP peers." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:319 a16c4be223234af9bd6f8d5b77a445f8 -msgid "" -"This command specifies attributes to be left unchanged for advertisements " -"sent to a peer or peer group." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:325 f98d601330e94914b2bbd92e39c442ad -msgid "" -"This command specifies a maximum number of prefixes we can receive from a " -"given peer. If this number is exceeded, the BGP session will be destroyed. " -"The number range is 1 to 4294967295." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:332 476e1c2bea8f4c97829b65a02fcfe903 -msgid "" -"This command forces the BGP speaker to report itself as the next hop for an " -"advertised route it advertised to a neighbor." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:338 28a364d29ca6436b9bffaa762c9c9d49 -msgid "" -"This command removes the private ASN of routes that are advertised to the " -"configured peer. It removes only private ASNs on routes advertised to EBGP " -"peers." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:342 ff9e7008fafe471791cb6cfaa784ce81 -msgid "" -"If the AS-Path for the route has only private ASNs, the private ASNs are " -"removed." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:345 e1818c221f2f4327b87d8320278bb6cf -msgid "" -"If the AS-Path for the route has a private ASN between public ASNs, it is " -"assumed that this is a design choice, and the private ASN is not removed." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:352 e31b843c9aae40dcbb0c250fd8989f91 -msgid "" -"Changes in BGP policies require the BGP session to be cleared. Clearing has " -"a large negative impact on network operations. Soft reconfiguration enables " -"you to generate inbound updates from a neighbor, change and activate BGP " -"policies without clearing the BGP session." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:357 aff6a536fb1f4dfcb0765c404cb69052 -msgid "" -"This command specifies that route updates received from this neighbor will " -"be stored unmodified, regardless of the inbound policy. When inbound soft " -"reconfiguration is enabled, the stored updates are processed by the new " -"policy configuration to create new inbound updates." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:362 ef516cfc2c16427690c9f08ce2b5bf5b -msgid "" -"Storage of route updates uses memory. If you enable soft reconfiguration " -"inbound for multiple neighbors, the amount of memory used can become " -"significant." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:369 bf00b525e58a4fd19c5ebd30bb4bb27e -msgid "" -"This command specifies a default weight value for the neighbor’s routes. The" -" number range is 1 to 65535." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:375 6df879afc0554962abf988154346fddd -msgid "" -"This command specifies the minimum route advertisement interval for the " -"peer. The interval value is 0 to 600 seconds, with the default advertisement" -" interval being 0." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:382 0cf4b73b509846f7967716dad61dae8e -msgid "" -"This command allows peerings between directly connected eBGP peers using " -"loopback addresses without adjusting the default TTL of 1." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:388 694027c147004693a320f47d118769b7 -msgid "" -"This command specifies that the community attribute should not be sent in " -"route updates to a peer. By default community attribute is sent." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:394 cbd3eee143d84a2996bbd9234a7b3551 -msgid "" -"This command allows sessions to be established with eBGP neighbors when they" -" are multiple hops away. When the neighbor is not directly connected and " -"this knob is not enabled, the session will not establish. The number of hops" -" range is 1 to 255. This command is mutually exclusive with :cfgcmd:`ttl-" -"security hops`." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:403 f33adf1319714fa889af21e23b763bde -msgid "" -"Specify an alternate AS for this BGP process when interacting with the " -"specified peer or peer group. With no modifiers, the specified local-as is " -"prepended to the received AS_PATH when receiving routing updates from the " -"peer, and prepended to the outgoing AS_PATH (after the process local AS) " -"when transmitting local routes to the peer." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:409 66db4be16c994e06bcae9dd6e2e336a6 -msgid "" -"If the :cfgcmd:`no-prepend` attribute is specified, then the supplied local-" -"as is not prepended to the received AS_PATH." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:412 e6bd01d1d4df422097dcf4cd6d08b30e -msgid "" -"If the :cfgcmd:`replace-as` attribute is specified, then only the supplied " -"local-as is prepended to the AS_PATH when transmitting local-route updates " -"to this peer." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:420 64995ee4139b44e6bc42c5f6e412c7dc -msgid "" -"Configures the BGP speaker so that it only accepts inbound connections from," -" but does not initiate outbound connections to the peer or peer group." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:426 419ba17e800647b5a9de6b0c0b433465 -msgid "" -"This command specifies a MD5 password to be used with the tcp socket that is" -" being used to connect to the remote peer." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:432 09cef1df12774e9dbc77fd0fcb8790c1 -msgid "" -"This command enforces Generalized TTL Security Mechanism (GTSM), as " -"specified in :rfc:`5082`. With this command, only neighbors that are " -"specified number of hops away will be allowed to become neighbors. The " -"number of hops range is 1 to 254. This command is mutually exclusive with " -":cfgcmd:`ebgp-multihop`." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:440 7a5e6dbd213b458abc914f41ad1397cd -msgid "Peer Groups" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:442 cb7a992f034547258bec3fe536bad3dd -msgid "" -"Peer groups are used to help improve scaling by generating the same update " -"information to all members of a peer group. Note that this means that the " -"routes generated by a member of a peer group will be sent back to that " -"originating peer with the originator identifier attribute set to indicated " -"the originating peer. All peers not associated with a specific peer group " -"are treated as belonging to a default peer group, and will share updates." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:451 98fb94bd711e4f1a9057627fd0343706 -msgid "" -"This command defines a new peer group. You can specify to the group the same" -" parameters that you can specify for specific neighbors." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:454 7bdb4ee47bc0436da74cf392b0daff73 -msgid "" -"If you apply a parameter to an individual neighbor IP address, you override " -"the action defined for a peer group that includes that IP address." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:461 d6ef59dbd43c4eb48574539734df240b -msgid "This command bind specific peer to peer group with a given name." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:465 a569530268d14b369843383d852c22ab -msgid "Network Advertisement Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:470 89bf395a19eb4f7593962855bdde972c -msgid "This command is used for advertising IPv4 or IPv6 networks." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:472 b4ece270008f46ce983aff01006411a9 -msgid "" -"By default, the BGP prefix is advertised even if it's not present in the " -"routing table. This behaviour differs from the implementation of some " -"vendors." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:478 352ab51860ec493ca0850130b53d0eb1 -msgid "" -"This configuration modifies the behavior of the network statement. If you " -"have this configured the underlying network must exist in the routing table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:484 e5c0ebb3ba4940d49fffd576b721564a -msgid "" -"By default, VyOS does not advertise a default route (0.0.0.0/0) even if it " -"is in routing table. When you want to announce default routes to the peer, " -"use this command. Using optional argument :cfgcmd:`route-map` you can inject" -" the default route to given neighbor only if the conditions in the route map" -" are met." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:492 6a81cf010ad34aebabbd0c6962d2f2c8 -msgid "Route Aggregation Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:497 d3d9ea2e0c60496f8de0278f08a9f7fe -msgid "" -"This command specifies an aggregate address. The router will also announce " -"longer-prefixes inside of the aggregate address." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:503 489263e2637c4fbe89da5dc6ad5187a9 -msgid "" -"This command specifies an aggregate address with a mathematical set of " -"autonomous systems. This command summarizes the AS_PATH attributes of all " -"the individual routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:510 49314960466243eeb542a826548f5a86 -msgid "" -"This command specifies an aggregate address and provides that longer-" -"prefixes inside of the aggregate address are suppressed before sending BGP " -"updates out to peers." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:517 e9bcd6aaa78c48a9b8a11eaa438203f2 -msgid "" -"This command applies route-map to selectively unsuppress prefixes suppressed" -" by summarisation." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:522 d48c2233760440369744650160990135 -msgid "Redistribution Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:527 f494af130c7e48cebbf736117e2d0cae -msgid "" -"This command redistributes routing information from the given route source " -"to the BGP process. There are six modes available for route source: " -"connected, kernel, ospf, rip, static, table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:534 d1b467c9fbd540a1adb9c00f9df5b59d -msgid "" -"This command specifies metric (MED) for redistributed routes. The metric " -"range is 0 to 4294967295. There are six modes available for route source: " -"connected, kernel, ospf, rip, static, table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:541 f75fe34a27294848b52d13a188f79edc -msgid "" -"This command allows to use route map to filter redistributed routes. There " -"are six modes available for route source: connected, kernel, ospf, rip, " -"static, table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:547 d792ad6dcc544431b3fb1ce2096052af -msgid "General Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:550 e3355f81f62e4b0f8434b9f6adde69cd -msgid "Common parameters" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:554 b8ac15ea916e43e0a0365c1fea6effc9 -msgid "" -"This command specifies the router-ID. If router ID is not specified it will " -"use the highest interface IP address." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:560 306fe7a07afb411690ffa7928ea11437 -msgid "" -"This command defines the maximum number of parallel routes that the BGP can " -"support. In order for BGP to use the second path, the following attributes " -"have to match: Weight, Local Preference, AS Path (both AS number and AS path" -" length), Origin code, MED, IGP metric. Also, the next hop address for each " -"path must be different." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:568 c62b1097d5304af79984d86956a26c79 -msgid "This command enable logging neighbor up/down changes and reset reason." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:572 0c1156d89c6442bdad4b7b9c7faeff3e -msgid "" -"This command disables route reflection between route reflector clients. By " -"default, the clients of a route reflector are not required to be fully " -"meshed and the routes from a client are reflected to other clients. However," -" if the clients are fully meshed, route reflection is not required. In this " -"case, use the :cfgcmd:`no-client-to-client-reflection` command to disable " -"client-to-client reflection." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:581 b82898567c4a4b2aa52a74059dfcd938 -msgid "Disable immediate session reset if peer's connected link goes down." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:585 7b71bfcf9c5a4598a54d92e63ea24ab3 -msgid "" -"This command is useful if one desires to loosen the requirement for BGP to " -"have strictly defined neighbors. Specifically what is allowed is for the " -"local router to listen to a range of IPv4 or IPv6 addresses defined by a " -"prefix and to accept BGP open messages. When a TCP connection (and " -"subsequently a BGP open message) from within this range tries to connect the" -" local router then the local router will respond and connect with the " -"parameters that are defined within the peer group. One must define a peer-" -"group for each range that is listed. If no peer-group is defined then an " -"error will keep you from committing the configuration." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:597 2f5a911656cf4ea5be4a596d4b53a0bf -msgid "" -"This command goes hand in hand with the listen range command to limit the " -"amount of BGP neighbors that are allowed to connect to the local router. The" -" limit range is 1 to 5000." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:603 854a2e537a8344a493d2975970505a5b -msgid "" -"This command changes the eBGP behavior of FRR. By default FRR enables " -":rfc:`8212` functionality which affects how eBGP routes are advertised, " -"namely no routes are advertised across eBGP sessions without some sort of " -"egress route-map/policy in place. In VyOS however we have this RFC " -"functionality disabled by default so that we can preserve backwards " -"compatibility with older versions of VyOS. With this option one can enable " -":rfc:`8212` functionality to operate." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:612 1afb48cd9ca540a4847401c93643bad6 -msgid "Administrative Distance" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:617 e91b696248534ba3a3fab7d9898ee597 -msgid "" -"This command change distance value of BGP. The arguments are the distance " -"values for external routes, internal routes and local routes respectively. " -"The distance range is 1 to 255." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:624 033b164374c94937a4bd59e18b523434 -msgid "" -"This command sets the administrative distance for a particular route. The " -"distance range is 1 to 255." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:627 c6abc4fa29114cb88bb4ef2f2ba63041 -msgid "" -"Routes with a distance of 255 are effectively disabled and not installed " -"into the kernel." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:632 6b2a28fbb8db413c803c611bc8370ac8 -msgid "Timers" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:636 81626335c4bc498cb92dd4e8df8cb882 -msgid "" -"This command specifies hold-time in seconds. The timer range is 4 to 65535. " -"The default value is 180 second. If you set value to 0 VyOS will not hold " -"routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:642 ec4a920ebe4c49c780c1fd83adfd9dd7 -msgid "" -"This command specifies keep-alive time in seconds. The timer can range from " -"4 to 65535. The default value is 60 second." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:647 776042677392494fafd039c7dc95796c -msgid "Route Dampening" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:649 f1fc599201524c6da119c496357508d4 -msgid "" -"When a route fails, a routing update is sent to withdraw the route from the " -"network's routing tables. When the route is re-enabled, the change in " -"availability is also advertised. A route that continually fails and returns " -"requires a great deal of network traffic to update the network about the " -"route's status." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:655 18909836b5494a5097a871203947e615 -msgid "" -"Route dampening wich described in :rfc:`2439` enables you to identify routes" -" that repeatedly fail and return. If route dampening is enabled, an unstable" -" route accumulates penalties each time the route fails and returns. If the " -"accumulated penalties exceed a threshold, the route is no longer advertised." -" This is route suppression. Routes that have been suppressed are re-entered " -"into the routing table only when the amount of their penalty falls below a " -"threshold." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:663 f4e5e2fa78674adfbd974c80fbefc86b -msgid "" -"A penalty of 1000 is assessed each time the route fails. When the penalties " -"reach a predefined threshold (suppress-value), the router stops advertising " -"the route." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:667 6ad1f2094ab6499b83b6cc1139163b04 -msgid "" -"Once a route is assessed a penalty, the penalty is decreased by half each " -"time a predefined amount of time elapses (half-life-time). When the " -"accumulated penalties fall below a predefined threshold (reuse-value), the " -"route is unsuppressed and added back into the BGP routing table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:672 58f0b17df9ed4303848b6f822d13af83 -msgid "" -"No route is suppressed indefinitely. Maximum-suppress-time defines the " -"maximum time a route can be suppressed before it is re-advertised." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:678 6749f62fb5d94d8281c9fa26e3821060 -msgid "" -"This command defines the amount of time in minutes after which a penalty is " -"reduced by half. The timer range is 10 to 45 minutes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:685 dbc7c81aaf0c458bb4d4c9dad95da93c -msgid "" -"This command defines the accumulated penalty amount at which the route is " -"re-advertised. The penalty range is 1 to 20000." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:691 8c4aa12c57d04429a54cf370fef64ddf -msgid "" -"This command defines the accumulated penalty amount at which the route is " -"suppressed. The penalty range is 1 to 20000." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:697 25a3ae4e51c648698ddb18dbcf2da1e3 -msgid "" -"This command defines the maximum time in minutes that a route is suppressed." -" The timer range is 1 to 255 minutes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:702 f24ff89c58f74ec4834ed1e09eee58a1 -msgid "Route Selection Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:706 9960856495d244e5bb0f7069247459fc -msgid "" -"This command provides to compare the MED on routes, even when they were " -"received from different neighbouring ASes. Setting this option makes the " -"order of preference of routes more defined, and should eliminate MED induced" -" oscillations." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:713 4626adf0da554a91bdaba6bb6d6f3c8b -msgid "" -"This command specifies that the length of confederation path sets and " -"sequences should be taken into account during the BGP best path decision " -"process." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:719 d2e92d13aa0e47c08a1a2534a9ed5fd8 -msgid "" -"This command specifies that BGP decision process should consider paths of " -"equal AS_PATH length candidates for multipath computation. Without the knob," -" the entire AS_PATH must match for multipath computation." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:725 81971dcd8ea246918f85a6542427fbe6 -msgid "Ignore AS_PATH length when selecting a route" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:729 ffc9b69a1152457ab5647927cd86505c -msgid "" -"Ensure that when comparing routes where both are equal on most metrics, " -"including local-pref, AS_PATH length, IGP cost, MED, that the tie is broken " -"based on router-ID." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:733 4ba8a6fa31b2416ca32cd65b16f6cf55 -msgid "" -"If this option is enabled, then the already-selected check, where already " -"selected eBGP routes are preferred, is skipped." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:736 927c4932dbbc488a810990f9ce43b29c -msgid "" -"If a route has an ORIGINATOR_ID attribute because it has been reflected, " -"that ORIGINATOR_ID will be used. Otherwise, the router-ID of the peer the " -"route was received from will be used." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:740 071d53b8f0794a1a9bdbcabfbec7bdd9 -msgid "" -"The advantage of this is that the route-selection (at this point) will be " -"more deterministic. The disadvantage is that a few or even one lowest-ID " -"router may attract all traffic to otherwise-equal paths because of this " -"check. It may increase the possibility of MED or IGP oscillation, unless " -"other measures were taken to avoid these. The exact behaviour will be " -"sensitive to the iBGP and reflection topology." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:749 b387655c6c1d47ebb80dadf515cd9c1f -msgid "" -"This command specifies that BGP considers the MED when comparing routes " -"originated from different sub-ASs within the confederation to which this BGP" -" speaker belongs. The default state, where the MED attribute is not " -"considered." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:756 b19035d9e7f04a1fadd64b0c9ebf51c3 -msgid "" -"This command specifies that a route with a MED is always considered to be " -"better than a route without a MED by causing the missing MED attribute to " -"have a value of infinity. The default state, where the missing MED attribute" -" is considered to have a value of zero." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:764 55b6432330094057bfba140eef0383c0 -msgid "" -"This command specifies the default local preference value. The local " -"preference range is 0 to 4294967295." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:769 5ccad8c4a380413da39df1595f31513f -msgid "" -"This command provides to compare different MED values that advertised by " -"neighbours in the same AS for routes selection. When this command is " -"enabled, routes from the same autonomous system are grouped together, and " -"the best entries of each group are compared." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:777 dbefb5d56a084929a2358730f41f50c7 -msgid "" -"This command allows the router to prefer route to specified prefix learned " -"via IGP through backdoor link instead of a route to the same prefix learned " -"via EBGP." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:783 b3e3841f85734c658f583030e08f4c93 -msgid "Route Filtering Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:785 b6b74c3ef31a441fa39fbecd34830637 -msgid "" -"In order to control and modify routing information that is exchanged between" -" peers you can use route-map, filter-list, prefix-list, distribute-list." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:788 38dde1a43da64beaba49f4a06f116f44 -msgid "For inbound updates the order of preference is:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:790 -#: ../../configuration/protocols/bgp.rst:798 5de18d5c507744b4856b1b44d6bdc460 -#: de1b132c815941e882eae88478c15bff -msgid "route-map" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:791 -#: ../../configuration/protocols/bgp.rst:797 2798a65fff24422ba8cc3b810311234e -#: 7c7832157ffc48c6a502f775919e4467 -msgid "filter-list" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:792 -#: ../../configuration/protocols/bgp.rst:796 67ec130833ee4161a0de71285ca5a014 -#: 72ad7a67c18d4463ad9e2a018d785085 -msgid "prefix-list, distribute-list" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:794 17a4794992f048ef843447ff444bc67f -msgid "For outbound updates the order of preference is:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:800 ce9ebff32edd47d5accb25273b71c3c0 -msgid "" -"The attributes :cfgcmd:`prefix-list` and :cfgcmd:`distribute-list` are " -"mutually exclusive, and only one command (distribute-list or prefix-list) " -"can be applied to each inbound or outbound direction for a particular " -"neighbor." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:808 10a479741101408eb31e1ca29c726070 -msgid "" -"This command applies the access list filters named in <number> to the " -"specified BGP neighbor to restrict the routing information that BGP learns " -"and/or advertises. The arguments :cfgcmd:`export` and :cfgcmd:`import` " -"specify the direction in which the access list are applied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:816 17deb79682fe48a18fd104910057cd85 -msgid "" -"This command applies the prfefix list filters named in <name> to the " -"specified BGP neighbor to restrict the routing information that BGP learns " -"and/or advertises. The arguments :cfgcmd:`export` and :cfgcmd:`import` " -"specify the direction in which the prefix list are applied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:824 08d10ff6ae2f4b81a0fa57bb619a1b7e -msgid "" -"This command applies the route map named in <name> to the specified BGP " -"neighbor to control and modify routing information that is exchanged between" -" peers. The arguments :cfgcmd:`export` and :cfgcmd:`import` specify the " -"direction in which the route map are applied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:832 8464caf8fb6a4e5f91a596545e3e00a2 -msgid "" -"This command applies the AS path access list filters named in <name> to the " -"specified BGP neighbor to restrict the routing information that BGP learns " -"and/or advertises. The arguments :cfgcmd:`export` and :cfgcmd:`import` " -"specify the direction in which the AS path access list are applied." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:840 c7c14eefa0c04583aefbf521f370eaea -msgid "" -"This command enables the ORF capability (described in :rfc:`5291`) on the " -"local router, and enables ORF capability advertisement to the specified BGP " -"peer. The :cfgcmd:`receive` keyword configures a router to advertise ORF " -"receive capabilities. The :cfgcmd:`send` keyword configures a router to " -"advertise ORF send capabilities. To advertise a filter from a sender, you " -"must create an IP prefix list for the specified BGP peer applied in inbound " -"derection." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:850 b10f0fc629c54d46add3cd1466b38340 -msgid "" -"This command prevents from sending back prefixes learned from the neighbor." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:853 83cedaa6d5f049559314c683aa88465f -msgid "BGP Scaling Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:855 0c075ff6fefb4528b63cfa7ba8c67ba5 -msgid "" -"BGP routers connected inside the same AS through BGP belong to an internal " -"BGP session, or IBGP. In order to prevent routing table loops, IBGP speaker " -"does not advertise IBGP-learned routes to other IBGP speaker (Split Horizon " -"mechanism). As such, IBGP requires a full mesh of all peers. For large " -"networks, this quickly becomes unscalable." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:861 3cc93c6b81fb46b6ac54352e13d5c1d7 -msgid "" -"There are two ways that help us to mitigate the BGPs full-mesh requirement " -"in a network:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:864 a5866b9ee6ba4423a82eba1063920aff -msgid "Using BGP route-reflectors" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:865 0bb4f88f06264e3d8362fdbbc1c3ca30 -msgid "Using BGP confederation" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:869 b52e75bc25694af69287a5893007127f -msgid "Route Reflector Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:871 87fd2839690f465ebed630a9198083a5 -msgid "" -"Introducing route reflectors removes the need for the full-mesh. When you " -"configure a route reflector you have to tell the router whether the other " -"IBGP router is a client or non-client. A client is an IBGP router that the " -"route reflector will “reflect” routes to, the non-client is just a regular " -"IBGP neighbor. Route reflectors mechanism is described in :rfc:`4456` and " -"updated by :rfc:`7606`." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:881 1fc5e2121adc461f8d718adbfb0c740d -msgid "This command specifies the given neighbor as route reflector client." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:885 2b9ae6a2c4914c5c8e4e51e88313a996 -msgid "" -"This command specifies cluster ID which identifies a collection of route " -"reflectors and their clients, and is used by route reflectors to avoid " -"looping. By default cluster ID is set to the BGP router id value, but can be" -" set to an arbitrary 32-bit value." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:892 04fd1fb075b740f2ba2760ad76dc56e4 -msgid "Confederation Configuration" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:894 72b80a118fb64ac88cb026eea9539f71 -msgid "" -"A BGP confederation divides our AS into sub-ASes to reduce the number of " -"required IBGP peerings. Within a sub-AS we still require full-mesh IBGP but " -"between these sub-ASes we use something that looks like EBGP but behaves " -"like IBGP (called confederation BGP). Confederation mechanism is described " -"in :rfc:`5065`" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:903 8e1df305faa54cadb0d940ccf3ab8973 -msgid "" -"This command specifies a BGP confederation identifier. <asn> is the number " -"of the autonomous system that internally includes multiple sub-autonomous " -"systems (a confederation)." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:910 672f0f87fb7b44918c28136b10a77656 -msgid "" -"This command sets other confederations <nsubasn> as members of autonomous " -"system specified by :cfgcmd:`confederation identifier <asn>`." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:916 6b6fd1baf39f4212aa2052fd2da7c6ee -msgid "Operational Mode Commands" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:919 d0c237d7d6cc453ea080663d23579f8e -msgid "Show" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:923 f77556ffc65149c3b37017e2cfa96111 -msgid "This command displays all entries in BGP routing table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:942 48ec820d1125491895858805acf19eb5 -msgid "" -"This command displays information about the particular entry in the BGP " -"routing table." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:958 ff8aa79c29ed474780e6a3fa71a081a5 -msgid "" -"This command displays routes with classless interdomain routing (CIDR)." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:962 554841e0625f49e89f01dd4330bb2418 -msgid "" -"This command displays routes that belong to specified BGP communities. Valid" -" value is a community number in the range from 1 to 4294967200, or AA:NN " -"(autonomous system-community number/2-byte number), no-export, local-as, or " -"no-advertise." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:969 7618a5458feb4af0bea2cedeaf56fa3b -msgid "" -"This command displays routes that are permitted by the BGP community list." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:974 ce02c4e5e7a5403f9b9f1bbb46815dcf -msgid "This command displays BGP dampened routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:978 594a203a72584e0cbc538dd638f06bcf -msgid "This command displays information about flapping BGP routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:982 442559a1f69847d6aa7c324693d5d0f9 -msgid "" -"This command displays BGP routes allowed by the specified AS Path access " -"list." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:987 a54c21abb6224e44b2ffd9d1b3e8d754 -msgid "This command displays BGP routes advertised to a neighbor." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:991 5ed25bd1e09046fd8f05ea4e823e2928 -msgid "" -"This command displays BGP routes originating from the specified BGP neighbor" -" before inbound policy is applied. To use this command inbound soft " -"reconfiguration must be enabled." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:997 a62d4d6812984420bf2bb17324c03e14 -msgid "" -"This command displays BGP received-routes that are accepted after filtering." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1001 776015ab58b94e3dbb8f2027d9eda652 -msgid "This command displays dampened routes received from BGP neighbor." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1005 1d03e5f85a10462bafe5b79204d4354e -msgid "" -"This command displays information about BGP routes whose AS path matches the" -" specified regular expression." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1010 2875cc14bd3540dabfa5622f14effb88 -msgid "This command displays the status of all BGP connections." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1029 0ba07f9dd2f54e25935c3492e4c90c36 -msgid "Reset" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1033 0144db1c435c4392ba8bd8f7ec7494f5 -msgid "" -"This command resets BGP connections to the specified neighbor IP address. " -"With argument :cfgcmd:`soft` this command initiates a soft reset. If you do " -"not specify the :cfgcmd:`in` or :cfgcmd:`out` options, both inbound and " -"outbound soft reconfiguration are triggered." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1040 e444912425014fe8b2630fc1c2976852 -msgid "This command resets all BGP connections of given router." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1044 2cf4c25cdbac4880bfe0c746678ced4b -msgid "" -"This command uses to clear BGP route dampening information and to unsuppress" -" suppressed routes." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1049 46e84d0a82ab445da14a886edb0d7c0e -msgid "This command resets all external BGP peers of given router." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1053 f39f857afb29442695df738be7ac13c5 -msgid "" -"This command resets BGP connections to the specified peer group. With " -"argument :cfgcmd:`soft` this command initiates a soft reset. If you do not " -"specify the :cfgcmd:`in` or :cfgcmd:`out` options, both inbound and outbound" -" soft reconfiguration are triggered." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1061 630744fe88744341ada8d5b7eeb23173 -msgid "Examples" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1064 5ee6adc7b7a447c68e314aecce5de621 -msgid "IPv4 peering" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1066 a98b9028d05045109967ac0fc0af26e3 -msgid "A simple eBGP configuration:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1068 -#: ../../configuration/protocols/bgp.rst:1095 -#: ../../configuration/protocols/bgp.rst:1113 -#: ../../configuration/protocols/bgp.rst:1141 ace2389cedcb487cbb728cc7f7505a77 -#: 99093296d76f4b9e87225fb3d8b8813b 529ccf0aa77443b5b5821f391d1d137b -#: 8959f0acbbda43b782310cafec53c9b8 -msgid "**Node 1:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1079 -#: ../../configuration/protocols/bgp.rst:1101 -#: ../../configuration/protocols/bgp.rst:1125 -#: ../../configuration/protocols/bgp.rst:1147 48fa51a31ced499cbe2f53613608f9b5 -#: 8a00fb640c7d4046955d28ecafd0c043 fae3c43c9a5140fda11f8da762fb3745 -#: 1aec69c3d67d449d9ba7cf14528aaca2 -msgid "**Node 2:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1091 4df50b8d6fe8476cb7be34ebb481facb -msgid "" -"Don't forget, the CIDR declared in the network statement MUST **exist in " -"your routing table (dynamic or static), the best way to make sure that is " -"true is creating a static route:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1109 e9cd37392ea54b7f94e13056943f2464 -msgid "IPv6 peering" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1111 bb6216deb2e041bdba589efd3821a230 -msgid "A simple BGP configuration via IPv6." -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1137 c1e4545cb8654091b56c51850e85c78f -msgid "" -"Don't forget, the CIDR declared in the network statement **MUST exist in " -"your routing table (dynamic or static), the best way to make sure that is " -"true is creating a static route:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1154 204805ab5e4848e38ea07a5fac972a1f -msgid "Route Filtering" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1156 194728a7a62f422a9c954c887e57f02a -msgid "Route filter can be applied using a route-map:" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1158 7005f4db47e24dfdb09b16f34a2f514d -msgid "**Node1:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1186 4457206aad1e43f28af56b378b3fd1c9 -msgid "**Node2:**" -msgstr "" - -#: ../../configuration/protocols/bgp.rst:1214 fed512de983c4f858d9a2e3f0c52bb5c -msgid "" -"We could expand on this and also deny link local and multicast in the rule " -"20 action deny." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/igmp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/igmp.po deleted file mode 100644 index d527da29..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/igmp.po +++ /dev/null @@ -1,259 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/igmp.rst:7 73170b0524e84e909efd5d193436e306 -msgid "Multicast" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:9 f96ce9ad4fe84d10ad5e7eff17ff4e3b -msgid "" -"VyOS facilitates IP Multicast by supporting **PIM Sparse Mode**, **IGMP** " -"and **IGMP-Proxy**." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:14 0fdd2bf63a8343ae9a5a0d72a9cc3c63 -msgid "PIM and IGMP" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:16 4ea16075d11c4e4db86a05694ca6fc82 -msgid "" -"PIM (Protocol Independent Multicast) must be configured in every interface " -"of every participating router. Every router must also have the location of " -"the Rendevouz Point manually configured. Then, unidirectional shared trees " -"rooted at the Rendevouz Point will automatically be built for multicast " -"distribution." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:22 aef5c28fd1a54905b814d9d70dd6b60c -msgid "" -"Traffic from multicast sources will go to the Rendezvous Point, and " -"receivers will pull it from a shared tree using IGMP (Internet Group " -"Management Protocol)." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:26 60422c65d7be4e7bb930547e55500c35 -msgid "" -"Multicast receivers will talk IGMP to their local router, so, besides having" -" PIM configured in every router, IGMP must also be configured in any router " -"where there could be a multicast receiver locally connected." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:30 6ec1b3c2b56240c7aad3f1660166d90c -msgid "" -"VyOS supports both IGMP version 2 and version 3 (which allows source-" -"specific multicast)." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:35 -#: ../../configuration/protocols/igmp.rst:233 056585cb054f40fab1676ef96518255f -#: d9b9278ab3554f69b10646766da4153a -msgid "Example" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:37 1d03bafd27e2451e969aad97e3d10187 -msgid "In the following example we can see a basic multicast setup:" -msgstr "" - -#: ../../configuration/protocols/igmp.rstNone a01fe8a799ff4dd7ad87f6b049acfdbd -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:46 cb0856f0a32b4bf193eaecff7ec0d821 -msgid "**Router 1**" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:59 979e527ff5b0426b912a237a6c0ccc25 -msgid "**Router 3**" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:74 2b47ec89cbd84c2794958adf2f7f2dbc -msgid "**Router 2**" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:91 02b04aded9f746e5a8c00452d76056ec -msgid "Basic commands" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:93 e44a018c63c246d7a679109a8e875665 -msgid "These are the commands for a basic setup." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:97 f85930e3ed584348ada9abf3e02abd17 -msgid "" -"Use this command to enable PIM in the selected interface so that it can " -"communicate with PIM neighbors." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:104 930d2957bbc845a491ef0d7d7c06ff94 -msgid "" -"Use this command to manually configure a Rendezvous Point for PIM so that " -"join messages can be sent there. Set the Rendevouz Point address and the " -"matching prefix of group ranges covered. These values must be shared with " -"every router participating in the PIM network." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:112 08e1160f8f3d40ae8845f6cb0f720c9c -msgid "" -"Use this command to configure an interface with IGMP so that PIM can receive" -" IGMP reports and query on the selected interface. By default IGMP version 3" -" will be used." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:119 466b080ac0e4450492cae297012b1fcc -msgid "Tuning commands" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:121 1585de73aa944260a2b7c22b540ffba3 -msgid "You can also tune multicast with the following commands." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:125 051f73cb374843a9a5c3bf72998dae20 -msgid "" -"Use this PIM command in the selected interface to set the priority " -"(1-4294967295) you want to influence in the election of a node to become the" -" Designated Router for a LAN segment. The default priority is 1, set a " -"higher value to give the router more preference in the DR election process." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:134 7053461d00b6473f873cf45081236976 -msgid "" -"Use this command to configure the PIM hello interval in seconds (1-180) for " -"the selected interface." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:140 6f62dd225ef642fa893868afc9cb5b44 -msgid "" -"Use this PIM command to modify the time out value (31-60000 seconds) for an " -"`(S,G) <https://tools.ietf.org/html/rfc7761#section-4.1>`_ flow. 31 seconds " -"is chosen for a lower bound as some hardware platforms cannot see data " -"flowing in better than 30 seconds chunks." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:149 9541bf37e9654d35ac179d280927120d -msgid "" -"Use this command to allow the selected interface to join a multicast group " -"defining the multicast address you want to join and the source IP address " -"too." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:156 62a1eb5df1194d0f9c1aa107b274d588 -msgid "" -"Use this command to configure in the selected interface the IGMP host query " -"interval (1-1800) in seconds that PIM will use." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:163 f719c69f858341b4be984a74c1a1b48b -msgid "" -"Use this command to configure in the selected interface the IGMP query " -"response timeout value (10-250) in deciseconds. If a report is not returned " -"in the specified time, it will be assumed the `(S,G) or (*,G) state " -"<https://tools.ietf.org/html/rfc7761#section-4.1>`_ has timed out." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:172 62eb3f5c3734455dab46145b85d8be7c -msgid "" -"Use this command to define in the selected interface whether you choose IGMP" -" version 2 or 3. The default value is 3." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:179 4c819df06e6c499cb3e8a9bba197b37c -msgid "IGMP Proxy" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:181 f90796cb941b47528f931affc3989d8c -msgid "" -":abbr:`IGMP (Internet Group Management Protocol)` proxy sends IGMP host " -"messages on behalf of a connected client. The configuration must define one," -" and only one upstream interface, and one or more downstream interfaces." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:186 d5cc85b57d8b400e861707597f6225e9 -msgid "Configuration" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:191 de064b4174854df482039e09b59e8cc3 -msgid "" -"**upstream:** The upstream network interface is the outgoing interface which" -" is responsible for communicating to available multicast data sources. There" -" can only be one upstream interface." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:195 9e94544404fd4a55a2dad363c335e4c4 -msgid "" -"**downstream:** Downstream network interfaces are the distribution " -"interfaces to the destination networks, where multicast clients can join " -"groups and receive multicast data. One or more downstream interfaces must be" -" configured." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:202 5869fcca67ae4ac4ae0841b192acafe1 -msgid "" -"Defines alternate sources for multicasting and IGMP data. The network " -"address must be on the following format 'a.b.c.d/n'. By default, the router " -"will accept data from sources on the same network as configured on an " -"interface. If the multicast source lies on a remote network, one must define" -" from where traffic should be accepted." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:208 cffbb03d247a4b57856e5a6d60330691 -msgid "" -"This is especially useful for the upstream interface, since the source for " -"multicast traffic is often from a remote location." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:211 74aeef7f75e74b2ba59c9b590f090c16 -msgid "This option can be supplied multiple times." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:215 16a2dc59682f4f9694955dbe22c2664c -msgid "" -"Disables quickleave mode. In this mode the daemon will not send a Leave IGMP" -" message upstream as soon as it receives a Leave message for any downstream " -"interface. The daemon will not ask for Membership reports on the downstream " -"interfaces, and if a report is received the group is not joined again the " -"upstream." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:221 ffc46e1ae57f4cdc871aa352a623d9f5 -msgid "" -"If it's vital that the daemon should act exactly like a real multicast " -"client on the upstream interface, this function should be enabled." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:224 cedb77b217b54e02893243d7452e1d9c -msgid "Enabling this function increases the risk of bandwidth saturation." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:228 622cb2d280c1450fb2d2bb196a0f4f92 -msgid "Disable this service." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:235 49f590bac93b42a0ba96457016d9bd87 -msgid "" -"Interface `eth1` LAN is behind NAT. In order to subscribe `10.0.0.0/23` " -"subnet multicast which is in `eth0` WAN we need to configure igmp-proxy." -msgstr "" - -#: ../../configuration/protocols/igmp.rst:245 7f937de509164566a36c120ac99ebce8 -msgid "Operation" -msgstr "" - -#: ../../configuration/protocols/igmp.rst:249 2d344d86d4934459bb5bbe631f2034b7 -msgid "Restart the IGMP proxy process." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/index.po deleted file mode 100644 index 4fb4f883..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/index.rst:3 e0d55099b582444faaddcd2a2709ea20 -msgid "Protocols" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/isis.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/isis.po deleted file mode 100644 index c25f92ca..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/isis.po +++ /dev/null @@ -1,338 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../_include/need_improvement.txt:11 25be2429befb4076a9297e2bea64b5e8 -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 95810b9d23a94b699fcf91c00f27cdf4 -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/protocols/isis.rst:7 ce1df8d9d31345b3913cc008754e0080 -msgid "IS-IS" -msgstr "" - -#: ../../configuration/protocols/isis.rst:9 2a50bb040af3403b8e90f0b284795ee2 -msgid "" -":abbr:`IS-IS (Intermediate System to Intermediate System)` is a link-state " -"interior gateway routing protocol which is described in ISO10589, " -":rfc:`1195`, :rfc:`5308`. Like OSPF, IS-IS runs the Dijkstra shortest-path " -"first (SPF) algorithm to create a database of the network’s topology and, " -"from that database, to determine the best (that is, shortest) path to a " -"destination. The routers exchange topology information with their nearest " -"neighbors. IS-IS runs directly on the data link layer (Layer 2). IS-IS " -"addresses are called :abbr:`NETs (Network Entity Titles)` and can be 8 to 20" -" bytes long, but are generally 10 bytes long." -msgstr "" - -#: ../../configuration/protocols/isis.rst:21 15d4da431bfd4c50b04b2a0977cf878e -msgid "General" -msgstr "" - -#: ../../configuration/protocols/isis.rst:24 64721c775c4b4e039b2e61e1fbdd45eb -msgid "Configuration" -msgstr "" - -#: ../../configuration/protocols/isis.rst:27 8846222fab694564ae24ba27d811c4df -msgid "Mandatory Settings" -msgstr "" - -#: ../../configuration/protocols/isis.rst:31 995badb93bd24eb0a55c79791018cb4c -msgid "" -"This commad also sets network entity title (NET) provided in ISO format." -msgstr "" - -#: ../../configuration/protocols/isis.rst:33 661d296504494f9a8a30f4ba31fc4609 -msgid "For example :abbr:`NET (Network Entity Title)`" -msgstr "" - -#: ../../configuration/protocols/isis.rst:39 af651ea25b2f4c0a8fd4080fb8520435 -msgid "The IS-IS address consists of the following parts:" -msgstr "" - -#: ../../configuration/protocols/isis.rst:41 08b4e7ac72484d32b4afc23e18340eac -msgid "" -":abbr:`AFI (Address family authority identifier)` - ``49`` The AFI value 49 " -"is what IS-IS uses for private addressing." -msgstr "" - -#: ../../configuration/protocols/isis.rst:44 89cd3285e6ad4f43be4bac6d0375d184 -msgid "Area identifier: ``0001`` IS-IS area number (Area1)" -msgstr "" - -#: ../../configuration/protocols/isis.rst:46 41f025b9cfe54ccb95e086285bbc0574 -msgid "" -"System identifier: ``1921.6800.1002`` - for system idetifiers we recommend " -"to use IP address or MAC address of the router itself." -msgstr "" - -#: ../../configuration/protocols/isis.rst:49 a4e5e01e06494acb9be4b3877e36d3be -msgid "NET selector: ``00`` Must always be 00, to indicate \"this system\"." -msgstr "" - -#: ../../configuration/protocols/isis.rst:53 0bae8b56cfcd4b15922eeffff785f3b7 -msgid "" -"This command activates ISIS adjacency on this interface. Note that the name " -"of ISIS instance must be the same as the one used to configure the ISIS " -"process." -msgstr "" - -#: ../../configuration/protocols/isis.rst:59 1a02bbf02fd1453f89e108e145c1eb95 -msgid "" -"This command enables support for dynamic hostname. Dynamic hostname mapping " -"determined as described in :rfc:`2763`, Dynamic Hostname Exchange Mechanism " -"for IS-IS." -msgstr "" - -#: ../../configuration/protocols/isis.rst:65 39747e42f1bb4c098cb38675cbc32cf0 -msgid "This command defines the ISIS router behavior:" -msgstr "" - -#: ../../configuration/protocols/isis.rst:67 b05f7aac1d3045c8a9bc85455c3e0609 -msgid "" -"**level-1** Act as a station router only. **level-1-2** Act as both a " -"station router and an area router. **level-2-only** Act as an area router " -"only." -msgstr "" - -#: ../../configuration/protocols/isis.rst:73 9ec3d8145e5b40d7a2e61aaf8da3c43b -msgid "" -"This command configures the maximum size of generated LSPs, in bytes. The " -"size range is 128 to 4352." -msgstr "" - -#: ../../configuration/protocols/isis.rst:78 4842250b02af4e7b8c4af3bc5a7c1884 -msgid "This command sets old-style (ISO 10589) or new-style packet formats:" -msgstr "" - -#: ../../configuration/protocols/isis.rst:80 1acb3cff4d65498888f7a56834af2c29 -msgid "" -"**narrow** Use old style of TLVs with narrow metric. **transition** Send and" -" accept both styles of TLVs during transition. **wide** Use new style of " -"TLVs to carry wider metric." -msgstr "" - -#: ../../configuration/protocols/isis.rst:86 ea58c836ea7f4ea4a539cf208feb630c -msgid "" -"This command enables :rfc:`6232` purge originator identification. Enable " -"purge originator identification (POI) by adding the type, length and value " -"(TLV) with the Intermediate System (IS) identification to the LSPs that do " -"not contain POI information. If an IS generates a purge, VyOS adds this TLV " -"with the system ID of the IS to the purge." -msgstr "" - -#: ../../configuration/protocols/isis.rst:94 d066f41614884b16a229b99bf880e708 -msgid "" -"This command sets ATT bit to 1 in Level1 LSPs. It is described in " -":rfc:`3787`." -msgstr "" - -#: ../../configuration/protocols/isis.rst:98 3ceb67d4da784f068cc557f1c02a4e80 -msgid "" -"This command sets overload bit to avoid any transit traffic through this " -"router. It is described in :rfc:`3787`." -msgstr "" - -#: ../../configuration/protocols/isis.rst:104 b3cb08934c4a4c37a14fca43d7f6e96a -msgid "This command will generate a default-route in L1 database." -msgstr "" - -#: ../../configuration/protocols/isis.rst:109 9e46f39bb2094664aeee3035dac9d83b -msgid "This command will generate a default-route in L2 database." -msgstr "" - -#: ../../configuration/protocols/isis.rst:113 b3ba02a1f2fa48338d7660fc1f938861 -msgid "Interface Configuration" -msgstr "" - -#: ../../configuration/protocols/isis.rst:118 46359d83cee64c8ba0e089246e9a5343 -msgid "This command specifies circuit type for interface:" -msgstr "" - -#: ../../configuration/protocols/isis.rst:120 a5b222eb7f64415596e72587eed3f761 -msgid "**level-1** Level-1 only adjacencies are formed." -msgstr "" - -#: ../../configuration/protocols/isis.rst:121 42a50dbba4224ef996bf1d5a1b6fa05a -msgid "**level-1-2** Level-1-2 adjacencies are formed" -msgstr "" - -#: ../../configuration/protocols/isis.rst:122 ca1b7f5659864bfab83f282cd29825e8 -msgid "**level-2-only** Level-2 only adjacencies are formed" -msgstr "" - -#: ../../configuration/protocols/isis.rst:127 e7af8645a39747f4974e1838a0d7f7f5 -msgid "" -"This command sets hello interval in seconds on a given interface. The range " -"is 1 to 600." -msgstr "" - -#: ../../configuration/protocols/isis.rst:133 de4cead92ce6404aaded28f81b055f7a -msgid "" -"This command sets multiplier for hello holding time on a given interface. " -"The range is 2 to 100." -msgstr "" - -#: ../../configuration/protocols/isis.rst:138 44bd1903e60e48ceb960d92c5a4ee140 -msgid "" -"This command configures padding on hello packets to accommodate asymmetrical" -" maximum transfer units (MTUs) from different hosts as described in " -":rfc:`3719`. This helps to prevent a premature adjacency Up state when one " -"routing devices MTU does not meet the requirements to establish the " -"adjacency." -msgstr "" - -#: ../../configuration/protocols/isis.rst:145 b7e9677f226a46658fe7c5feb6a89da0 -msgid "This command set default metric for circuit." -msgstr "" - -#: ../../configuration/protocols/isis.rst:147 ebc7128a9ad1418297b1237d1bbb852e -msgid "" -"The metric range is 1 to 16777215 (Max value depend if metric support narrow" -" or wide value)." -msgstr "" - -#: ../../configuration/protocols/isis.rst:153 d5f0fd3388f04102932b8cec243916f7 -msgid "" -"This command specifies network type to Point-to-Point. The default network " -"type is broadcast." -msgstr "" - -#: ../../configuration/protocols/isis.rst:158 41d0f4766b194b3bba11329069f9a3e6 -msgid "This command configures the passive mode for this interface." -msgstr "" - -#: ../../configuration/protocols/isis.rst:163 c97299de9670478abc4cc7d4ed5e502e -msgid "This command configures the authentication password for the interface." -msgstr "" - -#: ../../configuration/protocols/isis.rst:167 2360dab3d738425da25c02e35d7d4bae -msgid "" -"This command sets priority for the interface for :abbr:`DIS (Designated " -"Intermediate System)` election. The priority range is 0 to 127." -msgstr "" - -#: ../../configuration/protocols/isis.rst:174 9b9272f8f8904ff1a8d03510d1cfca8c -msgid "" -"This command sets PSNP interval in seconds. The interval range is 0 to 127." -msgstr "" - -#: ../../configuration/protocols/isis.rst:180 0a404b0341a647659d182dbd56ec04b8 -msgid "" -"This command disables Three-Way Handshake for P2P adjacencies which " -"described in :rfc:`5303`. Three-Way Handshake is enabled by default." -msgstr "" - -#: ../../configuration/protocols/isis.rst:185 5d1a331dd5b8492d99c2e159ed1b747d -msgid "Route Redistribution" -msgstr "" - -#: ../../configuration/protocols/isis.rst:189 7365777855374a8aa34753f7bd7bd6a4 -msgid "" -"This command redistributes routing information from the given route source " -"into the ISIS database as Level-1. There are six modes available for route " -"source: bgp, connected, kernel, ospf, rip, static." -msgstr "" - -#: ../../configuration/protocols/isis.rst:195 ca42504d69d54eb6823f946ffe2404bd -msgid "" -"This command redistributes routing information from the given route source " -"into the ISIS database as Level-2. There are six modes available for route " -"source: bgp, connected, kernel, ospf, rip, static." -msgstr "" - -#: ../../configuration/protocols/isis.rst:202 a6f21f4746cc4cfd919e2637ad8fe221 -msgid "" -"This command specifies metric for redistributed routes from the given route " -"source. There are six modes available for route source: bgp, connected, " -"kernel, ospf, rip, static. The metric range is 1 to 16777215." -msgstr "" - -#: ../../configuration/protocols/isis.rst:209 af99ee98c2484429be1b9caf32170706 -msgid "" -"This command allows to use route map to filter redistributed routes from the" -" given route source. There are six modes available for route source: bgp, " -"connected, kernel, ospf, rip, static." -msgstr "" - -#: ../../configuration/protocols/isis.rst:215 9f0656f696214654baf286cbcdb3d69d -msgid "Timers" -msgstr "" - -#: ../../configuration/protocols/isis.rst:219 97692bdcaeb3409e91c9ed9b78c28b32 -msgid "" -"This command sets minimum interval in seconds between regenerating same LSP." -" The interval range is 1 to 120." -msgstr "" - -#: ../../configuration/protocols/isis.rst:224 39530b8f812843f59b606c8ea2ae46cc -msgid "" -"This command sets LSP refresh interval in seconds. IS-IS generates LSPs when" -" the state of a link changes. However, to ensure that routing databases on " -"all routers remain converged, LSPs in stable networks are generated on a " -"regular basis even though there has been no change to the state of the " -"links. The interval range is 1 to 65235. The default value is 900 seconds." -msgstr "" - -#: ../../configuration/protocols/isis.rst:233 d2eaaef9028346118e34486041c7e789 -msgid "" -"This command sets LSP maximum LSP lifetime in seconds. The interval range is" -" 350 to 65535. LSPs remain in a database for 1200 seconds by default. If " -"they are not refreshed by that time, they are deleted. You can change the " -"LSP refresh interval or the LSP lifetime. The LSP refresh interval should be" -" less than the LSP lifetime or else LSPs will time out before they are " -"refreshed." -msgstr "" - -#: ../../configuration/protocols/isis.rst:242 3cb73ce94a5e4377af6d406d9cf7412d -msgid "" -"This command sets minimum interval between consecutive SPF calculations in " -"seconds.The interval range is 1 to 120." -msgstr "" - -#: ../../configuration/protocols/isis.rst:259 5ff2c0bb6f0245f08c083c567c2d168c -msgid "" -"This commands specifies the Finite State Machine (FSM) intended to control " -"the timing of the execution of SPF calculations in response to IGP events. " -"The process described in :rfc:`8405`." -msgstr "" - -#: ../../configuration/protocols/isis.rst:266 3247ec7aba244689ba964160fb2c51fb -msgid "Example" -msgstr "" - -#: ../../configuration/protocols/isis.rst:268 ea47fe2759054a2d83f75cfbc7a54df5 -msgid "" -"Simple IS-IS configuration using 2 nodes and redistributing connected " -"interfaces." -msgstr "" - -#: ../../configuration/protocols/isis.rst:271 dbaadd1e5aa2420e98a910debb6a47b8 -msgid "**Node 1:**" -msgstr "" - -#: ../../configuration/protocols/isis.rst:287 125c429537924a8c8a0b99d40eaf97b1 -msgid "**Node 2:**" -msgstr "" - -#: ../../configuration/protocols/isis.rst:296 cb94cb180fc14aab85f32949240fb50c -msgid "Show ip routes on Node2:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/mpls.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/mpls.po deleted file mode 100644 index d3351567..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/mpls.po +++ /dev/null @@ -1,283 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/mpls.rst:5 319f4ed093e842b1a4863b28b0118061 -msgid "MPLS" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:7 b442a9cba1624d00bc1eaaa5b52168ce -msgid "" -":abbr:`MPLS (Multi-Protocol Label Switching)` is a packet forwarding " -"paradigm which differs from regular IP forwarding. Instead of IP addresses " -"being used to make the decision on finding the exit interface, a router will" -" instead use an exact match on a 32 bit/4 byte header called the MPLS label." -" This label is inserted between the ethernet (layer 2) header and the IP " -"(layer 3) header. One can statically or dynamically assign label " -"allocations, but we will focus on dynamic allocation of labels using some " -"sort of label distribution protocol (such as the aptly named Label " -"Distribution Protocol / LDP, Resource Reservation Protocol / RSVP, or " -"Segment Routing through OSPF/ISIS). These protocols allow for the creation " -"of a unidirectional/unicast path called a labeled switched path (initialized" -" as LSP) throughout the network that operates very much like a tunnel " -"through the network. An easy way of thinking about how an MPLS LSP actually " -"forwards traffic throughout a network is to think of a GRE tunnel. They are " -"not the same in how they operate, but they are the same in how they handle " -"the tunneled packet. It would be good to think of MPLS as a tunneling " -"technology that can be used to transport many different types of packets, to" -" aid in traffic engineering by allowing one to specify paths throughout the " -"network (using RSVP or SR), and to generally allow for easier intra/inter " -"network transport of data packets." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:27 f8f4a5215a3f45f6a4a77f529aef6d6a -msgid "" -"For more information on how MPLS label switching works, please go visit " -"`Wikipedia (MPLS)`_." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:30 4c0dadedc2cd448ebe40f433b538b82a -msgid "" -"MPLS support in VyOS is not finished yet, and therefore its functionality is" -" limited. Currently there is no support for MPLS enabled VPN services such " -"as L2VPNs and mVPNs. RSVP support is also not present as the underlying " -"routing stack (FRR) does not implement it. Currently VyOS implements LDP as " -"described in RFC 5036; other LDP standard are the following ones: RFC 6720, " -"RFC 6667, RFC 5919, RFC 5561, RFC 7552, RFC 4447. Because MPLS is already " -"available (FRR also supports RFC 3031)." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:40 30f7d70b0c6d4062b84042fb63b190e1 -msgid "Label Distribution Protocol" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:42 690cebb33f2543ea808b90a14c5eb42b -msgid "" -"The :abbr:`MPLS (Multi-Protocol Label Switching)` architecture does not " -"assume a single protocol to create MPLS paths. VyOS supports the Label " -"Distribution Protocol (LDP) as implemented by FRR, based on :rfc:`5036`." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:46 a37724aac9c44f96bdc7dfde7b50d220 -msgid "" -":abbr:`LDP (Label Distribution Protocol)` is a TCP based MPLS signaling " -"protocol that distributes labels creating MPLS label switched paths in a " -"dynamic manner. LDP is not a routing protocol, as it relies on other routing" -" protocols for forwarding decisions. LDP cannot bootstrap itself, and " -"therefore relies on said routing protocols for communication with other " -"routers that use LDP." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:52 ec5eaa5e950b4f6980d040445ea11c4c -msgid "" -"In order to allow for LDP on the local router to exchange label " -"advertisements with other routers, a TCP session will be established between" -" automatically discovered and statically assigned routers. LDP will try to " -"establish a TCP session to the **transport address** of other routers. " -"Therefore for LDP to function properly please make sure the transport " -"address is shown in the routing table and reachable to traffic at all times." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:59 c19c9c3294cf4cf2be368e67510c87b9 -msgid "" -"It is highly recommended to use the same address for both the LDP router-id " -"and the discovery transport address, but for VyOS MPLS LDP to work both " -"parameters must be explicitly set in the configuration." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:63 66adf3b72958442c8c00b32eba6cf45e -msgid "" -"Another thing to keep in mind with LDP is that much like BGP, it is a " -"protocol that runs on top of TCP. It however does not have an ability to do " -"something like a refresh capability like BGPs route refresh capability. " -"Therefore one might have to reset the neighbor for a capability change or a " -"configuration change to work." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:70 887e2356d4684638bcea4082c72c5806 -msgid "Configuration Options" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:74 27d991948ccd4e69a3e89494377755bf -msgid "" -"Use this command to enable MPLS processing on the interface you define." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:78 e564f28f32c54bd89109ca54f5af78d0 -msgid "Use this command to enable LDP on the interface you define." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:82 7e09356be27844c1ae0a879301a63db8 -msgid "" -"Use this command to configure the IP address used as the LDP router-id of " -"the local device." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:88 66f387c89cc346cf9f8f1af2d8f13f5d -msgid "" -"Use this command to set the IPv4 or IPv6 transport-address used by LDP." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:92 4f964f94611c45efb376052b3164335a -msgid "" -"Use this command to configure authentication for LDP peers. Set the IP " -"address of the LDP peer and a password that should be shared in order to " -"become neighbors." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:98 e8751c8945cd4697aa10dcc93761c124 -msgid "" -"Use this command to configure a specific session hold time for LDP peers. " -"Set the IP address of the LDP peer and a session hold time that should be " -"configured for it. You may have to reset the neighbor for this to work." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:105 4b437814a3c941ccb32d958fd487f32f -msgid "" -"Use this command to enable, disable, or specify hop count for TTL security " -"for LDP peers. By default the value is set to 255 (or max TTL)." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:113 26e7be864fc34d7595d6d17b8be55d97 -msgid "" -"Use these commands if you would like to set the discovery hello and hold " -"time parameters." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:119 34db60e606af4a358fbe6ecedd88afb2 -msgid "" -"Use this command if you would like to set the TCP session hold time " -"intervals." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:126 9a897e652844497d9c132fcd8f50f192 -msgid "" -"Use these commands to control the importing of forwarding equivalence " -"classes (FECs) for LDP from neighbors. This would be useful for example on " -"only accepting the labeled routes that are needed and not ones that are not " -"needed, such as accepting loopback interfaces and rejecting all others." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:136 b3547febc49148c2be2a3325ed0bc52c -msgid "" -"Use these commands to control the exporting of forwarding equivalence " -"classes (FECs) for LDP to neighbors. This would be useful for example on " -"only announcing the labeled routes that are needed and not ones that are not" -" needed, such as announcing loopback interfaces and no others." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:144 d3e93c308b464b3abedfb4419b897dd3 -msgid "" -"Use this command if you would like for the router to advertise FECs with a " -"label of 0 for explicit null operations." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:152 129c4ca317364be986c91893276edac9 -msgid "" -"Use this command if you would like to control the local FEC allocations for " -"LDP. A good example would be for your local router to not allocate a label " -"for everything. Just a label for what it's useful. A good example would be " -"just a loopback label." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:159 eaeb0129ebca49baa962a36232632b6c -msgid "" -"Use this command to use a Cisco non-compliant format to send and interpret " -"the Dual-Stack capability TLV for IPv6 LDP communications. This is related " -"to :rfc:`7552`." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:165 44290a815d6049d287717b2b7f4ee252 -msgid "" -"Use this command to use ordered label distribution control mode. FRR by " -"default uses independent label distribution control mode for label " -"distribution. This is related to :rfc:`5036`." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:171 629dcd86363142d29c851557a5d923aa -msgid "" -"Use this command to prefer IPv4 for TCP peer transport connection for LDP " -"when both an IPv4 and IPv6 LDP address are configured on the same interface." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:177 81b3cb8314db46b6b3cc335eb63b09aa -msgid "" -"Use this command to enable targeted LDP sessions to the local router. The " -"router will then respond to any sessions that are trying to connect to it " -"that are not a link local type of TCP connection." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:184 11a22c4e5f5a411b8996f48891e864f4 -msgid "" -"Use this command to enable the local router to try and connect with a " -"targeted LDP session to another router." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:196 fabf2e7092274fa2811e7baf67268acc -msgid "" -"Use these commands if you would like to set the discovery hello and hold " -"time parameters for the targeted LDP neighbors." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:201 f14cd271d42b4587a2e0aaee6c758f7b -msgid "Sample configuration to setup LDP on VyOS" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:218 3e3387b2d45b437d813d0791a1359b0a -msgid "Operational Mode Commands" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:220 40005f33d4db4eb5b238d9588e609ca6 -msgid "" -"When LDP is working, you will be able to see label information in the " -"outcome of ``show ip route``. Besides that information, there are also " -"specific *show* commands for LDP:" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:225 ee274d5bb9d14eedb26a8515dd1c91e8 -msgid "Show" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:229 2d3af2d78a694e898d1e10113fc9b7e8 -msgid "Use this command to see the Label Information Base." -msgstr "" - -#: ../../configuration/protocols/mpls.rst:233 a655b7a4d1f146ef852f0ede0f0c213c -msgid "Use this command to see discovery hello information" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:237 d20e34bc03ff434dacb9875b902865c1 -msgid "Use this command to see LDP interface information" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:241 ea32f6f53bae47618fcce3cab3628080 -msgid "Use this command to see LDP neighbor information" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:245 d1a837bc74c844db9867fd21794b2ef7 -msgid "Use this command to see detailed LDP neighbor information" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:248 505087f8aa1b4ac8b437e56fdfcb1475 -msgid "Reset" -msgstr "" - -#: ../../configuration/protocols/mpls.rst:252 bcda5b208d564debb7876e865d11eea9 -msgid "" -"Use this command to reset an LDP neighbor/TCP session that is established" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/ospf.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/ospf.po deleted file mode 100644 index aabce07e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/ospf.po +++ /dev/null @@ -1,909 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/ospf.rst:5 be61d874b7254c34941ab334d53c560a -msgid "OSPF" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:7 404fca00e5c44ac1be74b92b958a21e9 -msgid "" -":abbr:`OSPF (Open Shortest Path First)` is a routing protocol for Internet " -"Protocol (IP) networks. It uses a link state routing (LSR) algorithm and " -"falls into the group of interior gateway protocols (IGPs), operating within " -"a single autonomous system (AS). It is defined as OSPF Version 2 in " -":rfc:`2328` (1998) for IPv4. Updates for IPv6 are specified as OSPF Version " -"3 in :rfc:`5340` (2008). OSPF supports the :abbr:`CIDR (Classless Inter-" -"Domain Routing)` addressing model." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:15 e5a8a36ba4f34e49b89e240cfec15ea9 -msgid "OSPF is a widely used IGP in large enterprise networks." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:19 2a3290f75c6a4f13915cda6261719d97 -msgid "OSPFv2 (IPv4)" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:22 -#: ../../configuration/protocols/ospf.rst:784 9b9e9cc283334d198f4734b1d1601bc6 -#: 7c2fb58e39aa43f0a5744f8238c10831 -msgid "Configuration" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:25 -#: ../../configuration/protocols/ospf.rst:789 1de454bde74d40eea02f6de610bca85b -#: e8edc51c75a84edf85ee48c9fcd26bfd -msgid "General" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:27 0de20cb46f3d4c3cb145922486369fe6 -msgid "" -"VyOS does not have a special command to start the OSPF process. The OSPF " -"process starts when the first ospf enabled interface is configured." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:32 b2b8e657fc8c4ef4abf96b63ada8d860 -msgid "" -"This command specifies the OSPF enabled interface(s). If the interface has " -"an address from defined range then the command enables OSPF on this " -"interface so router can provide network information to the other ospf " -"routers via this interface." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:37 10eeebe0b2a546229a358daed76aded9 -msgid "" -"This command is also used to enable the OSPF process. The area number can be" -" specified in decimal notation in the range from 0 to 4294967295. Or it can " -"be specified in dotted decimal notation similar to ip address." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:41 38313e472cd14c11a60466a216e675d2 -msgid "" -"Prefix length in interface must be equal or bigger (i.e. smaller network) " -"than prefix length in network statement. For example statement above doesn't" -" enable ospf on interface with address 192.168.1.1/23, but it does on " -"interface with address 192.168.1.129/25." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:46 0b8d56d4ccec4bb5aa58f581b6d9b50e -msgid "" -"In some cases it may be more convenient to enable OSPF on a per " -"interface/subnet basis :cfgcmd:`set protocols ospf interface <interface> " -"area <x.x.x.x | x>`" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:52 453b886df9ec4fd5ae755bdcac3b54f3 -msgid "" -"This command sets the reference bandwidth for cost calculations, where " -"bandwidth can be in range from 1 to 4294967, specified in Mbits/s. The " -"default is 100Mbit/s (i.e. a link of bandwidth 100Mbit/s or higher will have" -" a cost of 1. Cost of lower bandwidth links will be scaled with reference to" -" this cost)." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:60 5a6560bf4ae241c490b84b64ad95f1d4 -msgid "" -"This command sets the router-ID of the OSPF process. The router-ID may be an" -" IP address of the router, but need not be – it can be any arbitrary 32bit " -"number. However it MUST be unique within the entire OSPF domain to the OSPF " -"speaker – bad things will happen if multiple OSPF speakers are configured " -"with the same router-ID!" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:68 -#: ../../configuration/protocols/ospf.rst:813 33a62e78b3c4426fa0e5b9e74de78f88 -#: e0f7af48e29b491895b103c8d941bdf0 -msgid "Optional" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:73 e80d9334003942e6b91b945dda476851 -msgid "" -"Originate an AS-External (type-5) LSA describing a default route into all " -"external-routing capable areas, of the specified metric and metric type. If " -"the :cfgcmd:`always` keyword is given then the default is always advertised," -" even when there is no default present in the routing table. The argument " -":cfgcmd:`route-map` specifies to advertise the default route if the route " -"map is satisfied." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:82 6ed61a06807b4d828f6835bc0f35eec3 -msgid "" -"This command change distance value of OSPF globally. The distance range is 1" -" to 255." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:88 8d80beb2a9c94ce69e8efef98673148b -msgid "" -"This command change distance value of OSPF. The arguments are the distance " -"values for external routes, inter-area routes and intra-area routes " -"respectively. The distance range is 1 to 255." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:92 926c049a726b4151880a3ee7a335ae7b -msgid "" -"Routes with a distance of 255 are effectively disabled and not installed " -"into the kernel." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:97 2f6aed6842b249f9a4afd897d885930f -msgid "" -"This command allows to log changes in adjacency. With the optional " -":cfgcmd:`detail` argument, all changes in adjacency status are shown. " -"Without :cfgcmd:`detail`, only changes to full or regressions are shown." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:104 a53e57f559774eb0844264877be5a12f -msgid "" -"This enables :rfc:`3137` support, where the OSPF process describes its " -"transit links in its router-LSA as having infinite distance so that other " -"routers will avoid calculating transit paths through the router while still " -"being able to reach networks through the router." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:109 b3e8ab36152d4b9d8df89e740c60589c -msgid "" -"This support may be enabled administratively (and indefinitely) with the " -":cfgcmd:`administrative` command. It may also be enabled conditionally. " -"Conditional enabling of max-metric router-lsas can be for a period of " -"seconds after startup with the :cfgcmd:`on-startup <seconds>` command and/or" -" for a period of seconds prior to shutdown with the :cfgcmd:`on-shutdown " -"<seconds>` command. The time range is 5 to 86400." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:119 741dd4ab7f2b48cd80b8e16d88bc5609 -msgid "This command selects ABR model. OSPF router supports four ABR models:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:121 b8d54022629a4da582d20679edbc90b4 -msgid "" -"**cisco** – a router will be considered as ABR if it has several configured " -"links to the networks in different areas one of which is a backbone area. " -"Moreover, the link to the backbone area should be active (working). **ibm** " -"– identical to \"cisco\" model but in this case a backbone area link may not" -" be active. **standard** – router has several active links to different " -"areas. **shortcut** – identical to \"standard\" but in this model a router " -"is allowed to use a connected areas topology without involving a backbone " -"area for inter-area connections." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:131 5a7d9e90d899439f9712802152f21f54 -msgid "" -"Detailed information about \"cisco\" and \"ibm\" models differences can be " -"found in :rfc:`3509`. A \"shortcut\" model allows ABR to create routes " -"between areas based on the topology of the areas connected to this router " -"but not using a backbone area in case if non-backbone route will be cheaper." -" For more information about \"shortcut\" model, see :t:`ospf-shortcut-" -"abr-02.txt`" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:140 bd7972910e124507ba7b6cefc78781af -msgid "" -":rfc:`2328`, the successor to :rfc:`1583`, suggests according to section G.2" -" (changes) in section 16.4.1 a change to the path preference algorithm that " -"prevents possible routing loops that were possible in the old version of " -"OSPFv2. More specifically it demands that inter-area paths and intra-area " -"backbone path are now of equal preference but still both preferred to " -"external paths." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:147 95b0240454004ab4baf5c13d8f5ab8ad -msgid "This command should NOT be set normally." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:151 -#: ../../configuration/protocols/ospf.rst:895 44ecb673aeef4dc4a73a2a2a4e4dea85 -#: 518fd8170b8240a9b26331afeab20046 -msgid "" -"This command specifies interface as passive. Passive interface advertises " -"its address, but does not run the OSPF protocol (adjacencies are not formed " -"and hello packets are not generated)." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:155 960c7023fcac447fb3b2f7423392d252 -msgid "" -"The optional `disable` option allows to exclude interface from passive " -"state. This command is used if the command :cfgcmd:`passive-interface " -"default` was configured." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:161 0fc3781eb7714085ab677f82ba0dbdf7 -msgid "" -"This command specifies all interfaces as passive by default. Because this " -"command changes the configuration logic to a default passive; therefore, " -"interfaces where router adjacencies are expected need to be configured with " -"the :cfgcmd:`passive-interface-exclude` command." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:168 81f2da9c99ce48da8eb7db4675edf20b -msgid "" -"Use this command to control the maximum number of equal cost paths to reach " -"a specific destination. The upper limit may differ if you change the value " -"of MULTIPATH_NUM during compilation. The default is MULTIPATH_NUM (64)." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:174 a6d13f781e4546f5812bf52ce8d14a07 -msgid "" -"The router automatically updates link-state information with its neighbors. " -"Only an obsolete information is updated which age has exceeded a specific " -"threshold. This parameter changes a threshold value, which by default is " -"1800 seconds (half an hour). The value is applied to the whole OSPF router. " -"The timer range is 10 to 1800." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:183 794c8efd6a4a412da7c2943f6c6531eb -msgid "" -"This command sets the initial delay, the initial-holdtime and the maximum-" -"holdtime between when SPF is calculated and the event which triggered the " -"calculation. The times are specified in milliseconds and must be in the " -"range of 0 to 600000 milliseconds. :cfgcmd:`delay` sets the initial SPF " -"schedule delay in milliseconds. The default value is 200 ms. " -":cfgcmd:`initial-holdtime` sets the minimum hold time between two " -"consecutive SPF calculations. The default value is 1000 ms. :cfgcmd:`max-" -"holdtime` sets the maximum wait time between two consecutive SPF " -"calculations. The default value is 10000 ms." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:195 -#: ../../configuration/protocols/ospf.rst:830 e4a3a6ee09e84df78e3c537cebd1a472 -#: 859f5f1c72f74edda64a0a87c496063f -msgid "Area Configuration" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:199 2a73fc25e04e423f98f6e33deff238f3 -msgid "" -"This command specifies the area to be a Stub Area. That is, an area where no" -" router originates routes external to OSPF and hence an area where all " -"external routes are via the ABR(s). Hence, ABRs for such an area do not need" -" to pass AS-External LSAs (type-5) or ASBR-Summary LSAs (type-4) into the " -"area. They need only pass Network-Summary (type-3) LSAs into such an area, " -"along with a default-route summary." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:208 5528b6622dff42bf8489ff955359057b -msgid "" -"This command specifies the area to be a Totally Stub Area. In addition to " -"stub area limitations this area type prevents an ABR from injecting Network-" -"Summary (type-3) LSAs into the specified stub area. Only default summary " -"route is allowed." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:216 dc30de78fd9045bba5d2775dafec0989 -msgid "" -"This command sets the cost of default-summary LSAs announced to stubby " -"areas. The cost range is 0 to 16777215." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:221 be246b56211845a19e17da26a7451f9c -msgid "" -"This command specifies the area to be a Not So Stubby Area. External routing" -" information is imported into an NSSA in Type-7 LSAs. Type-7 LSAs are " -"similar to Type-5 AS-external LSAs, except that they can only be flooded " -"into the NSSA. In order to further propagate the NSSA external information, " -"the Type-7 LSA must be translated to a Type-5 AS-external-LSA by the NSSA " -"ABR." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:230 e124b837078c4d49acbd1941ee7bd875 -msgid "" -"This command specifies the area to be a NSSA Totally Stub Area. ABRs for " -"such an area do not need to pass Network-Summary (type-3) LSAs (except the " -"default summary route), ASBR-Summary LSAs (type-4) and AS-External LSAs " -"(type-5) into the area. But Type-7 LSAs that convert to Type-5 at the NSSA " -"ABR are allowed." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:239 6e57515bcfa84057b4bdd15490a60a76 -msgid "" -"This command sets the default cost of LSAs announced to NSSA areas. The cost" -" range is 0 to 16777215." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:245 55f19b3d1d9c49b3aa9a500b4b2d3790 -msgid "" -"Specifies whether this NSSA border router will unconditionally translate " -"Type-7 LSAs into Type-5 LSAs. When role is Always, Type-7 LSAs are " -"translated into Type-5 LSAs regardless of the translator state of other NSSA" -" border routers. When role is Candidate, this router participates in the " -"translator election to determine if it will perform the translations duties." -" When role is Never, this router will never translate Type-7 LSAs into " -"Type-5 LSAs." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:255 ba4c8ab2af5d4a6b9353c1c619663ef8 -msgid "" -"This command specifies that simple password authentication should be used " -"for the given area. The password must also be configured on a per-interface " -"basis." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:261 0ee207fa134149baa945aaabeb1c9404 -msgid "" -"This command specify that OSPF packets must be authenticated with MD5 HMACs " -"within the given area. Keying material must also be configured on a per-" -"interface basis." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:267 a29e63b95a4e4bd39e5db5a03ba871d1 -msgid "" -"This command summarizes intra area paths from specified area into one " -"summary-LSA (Type-3) announced to other areas. This command can be used only" -" in ABR and ONLY router-LSAs (Type-1) and network-LSAs (Type-2) (i.e. LSAs " -"with scope area) can be summarized. AS-external-LSAs (Type-5) can’t be " -"summarized - their scope is AS. The optional argument :cfgcmd:`cost` " -"specifies the aggregated link metric. The metric range is 0 to 16777215." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:277 -#: ../../configuration/protocols/ospf.rst:840 6bafba4ec8ef48298bbebf74719ab1db -#: ba22b65b4635427381dd2c138e7ceca2 -msgid "" -"This command instead of summarizing intra area paths filter them - i.e. " -"intra area paths from this range are not advertised into other areas. This " -"command makes sense in ABR only." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:283 96ee74fa7fa441bdb48b2731944845d4 -msgid "" -"Filter Type-3 summary-LSAs announced to other areas originated from intra- " -"area paths from specified area. This command makes sense in ABR only." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:289 0666d353b27e472eabc844cedf9aa3dc -msgid "" -"Same as export-list, but it applies to paths announced into specified area " -"as Type-3 summary-LSAs. This command makes sense in ABR only." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:296 542a3c11f01441af98607a8d4e68d0ef -msgid "" -"One Type-3 summary-LSA with routing info <E.F.G.H/M> is announced into " -"backbone area if defined area contains at least one intra-area network (i.e." -" described with router-LSA or network-LSA) from range <A.B.C.D/M>. This " -"command makes sense in ABR only." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:303 f3b5a7b1baaf4fd5acf86d85330f9d29 -msgid "" -"This parameter allows to \"shortcut\" routes (non-backbone) for inter-area " -"routes. There are three modes available for routes shortcutting:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:306 d00248dbf3f7495f9bb6cc2231d7a649 -msgid "" -"**default** – this area will be used for shortcutting only if ABR does not " -"have a link to the backbone area or this link was lost. **enable** – the " -"area will be used for shortcutting every time the route that goes through it" -" is cheaper. **disable** – this area is never used by ABR for routes " -"shortcutting." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:314 e9ee79855d4d44cf89cfa834ebe8a79d -msgid "Provides a backbone area coherence by virtual link establishment." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:316 1aa391335ca8421db7ac2c15fcf8b129 -msgid "" -"In general, OSPF protocol requires a backbone area (area 0) to be coherent " -"and fully connected. I.e. any backbone area router must have a route to any " -"other backbone area router. Moreover, every ABR must have a link to backbone" -" area. However, it is not always possible to have a physical link to a " -"backbone area. In this case between two ABR (one of them has a link to the " -"backbone area) in the area (not stub area) a virtual link is organized." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:323 9a1276600de94a769032c8ca706829ef -msgid "" -"<number> – area identifier through which a virtual link goes. <A.B.C.D> – " -"ABR router-id with which a virtual link is established. Virtual link must be" -" configured on both routers." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:327 bb9edaa3d59643bca24f800e2b9feb21 -msgid "" -"Formally, a virtual link looks like a point-to-point network connecting two " -"ABR from one area one of which physically connected to a backbone area. This" -" pseudo-network is considered to belong to a backbone area." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:333 -#: ../../configuration/protocols/ospf.rst:847 a726f9fa108f4b8d8d52fd1161bfb5fe -#: 4f9a3f440cb7458bb5293e70c1058d7c -msgid "Interface Configuration" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:337 a7e322fabc1e450bb43ad6fe55fe79f5 -msgid "Enable ospf on an interface and set associated area." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:339 8492b58a427a4127b4b64f249b80f1c3 -msgid "" -"If you have a lot of interfaces, and/or a lot of subnets, then enabling OSPF" -" via this command may result in a slight performance improvement." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:345 f791acb2614549bea724b77ee4f5756e -msgid "" -"This command sets OSPF authentication key to a simple password. After " -"setting, all OSPF packets are authenticated. Key has length up to 8 chars." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:348 f79d9a7b679245ffb25f5dce05665a3f -msgid "" -"Simple text password authentication is insecure and deprecated in favour of " -"MD5 HMAC authentication." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:354 49ac8ee2b26c486f8b85bea0ce6477a0 -msgid "" -"This command specifys that MD5 HMAC authentication must be used on this " -"interface. It sets OSPF authentication key to a cryptographic password. Key-" -"id identifies secret key used to create the message digest. This ID is part " -"of the protocol and must be consistent across routers on a link. The key can" -" be long up to 16 chars (larger strings will be truncated), and is " -"associated with the given key-id." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:363 81827eb422ce4a74919776b7e7c9c238 -msgid "" -"This command sets the interface bandwidth for cost calculations, where " -"bandwidth can be in range from 1 to 100000, specified in Mbits/s." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:368 -#: ../../configuration/protocols/ospf.rst:851 1eb5df790b8b411cad7d031ce16ac429 -#: 0d06f8ac47de4ad090347841638ab23c -msgid "" -"This command sets link cost for the specified interface. The cost value is " -"set to router-LSA’s metric field and used for SPF calculation. The cost " -"range is 1 to 65535." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:374 -#: ../../configuration/protocols/ospf.rst:857 5271b5e5f52345cb863ea00e1b1cc148 -#: 1831257a6c2f491abb75677d0b55fdca -msgid "" -"Set number of seconds for router Dead Interval timer value used for Wait " -"Timer and Inactivity Timer. This value must be the same for all routers " -"attached to a common network. The default value is 40 seconds. The interval " -"range is 1 to 65535." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:381 98e1d855c68f48ccad1d3b16995599ca -msgid "" -"The hello-multiplier specifies how many Hellos to send per second, from 1 " -"(every second) to 10 (every 100ms). Thus one can have 1s convergence time " -"for OSPF. If this form is specified, then the hello-interval advertised in " -"Hello packets is set to 0 and the hello-interval on received Hello packets " -"is not checked, thus the hello-multiplier need NOT be the same across " -"multiple routers on a common link." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:390 -#: ../../configuration/protocols/ospf.rst:865 4938ebbf6fce435c9af610cb1e419986 -#: 4f07a66d0bee43f7afeda7ae6edc9554 -msgid "" -"Set number of seconds for Hello Interval timer value. Setting this value, " -"Hello packet will be sent every timer value seconds on the specified " -"interface. This value must be the same for all routers attached to a common " -"network. The default value is 10 seconds. The interval range is 1 to 65535." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:398 abc1c6297d934f1bb434f1646c511db3 -msgid "" -"This command enables :abbr:`BFD (Bidirectional Forwarding Detection)` on " -"this OSPF link interface." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:403 -#: ../../configuration/protocols/ospf.rst:873 8127a95f861f4363a7cffada1e500aa3 -#: 07728f0c4b5b4f85b691fe2f86034bfa -msgid "" -"This command disables check of the MTU value in the OSPF DBD packets. Thus, " -"use of this command allows the OSPF adjacency to reach the FULL state even " -"though there is an interface MTU mismatch between two OSPF routers." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:409 -#: ../../configuration/protocols/ospf.rst:880 290b08ed0f034a6086c7640cea77308e -#: 137fa4a39e104a058eccddcfe65c4644 -msgid "" -"This command allows to specify the distribution type for the network " -"connected to this interface:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:412 14401f0ad44c4031b665f3f3d263564f -msgid "" -"**broadcast** – broadcast IP addresses distribution. **non-broadcast** – " -"address distribution in NBMA networks topology. **point-to-multipoint** – " -"address distribution in point-to-multipoint networks. **point-to-point** – " -"address distribution in point-to-point networks." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:420 -#: ../../configuration/protocols/ospf.rst:888 69ab8c0628a44729bd657fd3d49df480 -#: abb6df45d8c445b78f7c726eedf10191 -msgid "" -"This command sets Router Priority integer value. The router with the highest" -" priority will be more eligible to become Designated Router. Setting the " -"value to 0, makes the router ineligible to become Designated Router. The " -"default value is 1. The interval range is 0 to 255." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:428 -#: ../../configuration/protocols/ospf.rst:902 597e90c33e5e429ba1dbc89f50437c2d -#: d85932af73844481a7771e1fa6de9857 -msgid "" -"This command sets number of seconds for RxmtInterval timer value. This value" -" is used when retransmitting Database Description and Link State Request " -"packets if acknowledge was not received. The default value is 5 seconds. The" -" interval range is 3 to 65535." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:435 -#: ../../configuration/protocols/ospf.rst:910 8f4f220a1ccd4b82b4b8fbb327dbcd24 -#: da2975ef22ec49118511b1e29f07b72a -msgid "" -"This command sets number of seconds for InfTransDelay value. It allows to " -"set and adjust for each interface the delay interval before starting the " -"synchronizing process of the router's database with all neighbors. The " -"default value is 1 seconds. The interval range is 3 to 65535." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:442 c67cfc76f5a74a9e862121967f413254 -msgid "Manual Neighbor Configuration" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:444 0577dc47024f491f9b608af640251918 -msgid "" -"OSPF routing devices normally discover their neighbors dynamically by " -"listening to the broadcast or multicast hello packets on the network. " -"Because an NBMA network does not support broadcast (or multicast), the " -"device cannot discover its neighbors dynamically, so you must configure all " -"the neighbors statically." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:452 5da2bda408274b6dbb0871ddbc4290cf -msgid "This command specifies the IP address of the neighboring device." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:456 614a663f1ae544d8bec1bf832029d75f -msgid "" -"This command specifies the length of time, in seconds, before the routing " -"device sends hello packets out of the interface before it establishes " -"adjacency with a neighbor. The range is 1 to 65535 seconds. The default " -"value is 60 seconds." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:463 fab22e795bc14f679941ee55921c4866 -msgid "" -"This command specifies the router priority value of the nonbroadcast " -"neighbor associated with the IP address specified. The default is 0. This " -"keyword does not apply to point-to-multipoint interfaces." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:469 -#: ../../configuration/protocols/ospf.rst:918 bf291f71a29949439ef7ab2c384383bf -#: ddef832b89e24d76a0c584f8a05a5d56 -msgid "Redistribution Configuration" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:473 fd557cfd1b0347c7b8d89dbf66535d8a -msgid "" -"This command redistributes routing information from the given route source " -"to the OSPF process. There are five modes available for route source: bgp, " -"connected, kernel, rip, static." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:479 f92d857774b14836aa6b2368fca14df8 -msgid "" -"This command specifies the default metric value of redistributed routes. The" -" metric range is 0 to 16777214." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:484 5da5b07313054f38b053554209fed43f -msgid "" -"This command specifies metric for redistributed routes from the given route " -"source. There are five modes available for route source: bgp, connected, " -"kernel, rip, static. The metric range is 1 to 16777214." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:490 1b43a6f618f642d3b554246712bdb0a6 -msgid "" -"This command specifies metric type for redistributed routes. Difference " -"between two metric types that metric type 1 is a metric which is " -"\"commensurable\" with inner OSPF links. When calculating a metric to the " -"external destination, the full path metric is calculated as a metric sum " -"path of a router which had advertised this link plus the link metric. Thus, " -"a route with the least summary metric will be selected. If external link is " -"advertised with metric type 2 the path is selected which lies through the " -"router which advertised this link with the least metric despite of the fact " -"that internal path to this router is longer (with more cost). However, if " -"two routers advertised an external link and with metric type 2 the " -"preference is given to the path which lies through the router with a shorter" -" internal path. If two different routers advertised two links to the same " -"external destimation but with different metric type, metric type 1 is " -"preferred. If type of a metric left undefined the router will consider these" -" external links to have a default metric type 2." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:508 c9e4402b19ce4d3399f2b0e49243d90b -msgid "" -"This command allows to use route map to filter redistributed routes from the" -" given route source. There are five modes available for route source: bgp, " -"connected, kernel, rip, static." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:514 -#: ../../configuration/protocols/ospf.rst:935 e7b88b6e44724740abc1921f397397a9 -#: d9e5c2dda98f4a12b1f41fae0f67f8dd -msgid "Operational Mode Commands" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:518 -#: ../../configuration/protocols/ospf.rst:939 42f9057acde047d79212aae12b522d87 -#: ffb613dbfdfb449dae733f692e54fd5d -msgid "This command displays the neighbors status." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:528 -#: ../../configuration/protocols/ospf.rst:943 941e24d2170c45b0996bb417d3642781 -#: 8f5e59fc82bc4e1a8c51b98e2e45c88f -msgid "" -"This command displays the neighbors information in a detailed form, not just" -" a summary table." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:567 4e9ba9116c604c9bb293440930819345 -msgid "" -"This command displays the neighbors information in a detailed form for a " -"neighbor whose IP address is specified." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:572 81335795f2e344b6bf503429098cbf6b -msgid "" -"This command displays the neighbors status for a neighbor on the specified " -"interface." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:577 061d2b04bc8a41a5a89323d4ceb6f71b -msgid "" -"This command displays state and configuration of OSPF the specified " -"interface, or all interfaces if no interface is given." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:608 -#: ../../configuration/protocols/ospf.rst:958 a06d4b330b4e4f34925941a7ba7685a5 -#: 8501269415eb493c97e4e10032eae5e5 -msgid "" -"This command displays the OSPF routing table, as determined by the most " -"recent SPF calculation." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:633 b45055e53f114b96a3905e2a11b5edfa -msgid "The table consists of following data:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:635 b429c057a65a49ed822f43c91c2f2c18 -msgid "" -"**OSPF network routing table** – includes a list of acquired routes for all " -"accessible networks (or aggregated area ranges) of OSPF system. \"IA\" flag " -"means that route destination is in the area to which the router is not " -"connected, i.e. it’s an inter-area path. In square brackets a summary metric" -" for all links through which a path lies to this network is specified. " -"\"via\" prefix defines a router-gateway, i.e. the first router on the way to" -" the destination (next hop). **OSPF router routing table** – includes a list" -" of acquired routes to all accessible ABRs and ASBRs. **OSPF external " -"routing table** – includes a list of acquired routes that are external to " -"the OSPF process. \"E\" flag points to the external link metric type (E1 – " -"metric type 1, E2 – metric type 2). External link metric is printed in the " -"\"<metric of the router which advertised the link>/<link metric>\" format." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:651 -#: ../../configuration/protocols/ospf.rst:963 a9e91565bcf14a648b55aee8e75f9b6c -#: a09419bb77c34a4e9dbeebbf8cb45316 -msgid "" -"This command displays a table of paths to area boundary and autonomous " -"system boundary routers." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:656 -#: ../../configuration/protocols/ospf.rst:968 503dbe7a048e4550ab93551fa07a79d5 -#: 592df99c8b8c4e20ae4502c00160b09a -msgid "This command displays a summary table with a database contents (LSA)." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:689 -#: ../../configuration/protocols/ospf.rst:973 de52a2f0d2c54f7a967eec57b3633978 -#: 1a3e6f9274b147e695b659b648a034f7 -msgid "" -"This command displays a database contents for a specific link advertisement " -"type." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:692 16e7d6d0bb814021bac9328baa528553 -msgid "" -"The type can be the following: asbr-summary, external, network, nssa-" -"external, opaque-area, opaque-as, opaque-link, router, summary." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:696 f979d8fed0db48a980a58e95a20766c5 -msgid "" -"[A.B.C.D] – link-state-id. With this specified the command displays portion " -"of the network environment that is being described by the advertisement. The" -" value entered depends on the advertisement’s LS type. It must be entered in" -" the form of an IP address." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:701 aa3aac4f91ff49d9b738c29ce3f1bb5d -msgid "" -":cfgcmd:`adv-router <A.B.C.D>` – router id, which link advertisements need " -"to be reviewed." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:704 4604b0c467d74d4e8e25358a1d2e6f44 -msgid "" -":cfgcmd:`self-originate` displays only self-originated LSAs from the local " -"router." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:734 2761e59df2974824bdcf42ef0e90abaa -msgid "This command displays LSAs in MaxAge list." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:738 -#: ../../configuration/protocols/ospf.rst:983 f3bd5bfe30e04359a51f8c703120fb6f -#: 962c304de3e24d4fba3c75e917364b30 -msgid "Configuration Example" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:740 1d10496abb9044c280388864817bc3a2 -msgid "" -"Below you can see a typical configuration using 2 nodes, redistribute " -"loopback address and the node 1 sending the default route:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:743 -#: ../../configuration/protocols/ospf.rst:1017 -#: f1ecaf7d6f0b4166a628c12401508db4 43e607f4e0b243f0a2b93ace3558dcf1 -msgid "**Node 1**" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:760 -#: ../../configuration/protocols/ospf.rst:1032 -#: 4467de1e6af640b28f4e72d0d14ae1ec 53fde67f06874c5fb01c630a43baa1a4 -msgid "**Node 2**" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:779 9d89f72103424330b534385fc35eade5 -msgid "OSPFv3 (IPv6)" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:791 5f9a19053c6b465fad3165d8ba2b1fde -msgid "" -"VyOS does not have a special command to start the OSPFv3 process. The OSPFv3" -" process starts when the first ospf enabled interface is configured." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:796 c34a749fd1e6469f90ff13e568aa18de -msgid "" -"This command specifies the OSPFv3 enabled interface. This command is also " -"used to enable the OSPF process. The area number can be specified in decimal" -" notation in the range from 0 to 4294967295. Or it can be specified in " -"dotted decimal notation similar to ip address." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:803 9b7ac4b5690644c0b0f733783aa3da09 -msgid "" -"This command sets the router-ID of the OSPFv3 process. The router-ID may be " -"an IP address of the router, but need not be – it can be any arbitrary 32bit" -" number. However it MUST be unique within the entire OSPFv3 domain to the " -"OSPFv3 speaker – bad things will happen if multiple OSPFv3 speakers are " -"configured with the same router-ID!" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:817 07551c5f39414186a63c37e1eaccd508 -msgid "" -"This command change distance value of OSPFv3 globally. The distance range is" -" 1 to 255." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:823 7d5d4c8bbdda484ba796621a5f122e7f -msgid "" -"This command change distance value of OSPFv3. The arguments are the distance" -" values for external routes, inter-area routes and intra-area routes " -"respectively. The distance range is 1 to 255." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:834 8960447dc53f43b5b101424569061057 -msgid "" -"This command summarizes intra area paths from specified area into one Type-3" -" Inter-Area Prefix LSA announced to other areas. This command can be used " -"only in ABR." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:883 9258d14858ba46bebc7287146143e7a3 -msgid "" -"**broadcast** – broadcast IP addresses distribution. **point-to-point** – " -"address distribution in point-to-point networks." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:922 4e72c75a20cf46c5a59831085e3b401b -msgid "" -"This command redistributes routing information from the given route source " -"to the OSPFv3 process. There are five modes available for route source: bgp," -" connected, kernel, ripng, static." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:928 f3ac8120abbf45249dd5afcf16e9402e -msgid "" -"This command allows to use route map to filter redistributed routes from " -"given route source. There are five modes available for route source: bgp, " -"connected, kernel, ripng, static." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:948 6eed6dad78474f369976b9b8e7f4fe46 -msgid "This command displays the neighbor DR choice information." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:952 a4674b2df8c04722b64399c42b7a1a04 -msgid "" -"This command displays state and configuration of OSPF the specified " -"interface, or all interfaces if no interface is given. Whith the argument " -":cfgcmd:`prefix` this command shows connected prefixes to advertise." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:978 f8433124b8e448b9afba90cbce9970cc -msgid "This command displays external information redistributed into OSPFv3" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:985 31c3373f27a4458d93b048e21abcceef -msgid "A typical configuration using 2 nodes." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:987 8c3f79a41fef4adfa9745c2d268dfeab -msgid "**Node 1:**" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:996 8546efdeddcf495daa8192a49465c09b -msgid "**Node 2:**" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:1005 -#: 26ed2550753b41e2b67abbbe5dcf3e5a -msgid "**To see the redistributed routes:**" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:1011 -#: 086762874a6b4f128ea2b526ceb26a64 -msgid "" -"You cannot easily redistribute IPv6 routes via OSPFv3 on a WireGuard " -"interface link. This requires you to configure link-local addresses manually" -" on the WireGuard interfaces, see :vytask:`T1483`." -msgstr "" - -#: ../../configuration/protocols/ospf.rst:1015 -#: 4dc1e885308b4ad1b73894a7484b20de -msgid "Example configuration for WireGuard interfaces:" -msgstr "" - -#: ../../configuration/protocols/ospf.rst:1047 -#: 6286c008c90a4a67b8fe53bc75c4b54a -msgid "**Status**" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rip.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rip.po deleted file mode 100644 index 213871d2..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rip.po +++ /dev/null @@ -1,273 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/rip.rst:7 6fc3ec7cfd8244af80453d0ce1c149bc -msgid "RIP" -msgstr "" - -#: ../../configuration/protocols/rip.rst:9 490d09119f394fd094892b23bc134bf6 -msgid "" -":abbr:`RIP (Routing Information Protocol)` is a widely deployed interior " -"gateway protocol. RIP was developed in the 1970s at Xerox Labs as part of " -"the XNS routing protocol. RIP is a distance-vector protocol and is based on " -"the Bellman-Ford algorithms. As a distance-vector protocol, RIP router send " -"updates to its neighbors periodically, thus allowing the convergence to a " -"known topology. In each update, the distance to any given network will be " -"broadcast to its neighboring router." -msgstr "" - -#: ../../configuration/protocols/rip.rst:17 d7689f5e7bdd4210aa8caf674de45011 -msgid "Supported versions of RIP are:" -msgstr "" - -#: ../../configuration/protocols/rip.rst:19 121160551d824146b2e563da197c9dcd -msgid "RIPv1 as described in :rfc:`1058`" -msgstr "" - -#: ../../configuration/protocols/rip.rst:20 7ba8f1c0445d438db51ecd501bf9daf8 -msgid "RIPv2 as described in :rfc:`2453`" -msgstr "" - -#: ../../configuration/protocols/rip.rst:23 97569bf6cb72418d87057d223a2b39b1 -msgid "General Configuration" -msgstr "" - -#: ../../configuration/protocols/rip.rst:27 c15f20a1296f48c6ba68f5bc7673a436 -msgid "" -"This command enables RIP and sets the RIP enable interface by NETWORK. The " -"interfaces which have addresses matching with NETWORK are enabled." -msgstr "" - -#: ../../configuration/protocols/rip.rst:32 1fd1a58d1c194b8985d9fc87aac45004 -msgid "" -"This command specifies a RIP enabled interface by interface name. Both the " -"sending and receiving of RIP packets will be enabled on the port specified " -"in this command." -msgstr "" - -#: ../../configuration/protocols/rip.rst:38 a66a38bdcd8141338a5e4537d3babed0 -msgid "" -"This command specifies a RIP neighbor. When a neighbor doesn’t understand " -"multicast, this command is used to specify neighbors. In some cases, not all" -" routers will be able to understand multicasting, where packets are sent to " -"a network or a group of addresses. In a situation where a neighbor cannot " -"process multicast packets, it is necessary to establish a direct link " -"between routers." -msgstr "" - -#: ../../configuration/protocols/rip.rst:47 a833ba7f4ec2446f982c96d78272c759 -msgid "" -"This command sets the specified interface to passive mode. On passive mode " -"interface, all receiving packets are processed as normal and VyOS does not " -"send either multicast or unicast RIP packets except to RIP neighbors " -"specified with neighbor command." -msgstr "" - -#: ../../configuration/protocols/rip.rst:54 7c8048872d5d41c6800f6722f5dfa7b0 -msgid "This command specifies all interfaces to passive mode." -msgstr "" - -#: ../../configuration/protocols/rip.rst:58 4b96caa173d5489784986af2d6b9bcfc -msgid "Optional Configuration" -msgstr "" - -#: ../../configuration/protocols/rip.rst:62 200a30f7858d4e249541739165ea5845 -msgid "" -"This command change the distance value of RIP. The distance range is 1 to " -"255." -msgstr "" - -#: ../../configuration/protocols/rip.rst:64 6eed7871ee544c8bb1c81733ea908915 -msgid "" -"Routes with a distance of 255 are effectively disabled and not installed " -"into the kernel." -msgstr "" - -#: ../../configuration/protocols/rip.rst:69 1cfd091fdd4f4d0e80f21fa8875c03e6 -msgid "" -"This command sets default RIP distance to a specified value when the routes " -"source IP address matches the specified prefix." -msgstr "" - -#: ../../configuration/protocols/rip.rst:74 77be12b78a7148b3b178e1df0ec93dff -msgid "" -"This command can be used with previous command to sets default RIP distance " -"to specified value when the route source IP address matches the specified " -"prefix and the specified access-list." -msgstr "" - -#: ../../configuration/protocols/rip.rst:80 2a2d50047439469d8f1a5cc16bf5b799 -msgid "This command generate a default route into the RIP." -msgstr "" - -#: ../../configuration/protocols/rip.rst:84 14ed4259523c44dc901791a15b581a2c -msgid "" -"This command can be used to filter the RIP path using access lists. " -":cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the access " -"lists are applied." -msgstr "" - -#: ../../configuration/protocols/rip.rst:90 4931f8d427ab464083c519b7ba70e215 -msgid "" -"This command allows you apply access lists to a chosen interface to filter " -"the RIP path." -msgstr "" - -#: ../../configuration/protocols/rip.rst:95 377096f1558a41ee9c2683509437bd8b -msgid "" -"This command can be used to filter the RIP path using prefix lists. " -":cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the prefix " -"lists are applied." -msgstr "" - -#: ../../configuration/protocols/rip.rst:101 042f3256736c4d0385fbb31fbf348cfa -msgid "" -"This command allows you apply prefix lists to a chosen interface to filter " -"the RIP path." -msgstr "" - -#: ../../configuration/protocols/rip.rst:106 7f17446d2d4b48c6befc84c9b7d9ce8a -msgid "" -"This command is specific to FRR and VyOS. The route command makes a static " -"route only inside RIP. This command should be used only by advanced users " -"who are particularly knowledgeable about the RIP protocol. In most cases, we" -" recommend creating a static route in VyOS and redistributing it in RIP " -"using :cfgcmd:`redistribute static`." -msgstr "" - -#: ../../configuration/protocols/rip.rst:114 cc343d380079428c8c2c93c5d4324d9b -msgid "" -"This command specifies the update timer. Every update timer seconds, the RIP" -" process is awakened to send an unsolicited response message containing the " -"complete routing table to all neighboring RIP routers. The time range is 5 " -"to 2147483647. The default value is 30 seconds." -msgstr "" - -#: ../../configuration/protocols/rip.rst:121 cf443300941c4a80ba298391e1153612 -msgid "" -"This command specifies the timeout timer. Upon expiration of the timeout, " -"the route is no longer valid; however, it is retained in the routing table " -"for a short time so that neighbors can be notified that the route has been " -"dropped. The time range is 5 to 2147483647. The default value is 180 " -"seconds." -msgstr "" - -#: ../../configuration/protocols/rip.rst:129 9b24944e56604032bf0511d4091dfcf5 -msgid "" -"This command specifies the garbage-collection timer. Upon expiration of the " -"garbage-collection timer, the route is finally removed from the routing " -"table. The time range is 5 to 2147483647. The default value is 120 seconds." -msgstr "" - -#: ../../configuration/protocols/rip.rst:136 83c1d23512bd4127b4a8dfb18461fa0c -msgid "Redistribution Configuration" -msgstr "" - -#: ../../configuration/protocols/rip.rst:140 5cc9716f7b5547b1a6a069e27b6e6445 -msgid "" -"This command redistributes routing information from the given route source " -"into the RIP tables. There are five modes available for route source: bgp, " -"connected, kernel, ospf, static." -msgstr "" - -#: ../../configuration/protocols/rip.rst:146 4afb87d13fef4cb59e09389070b62dd7 -msgid "" -"This command specifies metric for redistributed routes from the given route " -"source. There are five modes available for route source: bgp, connected, " -"kernel, ospf, static. The metric range is 1 to 16." -msgstr "" - -#: ../../configuration/protocols/rip.rst:152 0a24c8166b3145179671e0664ffc198b -msgid "" -"This command allows to use route map to filter redistributed routes from the" -" given route source. There are five modes available for route source: bgp, " -"connected, kernel, ospf, static." -msgstr "" - -#: ../../configuration/protocols/rip.rst:158 c4e70084aab8480498f92206231c48d8 -msgid "" -"This command modifies the default metric (hop count) value for redistributed" -" routes. The metric range is 1 to 16. The default value is 1. This command " -"does not affect connected route even if it is redistributed by " -":cfgcmd:`redistribute connected`. To modify connected routes metric value, " -"please use :cfgcmd:`redistribute connected metric`." -msgstr "" - -#: ../../configuration/protocols/rip.rst:166 a71e036258d14c9da8903e58f87272d6 -msgid "Interfaces Configuration" -msgstr "" - -#: ../../configuration/protocols/rip.rst:170 e39a84e079cb4ab9a900f77d92304314 -msgid "" -"This command sets the interface with RIP simple password authentication. " -"This command also sets authentication string. The string must be shorter " -"than 16 characters." -msgstr "" - -#: ../../configuration/protocols/rip.rst:176 12146310bd0b43fc8f62ede687ded20f -msgid "" -"This command sets the interface with RIP MD5 authentication. This command " -"also sets MD5 Key. The key must be shorter than 16 characters." -msgstr "" - -#: ../../configuration/protocols/rip.rst:181 b0c2a7bd88f040b0876d560800d66f95 -msgid "" -"This command disables split-horizon on the interface. By default, VyOS does " -"not advertise RIP routes out the interface over which they were learned " -"(split horizon).3" -msgstr "" - -#: ../../configuration/protocols/rip.rst:187 8fbf68d36815489d8666b99fbbeafc87 -msgid "" -"This command enables poison-reverse on the interface. If both poison reverse" -" and split horizon are enabled, then VyOS advertises the learned routes as " -"unreachable over the interface on which the route was learned." -msgstr "" - -#: ../../configuration/protocols/rip.rst:193 a74c50027f0c46ccb4403efdfb22b323 -msgid "Operational Mode Commands" -msgstr "" - -#: ../../configuration/protocols/rip.rst:197 ef65acbe5c534876b42dd1a3df3e2bd8 -msgid "This command displays RIP routes." -msgstr "" - -#: ../../configuration/protocols/rip.rst:213 89b074f310a8409aa4233b79d3e5ca28 -msgid "" -"The command displays current RIP status. It includes RIP timer, filtering, " -"version, RIP enabled interface and RIP peer information." -msgstr "" - -#: ../../configuration/protocols/rip.rst:239 e7486e3160b54ee6b534c078fd691894 -msgid "Configuration Example" -msgstr "" - -#: ../../configuration/protocols/rip.rst:241 d04899a06f2047569290b32f6391ccbf -msgid "" -"Simple RIP configuration using 2 nodes and redistributing connected " -"interfaces." -msgstr "" - -#: ../../configuration/protocols/rip.rst:243 4329e2b585d4417b8e9d8ed6e5d31142 -msgid "**Node 1:**" -msgstr "" - -#: ../../configuration/protocols/rip.rst:251 45f088e27cbb47408058063bcc63df7e -msgid "**Node 2:**" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rpki.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rpki.po deleted file mode 100644 index 2c2a2223..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/rpki.po +++ /dev/null @@ -1,267 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/rpki.rst:5 1bd61b4c15664efdbca3b9b4df271aca -msgid "RPKI" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:9 e6cfd8941dec4bceb55ae5121148b571 -msgid "" -"There are two types of Network Admins who deal with BGP, those who have " -"created an international incident and/or outage, and those who are lying" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:16 220f227c43f1419fb5c051e721c70d08 -msgid "`tweet by EvilMog`_, 2020-02-21" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:14 44119109520d462d86a9d6fc6ccd97b1 -msgid "" -":abbr:`RPKI (Resource Public Key Infrastructure)` is a framework :abbr:`PKI " -"(Public Key Infrastructure)` designed to secure the Internet routing " -"infrastructure. It associates BGP route announcements with the correct " -"originating :abbr:`ASN (Autonomus System Number)` which BGP routers can then" -" use to check each route against the corresponding :abbr:`ROA (Route Origin " -"Authorisation)` for validity. RPKI is described in :rfc:`6480`." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:21 6ad01fd0e5bb48a887151f3178e9d08e -msgid "" -"A BGP-speaking router like VyOS can retrieve ROA information from RPKI " -"\"Relying Party software\" (often just called an \"RPKI server\" or \"RPKI " -"validator\") by using :abbr:`RTR (RPKI to Router)` protocol. There are " -"several open source implementations to choose from, such as NLNetLabs' " -"Routinator_ (written in Rust), Cloudflare's GoRTR_ and OctoRPKI_ (written in" -" Go), and RIPE NCC's RPKI Validator_ (written in Java). The RTR protocol is " -"described in :rfc:`8210`." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:30 d954e8652e7544d9bd395c4c794daf58 -msgid "" -"If you are new to these routing security technologies then there is an " -"`excellent guide to RPKI`_ by NLnet Labs which will get you up to speed very" -" quickly. Their documentation explains everything from what RPKI is to " -"deploying it in production. It also has some `help and operational " -"guidance`_ including \"What can I do about my route having an Invalid " -"state?\"" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:39 1cf071e50cfb42289176729dbe394f7a -msgid "Getting started" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:41 ad74482bc987491b9eaa4621315fc46e -msgid "" -"First you will need to deploy an RPKI validator for your routers to use. The" -" RIPE NCC helpfully provide `some instructions`_ to get you started with " -"several different options. Once your server is running you can start " -"validating announcements." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:46 9f395bc595e14b29ad5e25732eef541d -msgid "Imported prefixes during the validation may have values:" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:50 77da08266569477f8938c275d180d8b4 -msgid "valid" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:49 cd9d9e6e8d864e1ebf72445b693a6525 -msgid "" -"The prefix and ASN that originated it match a signed ROA. These are probably" -" trustworthy route announcements." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:56 fc73537ac7b740018df729dc62c99176 -msgid "invalid" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:53 e51152de42cd45d8a8c4444c541f7a1f -msgid "" -"The prefix or prefix length and ASN that originated it doesn't match any " -"existing ROA. This could be the result of a prefix hijack, or merely a " -"misconfiguration, but should probably be treated as untrustworthy route " -"announcements." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:61 393184b5732947f3924f8711c5eb16f7 -msgid "notfound" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:59 0d7810f523da4aaa8ff3af02cdf509b3 -msgid "" -"No ROA exists which covers that prefix. Unfortunately this is the case for " -"about 80% of the IPv4 prefixes which were announced to the :abbr:`DFZ " -"(default-free zone)` at the start of 2020" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:64 ca90c7c8c5d748eab9029abcdcfc9f33 -msgid "" -"If you are responsible for the global addresses assigned to your network, " -"please make sure that your prefixes have ROAs associated with them to avoid " -"being `notfound` by RPKI. For most ASNs this will involve publishing ROAs " -"via your :abbr:`RIR (Regional Internet Registry)` (RIPE NCC, APNIC, ARIN, " -"LACNIC or AFRINIC), and is something you are encouraged to do whenever you " -"plan to announce addresses into the DFZ." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:71 f2f8bc07e9d44ebe9bebb09c45913941 -msgid "" -"Particularly large networks may wish to run their own RPKI certificate " -"authority and publication server instead of publishing ROAs via their RIR. " -"This is a subject far beyond the scope of VyOS' documentation. Consider " -"reading about Krill_ if this is a rabbit hole you need or especially want to" -" dive down." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:78 76089628d8ce402ab91e0adde43a2898 -msgid "Features of the Current Implementation" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:80 f8ad2f7d942643beab4327271108a05d -msgid "" -"In a nutshell, the current implementation provides the following features:" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:82 19b31ea1b4e74aa79f078b32117ebd89 -msgid "" -"The BGP router can connect to one or more RPKI cache servers to receive " -"validated prefix to origin AS mappings. Advanced failover can be implemented" -" by server sockets with different preference values." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:86 b445b9b18f054e288d8b56cb962a43b5 -msgid "" -"If no connection to an RPKI cache server can be established after a pre-" -"defined timeout, the router will process routes without prefix origin " -"validation. It still will try to establish a connection to an RPKI cache " -"server in the background." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:91 b9c92a88e7914870ae611a9db500a84b -msgid "" -"By default, enabling RPKI does not change best path selection. In " -"particular, invalid prefixes will still be considered during best path " -"selection. However, the router can be configured to ignore all invalid " -"prefixes." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:95 26514a15701044b095230a997dce447d -msgid "" -"Route maps can be configured to match a specific RPKI validation state. This" -" allows the creation of local policies, which handle BGP routes based on the" -" outcome of the Prefix Origin Validation." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:99 45e342fa456940a4b3b4e5d4b5cea3f9 -msgid "" -"Updates from the RPKI cache servers are directly applied and path selection " -"is updated accordingly. (Soft reconfiguration must be enabled for this to " -"work)." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:104 a7ba2bf755da42f48595901da621cf6e -msgid "Configuration" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:108 03511dc3a83d4e408ade97a500c65232 -msgid "Define the time interval to update the local cache" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:110 9b0b1087ef1846d9996c4e891958b27c -msgid "The default value is 300 seconds." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:114 e2aef470087c476aab20592744a01950 -msgid "" -"Defined the IPv4, IPv6 or FQDN and port number of the caching RPKI caching " -"instance which is used." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:117 -#: ../../configuration/protocols/rpki.rst:124 6c88944bb61342e2883ed1d3566d7db5 -#: 44de7c2448ed40b09a66e47cb98e52f9 -msgid "This is a mandatory setting." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:121 65de0f2c2dfe4d7d8d1bbec0e0592f49 -msgid "" -"Multiple RPKI caching instances can be supplied and they need a preference " -"in which their result sets are used." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:127 b6e433899a3a4a4098b5e36c17a864d6 -msgid "SSH" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:129 756c3bee52fe4f42877799de5947d2f3 -msgid "" -"Connections to the RPKI caching server can not only be established by " -"HTTP/TLS but you can also rely on a secure SSH session to the server. To " -"enable SSH you first need to create yoursels an SSH client keypair using " -"``generate ssh client-key /config/auth/id_rsa_rpki``. Once your key is " -"created you can setup the connection." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:137 de30b47273e74d7595377eddcab3d1d7 -msgid "SSH username to establish an SSH connection to the cache server." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:141 ca9167aa471a461084c2c9b36d6923a6 -msgid "Local path that includes the known hosts file." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:145 3c75b30efdf14b5fbd98db779033eac4 -msgid "Local path that includes the private key file of the router." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:149 6abc754d30f140b18a58198690f2afd6 -msgid "Local path that includes the public key file of the router." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:151 0f33a93c3f6c4beda15cb4d9246de6e9 -msgid "" -"When using SSH, known-hosts-file, private-key-file and public-key-file are " -"mandatory options." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:156 b2100d8f6db146a1bec22156c151cc1c -msgid "Example" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:158 71524aff9c254b919fe68224ac362f95 -msgid "" -"We can build route-maps for import based on these states. Here is a simple " -"RPKI configuration, where `routinator` is the RPKI-validating \"cache\" " -"server with ip `192.0.2.1`:" -msgstr "" - -#: ../../configuration/protocols/rpki.rst:167 0ab8a8f3af1344f88143d6000036a12e -msgid "" -"Here is an example route-map to apply to routes learned at import. In this " -"filter we reject prefixes with the state `invalid`, and set a higher `local-" -"preference` if the prefix is RPKI `valid` rather than merely `notfound`." -msgstr "" - -#: ../../configuration/protocols/rpki.rst:183 ed77a709999b4ab2bf29c2b7dc4b7fae -msgid "" -"Once your routers are configured to reject RPKI-invalid prefixes, you can " -"test whether the configuration is working correctly using the `RIPE Labs " -"RPKI Test`_ experimental tool." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/static.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/static.po deleted file mode 100644 index 1eb307a0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/protocols/static.po +++ /dev/null @@ -1,228 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/protocols/static.rst:5 c0cb379796b64da09d909445513dbb23 -msgid "Static" -msgstr "" - -#: ../../configuration/protocols/static.rst:7 9397865f01834f51b32dc6bf166c90ef -msgid "" -"Static routes are manually configured routes, which, in general, cannot be " -"updated dynamically from information VyOS learns about the network topology " -"from other routing protocols. However, if a link fails, the router will " -"remove routes, including static routes, from the :abbr:`RIPB (Routing " -"Information Base)` that used this interface to reach the next hop. In " -"general, static routes should only be used for very simple network " -"topologies, or to override the behavior of a dynamic routing protocol for a " -"small number of routes. The collection of all routes the router has learned " -"from its configuration or from its dynamic routing protocols is stored in " -"the RIB. Unicast routes are directly used to determine the forwarding table " -"used for unicast packet forwarding." -msgstr "" - -#: ../../configuration/protocols/static.rst:20 -#: 7e54c2806f784bce8702ba9bf918daeb -msgid "Static Routes" -msgstr "" - -#: ../../configuration/protocols/static.rst:24 -#: 74194551ea974d78aa1930e3f92c63b0 -msgid "" -"Configure next-hop `<address>` for an IPv4 static route. Multiple static " -"routes can be created." -msgstr "" - -#: ../../configuration/protocols/static.rst:29 -#: 4de92aa024ba47f98be3b28c3550b59b -msgid "Disable this IPv4 static route entry." -msgstr "" - -#: ../../configuration/protocols/static.rst:34 -#: ../../configuration/protocols/static.rst:54 -#: ../../configuration/protocols/static.rst:81 -#: ../../configuration/protocols/static.rst:101 -#: de3dcd8d037a4722947c55c7dca08cb6 d940c682efbf4400b5b05282ddd16dfd -#: 1ebd04e13bae4957879eb336d730efe3 b55efa2034704fbe9068731a13062dcd -msgid "" -"Defines next-hop distance for this route, routes with smaller administrative" -" distance are elected prior to those with a higher distance." -msgstr "" - -#: ../../configuration/protocols/static.rst:37 -#: ../../configuration/protocols/static.rst:57 -#: ../../configuration/protocols/static.rst:84 -#: ../../configuration/protocols/static.rst:104 -#: df38cf753ead4159be24d569208a22e1 5412f2a930d547abaf720e6f8ba34d37 -#: 9ae33139993741f993eb3b69ef4aefc0 bba243592204415f86b74f749a3d4839 -msgid "Range is 1 to 255, default is 1." -msgstr "" - -#: ../../configuration/protocols/static.rst:39 -#: ../../configuration/protocols/static.rst:59 -#: 3a918f9350ce4ab0a35bac77f58687a0 b37387c281524e14a557ab2fa4a992a4 -msgid "" -"Routes with a distance of 255 are effectively disabled and not installed " -"into the kernel." -msgstr "" - -#: ../../configuration/protocols/static.rst:44 -#: ab34fd19195a40c490404b01eea7e8b5 -msgid "" -"Configure next-hop `<address>` for an IPv6 static route. Multiple static " -"routes can be created." -msgstr "" - -#: ../../configuration/protocols/static.rst:49 -#: 385bf28e072646578215634793ff5921 -msgid "Disable this IPv6 static route entry." -msgstr "" - -#: ../../configuration/protocols/static.rst:64 -#: 0c24f2c280694622a549834d2f292ae5 -msgid "Interface Routes" -msgstr "" - -#: ../../configuration/protocols/static.rst:69 -#: 327b3640dac443c387e855c8360e865f -msgid "" -"Allows you to configure the next-hop interface for an interface-based IPv4 " -"static route. `<interface>` will be the next-hop interface where traffic is " -"routed for the given `<subnet>`." -msgstr "" - -#: ../../configuration/protocols/static.rst:76 -#: 26459a66c77740dca41310cc42e5b2a9 -msgid "Disables interface-based IPv4 static route." -msgstr "" - -#: ../../configuration/protocols/static.rst:89 -#: 2e5099a5c1b14a5caf1b1f800ef6c056 -msgid "" -"Allows you to configure the next-hop interface for an interface-based IPv6 " -"static route. `<interface>` will be the next-hop interface where traffic is " -"routed for the given `<subnet>`." -msgstr "" - -#: ../../configuration/protocols/static.rst:96 -#: b82151038e6945038adf5b3d177e9ac2 -msgid "Disables interface-based IPv6 static route." -msgstr "" - -#: ../../configuration/protocols/static.rst:108 -#: 0b2bf8847be046099b2b3927d6674290 -msgid "Blackhole" -msgstr "" - -#: ../../configuration/protocols/static.rst:112 -#: ../../configuration/protocols/static.rst:125 -#: 2cb4e9e8c23b4cbfb09773a444734be6 2d3034f954c34aeb9eeb121199edc204 -msgid "" -"Use this command to configure a \"black-hole\" route on the router. A black-" -"hole route is a route for which the system silently discard packets that are" -" matched. This prevents networks leaking out public interfaces, but it does " -"not prevent them from being used as a more specific route inside your " -"network." -msgstr "" - -#: ../../configuration/protocols/static.rst:120 -#: ../../configuration/protocols/static.rst:133 -#: eb8de21c92f64e278b75017600c5116f 5666a897614c4a41b0821971f8896652 -msgid "" -"Defines blackhole distance for this route, routes with smaller " -"administrative distance are elected prior to those with a higher distance." -msgstr "" - -#: ../../configuration/protocols/static.rst:138 -#: fb24a302e8b8450495203a2ed8ba9fd9 -msgid "Alternate Routing Tables" -msgstr "" - -#: ../../configuration/protocols/static.rst:140 -#: 1c2f51ca845a407ea980c11f9ba365c9 -msgid "TBD" -msgstr "" - -#: ../../configuration/protocols/static.rst:142 -#: 5be8780519e74384983703b6b4043ef9 -msgid "" -"Alternate routing tables are used with policy based routing by utilizing " -":ref:`vrf`." -msgstr "" - -#: ../../configuration/protocols/static.rst:150 -#: 575365e22aaf4eb181b646368ae0aa49 -msgid "ARP" -msgstr "" - -#: ../../configuration/protocols/static.rst:152 -#: a35fda4343a9400db4e82ebb30eec4e8 -msgid "" -":abbr:`ARP (Address Resolution Protocol)` is a communication protocol used " -"for discovering the link layer address, such as a MAC address, associated " -"with a given internet layer address, typically an IPv4 address. This mapping" -" is a critical function in the Internet protocol suite. ARP was defined in " -"1982 by :rfc:`826` which is Internet Standard STD 37." -msgstr "" - -#: ../../configuration/protocols/static.rst:158 -#: c495ed9891414ce2909e9b55ba165ec6 -msgid "" -"In Internet Protocol Version 6 (IPv6) networks, the functionality of ARP is " -"provided by the Neighbor Discovery Protocol (NDP)." -msgstr "" - -#: ../../configuration/protocols/static.rst:161 -#: b08fa2b6512d4d16bf16dc7c867a8c84 -msgid "" -"To manipulate or display ARP_ table entries, the following commands are " -"implemented." -msgstr "" - -#: ../../configuration/protocols/static.rst:166 -#: 57475f6a944a4ea5abdd07f0497fed0f -msgid "Configure" -msgstr "" - -#: ../../configuration/protocols/static.rst:171 -#: baf8357ceffa44398630d29490cff4f1 -msgid "" -"This will configure a static ARP entry always resolving `<address>` to " -"`<mac>` for interface `<interface>`." -msgstr "" - -#: ../../configuration/protocols/static.rst:174 -#: 890ef69425f64428a60e756bdf8813f6 -msgid "Example:" -msgstr "" - -#: ../../configuration/protocols/static.rst:183 -#: cd3bd9363aba4cc78bfd7e0fe58a07dc -msgid "Operation" -msgstr "" - -#: ../../configuration/protocols/static.rst:188 -#: 7b892819f8ec497199e728778db5345f -msgid "Display all known ARP table entries spanning across all interfaces" -msgstr "" - -#: ../../configuration/protocols/static.rst:200 -#: 34580da66a7c432194f33cae45de4734 -msgid "" -"Display all known ARP table entries on a given interface only (`eth1`):" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/broadcast-relay.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/broadcast-relay.po deleted file mode 100644 index 4f6641cc..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/broadcast-relay.po +++ /dev/null @@ -1,112 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/broadcast-relay.rst:5 -#: 9f06b22b56ce4807a8e313f22df58bdb -msgid "UDP Broadcast Relay" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:7 -#: 1631755745c943578b053fddaaf1e714 -msgid "" -"Certain vendors use broadcasts to identify their equipment within one " -"ethernet segment. Unfortunately if you split your network with multiple " -"VLANs you loose the ability of identifying your equipment." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:11 -#: 63312ea281104fcaac7d39b3b90c52a3 -msgid "" -"This is where \"UDP broadcast relay\" comes into play! It will forward " -"received broadcasts to other configured networks." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:14 -#: a1f1a6022bab47fba2e8e13bf6791c14 -msgid "" -"Every UDP port which will be forward requires one unique ID. Currently we " -"support 99 IDs!" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:18 -#: f38a03b32557452091c28bbb859db352 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:22 -#: e82639efc84b4282adff04f352dbf147 -msgid "" -"A description can be added for each and every unique relay ID. This is " -"useful to distinguish between multiple different ports/appliactions." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:27 -#: 7092920df24f4224907df1d5e383c663 -msgid "" -"The interface used to receive and relay individual broadcast packets. If you" -" want to receive/relay packets on both `eth1` and `eth2` both interfaces " -"need to be added." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:33 -#: 4f69c5bb026640cdb0470e0610b245bd -msgid "" -"Set the source IP of forwarded packets, otherwise original senders address " -"is used." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:38 -#: a7d648f85d454fd7b66b4ba586487851 -msgid "" -"The UDP port number used by your apllication. It is mandatory for this kind " -"of operation." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:43 -#: 45a8cdfb71784ea69027fc5439c41335 -msgid "" -"Each broadcast relay instance can be individually disabled without deleting " -"the configured node by using the following command:" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:48 -#: 7e5ebed6ce424eb5aa33dede00857afa -msgid "" -"In addition you can also disable the whole service without the need to " -"remove it from the current configuration." -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:51 -#: 5ac7029ed7d94b50ac814147f7f63ee8 -msgid "" -"You can run the UDP broadcast relay service on multiple routers connected to" -" a subnet. There is **NO** UDP broadcast relay packet storm!" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:55 -#: 6c4bb0dd723d4556b03c43078ad207d7 -msgid "Example" -msgstr "" - -#: ../../configuration/service/broadcast-relay.rst:57 -#: e6f77f5519d4448197a90ec3bf701fae -msgid "" -"To forward all broadcast packets received on `UDP port 1900` on `eth3`, " -"`eth4` or `eth5` to all other interfaces in this configuration." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/conntrack-sync.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/conntrack-sync.po deleted file mode 100644 index 4ba2867d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/conntrack-sync.po +++ /dev/null @@ -1,230 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/conntrack-sync.rst:5 -#: b551a0606c1d407889b7ec88a15a1205 -msgid "Conntrack Sync" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:7 -#: d1c86a591ee44a79ac077ef030d566a1 -msgid "" -"One of the important features built on top of the Netfilter framework is " -"connection tracking. Connection tracking allows the kernel to keep track of " -"all logical network connections or sessions, and thereby relate all of the " -"packets which may make up that connection. NAT relies on this information to" -" translate all related packets in the same way, and iptables can use this " -"information to act as a stateful firewall." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:14 -#: 627509ed87934f4a8c080172673383bf -msgid "" -"The connection state however is completely independent of any upper-level " -"state, such as TCP's or SCTP's state. Part of the reason for this is that " -"when merely forwarding packets, i.e. no local delivery, the TCP engine may " -"not necessarily be invoked at all. Even connectionless-mode transmissions " -"such as UDP, IPsec (AH/ESP), GRE and other tunneling protocols have, at " -"least, a pseudo connection state. The heuristic for such protocols is often " -"based upon a preset timeout value for inactivity, after whose expiration a " -"Netfilter connection is dropped." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:23 -#: 3224e71801764714b195a539bb4c0b20 -msgid "" -"Each Netfilter connection is uniquely identified by a (layer-3 protocol, " -"source address, destination address, layer-4 protocol, layer-4 key) tuple. " -"The layer-4 key depends on the transport protocol; for TCP/UDP it is the " -"port numbers, for tunnels it can be their tunnel ID, but otherwise is just " -"zero, as if it were not part of the tuple. To be able to inspect the TCP " -"port in all cases, packets will be mandatorily defragmented." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:30 -#: 0b13a06f7c414ce2a2c68f8751a8ace4 -msgid "" -"It is possible to use either Multicast or Unicast to sync conntrack traffic." -" Most examples below show Multicast, but unicast can be specified by using " -"the \"peer\" keywork after the specificed interface, as in the following " -"example:" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:34 -#: c3982c7a20194ae79688835df39ec83f -msgid ":cfgcmd:`set service conntrack-sync interface eth0 peer 192.168.0.250`" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:38 -#: 6b6091ece83a41dfa5ba57da3c33a2a7 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:42 -#: adf2df21c38e454eb47da121a5ab5275 -msgid "" -"Accept only certain protocols: You may want to replicate the state of flows " -"depending on their layer 4 protocol." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:45 -#: 70c8ed63b11c4001b54cc990dbe72937 -msgid "Protocols are: tcp, sctp, dccp, udp, icmp and ipv6-icmp." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:49 -#: 246df012a5934d0bbd2034e459074d90 -msgid "" -"The daemon doubles the size of the netlink event socket buffer size if it " -"detects netlink event message dropping. This clause sets the maximum buffer " -"size growth that can be reached." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:53 -#: 8fdae35a1e394bd396ae5a07981e699f -msgid "Queue size for listening to local conntrack events in MB." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:57 -#: dbce76d4d3ee4c27801669852e8fa258 -msgid "Protocol for which expect entries need to be synchronized." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:61 -#: ed965d99e22f4c808d7ca4f8d5daea9f -msgid "Failover mechanism to use for conntrack-sync." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:63 -#: b03daa03c13b4f7f954d555c7441b29a -msgid "Only VRRP is supported. Required option." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:67 -#: 8f43977bf6be42f5b0c16dd9ae8502b7 -msgid "" -"IP addresses or networks for which local conntrack entries will not be " -"synced" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:71 -#: 7b59ffd55fb24f928d4570b3f7193ed5 -msgid "Interface to use for syncing conntrack entries." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:75 -#: cd859e4d46ff4d2a922d65595a93e107 -msgid "Multicast group to use for syncing conntrack entries." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:77 -#: 28e7cb0eedec4389bf42ed20f29adacd -msgid "Defaults to 225.0.0.50." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:81 -#: 8b1aa1b96fa144ea940624b6792ca887 -msgid "" -"Peer to send unicast UDP conntrack sync entires to, if not using Multicast " -"configuration from above above." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:86 -#: fe8e336555fc46dba2e39b1946d3bbfd -msgid "Queue size for syncing conntrack entries in MB." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:90 -#: f3a3f3560bfe4bf59f376f5e391db132 -msgid "Operation" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:94 -#: bf3cea7e40da4b2c916e5aeb53723899 -msgid "" -"Make sure conntrack is enabled by running and show connection tracking " -"table." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:113 -#: 549c166e52174028b0e7688e9d935f03 -msgid "" -"If the table is empty and you have a warning message, it means conntrack is " -"not enabled. To enable conntrack, just create a NAT or a firewall rule. " -":cfgcmd:`set firewall state-policy established action accept`" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:119 -#: 9b4071949af8420cb6f97a441c40cb22 -msgid "Show connection syncing external cache entries" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:123 -#: 50e4bcd6bdb448afaddd472ec99ac8c5 -msgid "Show connection syncing internal cache entries" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:127 -#: 4cbfe24578054eb6b1aad18f133436aa -msgid "Retrieve current statistics of connection tracking subsystem." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:160 -#: 9b76977048174b938f584053597b6b00 -msgid "Retrieve current status of connection tracking subsystem." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:173 -#: d9070014d8df43eb8977836b83ef6124 -msgid "Example" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:175 -#: bd616f885bbc4972b5ded6eba21e8207 -msgid "The next example is a simple configuration of conntrack-sync." -msgstr "" - -#: ../../configuration/service/conntrack-sync.rstNone -#: d1c3eecec50a49b391bc71ef78ef814a -msgid "Conntrack Sync Example" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:181 -#: ec26b7452705478baca5db6df25d1c6b -msgid "" -"Now configure conntrack-sync service on ``router1`` **and** ``router2``" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:194 -#: 43cfe86bbf074bcdbda86d087382a328 -msgid "" -"On the active router, you should have information in the internal-cache of " -"conntrack-sync. The same current active connections number should be shown " -"in the external-cache of the standby router" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:198 -#: 480b10160187432c84138a3b57cb84f3 -msgid "On active router run:" -msgstr "" - -#: ../../configuration/service/conntrack-sync.rst:229 -#: a96dece49d1541c89370df7d07950252 -msgid "On standby router run:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/console-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/console-server.po deleted file mode 100644 index db335c0d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/console-server.po +++ /dev/null @@ -1,171 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/console-server.rst:5 -#: 66958977a3fe400884df1779c331a5c9 -msgid "Console Server" -msgstr "" - -#: ../../configuration/service/console-server.rst:7 -#: 9e5dccb09c5f483e8e50eccd7d4dc683 -msgid "" -"Starting of with VyOS 1.3 (equuleus) we added support for running VyOS as an" -" Out-of-Band Management device which provides remote access by means of SSH " -"to directly attached serial interfaces." -msgstr "" - -#: ../../configuration/service/console-server.rst:11 -#: 2f6b6545841344acb0d7f67cf5336281 -msgid "" -"Serial interfaces can be any interface which is directly connected to the " -"CPU or chipset (mostly known as a ttyS interface in Linux) or any other USB " -"to serial converter (Prolific PL2303 or FTDI FT232/FT4232 based chips)." -msgstr "" - -#: ../../configuration/service/console-server.rst:15 -#: b7de17ba5d0b461984e8164bcc14a710 -msgid "" -"If you happened to use a Cisco NM-16A - Sixteen Port Async Network Module or" -" NM-32A - Thirty-two Port Async Network Module - this is your VyOS " -"replacement." -msgstr "" - -#: ../../configuration/service/console-server.rst:18 -#: bee7e9f6f0204ac38b3dbf28f3d52ce8 -msgid "For USB port information please refor to: :ref:`hardware_usb`." -msgstr "" - -#: ../../configuration/service/console-server.rst:21 -#: 85c1704215394e6fbcac15b1ac9b6067 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/console-server.rst:23 -#: bf2b48e0b1e542e5a9e3f795df26671b -msgid "" -"Between computers, the most common configuration used was \"8N1\": eight bit" -" characters, with one start bit, one stop bit, and no parity bit. Thus 10 " -"Baud times are used to send a single character, and so dividing the " -"signalling bit-rate by ten results in the overall transmission speed in " -"characters per second. This is also the default setting if none of those " -"options are defined." -msgstr "" - -#: ../../configuration/service/console-server.rst:31 -#: 3c9eefac12584bef92f35983f7e26b27 -msgid "" -"Configure either seven or eight data bits. This defaults to eight data bits " -"if left unconfigured." -msgstr "" - -#: ../../configuration/service/console-server.rst:36 -#: 4bc4080195fe4198b62dd15f1e92e7b8 -msgid "A user friendly description identifying the connected peripheral." -msgstr "" - -#: ../../configuration/service/console-server.rst:40 -#: f8b76e6c25d94fa6b99bf054fd6a64a1 -msgid "" -"A user friendly alias for this connection. Can be used instead of the device" -" name when connecting." -msgstr "" - -#: ../../configuration/service/console-server.rst:45 -#: ce6e4824ca234716956bb07f186860a9 -msgid "" -"Set the parity option for the console. If unset this will default to none." -msgstr "" - -#: ../../configuration/service/console-server.rst:49 -#: a3c6b8c796924c4a8957da33afe7e421 -msgid "" -"Configure either one or two stop bits. This defaults to one stop bits if " -"left unconfigured." -msgstr "" - -#: ../../configuration/service/console-server.rst:55 -#: 6091add146dc4d2da8e16e1e664ba776 -msgid "" -"USB to serial converters will handle most of their work in software so you " -"should be carefull with the selected baudrate as some times they can't cope " -"with the expected speed." -msgstr "" - -#: ../../configuration/service/console-server.rst:60 -#: 6839496499034d5c8387b4105328bbad -msgid "Remote Access" -msgstr "" - -#: ../../configuration/service/console-server.rst:62 -#: ad15143b2cfc4f3a96ae3ecf46a16329 -msgid "" -"Each individual configured console-server device can be directly exposed to " -"the outside world. A user can directly connect via SSH to the configured " -"port." -msgstr "" - -#: ../../configuration/service/console-server.rst:68 -#: 6bc9390f14d445e8b0af658ba71335c8 -msgid "" -"Accept SSH connections for the given `<device>` on TCP port `<port>`. After " -"successfull authentication the user will be directly dropped to the " -"connected serial device." -msgstr "" - -#: ../../configuration/service/console-server.rst:72 -#: ../../configuration/service/console-server.rst:109 -#: 9b7487a2a0e9488e98a7b5a5cad5f78a 1bb6ee7193c141878d6b44992e5fe5e5 -msgid "" -"Multiple users can connect to the same serial device but only one is allowed" -" to write to the console port." -msgstr "" - -#: ../../configuration/service/console-server.rst:76 -#: 02d3718b9d28488cbe5019be37db56a2 -msgid "Operation" -msgstr "" - -#: ../../configuration/service/console-server.rst:80 -#: 06d34493fdd84493b825cac92f5e4c37 -msgid "" -"Show configured serial ports and their respective interface configuration." -msgstr "" - -#: ../../configuration/service/console-server.rst:89 -#: ef7a6665e19c434d844ae5bbc3108bd8 -msgid "Show currently connected users." -msgstr "" - -#: ../../configuration/service/console-server.rst:99 -#: 48c4721d92444afca9494f00483dc3f8 -msgid "Locally connect to serial port identified by `<device>`." -msgstr "" - -#: ../../configuration/service/console-server.rst:112 -#: 11377462f7f34d6786ed3fcee77a99b1 -msgid "" -"The sequence ``^Ec?`` translates to: ``Ctrl+E c ?``. To quit the session " -"use: ``Ctrl+E c .``" -msgstr "" - -#: ../../configuration/service/console-server.rst:115 -#: 9940b442a8914c6b83241c4d1b68d5ed -msgid "" -"If ``alias`` is set, it can be used instead of the device when connecting." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-relay.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-relay.po deleted file mode 100644 index f1df96b5..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-relay.po +++ /dev/null @@ -1,232 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/dhcp-relay.rst:5 -#: f1d972af0c464a4d8d7ab9addf3f0873 -msgid "DHCP Relay" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:7 -#: 664fc9fda46845de9fa1bb7fd6ffffaf -msgid "" -"If you want your router to forward DHCP requests to an external DHCP server " -"you can configure the system to act as a DHCP relay agent. The DHCP relay " -"agent works with IPv4 and IPv6 addresses." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:11 -#: 9fc422f5bd2842289a1fe35a056650ac -msgid "" -"All interfaces used for the DHCP relay must be configured. This includes the" -" uplink to the DHCP server." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:16 -#: 5bbb2770332f4f75b9bc97ed19040a25 -msgid "IPv4 relay" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:19 -#: ../../configuration/service/dhcp-relay.rst:108 -#: 0d65f4ea66d140558b51ef83b14e57a8 c093e1a4406c4199a8bcc07f6439f708 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:23 -#: 9b751c216735430f931ad8488e635b8e -msgid "" -"Interfaces that participate in the DHCP relay process, including the uplink " -"to the DHCP server." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:28 -#: 6323b632ebc044659052973e17a3e7f3 -msgid "" -"Configure IP address of the DHCP `<server>` which will handle the relayed " -"packets." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:33 -#: 84459656951e4653b11acb29a439dd91 -msgid "" -"The router should discard DHCP packages already containing relay agent " -"information to ensure that only requests from DHCP clients are forwarded." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:37 -#: ../../configuration/service/dhcp-relay.rst:125 -#: 4f1d8d4c44db4749aa94e08316ed3a15 6a39af659a6f4af2baddf2700be1d354 -msgid "Options" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:41 -#: e203f00118d24dab93160283589644e3 -msgid "" -"Set the maximum hop `<count>` before packets are discarded. Range 0...255, " -"default 10." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:46 -#: ebc842ddcff74e04807bc7964a169469 -msgid "" -"Set maximum `<size>` of DHCP packets including relay agent information. If a" -" DHCP packet size surpasses this value it will be forwarded without " -"appending relay agent information. Range 64...1400, default 576." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:53 -#: 07663448743a48c2ace5054d4fdbb8b4 -msgid "Four policies for reforwarding DHCP packets exist:" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:55 -#: 7a7d4251e20e44699d96f772e5092c7d -msgid "" -"**append:** The relay agent is allowed to append its own relay information " -"to a received DHCP packet, disregarding relay information already present in" -" the packet." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:59 -#: e39dda42cfcc4c1db0aed505e3229ba8 -msgid "" -"**discard:** Received packets which already contain relay information will " -"be discarded." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:62 -#: 14bbfab01f0c49fda364955265b1f0f0 -msgid "" -"**forward:** All packets are forwarded, relay information already present " -"will be ignored." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:65 -#: efaf576817d44fc7bebaf197f8515d4b -msgid "" -"**replace:** Relay information already present in a packet is stripped and " -"replaced with the router's own relay information set." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:69 -#: ../../configuration/service/dhcp-relay.rst:139 -#: 7a2e5867b9774ea69bb73406c2dfe25c c0c3930fdfc74bc29d07c2d36336eefd -msgid "Example" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:71 -#: ceffa332db6547d08ee1107730c5dd02 -msgid "Listen for DHCP requests on interface ``eth1``." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:72 -#: 0a4a0caf59574158a3e70abd585a20db -msgid "DHCP server is located at IPv4 address 10.0.1.4 on ``eth2``." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:73 -#: 4020eb50e8284514b2c1a61cdd8ba724 -msgid "" -"Router receives DHCP client requests on ``eth1`` and relays them to the " -"server at 10.0.1.4 on ``eth2``." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:80 -#: ../../configuration/service/dhcp-relay.rst:80 -#: 6b0dfdb207b34724b174336d1177f8b3 74267855e3a24057876279ea593dfca6 -msgid "DHCP relay example" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:82 -#: ../../configuration/service/dhcp-relay.rst:151 -#: 07c07a511b634a9f9205d2e0acd84594 20d2f4ce58344115a9bbc3ad2238916a -msgid "The generated configuration will look like:" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:95 -#: ../../configuration/service/dhcp-relay.rst:166 -#: 675e0b25fc1344dbbf7f24ef4639e51f 4618aea51748404e832e883f0068d502 -msgid "Operation" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:99 -#: bb8a2c3cfcc6437e883088a0d18c355f -msgid "Restart DHCP relay service" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:103 -#: fa181c5724f448f2aa6554e33b1a25ab -msgid "IPv6 relay" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:112 -#: b69fae6516a54d1b803d0691ba1ee25f -msgid "Set eth1 to be the listening interface for the DHCPv6 relay." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:114 -#: ab33f5ab7a6d4a0ca985639f00d4cba3 -msgid "Multiple interfaces may be specified." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:119 -#: 532b702bd50742daa49839ad53c4e748 -msgid "" -"Specifies an upstream network `<interface>` from which replies from " -"`<server>` and other relay agents will be accepted." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:129 -#: 6649ac8820aa492da3f58cc2a2c99bbd -msgid "Set maximum hop count before packets are discarded, default: 10" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:133 -#: 3b63645067ad4e9cb1eb51d6b86160b8 -msgid "" -"If this is set the relay agent will insert the interface ID. This option is " -"set automatically if more than one listening interfaces are in use." -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:141 -#: f8e63021779e4ba2ad4b1d780b5f9228 -msgid "" -"DHCPv6 requests are received by the router on `listening interface` ``eth1``" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:142 -#: 28abea8369a0485180a40a9cf65b362e -msgid "Requests are forwarded through ``eth2`` as the `upstream interface`" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:143 -#: a36d2237ec744efcabaf3475aef738ad -msgid "External DHCPv6 server is at 2001:db8::4" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:149 -#: ../../configuration/service/dhcp-relay.rst:149 -#: 8d853fe3edbe47eea6da44c9399fb8d1 e138778511f541cfafe828f039c73760 -msgid "DHCPv6 relay example" -msgstr "" - -#: ../../configuration/service/dhcp-relay.rst:170 -#: 1a07b1d064fe424fb48791a0440f7775 -msgid "Restart DHCPv6 relay agent immediately." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-server.po deleted file mode 100644 index 327890da..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dhcp-server.po +++ /dev/null @@ -1,1223 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/dhcp-server.rst:5 -#: 505c9b867d16474d91a84441da48de6d -msgid "DHCP Server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:7 -#: 7fce6dbca2f942b3bb7af4699fb29064 -msgid "VyOS uses ISC DHCP server for both IPv4 and IPv6 address assignment." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:11 -#: bce2104f3ce8412b9c4fb51546fb2b75 -msgid "IPv4 server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:13 -#: 6d872fab612545439bc4dd42cb080912 -msgid "" -"The network topology is declared by shared-network-name and the subnet " -"declarations. The DHCP service can serve multiple shared networks, with each" -" shared network having 1 or more subnets. Each subnet must be present on an " -"interface. A range can be declared inside a subnet to define a pool of " -"dynamic addresses. Multiple ranges can be defined and can contain holes. " -"Static mappings can be set to assign \"static\" addresses to clients based " -"on their MAC address." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:22 -#: ../../configuration/service/dhcp-server.rst:586 -#: 2f386f9129804c0ca6fc123f6bd8746a 9ec9b0bc7ab84153b3768a64cf8cf4b0 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:26 -#: 9a4f96b44cbf485e839d84b9aabdb117 -msgid "" -"Create DNS record per client lease, by adding clients to /etc/hosts file. " -"Entry will have format: `<shared-network-name>_<hostname>.<domain-name>`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:31 -#: 765c5dd6e190466c98292362124c1612 -msgid "" -"Will drop `<shared-network-name>_` from client DNS record, using only the " -"host declaration name and domain: `<hostname>.<domain-name>`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:36 -#: ../../configuration/service/dhcp-server.rst:138 -#: b8029485ef3a4fd3b06ca1d5e55dde24 6c184ac0f406473aad7e614aa1bfa951 -msgid "" -"The domain-name parameter should be the domain name that will be appended to" -" the client's hostname to form a fully-qualified domain-name (FQDN) (DHCP " -"Option 015)." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:40 -#: ../../configuration/service/dhcp-server.rst:49 -#: ../../configuration/service/dhcp-server.rst:56 -#: 7f75bbd068ee4b2989f212d3df7474bc 7e47c7fd1123404ba12e9fd6afe1a41c -#: 1c2cece981644c8bb8bef63340350215 -msgid "" -"This is the configuration parameter for the entire shared network " -"definition. All subnets will inherit this configuration item if not " -"specified locally." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:45 -#: ../../configuration/service/dhcp-server.rst:145 -#: c69a8a0533744902b59743c3c0840623 d78e4bb32ce94ea99eaf8faa9661b8f5 -msgid "" -"The domain-name parameter should be the domain name used when completing DNS" -" request where no full FQDN is passed. This option can be given multiple " -"times if you need multiple search domains (DHCP Option 119)." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:54 -#: 002d884bd34446e9969a0d166ba20f3a -msgid "Inform client that the DNS server can be found at `<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:59 -#: ../../configuration/service/dhcp-server.rst:106 -#: a35d3c150a2346229057dc05ee70c6c4 6c6b7599820046359f0af900c4930b6d -msgid "Multiple DNS servers can be defined." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:63 -#: ../../configuration/service/dhcp-server.rst:152 -#: f9a5735e4f7d469986905c220b7c20cb 22afdfc1ce2a411099ce5c65be61c141 -msgid "" -"When the DHCP server is considering dynamically allocating an IP address to " -"a client, it first sends an ICMP Echo request (a ping) to the address being " -"assigned. It waits for a second, and if no ICMP Echo response has been " -"heard, it assigns the address." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:68 -#: ../../configuration/service/dhcp-server.rst:157 -#: c22ef267d08f49a18c2593c7f1215c4f 95ff61d64fba452a9d3b8dc2c4bc08ba -msgid "" -"If a response is heard, the lease is abandoned, and the server does not " -"respond to the client. The lease will remain abandoned for a minimum of " -"abandon-lease-time seconds (defaults to 24 hours)." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:72 -#: 00053f7e32bb4661bce56a0d1009c5f0 -msgid "" -"If there are no free addresses but there are abandoned IP addresses, the " -"DHCP server will attempt to reclaim an abandoned IP address regardless of " -"the value of abandon-lease-time." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:78 -#: a856333a3f334178bb9f257fa480a503 -msgid "" -"This configuration parameter lets the DHCP server to listen for DHCP " -"requests sent to the specified address, it is only realistically useful for " -"a server whose only clients are reached via unicasts, such as via DHCP relay" -" agents." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:84 -#: 42a4bc77833d486da11a2a7b51960ae7 -msgid "Individual Client Subnet" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:88 -#: cfb28248bc7b4d75a21afc8fcdcf4038 -msgid "" -"This says that this device is the only DHCP server for this network. If " -"other devices are trying to offer DHCP leases, this machine will send " -"'DHCPNAK' to any device trying to request an IP address that is not valid " -"for this network." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:96 -#: 0153c4fbf005431690d8868b6a59098a -msgid "" -"This is a configuration parameter for the `<subnet>`, saying that as part of" -" the response, tell the client that the default gateway can be reached at " -"`<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:103 -#: ec654be7a2df4576b1cd4512f4fba3e3 -msgid "" -"This is a configuration parameter for the subnet, saying that as part of the" -" response, tell the client that the DNS server can be found at `<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:111 -#: b6681b02c2ba45588ce3e6e473dd2d69 -msgid "Assign the IP address to this machine for `<time>` seconds." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:113 -#: 5fd94b39391045a7a540a07f7799962c -msgid "The default value is 86400 seconds which corresponds to one day." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:118 -#: 147eafb1ac934345b9ad69fa3ff8b542 -msgid "" -"Create DHCP address range with a range id of `<n>`. DHCP leases are taken " -"from this pool. The pool starts at address `<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:124 -#: 7609d5c9dcd64fa888f867fb1e710d22 -msgid "" -"Create DHCP address range with a range id of `<n>`. DHCP leases are taken " -"from this pool. The pool stops with address `<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:130 -#: dfa737ed587445d29fd834b342649cd4 -msgid "" -"Always exclude this address from any defined range. This address will never " -"be assigned by the DHCP server." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:133 -#: cb3fa1be6bba44a3ae6f7c5ddebb942e -msgid "This option can be specified multiple times." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:161 -#: 3aa316547a1f41c4a7c606b91204b993 -msgid "" -"If a there are no free addresses but there are abandoned IP addresses, the " -"DHCP server will attempt to reclaim an abandoned IP address regardless of " -"the value of abandon-lease-time." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:168 -#: 5c9282ed97a64e3b89358683e741fadf -msgid "Enable DHCP failover configuration for this address pool." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:171 -#: ../../configuration/service/dhcp-server.rst:428 -#: ae9e9a8b97fb4e8792340b61b97a155f 08d011d5e50d4be5a8b23fecf44cbf10 -msgid "Failover" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:173 -#: 92289fcd2a59467fb6eb8fa3564615f9 -msgid "" -"VyOS provides support for DHCP failover. DHCP failover must be configured " -"explicitly by the following statements." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:178 -#: 04981005da2f40a286b80fcbf49bdfbe -msgid "Local IP `<address>` used when communicating to the failover peer." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:182 -#: f1b95d8cbdd84951a3f217ddef428e8e -msgid "" -"Remote peer IP `<address>` of the second DHCP server in this failover " -"cluster." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:187 -#: 9b9802d7bb284594a3037b94ad2c344a -msgid "A generic `<name>` referencing this sync service." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:189 -#: f8187bf238a54b25b57abf2050f3c648 -msgid "`<name>` must be identical on both sides!" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:193 -#: d609fe9b84024ce1b953db0523d55792 -msgid "" -"The primary and secondary statements determines whether the server is " -"primary or secondary." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:196 -#: d9db90ecac3c408d96e1867e55d9d8cb -msgid "" -"In order for the primary and the secondary DHCP server to keep their lease " -"tables in sync, they must be able to reach each other on TCP port 647. If " -"you have firewall rules in effect, adjust them accordingly." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:200 -#: d94fab1c53e24b54a3cbc823adae2dc1 -msgid "" -"The dialogue between failover partners is neither encrypted nor " -"authenticated. Since most DHCP servers exist within an organisation's own " -"secure Intranet, this would be an unnecessary overhead. However, if you have" -" DHCP failover peers whose communications traverse insecure networks, then " -"we recommend that you consider the use of VPN tunneling between them to " -"ensure that the failover partnership is immune to disruption (accidental or " -"otherwise) via third parties." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:209 -#: ../../configuration/service/dhcp-server.rst:689 -#: 915328c8c0b4487b92421878fbcdadce 456dc7dc155e4c80a03fbd3bada9eb23 -msgid "Static mappings" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:211 -#: 742eede353fa4672a108af5f04976146 -msgid "" -"You can specify a static DHCP assignment on a per host basis. You will need " -"the MAC address of the station and your desired IP address. The address must" -" be inside the subnet definition but can be outside of the range statement." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:218 -#: b0316adb23314d87abad81baba2f65de -msgid "" -"Create a new DHCP static mapping named `<description>` which is valid for " -"the host identified by its MAC `<address>`." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:224 -#: 9a53d03347444c22b2caf331d62dbf8d -msgid "" -"Static DHCP IP address assign to host identified by `<description>`. IP " -"address must be inside the `<subnet>` which is defined but can be outside " -"the dynamic range created with :cfgcmd:`set service dhcp-server shared-" -"network-name <name> subnet <subnet> range <n>`. If no ip-address is " -"specified, an IP from the dynamic pool is used." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:230 -#: 699f4678f1724d14b0daa06973bf501f -msgid "This is useful, for example, in combination with hostfile update." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:232 -#: 10c23d3c6e1446eb979246ee507f23d8 -msgid "This is the equivalent of the host block in dhcpd.conf of isc-dhcpd." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:235 -#: ../../configuration/service/dhcp-server.rst:657 -#: ../../configuration/service/dhcp-server.rst:694 -#: d9c6f9561465498690cbe53ec4bbf960 63f91d9659354d22a1bb8a913c94f1ce -#: 08b99181213d4b509df4cd3dbbc6c5d1 -msgid "**Example:**" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:237 -#: 51903f745c0741f2aff0adcf22efcc5a -msgid "" -"IP address ``192.168.1.100`` shall be statically mapped to client named " -"``client100``" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:244 -#: ../../configuration/service/dhcp-server.rst:670 -#: ../../configuration/service/dhcp-server.rst:712 -#: 1a04659d04aa4507b867740746074b31 a4181c5a9c484911bd688c8ae90b15a6 -#: e24c6f63e47940d0bcde0ee170ff1db4 -msgid "The configuration will look as follows:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:257 -#: adee6ce953fe47779ef471a90398132e -msgid "Options" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:264 -#: 42473e45a68e42e6925777225e41e89d -msgid "Setting name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:265 -#: b0df637f55e7477f98033ef4f6f24245 -msgid "Option number" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:266 -#: 2d119fbacc2c4168bdbef2f68580004f -msgid "ISC-DHCP Option name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:267 -#: 521bdf44330f456abce55ab084a9f983 -msgid "Option description" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:268 -#: f29ff738eed2453baa308cdd3fc3f53b -msgid "Multi" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:269 -#: 354d1d886d6745a6825d749f3396c838 -msgid "client-prefix-length" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:270 -#: 0a7521437b924626927f06537d96277c -msgid "1" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:271 -#: 1a8afab12fee4cbe84ed796a3d878e45 -msgid "subnet-mask" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:272 -#: bda63b0359c742389b919d02efde44b4 -msgid "" -"Specifies the clients subnet mask as per RFC 950. If unset, subnet " -"declaration is used." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:274 -#: ../../configuration/service/dhcp-server.rst:280 -#: ../../configuration/service/dhcp-server.rst:285 -#: ../../configuration/service/dhcp-server.rst:305 -#: ../../configuration/service/dhcp-server.rst:320 -#: ../../configuration/service/dhcp-server.rst:325 -#: ../../configuration/service/dhcp-server.rst:330 -#: ../../configuration/service/dhcp-server.rst:335 -#: ../../configuration/service/dhcp-server.rst:340 -#: ../../configuration/service/dhcp-server.rst:360 -#: ../../configuration/service/dhcp-server.rst:365 -#: ../../configuration/service/dhcp-server.rst:370 -#: b74fa8aab9b24cf2823a52c0a83e7604 3e6a030b4412403db29520c5572992d9 -#: a13fd7c8feaa431496ef41f3dea176cc 250e5e83c8454c1c8f63f9ce7a97d3dc -#: 3bb7709f5d75451cbb37c8b7aaa76f6a ac35960b949341ddbc35144fa4d2a667 -#: b9e18865571c4ae8929bcf1b46291015 fc29debd6dcc449ab27aa76e0125c9df -#: 7a8b209e89874d658c9967c3c2ca7d0f 60f84a800ba04cdd92d1897f506dc048 -#: 6633bab135314b7183fa907e22e84bc0 67d81f38743e440c85de6587c78a4092 -msgid "N" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:275 -#: ../../configuration/service/dhcp-server.rst:277 -#: 9f96eb328e7e46c5b1d2d84d648270a7 4682f658309e4610a274393188b59403 -msgid "time-offset" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:276 -#: 3da301e946f142a38ddb75110e008295 -msgid "2" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:278 -#: fc08f0e153cf4bf9a5b653df3483da4d -msgid "" -"Offset of the client's subnet in seconds from Coordinated Universal Time " -"(UTC)" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:281 -#: bd06a69f8937435ea694e78eb2a9ecfc -msgid "default-router" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:282 -#: ecb7d5015c784f11937d8cbeacb39abf -msgid "3" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:283 -#: 10169d3957bc4f5ea7fb18f88fed2f93 -msgid "routers" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:284 -#: 763cc03a25b04d8081b92152842c4184 -msgid "IPv4 address of router on the client's subnet" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:286 -#: 235d8e8b416f44528a5ab47fe97bd3ad -msgid "time-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:287 -#: 5d8f56999651440eadae78ba8c80231b -msgid "4" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:288 -#: 6379f4da99e840258f84285549b78d91 -msgid "time-servers" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:289 -#: 9e436b17d64b4e259bbf5b0706fba1e8 -msgid "RFC 868 time server IPv4 address" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:290 -#: ../../configuration/service/dhcp-server.rst:295 -#: ../../configuration/service/dhcp-server.rst:300 -#: ../../configuration/service/dhcp-server.rst:310 -#: ../../configuration/service/dhcp-server.rst:315 -#: ../../configuration/service/dhcp-server.rst:345 -#: ../../configuration/service/dhcp-server.rst:350 -#: ../../configuration/service/dhcp-server.rst:355 -#: ../../configuration/service/dhcp-server.rst:375 -#: ../../configuration/service/dhcp-server.rst:380 -#: ../../configuration/service/dhcp-server.rst:390 -#: 79f8d4fc6715425296778c198a9b6ef1 1825ccf896454ec8989745f1b3a7feea -#: 0043c0a150804a248ac4c528193426c2 c6b3d2b3e94f4cda89852214ba0a1e36 -#: 91d5443be7ae400ba1a914d071903c1a baad4d4678a14019a919dd2cdb37b95a -#: a8ea6850d89d4e95a4ac8ff789c93a57 3af08502e7204908812bee985a410d79 -#: 75166f614e784bbf890ecb94e6f7c8d5 ae7b57e7bfa14468af868d39bd1ee947 -#: 6aa86875a0624288b140f07b8b87ce7a -msgid "Y" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:291 -#: 20155a65ac524c0ea5fb3431683068ca -msgid "name-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:292 -#: dbcdfc6dd0c64023b9c72210185d9e79 -msgid "6" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:293 -#: eed89e902a654d9eb9ff45568f6f8c29 -msgid "domain-name-servers" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:294 -#: 8a63d007353847e88ecd484f69debcfc -msgid "DNS server IPv4 address" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:296 -#: ../../configuration/service/dhcp-server.rst:298 -#: d795102021624ab385ae11b3859bad16 e9867347b56441e6bdabc0165e678e66 -msgid "domain-name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:297 -#: 70c5e2a33e764cf28ba946857899525b -msgid "15" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:299 -#: 65c43c9b9f9440959880003d3c750839 -msgid "Client domain name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:301 -#: ../../configuration/service/dhcp-server.rst:303 -#: 190b30a0cbbd48e7a7cef93e5145a319 0855e923efae42bdbeefb259e4b11ecb -msgid "ip-forwarding" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:302 -#: d6d7248f918b412c8da840011717da72 -msgid "19" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:304 -#: 90d50be416bb4b5e9163c91d2daa42ba -msgid "Enable IP forwarding on client" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:306 -#: 7d080fd2614d4105834214586a2f51ee -msgid "ntp-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:307 -#: 862f62ca675246668e00d89a03efd4de -msgid "42" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:308 -#: 019ade15e4d84e9fb084ef851d79dd59 -msgid "ntp-servers" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:309 -#: 192e1fad3a104423af13574450036a37 -msgid "IP address of NTP server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:311 -#: aa18011b1660423e816f3a75712e0253 -msgid "wins-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:312 -#: 80a0c80438f444618df0feabd4743314 -msgid "44" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:313 -#: a8754eb857a940d59894ff95d09aa2b5 -msgid "netbios-name-servers" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:314 -#: d2d4cf91b2da47e78d8aa20d7f3a5cd5 -msgid "NetBIOS over TCP/IP name server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:316 -#: c63529ec069e41c5956a4414006c3f33 -msgid "server-identifier" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:317 -#: d9378feecc594f9d845cbb21f37fa89c -msgid "54" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:318 -#: 9c625b43a4ec412385c9adaa75cd525e -msgid "dhcp-server-identifier" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:319 -#: b06ab50ee4ff477390c2850ba041d865 -msgid "IP address for DHCP server identifier" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:321 -#: 54e2fdfcdfc045008027091d1c85b360 -msgid "bootfile-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:322 -#: aeca39081bfc44e398d71aea550c9ac3 -msgid "siaddr" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:323 -#: 192c48c2564f409da7110060b1e1f8e4 -msgid "next-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:324 -#: 05509f5959fc436fa14f596cf909f616 -msgid "IPv4 address of next bootstrap server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:326 -#: ../../configuration/service/dhcp-server.rst:328 -#: 04ae5bb06e56418f8688bb37775c16a9 6fcb5abea5c94651b8e3a6a935afe8b6 -msgid "tftp-server-name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:327 -#: ce86d7bcd6b54e56b7d39165d51cdca0 -msgid "66" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:329 -#: f3def37134d649869fded6c6ca6f7d77 -msgid "Name or IPv4 address of TFTP server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:331 -#: ffd85b9d0c184ba78b1dab680742bf5e -msgid "bootfile-name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:332 -#: 4da5a1dba3274e3c943fb95bf19018a8 -msgid "67" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:333 -#: da08160fd440461f9969bfe635744c06 -msgid "bootfile-name, filename" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:334 -#: 05bde961228444aca9d3b925f1d46798 -msgid "Bootstrap file name" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:336 -#: 0452fb9e7b4c4f89901375e2056d930d -msgid "bootfile-size" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:337 -#: a037d03606a842c2a0c8074a92a390c6 -msgid "13" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:338 -#: 950e5dab635a4e1d8cddd3e4d3ec4845 -msgid "boot-size" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:339 -#: 4880149eb083443e8c86e882d467d9c1 -msgid "Boot image length in 512-octet blocks" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:341 -#: ../../configuration/service/dhcp-server.rst:343 -#: 95464169265e4760bd84d839f457c1cf c5c9c17c5cf1448db27a8791b6c98799 -msgid "smtp-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:342 -#: 9c5c31ac645d48c6987cba4d606cdd6b -msgid "69" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:344 -#: 46c9a0f594f648e4834ce059b88a1ece -msgid "IP address of SMTP server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:346 -#: ../../configuration/service/dhcp-server.rst:348 -#: 2d0ae7ee2bf94a3f88de4a3e2169d08e 72cefb6a353c4cc2902a0d600bef0042 -msgid "pop-server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:347 -#: a5d7bb08c4ef48f5907ae9d07dda3596 -msgid "70" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:349 -#: 4bcf4378bf064372bcc3b70f608f886b -msgid "IP address of POP3 server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:351 -#: ../../configuration/service/dhcp-server.rst:353 -#: ce53f02045ec470dadeed46b0ae66cc3 93f9be9ce9e24c6a985f74004ff9be27 -msgid "domain-search" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:352 -#: 687f37f788094da98e5dfc0d3c1a8423 -msgid "119" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:354 -#: 1cd10f1b2ea8482aac5cc25149fe1350 -msgid "Client domain search" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:356 -#: b415652bc9704077b578a81b8a8bef17 -msgid "static-route" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:357 -#: 7e85d0cfda7f4cf0977a17a02bac6741 -msgid "121, 249" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:358 -#: abd3650b2c0342a39af31fd9471749b4 -msgid "rfc3442-static-route, windows-static-route" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:359 -#: 031d7ccbe73042d19cdd2849eb023b6d -msgid "Classless static route" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:361 -#: 70b68284c67a464f8f34e381a4dfb544 -msgid "wpad-url" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:362 -#: 6c758f08e7fc4cec8d2dc388ee178e83 -msgid "252" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:363 -#: 5d8a68e110df42f9a7e44f38d7588fa3 -msgid "wpad-url, wpad-url code 252 = text" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:364 -#: 899b9159612e4194bed2dbc0cc054fa4 -msgid "Web Proxy Autodiscovery (WPAD) URL" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:366 -#: e641940093f64688aa5b69ab50ff349f -msgid "lease" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:368 -#: 986340f1ad0246fc90c35b3e20966eed -msgid "default-lease-time, max-lease-time" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:369 -#: 280a1d4bae524aa4af72d4bb34315d5f -msgid "Lease timeout in seconds (default: 86400)" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:371 -#: ../../configuration/service/dhcp-server.rst:373 -#: 80e0f66d43f4439ab536f3b1efb6b656 a501491d5e6748d4a3f9142df1f3597f -msgid "range" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:374 -#: 40d263a108af47d9b9e444936297e526 -msgid "DHCP lease range" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:376 -#: 1ae8e7c490ba4762a84b2b2f7af77bbc -msgid "exclude" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:379 -#: ff168a5e3a904079a4587ee476fd6191 -msgid "IP address to exclude from DHCP lease range" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:381 -#: fba9441866b54b1ebacb9e3be9ba401a -msgid "failover" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:384 -#: 0b333e3927ba4fd6a364de7053beec93 -msgid "DHCP failover parameters" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:386 -#: 872d33a47b66446bb077f9b6171f1d48 -msgid "static-mapping" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:389 -#: 12c59e9f77b14573b3680b8bbc260b46 -msgid "Name of static mapping" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:392 -#: 3fecfb4a7adb4b5cad03726398e206df -msgid "Multi: can be specified multiple times." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:395 -#: ../../configuration/service/dhcp-server.rst:471 -#: 31b7ade9bec84b19be029e0f776c5fb5 f44e3541cb734e8895abda48f2280c79 -msgid "Raw Parameters" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:397 -#: ecb53fa77d1d448183c0ea00437b9cb1 -msgid "" -"Raw parameters can be passed to shared-network-name, subnet and static-" -"mapping:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:409 -#: ebeb6c9b0006410c9d0df116bbe0e55b -msgid "" -"These parameters are passed as-is to isc-dhcp's dhcpd.conf under the " -"configuration node they are defined in. They are not validated so an error " -"in the raw parameters won't be caught by vyos's scripts and will cause dhcpd" -" to fail to start. Always verify that the parameters are correct before " -"committing the configuration. Refer to isc-dhcp's dhcpd.conf manual for more" -" information: https://kb.isc.org/docs/isc-dhcp-44-manual-pages-dhcpdconf" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:416 -#: 99ea1d2c6ab7421d9e4635d556295c03 -msgid "" -"Quotes can be used inside parameter values by replacing all quote characters" -" with the string ``"``. They will be replaced with literal quote " -"characters when generating dhcpd.conf." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:421 -#: 491edc8964d44ce09e9ce78a3fbd5391 -msgid "Example" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:423 -#: 94a8fc41e2534c37a12f13793410fc9e -msgid "Please see the :ref:`dhcp-dns-quick-start` configuration." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:430 -#: b8fdd93a617d41b3bf825f9f9942f49a -msgid "Configuration of a DHCP failover pair" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:432 -#: 95c0392d41f44e41b0bdd0bd68e2bb71 -msgid "Setup DHCP failover for network 192.0.2.0/24" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:433 -#: 71beae4a355f4855a3c9466595d2731a -msgid "Default gateway and DNS server is at `192.0.2.254`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:434 -#: 17c3b77cd53c407e8edf3020653415e3 -msgid "The primary DHCP server uses address `192.168.189.252`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:435 -#: 99da3d86a1f544d4afc1dd7e8553cbb4 -msgid "The secondary DHCP server uses address `192.168.189.253`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:436 -#: 232072ab0d734acab7a809e313cc7e38 -msgid "DHCP range spans from `192.168.189.10` - `192.168.189.250`" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:438 -#: 867208a071554a788a34de57e3bdc4a6 -msgid "Common configuration, valid for both primary and secondary node." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:450 -#: 561a050b34ad495a80ba31ae37bd982f -msgid "**Primary**" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:459 -#: 3a0a8287b91e4d9f962f65e5c89ea247 -msgid "**Secondary**" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:473 -#: 9c0ee93793cf4446a0c96785de4fb1a1 -msgid "" -"Override static-mapping's name-server with a custom one that will be sent " -"only to this host." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:475 -#: 5c8ca344cafe41f589ce3a11d95813c1 -msgid "" -"An option that takes a quoted string is set by replacing all quote " -"characters with the string ``"`` inside the static-mapping-parameters " -"value. The resulting line in dhcpd.conf will be ``option pxelinux.configfile" -" \"pxelinux.cfg/01-00-15-17-44-2d-aa\";``." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:487 -#: 214aa9ce80b84470b1b5cceca9262ed1 -msgid "Option 43 for UniFI" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:489 -#: 08710e76092547f797d67638d0846b7d -msgid "" -"These parameters need to be part of the DHCP global options. They stay " -"unchanged." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:503 -#: fcbfa1af2dee49c59a125cfa8dfddbc9 -msgid "Now we add the option to the scope, adapt to your setup" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:512 -#: ../../configuration/service/dhcp-server.rst:732 -#: d5536d21f979475aae30ac9fab79b3b2 b07e7bbfebdd49d083d443321a4effe9 -msgid "Operation Mode" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:516 -#: 5fcda5fdbb5f4eaba41dfc6676617cde -msgid "Show DHCP server daemon log file" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:520 -#: 6a113b30011d4bb9a9e0df3dfd07a312 -msgid "Show logs from all DHCP client processes." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:524 -#: 4f2cb913ec6040b9891c261ebcdaa28d -msgid "Show logs from specific `interface` DHCP client process." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:528 -#: f0ab1b7267b64cd8a846d51fac770ae0 -msgid "Restart the DHCP server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:532 -#: 7e810bc9218643b6bdd2a1af7ba7a41d -msgid "Show the DHCP server statistics:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:543 -#: 062d6af0cb954a85b27d9b1a52031689 -msgid "Show the DHCP server statistics for the specified pool." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:547 -#: 9c1daf4574ce421c99ed90df817089f1 -msgid "Show statuses of all active leases:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:557 -#: ../../configuration/service/dhcp-server.rst:766 -#: ae9b1471c54643f1ab705bc546ea41bd af5c31c0838044f68f15c69849778f88 -msgid "" -"Static mappings aren't shown. To show all states, use ``show dhcp server " -"leases state all``." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:562 -#: ../../configuration/service/dhcp-server.rst:771 -#: 5604cd7fcbe14b60a5aff08bdb5d8f5d ba650b9d41064cc9823263c1bfbec36b -msgid "Show only leases in the specified pool." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:566 -#: 7f35681c62e243c2acff691b5bb44a3e -msgid "" -"Sort the output by the specified key. Possible keys: ip, hardware_address, " -"state, start, end, remaining, pool, hostname (default = ip)" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:571 -#: 9032a86745d7405ca8e16a4bee150173 -msgid "" -"Show only leases with the specified state. Possible states: all, active, " -"free, expired, released, abandoned, reset, backup (default = active)" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:578 -#: e3e3fb4ab33642b99145f3bded912a79 -msgid "IPv6 server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:580 -#: 7b88ad68138a42a9a285c1e282b75e6b -msgid "" -"VyOS also provides DHCPv6 server functionality which is described in this " -"section." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:590 -#: f3ad6e76309944e0b1d4d2ddf5038ba1 -msgid "" -"Clients receiving advertise messages from multiple servers choose the server" -" with the highest preference value. The range for this value is ``0...255``." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:596 -#: 1e2d4ff0c73b4705bdfdf0821fe05ef2 -msgid "" -"The default lease time for DHCPv6 leases is 24 hours. This can be changed by" -" supplying a ``default-time``, ``maximum-time`` and ``minimum-time``. All " -"values need to be supplied in seconds." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:603 -#: 272f4cd913454f5faaf470bc9396967c -msgid "" -"A :abbr:`NIS (Network Information Service)` domain can be set to be used for" -" DHCPv6 clients." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:609 -#: 1280b2b2dab84055aef0bfbae64f548f -msgid "" -"The procedure to specify a :abbr:`NIS+ (Network Information Service Plus)` " -"domain is similar to the NIS domain one:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:615 -#: eea79ba30d8c4cf28da90395a647d99b -msgid "Specify a NIS server address for DHCPv6 clients." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:620 -#: a33fa5e73465470baf10b423915df575 -msgid "Specify a NIS+ server address for DHCPv6 clients." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:625 -#: 4622e7d927a944dc9767c3f4e48e1088 -msgid "" -"Specify a :abbr:`SIP (Session Initiation Protocol)` server by IPv6 address " -"of Fully Qualified Domain Name for all DHCPv6 clients." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:631 -#: 6a75e4ee2b3540088847a7f00dc56a25 -msgid "A SNTP server address can be specified for DHCPv6 clients." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:634 -#: 6222a44d3b2c41038735c98722628b18 -msgid "Prefix Delegation" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:636 -#: a7da8578c5f54c40ac70583edca31dc8 -msgid "" -"To hand out individual prefixes to your clients the following configuration " -"is used:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:643 -#: 11c0030a29774f8d8be2c75599828dd0 -msgid "" -"Hand out prefixes of size `<length>` to clients in subnet `<prefix>` when " -"they request for prefix delegation." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:649 -#: 1a672fa312a6486e86155b4618dccaad -msgid "" -"Delegate prefixes from the range indicated by the start and stop qualifier." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:652 -#: 211393d681b94d87b95dd93eba158af2 -msgid "Address pools" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:654 -#: 4b062a7a1c6b4d788b735b0d3266321e -msgid "" -"DHCPv6 address pools must be configured for the system to act as a DHCPv6 " -"server. The following example describes a common scenario." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:659 -#: d84caed6e9194ec29aa60cf117ee33bb -msgid "A shared network named ``NET1`` serves subnet ``2001:db8::/64``" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:660 -#: 963b5d2bf258483aadff1ae5a3968c97 -msgid "It is connected to ``eth1``" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:661 -#: 25c0df8bc2d34c7b92b42708585715f5 -msgid "DNS server is located at ``2001:db8::ffff``" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:662 -#: f84e59b10f2c4c0696f190b5bb42ec7f -msgid "Address pool shall be ``2001:db8::100`` through ``2001:db8::199``." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:663 -#: 70e178448b9a41549521a887656c8b6b -msgid "Lease time will be left at the default value which is 24 hours" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:691 -#: f80117e8bc674bb68a52434c396f7c09 -msgid "" -"In order to map specific IPv6 addresses to specific hosts static mappings " -"can be created. The following example explains the process." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:696 -#: 3f5f67e3bc6c4b7ca4a18b7fc9e0018e -msgid "IPv6 address ``2001:db8::101`` shall be statically mapped" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:697 -#: 735ff399079143cab9bd9a9ff48c2810 -msgid "IPv6 prefix ``2001:db8:0:101::/64`` shall be statically mapped" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:698 -#: 7474e62f7b29440b925a9b1db1b6a665 -msgid "Host specific mapping shall be named ``client1``" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:700 -#: 7c8fe30d8fc54e67b5257e8a438b1ce0 -msgid "" -"The identifier is the device's DUID: colon-separated hex list (as used by " -"isc-dhcp option dhcpv6.client-id). If the device already has a dynamic lease" -" from the DHCPv6 server, its DUID can be found with ``show service dhcpv6 " -"server leases``. The DUID begins at the 5th octet (after the 4th colon) of " -"IAID_DUID." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:736 -#: 8d572850845d4db2b27eb0c20d7e19fb -msgid "Show DHCPv6 server daemon log file" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:740 -#: 1f3589aaa025440780cf97f6bc0b23ae -msgid "Show logs from all DHCPv6 client processes." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:744 -#: 2bdf1883ab7c4481bd399299d9a3d0ff -msgid "Show logs from specific `interface` DHCPv6 client process." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:748 -#: 8848d2fe143e464cbf6a10f9ec51aae2 -msgid "To restart the DHCPv6 server" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:752 -#: 332d22083e9a49d681b4643516d342f9 -msgid "To show the current status of the DHCPv6 server." -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:756 -#: 27bfa10bcf6242b4a9720cf34f76cba9 -msgid "Shows status of all assigned leases:" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:775 -#: be856d4d878a4a1295ec433ae09713ab -msgid "" -"Sort the output by the specified key. Possible keys: expires, iaid_duid, ip," -" last_comm, pool, remaining, state, type (default = ip)" -msgstr "" - -#: ../../configuration/service/dhcp-server.rst:780 -#: a05f5ac241f648a9a7cd4fb22c073b31 -msgid "" -"Show only leases with the specified state. Possible states: abandoned, " -"active, all, backup, expired, free, released, reset (default = active)" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dns.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dns.po deleted file mode 100644 index 70b8609b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/dns.po +++ /dev/null @@ -1,442 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/dns.rst:5 be0eccf16c3e4744beef004bbf6066ab -msgid "DNS Forwarding" -msgstr "" - -#: ../../configuration/service/dns.rst:8 -#: ../../configuration/service/dns.rst:198 c3d1290f85a146b18b9fd6ab8513c24b -#: e90845d6dcd14e20bba245cf44a8ed65 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/dns.rst:10 c1ba3fb5b0de47e091e555c3c59faea6 -msgid "" -"VyOS provides DNS infrastructure for small networks. It is designed to be " -"lightweight and have a small footprint, suitable for resource constrained " -"routers and firewalls. For this we utilize PowerDNS recursor." -msgstr "" - -#: ../../configuration/service/dns.rst:14 ea7fb66c11cb49968d1b11288089abdd -msgid "" -"The VyOS DNS forwarder does not require an upstream DNS server. It can serve" -" as a full recursive DNS server - but it can also forward queries to " -"configurable upstream DNS servers. By not configuring any upstream DNS " -"servers you also avoid being tracked by the provider of your upstream DNS " -"server." -msgstr "" - -#: ../../configuration/service/dns.rst:21 0ff64d30f92a492d96609709622a4dc1 -msgid "" -"Forward incoming DNS queries to the DNS servers configured under the " -"``system name-server`` nodes." -msgstr "" - -#: ../../configuration/service/dns.rst:26 87c71c49e60f442ab14fd2a108415c5e -msgid "" -"Send all DNS queries to the IPv4/IPv6 DNS server specified under " -"`<address>`. You can configure multiple nameservers here." -msgstr "" - -#: ../../configuration/service/dns.rst:31 d82ce4936b5a4076bd4193d1c9995cb3 -msgid "" -"Forward received queries for a particular domain (specified via `domain-" -"name`) to a given nameserver. Multiple nameservers can be specified. You can" -" use this feature for a DNS split-horizon configuration." -msgstr "" - -#: ../../configuration/service/dns.rst:36 81c277220d654aa5bc6230e75eca6413 -msgid "This also works for reverse-lookup zones (``18.172.in-addr.arpa``)." -msgstr "" - -#: ../../configuration/service/dns.rst:40 a84fecf9c7b34628b2fe851f21c6353b -msgid "" -"Given the fact that open DNS recursors could be used on DDoS amplification " -"attacks, you must configure the networks which are allowed to use this " -"recursor. A network of ``0.0.0.0/0`` or ``::/0`` would allow all IPv4 and " -"IPv6 networks to query this server. This is generally a bad idea." -msgstr "" - -#: ../../configuration/service/dns.rst:48 17494ac035324244983b6cee7001784d -msgid "" -"The PowerDNS recursor has 5 different levels of DNSSEC processing, which can" -" be set with the dnssec setting. In order from least to most processing, " -"these are:" -msgstr "" - -#: ../../configuration/service/dns.rst:52 66636a78b5c943b78fd7c88054828797 -msgid "" -"**off** In this mode, no DNSSEC processing takes place. The recursor will " -"not set the DNSSEC OK (DO) bit in the outgoing queries and will ignore the " -"DO and AD bits in queries." -msgstr "" - -#: ../../configuration/service/dns.rst:56 2e51660c883c472c9e94b03a4f91e837 -msgid "" -"**process-no-validate** In this mode the recursor acts as a \"security " -"aware, non-validating\" nameserver, meaning it will set the DO-bit on " -"outgoing queries and will provide DNSSEC related RRsets (NSEC, RRSIG) to " -"clients that ask for them (by means of a DO-bit in the query), except for " -"zones provided through the auth-zones setting. It will not do any validation" -" in this mode, not even when requested by the client." -msgstr "" - -#: ../../configuration/service/dns.rst:63 086dce77e4be401887e3ca38fdb91236 -msgid "" -"**process** When dnssec is set to process the behavior is similar to " -"process-no-validate. However, the recursor will try to validate the data if " -"at least one of the DO or AD bits is set in the query; in that case, it will" -" set the AD-bit in the response when the data is validated successfully, or " -"send SERVFAIL when the validation comes up bogus." -msgstr "" - -#: ../../configuration/service/dns.rst:69 4b7e5a1ded8c4c00ac5260cab7a9f087 -msgid "" -"**log-fail** In this mode, the recursor will attempt to validate all data it" -" retrieves from authoritative servers, regardless of the client's DNSSEC " -"desires, and will log the validation result. This mode can be used to " -"determine the extra load and amount of possibly bogus answers before turning" -" on full-blown validation. Responses to client queries are the same as with " -"process." -msgstr "" - -#: ../../configuration/service/dns.rst:76 f69f068934044a058c059243af30b7e1 -msgid "" -"**validate** The highest mode of DNSSEC processing. In this mode, all " -"queries will be validated and will be answered with a SERVFAIL in case of " -"bogus data, regardless of the client's request." -msgstr "" - -#: ../../configuration/service/dns.rst:80 701f22b454ba403e8117ac693f793279 -msgid "" -"The popular Unix/Linux ``dig`` tool sets the AD-bit in the query. This might" -" lead to unexpected query results when testing. Set ``+noad`` on the ``dig``" -" command line when this is the case." -msgstr "" - -#: ../../configuration/service/dns.rst:84 427795b5dc2d48ffbd30cf747d0662cc -msgid "" -"The ``CD``-bit is honored correctly for process and validate. For log-fail, " -"failures will be logged too." -msgstr "" - -#: ../../configuration/service/dns.rst:89 8a5cce7228ff4a01b9ebe080d09b3358 -msgid "" -"Do not use the local ``/etc/hosts`` file in name resolution. VyOS DHCP " -"server will use this file to add resolvers to assigned addresses." -msgstr "" - -#: ../../configuration/service/dns.rst:94 132f8475ff504a5484d67e003722b96c -msgid "" -"Maximum number of DNS cache entries. 1 million per CPU core will generally " -"suffice for most installations." -msgstr "" - -#: ../../configuration/service/dns.rst:97 5cad4345461c4b63ab0c1b4c614a3673 -msgid "This defaults to 10000." -msgstr "" - -#: ../../configuration/service/dns.rst:101 e995cca58c6344f69f9387c288eff0f0 -msgid "" -"A query for which there is authoritatively no answer is cached to quickly " -"deny a record's existence later on, without putting a heavy load on the " -"remote server. In practice, caches can become saturated with hundreds of " -"thousands of hosts which are tried only once." -msgstr "" - -#: ../../configuration/service/dns.rst:106 2a2adc3cfd5947e4adb0e90a579b1e25 -msgid "" -"This setting, which defaults to 3600 seconds, puts a maximum on the amount " -"of time negative entries are cached." -msgstr "" - -#: ../../configuration/service/dns.rst:111 5c7b57b10b0041d0937ec30cae1b3ed0 -msgid "" -"The number of milliseconds to wait for a remote authoritative server to " -"respond before timing out and responding with SERVFAIL." -msgstr "" - -#: ../../configuration/service/dns.rst:114 a54b3cb2b3164d95ac4d56d0f1df5837 -msgid "This setting defaults to 1500 and is valid between 10 and 60000." -msgstr "" - -#: ../../configuration/service/dns.rst:118 276ffb6dd4364b5b93cd944a438ab2e7 -msgid "" -"The local IPv4 or IPv6 addresses to bind the DNS forwarder to. The forwarder" -" will listen on this address for incoming connections." -msgstr "" - -#: ../../configuration/service/dns.rst:123 3bf5aa9483ad40f789a2edd621eaa318 -msgid "" -"The local IPv4 or IPv6 addresses to use as a source address for sending " -"queries. The forwarder will send forwarded outbound DNS requests from this " -"address." -msgstr "" - -#: ../../configuration/service/dns.rst:128 24dc8673dab0466f8a2b359ee3dfeb6a -msgid "" -"This makes the server authoritatively not aware of: 10.in-addr.arpa, " -"168.192.in-addr.arpa, 16-31.172.in-addr.arpa, which enabling upstream DNS " -"server(s) to be used for reverse lookups of these zones." -msgstr "" - -#: ../../configuration/service/dns.rst:133 -#: ../../configuration/service/dns.rst:241 8a465b2de4e3439fb39c6ee29d0c67ca -#: 54967759465148769f69a36795804bab -msgid "Example" -msgstr "" - -#: ../../configuration/service/dns.rst:135 d6029af4910c4ea7b3716931cfd6475d -msgid "" -"A VyOS router with two interfaces - eth0 (WAN) and eth1 (LAN) - is required " -"to implement a split-horizon DNS configuration for example.com." -msgstr "" - -#: ../../configuration/service/dns.rst:138 afc692c11c38469bafc20efe4b623ece -msgid "In this scenario:" -msgstr "" - -#: ../../configuration/service/dns.rst:140 81cc16add0a944a4a760c1e9a4ae8fba -msgid "" -"All DNS requests for example.com must be forwarded to a DNS server at " -"192.0.2.254 and 2001:db8:cafe::1" -msgstr "" - -#: ../../configuration/service/dns.rst:142 2c8239d1ac3146b2a1ea1a5f4c3c169b -msgid "" -"All other DNS requests will be forwarded to a different set of DNS servers " -"at 192.0.2.1, 192.0.2.2, 2001:db8::1:ffff and 2001:db8::2:ffff" -msgstr "" - -#: ../../configuration/service/dns.rst:144 1fa1ae10d0974f59840c4401ac60fe9f -msgid "" -"The VyOS DNS forwarder will only listen for requests on the eth1 (LAN) " -"interface addresses - 192.168.1.254 for IPv4 and 2001:db8::ffff for IPv6" -msgstr "" - -#: ../../configuration/service/dns.rst:146 ccb222184c96479fb436d1673e318cb5 -msgid "" -"The VyOS DNS forwarder will only accept lookup requests from the LAN subnets" -" - 192.168.1.0/24 and 2001:db8::/64" -msgstr "" - -#: ../../configuration/service/dns.rst:148 5f0224105a344c6882e7317eae29f696 -msgid "" -"The VyOS DNS forwarder will pass reverse lookups for 10.in-addr.arpa, " -"168.192.in-addr.arpa, 16-31.172.in-addr.arpa zones to upstream server." -msgstr "" - -#: ../../configuration/service/dns.rst:166 4c19d32a1cc94749852143556d10ef69 -msgid "Operation" -msgstr "" - -#: ../../configuration/service/dns.rst:170 f9fc8cbce0ba4f5283cf683b6b0e6636 -msgid "" -"Resets the local DNS forwarding cache database. You can reset the cache for " -"all entries or only for entries to a specific domain." -msgstr "" - -#: ../../configuration/service/dns.rst:175 7769c597a8b04ee19bdda039a9a0f6f5 -msgid "" -"Restarts the DNS recursor process. This also invalidates the local DNS " -"forwarding cache." -msgstr "" - -#: ../../configuration/service/dns.rst:183 b7d2faafe04e42c5b88c7a8213c3570e -msgid "Dynamic DNS" -msgstr "" - -#: ../../configuration/service/dns.rst:185 3dd121adbeba4147957d0affee0993f1 -msgid "" -"VyOS is able to update a remote DNS record when an interface gets a new IP " -"address. In order to do so, VyOS includes ddclient_, a Perl script written " -"for this only one purpose." -msgstr "" - -#: ../../configuration/service/dns.rst:189 12bac9daf5484d728534e7b653f2ed13 -msgid "" -"ddclient_ uses two methods to update a DNS record. The first one will send " -"updates directly to the DNS daemon, in compliance with :rfc:`2136`. The " -"second one involves a third party service, like DynDNS.com or any other " -"similar website. This method uses HTTP requests to transmit the new IP " -"address. You can configure both in VyOS." -msgstr "" - -#: ../../configuration/service/dns.rst:201 beef4ce428cd41f1bc0fae615f3f26d3 -msgid ":rfc:`2136` Based" -msgstr "" - -#: ../../configuration/service/dns.rst:205 0185af3d408846608e45ec22c9c74b90 -msgid "" -"Create new :rfc:`2136` DNS update configuration which will update the IP " -"address assigned to `<interface>` on the service you configured under " -"`<service-name>`." -msgstr "" - -#: ../../configuration/service/dns.rst:212 00dfe4a3fddb4e98aae958d219e8fdfd -msgid "" -"File identified by `<keyfile>` containing the secret RNDC key shared with " -"remote DNS server." -msgstr "" - -#: ../../configuration/service/dns.rst:218 075300679d594348a07dd38cbd39964b -msgid "" -"Configure the DNS `<server>` IP/FQDN used when updating this dynamic " -"assignment." -msgstr "" - -#: ../../configuration/service/dns.rst:224 2e52bc4fff424997a8b709646f46529b -msgid "Configure DNS `<zone>` to be updated." -msgstr "" - -#: ../../configuration/service/dns.rst:229 d1d04cf94032406890a9a3b1e5d36c30 -msgid "" -"Configure DNS `<record>` which should be updated. This can be set multiple " -"times." -msgstr "" - -#: ../../configuration/service/dns.rst:235 471a9111d60e488ba34b8aeb5537ffdf -msgid "" -"Configure optional TTL value on the given resource record. This defaults to " -"600 seconds." -msgstr "" - -#: ../../configuration/service/dns.rst:243 df5e0158331d4ac88d9c58417d474c5e -msgid "Register DNS record ``example.vyos.io`` on DNS server ``ns1.vyos.io``" -msgstr "" - -#: ../../configuration/service/dns.rst:244 8ae003c2e37f4e728ca6a65c9ec41cb0 -msgid "Use auth key file at ``/config/auth/my.key``" -msgstr "" - -#: ../../configuration/service/dns.rst:245 2f01cbf85387415492dffdbe6688046f -msgid "Set TTL to 300 seconds" -msgstr "" - -#: ../../configuration/service/dns.rst:260 166b6d697d3349919a25740eb94f37ed -msgid "This will render the following ddclient_ configuration entry:" -msgstr "" - -#: ../../configuration/service/dns.rst:277 040885ae0dec4529b7d5d90e7de39470 -msgid "" -"You can also keep different DNS zone updated. Just create a new config node:" -" ``set service dns dynamic interface <interface> rfc2136 <other-service-" -"name>``" -msgstr "" - -#: ../../configuration/service/dns.rst:282 ebf98747db064c8492f7d677c78f6929 -msgid "HTTP based services" -msgstr "" - -#: ../../configuration/service/dns.rst:284 c67d37cc72744b8b9f058e5413707edb -msgid "" -"VyOS is also able to use any service relying on protocols supported by " -"ddclient." -msgstr "" - -#: ../../configuration/service/dns.rst:286 a8468184edef4dfc8bd68523b342eaf4 -msgid "" -"To use such a service, one must define a login, password, one or multiple " -"hostnames, protocol and server." -msgstr "" - -#: ../../configuration/service/dns.rst:292 da38549569e44fca90e1e2e8d71a9396 -msgid "" -"Setup the dynamic DNS hostname `<hostname>` associated with the DynDNS " -"provider identified by `<service>` when the IP address on interface " -"`<interface>` changes." -msgstr "" - -#: ../../configuration/service/dns.rst:299 531f541a9bb34ecc9f7db81fe4b7ee02 -msgid "" -"Configure `<username>` used when authenticating the update request for " -"DynDNS service identified by `<service>`. For Namecheap, set the <domain> " -"you wish to update." -msgstr "" - -#: ../../configuration/service/dns.rst:306 0dad594d75284193a92bfbd3c89184a5 -msgid "" -"Configure `<password>` used when authenticating the update request for " -"DynDNS service identified by `<service>`." -msgstr "" - -#: ../../configuration/service/dns.rst:312 112f3acfe28f47cebafd0e625fa7122a -msgid "" -"When a ``custom`` DynDNS provider is used the protocol used for " -"communicating to the provider must be specified under `<protocol>`. See the " -"embedded completion helper for available protocols." -msgstr "" - -#: ../../configuration/service/dns.rst:319 f55b99280f6b4eba9889a6fd4ae4233c -msgid "" -"When a ``custom`` DynDNS provider is used the `<server>` where update " -"requests are being sent to must be specified." -msgstr "" - -#: ../../configuration/service/dns.rst:324 68fac9ba0f3b4f53be712ae9cf855ccf -msgid "Allow explicit IPv6 address for the interface." -msgstr "" - -#: ../../configuration/service/dns.rst:328 33a460af02ec472f946e09806b27f461 -msgid "Example:" -msgstr "" - -#: ../../configuration/service/dns.rst:330 4b007fab9b8a4012985f03f86145ffcf -msgid "Use DynDNS as your preferred provider:" -msgstr "" - -#: ../../configuration/service/dns.rst:339 84cdbb65e6dc4a85a4118bc232b5a2ea -msgid "" -"Multiple services can be used per interface. Just specify as many services " -"per interface as you like!" -msgstr "" - -#: ../../configuration/service/dns.rst:343 5052224efcbf4bfd8a69f7c2db923f1c -msgid "Example IPv6 only:" -msgstr "" - -#: ../../configuration/service/dns.rst:356 2f80ddda6c5a4e8aa2a0bc2826160948 -msgid "Running Behind NAT" -msgstr "" - -#: ../../configuration/service/dns.rst:358 38fc44bb48d64fa49b91f819500f8411 -msgid "" -"By default, ddclient_ will update a dynamic dns record using the IP address " -"directly attached to the interface. If your VyOS instance is behind NAT, " -"your record will be updated to point to your internal IP." -msgstr "" - -#: ../../configuration/service/dns.rst:362 33a4b35a1468486184426de88b8662cb -msgid "" -"ddclient_ has another way to determine the WAN IP address. This is " -"controlled by:" -msgstr "" - -#: ../../configuration/service/dns.rst:367 9096e4ab42264ba5b6216b5f8fe2db23 -msgid "" -"Use configured `<url>` to determine your IP address. ddclient_ will load " -"`<url>` and tries to extract your IP address from the response." -msgstr "" - -#: ../../configuration/service/dns.rst:372 786fc7bbabd1405bb33028a77a4bb148 -msgid "" -"ddclient_ will skip any address located before the string set in " -"`<pattern>`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/eventhandler.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/eventhandler.po deleted file mode 100644 index 64da7411..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/eventhandler.po +++ /dev/null @@ -1,165 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/eventhandler.rst:5 -#: d2144e6a1eb24783a4118338afff1d2f -msgid "Event Handler" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:9 -#: 979573eacaab46ba83f06a4908a214e8 -msgid "Event Handler Technology Overview" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:11 -#: 6970ce32aad54a07935ce20ac3971d00 -msgid "" -"Event handler allows you to execute scripts when a string that matches a " -"regex or a regex with a service name appears in journald logs. You can pass " -"variables, arguments, and a full matching string to the script." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:17 -#: 7f593868fab047028eb13b1a498cb2c9 -msgid "How to configure Event Handler" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:19 -#: fcbb47f848994a879a9676acf45fe90f -msgid "`1. Create an event handler`_" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:21 -#: 4f27c363c42d4def88f33c7425e0be83 -msgid "`2. Add regex to the script`_" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:23 -#: 484cc3d92219402b8402924350658762 -msgid "`3. Add a full path to the script`_" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:25 -#: 014aed73eeb747bab332bf551cce2a95 -msgid "`4. Add optional parameters`_" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:29 -#: b51d8f8b56c249ab8d1502e997a8cb1d -msgid "Event Handler Configuration Steps" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:32 -#: e7b303d8fa434dccb27f4026bcda1f66 -msgid "1. Create an event handler" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:36 -#: 3c0f3a0ccebf4c6786f1a410ae008f93 -msgid "" -"This is an optional command because the event handler will be automatically " -"created after any of the next commands." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:40 -#: 47b2f6e1e8cd4d8b85c7570fdd8b9326 -msgid "2. Add regex to the script" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:44 -#: 7ff6fcee218446488fe3ddc71cf9fd64 -msgid "" -"This is a mandatory command. Sets regular expression to match against log " -"string message." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:46 -#: 98be815d60404249a925a77e47294aa5 -msgid "" -"The regular expression matches if and only if the entire string matches the " -"pattern." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:51 -#: e07b0382161d4d08afdd3ed26c23ffd1 -msgid "3. Add a full path to the script" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:55 -#: 89698b6769ce446aa5bc296e302d048e -msgid "" -"This is a mandatory command. Sets the full path to the script. The script " -"file must be executable." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:60 -#: 0ade4da86ca345b19377fb62edda4df2 -msgid "4. Add optional parameters" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:64 -#: bdb4921f90d74fba9a7d7839208c7c3d -msgid "" -"This is an optional command. Filters log messages by syslog-identifier." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:68 -#: e3980d34d386476fa74a4a5dce3ddb79 -msgid "" -"This is an optional command. Adds environment and its value to the script. " -"Use separate commands for each environment." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:70 -#: dad9affa614246c3af3c9924febb0a9a -msgid "One implicit environment exists." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:72 -#: 833768ef67264f23902e3481fc3695a0 -msgid "``message``: Full message that has triggered the script." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:76 -#: 76523eafdd644d6ebec41aa58164da17 -msgid "" -"This is an optional command. Adds arguments to the script. Arguments must be" -" separated by spaces." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:78 -#: b913e33cf397425bb879ae10c5a4b2d1 -msgid "" -"We don't recomend to use arguments. Using environments is more preffereble." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:83 -#: 00ec965cf5574110909e47d79675c910 -msgid "Example" -msgstr "" - -#: ../../configuration/service/eventhandler.rst:85 -#: f6d6849c042d4e118193b3db04e818cb -msgid "Event handler that monitors the state of interface eth0." -msgstr "" - -#: ../../configuration/service/eventhandler.rst:95 -#: c7ce652b2f6748b5aa8888ba31b74554 -msgid "Event handler script" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/https.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/https.po deleted file mode 100644 index 72e4e3ef..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/https.po +++ /dev/null @@ -1,108 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/https.rst:5 6eb9ab75144b4244a9bc9a0153d710b9 -msgid "HTTP-API" -msgstr "" - -#: ../../configuration/service/https.rst:7 4aed16aabc2943d3aa001087589cd324 -msgid "" -"VyOS provide an HTTP API. You can use it to execute op-mode commands, update" -" VyOS, set or delete config." -msgstr "" - -#: ../../configuration/service/https.rst:10 23a386981be74e158019d492fe4c2712 -msgid "Please take a look at the :ref:`vyosapi` page for an detailed how-to." -msgstr "" - -#: ../../configuration/service/https.rst:14 fd48243e3cd04d9591ab4d2c06eace3d -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/https.rst:18 b46f423b568742b582ed2c5255ecd3e1 -msgid "" -"Set a named api key. Every key has the same, full permissions on the system." -msgstr "" - -#: ../../configuration/service/https.rst:23 8045fca770c04af4b68e2b301d52ef18 -msgid "" -"To enable debug messages. Available via :opcmd:`show log` or :opcmd:`monitor" -" log`" -msgstr "" - -#: ../../configuration/service/https.rst:28 ff468101dcd048eda92c63a3a67cb86c -msgid "" -"Set the listen port of the local API, this has no effect on the webserver. " -"The default is port 8080" -msgstr "" - -#: ../../configuration/service/https.rst:33 ba56034a469141e99d28b1ed23dc7473 -msgid "Use local socket for API" -msgstr "" - -#: ../../configuration/service/https.rst:37 a0bc5d08eb484d269ddafbad4e374733 -msgid "Enforce strict path checking" -msgstr "" - -#: ../../configuration/service/https.rst:42 6c7faa808c054a14a7326095a3ce2adc -msgid "Address to listen for HTTPS requests" -msgstr "" - -#: ../../configuration/service/https.rst:46 20b318a1c3da40e1a65b8bb0d5dfa101 -msgid "Port to listen for HTTPS requests; default 443" -msgstr "" - -#: ../../configuration/service/https.rst:50 ac21ead2e06c4516b178ab121a52bf90 -msgid "Server names for virtual hosts it can be exact, wildcard or regex." -msgstr "" - -#: ../../configuration/service/https.rst:54 96e4c14fde8e483897a44682e26174c3 -msgid "" -"By default, nginx exposes the local API on all virtual servers. Use this to " -"restrict nginx to one or more virtual hosts." -msgstr "" - -#: ../../configuration/service/https.rst:59 0e1b082bb57e4c279ef9359c95419bfa -msgid "Domain name(s) for which to obtain certificate" -msgstr "" - -#: ../../configuration/service/https.rst:63 1be030c1f4604be8a7fb7ffae1d7113c -msgid "Email address to associate with certificate" -msgstr "" - -#: ../../configuration/service/https.rst:67 5f41c2c1ce804065bb25e08227e01296 -msgid "Use an automatically generated self-signed certificate" -msgstr "" - -#: ../../configuration/service/https.rst:72 e75aef2259d545a8bd27ee318b3c9a41 -msgid "Lifetime in days; default is 365" -msgstr "" - -#: ../../configuration/service/https.rst:77 6992a5a7b7ad4dd6adb9fe28f2516492 -msgid "Example Configuration" -msgstr "" - -#: ../../configuration/service/https.rst:79 c988f3ba4e7746b2874ea771682811fc -msgid "" -"Set an API-KEY is the minimal configuration to get a working API Endpoint." -msgstr "" - -#: ../../configuration/service/https.rst:86 5a9df4d2dd7744ed91aaa368e13d465b -msgid "To use this full configuration we asume a public accessible hostname." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/index.po deleted file mode 100644 index 3d0fa3c4..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/index.rst:3 00c32a14ce5e43d3b3403f90a3ae4e18 -msgid "Service" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ipoe-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ipoe-server.po deleted file mode 100644 index 418afa13..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ipoe-server.po +++ /dev/null @@ -1,171 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../_include/need_improvement.txt:11 8348fbf901bb4aa2a6c7da5bdf209b7b -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 a300079c41c940848963b547888f40ba -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:7 -#: 086088e28acb4a2b98974a5605d33897 -msgid "IPoE Server" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:9 -#: 64cae27b1ad94e19b77b795448aafecc -msgid "" -"VyOS utilizes `accel-ppp`_ to provide :abbr:`IPoE (Internet Protocol over " -"Ethernet)` server functionality. It can be used with local authentication " -"(mac-address) or a connected RADIUS server." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:13 -#: 54cd75d957d643899b54eeaf83393401 -msgid "" -"IPoE is a method of delivering an IP payload over an Ethernet-based access " -"network or an access network using bridged Ethernet over Asynchronous " -"Transfer Mode (ATM) without using PPPoE. It directly encapsulates the IP " -"datagrams in Ethernet frames, using the standard :rfc:`894` encapsulation." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:18 -#: 2b94604b3daa4b5db90c5479f373855e -msgid "" -"The use of IPoE addresses the disadvantage that PPP is unsuited for " -"multicast delivery to multiple users. Typically, IPoE uses Dynamic Host " -"Configuration Protocol and Extensible Authentication Protocol to provide the" -" same functionality as PPPoE, but in a less robust manner." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:23 -#: 4cb6e537be16442dbcad8f52798734ac -msgid "" -"Please be aware, due to an upstream bug, config changes/commits will restart" -" the ppp daemon and will reset existing IPoE sessions, in order to become " -"effective." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:28 -#: f166f77cdbb64b2685742f4fca6c9d4f -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:30 -#: 4085f66aa4ac4b048480b5e316685d85 -msgid "" -"IPoE can be configure on different interfaces, it will depend on each " -"specific situation which interface will provide IPoE to clients. The clients" -" mac address and the incoming interface is being used as control parameter, " -"to authenticate a client." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:35 -#: 947c9232295b463b8071714d62638d68 -msgid "" -"The example configuration below will assign an IP to the client on the " -"incoming interface eth2 with the client mac address 08:00:27:2f:d8:06. Other" -" DHCP discovery requests will be ignored, unless the client mac has been " -"enabled in the configuration." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:49 -#: cc1541e15d514ca8a4eba781a990731a -msgid "" -"The first address of the parameter ``client-subnet``, will be used as the " -"default gateway. Connected sessions can be checked via the ``show ipoe-" -"server sessions`` command." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:63 -#: 262441ec84624c52af1b0e553876055b -msgid "IPv6 SLAAC and IA-PD" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:65 -#: 476e3aafcfc3445f90b123f57c668860 -msgid "" -"To configure IPv6 assignments for clients, two options need to be " -"configured. A global prefix which is terminated on the clients cpe and a " -"delegated prefix, the client can use for devices routed via the clients cpe." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:69 -#: a1390332b48649e0af25c379d3123a51 -msgid "IPv6 DNS addresses are optional." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:90 -#: f12341dcb01e4ee1aebc335099d09062 -msgid "" -"The clients :abbr:`CPE (Customer Premises Equipment)` can now communicate " -"via IPv4 or IPv6. All devices behind ``2001:db8::a00:27ff:fe2f:d806/64`` can" -" use addresses from ``2001:db8:1::/56`` and can globally communicate without" -" the need of any NAT rules." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:96 -#: 3dd3e5e99a3a429fbb14a39ed1b408b1 -msgid "Automatic VLAN creation" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:98 -#: 95e304ab498a48be968945d0b1473556 -msgid "" -"To create VLANs per user during runtime, the following settings are required" -" on a per interface basis. VLAN ID and VLAN range can be present in the " -"configuration at the same time." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:111 -#: 24fca7b795f745639ec2548d0a2a5f25 -msgid "RADIUS Setup" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:113 -#: aef6b9d9916c4789b55104cc3f0de005 -msgid "" -"To use a RADIUS server for authentication and bandwidth-shaping, the " -"following example configuration can be used." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:122 -#: d48bfc6944404961bc625fb8620e5b1b -msgid "Bandwidth Shaping" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:124 -#: a5c9eacd12ac43a18016de4b05bf4f8c -msgid "" -"Bandwidth rate limits can be set for local users within the configuration or" -" via RADIUS based attributes." -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:128 -#: f4a5664de23a4767819063a351f04edc -msgid "Bandwidth Shaping for local users" -msgstr "" - -#: ../../configuration/service/ipoe-server.rst:130 -#: b6aa0fdbfce5419191228b1c725623a2 -msgid "The rate-limit is set in kbit/sec." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/lldp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/lldp.po deleted file mode 100644 index e5caa7bc..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/lldp.po +++ /dev/null @@ -1,153 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/lldp.rst:5 6f7052bec41f4735894ab71472565992 -msgid "LLDP" -msgstr "" - -#: ../../configuration/service/lldp.rst:7 ab82eb7134f84f359bfeb3d75d29547c -msgid "" -":abbr:`LLDP (Link Layer Discovery Protocol)` is a vendor-neutral link layer " -"protocol in the Internet Protocol Suite used by network devices for " -"advertising their identity, capabilities, and neighbors on an IEEE 802 local" -" area network, principally wired Ethernet. The protocol is formally referred" -" to by the IEEE as Station and Media Access Control Connectivity Discovery " -"specified in IEEE 802.1AB and IEEE 802.3-2012 section 6 clause 79." -msgstr "" - -#: ../../configuration/service/lldp.rst:14 7b66e09f651e4ba09cd0d30b182d6cd8 -msgid "" -"LLDP performs functions similar to several proprietary protocols, such as " -":abbr:`CDP (Cisco Discovery Protocol)`, :abbr:`FDP (Foundry Discovery " -"Protocol)`, :abbr:`NDP (Nortel Discovery Protocol)` and :abbr:`LLTD (Link " -"Layer Topology Discovery)`." -msgstr "" - -#: ../../configuration/service/lldp.rst:20 5b85b0f7807041d8ad435b3fb0ee21ba -msgid "" -"Information gathered with LLDP is stored in the device as a :abbr:`MIB " -"(Management Information Database)` and can be queried with :abbr:`SNMP " -"(Simple Network Management Protocol)` as specified in :rfc:`2922`. The " -"topology of an LLDP-enabled network can be discovered by crawling the hosts " -"and querying this database. Information that may be retrieved include:" -msgstr "" - -#: ../../configuration/service/lldp.rst:26 81b10f8d665d4665ba2147597b9755a1 -msgid "System Name and Description" -msgstr "" - -#: ../../configuration/service/lldp.rst:27 f12327059af34dab97f315144c5597f5 -msgid "Port name and description" -msgstr "" - -#: ../../configuration/service/lldp.rst:28 de721962e67b42fca18648b6afa28499 -msgid "VLAN name" -msgstr "" - -#: ../../configuration/service/lldp.rst:29 3651d289a73c4f889eab514a076a891c -msgid "IP management address" -msgstr "" - -#: ../../configuration/service/lldp.rst:30 93b55fcddccd4e36881fc89e4e705fa8 -msgid "System capabilities (switching, routing, etc.)" -msgstr "" - -#: ../../configuration/service/lldp.rst:31 ec2c5125c2eb4bfe9c8322afdf8b6028 -msgid "MAC/PHY information" -msgstr "" - -#: ../../configuration/service/lldp.rst:32 56495c461df3456298f3a83d0a2d90ca -msgid "MDI power" -msgstr "" - -#: ../../configuration/service/lldp.rst:33 1032a065d6444d3caac841d2893c4e1e -msgid "Link aggregation" -msgstr "" - -#: ../../configuration/service/lldp.rst:36 5fe22852d4c849ae9ebd59bde7ba0dd5 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/lldp.rst:40 e4765fd56b5544c2883f7783f6b32456 -msgid "Enable LLDP service" -msgstr "" - -#: ../../configuration/service/lldp.rst:44 2043e229c59445fdb4ef9f2cbe8d0111 -msgid "" -"Define IPv4/IPv6 management address transmitted via LLDP. Multiple addresses" -" can be defined. Only addresses connected to the system will be transmitted." -msgstr "" - -#: ../../configuration/service/lldp.rst:49 35aa51dad35345d49ce9ceae391ab182 -msgid "" -"Enable transmission of LLDP information on given `<interface>`. You can also" -" say ``all`` here so LLDP is turned on on every interface." -msgstr "" - -#: ../../configuration/service/lldp.rst:54 72802aadfc444347b85e43bf68390488 -msgid "" -"Disable transmit of LLDP frames on given `<interface>`. Useful to exclude " -"certain interfaces from LLDP when ``all`` have been enabled." -msgstr "" - -#: ../../configuration/service/lldp.rst:59 4a7f7e1d26b743b0a4c7eab899884e84 -msgid "Enable SNMP queries of the LLDP database" -msgstr "" - -#: ../../configuration/service/lldp.rst:63 eeb07d0a54ba462aadf47a5c315b4056 -msgid "" -"Enable given legacy protocol on this LLDP instance. Legacy protocols " -"include:" -msgstr "" - -#: ../../configuration/service/lldp.rst:65 3e362554a74741d3b1e4cddaad2e737f -msgid "``cdp`` - Listen for CDP for Cisco routers/switches" -msgstr "" - -#: ../../configuration/service/lldp.rst:66 20fec6625c2c4e669d156a990845b652 -msgid "``edp`` - Listen for EDP for Extreme routers/switches" -msgstr "" - -#: ../../configuration/service/lldp.rst:67 e5e5ab325e194cc3b7aaf905c78cda39 -msgid "``fdp`` - Listen for FDP for Foundry routers/switches" -msgstr "" - -#: ../../configuration/service/lldp.rst:68 77b00bb648c14fc9b58cad7718d18554 -msgid "``sonmp`` - Listen for SONMP for Nortel routers/switches" -msgstr "" - -#: ../../configuration/service/lldp.rst:71 d7ccb8993a1d43b3b80d0855b927a0b7 -msgid "Operation" -msgstr "" - -#: ../../configuration/service/lldp.rst:75 9c22ec2ef62f4ac3a201492073b7d2c5 -msgid "Displays information about all neighbors discovered via LLDP." -msgstr "" - -#: ../../configuration/service/lldp.rst:91 d4dc7e4ecb874635803dd84dff2bfcac -msgid "Get detailed information about LLDP neighbors." -msgstr "" - -#: ../../configuration/service/lldp.rst:138 5de155e2ed5449ffa60185ed491c15b2 -msgid "Show LLDP neighbors connected via interface `<interface>`." -msgstr "" - -#: ../../configuration/service/lldp.rst:142 d1857d308804459d8006d15245604980 -msgid "Used for troubleshooting." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/mdns.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/mdns.po deleted file mode 100644 index e55fa7eb..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/mdns.po +++ /dev/null @@ -1,76 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/mdns.rst:2 4bf3433679154e129eae42ac905a5d41 -msgid "mDNS Repeater" -msgstr "" - -#: ../../configuration/service/mdns.rst:4 c991751ed8be473dbb1c0665979edec8 -msgid "" -"Starting with VyOS 1.2 a :abbr:`mDNS (Multicast DNS)` repeater functionality" -" is provided. Additional information can be obtained from " -"https://en.wikipedia.org/wiki/Multicast_DNS." -msgstr "" - -#: ../../configuration/service/mdns.rst:8 45c2a878be114df08e9e3fddb6c864e6 -msgid "" -"Multicast DNS uses the 224.0.0.251 address, which is \"administratively " -"scoped\" and does not leave the subnet. It retransmits mDNS packets from one" -" interface to other interfaces. This enables support for e.g. Apple Airplay " -"devices across multiple VLANs." -msgstr "" - -#: ../../configuration/service/mdns.rst:13 28390662706549e5a1c8a77a32e65453 -msgid "" -"Since the mDNS protocol sends the AA records in the packet itself, the " -"repeater does not need to forge the source address. Instead, the source " -"address is of the interface that repeats the packet." -msgstr "" - -#: ../../configuration/service/mdns.rst:18 e92b0830be3f44d0b0fe2348d90ffa44 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/mdns.rst:22 321a9b123ab04c10b556addd6794da0a -msgid "" -"To enable mDNS repeater you need to configure at least two interfaces. To " -"re-broadcast all incoming mDNS packets from any interface configured here to" -" any other interface configured under this section." -msgstr "" - -#: ../../configuration/service/mdns.rst:28 9ea15eca40e5457792e23c59c5986804 -msgid "" -"mDNS repeater can be temporarily disabled without deleting the service using" -msgstr "" - -#: ../../configuration/service/mdns.rst:30 38bfe80bba8a4f6abf2a07218e3b69ad -msgid "" -"You can not run this in a VRRP setup, if multiple mDNS repeaters are " -"launched in a subnet you will experience the mDNS packet storm death!" -msgstr "" - -#: ../../configuration/service/mdns.rst:34 31e7121ee7f74015939c3193479429a2 -msgid "Example" -msgstr "" - -#: ../../configuration/service/mdns.rst:36 a3291b8ceaab42eeadb149752462904e -msgid "" -"To listen on both `eth0` and `eth1` mDNS packets and also repeat packets " -"received on `eth0` to `eth1` (and vice-versa) use the following commands:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/monitoring.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/monitoring.po deleted file mode 100644 index 5bc46d81..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/monitoring.po +++ /dev/null @@ -1,192 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/monitoring.rst:2 -#: e706be124c4c4483ada8599d6c4cf60e -msgid "Monitoring" -msgstr "" - -#: ../../configuration/service/monitoring.rst:5 -#: eb4901eb98004eb3a432e7ad902ea55f -msgid "Azure-data-explorer" -msgstr "" - -#: ../../configuration/service/monitoring.rst:6 -#: fce461d1dc94438cb3748a66f2051cb6 -msgid "Telegraf output plugin azure-data-explorer_" -msgstr "" - -#: ../../configuration/service/monitoring.rst:10 -#: 79621ee0f9f945e49219bc940d93b94d -msgid "Authentication application client-id." -msgstr "" - -#: ../../configuration/service/monitoring.rst:14 -#: 36416eda01e440509a26216ab9c41aef -msgid "Authentication application client-secret." -msgstr "" - -#: ../../configuration/service/monitoring.rst:18 -#: 7270ccf8ffbd462e95e6c13a00591a9a -msgid "Authentication application tenant-id" -msgstr "" - -#: ../../configuration/service/monitoring.rst:22 -#: d9d6587d5eb94ca9903be0920a8c0c68 -msgid "Remote databe name." -msgstr "" - -#: ../../configuration/service/monitoring.rst:26 -#: 341f908216374250aa56bb28347b5390 -msgid "" -"Type of metrics grouping when push to Azure Data Explorer. The default is " -"``table-per-metric``." -msgstr "" - -#: ../../configuration/service/monitoring.rst:31 -#: 69c2405379af42a4b2a07f87f74f73a5 -msgid "Name of the single table Only if set group-metrics single-table." -msgstr "" - -#: ../../configuration/service/monitoring.rst:35 -#: 5a986befad944338b6b8ce9821424a4e -msgid "Remote URL." -msgstr "" - -#: ../../configuration/service/monitoring.rst:38 -#: 5ee4b2b2eb8448b797c2d85c76316853 -msgid "Prometheus-client" -msgstr "" - -#: ../../configuration/service/monitoring.rst:39 -#: 6a5626e76c39416f9929b7e95e385baf -msgid "Telegraf output plugin prometheus-client_" -msgstr "" - -#: ../../configuration/service/monitoring.rst:43 -#: e93429a097f0446bb0c07cadc9e060a3 -msgid "Output plugin Prometheus client" -msgstr "" - -#: ../../configuration/service/monitoring.rst:47 -#: 011f9b3bd5ae462a996e6292e6cf0c60 -msgid "Networks allowed to query this server" -msgstr "" - -#: ../../configuration/service/monitoring.rst:51 -#: ../../configuration/service/monitoring.rst:55 -#: f3083afa501b434495a28716ad69f8e3 b4c92d14498940e29ae4e670e7f135ae -msgid "HTTP basic authentication username" -msgstr "" - -#: ../../configuration/service/monitoring.rst:59 -#: cc6f647640b745beb1f8520a77117f90 -msgid "Local IP addresses to listen on" -msgstr "" - -#: ../../configuration/service/monitoring.rst:63 -#: c2387ebb9b1147e8a536b1fe482b8823 -msgid "Metris version, the default is ``2``" -msgstr "" - -#: ../../configuration/service/monitoring.rst:67 -#: 95eccd41ce4745d0807504e2966d6afa -msgid "Port number used by connection, default is ``9273``" -msgstr "" - -#: ../../configuration/service/monitoring.rst:69 -#: ../../configuration/service/monitoring.rst:98 -#: a9d8051100aa4daaaf7c1c09f599b503 55db67a44caa4767b8b0f91b28e5ea96 -msgid "Example:" -msgstr "" - -#: ../../configuration/service/monitoring.rst:83 -#: f67780d57da64454b2967a02126fe990 -msgid "Splunk" -msgstr "" - -#: ../../configuration/service/monitoring.rst:84 -#: 60ddd8df2a1742e59f98549832bc0472 -msgid "Telegraf output plugin splunk_. HTTP Event Collector." -msgstr "" - -#: ../../configuration/service/monitoring.rst:88 -#: 5483fc179e7245b5986f76079ff5be90 -msgid "Use TLS but skip host validation" -msgstr "" - -#: ../../configuration/service/monitoring.rst:92 -#: 64615075895942a0b7f2f653a68724cf -msgid "Authorization token" -msgstr "" - -#: ../../configuration/service/monitoring.rst:96 -#: fa795a95b5284fd1a92c4db332d08cb0 -msgid "Remote URL to Splunk collector" -msgstr "" - -#: ../../configuration/service/monitoring.rst:107 -#: 290015ea98774e45a50982fdd5fbff6f -msgid "Telegraf" -msgstr "" - -#: ../../configuration/service/monitoring.rst:108 -#: cac5d195b00c4bfbac74a8d9df4f3922 -msgid "" -"Monitoring functionality with ``telegraf`` and ``InfluxDB 2`` is provided. " -"Telegraf is the open source server agent to help you collect metrics, events" -" and logs from your routers." -msgstr "" - -#: ../../configuration/service/monitoring.rst:114 -#: aad0e7c2a001484987a8e2d30ba87cdf -msgid "Authentication organization name" -msgstr "" - -#: ../../configuration/service/monitoring.rst:118 -#: cabddf8317dc459eabd522a66a74959d -msgid "Authentication token" -msgstr "" - -#: ../../configuration/service/monitoring.rst:122 -#: fcc9aaf52c284b618a05113d946f792b -msgid "Remote ``InfluxDB`` bucket name" -msgstr "" - -#: ../../configuration/service/monitoring.rst:126 -#: 4f607da7d42d49e0b470f2f1c5ba5a80 -msgid "Remote port" -msgstr "" - -#: ../../configuration/service/monitoring.rst:130 -#: 4ba704b2d889441f9daaaf8bd927abdd -msgid "Remote URL" -msgstr "" - -#: ../../configuration/service/monitoring.rst:134 -#: 17b3a7558ea144b693e60c7b53d3d688 -msgid "Example" -msgstr "" - -#: ../../configuration/service/monitoring.rst:136 -#: 4ab7d707bea44ad89b6db89d453925ea -msgid "" -"An example of a configuration that sends ``telegraf`` metrics to remote " -"``InfluxDB 2``" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/pppoe-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/pppoe-server.po deleted file mode 100644 index 4024e9ad..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/pppoe-server.po +++ /dev/null @@ -1,426 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/pppoe-server.rst:7 -#: bd4d7b254e25420f9567a85b10201bbc -msgid "PPPoE Server" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:9 -#: 1f096fee1c05483cac964daa162c1add -msgid "" -"VyOS utilizes `accel-ppp`_ to provide PPPoE server functionality. It can be " -"used with local authentication or a connected RADIUS server." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:12 -#: ddf4a22b51d647c2877278be23425465 -msgid "" -"Please be aware, due to an upstream bug, config changes/commits will restart" -" the ppp daemon and will reset existing PPPoE connections from connected " -"users, in order to become effective." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:17 -#: 51ccdf86226347e9938cdd96a39e5e59 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:21 -#: f6727c28711c4fb8b2be338b3366c867 -msgid "First steps" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:26 -#: 37d80555046c48dfbdc4a2d33c2fe867 -msgid "" -"Use this command to set a name for this PPPoE-server access concentrator." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:31 -#: 431a1767e38a4a44851a0b002f35c612 -msgid "" -"Use this command to define whether your PPPoE clients will locally " -"authenticate in your VyOS system or in RADIUS server." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:37 -#: 4618826179a64a689456e3a849c84da5 -msgid "" -"Use this command to configure the username and the password of a locally " -"configured user." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:42 -#: 54df79824215465b97a3587f20796dda -msgid "" -"Use this command to define the interface the PPPoE server will use to listen" -" for PPPoE clients." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:47 -#: 627621d12d00412ea71a5b609c8f5906 -msgid "Use this command to configure the local gateway IP address." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:51 -#: b1aa679466b34516b69eeb8f6693f93b -msgid "" -"Use this command to set the IPv4 or IPv6 address of every Doman Name Server " -"you want to configure. They will be propagated to PPPoE clients." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:57 -#: b7a7d34a7b12485abd464df5d8e40a22 -msgid "Client Address Pools" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:59 -#: 9c18211f7b294f3a9da14afaf91341b4 -msgid "" -"To automatically assign the client an IP address as tunnel endpoint, a " -"client IP pool is needed. The source can be either RADIUS or a local subnet " -"or IP range definition." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:63 -#: c891fe4f565942eeaf8c3398b7ae77ea -msgid "" -"Once the local tunnel endpoint ``set service pppoe-server gateway-address " -"'10.1.1.2'`` has been defined, the client IP pool can be either defined as a" -" range or as subnet using CIDR notation. If the CIDR notation is used, " -"multiple subnets can be setup which are used sequentially." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:69 -#: 9cff7e48cc5d44c8afce5f00d9a73e97 -msgid "**Client IP address via IP range definition**" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:73 -#: 4125b5060b2c42a99857774d2db48da5 -msgid "" -"Use this command to define the first IP address of a pool of addresses to be" -" given to PPPoE clients. It must be within a /24 subnet." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:79 -#: 0bf22b2beeaf46d48b4aab1cebc0cb2c -msgid "" -"Use this command to define the last IP address of a pool of addresses to be " -"given to PPPoE clients. It must be within a /24 subnet." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:89 -#: 8b963fd4f6be44d9ac638d163f9ab6fe -msgid "**Client IP subnets via CIDR notation**" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:93 -#: e68c92a7ade342c7aa336f3732171593 -msgid "" -"Use this command for every pool of client IP addresses you want to define. " -"The addresses of this pool will be given to PPPoE clients. You must use CIDR" -" notation and it must be within a /24 subnet." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:104 -#: 6a43b9085cbb4e1a844d31cfca055247 -msgid "**RADIUS based IP pools (Framed-IP-Address)**" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:106 -#: e936dfd7560c4f00b9cf25eec7f3a893 -msgid "" -"To use a radius server, you need to switch to authentication mode RADIUS and" -" then configure it." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:112 -#: 3c70d01251604aff85a7a5568bb4d593 -msgid "" -"Use this command to configure the IP address and the shared secret key of " -"your RADIUS server. You can have multiple RADIUS servers configured if you " -"wish to achieve redundancy." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:125 -#: bc1f5baea6464236ba1bfac2fb1ee793 -msgid "" -"RADIUS provides the IP addresses in the example above via Framed-IP-Address." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:128 -#: 522802d9dbcd4472a4cb45fb843af1cf -msgid "**RADIUS sessions management DM/CoA**" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:133 -#: 3b170c81c0284d7eae376486835cbb51 -msgid "" -"Use this command to configure Dynamic Authorization Extensions to RADIUS so " -"that you can remotely disconnect sessions and change some authentication " -"parameters." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:144 -#: 212be848deb747488fbee0437ed911d5 -msgid "" -"Example, from radius-server send command for disconnect client with username" -" test" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:152 -#: c3a78625fb6b4ca08e89e45f260e3cc6 -msgid "" -"You can also use another attributes for identify client for disconnect, like" -" Framed-IP-Address, Acct-Session-Id, etc. Result commands appears in log." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:160 -#: 58b2c7a3541b42bc8abe05c7c23531b3 -msgid "Example for changing rate-limit via RADIUS CoA." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:167 -#: 7746ca8b40b74517a8578392ba751302 -msgid "" -"Filter-Id=5000/4000 (means 5000Kbit down-stream rate and 4000Kbit up-stream " -"rate) If attribute Filter-Id redefined, replace it in RADIUS CoA request." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:172 -#: 8fb25cb773b94ffe8d5d7eb042112abb -msgid "Automatic VLAN Creation" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:176 -#: f8531ffe21cc494ead3a89922b4cf226 -msgid "" -"VLAN's can be created by Accel-ppp on the fly via the use of a Kernel module" -" named `vlan_mon`, which is monitoring incoming vlans and creates the " -"necessary VLAN if required and allowed. VyOS supports the use of either VLAN" -" ID's or entire ranges, both values can be defined at the same time for an " -"interface." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:182 -#: 2fd0552f629249aab1d76750c2a26ad2 -msgid "" -"When configured, PPPoE will create the necessary VLANs when required. Once " -"the user session has been cancelled and the VLAN is not needed anymore, VyOS" -" will remove it again." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:195 -#: ea28c6401e6648a2950277ab51090d15 -msgid "Bandwidth Shaping" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:197 -#: 6837b6af85094aefb8acf3ba8dfaad5e -msgid "" -"Bandwidth rate limits can be set for local users or RADIUS based attributes." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:201 -#: 4bac457147f24185897daa120a4e9857 -msgid "For Local Users" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:206 -#: 1735c3ab4e504450916a807c4cd777be -msgid "" -"Use this command to configure a data-rate limit to PPPOoE clients for " -"traffic download or upload. The rate-limit is set in kbit/sec." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:224 -#: 0a054c60aa404ddda536bd30694a15fb -msgid "" -"Once the user is connected, the user session is using the set limits and can" -" be displayed via 'show pppoe-server sessions'." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:236 -#: a7098570e5fa440bb94fe42a94bf09a1 -msgid "For RADIUS users" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:238 -#: 202f9e5a8ad14a00af54b0ac1648e6a0 -msgid "" -"The current attribute 'Filter-Id' is being used as default and can be setup " -"within RADIUS:" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:241 -#: d4723ab73e23403b8e16f9a5ea28ba3c -msgid "" -"Filter-Id=2000/3000 (means 2000Kbit down-stream rate and 3000Kbit up-stream " -"rate)" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:244 -#: e0dc050deee849bca619c7aacc819c96 -msgid "" -"The command below enables it, assuming the RADIUS connection has been setup " -"and is working." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:249 -#: 8a1e75df596f49c1a7a5c011a8668496 -msgid "Use this command to enable bandwidth shaping via RADIUS." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:251 -#: a71ecadbcb2e497f90cf7f5af7a74b80 -msgid "" -"Other attributes can be used, but they have to be in one of the dictionaries" -" in */usr/share/accel-ppp/radius*." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:256 -#: fff40866a2ca4541bf0fa129faee9bab -msgid "Load Balancing" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:262 -#: 4e6f9a5bdb1343569753489ab0d9cbd0 -msgid "" -"Use this command to enable the delay of PADO (PPPoE Active Discovery Offer) " -"packets, which can be used as a session balancing mechanism with other PPPoE" -" servers." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:272 -#: 603e61889f264b18a42b74d411084fba -msgid "" -"In the example above, the first 499 sessions connect without delay. PADO " -"packets will be delayed 50 ms for connection from 500 to 999, this trick " -"allows other PPPoE servers send PADO faster and clients will connect to " -"other servers. Last command says that this PPPoE server can serve only 3000 " -"clients." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:280 -#: 984c71bb30c7441ab6db36527350a0b9 -msgid "IPv6" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:283 -#: b76b7c61b3594f8abe76e148b610c954 -msgid "IPv6 client's prefix assignment" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:288 -#: f627f07ffdee48a3839e5462350b4773 -msgid "" -"Use this comand to set the IPv6 address pool from which a PPPoE client will " -"get an IPv6 prefix of your defined length (mask) to terminate the PPPoE " -"endpoint at their side. The mask length can be set from 48 to 128 bit long, " -"the default value is 64." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:295 -#: b3a78b30ca4543309f3ed5b18c6d2951 -msgid "IPv6 Prefix Delegation" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:300 -#: 913a8e925c09468c80f891ef734e75d9 -msgid "" -"Use this command to configure DHCPv6 Prefix Delegation (RFC3633). You will " -"have to set your IPv6 pool and the length of the delegation prefix. From the" -" defined IPv6 pool you will be handing out networks of the defined length " -"(delegation-prefix). The length of the delegation prefix can be set from 32 " -"to 64 bit long." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:308 -#: a73c4a1a586040cfbe09db70ba1f771d -msgid "Maintenance mode" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:312 -#: 8743944ebe7b4c37b6b96da01099fd70 -msgid "" -"For network maintenance, it's a good idea to direct users to a backup server" -" so that the primary server can be safely taken out of service. It's " -"possible to switch your PPPoE server to maintenance mode where it maintains " -"already established connections, but refuses new connection attempts." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:320 -#: c16449111f2b4d06bbcd1a8c36edfb7c -msgid "Checking connections" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:324 -#: 40bc5c5dcad944f68f8646a4308fb0c4 -msgid "" -"Use this command to locally check the active sessions in the PPPoE server." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:336 -#: e5a3d9a6fbb445ecad5c6301eb3e1cef -msgid "" -"Per default the user session is being replaced if a second authentication " -"request succeeds. Such session requests can be either denied or allowed " -"entirely, which would allow multiple sessions for a user in the latter case." -" If it is denied, the second session is being rejected even if the " -"authentication succeeds, the user has to terminate its first session and can" -" then authentication again." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:356 -#: e2e19e088a2842718d649001d4fa28a0 -msgid "Examples" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:359 -#: 15eb830cb11144e38b3c5a2206f1bc85 -msgid "IPv4" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:361 -#: 97b7e11702eb496dbce0a5bfbc3912cb -msgid "" -"The example below uses ACN as access-concentrator name, assigns an address " -"from the pool 10.1.1.100-111, terminates at the local endpoint 10.1.1.1 and " -"serves requests only on eth1." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:380 -#: 1d1ed906d69f4652acde698114bf79ac -msgid "Dual-Stack IPv4/IPv6 provisioning with Prefix Delegation" -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:382 -#: 33ef5d0b929d4d4c8f248315434a11ee -msgid "The example below covers a dual-stack configuration via pppoe-server." -msgstr "" - -#: ../../configuration/service/pppoe-server.rst:398 -#: 033c50652faf48468775948d77cda94e -msgid "" -"The client, once successfully authenticated, will receive an IPv4 and an " -"IPv6 /64 address to terminate the pppoe endpoint on the client side and a " -"/56 subnet for the clients internal use." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/router-advert.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/router-advert.po deleted file mode 100644 index 3ffd5187..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/router-advert.po +++ /dev/null @@ -1,374 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/router-advert.rst:5 -#: 0ef10b50d09649b1934411939bead5bc -msgid "Router Advertisements" -msgstr "" - -#: ../../configuration/service/router-advert.rst:7 -#: 6d817f4e5274468198036dc88aeac613 -msgid "" -":abbr:`RAs (Router advertisements)` are described in " -":rfc:`4861#section-4.6.2`. They are part of what is known as :abbr:`SLAAC " -"(Stateless Address Autoconfiguration)`." -msgstr "" - -#: ../../configuration/service/router-advert.rst:12 -#: abb664f2296249179965db376ed3875f -msgid "Supported interface types:" -msgstr "" - -#: ../../configuration/service/router-advert.rst:14 -#: 2802543c48d84cc58c0f5bd4e6f09d91 -msgid "bonding" -msgstr "" - -#: ../../configuration/service/router-advert.rst:15 -#: b15ce921054a42ab8c05dd73c95def90 -msgid "bridge" -msgstr "" - -#: ../../configuration/service/router-advert.rst:16 -#: 18e723d8e6ae4744b47d2f068d797120 -msgid "ethernet" -msgstr "" - -#: ../../configuration/service/router-advert.rst:17 -#: 34427b78a47440d4b2afb06dcb0ec8af -msgid "l2tpv3" -msgstr "" - -#: ../../configuration/service/router-advert.rst:18 -#: 9fed4fcf05e149d8a18b09d69d029fab -msgid "openvpn" -msgstr "" - -#: ../../configuration/service/router-advert.rst:19 -#: d649cbc695254308b76e51f9c36e142d -msgid "pseudo-ethernet" -msgstr "" - -#: ../../configuration/service/router-advert.rst:20 -#: 8677df4e0d04491e83dbff2c7dd2c15f -msgid "tunnel" -msgstr "" - -#: ../../configuration/service/router-advert.rst:21 -#: 34f3ee33128f47848db9887d5fd82e32 -msgid "vxlan" -msgstr "" - -#: ../../configuration/service/router-advert.rst:22 -#: 100ab9bf56a5450392c96579c8ba32f6 -msgid "wireguard" -msgstr "" - -#: ../../configuration/service/router-advert.rst:23 -#: f7729a45cf2d4b3384673322e6b6b99f -msgid "wireless" -msgstr "" - -#: ../../configuration/service/router-advert.rst:24 -#: 58f96528ba7246b4ae40066874f2fdfd -msgid "wirelessmodem" -msgstr "" - -#: ../../configuration/service/router-advert.rst:28 -#: 1b381e306213427c97ed933698a0ff71 -msgid "Enabling Advertisments" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: ae6ce5a72cd64b4eaae167f07afb4411 -msgid "Field" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 796a8b8306f744f48140ada3a170bf64 -msgid "VyOS Option" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: ../../configuration/service/router-advert.rst:1 -#: c4e2bcf7db9d4ba5a300cef420c701b4 d0bce4b9ba3a45b1872c55e96189819f -msgid "Description" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: fd5a460187d64bf1aac160d677c007cd -msgid "Cur Hop Limit" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 5d7bc99e32ac45f0b4db10ad1758da3d -msgid "hop-limit" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: ccb83a8b9d78437b8346a6816b5ae6a5 -msgid "Hop count field of the outgoing RA packets" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 2633269240424422a961694fa873556e -msgid "\"Managed address configuration\" flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 2a819e2e708c499aadef365ecab9c2fa -msgid "managed-flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: d9ca9730db5c411dbf6c82ab19bef1b3 -msgid "" -"Tell hosts to use the administered stateful protocol (i.e. DHCP) for " -"autoconfiguration" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 5fef1ac872504f13891b93ccfbbf987f -msgid "\"Other configuration\" flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 7626bc314b754ca49863745e63c8d414 -msgid "other-config-flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: ed54dca08d364165963afc9606a87359 -msgid "" -"Tell hosts to use the administered (stateful) protocol (i.e. DHCP) for " -"autoconfiguration of other (non-address) information" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 0d4b743283914aa08eda7d934ce410b6 -msgid "MTU" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 87a1908f3a134bd2b3d5714a103b2252 -msgid "link-mtu" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 62c2cfb54c4341bf88d70943877f1ad3 -msgid "Link MTU value placed in RAs, exluded in RAs if unset" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 3a90e648c9bd4776bd02690f025faf6d -msgid "Router Lifetime" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: d9369c5fe0744dc68f65bef4b87a6ef3 -msgid "default-lifetime" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 7f23860e61594c4c834805e8fc02f41e -msgid "Lifetime associated with the default router in units of seconds" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: dff33d83b2614d449c9597fd51157681 -msgid "Reachable Time" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: b32bcad949cb471899ac7402773fb9f1 -msgid "reachable-time" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 827818796b98440584fad1f44ced8421 -msgid "" -"Time, in milliseconds, that a node assumes a neighbor is reachable after " -"having received a reachability confirmation" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 6646f7a9009e4bd8b7dcbd41a1d8ff8f -msgid "Retransmit Timer" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 90484658449e480e966c38cd42fe70aa -msgid "retrans-timer" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 0fea090e73f241c59b5550d44efc1edf -msgid "" -"Time in milliseconds between retransmitted Neighbor Solicitation messages" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 3080e74da17c410bab107789910cc42c -msgid "Default Router Preference" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: adf24795662643eb855dd8b61976bef7 -msgid "default-preference" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 221f6121d5e941569752b56dcc5105e9 -msgid "Preference associated with the default router" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: f6e52feb9b574e448c3f8463d8664d9d -msgid "Interval" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: b970bfd7f34740cfad8c148f5db1da02 -msgid "interval" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 864137937cb44aaea74d2b1aecb59d94 -msgid "Min and max intervals between unsolicited multicast RAs" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 71b2b409722745e7a8275a841b3f835f -msgid "DNSSL" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 50e9beba53234d41a140feff81631749 -msgid "dnssl" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 27f0315f43224fe690c20f5f1dc000ba -msgid "DNS search list to advertise" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: c507b73f0db64be086a05c08f0933870 -msgid "Name Server" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: e89e74e81c844feea7f9743e5d77769a -msgid "name-server" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: d48befc4a0e54de58570c3302202dee2 -msgid "Advertise DNS server per https://tools.ietf.org/html/rfc6106" -msgstr "" - -#: ../../configuration/service/router-advert.rst:54 -#: bd9131f8f85c4e8fb68b1c1f5cedbd81 -msgid "Advertising a Prefix" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 46005a0517e74a0a8fa2571089364d43 -msgid "VyOS Field" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 6cb98638000b42658591fc43d33495ba -msgid "decrement-lifetime" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 4847cdb53a6a4dabbb7749c2f2278ff8 -msgid "" -"Lifetime is decremented by the number of seconds since the last RA - use in " -"conjunction with a DHCPv6-PD prefix" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: a9fb81bea8d4473fb7a6b49eafd13712 -msgid "deprecate-prefix" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 20503fd5fb7a4d4b9b5b71cdad4f1b7c -msgid "" -"Upon shutdown, this option will deprecate the prefix by announcing it in the" -" shutdown RA" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: db903fb0a47947a0a8d5e75e5bdfa0ff -msgid "no-autonomous-flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: c80ed9c76c93418d877d4933113c6739 -msgid "Prefix can not be used for stateless address auto-configuration" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 1f2e0121b3c74487ba15bb347716a2c3 -msgid "no-on-link-flag" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 64e1124b0f014efc9fbf038a3af0b632 -msgid "Prefix can not be used for on-link determination" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 1ce3440969634606abb1791c4d328075 -msgid "preferred-lifetime" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 83079f15719e4b30bc0ab4a640f9321d -msgid "" -"Time in seconds that the prefix will remain preferred (default 4 hours)" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 7920dcc8b5894884bd5e2be8dba4144e -msgid "valid-lifetime" -msgstr "" - -#: ../../configuration/service/router-advert.rst:1 -#: 37ca37f336e74f85b35c318397bfab50 -msgid "Time in seconds that the prefix will remain valid (default: 30 days)" -msgstr "" - -#: ../../configuration/service/router-advert.rst:74 -#: 87e3cc0a5be04315973cdb981df8f658 -msgid "Disabling Advertisements" -msgstr "" - -#: ../../configuration/service/router-advert.rst:76 -#: fbc1406cdc674ffbabd1704465c33591 -msgid "To disable advertisements without deleting the configuration:" -msgstr "" - -#: ../../configuration/service/router-advert.rst:81 -#: cfe0367334a74a5da873b8b17f8793dc -msgid "Example Configuration" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/salt-minion.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/salt-minion.po deleted file mode 100644 index d0b8e8ec..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/salt-minion.po +++ /dev/null @@ -1,83 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/salt-minion.rst:5 -#: eedd2382b28f445499c48f7418f67c7a -msgid "Salt-Minion" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:7 -#: 97995c49ac2a461396473c93061a5715 -msgid "" -"SaltStack_ is Python-based, open-source software for event-driven IT " -"automation, remote task execution, and configuration management. Supporting " -"the \"infrastructure as code\" approach to data center system and network " -"deployment and management, configuration automation, SecOps orchestration, " -"vulnerability remediation, and hybrid cloud control." -msgstr "" - -#: ../../configuration/service/salt-minion.rst:17 -#: d183564286024ed28739c1c9f54132b3 -msgid "Requirements" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:19 -#: c922c5890c134199b5e17973c489a3d7 -msgid "" -"To use the Salt-Minion, a running Salt-Master is required. You can find more" -" in the `Salt Poject Documentaion " -"<https://docs.saltproject.io/en/latest/contents.html>`_" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:25 -#: e681f6ccad92466c9965b111af45f50d -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:29 -#: 4f9d7de795a54dd49bc4600f055df36a -msgid "" -"The hash type used when discovering file on master server (default: sha256)" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:33 -#: ff61173c04c846999a3120f30849dba6 -msgid "Explicitly declare ID for this minion to use (default: hostname)" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:37 -#: 841d7b7883bf45299419f7e6fea28d2d -msgid "Interval in minutes between updates (default: 60)" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:41 -#: 68ff5dcab36d4d49813f37e2970f5220 -msgid "The hostname or IP address of the master" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:45 -#: 96099dbb99e84e1f90e46db4fd6b7ee6 -msgid "URL with signature of master for auth reply verification" -msgstr "" - -#: ../../configuration/service/salt-minion.rst:48 -#: e249605e6ee44cf6be099cb13b7c9698 -msgid "" -"Please take a look in the Automation section to find some usefull Examples." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/snmp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/snmp.po deleted file mode 100644 index 359f6084..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/snmp.po +++ /dev/null @@ -1,281 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/snmp.rst:5 673b54ae8a7644f99cbdf9a75c39d61f -msgid "SNMP" -msgstr "" - -#: ../../configuration/service/snmp.rst:7 e32ce30fcbbf445cae73cf66d09160bc -msgid "" -":abbr:`SNMP (Simple Network Management Protocol)` is an Internet Standard " -"protocol for collecting and organizing information about managed devices on " -"IP networks and for modifying that information to change device behavior. " -"Devices that typically support SNMP include cable modems, routers, switches," -" servers, workstations, printers, and more." -msgstr "" - -#: ../../configuration/service/snmp.rst:13 1b4c23bde7684649be0e499f766c8263 -msgid "" -"SNMP is widely used in network management for network monitoring. SNMP " -"exposes management data in the form of variables on the managed systems " -"organized in a management information base (MIB_) which describe the system " -"status and configuration. These variables can then be remotely queried (and," -" in some circumstances, manipulated) by managing applications." -msgstr "" - -#: ../../configuration/service/snmp.rst:19 85b90a44324e4a76b93874eb83500c89 -msgid "" -"Three significant versions of SNMP have been developed and deployed. SNMPv1 " -"is the original version of the protocol. More recent versions, SNMPv2c and " -"SNMPv3, feature improvements in performance, flexibility and security." -msgstr "" - -#: ../../configuration/service/snmp.rst:23 7636576a08484fa890f6b2168dab90e7 -msgid "" -"SNMP is a component of the Internet Protocol Suite as defined by the " -"Internet Engineering Task Force (IETF). It consists of a set of standards " -"for network management, including an application layer protocol, a database " -"schema, and a set of data objects." -msgstr "" - -#: ../../configuration/service/snmp.rst:29 672f5c1096754a669e9ffcba1308abe4 -msgid "Overview and basic concepts" -msgstr "" - -#: ../../configuration/service/snmp.rst:31 508ce66678cc4bfda08705280fb22c9f -msgid "" -"In typical uses of SNMP, one or more administrative computers called " -"managers have the task of monitoring or managing a group of hosts or devices" -" on a computer network. Each managed system executes a software component " -"called an agent which reports information via SNMP to the manager." -msgstr "" - -#: ../../configuration/service/snmp.rst:36 fc75eec6b530433583ad04a00081ded1 -msgid "An SNMP-managed network consists of three key components:" -msgstr "" - -#: ../../configuration/service/snmp.rst:38 952f85c2f06041609f4fe159edabbfdc -msgid "Managed devices" -msgstr "" - -#: ../../configuration/service/snmp.rst:39 8f82592033cf40429089b6d258ee268b -msgid "Agent - software which runs on managed devices" -msgstr "" - -#: ../../configuration/service/snmp.rst:40 4a7ef3c5b5654fbb8c7149dafdabb1c5 -msgid "Network management station (NMS) - software which runs on the manager" -msgstr "" - -#: ../../configuration/service/snmp.rst:42 e962b6aff998468db3e9e8bf67592032 -msgid "" -"A managed device is a network node that implements an SNMP interface that " -"allows unidirectional (read-only) or bidirectional (read and write) access " -"to node-specific information. Managed devices exchange node-specific " -"information with the NMSs. Sometimes called network elements, the managed " -"devices can be any type of device, including, but not limited to, routers, " -"access servers, switches, cable modems, bridges, hubs, IP telephones, IP " -"video cameras, computer hosts, and printers." -msgstr "" - -#: ../../configuration/service/snmp.rst:50 5b38f53565cf4caf90acace13d163b70 -msgid "" -"An agent is a network-management software module that resides on a managed " -"device. An agent has local knowledge of management information and " -"translates that information to or from an SNMP-specific form." -msgstr "" - -#: ../../configuration/service/snmp.rst:54 f6aa9aff15b44d0ca707245a1c6387a1 -msgid "" -"A network management station executes applications that monitor and control " -"managed devices. NMSs provide the bulk of the processing and memory " -"resources required for network management. One or more NMSs may exist on any" -" managed network." -msgstr "" - -#: ../../configuration/service/snmp.rst:63 f5d46f82a1294fde9a99cc30a7018719 -msgid "Principle of SNMP Communication" -msgstr "" - -#: ../../configuration/service/snmp.rst:63 b42009da969f461d964ac71d49364114 -msgid "" -"Image thankfully borrowed from " -"https://en.wikipedia.org/wiki/File:SNMP_communication_principles_diagram.PNG" -" which is under the GNU Free Documentation License" -msgstr "" - -#: ../../configuration/service/snmp.rst:67 5cd54137885742b08aa89e12894391e4 -msgid "VyOS SNMP supports both IPv4 and IPv6." -msgstr "" - -#: ../../configuration/service/snmp.rst:70 c35469efc46440a0931e138a4709a560 -msgid "SNMP Protocol Versions" -msgstr "" - -#: ../../configuration/service/snmp.rst:72 a18328781b6749c2a5340ed69c4de073 -msgid "" -"VyOS itself supports SNMPv2_ (version 2) and SNMPv3_ (version 3) where the " -"later is recommended because of improved security (optional authentication " -"and encryption)." -msgstr "" - -#: ../../configuration/service/snmp.rst:77 f859015da9814c6595022563749b438f -msgid "SNMPv2" -msgstr "" - -#: ../../configuration/service/snmp.rst:79 e39778b1ba06412dbe73ef5779cf2a9e -msgid "" -"SNMPv2 is the original and most commonly used version. For authorizing " -"clients, SNMP uses the concept of communities. Communities may have " -"authorization set to read only (this is most common) or to read and write " -"(this option is not actively used in VyOS)." -msgstr "" - -#: ../../configuration/service/snmp.rst:84 607f7800ab7649229ee1215ab4647d68 -msgid "" -"SNMP can work synchronously or asynchronously. In synchronous communication," -" the monitoring system queries the router periodically. In asynchronous, the" -" router sends notification to the \"trap\" (the monitoring host)." -msgstr "" - -#: ../../configuration/service/snmp.rst:88 e1d7831bee1d4becab797729175d9549 -msgid "" -"SNMPv2 does not support any authentication mechanisms, other than client " -"source address, so you should specify addresses of clients allowed to " -"monitor the router. Note that SNMPv2 also supports no encryption and always " -"sends data in plain text." -msgstr "" - -#: ../../configuration/service/snmp.rst:94 -#: ../../configuration/service/snmp.rst:145 507ef696ec524a189d8e1f4c888c97cb -#: 7285140432824b5eac1701fd996a6276 -msgid "Example" -msgstr "" - -#: ../../configuration/service/snmp.rst:122 9ff9a44b54134b05a3ce6fac4afeb02c -msgid "SNMPv3" -msgstr "" - -#: ../../configuration/service/snmp.rst:124 44ab9c93f4c44b6c88a2d7e7351761d4 -msgid "" -"SNMPv3 (version 3 of the SNMP protocol) introduced a whole slew of new " -"security related features that have been missing from the previous versions." -" Security was one of the biggest weakness of SNMP until v3. Authentication " -"in SNMP Versions 1 and 2 amounts to nothing more than a password (community " -"string) sent in clear text between a manager and agent. Each SNMPv3 message " -"contains security parameters which are encoded as an octet string. The " -"meaning of these security parameters depends on the security model being " -"used." -msgstr "" - -#: ../../configuration/service/snmp.rst:132 fd9a6074a397488ca7e4d5a963896fae -msgid "The security approach in SNMPv3 targets:" -msgstr "" - -#: ../../configuration/service/snmp.rst:134 071d203c90114ab4bd8208f5c55eb729 -msgid "" -"Confidentiality – Encryption of packets to prevent snooping by an " -"unauthorized source." -msgstr "" - -#: ../../configuration/service/snmp.rst:137 816c745d250e4560b04fd058fd563f3a -msgid "" -"Integrity – Message integrity to ensure that a packet has not been tampered " -"while in transit including an optional packet replay protection mechanism." -msgstr "" - -#: ../../configuration/service/snmp.rst:140 ad27f29b46f34ed4bb7709f054682071 -msgid "Authentication – to verify that the message is from a valid source." -msgstr "" - -#: ../../configuration/service/snmp.rst:147 f11d6eb73e1e4d7bb77203b7757bf6cc -msgid "Let SNMP daemon listen only on IP address 192.0.2.1" -msgstr "" - -#: ../../configuration/service/snmp.rst:148 938627e7264c42459261c00c73e9b148 -msgid "Configure new SNMP user named \"vyos\" with password \"vyos12345678\"" -msgstr "" - -#: ../../configuration/service/snmp.rst:149 2b6bc6679e3849ff811779224466483e -msgid "New user will use SHA/AES for authentication and privacy" -msgstr "" - -#: ../../configuration/service/snmp.rst:165 f1625b2d48ba4916894f0753ae9d975a -msgid "" -"After commit the plaintext passwords will be hashed and stored in your " -"configuration. The resulting CLI config will look like:" -msgstr "" - -#: ../../configuration/service/snmp.rst:197 b97b7c55ee66439eafea0db02600ee63 -msgid "" -"You can test the SNMPv3 functionality from any linux based system, just run " -"the following command: ``snmpwalk -v 3 -u vyos -a SHA -A vyos12345678 -x AES" -" -X vyos12345678 -l authPriv 192.0.2.1 .1``" -msgstr "" - -#: ../../configuration/service/snmp.rst:202 0dc0e70e9678473da4b30df269bb98ea -msgid "VyOS MIBs" -msgstr "" - -#: ../../configuration/service/snmp.rst:204 0e1a8de3fac144eeb2391e46928095e5 -msgid "" -"All SNMP MIBs are located in each image of VyOS here: " -"``/usr/share/snmp/mibs/``" -msgstr "" - -#: ../../configuration/service/snmp.rst:206 d34fa75e55704b6db6576cadb7e92edd -msgid "" -"You are be able to download the files using SCP, once the SSH service has " -"been activated like so" -msgstr "" - -#: ../../configuration/service/snmp.rst:214 b98ddd1ead1c4cc8ad955b3d5e614591 -msgid "SNMP Extensions" -msgstr "" - -#: ../../configuration/service/snmp.rst:216 dba386315d364f90b4c8392736d35c84 -msgid "" -"To extend SNMP agent functionality, custom scripts can be executed every " -"time the agent is being called. This can be achieved by using ``arbitrary " -"extensioncommands``. The first step is to create a functional script of " -"course, then upload it to your VyOS instance via the command ``scp " -"your_script.sh vyos@your_router:/config/user-data``. Once the script is " -"uploaded, it needs to be configured via the command below." -msgstr "" - -#: ../../configuration/service/snmp.rst:231 1da0746f60014560b4d550769f356afe -msgid "" -"The OID ``.1.3.6.1.4.1.8072.1.3.2.3.1.1.4.116.101.115.116``, once called, " -"will contain the output of the extension." -msgstr "" - -#: ../../configuration/service/snmp.rst:245 2309ee4f72f04ec99c1c7bdad02b9669 -msgid "SolarWinds" -msgstr "" - -#: ../../configuration/service/snmp.rst:247 bde288684d2e45e3bbd1f5688d6ad7d4 -msgid "" -"If you happen to use SolarWinds Orion as NMS you can also use the Device " -"Templates Management. A template for VyOS can be easily imported." -msgstr "" - -#: ../../configuration/service/snmp.rst:252 bcb2fed7220142fdb524aad933d9f745 -msgid "" -"Create a file named ``VyOS-1.3.6.1.4.1.44641.ConfigMgmt-Commands`` using the" -" following content:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ssh.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ssh.po deleted file mode 100644 index 56472868..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/ssh.po +++ /dev/null @@ -1,254 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/ssh.rst:5 fab12a30042344f2aed0bb2927bf95b8 -msgid "SSH" -msgstr "" - -#: ../../configuration/service/ssh.rst:7 7abb8613c7734008a0472737b5269796 -msgid "" -":abbr:`SSH (Secure Shell)` is a cryptographic network protocol for operating" -" network services securely over an unsecured network. The standard TCP port " -"for SSH is 22. The best known example application is for remote login to " -"computer systems by users." -msgstr "" - -#: ../../configuration/service/ssh.rst:12 dad607f902c5476cbb25927f4e9bac1f -msgid "" -"SSH provides a secure channel over an unsecured network in a client-server " -"architecture, connecting an SSH client application with an SSH server. " -"Common applications include remote command-line login and remote command " -"execution, but any network service can be secured with SSH. The protocol " -"specification distinguishes between two major versions, referred to as SSH-1" -" and SSH-2." -msgstr "" - -#: ../../configuration/service/ssh.rst:18 71d4da888ed24a408bda4e8dbc7a614e -msgid "" -"The most visible application of the protocol is for access to shell accounts" -" on Unix-like operating systems, but it sees some limited use on Windows as " -"well. In 2015, Microsoft announced that they would include native support " -"for SSH in a future release." -msgstr "" - -#: ../../configuration/service/ssh.rst:23 9b765f6c14004a4bacda60ecd6078e50 -msgid "" -"SSH was designed as a replacement for Telnet and for unsecured remote shell " -"protocols such as the Berkeley rlogin, rsh, and rexec protocols. Those " -"protocols send information, notably passwords, in plaintext, rendering them " -"susceptible to interception and disclosure using packet analysis. The " -"encryption used by SSH is intended to provide confidentiality and integrity " -"of data over an unsecured network, such as the Internet." -msgstr "" - -#: ../../configuration/service/ssh.rst:30 7c6c65b7a9d1457989890f99d0212084 -msgid "" -"VyOS 1.1 supported login as user ``root``. This has been removed due to " -"tighter security in VyOS 1.2." -msgstr "" - -#: ../../configuration/service/ssh.rst:33 d8dccf2a289d40a0a6e57ff1145f9538 -msgid "SSH :ref:`ssh_key_based_authentication`" -msgstr "" - -#: ../../configuration/service/ssh.rst:36 6e39da5ae0ca4c118b9986abea83e66f -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/ssh.rst:40 c2be9219cb1f4382817419a9d02c83d6 -msgid "" -"Enabling SSH only requires you to specify the port ``<port>`` you want SSH " -"to listen on. By default, SSH runs on port 22." -msgstr "" - -#: ../../configuration/service/ssh.rst:45 8e12c00d53a24c488196b13f6731bc85 -msgid "" -"Specify IPv4/IPv6 listen address of SSH server. Multiple addresses can be " -"defined." -msgstr "" - -#: ../../configuration/service/ssh.rst:50 6b9d60576b1b4be89f1063de0909be37 -msgid "" -"Define allowed ciphers used for the SSH connection. A number of allowed " -"ciphers can be specified, use multiple occurrences to allow multiple " -"ciphers." -msgstr "" - -#: ../../configuration/service/ssh.rst:53 2053f5d20be24339a08b6eb06b9e4f95 -msgid "" -"List of supported ciphers: ``3des-cbc``, ``aes128-cbc``, ``aes192-cbc``, " -"``aes256-cbc``, ``aes128-ctr``, ``aes192-ctr``, ``aes256-ctr``, " -"``arcfour128``, ``arcfour256``, ``arcfour``, ``blowfish-cbc``, " -"``cast128-cbc``" -msgstr "" - -#: ../../configuration/service/ssh.rst:59 7e34e9182d234e93b436bc394fcc3ac8 -msgid "" -"Disable password based authentication. Login via SSH keys only. This hardens" -" security!" -msgstr "" - -#: ../../configuration/service/ssh.rst:64 856316e7319a4f2ab0eeb18437f4d563 -msgid "" -"Disable the host validation through reverse DNS lookups - can speedup login " -"time when reverse lookup is not possible." -msgstr "" - -#: ../../configuration/service/ssh.rst:69 67c8bcab57654ee892ab366c20adc3ce -msgid "" -"Specifies the available :abbr:`MAC (Message Authentication Code)` " -"algorithms. The MAC algorithm is used in protocol version 2 for data " -"integrity protection. Multiple algorithms can be provided." -msgstr "" - -#: ../../configuration/service/ssh.rst:73 633357d5f10849e39bb22f8720260716 -msgid "" -"List of supported MACs: ``hmac-md5``, ``hmac-md5-96``, ``hmac-ripemd160``, " -"``hmac-sha1``, ``hmac-sha1-96``, ``hmac-sha2-256``, ``hmac-sha2-512``, " -"``umac-64@openssh.com``, ``umac-128@openssh.com``, ``hmac-" -"md5-etm@openssh.com``, ``hmac-md5-96-etm@openssh.com``, ``hmac-" -"ripemd160-etm@openssh.com``, ``hmac-sha1-etm@openssh.com``, ``hmac-" -"sha1-96-etm@openssh.com``, ``hmac-sha2-256-etm@openssh.com``, ``hmac-" -"sha2-512-etm@openssh.com``, ``umac-64-etm@openssh.com``, " -"``umac-128-etm@openssh.com``" -msgstr "" - -#: ../../configuration/service/ssh.rst:84 68b1e555abb74c3bb8ed1f76980f6ad9 -msgid "" -"Add access-control directive to allow or deny users and groups. Directives " -"are processed in the following order of precedence: ``deny-users``, ``allow-" -"users``, ``deny-groups`` and ``allow-groups``." -msgstr "" - -#: ../../configuration/service/ssh.rst:90 2c17c4c762bc46ada922db6284971c97 -msgid "Specify timeout interval for keepalive message in seconds." -msgstr "" - -#: ../../configuration/service/ssh.rst:94 fa69712b894541f58ab5402262758a2d -msgid "Specify allowed :abbr:`KEX (Key Exchange)` algorithms." -msgstr "" - -#: ../../configuration/service/ssh.rst:96 b9af96b551ca408498c03952ad80ac55 -msgid "" -"List of supported algorithms: ``diffie-hellman-group1-sha1``, ``diffie-" -"hellman-group14-sha1``, ``diffie-hellman-group14-sha256``, ``diffie-hellman-" -"group16-sha512``, ``diffie-hellman-group18-sha512``, ``diffie-hellman-group-" -"exchange-sha1``, ``diffie-hellman-group-exchange-sha256``, ``ecdh-" -"sha2-nistp256``, ``ecdh-sha2-nistp384``, ``ecdh-sha2-nistp521``, " -"``curve25519-sha256`` and ``curve25519-sha256@libssh.org``." -msgstr "" - -#: ../../configuration/service/ssh.rst:106 a8e69ca756fa410a8265fbd9994c3d82 -msgid "Set the ``sshd`` log level. The default is ``info``." -msgstr "" - -#: ../../configuration/service/ssh.rst:110 f96e71685cab4768918f251afb5e4b44 -msgid "" -"Specify name of the :abbr:`VRF (Virtual Routing and Forwarding)` instance." -msgstr "" - -#: ../../configuration/service/ssh.rst:113 33921a83af8d4c92babfe7a4c8c3e673 -msgid "Dynamic-protection" -msgstr "" - -#: ../../configuration/service/ssh.rst:114 b2ac0add88994fa3a87a3eee898ebe23 -msgid "" -"Protects host from brute-force attacks against SSH. Log messages are parsed," -" line-by-line, for recognized patterns. If an attack, such as several login " -"failures within a few seconds, is detected, the offending IP is blocked. " -"Offenders are unblocked after a set interval." -msgstr "" - -#: ../../configuration/service/ssh.rst:121 b441c882e2f24de3b38bdd9f8e93019d -msgid "Allow ``ssh`` dynamic-protection." -msgstr "" - -#: ../../configuration/service/ssh.rst:125 7a53d3dd4876492499391f781d8228aa -msgid "" -"Whitelist of addresses and networks. Always allow inbound connections from " -"these systems." -msgstr "" - -#: ../../configuration/service/ssh.rst:130 71404cfc03b94a74aa62ed0b8f5ac1bb -msgid "" -"Block source IP in seconds. Subsequent blocks increase by a factor of 1.5 " -"The default is 120." -msgstr "" - -#: ../../configuration/service/ssh.rst:135 a6384bbfdd9f4834b6159c84872a43cf -msgid "" -"Remember source IP in seconds before reset their score. The default is 1800." -msgstr "" - -#: ../../configuration/service/ssh.rst:139 f5229921a8394633bf74412e5b214bee -msgid "" -"Block source IP when their cumulative attack score exceeds threshold. The " -"default is 30." -msgstr "" - -#: ../../configuration/service/ssh.rst:143 b13a85e598bb414fa3aa5690ac7edfba -msgid "Operation" -msgstr "" - -#: ../../configuration/service/ssh.rst:147 d80496915497406cb818cbfbfab02d25 -msgid "" -"Restart the SSH daemon process, the current session is not affected, only " -"the background daemon is restarted." -msgstr "" - -#: ../../configuration/service/ssh.rst:152 3451e104bd784342aced2b91730f0111 -msgid "" -"Re-generated the public/private keyportion which SSH uses to secure " -"connections." -msgstr "" - -#: ../../configuration/service/ssh.rst:155 79e13472464647a4aab223fd8a1d744f -msgid "" -"Already learned known_hosts files of clients need an update as the public " -"key will change." -msgstr "" - -#: ../../configuration/service/ssh.rst:160 377ebda07bd543e4a6e174ccecf632f8 -msgid "" -"Re-generated a known pub/private keyfile which can be used to connect to " -"other services (e.g. RPKI cache)." -msgstr "" - -#: ../../configuration/service/ssh.rst:163 -#: ../../configuration/service/ssh.rst:198 640a2f6196594e148280f19bd14d48ee -#: eaf008d38eff422188f33feba5792f12 -msgid "Example:" -msgstr "" - -#: ../../configuration/service/ssh.rst:186 1509b88ec9454619bc622b8b27487aff -msgid "" -"Two new files ``/config/auth/id_rsa_rpki`` and " -"``/config/auth/id_rsa_rpki.pub`` will be created." -msgstr "" - -#: ../../configuration/service/ssh.rst:192 fc470d24be7e4e1eb5fbd4bf84ece1b1 -msgid "" -"Generate the configuration mode commands to add a public key for " -":ref:`ssh_key_based_authentication`. ``<location>`` can be a local path or a" -" URL pointing at a remote file." -msgstr "" - -#: ../../configuration/service/ssh.rst:196 b9efad6b1e24470e9c252126e43fa3ec -msgid "Supported remote protocols are FTP, HTTP, HTTPS, SCP/SFTP and TFTP." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/tftp-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/tftp-server.po deleted file mode 100644 index 62444eac..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/tftp-server.po +++ /dev/null @@ -1,113 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/tftp-server.rst:5 -#: c4296b54522549b3bab0063f866da9bf -msgid "TFTP Server" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:7 -#: 0ed7be753884413cb08d72de9c9a1d71 -msgid "" -":abbr:`TFTP (Trivial File Transfer Protocol)` is a simple, lockstep file " -"transfer protocol which allows a client to get a file from or put a file " -"onto a remote host. One of its primary uses is in the early stages of nodes " -"booting from a local area network. TFTP has been used for this application " -"because it is very simple to implement." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:14 -#: c6e88c3efac54d68b9ee9d3b60679643 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:18 -#: 4b6aadab8c6b43da9e3846e112ef1a03 -msgid "" -"Enable TFTP service by specifying the `<directory>` which will be used to " -"serve files." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:21 -#: 7b91672354f44687b0c8779f1f922a38 -msgid "" -"Choose your ``directory`` location carefully or you will loose the content " -"on image upgrades. Any directory under ``/config`` is save at this will be " -"migrated." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:27 -#: ac29a2687de8440abcb0c2195511d899 -msgid "" -"Configure the IPv4 or IPv6 listen address of the TFTP server. Multiple IPv4 " -"and IPv6 addresses can be given. There will be one TFTP server instances " -"listening on each IP address." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:35 -#: 7defff1c22914ad8a87c1d7416ca40ff -msgid "" -"Additional option to run TFTP server in the :abbr:`VRF (Virtual Routing and " -"Forwarding)` context" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:39 -#: c8297270cf6e482e8de81b9143fee97e -msgid "Configuring a listen-address is essential for the service to work." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:43 -#: 3e2823a645514066a2242046d6b8007e -msgid "" -"Optional, if you want to enable uploads, else TFTP server will act as a " -"read-only server." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:47 -#: 9b57f95ff7344edfa52d806293694077 -msgid "Example" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:49 -#: d49d63b3ea1b4ab09f422d0da872cc49 -msgid "" -"Provide TFTP server listening on both IPv4 and IPv6 addresses ``192.0.2.1`` " -"and ``2001:db8::1`` serving the content from ``/config/tftpboot``. Uploading" -" via TFTP to this server is disabled." -msgstr "" - -#: ../../configuration/service/tftp-server.rst:53 -#: b55c58f646c548188beeea943337eef0 -msgid "The resulting configuration will look like:" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:65 -#: e4d9f2b09594484cbda496ddef330a7c -msgid "Verification" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:67 -#: bd7af248b54a43aba84184c1cbb7d8af -msgid "Client:" -msgstr "" - -#: ../../configuration/service/tftp-server.rst:74 -#: 43bbca045d1f4b54903c79eca0bfbbb1 -msgid "Server:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/webproxy.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/service/webproxy.po deleted file mode 100644 index a48e90b1..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/service/webproxy.po +++ /dev/null @@ -1,483 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/service/webproxy.rst:5 69fdee8863264000a88313d8fd75f6fd -msgid "Webproxy" -msgstr "" - -#: ../../configuration/service/webproxy.rst:7 2ecb7d48688b46c2badfa67dc3c2935e -msgid "The proxy service in VyOS is based on Squid_ and some related modules." -msgstr "" - -#: ../../configuration/service/webproxy.rst:9 5e7bea2133b946cead309dcad705d812 -msgid "" -"Squid_ is a caching and forwarding HTTP web proxy. It has a wide variety of " -"uses, including speeding up a web server by caching repeated requests, " -"caching web, DNS and other computer network lookups for a group of people " -"sharing network resources, and aiding security by filtering traffic. " -"Although primarily used for HTTP and FTP, Squid includes limited support for" -" several other protocols including Internet Gopher, SSL,[6] TLS and HTTPS. " -"Squid does not support the SOCKS protocol." -msgstr "" - -#: ../../configuration/service/webproxy.rst:17 -#: 0404a62051e44d20ad54a16b7d591abe -msgid "URL Filtering is provided by SquidGuard_." -msgstr "" - -#: ../../configuration/service/webproxy.rst:21 -#: 11a43c155a6e45eabdbc64f6cf3b7c03 -msgid "Configuration" -msgstr "" - -#: ../../configuration/service/webproxy.rst:25 -#: 538de92f8cda4d54a24aa845e29bebb3 -msgid "" -"Use this command to specify a domain name to be appended to domain-names " -"within URLs that do not include a dot ``.`` the domain is appended." -msgstr "" - -#: ../../configuration/service/webproxy.rst:28 -#: 008cef5b96844d2989efab58e110af45 -msgid "" -"Example: to be appended is set to ``vyos.net`` and the URL received is " -"``www/foo.html``, the system will use the generated, final URL of " -"``www.vyos.net/foo.html``." -msgstr "" - -#: ../../configuration/service/webproxy.rst:38 -#: 933ef6eabfc54ca5a22e65fb65a21307 -msgid "" -"The size of the on-disk Proxy cache is user configurable. The Proxies " -"default cache-size is configured to 100 MB." -msgstr "" - -#: ../../configuration/service/webproxy.rst:41 -#: a4ce00087686479eb25f6eabc20c819c -msgid "Unit of this command is MB." -msgstr "" - -#: ../../configuration/service/webproxy.rst:49 -#: 23e11cde1f8c4ffe9978c5aecb2f8351 -msgid "" -"Specify the port used on which the proxy service is listening for requests. " -"This port is the default port used for the specified listen-address." -msgstr "" - -#: ../../configuration/service/webproxy.rst:52 -#: 64ec67f5a9c74ad49e03e74c5b4185b7 -msgid "Default port is 3128." -msgstr "" - -#: ../../configuration/service/webproxy.rst:60 -#: 6692ea15c0a0446eb81a04b32c59d047 -msgid "" -"Used to block specific domains by the Proxy. Specifying \"vyos.net\" will " -"block all access to vyos.net, and specifying \".xxx\" will block all access " -"to URLs having an URL ending on .xxx." -msgstr "" - -#: ../../configuration/service/webproxy.rst:70 -#: ef436427acd84b569dbb2470843fbbaf -msgid "" -"Allow access to sites in a domain without retrieving them from the Proxy " -"cache. Specifying \"vyos.net\" will allow access to vyos.net but the pages " -"accessed will not be cached. It useful for working around problems with " -"\"If-Modified-Since\" checking at certain sites." -msgstr "" - -#: ../../configuration/service/webproxy.rst:81 -#: 3d40791b0175498e8a92329abaa7cc15 -msgid "" -"Specifies proxy service listening address. The listen address is the IP " -"address on which the web proxy service listens for client requests." -msgstr "" - -#: ../../configuration/service/webproxy.rst:84 -#: 9fa25683713d4ab8a71fb1bdfe1cd4fa -msgid "" -"For security, the listen address should only be used on internal/trusted " -"networks!" -msgstr "" - -#: ../../configuration/service/webproxy.rst:93 -#: 50a2aaab0b7a435e8dcad332db909d9e -msgid "Disables web proxy transparent mode at a listening address." -msgstr "" - -#: ../../configuration/service/webproxy.rst:95 -#: 767fafde12b4451abd51078e02e034c8 -msgid "" -"In transparent proxy mode, all traffic arriving on port 80 and destined for " -"the Internet is automatically forwarded through the proxy. This allows " -"immediate proxy forwarding without configuring client browsers." -msgstr "" - -#: ../../configuration/service/webproxy.rst:99 -#: cb85f1db56664838bc5a84cda2fab9f2 -msgid "" -"Non-transparent proxying requires that the client browsers be configured " -"with the proxy settings before requests are redirected. The advantage of " -"this is that the client web browser can detect that a proxy is in use and " -"can behave accordingly. In addition, web-transmitted malware can sometimes " -"be blocked by a non-transparent web proxy, since they are not aware of the " -"proxy settings." -msgstr "" - -#: ../../configuration/service/webproxy.rst:111 -#: 5a9ceddce0eb4c03aeb54c02ac529e88 -msgid "" -"Sets the listening port for a listening address. This overrides the default " -"port of 3128 on the specific listen address." -msgstr "" - -#: ../../configuration/service/webproxy.rst:121 -#: 930057be20964eae8a4a1e6a5dd79fe1 -msgid "Used to block a specific mime-type." -msgstr "" - -#: ../../configuration/service/webproxy.rst:131 -#: 73d7aea74901472b85163b228f616b08 -msgid "" -"Specifies the maximum size of a reply body in KB, used to limit the reply " -"size." -msgstr "" - -#: ../../configuration/service/webproxy.rst:134 -#: cfe873ebb6c5462597fd7ed9c2a1f79a -msgid "All reply sizes are accepted by default." -msgstr "" - -#: ../../configuration/service/webproxy.rst:142 -#: 128f4223a5cb455082966f09bc31b8de -msgid "" -"Add new port to Safe-ports acl. Ports included by default in Safe-ports acl:" -" 21, 70, 80, 210, 280, 443, 488, 591, 777, 873, 1025-65535" -msgstr "" - -#: ../../configuration/service/webproxy.rst:147 -#: d809f26229244b62b9b68e0a57398927 -msgid "" -"Add new port to SSL-ports acl. Ports included by default in SSL-ports acl: " -"443" -msgstr "" - -#: ../../configuration/service/webproxy.rst:152 -#: 999a7db2ee664ffbbd091de8bc0b7e63 -msgid "Authentication" -msgstr "" - -#: ../../configuration/service/webproxy.rst:154 -#: 40626486edef4f739addeef49e9ffada -msgid "" -"The embedded Squid proxy can use LDAP to authenticate users against a " -"company wide directory. The following configuration is an example of how to " -"use Active Directory as authentication backend. Queries are done via LDAP." -msgstr "" - -#: ../../configuration/service/webproxy.rst:160 -#: ca29bc16039843558774ccc783a7be8e -msgid "" -"Maximum number of authenticator processes to spawn. If you start too few " -"Squid will have to wait for them to process a backlog of credential " -"verifications, slowing it down. When password verifications are done via a " -"(slow) network you are likely to need lots of authenticator processes." -msgstr "" - -#: ../../configuration/service/webproxy.rst:165 -#: 7aefcb04a09748648dcfdca982d82c5e -msgid "This defaults to 5." -msgstr "" - -#: ../../configuration/service/webproxy.rst:173 -#: ae1c75474794419490345a7513e3261f -msgid "" -"Specifies how long squid assumes an externally validated username:password " -"pair is valid for - in other words how often the helper program is called " -"for that user. Set this low to force revalidation with short lived " -"passwords." -msgstr "" - -#: ../../configuration/service/webproxy.rst:177 -#: 6c6f6390dd08483a8d31a1e52d58a439 -msgid "Time is in minutes and defaults to 60." -msgstr "" - -#: ../../configuration/service/webproxy.rst:186 -#: a4c00af4f7a8454fba076b7dd24ac873 -msgid "Proxy authentication method, currently only LDAP is supported." -msgstr "" - -#: ../../configuration/service/webproxy.rst:194 -#: 8c02a1ce915d419f82050d136971bcdf -msgid "" -"Specifies the protection scope (aka realm name) which is to be reported to " -"the client for the authentication scheme. It is commonly part of the text " -"the user will see when prompted for their username and password." -msgstr "" - -#: ../../configuration/service/webproxy.rst:203 -#: 018419ead11e48ffa29a3f80d280c32e -msgid "LDAP" -msgstr "" - -#: ../../configuration/service/webproxy.rst:207 -#: 376a4eb7086f43ac84b4e3d863e38cf0 -msgid "Specifies the base DN under which the users are located." -msgstr "" - -#: ../../configuration/service/webproxy.rst:216 -#: da28a43e344f4870ac3635846e74c143 -msgid "The DN and password to bind as while performing searches." -msgstr "" - -#: ../../configuration/service/webproxy.rst:224 -#: 751d42ed19ea4b94a9e8b6860ec0cdd8 -msgid "" -"LDAP search filter to locate the user DN. Required if the users are in a " -"hierarchy below the base DN, or if the login name is not what builds the " -"user specific part of the users DN." -msgstr "" - -#: ../../configuration/service/webproxy.rst:228 -#: d6e52dae4f0d4c439d63b2b0f336f527 -msgid "" -"The search filter can contain up to 15 occurrences of %s which will be " -"replaced by the username, as in \"uid=%s\" for :rfc:`2037` directories. For " -"a detailed description of LDAP search filter syntax see :rfc:`2254`." -msgstr "" - -#: ../../configuration/service/webproxy.rst:238 -#: 9017f65599804794b7319c69c903d941 -msgid "" -"The DN and password to bind as while performing searches. As the password " -"needs to be printed in plain text in your Squid configuration it is strongly" -" recommended to use a account with minimal associated privileges. This to " -"limit the damage in case someone could get hold of a copy of your Squid " -"configuration file." -msgstr "" - -#: ../../configuration/service/webproxy.rst:250 -#: eb937ab1e8244f069c6ddc32fbc6339a -msgid "" -"Use a persistent LDAP connection. Normally the LDAP connection is only open " -"while validating a username to preserve resources at the LDAP server. This " -"option causes the LDAP connection to be kept open, allowing it to be reused " -"for further user validations." -msgstr "" - -#: ../../configuration/service/webproxy.rst:255 -#: 9ceafaf48a484a65857eb4638af99f1e -msgid "Recommended for larger installations." -msgstr "" - -#: ../../configuration/service/webproxy.rst:263 -#: bbd3263d168446d4be03ad4af841e1be -msgid "" -"Specify an alternate TCP port where the ldap server is listening if other " -"than the default LDAP port 389." -msgstr "" - -#: ../../configuration/service/webproxy.rst:272 -#: 9d74d3e2b9b74b45b1a09d8bb121d3af -msgid "Specify the LDAP server to connect to." -msgstr "" - -#: ../../configuration/service/webproxy.rst:281 -#: 6763d958d61b46aa9c6c4248560a8e46 -msgid "Use TLS encryption." -msgstr "" - -#: ../../configuration/service/webproxy.rst:290 -#: 457b5b77ff4e463cbb13f535b24a7743 -msgid "" -"Specifies the name of the DN attribute that contains the username/login. " -"Combined with the base DN to construct the users DN when no search filter is" -" specified (`filter-expression`)." -msgstr "" - -#: ../../configuration/service/webproxy.rst:294 -#: 1dbb8c6c5ac64d63ae6015007f4fe68f -msgid "Defaults to 'uid'" -msgstr "" - -#: ../../configuration/service/webproxy.rst:296 -#: 678364aaeac34065a42ce428e0eb02c0 -msgid "" -"This can only be done if all your users are located directly under the same " -"position in the LDAP tree and the login name is used for naming each user " -"object. If your LDAP tree does not match these criterias or if you want to " -"filter who are valid users then you need to use a search filter to search " -"for your users DN (`filter-expression`)." -msgstr "" - -#: ../../configuration/service/webproxy.rst:308 -#: 166850e762e64808a1af34766b91aa25 -msgid "LDAP protocol version. Defaults to 3 if not specified." -msgstr "" - -#: ../../configuration/service/webproxy.rst:315 -#: 1cab4ca8905a4ab79bea13eb38b5d30d -msgid "URL filtering" -msgstr "" - -#: ../../_include/need_improvement.txt:11 -#: ../../_include/need_improvement.txt:11 -#: ../../_include/need_improvement.txt:11 2e6a6178362048ce803573ce1dc1a148 -#: 4d989f72f00e4240a3a8ee900b3b3765 e305f33888d947e3a07c9ef4a6642b8c -msgid "This section needs improvements, examples and explanations." -msgstr "" - -#: ../../_include/need_improvement.txt:13 -#: ../../_include/need_improvement.txt:13 -#: ../../_include/need_improvement.txt:13 9f148aab5d644e5a89571a1a217b32cf -#: d2dc8159d993442ba88bbce98010a464 52d30e7a13c44a179de6f7b2ae6fc03f -msgid "" -"Please take a look at the Contributing Guide for our :ref:`documentation`." -msgstr "" - -#: ../../configuration/service/webproxy.rst:322 -#: 253b836088b04211a386af03191e0bf4 -msgid "Disables web filtering without discarding configuration." -msgstr "" - -#: ../../configuration/service/webproxy.rst:330 -#: 72fbadeda83040fcb7c281501d1e07ed -msgid "Operation" -msgstr "" - -#: ../../configuration/service/webproxy.rst:335 -#: 4d5c9a2e6ae54dda9cefd9bc5eb14889 -msgid "Filtering" -msgstr "" - -#: ../../configuration/service/webproxy.rst:338 -#: dbf0eb4880cc46b39cdf0287631bec1f -msgid "Update" -msgstr "" - -#: ../../configuration/service/webproxy.rst:340 -#: 252e167bcfb14c7da73cce65adc65748 -msgid "" -"If you want to use existing blacklists you have to create/download a " -"database first. Otherwise you will not be able to commit the config changes." -msgstr "" - -#: ../../configuration/service/webproxy.rst:346 -#: 2360dec7a1f34b0ea3938bb3ee5b6e66 -msgid "Download/Update complete blacklist" -msgstr "" - -#: ../../configuration/service/webproxy.rst:377 -#: 02b17c7b9c68425fb1b4540824f86870 -msgid "Download/Update partial blacklist." -msgstr "" - -#: ../../configuration/service/webproxy.rst:379 -#: ffaade6edd3849058871ed600c583f64 -msgid "Use tab completion to get a list of categories." -msgstr "" - -#: ../../configuration/service/webproxy.rst:381 -#: 3f95aaf66e404964b0e9273eeebf7f7c -msgid "To auto update the blacklist files" -msgstr "" - -#: ../../configuration/service/webproxy.rst:383 -#: 1cd52f4051ad48529db82ac72a9fd0f3 -msgid "" -":code:`set service webproxy url-filtering squidguard auto-update update-hour" -" 23`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:386 -#: 5d6f042eba4341bbac7ac87a14af7a16 -msgid "To configure blocking add the following to the configuration" -msgstr "" - -#: ../../configuration/service/webproxy.rst:388 -#: 87b4e85b230a48dd87256a876ae3aa92 -msgid "" -":code:`set service webproxy url-filtering squidguard block-category ads`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:390 -#: 5c35bf2900d3452d924c3ddc66a778b2 -msgid "" -":code:`set service webproxy url-filtering squidguard block-category malware`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:393 -#: 47cc3779c6004383b64fe2e56913cea0 -msgid "Bypassing the webproxy" -msgstr "" - -#: ../../configuration/service/webproxy.rst:397 -#: 93e6e04d489e4766a499251856710dd7 -msgid "" -"Some services don't work correctly when being handled via a web proxy. So " -"sometimes it is useful to bypass a transparent proxy:" -msgstr "" - -#: ../../configuration/service/webproxy.rst:400 -#: eb403290f6524f5d8a55495e09529dc3 -msgid "" -"To bypass the proxy for every request that is directed to a specific " -"destination:" -msgstr "" - -#: ../../configuration/service/webproxy.rst:403 -#: fa20896664284b5d958a27eb72a3485e -msgid "" -":code:`set service webproxy whitelist destination-address 198.51.100.33`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:405 -#: 429099b711e54df4812b9a230bcdf7a5 -msgid "" -":code:`set service webproxy whitelist destination-address 192.0.2.0/24`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:408 -#: d8e55d5f16cb443eadc13d0a7c51c8c7 -msgid "" -"To bypass the proxy for every request that is coming from a specific source:" -msgstr "" - -#: ../../configuration/service/webproxy.rst:410 -#: 01ca9b67f2384032a1debc8a183d6218 -msgid ":code:`set service webproxy whitelist source-address 192.168.1.2`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:412 -#: 4f56491d176746cb9cbb3bf22104acbb -msgid ":code:`set service webproxy whitelist source-address 192.168.2.0/24`" -msgstr "" - -#: ../../configuration/service/webproxy.rst:414 -#: e2688db21cd14b2a86823399c499ac76 -msgid "" -"(This can be useful when a called service has many and/or often changing " -"destination addresses - e.g. Netflix.)" -msgstr "" - -#: ../../configuration/service/webproxy.rst:419 -#: 2617becbf29e45b0a475728b9f78083b -msgid "Examples" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/acceleration.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/acceleration.po deleted file mode 100644 index 85b43c5d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/acceleration.po +++ /dev/null @@ -1,109 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/acceleration.rst:5 -#: 821f098e97ac42178fce2d1d87697f85 -msgid "Acceleration" -msgstr "" - -#: ../../configuration/system/acceleration.rst:7 -#: 1d213449b6694993944862f72fcbbde8 -msgid "" -"In this command tree, all hardware acceleration options will be handled. At " -"the moment only `Intel® QAT`_ is supported" -msgstr "" - -#: ../../configuration/system/acceleration.rst:12 -#: ef7f658417ec41ba98e541510944379c -msgid "Intel® QAT" -msgstr "" - -#: ../../configuration/system/acceleration.rst:16 -#: e3d1480460b2482ca31ee123fd351265 -msgid "" -"use this command to check if there is an Intel® QAT supported Processor in " -"your system." -msgstr "" - -#: ../../configuration/system/acceleration.rst:24 -#: 907f542a3245459aadda77377308fc53 -msgid "if there is non device the command will show ```No QAT device found```" -msgstr "" - -#: ../../configuration/system/acceleration.rst:28 -#: b6cd70058eec49f4bdab1670c40799de -msgid "if there is a supported device, enable Intel® QAT" -msgstr "" - -#: ../../configuration/system/acceleration.rst:32 -#: ff39e7bf3bbc40968f1f16003607b506 -msgid "Check if the Intel® QAT device is up and ready to do the job." -msgstr "" - -#: ../../configuration/system/acceleration.rst:42 -#: d3427a1e78f14ca6af21919f36b7fd9a -msgid "Operation Mode" -msgstr "" - -#: ../../configuration/system/acceleration.rst:46 -#: 7cfa3edf9615495c94f808bc158d47da -msgid "Show the full config uploaded to the QAT device." -msgstr "" - -#: ../../configuration/system/acceleration.rst:50 -#: eb359a2c7fc445fdac4edc54bd502aec -msgid "Get an overview over the encryption counters." -msgstr "" - -#: ../../configuration/system/acceleration.rst:54 -#: 8f890562fd734c4eabe7a823000a0c21 -msgid "Show binded qat device interrupts to certain core." -msgstr "" - -#: ../../configuration/system/acceleration.rst:58 -#: 3811a9bf7bd34212a197873637e979e4 -msgid "Example" -msgstr "" - -#: ../../configuration/system/acceleration.rst:60 -#: 52abe2f1cd6c4398ad4a1eca77d9f7a9 -msgid "Let's build a simple VPN between 2 Intel® QAT ready devices." -msgstr "" - -#: ../../configuration/system/acceleration.rst:62 -#: 11e0d6128fa74778a14f95fa737ceb99 -msgid "Side A:" -msgstr "" - -#: ../../configuration/system/acceleration.rst:81 -#: ddeb4d4ef9254382b1808b25e99c5844 -msgid "Side B:" -msgstr "" - -#: ../../configuration/system/acceleration.rst:100 -#: 7dfe2d8f3cd94c77a1a24ebbd487716e -msgid "a bandwidth test over the VPN got these results:" -msgstr "" - -#: ../../configuration/system/acceleration.rst:122 -#: 9afaedaa0e94477da1e54ea3f13b1e7b -msgid "" -"with :cfgcmd:`set system acceleration qat` on both systems the bandwidth " -"increases." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/conntrack.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/conntrack.po deleted file mode 100644 index e87f37aa..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/conntrack.po +++ /dev/null @@ -1,47 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/conntrack.rst:3 00592094fdcc4840aa515ed9206b170f -msgid "Connection tracking" -msgstr "" - -#: ../../configuration/system/conntrack.rst:6 1b3b94e0296241f791b2c73b6fb576f4 -msgid "Modules" -msgstr "" - -#: ../../configuration/system/conntrack.rst:22 -#: 8e49e9ba31a449899efa9ff0fa534a05 -msgid "" -"Enables ``conntrack`` modules. All modules are now disabled by default, " -"while they used to be enabled in previous versions. Enabling the modules " -"ensures backwards compatibility — keeping the previous behavior." -msgstr "" - -#: ../../configuration/system/conntrack.rst:26 -#: bc264b665fae40c595e4ac7dbb3541e9 -msgid "" -"In most cases they can be disabled by removing the block of configuration." -msgstr "" - -#: ../../configuration/system/conntrack.rst:32 -#: 19bba7dcbe60459e934c51567a5333b8 -msgid "" -"For some scenarios it is in fact recommended, like in this example: " -":ref:`example-high-availability`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/console.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/console.po deleted file mode 100644 index cabaa128..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/console.po +++ /dev/null @@ -1,103 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/console.rst:5 c8a40a25bcf9478eb4d63081139a9836 -msgid "Serial Console" -msgstr "" - -#: ../../configuration/system/console.rst:7 d66bf136b560492a8a8734a90c40b9e8 -msgid "" -"For the average user a serial console has no advantage over a console " -"offered by a directly attached keyboard and screen. Serial consoles are much" -" slower, taking up to a second to fill a 80 column by 24 line screen. Serial" -" consoles generally only support non-proportional ASCII text, with limited " -"support for languages other than English." -msgstr "" - -#: ../../configuration/system/console.rst:13 c7d358150654443d9fb736b1c5cc0d39 -msgid "" -"There are some scenarios where serial consoles are useful. System " -"administration of remote computers is usually done using :ref:`ssh`, but " -"there are times when access to the console is the only way to diagnose and " -"correct software failures. Major upgrades to the installed distribution may " -"also require console access." -msgstr "" - -#: ../../configuration/system/console.rst:21 dbafadd94c9c4a678c64321460f5603d -msgid "" -"Defines the specified device as a system console. Available console devices " -"can be (see completion helper):" -msgstr "" - -#: ../../configuration/system/console.rst:24 8716655ab2914c6f90f54ffc77fc6ed1 -msgid "``ttySN`` - Serial device name" -msgstr "" - -#: ../../configuration/system/console.rst:25 f72ef713acb0410cad08fb73ae7e57ad -msgid "``ttyUSBX`` - USB Serial device name" -msgstr "" - -#: ../../configuration/system/console.rst:26 147f90ecdba247c4b4c12a616aa586d8 -msgid "``hvc0`` - Xen console" -msgstr "" - -#: ../../configuration/system/console.rst:30 caffe5cb53fe4278912ffde49551add1 -msgid "The speed (baudrate) of the console device. Supported values are:" -msgstr "" - -#: ../../configuration/system/console.rst:32 65bd9287f77e4a45b64dfa5d15a3e4e8 -msgid "``1200`` - 1200 bps" -msgstr "" - -#: ../../configuration/system/console.rst:33 7c395c67909a424c96901efe1f65ed9d -msgid "``2400`` - 2400 bps" -msgstr "" - -#: ../../configuration/system/console.rst:34 6b89ffe625c7448b89848f33cff8dce6 -msgid "``4800`` - 4800 bps" -msgstr "" - -#: ../../configuration/system/console.rst:35 bc61491fd7af4e359d612d7bc4b82e8e -msgid "``9600`` - 9600 bps" -msgstr "" - -#: ../../configuration/system/console.rst:36 c2642cd8b93c48e09817807d73e8baa6 -msgid "``19200`` - 19,200 bps" -msgstr "" - -#: ../../configuration/system/console.rst:37 8c364f95930d42b8a0b4d3eb666b2fab -msgid "``38400`` - 38,400 bps (default for Xen console)" -msgstr "" - -#: ../../configuration/system/console.rst:38 3786460da7bd48469f1168bef7bb1291 -msgid "``57600`` - 57,600 bps" -msgstr "" - -#: ../../configuration/system/console.rst:39 3c2a58bac7634966b4942aaf10dacd7e -msgid "``115200`` - 115,200 bps (default for serial console)" -msgstr "" - -#: ../../configuration/system/console.rst:41 3371b5e1ea0b426c807b2ca381a1ba9b -msgid "" -"If you use USB to serial converters for connecting to your VyOS appliance " -"please note that most of them use software emulation without flow control. " -"This means you should start with a common baud rate (most likely 9600 baud) " -"as otherwise you probably can not connect to the device using high speed " -"baud rates as your serial converter simply can not process this data rate." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/default-route.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/default-route.po deleted file mode 100644 index f2d73fa5..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/default-route.po +++ /dev/null @@ -1,63 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/default-route.rst:5 -#: 41b8642519e34e289af16b09c2d3ac2e -msgid "Default Gateway/Route" -msgstr "" - -#: ../../configuration/system/default-route.rst:7 -#: c1cf670feb7e40939d6d177190f6d233 -msgid "" -"In the past (VyOS 1.1) used a gateway-address configured under the system " -"tree (:cfgcmd:`set system gateway-address <address>`), this is no longer " -"supported and existing configurations are migrated to the new CLI command." -msgstr "" - -#: ../../configuration/system/default-route.rst:12 -#: 5987461251c8432c92c2f2d9f16f9a89 -msgid "Configuration" -msgstr "" - -#: ../../configuration/system/default-route.rst:16 -#: 8f0831ac121d4e549a0b81ea3dc54dd1 -msgid "" -"Specify static route into the routing table sending all non local traffic to" -" the nexthop address `<address>`." -msgstr "" - -#: ../../configuration/system/default-route.rst:22 -#: 5d3ff9c262114692afdc654b01f09da1 -msgid "Delete default route from the system." -msgstr "" - -#: ../../configuration/system/default-route.rst:25 -#: da68ce61593b45e889640a11630f4f65 -msgid "Operation" -msgstr "" - -#: ../../configuration/system/default-route.rst:29 -#: 95915e06c828449089c9d00e3a22b28d -msgid "Show routing table entry for the default route." -msgstr "" - -#: ../../configuration/system/default-route.rst:39 -#: cabae10b545749c9855b40003d305535 -msgid "Configuration of :ref:`routing-static`" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/flow-accounting.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/flow-accounting.po deleted file mode 100644 index 8bef5a1b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/flow-accounting.po +++ /dev/null @@ -1,329 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/flow-accounting.rst:5 -#: 7c507126ac294633bb2ecfe47674e6c4 -msgid "Flow Accounting" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:7 -#: 4faea2658801476db63363dfb3fe12a9 -msgid "" -"VyOS supports flow-accounting for both IPv4 and IPv6 traffic. The system " -"acts as a flow exporter, and you are free to use it with any compatible " -"collector." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:10 -#: dd690f2e299a40f59ec3e3b390f63f59 -msgid "" -"Flows can be exported via two different protocols: NetFlow (versions 5, 9 " -"and 10/IPFIX) and sFlow. Additionally, you may save flows to an in-memory " -"table internally in a router." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:14 -#: 28f932d5a9bf4962bcb4ab6e1ac4c4e4 -msgid "" -"You need to disable the in-memory table in production environments! Using " -":abbr:`IMT (In-Memory Table)` may lead to heavy CPU overloading and unstable" -" flow-accounting behavior." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:20 -#: 6729abc977804d3aa8dadcad836e9495 -msgid "NetFlow / IPFIX" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:21 -#: b64630766e7048ec9a9f61ff64d47170 -msgid "" -"NetFlow is a feature that was introduced on Cisco routers around 1996 that " -"provides the ability to collect IP network traffic as it enters or exits an " -"interface. By analyzing the data provided by NetFlow, a network " -"administrator can determine things such as the source and destination of " -"traffic, class of service, and the causes of congestion. A typical flow " -"monitoring setup (using NetFlow) consists of three main components:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:28 -#: 6c8d8f2c39e4449faff60e2069cbd003 -msgid "" -"**exporter**: aggregates packets into flows and exports flow records towards" -" one or more flow collectors" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:30 -#: 26cde8ce1615485cbe18aab92b3e315d -msgid "" -"**collector**: responsible for reception, storage and pre-processing of flow" -" data received from a flow exporter" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:32 -#: c4c8324a2e434706b973f016e8605c01 -msgid "" -"**application**: analyzes received flow data in the context of intrusion " -"detection or traffic profiling, for example" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:35 -#: 152addad6f744dd7a0c18c8a502c74f3 -msgid "" -"For connectionless protocols as like ICMP and UDP, a flow is considered " -"complete once no more packets for this flow appear after configurable " -"timeout." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:38 -#: 5d984f3b66a242fe9988752877fcc2e6 -msgid "" -"NetFlow is usually enabled on a per-interface basis to limit load on the " -"router components involved in NetFlow, or to limit the amount of NetFlow " -"records exported." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:43 -#: 5f7cb984c5794af28e0c0d60a2845850 -msgid "Configuration" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:45 -#: 6b55b581bf824d50824f3462c6284f87 -msgid "" -"In order for flow accounting information to be collected and displayed for " -"an interface, the interface must be configured for flow accounting." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:50 -#: acac6e44f7144abf9ed93cd37060bd1f -msgid "" -"Configure and enable collection of flow information for the interface " -"identified by `<interface>`." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:53 -#: 002e8284969f443fae523a8b6811ad66 -msgid "" -"You can configure multiple interfaces which whould participate in flow " -"accounting." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:56 -#: 168da2f6210149f095fbb964762c2f1c -msgid "" -"Will be recorded only packets/flows on **incoming** direction in configured " -"interfaces by default." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:60 -#: 4696bc924bc14ef9bd1613cf76546f2a -msgid "" -"By default, recorded flows will be saved internally and can be listed with " -"the CLI command. You may disable using the local in-memory table with the " -"command:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:65 -#: d7a3845c649048778f8fb2e4f28ff245 -msgid "" -"If you need to sample also egress traffic, you may want to configure egress " -"flow-accounting:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:70 -#: 984d7349b3ba4eebaae443065ea27cb1 -msgid "" -"Internally, in flow-accounting processes exist a buffer for data exchanging " -"between core process and plugins (each export target is a separated plugin)." -" If you have high traffic levels or noted some problems with missed records " -"or stopping exporting, you may try to increase a default buffer size (10 " -"MiB) with the next command:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:78 -#: 9bff01bb85ad4c61b34cb6ff1ebe0e94 -msgid "" -"In case, if you need to catch some logs from flow-accounting daemon, you may" -" configure logging facility:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:83 -#: 285242b2a836431ba1252c5c55a335c7 -msgid "TBD" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:86 -#: 99a439f8192a4c60b70326e4261dfc62 -msgid "Flow Export" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:88 -#: e5779d05d59b4c608a0bbb730084a32a -msgid "" -"In addition to displaying flow accounting information locally, one can also " -"exported them to a collection server." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:92 -#: cae0d897dd5d40f4b600e56997b91176 -msgid "NetFlow" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:96 -#: 6e3b6b23f45f4f2eae285cb0167dec0d -msgid "" -"There are multiple versions available for the NetFlow data. The `<version>` " -"used in the exported flow data can be configured here. The following " -"versions are supported:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:100 -#: 6248f70d055a4abc9805bf6ab005cc46 -msgid "**5** - Most common version, but restricted to IPv4 flows only" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:101 -#: 1d003b9e94cb45c18f09609bd87b1396 -msgid "**9** - NetFlow version 9 (default)" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:102 -#: 273c7b9390824620a80f65218203f773 -msgid "**10** - :abbr:`IPFIX (IP Flow Information Export)` as per :rfc:`3917`" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:106 -#: f30aaa3c140f42e1831113b06cf9b1c4 -msgid "" -"Configure address of NetFlow collector. NetFlow server at `<address>` can be" -" both listening on an IPv4 or IPv6 address." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:111 -#: 9222d33e53ed48fc942366baf2e95f3a -msgid "IPv4 or IPv6 source address of NetFlow packets" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:115 -#: 67c813562f61459ba5de8ad0f7a2057f -msgid "" -"NetFlow engine-id which will appear in NetFlow data. The range is 0 to 255." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:119 -#: 5e571bf1e2b840b9bdb0f7782048be85 -msgid "" -"Use this command to configure the sampling rate for flow accounting. The " -"system samples one in every `<rate>` packets, where `<rate>` is the value " -"configured for the sampling-rate option. The advantage of sampling every n " -"packets, where n > 1, allows you to decrease the amount of processing " -"resources required for flow accounting. The disadvantage of not sampling " -"every packet is that the statistics produced are estimates of actual data " -"flows." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:127 -#: 9974de1c428c445bbbe002b4314fbd99 -msgid "Per default every packet is sampled (that is, the sampling rate is 1)." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:132 -#: a13fae2fc12d48f5885e9f9776f059ca -msgid "" -"Specifies the interval at which Netflow data will be sent to a collector. As" -" per default, Netflow data will be sent every 60 seconds." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:135 -#: 73db344e4c5041b48d449a4160041493 -msgid "" -"You may also additionally configure timeouts for different types of " -"connections." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:140 -#: e493bc928a72478db2179fb8f3de1a64 -msgid "" -"If you want to change the maximum number of flows, which are tracking " -"simultaneously, you may do this with this command (default 8192)." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:144 -#: 5d89175c28014dc185b32d44825cba8e -msgid "sFlow" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:148 -#: 401373b64122454c98a13e16f010c6ef -msgid "" -"Configure address of sFlow collector. sFlow server at `<address>` can be an " -"IPv4 or IPv6 address. But you cannot export to both IPv4 and IPv6 collectors" -" at the same time!" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:154 -#: 8b283ec707fa4b23b74d9bab3d40466b -msgid "" -"Enable sampling of packets, which will be transmitted to sFlow collectors." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:158 -#: 3319c16077694ab2b6cba33c011a9c46 -msgid "" -"Configure a sFlow agent address. It can be IPv4 or IPv6 address, but you " -"must set the same protocol, which is used for sFlow collector addresses. By " -"default, using router-id from BGP or OSPF protocol, or the primary IP " -"address from the first interface." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:164 -#: 88055d7f47dd44a396ab62d20a529bce -msgid "Example:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:166 -#: 39a17c854eca4ba6a653b0b0aab05835 -msgid "NetFlow v5 example:" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:175 -#: 04c95584e414459ba916b8ba2177e9a7 -msgid "Operation" -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:177 -#: 4ae86c4c5ccb45d2bcfc3a69d1d31363 -msgid "" -"Once flow accounting is configured on an interfaces it provides the ability " -"to display captured network traffic information for all configured " -"interfaces." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:182 -#: f80509839b634eaa8a8a8e8308fbd9e9 -msgid "Show flow accounting information for given `<interface>`." -msgstr "" - -#: ../../configuration/system/flow-accounting.rst:199 -#: f5b3517b22bf4952b67a1432dd60f2cd -msgid "" -"Show flow accounting information for given `<interface>` for a specific host" -" only." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/host-name.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/host-name.po deleted file mode 100644 index c1d564db..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/host-name.po +++ /dev/null @@ -1,131 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/host-name.rst:5 d0bc5c5d489d426b80735313bc60e83b -msgid "Host Information" -msgstr "" - -#: ../../configuration/system/host-name.rst:7 ceedb0efa31b420886a06d2f1bb5c7b7 -msgid "" -"This section describes the system's host information and how to configure " -"them, it covers the following topics:" -msgstr "" - -#: ../../configuration/system/host-name.rst:10 -#: 29d0170b994448f688192ec7bc8612f4 -msgid "Host name" -msgstr "" - -#: ../../configuration/system/host-name.rst:11 -#: e9634b14823944158ad08385bfa2dee4 -msgid "Domain" -msgstr "" - -#: ../../configuration/system/host-name.rst:12 -#: 113e9630d8e0411e9475c415c9df9066 -msgid "IP address" -msgstr "" - -#: ../../configuration/system/host-name.rst:13 -#: 5f8ae80a2c2646f7a55e6b20a35c1361 -msgid "Aliases" -msgstr "" - -#: ../../configuration/system/host-name.rst:16 -#: bf01c992578d4413a6a6fa6efd83df8c -msgid "Hostname" -msgstr "" - -#: ../../configuration/system/host-name.rst:18 -#: afcc4e87dedb47e195e6fac545734cff -msgid "" -"A hostname is the label (name) assigned to a network device (a host) on a " -"network and is used to distinguish one device from another on specific " -"networks or over the internet. On the other hand this will be the name which" -" appears on the command line prompt." -msgstr "" - -#: ../../configuration/system/host-name.rst:25 -#: ab4085e22cd54710b6499bd7aad5deb8 -msgid "" -"The hostname can be up to 63 characters. A hostname must start and end with " -"a letter or digit, and have as interior characters only letters, digits, or " -"a hyphen." -msgstr "" - -#: ../../configuration/system/host-name.rst:29 -#: a0c9f7bd963d4c4fbeba5728b4ae667b -msgid "The default hostname used is `vyos`." -msgstr "" - -#: ../../configuration/system/host-name.rst:32 -#: 835f70ef00f046f28e557b14602a0b0e -msgid "Domain Name" -msgstr "" - -#: ../../configuration/system/host-name.rst:34 -#: 5e763071abdc4615b268a1f4f35e90c6 -msgid "" -"A domain name is the label (name) assigned to a computer network and is thus" -" unique. VyOS appends the domain name as a suffix to any unqualified name. " -"For example, if you set the domain name `example.com`, and you would ping " -"the unqualified name of `crux`, then VyOS qualifies the name to " -"`crux.example.com`." -msgstr "" - -#: ../../configuration/system/host-name.rst:41 -#: 08807b6ee7f8414cace69327abee7973 -msgid "" -"Configure system domain name. A domain name must start and end with a letter" -" or digit, and have as interior characters only letters, digits, or a " -"hyphen." -msgstr "" - -#: ../../configuration/system/host-name.rst:45 -#: e9b3511ebcd546009c72ac69d8aa3d9c -msgid "Static Hostname Mapping" -msgstr "" - -#: ../../configuration/system/host-name.rst:47 -#: 0773804cc61146c7aa54aac11f31f9f0 -msgid "" -"How an IP address is assigned to an interface in :ref:`ethernet-interface`. " -"This section shows how to statically map an IP address to a hostname for " -"local (meaning on this VyOS instance) name resolution." -msgstr "" - -#: ../../configuration/system/host-name.rst:53 -#: 896ee5133a8a494a9690d8b07beb5c7b -msgid "" -"Create a static hostname mapping which will always resolve the name " -"`<hostname>` to IP address `<address>`." -msgstr "" - -#: ../../configuration/system/host-name.rst:59 -#: 26593e0901974db1b9ca80f80901671b -msgid "" -"Create named `<alias>` for the configured static mapping for `<hostname>`. " -"Thus the address configured as :cfgcmd:`set system static-host-mapping host-" -"name <hostname> inet <address>` can be reached via multiple names." -msgstr "" - -#: ../../configuration/system/host-name.rst:63 -#: f09d1c6617874ec1a12fa1573794d9c0 -msgid "Multiple aliases can pe specified per host-name." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/index.po deleted file mode 100644 index 8717c391..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/index.rst:3 b1931293f06c4814b14cb8c73a206f80 -msgid "System" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ip.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ip.po deleted file mode 100644 index 58b997a4..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ip.po +++ /dev/null @@ -1,74 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/ip.rst:3 72827ac5eb8d42fba4f3f1343e006c76 -msgid "IP" -msgstr "" - -#: ../../configuration/system/ip.rst:6 fbd93824559142f0b0ce7b28a09a8791 -msgid "System configuration commands" -msgstr "" - -#: ../../configuration/system/ip.rst:10 7158b98a94a5403eaebf084f72ac5134 -msgid "Use this command to disable IPv4 forwarding on all interfaces." -msgstr "" - -#: ../../configuration/system/ip.rst:14 0f20c33be9a14f01a82ab4b8e98e0e49 -msgid "" -"Use this command to disable IPv4 directed broadcast forwarding on all " -"interfaces." -msgstr "" - -#: ../../configuration/system/ip.rst:17 5f8b9ecf5d344d00893c93afcf90e854 -msgid "" -"If set, IPv4 directed broadcast forwarding will be completely disabled " -"regardless of whether per-interface directed broadcast forwarding is enabled" -" or not." -msgstr "" - -#: ../../configuration/system/ip.rst:23 b30de3b04a0f48269160f52701a90341 -msgid "" -"Use this command to define the maximum number of entries to keep in the ARP " -"cache (1024, 2048, 4096, 8192, 16384, 32768)." -msgstr "" - -#: ../../configuration/system/ip.rst:28 a30dba31aef54ac8a8046c334a321fef -msgid "Use this command to use Layer 4 information for IPv4 ECMP hashing." -msgstr "" - -#: ../../configuration/system/ip.rst:32 f06b7f7e9b414164999ab0d9d7201111 -msgid "Operational commands" -msgstr "" - -#: ../../configuration/system/ip.rst:35 3293a6f5a401468e9e3d9086e058cc0d -msgid "show commands" -msgstr "" - -#: ../../configuration/system/ip.rst:37 391a60d6b6534a9e9367e1a3577d6bdc -msgid "" -"See below the different parameters available for the IPv4 **show** command:" -msgstr "" - -#: ../../configuration/system/ip.rst:67 14a72274adc9479384f3665bf377e2b9 -msgid "reset commands" -msgstr "" - -#: ../../configuration/system/ip.rst:69 7d62b4d25095493089f5b61320bafbfc -msgid "And the different IPv4 **reset** commands available:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ipv6.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ipv6.po deleted file mode 100644 index 40829511..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ipv6.po +++ /dev/null @@ -1,138 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/ipv6.rst:3 cedcaec63a064d889e34671a71a06712 -msgid "IPv6" -msgstr "" - -#: ../../configuration/system/ipv6.rst:6 b45aca5de9e64c159a13dfa203d13a7d -msgid "System configuration commands" -msgstr "" - -#: ../../configuration/system/ipv6.rst:10 a477535cc5a84c8cab696fcabb81f11b -msgid "Use this command to disable IPv6 forwarding on all interfaces." -msgstr "" - -#: ../../configuration/system/ipv6.rst:14 954c1c4f10d649838ceb32d95c24b26b -msgid "" -"Use this command to define the maximum number of entries to keep in the " -"Neighbor cache (1024, 2048, 4096, 8192, 16384, 32768)." -msgstr "" - -#: ../../configuration/system/ipv6.rst:19 6279de7f38c44a3c97ddbf1628a6fc19 -msgid "" -"Use this command to disable IPv6 operation on interface when Duplicate " -"Address Detection fails on Link-Local address." -msgstr "" - -#: ../../configuration/system/ipv6.rst:24 95f0935fe2af4d03a6b413b6d64981eb -msgid "Use this command to user Layer 4 information for ECMP hashing." -msgstr "" - -#: ../../configuration/system/ipv6.rst:28 901626e6b6b54c2b881d5f55fe990e91 -msgid "Operational commands" -msgstr "" - -#: ../../configuration/system/ipv6.rst:31 bf5f809b908142768eb86df0a218c634 -msgid "Show commands" -msgstr "" - -#: ../../configuration/system/ipv6.rst:35 bbc192c3fc2b498287f81d1fe4c2de95 -msgid "Use this command to show IPv6 Neighbor Discovery Protocol information." -msgstr "" - -#: ../../configuration/system/ipv6.rst:39 0e38489616bc470ca9dc016de7207c1c -msgid "Use this command to show IPv6 multicast group membership." -msgstr "" - -#: ../../configuration/system/ipv6.rst:43 b18579dabe0743a78786703359c5fc26 -msgid "Use this command to show IPv6 forwarding status." -msgstr "" - -#: ../../configuration/system/ipv6.rst:47 b9dc066a5d4841ef89b2fcf6f0855f17 -msgid "Use this command to show IPv6 routes." -msgstr "" - -#: ../../configuration/system/ipv6.rst:49 8fff9f91ba534194be643d3663c879cd -msgid "Check the many parameters available for the `show ipv6 route` command:" -msgstr "" - -#: ../../configuration/system/ipv6.rst:74 ff73ee6849ae49bdae3b327cb7012d29 -msgid "Use this command to show all IPv6 prefix lists" -msgstr "" - -#: ../../configuration/system/ipv6.rst:76 a447af3ccbf644b7a0db14eb5774d7eb -msgid "There are different parameters for getting prefix-list information:" -msgstr "" - -#: ../../configuration/system/ipv6.rst:89 f7b87642985a497687d8b070fcd85989 -msgid "Use this command to show all IPv6 access lists" -msgstr "" - -#: ../../configuration/system/ipv6.rst:91 7cab766e3a124be58465064a721204c1 -msgid "You can also specify which IPv6 access-list should be shown:" -msgstr "" - -#: ../../configuration/system/ipv6.rst:102 78b0bb91a3e5469b9d942439066db933 -msgid "Use this command to show IPv6 Border Gateway Protocol information." -msgstr "" - -#: ../../configuration/system/ipv6.rst:105 096bf04aebca4f518f72d380f7cedf2e -msgid "" -"In addition, you can specify many other parameters to get BGP information:" -msgstr "" - -#: ../../configuration/system/ipv6.rst:131 a7c5f791347a4cb5aaeb28b3b4b7230e -msgid "Use this command to get information about OSPFv3." -msgstr "" - -#: ../../configuration/system/ipv6.rst:133 1cec4a707efb4edbb999a124eada2832 -msgid "" -"You can get more specific OSPFv3 information by using the parameters shown " -"below:" -msgstr "" - -#: ../../configuration/system/ipv6.rst:153 f525dd3f953e4d1da74e11728051e72d -msgid "Use this command to get information about the RIPNG protocol" -msgstr "" - -#: ../../configuration/system/ipv6.rst:157 6e05122daaef4086818599f13f2b4370 -msgid "Use this command to show the status of the RIPNG protocol" -msgstr "" - -#: ../../configuration/system/ipv6.rst:161 c8f3dae52e654c8e918bc48bc9280255 -msgid "Reset commands" -msgstr "" - -#: ../../configuration/system/ipv6.rst:165 d9b8466aeb3e4209afad4e3a3868731b -msgid "" -"Use this command to clear Border Gateway Protocol statistics or status." -msgstr "" - -#: ../../configuration/system/ipv6.rst:171 9ba8addfc4ca4620b6074149e614434e -msgid "" -"Use this command to reset IPv6 Neighbor Discovery Protocol cache for an " -"address or interface." -msgstr "" - -#: ../../configuration/system/ipv6.rst:176 a9bee3489da44460a60dbe7d2ead0016 -msgid "" -"Use this command to flush the kernel IPv6 route cache. An address can be " -"added to flush it only for that route." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/lcd.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/lcd.po deleted file mode 100644 index 4a70b430..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/lcd.po +++ /dev/null @@ -1,83 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/lcd.rst:5 7e2d5a3a5afd40f788d5686fd1fdc3da -msgid "System Display (LCD)" -msgstr "" - -#: ../../configuration/system/lcd.rst:7 87c965e2109044a4b0926414377fab9f -msgid "" -"The system LCD :abbr:`LCD (Liquid-crystal display)` option is for users " -"running VyOS on hardware that features an LCD display. This is typically a " -"small display built in an 19 inch rack-mountable appliance. Those displays " -"are used to show runtime data." -msgstr "" - -#: ../../configuration/system/lcd.rst:12 68360fbe565e49acb9e398594f2f5218 -msgid "" -"To configure your LCD display you must first identify the used hardware, and" -" connectivity of the display to your system. This can be any serial port " -"(`ttySxx`) or serial via USB or even old parallel port interfaces." -msgstr "" - -#: ../../configuration/system/lcd.rst:17 ebc9af9ea8164794b29eb33cd975a9df -msgid "Configuration" -msgstr "" - -#: ../../configuration/system/lcd.rst:21 bd124499b0154f518d41f32be62c9b0d -msgid "" -"This is the name of the physical interface used to connect to your LCD " -"display. Tab completion is supported and it will list you all available " -"serial interface." -msgstr "" - -#: ../../configuration/system/lcd.rst:25 8664d5eb1cb14f2dbbb2cff631914943 -msgid "" -"For serial via USB port information please refor to: :ref:`hardware_usb`." -msgstr "" - -#: ../../configuration/system/lcd.rst:29 9120bc10827f44248ee4f64373892ed6 -msgid "This is the LCD model used in your system." -msgstr "" - -#: ../../configuration/system/lcd.rst:31 2a053d783b95427283934c983def3812 -msgid "At the time of this writing the following displays are supported:" -msgstr "" - -#: ../../configuration/system/lcd.rst:33 d5623379a3ee4ad28d64cf6f6edb11c0 -msgid "Crystalfontz CFA-533" -msgstr "" - -#: ../../configuration/system/lcd.rst:35 f6cb794313704525a92a251bbe65dd4f -msgid "Crystalfontz CFA-631" -msgstr "" - -#: ../../configuration/system/lcd.rst:37 21b111183e91400dbafdcf17ea639473 -msgid "Crystalfontz CFA-633" -msgstr "" - -#: ../../configuration/system/lcd.rst:39 f642016a9dac4413936aec6559a90a0c -msgid "Crystalfontz CFA-635" -msgstr "" - -#: ../../configuration/system/lcd.rst:41 fc46434f376545ce810d174e37f0b521 -msgid "" -"We can't support all displays from the beginning. If your display type is " -"missing, please create a feature request via Phabricator_." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/login.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/login.po deleted file mode 100644 index bd0f85fe..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/login.po +++ /dev/null @@ -1,336 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/login.rst:7 2a6ac8329326490fb89d619dc2b2b140 -msgid "Login/User Management" -msgstr "" - -#: ../../configuration/system/login.rst:9 f4099b92ffa74a258d310f21ee3382d0 -msgid "" -"The default VyOS user account (`vyos`), as well as newly created user " -"accounts, have all capabilities to configure the system. All accounts have " -"sudo capabilities and therefore can operate as root on the system." -msgstr "" - -#: ../../configuration/system/login.rst:13 22db3235d69143529fc78cdfe2a88a91 -msgid "" -"Both local administered and remote administered :abbr:`RADIUS (Remote " -"Authentication Dial-In User Service)` accounts are supported." -msgstr "" - -#: ../../configuration/system/login.rst:17 e3183a16fa194f4f9557bbd288dc6186 -msgid "Local" -msgstr "" - -#: ../../configuration/system/login.rst:21 867e1d7841c145eea5e4d90219b55a0f -msgid "" -"Create new system user with username `<name>` and real-name specified by " -"`<string>`." -msgstr "" - -#: ../../configuration/system/login.rst:27 bed1818524624887bd9530e2e9ab1f6e -msgid "" -"Specify the plaintext password user by user `<name>` on this system. The " -"plaintext password will be automatically transferred into a secure hashed " -"password and not saved anywhere in plaintext." -msgstr "" - -#: ../../configuration/system/login.rst:34 5838810f142241acb8957e86728f1303 -msgid "" -"Setup encrypted password for given username. This is useful for transferring" -" a hashed password from system to system." -msgstr "" - -#: ../../configuration/system/login.rst:40 2c554056c20c4757807a9681b41c61e3 -msgid "Key Based Authentication" -msgstr "" - -#: ../../configuration/system/login.rst:42 2c16e864c67c4a0b9bfce2e362beaa26 -msgid "" -"It is highly recommended to use SSH key authentication. By default there is " -"only one user (``vyos``), and you can assign any number of keys to that " -"user. You can generate a ssh key with the ``ssh-keygen`` command on your " -"local machine, which will (by default) save it as ``~/.ssh/id_rsa.pub``." -msgstr "" - -#: ../../configuration/system/login.rst:47 aee6a0c51a6a4a688ca1ddb5eb0e295b -msgid "Every SSH key comes in three parts:" -msgstr "" - -#: ../../configuration/system/login.rst:49 70a1c25713084de99cc6bce932244997 -msgid "" -"``ssh-rsa AAAAB3NzaC1yc2EAAAABAA...VBD5lKwEWB username@host.example.com``" -msgstr "" - -#: ../../configuration/system/login.rst:51 365b1f84ce5d43b8a4d09f69db403601 -msgid "" -"Only the type (``ssh-rsa``) and the key (``AAAB3N...``) are used. Note that " -"the key will usually be several hundred characters long, and you will need " -"to copy and paste it. Some terminal emulators may accidentally split this " -"over several lines. Be attentive when you paste it that it only pastes as a " -"single line. The third part is simply an identifier, and is for your own " -"reference." -msgstr "" - -#: ../../configuration/system/login.rst:60 e87f2fee13254054aa33f990fd2a62f5 -msgid "" -"Assign the SSH public key portion `<key>` identified by per-key " -"`<identifier>` to the local user `<username>`." -msgstr "" - -#: ../../configuration/system/login.rst:66 dda8b9d87f7a492eb2197f4387ba29bf -msgid "" -"Every SSH public key portion referenced by `<identifier>` requires the " -"configuration of the `<type>` of public-key used. This type can be any of:" -msgstr "" - -#: ../../configuration/system/login.rst:69 b5542e533f0e40dda92987a90102b825 -msgid "``ecdsa-sha2-nistp256``" -msgstr "" - -#: ../../configuration/system/login.rst:70 7ae7332b53a34d84a21d533fb7486a6f -msgid "``ecdsa-sha2-nistp384``" -msgstr "" - -#: ../../configuration/system/login.rst:71 f004901a27c24eccb4d57b2cbdfa6db4 -msgid "``ecdsa-sha2-nistp521``" -msgstr "" - -#: ../../configuration/system/login.rst:72 c90cc6740c394d7980327a7559a00717 -msgid "``ssh-dss``" -msgstr "" - -#: ../../configuration/system/login.rst:73 7d11a831bfbc41b09080fe1e2f7b74e9 -msgid "``ssh-ed25519``" -msgstr "" - -#: ../../configuration/system/login.rst:74 20129d2101844d59942efc954d4dd183 -msgid "``ssh-rsa``" -msgstr "" - -#: ../../configuration/system/login.rst:76 34dd248406d74d558a8c68ea90b7c067 -msgid "" -"You can assign multiple keys to the same user by using a unique identifier " -"per SSH key." -msgstr "" - -#: ../../configuration/system/login.rst:82 9a1b2b038bbc45b4be94df601818f7b4 -msgid "" -"Set the options for this public key. See the ssh ``authorized_keys`` man " -"page for details of what you can specify here. To place a ``\"`` character " -"in the options field, use ``"``, for example " -"``from="10.0.0.0/24"`` to restrict where the user may connect from" -" when using this key." -msgstr "" - -#: ../../configuration/system/login.rst:89 aaa95e5bad9848679398440af5851406 -msgid "" -"**Deprecation notice:** ``loadkey`` has been deprecated in favour of " -":opcmd:`generate public-key-commands` and will be removed in a future " -"version. See :ref:`ssh`." -msgstr "" - -#: ../../configuration/system/login.rst:93 20b19e774859441b93959b1703cd69a1 -msgid "" -"SSH keys can not only be specified on the command-line but also loaded for a" -" given user with `<username>` from a file pointed to by `<location>.` Keys " -"can be either loaded from local filesystem or any given remote location " -"using one of the following :abbr:`URIs (Uniform Resource Identifier)`:" -msgstr "" - -#: ../../configuration/system/login.rst:98 0e242a5e70b64e278232dcc0899b1166 -msgid "``<file>`` - Load from file on local filesystem path" -msgstr "" - -#: ../../configuration/system/login.rst:99 4e7cc229184c4e4cab22e42cae2cf9d0 -msgid "``scp://<user>@<host>:/<file>`` - Load via SCP from remote machine" -msgstr "" - -#: ../../configuration/system/login.rst:100 55f3eb106b344ee48e2a3a9a77cec8f9 -msgid "``sftp://<user>@<host>/<file>`` - Load via SFTP from remote machine" -msgstr "" - -#: ../../configuration/system/login.rst:101 4fa4f9ddd2fa4cc49c98bba0f3998a13 -msgid "``ftp://<user>@<host>/<file>`` - Load via FTP from remote machine" -msgstr "" - -#: ../../configuration/system/login.rst:102 26010d45a4d349b78895cd002437697e -msgid "``http://<host>/<file>`` - Load via HTTP from remote machine" -msgstr "" - -#: ../../configuration/system/login.rst:103 96cea3eda865402280abb37ba5713c02 -msgid "``tftp://<host>/<file>`` - Load via TFTP from remote machine" -msgstr "" - -#: ../../configuration/system/login.rst:106 5e3dae6003714a219e06743a1bde99db -msgid "MFA/2FA authentication using One-Time-Pad" -msgstr "" - -#: ../../configuration/system/login.rst:108 f88fd0af9f3b4e89a9a8ba724597e88f -msgid "" -"It is possible to enhance authentication security by using the :abbr:`2FA " -"(Two-factor authentication)`/:abbr:`MFA (Multi-factor authentication)` " -"feature together with :abbr:`OTP (One-Time-Pad)` on VyOS. :abbr:`2FA (Two-" -"factor authentication)`/:abbr:`MFA (Multi-factor authentication)` is " -"configured independently per each user. If an OTP key is configured for a " -"user, 2FA/MFA is automatically enabled for that particular user. If a user " -"does not have an OTP key configured, there is no 2FA/MFA check for that " -"user." -msgstr "" - -#: ../../configuration/system/login.rst:118 04c63b9c6c964971b4f5764001f7b2fe -msgid "" -"Enable OTP 2FA for user `username` with default settings, using the BASE32 " -"encoded 2FA/MFA key specified by `<key>`." -msgstr "" - -#: ../../configuration/system/login.rst:122 e6901c3640ed4843b8667ad7d5dbdcb3 -msgid "Optional/default settings" -msgstr "" - -#: ../../configuration/system/login.rst:127 084610ed114349ba8d8b378bc1883974 -msgid "" -"Limit logins to `<limit>` per every ``rate-time`` seconds. Rate limit must " -"be between 1 and 10 attempts." -msgstr "" - -#: ../../configuration/system/login.rst:133 9604988ec23a429186c2ba3c7675f894 -msgid "" -"Limit logins to ``rate-limit`` attemps per every `<seconds>`. Rate time must" -" be between 15 and 600 seconds." -msgstr "" - -#: ../../configuration/system/login.rst:139 3db27fa3ec744b8491f97ccbe0bb6b2e -msgid "Set window of concurrently valid codes." -msgstr "" - -#: ../../configuration/system/login.rst:141 6625cc16c9ee446486c61e8d650bac0a -msgid "" -"By default, a new token is generated every 30 seconds by the mobile " -"application. In order to compensate for possible time-skew between the " -"client and the server, an extra token before and after the current time is " -"allowed. This allows for a time skew of up to 30 seconds between " -"authentication server and client." -msgstr "" - -#: ../../configuration/system/login.rst:147 297aee9553994765b381f9d038570cc8 -msgid "" -"For example, if problems with poor time synchronization are experienced, the" -" window can be increased from its default size of 3 permitted codes (one " -"previous code, the current code, the next code) to 17 permitted codes (the 8" -" previous codes, the current code, and the 8 next codes). This will permit " -"for a time skew of up to 4 minutes between client and server." -msgstr "" - -#: ../../configuration/system/login.rst:153 319caca8a70143cd86eb1868ffaa94d3 -msgid "The window size must be between 1 and 21." -msgstr "" - -#: ../../configuration/system/login.rst:156 dfaf1e368f67459c9b2485cc1c942e83 -msgid "RADIUS" -msgstr "" - -#: ../../configuration/system/login.rst:158 c5783c1b051249599b55487369256f86 -msgid "" -"In large deployments it is not reasonable to configure each user " -"individually on every system. VyOS supports using :abbr:`RADIUS (Remote " -"Authentication Dial-In User Service)` servers as backend for user " -"authentication." -msgstr "" - -#: ../../configuration/system/login.rst:163 0985b0b2e5504718b23b45423d78e57d -msgid "Configuration" -msgstr "" - -#: ../../configuration/system/login.rst:167 487e74037f5d4f059712abb871bce0c5 -msgid "" -"Specify the `<address>` of the RADIUS server user with the pre-shared-secret" -" given in `<secret>`. Multiple servers can be specified." -msgstr "" - -#: ../../configuration/system/login.rst:172 27b3d5d547a64702ae3eb864e49ed1c7 -msgid "" -"Configure the discrete port under which the RADIUS server can be reached. " -"This defaults to 1812." -msgstr "" - -#: ../../configuration/system/login.rst:177 e357c9d09b51460fb994c3a34f647886 -msgid "Setup the `<timeout>` in seconds when querying the RADIUS server." -msgstr "" - -#: ../../configuration/system/login.rst:181 e9db2d4f9841444d918843ffe013e229 -msgid "Temporary disable this RADIUS server. It won't be queried." -msgstr "" - -#: ../../configuration/system/login.rst:185 45ffedba28d7419797d68762989e06d7 -msgid "" -"RADIUS servers could be hardened by only allowing certain IP addresses to " -"connect. As of this the source address of each RADIUS query can be " -"configured. If this is not set, incoming connections to the RADIUS server " -"will use the nearest interface address pointing towards the server - making " -"it error prone on e.g. OSPF networks when a link fails and a backup route is" -" taken." -msgstr "" - -#: ../../configuration/system/login.rst:192 0a7ca7de94564f5d99945df1174b8859 -msgid "" -"If you want to have admin users to authenticate via RADIUS it is essential " -"to sent the ``Cisco-AV-Pair shell:priv-lvl=15`` attribute. Without the " -"attribute you will only get regular, non privilegued, system users." -msgstr "" - -#: ../../configuration/system/login.rst:198 29d8d0cdb5d64e7fa123a30598c54319 -msgid "Login Banner" -msgstr "" - -#: ../../configuration/system/login.rst:200 e7ed5db1573e427a8f44c30ed92c705c -msgid "" -"You are able to set post-login or pre-login banner messages to display " -"certain information for this system." -msgstr "" - -#: ../../configuration/system/login.rst:205 42784b9c968640ae9a9b20b797040d22 -msgid "" -"Configure `<message>` which is shown during SSH connect and before a user is" -" logged in." -msgstr "" - -#: ../../configuration/system/login.rst:210 962e36bdd2e14f5ca81797208b72a182 -msgid "" -"Configure `<message>` which is shown after user has logged in to the system." -msgstr "" - -#: ../../configuration/system/login.rst:212 06ed08be24a84547bc5e2a804053793f -msgid "" -"To create a new line in your login message you need to escape the new line " -"character by using ``\\\\n``." -msgstr "" - -#: ../../configuration/system/login.rst:217 48a65d4b9031424a9e896f6b2be13516 -msgid "Example" -msgstr "" - -#: ../../configuration/system/login.rst:219 e0d7f0462a6c48a19fb4b388c21ab17b -msgid "" -"In the following example, both `User1` and `User2` will be able to SSH into " -"VyOS as user ``vyos`` using their very own keys. `User1` is restricted to " -"only be able to connect from a single IP address. In addition if password " -"base login is wanted for the ``vyos`` user a 2FA/MFA keycode is required in " -"addition to the password." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/name-server.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/name-server.po deleted file mode 100644 index 8c05796b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/name-server.po +++ /dev/null @@ -1,96 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/name-server.rst:5 -#: e0b4822e4c61455390426c3d1c68406f -msgid "System DNS" -msgstr "" - -#: ../../configuration/system/name-server.rst:7 -#: 93cc10ea68b342e384d0f1a2ba2eb501 -msgid "" -"If you are configuring a VRF for management purposes, there is currently no " -"way to force system DNS traffic via a specific VRF." -msgstr "" - -#: ../../configuration/system/name-server.rst:10 -#: 16bbae452f5041f485ac973352fa11ec -msgid "This section describes configuring DNS on the system, namely:" -msgstr "" - -#: ../../configuration/system/name-server.rst:12 -#: ../../configuration/system/name-server.rst:17 -#: a699f5ed8eff44daba87c269463aa168 810262f877774788a0d39625cda06042 -msgid "DNS name servers" -msgstr "" - -#: ../../configuration/system/name-server.rst:13 -#: ../../configuration/system/name-server.rst:45 -#: 52bf9562deca4963817d504d5fd6a6eb 2014d61f206543bcac7c11683946b4cf -msgid "Domain search order" -msgstr "" - -#: ../../configuration/system/name-server.rst:21 -#: 77e91ec443c945dfa0343cf49ca026ea -msgid "" -"Use this command to specify a DNS server for the system to be used for DNS " -"lookups. More than one DNS server can be added, configuring one at a time. " -"Both IPv4 and IPv6 addresses are supported." -msgstr "" - -#: ../../configuration/system/name-server.rst:28 -#: ../../configuration/system/name-server.rst:63 -#: b2df2df4d5854cf4b44a7e7f66c5048a bc0399b78274434ea2da7ce353eec43f -msgid "Example" -msgstr "" - -#: ../../configuration/system/name-server.rst:30 -#: f9cc13badb9d436188a2329b489188b3 -msgid "" -"In this example, some *OpenNIC* servers are used, two IPv4 addresses and two" -" IPv6 addresses:" -msgstr "" - -#: ../../configuration/system/name-server.rst:47 -#: 58e61f80e53e41ca90fdcf96c1184bd2 -msgid "" -"In order for the system to use and complete unqualified host names, a list " -"can be defined which will be used for domain searches." -msgstr "" - -#: ../../configuration/system/name-server.rst:53 -#: 7261bd4c4fdd403db2e2271e9d9f8637 -msgid "" -"Use this command to define domains, one at a time, so that the system uses " -"them to complete unqualified host names. Maximum: 6 entries." -msgstr "" - -#: ../../configuration/system/name-server.rst:57 -#: b2b9d9b66c0c4a309f390981f81f7813 -msgid "" -"Domain names can include letters, numbers, hyphens and periods with a " -"maximum length of 253 characters." -msgstr "" - -#: ../../configuration/system/name-server.rst:65 -#: 8f253802863f49778024f1211a5c1f0f -msgid "" -"The system is configured to attempt domain completion in the following " -"order: vyos.io (first), vyos.net (second) and vyos.network (last):" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ntp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ntp.po deleted file mode 100644 index 45ee6cb0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/ntp.po +++ /dev/null @@ -1,137 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/ntp.rst:5 1d7b560fa43c47fd940043e0cdea97f1 -msgid "NTP" -msgstr "" - -#: ../../configuration/system/ntp.rst:7 913c116635fa4defadb10cc3dca493d0 -msgid "" -":abbr:`NTP (Network Time Protocol`) is a networking protocol for clock " -"synchronization between computer systems over packet-switched, variable-" -"latency data networks. In operation since before 1985, NTP is one of the " -"oldest Internet protocols in current use." -msgstr "" - -#: ../../configuration/system/ntp.rst:12 0f3bb585dce14118b59eee2cb9038de2 -msgid "" -"NTP is intended to synchronize all participating computers to within a few " -"milliseconds of :abbr:`UTC (Coordinated Universal Time)`. It uses the " -"intersection algorithm, a modified version of Marzullo's algorithm, to " -"select accurate time servers and is designed to mitigate the effects of " -"variable network latency. NTP can usually maintain time to within tens of " -"milliseconds over the public Internet, and can achieve better than one " -"millisecond accuracy in local area networks under ideal conditions. " -"Asymmetric routes and network congestion can cause errors of 100 ms or more." -msgstr "" - -#: ../../configuration/system/ntp.rst:21 6c135878ce0c4626a0dca07d41f2a086 -msgid "" -"The protocol is usually described in terms of a client-server model, but can" -" as easily be used in peer-to-peer relationships where both peers consider " -"the other to be a potential time source. Implementations send and receive " -"timestamps using :abbr:`UDP (User Datagram Protocol)` on port number 123." -msgstr "" - -#: ../../configuration/system/ntp.rst:26 7987360f438244e296f08f9fc6e3f420 -msgid "" -"NTP supplies a warning of any impending leap second adjustment, but no " -"information about local time zones or daylight saving time is transmitted." -msgstr "" - -#: ../../configuration/system/ntp.rst:29 1c048adddd7b4628ade8dcee66fb7c7f -msgid "" -"The current protocol is version 4 (NTPv4), which is a proposed standard as " -"documented in :rfc:`5905`. It is backward compatible with version 3, " -"specified in :rfc:`1305`." -msgstr "" - -#: ../../configuration/system/ntp.rst:34 f9d0f3602ca6401f8cac0a21fa6f9e0e -msgid "Configuration" -msgstr "" - -#: ../../configuration/system/ntp.rst:38 db8b893bf53e4128bfe73fef7464fbc7 -msgid "" -"Configure one or more servers for synchronisation. Server name can be either" -" an IP address or :abbr:`FQDN (Fully Qualified Domain Name)`." -msgstr "" - -#: ../../configuration/system/ntp.rst:41 02a59b915b8640238a0fa1add8eab746 -msgid "There are 3 default NTP server set. You are able to change them." -msgstr "" - -#: ../../configuration/system/ntp.rst:43 ad2429ecdfc64800aa1a693852a1cd27 -msgid "``0.pool.ntp.org``" -msgstr "" - -#: ../../configuration/system/ntp.rst:44 c7f5fa2b8d664e2d8f1204a791bee117 -msgid "``1.pool.ntp.org``" -msgstr "" - -#: ../../configuration/system/ntp.rst:45 a6f3b00e474e4fa394cd30e733e1d743 -msgid "``2.pool.ntp.org``" -msgstr "" - -#: ../../configuration/system/ntp.rst:49 f3ef12db95244cfc9ad9dcad31358c13 -msgid "Configure one or more attributes to the given NTP server." -msgstr "" - -#: ../../configuration/system/ntp.rst:51 6bd8eb0c1f5843e9bc0f0bd843bb1773 -msgid "" -"``noselect`` marks the server as unused, except for display purposes. The " -"server is discarded by the selection algorithm." -msgstr "" - -#: ../../configuration/system/ntp.rst:54 e6639e29e7b34dba8bc793d0886ec2cc -msgid "" -"``pool`` mobilizes persistent client mode association with a number of " -"remote servers." -msgstr "" - -#: ../../configuration/system/ntp.rst:57 5150e3bb41d343da875e96af2345d68e -msgid "``preempt`` a preemptable association is expendable." -msgstr "" - -#: ../../configuration/system/ntp.rst:59 eaf785a69cad4afc9fb57f41228397b4 -msgid "" -"``prefer`` marks the server as preferred. All other things being equal, this" -" host will be chosen for synchronization among a set of correctly operating " -"hosts." -msgstr "" - -#: ../../configuration/system/ntp.rst:65 e12c85bd835d45bc93f8f4f8d5648f7a -msgid "" -"NTP process will only listen on the specified IP address. You must specify " -"the `<address>` and optionally the permitted clients. Multiple listen " -"addresses can be configured." -msgstr "" - -#: ../../configuration/system/ntp.rst:71 ebc6f11bab924530a01aff1c36669244 -msgid "" -"List of networks or client addresses permitted to contact this NTP server." -msgstr "" - -#: ../../configuration/system/ntp.rst:73 ff5cabfec37e49c1847045456b137291 -msgid "Multiple networks can be configured." -msgstr "" - -#: ../../configuration/system/ntp.rst:77 102ee8db603a4921a34d719d76418666 -msgid "" -"Specify name of the :abbr:`VRF (Virtual Routing and Forwarding)` instance." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/option.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/option.po deleted file mode 100644 index da44112a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/option.po +++ /dev/null @@ -1,147 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/option.rst:5 179b450d28fb4032a2247e53223facab -msgid "Option" -msgstr "" - -#: ../../configuration/system/option.rst:7 d1a99ec5ca9745b3af57877d49f731cc -msgid "This chapter describe the possibilities of advanced system behavior." -msgstr "" - -#: ../../configuration/system/option.rst:11 9198a86c948f4be5a24d667f43e78806 -msgid "General" -msgstr "" - -#: ../../configuration/system/option.rst:15 6b8cf7d3cda94965b7ca966ce4226ccf -msgid "Action which will be run once the ctrl-alt-del keystroke is received." -msgstr "" - -#: ../../configuration/system/option.rst:19 c828e0abd2e14f78b8a68a950e392f8c -msgid "Automatically reboot system on kernel panic after 60 seconds." -msgstr "" - -#: ../../configuration/system/option.rst:23 ca1c5190e8364027bcf5dd67ee864653 -msgid "Play an audible beep to the system speaker when system is ready." -msgstr "" - -#: ../../configuration/system/option.rst:27 4fa443c30ef941a0bdea875db5001b49 -msgid "HTTP client" -msgstr "" - -#: ../../configuration/system/option.rst:31 458f46c7f6224723aa8ae8cdf58ec7a4 -msgid "" -"Several commands utilize cURL to initiate transfers. Configure the local " -"source IPv4/IPv6 address used for all cURL operations." -msgstr "" - -#: ../../configuration/system/option.rst:36 dc708380068544b39c2df55e6fb751fe -msgid "" -"Several commands utilize curl to initiate transfers. Configure the local " -"source interface used for all CURL operations." -msgstr "" - -#: ../../configuration/system/option.rst:39 01339b6cd22e484488cee9e8c26e9cb9 -msgid "" -"`source-address` and `source-interface` can not be used at the same time." -msgstr "" - -#: ../../configuration/system/option.rst:44 e11b0a746b2a43c7a8ada34dee366ef9 -msgid "Keyboard Layout" -msgstr "" - -#: ../../configuration/system/option.rst:46 4c82f05d61ec46b2b0d3817454e1bb93 -msgid "" -"When starting a VyOS live system (the installation CD) the configured " -"keyboard layout defaults to US. As this might not suite everyones use case " -"you can adjust the used keyboard layout on the system console." -msgstr "" - -#: ../../configuration/system/option.rst:52 eb729955d82e46c4a8e300a9ff240816 -msgid "Change system keyboard layout to given language." -msgstr "" - -#: ../../configuration/system/option.rst:54 92a2246266fc4ec2a14bc28a4245f250 -msgid "Defaults to ``us``." -msgstr "" - -#: ../../configuration/system/option.rst:56 52295a3502de4381958a17a556711b4c -msgid "" -"Changing the keymap only has an effect on the system console, using SSH or " -"Serial remote access to the device is not affected as the keyboard layout " -"here corresponds to your access system." -msgstr "" - -#: ../../configuration/system/option.rst:64 f0cb4db8c170419e8d7039a5c39460a5 -msgid "Performance" -msgstr "" - -#: ../../configuration/system/option.rst:66 6b527929906d49b8b5e422b3cad9cc8d -msgid "" -"As more and more routers run on Hypervisors, expecially with a :abbr:`NOS " -"(Network Operating System)` as VyOS, it makes fewer and fewer sense to use " -"static resource bindings like ``smp-affinity`` as present in VyOS 1.2 and " -"earlier to pin certain interrupt handlers to specific CPUs." -msgstr "" - -#: ../../configuration/system/option.rst:71 53e00593cc4f429c8ef4b501ef0c4bca -msgid "" -"We now utilize `tuned` for dynamic resource balancing based on profiles." -msgstr "" - -#: ../../configuration/system/option.rst:75 e104c1975764490d9163e75b4bbfc740 -msgid "" -"https://access.redhat.com/sites/default/files/attachments/201501-perf-brief-" -"low-latency-tuning-rhel7-v2.1.pdf" -msgstr "" - -#: ../../configuration/system/option.rst:81 b726dd0835ab4b0d8a3cc4be731e3138 -msgid "Configure one of the predefined system performance profiles." -msgstr "" - -#: ../../configuration/system/option.rst:83 6f06cc1426574ababcbe206066ce6584 -msgid "" -"``throughput``: A server profile focused on improving network throughput. " -"This profile favors performance over power savings by setting " -"``intel_pstate`` and ``max_perf_pct=100`` and increasing kernel network " -"buffer sizes." -msgstr "" - -#: ../../configuration/system/option.rst:88 f2e88ca4c4fb4f8cb30296328098866e -msgid "" -"It enables transparent huge pages, and uses cpupower to set the performance " -"cpufreq governor. It also sets ``kernel.sched_min_granularity_ns`` to 10 us," -" ``kernel.sched_wakeup_granularity_ns`` to 15 uss, and ``vm.dirty_ratio`` to" -" 40%." -msgstr "" - -#: ../../configuration/system/option.rst:93 fce0175dde7148a3b771d2b19727231c -msgid "" -"``latency``: A server profile focused on lowering network latency. This " -"profile favors performance over power savings by setting ``intel_pstate`` " -"and ``min_perf_pct=100``." -msgstr "" - -#: ../../configuration/system/option.rst:97 539857446d7a4504a42483d3446e4b36 -msgid "" -"It disables transparent huge pages, and automatic NUMA balancing. It also " -"uses cpupower to set the performance cpufreq governor, and requests a " -"cpu_dma_latency value of 1. It also sets busy_read and busy_poll times to 50" -" us, and tcp_fastopen to 3." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/proxy.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/proxy.po deleted file mode 100644 index 45010e9e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/proxy.po +++ /dev/null @@ -1,51 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/proxy.rst:5 e54a155dfb67486b99add64d73f57911 -msgid "System Proxy" -msgstr "" - -#: ../../configuration/system/proxy.rst:7 0d6c757d7f5c413799c78f3e0891c808 -msgid "" -"Some IT environments require the use of a proxy to connect to the Internet. " -"Without this configuration VyOS updates could not be installed directly by " -"using the :opcmd:`add system image` command (:ref:`update_vyos`)." -msgstr "" - -#: ../../configuration/system/proxy.rst:13 b332abdfc12e4562bc88f01259b81a8c -msgid "" -"Set proxy for all connections initiated by VyOS, including HTTP, HTTPS, and " -"FTP (anonymous ftp)." -msgstr "" - -#: ../../configuration/system/proxy.rst:18 6d480ac7a3ab440d877128a8bc9e8ea9 -msgid "Configure proxy port if it does not listen to the default port 80." -msgstr "" - -#: ../../configuration/system/proxy.rst:22 90b4951a87da4ce597f43ddda2cb6cab -msgid "" -"Some proxys require/support the \"basic\" HTTP authentication scheme as per " -":rfc:`7617`, thus a username can be configured." -msgstr "" - -#: ../../configuration/system/proxy.rst:27 865049e8439c4f9bbe19d88167d21b71 -msgid "" -"Some proxys require/support the \"basic\" HTTP authentication scheme as per " -":rfc:`7617`, thus a password can be configured." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/syslog.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/syslog.po deleted file mode 100644 index 19e40387..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/syslog.po +++ /dev/null @@ -1,683 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/syslog.rst:5 3b2234e3843042b1af9e2ecd22a30dff -msgid "Syslog" -msgstr "" - -#: ../../configuration/system/syslog.rst:7 21a7d5157f274c4eb5954960d2906dd0 -msgid "" -"Per default VyOSs has minimal syslog logging enabled which is stored and " -"rotated locally. Errors will be always logged to a local file, which " -"includes `local7` error messages, emergency messages will be sent to the " -"console, too." -msgstr "" - -#: ../../configuration/system/syslog.rst:11 79d90850c78d487389bea5e27352777c -msgid "To configure syslog, you need to switch into configuration mode." -msgstr "" - -#: ../../configuration/system/syslog.rst:14 db97e746c5be480b828184f12af222ea -msgid "Logging" -msgstr "" - -#: ../../configuration/system/syslog.rst:16 0d1a5a4beeb449edb5d26976f1355db0 -msgid "" -"Syslog supports logging to multiple targets, those targets could be a plain " -"file on your VyOS installation itself, a serial console or a remote syslog " -"server which is reached via :abbr:`IP (Internet Protocol)` UDP/TCP." -msgstr "" - -#: ../../configuration/system/syslog.rst:21 990cdf1a674f47a4aa4db4d506b6b5e9 -msgid "Console" -msgstr "" - -#: ../../configuration/system/syslog.rst:25 2c99532986fe4de99905a079e208a143 -msgid "" -"Log syslog messages to ``/dev/console``, for an explanation on " -":ref:`syslog_facilities` keywords and :ref:`syslog_severity_level` keywords " -"see tables below." -msgstr "" - -#: ../../configuration/system/syslog.rst:32 0de714611c3c4e0fbbe1273c18fc470f -msgid "Custom File" -msgstr "" - -#: ../../configuration/system/syslog.rst:36 89aa7a7c100f4f1a86830105282eb581 -msgid "" -"Log syslog messages to file specified via `<filename>`, for an explanation " -"on :ref:`syslog_facilities` keywords and :ref:`syslog_severity_level` " -"keywords see tables below." -msgstr "" - -#: ../../configuration/system/syslog.rst:42 1ac9f3aa87ff48e586679963e44c7605 -msgid "" -"Syslog will write `<size>` kilobytes into the file specified by " -"`<filename>`. After this limit has been reached, the custom file is " -"\"rotated\" by logrotate and a new custom file is created." -msgstr "" - -#: ../../configuration/system/syslog.rst:48 dac895694448422b8d110b13f820f654 -msgid "" -"Syslog uses logrotate to rotate logiles after a number of gives bytes. We " -"keep as many as `<number>` rotated file before they are deleted on the " -"system." -msgstr "" - -#: ../../configuration/system/syslog.rst:54 5595534ca4144d2d837540181e496bc4 -msgid "Remote Host" -msgstr "" - -#: ../../configuration/system/syslog.rst:56 0b5ed3bc3b4c423483853d7990d3be8f -msgid "" -"Logging to a remote host leaves the local logging configuration intact, it " -"can be configured in parallel to a custom file or console logging. You can " -"log to multiple hosts at the same time, using either TCP or UDP. The default" -" is sending the messages via port 514/UDP." -msgstr "" - -#: ../../configuration/system/syslog.rst:64 43163fed55684bb1a1a2ce389570f755 -msgid "" -"Log syslog messages to remote host specified by `<address>`. The address can" -" be specified by either FQDN or IP address. For an explanation on " -":ref:`syslog_facilities` keywords and :ref:`syslog_severity_level` keywords " -"see tables below." -msgstr "" - -#: ../../configuration/system/syslog.rst:73 1c687427e96948b5b2a1b09403bbf8c0 -msgid "" -"Configure protocol used for communication to remote syslog host. This can be" -" either UDP or TCP." -msgstr "" - -#: ../../configuration/system/syslog.rst:78 39cd891f1a9148739721e40c59daf027 -msgid "Local User Account" -msgstr "" - -#: ../../configuration/system/syslog.rst:82 68112e94814843b591f7f039b916031b -msgid "" -"If logging to a local user account is configured, all defined log messages " -"are display on the console if the local user is logged in, if the user is " -"not logged in, no messages are being displayed. For an explanation on " -":ref:`syslog_facilities` keywords and :ref:`syslog_severity_level` keywords " -"see tables below." -msgstr "" - -#: ../../configuration/system/syslog.rst:91 ed29ddd5b6564b82a0ff1fdeba821556 -msgid "Facilities" -msgstr "" - -#: ../../configuration/system/syslog.rst:93 41456868ce824f5b877db8c7c991ff49 -msgid "" -"List of facilities used by syslog. Most facilities names are self " -"explanatory. Facilities local0 - local7 common usage is f.e. as network logs" -" facilities for nodes and network equipment. Generally it depends on the " -"situation how to classify logs and put them to facilities. See facilities " -"more as a tool rather than a directive to follow." -msgstr "" - -#: ../../configuration/system/syslog.rst:99 241dfa31668b4653b9c6046bad37da41 -msgid "Facilities can be adjusted to meet the needs of the user:" -msgstr "" - -#: ../../configuration/system/syslog.rst:102 f91480de77ad447d972072256511f436 -msgid "Facility Code" -msgstr "" - -#: ../../configuration/system/syslog.rst:102 -#: ../../configuration/system/syslog.rst:162 d885c5e29ff14a47b4a75627cf3165fd -#: 5750df5f312e4bf4a8290419394790f7 -msgid "Keyword" -msgstr "" - -#: ../../configuration/system/syslog.rst:102 -#: ../../configuration/system/syslog.rst:162 ef8af38f8f0648869f9034a9978892be -#: 6c39898ff34a4c478074dfee6ea0db8f -msgid "Description" -msgstr "" - -#: ../../configuration/system/syslog.rst:105 -#: ../../configuration/system/syslog.rst:164 -#: ../../configuration/system/syslog.rst:214 78fd7376f5144fab91d55d7dec7fa5d6 -#: 05b71697f1b4496ea52772bf0b645d27 56de5bb8917d42469d98fdf57725d8c4 -msgid "all" -msgstr "" - -#: ../../configuration/system/syslog.rst:105 0f6ad8f81ee84ae8833123df3a2890ea -msgid "All facilities" -msgstr "" - -#: ../../configuration/system/syslog.rst:107 -#: ../../configuration/system/syslog.rst:166 b5c9114296324154a839777d4c629cf2 -#: 1a0241e6ad09494dafe56525c046d939 -msgid "0" -msgstr "" - -#: ../../configuration/system/syslog.rst:107 9833ae8d7f014506863f7c935a286972 -msgid "kern" -msgstr "" - -#: ../../configuration/system/syslog.rst:107 c7ad84733ebf4971879c7bb2697486e7 -msgid "Kernel messages" -msgstr "" - -#: ../../configuration/system/syslog.rst:109 -#: ../../configuration/system/syslog.rst:168 e2695440e6e247b49a26862a1c6b118d -#: 614cc83762b148cc90e5465ef2e6463c -msgid "1" -msgstr "" - -#: ../../configuration/system/syslog.rst:109 f74cda16ae414f05b45322f08eff2ca1 -msgid "user" -msgstr "" - -#: ../../configuration/system/syslog.rst:109 169e97cf92d74e89bc8fde465fa98815 -msgid "User-level messages" -msgstr "" - -#: ../../configuration/system/syslog.rst:111 -#: ../../configuration/system/syslog.rst:173 bf4639851f3d4f0db9b385ac54e5101e -#: 0b68bc0365834eaba154b2133d70ae64 -msgid "2" -msgstr "" - -#: ../../configuration/system/syslog.rst:111 90a5ae12b0574641b71612ead60c1db4 -msgid "mail" -msgstr "" - -#: ../../configuration/system/syslog.rst:111 0705f8aa973b4ecc9f28d06d7fb57aac -msgid "Mail system" -msgstr "" - -#: ../../configuration/system/syslog.rst:113 -#: ../../configuration/system/syslog.rst:176 04182c78dc2c4e78bf3f45ccc588906b -#: 59df20bcefc84e33a8888bf7568e8cda -msgid "3" -msgstr "" - -#: ../../configuration/system/syslog.rst:113 5c5fb46a8b354b238ba3adcb8d42aba8 -msgid "daemon" -msgstr "" - -#: ../../configuration/system/syslog.rst:113 7e2071da3f1243eb8ff529241eb75e8a -msgid "System daemons" -msgstr "" - -#: ../../configuration/system/syslog.rst:115 -#: ../../configuration/system/syslog.rst:178 a334bfd11561492796a463f2fbbe79a8 -#: 9456ef626fcb4285a4d9bf62e2e7bf62 -msgid "4" -msgstr "" - -#: ../../configuration/system/syslog.rst:115 672177a3af4f4e758b7d0da1975af26c -msgid "auth" -msgstr "" - -#: ../../configuration/system/syslog.rst:115 -#: ../../configuration/system/syslog.rst:127 22a750a71f6b427996a154386c5e97d8 -#: 2f95354b5daa46999d3aa1d23be041d7 -msgid "Security/authentication messages" -msgstr "" - -#: ../../configuration/system/syslog.rst:117 -#: ../../configuration/system/syslog.rst:180 f9cb093cfbfa43df9ad37049bcb4a764 -#: c42b36cffb8c44bfaffadd805b4ce918 -msgid "5" -msgstr "" - -#: ../../configuration/system/syslog.rst:117 c65029a1ccde444babdfe80da5935d11 -msgid "syslog" -msgstr "" - -#: ../../configuration/system/syslog.rst:117 ad10c6c3edd748c794ef21113eb893a4 -msgid "Messages generated internally by syslogd" -msgstr "" - -#: ../../configuration/system/syslog.rst:119 -#: ../../configuration/system/syslog.rst:184 fe42474bbb7647b9b12c81fc0178f935 -#: ca5a35fee7914721834c3e0794c981a6 -msgid "6" -msgstr "" - -#: ../../configuration/system/syslog.rst:119 9dfbb40795ef4ee4b3349c77711b2511 -msgid "lpr" -msgstr "" - -#: ../../configuration/system/syslog.rst:119 6a088890ccf94d45b3b1c139bf8034a3 -msgid "Line printer subsystem" -msgstr "" - -#: ../../configuration/system/syslog.rst:121 -#: ../../configuration/system/syslog.rst:186 dfdec034a895471eb63f80464feaaf1a -#: 96606fc63e2e4117b1683358bb1cecae -msgid "7" -msgstr "" - -#: ../../configuration/system/syslog.rst:121 b3020ce1fb6647c6866b14d712d249a3 -msgid "news" -msgstr "" - -#: ../../configuration/system/syslog.rst:121 f467b9c559304f74a6eaf81349120eeb -msgid "Network news subsystem" -msgstr "" - -#: ../../configuration/system/syslog.rst:123 e52b7e6e0b5b4e1e865dce3d525c8a28 -msgid "8" -msgstr "" - -#: ../../configuration/system/syslog.rst:123 3bac4d983dbb4be8aa81d204f344b4c2 -msgid "uucp" -msgstr "" - -#: ../../configuration/system/syslog.rst:123 d30572fc6fe247b2845ab205224f9e95 -msgid "UUCP subsystem" -msgstr "" - -#: ../../configuration/system/syslog.rst:125 3eba8d2a6bad449fa31baac0c97f83a8 -msgid "9" -msgstr "" - -#: ../../configuration/system/syslog.rst:125 2cc71637595c4575bf3a54455c20d7f8 -msgid "cron" -msgstr "" - -#: ../../configuration/system/syslog.rst:125 ef25a67bcaf442a78cb6d7da87b78fd4 -msgid "Clock daemon" -msgstr "" - -#: ../../configuration/system/syslog.rst:127 b18b7d46d225450a96a04d28ecb7c62b -msgid "10" -msgstr "" - -#: ../../configuration/system/syslog.rst:127 c936f2932e1444a8bd6ba07968b71fb2 -msgid "security" -msgstr "" - -#: ../../configuration/system/syslog.rst:129 1f7826eaab604111ac04261af55c22c2 -msgid "11" -msgstr "" - -#: ../../configuration/system/syslog.rst:129 c595e9390dee45e2a2b45b6e0b5dc940 -msgid "ftp" -msgstr "" - -#: ../../configuration/system/syslog.rst:129 c94d7c664a5842a5b6dfff0f6b6c39ca -msgid "FTP daemon" -msgstr "" - -#: ../../configuration/system/syslog.rst:131 f46587d6c6914bbca136176bd3ad0d90 -msgid "12" -msgstr "" - -#: ../../configuration/system/syslog.rst:131 c732eb80666e4a92a0a6a9471222faa1 -msgid "ntp" -msgstr "" - -#: ../../configuration/system/syslog.rst:131 0802ac485eb84cdca8a8f3fb5f6f621d -msgid "NTP subsystem" -msgstr "" - -#: ../../configuration/system/syslog.rst:133 bd3dac6720a24437bcece5f0d59b2dbe -msgid "13" -msgstr "" - -#: ../../configuration/system/syslog.rst:133 0fd42a03d17e4824a9299a18564540b9 -msgid "logaudit" -msgstr "" - -#: ../../configuration/system/syslog.rst:133 8973504e6ce04f6abe8eaa8fc7ef34ec -msgid "Log audit" -msgstr "" - -#: ../../configuration/system/syslog.rst:135 981f4f4b9c764e1a8179aaef4fb406a4 -msgid "14" -msgstr "" - -#: ../../configuration/system/syslog.rst:135 904bba252d0243abb665918ad8276c53 -msgid "logalert" -msgstr "" - -#: ../../configuration/system/syslog.rst:135 c1d709a5ecd2451da7c051b213891a3a -msgid "Log alert" -msgstr "" - -#: ../../configuration/system/syslog.rst:137 bbfc163be5094330be6cd8ed0122f6d0 -msgid "15" -msgstr "" - -#: ../../configuration/system/syslog.rst:137 1e2624c0edea4c35812d2916325e64d4 -msgid "clock" -msgstr "" - -#: ../../configuration/system/syslog.rst:137 ba5ba71b6b3d4f78b094726a2f82c27d -msgid "clock daemon (note 2)" -msgstr "" - -#: ../../configuration/system/syslog.rst:139 13eaaec544db4a029874119a7f31071f -msgid "16" -msgstr "" - -#: ../../configuration/system/syslog.rst:139 f2559bbae64a4baea5a4e159d3ce588a -msgid "local0" -msgstr "" - -#: ../../configuration/system/syslog.rst:139 18173961a05f42afb7432c773a69798e -msgid "local use 0 (local0)" -msgstr "" - -#: ../../configuration/system/syslog.rst:141 cb6fdc1f8b1a4dfc940f62d95fa12bc6 -msgid "17" -msgstr "" - -#: ../../configuration/system/syslog.rst:141 47235f562a194316bc60dc8780c60323 -msgid "local1" -msgstr "" - -#: ../../configuration/system/syslog.rst:141 3868848d850f4abf98ad57a62320807f -msgid "local use 1 (local1)" -msgstr "" - -#: ../../configuration/system/syslog.rst:143 62793e837af6469785d8efb42d18b2f7 -msgid "18" -msgstr "" - -#: ../../configuration/system/syslog.rst:143 87eba6d988e34a42977a93125150b2ff -msgid "local2" -msgstr "" - -#: ../../configuration/system/syslog.rst:143 a75cfd4a36b145018e9d03f2e718c84a -msgid "local use 2 (local2)" -msgstr "" - -#: ../../configuration/system/syslog.rst:145 906c43c1846b4957b0d1d31a3292dfba -msgid "19" -msgstr "" - -#: ../../configuration/system/syslog.rst:145 0b5d9bacde1347e2b76b72866271b119 -msgid "local3" -msgstr "" - -#: ../../configuration/system/syslog.rst:145 8435b36378f646fea9fb135b2ddfbf9d -msgid "local use 3 (local3)" -msgstr "" - -#: ../../configuration/system/syslog.rst:147 fdf1dbc1fff34d2a90c37c10edcb89a6 -msgid "20" -msgstr "" - -#: ../../configuration/system/syslog.rst:147 0f8c78ba3ec84534bfaad5f2d1f2347e -msgid "local4" -msgstr "" - -#: ../../configuration/system/syslog.rst:147 308a6df8700444f2bf746e071d1b2e0a -msgid "local use 4 (local4)" -msgstr "" - -#: ../../configuration/system/syslog.rst:149 075720037aef409d919960aba90c15aa -msgid "21" -msgstr "" - -#: ../../configuration/system/syslog.rst:149 cce19586ed9646c8b365c0789cb03cd7 -msgid "local5" -msgstr "" - -#: ../../configuration/system/syslog.rst:149 5845a876d7094e4e92d57db507ab28a3 -msgid "local use 5 (local5)" -msgstr "" - -#: ../../configuration/system/syslog.rst:151 e43efcaab513489f86d614746d61bbe4 -msgid "22" -msgstr "" - -#: ../../configuration/system/syslog.rst:151 8a39f3dde87644baab694a8ad41aafed -msgid "local6" -msgstr "" - -#: ../../configuration/system/syslog.rst:151 f8587fd586d7438487a623f63e40a228 -msgid "use 6 (local6)" -msgstr "" - -#: ../../configuration/system/syslog.rst:153 7002e1a1c502417ca51f6d3a54ab55e2 -msgid "23" -msgstr "" - -#: ../../configuration/system/syslog.rst:153 4c9186f224054870a48db472de434aac -msgid "local7" -msgstr "" - -#: ../../configuration/system/syslog.rst:153 eb362ea6b41b4992b5ee061129cf6e30 -msgid "local use 7 (local7)" -msgstr "" - -#: ../../configuration/system/syslog.rst:159 584d4bad495a45beb7ff18b1aa1f6864 -msgid "Severity Level" -msgstr "" - -#: ../../configuration/system/syslog.rst:162 931747bd0c57480c904b77b7b4a7bd08 -msgid "Value" -msgstr "" - -#: ../../configuration/system/syslog.rst:162 43927a8efef640279518be3fe53c52a0 -msgid "Severity" -msgstr "" - -#: ../../configuration/system/syslog.rst:164 414dd4bf853d4c0fb5faa9277a6f4aa9 -msgid "Log everything" -msgstr "" - -#: ../../configuration/system/syslog.rst:166 e437d6dc5c48464fafce2921a8524496 -msgid "Emergency" -msgstr "" - -#: ../../configuration/system/syslog.rst:166 9d84ba94a40a4658af7b2261873f4e7a -msgid "emerg" -msgstr "" - -#: ../../configuration/system/syslog.rst:166 80a13bb5f0d3475a97c049e130d526cb -msgid "System is unusable - a panic condition" -msgstr "" - -#: ../../configuration/system/syslog.rst:168 9e583e9d8abd4a00b151a8c8a8783c58 -msgid "Alert" -msgstr "" - -#: ../../configuration/system/syslog.rst:168 be8f4b669d27403194758da9c3410e4e -msgid "alert" -msgstr "" - -#: ../../configuration/system/syslog.rst:168 f48af2e1c23c4f7db0f8bffdaac57a99 -msgid "" -"Action must be taken immediately - A condition that should be corrected " -"immediately, such as a corrupted system database." -msgstr "" - -#: ../../configuration/system/syslog.rst:173 92da0f095f684ccca07d235c1fb0dc5e -msgid "Critical" -msgstr "" - -#: ../../configuration/system/syslog.rst:173 166464a1e64f45d4ab64c19122deed66 -msgid "crit" -msgstr "" - -#: ../../configuration/system/syslog.rst:173 a9a88e61e93f41a396fed1747bfa49a6 -msgid "Critical conditions - e.g. hard drive errors." -msgstr "" - -#: ../../configuration/system/syslog.rst:176 2c09e4ca1cb94fefaa49951afa6c581d -msgid "Error" -msgstr "" - -#: ../../configuration/system/syslog.rst:176 aaea04bb05ee483cb83e85fe91aec6c4 -msgid "err" -msgstr "" - -#: ../../configuration/system/syslog.rst:176 207e3418c1cd400b878493c02840b420 -msgid "Error conditions" -msgstr "" - -#: ../../configuration/system/syslog.rst:178 900492c5796f471297dda17e0090b4b5 -msgid "Warning" -msgstr "" - -#: ../../configuration/system/syslog.rst:178 b8f9d25e89fa45d593bbf1fa19478d19 -msgid "warning" -msgstr "" - -#: ../../configuration/system/syslog.rst:178 10087f064c95447593bec2d72f66593c -msgid "Warning conditions" -msgstr "" - -#: ../../configuration/system/syslog.rst:180 724b271ce7e54b4fa947076c92590284 -msgid "Notice" -msgstr "" - -#: ../../configuration/system/syslog.rst:180 ce0cf35f59b948e2ad2875b22c1541f8 -msgid "notice" -msgstr "" - -#: ../../configuration/system/syslog.rst:180 4081bf0eeb7b476ba6e4389652e040da -msgid "" -"Normal but significant conditions - conditions that are not error " -"conditions, but that may require special handling." -msgstr "" - -#: ../../configuration/system/syslog.rst:184 5cf7de0177bd48f2aa5fb225447c7172 -msgid "Informational" -msgstr "" - -#: ../../configuration/system/syslog.rst:184 2b66b9be72b74953a9fb2d7975d8daf8 -msgid "info" -msgstr "" - -#: ../../configuration/system/syslog.rst:184 f363748cc5e744558e355a084727f2f1 -msgid "Informational messages" -msgstr "" - -#: ../../configuration/system/syslog.rst:186 72b10578cbc64cd09b111bfa83deb10a -msgid "Debug" -msgstr "" - -#: ../../configuration/system/syslog.rst:186 453a1e69b26b435abdd9c97140460204 -msgid "debug" -msgstr "" - -#: ../../configuration/system/syslog.rst:186 785211b54db544ddb90bc36efe017786 -msgid "" -"Debug-level messages - Messages that contain information normally of use " -"only when debugging a program." -msgstr "" - -#: ../../configuration/system/syslog.rst:193 2c6dc99cd867415cad134b4fb69dd475 -msgid "Display Logs" -msgstr "" - -#: ../../configuration/system/syslog.rst:197 33c18d3a2ff04c7db53eab0bcc6cadab -msgid "" -"Display log files of given category on the console. Use tab completion to " -"get a list of available categories. Thos categories could be: all, " -"authorization, cluster, conntrack-sync, dhcp, directory, dns, file, " -"firewall, https, image lldp, nat, openvpn, snmp, tail, vpn, vrrp" -msgstr "" - -#: ../../configuration/system/syslog.rst:202 26e9f773e31642dfaa47fd3923fe24dc -msgid "If no option is specified, this defaults to `all`." -msgstr "" - -#: ../../configuration/system/syslog.rst:207 091bcd3025fa4e8f988d025bfa5678fe -msgid "" -"Log messages from a specified image can be displayed on the console. Details" -" of allowed parameters:" -msgstr "" - -#: ../../configuration/system/syslog.rst:215 3513930bbf254959a7b84b344fb6d29a -msgid "Display contents of all master log files of the specified image" -msgstr "" - -#: ../../configuration/system/syslog.rst:216 95ffb728c29c4f08bd11fbaa9fd95626 -msgid "authorization" -msgstr "" - -#: ../../configuration/system/syslog.rst:217 c823d33e9386426cab3f3df36633e572 -msgid "Display all authorization attempts of the specified image" -msgstr "" - -#: ../../configuration/system/syslog.rst:218 e8ae6c623458454c84022859449c9c67 -msgid "directory" -msgstr "" - -#: ../../configuration/system/syslog.rst:219 033178fccaf340a0a13aa347627f3748 -msgid "Display list of all user-defined log files of the specified image" -msgstr "" - -#: ../../configuration/system/syslog.rst:220 d7d64d86d551483e84783ec076057e6e -msgid "file <file name>" -msgstr "" - -#: ../../configuration/system/syslog.rst:221 0c10e7108cf64f16af967e3d4224b932 -msgid "" -"Display contents of a specified user-defined log file of the specified image" -msgstr "" - -#: ../../configuration/system/syslog.rst:223 3099e5c6ed72414084569761712aec97 -msgid "tail" -msgstr "" - -#: ../../configuration/system/syslog.rst:224 72579a558464439baca5ce5ea9ff650e -msgid "Display last lines of the system log of the specified image" -msgstr "" - -#: ../../configuration/system/syslog.rst:225 bfdbe69fec624537b99432460e8abb7a -msgid "<lines>" -msgstr "" - -#: ../../configuration/system/syslog.rst:226 56a1323d236b4199842ee53876e015a8 -msgid "Number of lines to be displayed, default 10" -msgstr "" - -#: ../../configuration/system/syslog.rst:228 1341799746144b0b8f80e75518d02519 -msgid "" -"When no options/parameters are used, the contents of the main syslog file " -"are displayed." -msgstr "" - -#: ../../configuration/system/syslog.rst:231 79d1e44fa48740b39bd54165da05b3cb -msgid "" -"Use ``show log | strip-private`` if you want to hide private data when " -"sharing your logs." -msgstr "" - -#: ../../configuration/system/syslog.rst:235 21139e7b6eb14c80aa7514e282b6be87 -msgid "Delete Logs" -msgstr "" - -#: ../../configuration/system/syslog.rst:239 e6dc5e5b752b407daba191da90d25719 -msgid "" -"Deletes the specified user-defined file <text> in the /var/log/user " -"directory" -msgstr "" - -#: ../../configuration/system/syslog.rst:241 7b59f4a0f5e34cd998512c41b0f93b02 -msgid "" -"Note that deleting the log file does not stop the system from logging " -"events. If you use this command while the system is logging events, old log " -"events will be deleted, but events after the delete operation will be " -"recorded in the new file. To delete the file altogether, first delete " -"logging to the file using system syslog :ref:`custom-file` command, and then" -" delete the file." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/task-scheduler.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/task-scheduler.po deleted file mode 100644 index aba77170..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/task-scheduler.po +++ /dev/null @@ -1,89 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/task-scheduler.rst:5 -#: 48a7214f6c974ec98cc6523422e3bcec -msgid "Task Scheduler" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:7 -#: e55f58f4c9ad4942bb2cddf3ceed05d7 -msgid "" -"The task scheduler allows you to execute tasks on a given schedule. It makes" -" use of UNIX cron_." -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:10 -#: 00f286a53d854932809ddffec87ab1f1 -msgid "" -"All scripts excecuted this way are executed as root user - this may be " -"dangerous. Together with :ref:`command-scripting` this can be used for " -"automating (re-)configuration." -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:16 -#: efb6dfff08b64eda942a257f98c89ec2 -msgid "" -"Specify the time interval when `<task>` should be executed. The interval is " -"specified as number with one of the following suffixes:" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:19 -#: f97fbe70cd104cdc8e3e532b47a3c60f -msgid "``none`` - Execution interval in minutes" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:20 -#: 51e3141e55384b2caf6e7fc9bd9fec91 -msgid "``m`` - Execution interval in minutes" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:21 -#: da673360cb2741ac8d785c80eff65371 -msgid "``h`` - Execution interval in hours" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:22 -#: 4d08363e323e41879790f786eac8f2dc -msgid "``d`` - Execution interval in days" -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:24 -#: 009c5f8eb34a486ba620109c19483fdd -msgid "If suffix is omitted, minutes are implied." -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:28 -#: 35f573981f3247d2bb0dbe2476785169 -msgid "" -"Set execution time in common cron_ time format. A cron `<spec>` of ``30 */6 " -"* * *`` would execute the `<task>` at minute 30 past every 6th hour." -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:33 -#: 903d5dc5200b419db49e015ed26e3828 -msgid "" -"Specify absolute `<path>` to script which will be run when `<task>` is " -"executed." -msgstr "" - -#: ../../configuration/system/task-scheduler.rst:38 -#: 426d25ebcec04352a1c9e985daa6e938 -msgid "Arguments which will be passed to the executable." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/time-zone.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/system/time-zone.po deleted file mode 100644 index b2961d43..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/system/time-zone.po +++ /dev/null @@ -1,44 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/system/time-zone.rst:5 0412ec66649c4806a6601ff25167a2bd -msgid "Time Zone" -msgstr "" - -#: ../../configuration/system/time-zone.rst:7 fdf0576fbfed4ea690d6b092ecfc9709 -msgid "" -"Time Zone setting is very important as e.g all your logfile entries will be " -"based on the configured zone. Without proper time zone configuration it will" -" be very difficult to compare logfiles from different systems." -msgstr "" - -#: ../../configuration/system/time-zone.rst:13 -#: 040d174b510845249672c01a5e7bee86 -msgid "" -"Specify the systems `<timezone>` as the Region/Location that best defines " -"your location. For example, specifying US/Pacific sets the time zone to US " -"Pacific time." -msgstr "" - -#: ../../configuration/system/time-zone.rst:17 -#: 5860339ac6f748e7b751c9ede5677e4e -msgid "" -"Command completion can be used to list available time zones. The adjustment " -"for daylight time will take place automatically based on the time of year." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/trafficpolicy/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/trafficpolicy/index.po deleted file mode 100644 index 8335f3ed..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/trafficpolicy/index.po +++ /dev/null @@ -1,1778 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/trafficpolicy/index.rst:5 -#: 187b3bb14fe0419cbcad6fa1ebf19b7a -msgid "Traffic Policy" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:10 -#: ced0ff17281c4c8b96f858baefee06c1 -msgid "QoS" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:12 -#: 2038d744215e415fa4c15e9d5980b1b7 -msgid "" -"The generic name of Quality of Service or Traffic Control involves things " -"like shaping traffic, scheduling or dropping packets, which are the kind of " -"things you may want to play with when you have, for instance, a bandwidth " -"bottleneck in a link and you want to somehow prioritize some type of traffic" -" over another." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:18 -#: e0114d43f0cd4a1f91ff0a581d3f2797 -msgid "" -"tc_ is a powerful tool for Traffic Control found at the Linux kernel. " -"However, its configuration is often considered a cumbersome task. " -"Fortunately, VyOS eases the job through its CLI, while using ``tc`` as " -"backend." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:25 -#: edb2fce5292a4b649dd7620395b47ed3 -msgid "How to make it work" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:27 -#: ebc9a418dd1b4bd291418c226e752535 -msgid "" -"In order to have VyOS Traffic Control working you need to follow 2 steps:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:30 -#: 6bea14563acb4cb1a1a25c4ad8df21b4 -msgid "**Create a traffic policy**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:32 -#: 218c386199794550a85bdea7235a26c5 -msgid "**Apply the traffic policy to an interface ingress or egress**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:35 -#: 70c92c3967d04585a9f2ce06b6a047fb -msgid "" -"But before learning to configure your policy, we will warn you about the " -"different units you can use and also show you what *classes* are and how " -"they work, as some policies may require you to configure them." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:42 -#: aa7ffadd0cab43d2956864d799593695 -msgid "Units" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:44 -#: dbd53c94e8424d34b2afa8e7cb5a977c -msgid "" -"When configuring your traffic policy, you will have to set data rate values," -" watch out the units you are managing, it is easy to get confused with the " -"different prefixes and suffixes you can use. VyOS will always show you the " -"different units you can use." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:50 -#: 6a446e0bcff34a3e9cca2c0675054beb -msgid "Prefixes" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:52 -#: 6cf9fb29b450420fbd73409559924d43 -msgid "They can be **decimal** prefixes." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:66 -#: e19ffdfab2e74d6ab99fc4308b33f91d -msgid "Or **binary** prefixes." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:82 -#: 44857022bc50421bbc4f7cead7b7a5a5 -msgid "Suffixes" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:84 -#: 39ce8577a6b341ceac29e9b20f22c08c -msgid "A *bit* is written as **bit**," -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:93 -#: a651386a75cb4c46852c4f2c5f3c636d -msgid "while a *byte* is written as a single **b**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:107 -#: 8589badcaa75421e83c242230de7dab2 -msgid "Classes" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:109 -#: 680cd599c43c4204ad93b967d2348757 -msgid "" -"In the :ref:`creating_a_traffic_policy` section you will see that some of " -"the policies use *classes*. Those policies let you distribute traffic into " -"different classes according to different parameters you can choose. So, a " -"class is just a specific type of traffic you select." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:114 -#: a6844386e265447899b0017b5acdef5e -msgid "" -"The ultimate goal of classifying traffic is to give each class a different " -"treatment." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:119 -#: 1a424286543e41afafa38d2118dedb76 -msgid "Matching traffic" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:121 -#: 91b5e7df6eeb4628b04a4d10c7849d05 -msgid "" -"In order to define which traffic goes into which class, you define filters " -"(that is, the matching criteria). Packets go through these matching rules " -"(as in the rules of a firewall) and, if a packet matches the filter, it is " -"assigned to that class." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:126 -#: 226f1dcfbf3642b3860afc99c278b5ee -msgid "" -"In VyOS, a class is identified by a number you can choose when configuring " -"it." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:130 -#: 2407e7a84d614d50a76651b241548ebf -msgid "" -"The meaning of the Class ID is not the same for every type of policy. " -"Normally policies just need a meaningless number to identify a class (Class " -"ID), but that does not apply to every policy. The the number of a class in a" -" Priority Queue it does not only identify it, it also defines its priority." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:142 -#: b3f6d389a0784e6c9a5ffeda87af7e90 -msgid "" -"In the command above, we set the type of policy we are going to work with " -"and the name we choose for it; a class (so that we can differentiate some " -"traffic) and an identifiable number for that class; then we configure a " -"matching rule (or filter) and a name for it." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:147 -#: 1f75ab93e65e4ceaa912e11fea11f5a9 -msgid "A class can have multiple match filters:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:154 -#: df2e26e4f7b3440da44f14da921c7fee -msgid "" -"A match filter can contain multiple criteria and will match traffic if all " -"those criteria are true." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:157 -#: 088b7eaee33d4f188740e071a5cd2e1c -msgid "For example:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:164 -#: 83df0a1677d34f6e869a0552220aa740 -msgid "This will match TCP traffic with source port 80." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:166 -#: 610fc9c98ff040d08c80d6d2bc0af365 -msgid "" -"There are many parameters you will be able to use in order to match the " -"traffic you want for a class:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:169 -#: 622efa2256154651af747d8319fc3d36 -msgid "**Ethernet (protocol, destination address or source address)**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:170 -#: f547fd9d1e234259a41a79730aeacd21 -msgid "**Interface name**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:171 -#: 598c40faa1e242c386066465746fc63d -msgid "" -"**IPv4 (DSCP value, maximum packet length, protocol, source address,** " -"**destination address, source port, destination port or TCP flags)**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:173 -#: 14d6849328d645019c0961efb98ef54f -msgid "" -"**IPv6 (DSCP value, maximum payload length, protocol, source address,** " -"**destination address, source port, destination port or TCP flags)**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:175 -#: 7a9cc4593fed4c2ea82c4657de3d5d1c -msgid "**Firewall mark**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:176 -#: d89943f371604f1882ecc7975305b7c3 -msgid "**VLAN ID**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:178 -#: edc41e53e6dd43afb7d58011aaa0b1f9 -msgid "" -"When configuring your filter, you can use the ``Tab`` key to see the many " -"different parameters you can configure." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:196 -#: b77fd857b1b144aa98dc37f78b626df7 -msgid "" -"As shown in the example above, one of the possibilities to match packets is " -"based on marks done by the firewall, `that can give you a great deal of " -"flexibility`_." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:200 -#: 224b64d2460b43ca97a4041153f773fe -msgid "You can also write a description for a filter:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:208 -#: d87d05f73763466a8741506c9ac0d248 -msgid "" -"An IPv4 TCP filter will only match packets with an IPv4 header length of 20 " -"bytes (which is the majority of IPv4 packets anyway)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:212 -#: c19d116c61f8491085eef940dbbaa01a -msgid "" -"IPv6 TCP filters will only match IPv6 packets with no header extension, see " -"https://en.wikipedia.org/wiki/IPv6_packet#Extension_headers" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:217 -#: ecfa44dfc8114c48971843ffcae37397 -msgid "Default" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:219 -#: 7493dd73b91e4db1b98f92d39108bb5b -msgid "" -"Often you will also have to configure your *default* traffic in the same way" -" you do with a class. *Default* can be considered a class as it behaves like" -" that. It contains any traffic that did not match any of the defined " -"classes, so it is like an open class, a class without matching filters." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:227 -#: 97765e293140464182426585f7af1f7a -msgid "Class treatment" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:229 -#: 6864dfa3282a430292b1fee3526ee7f8 -msgid "" -"Once a class has a filter configured, you will also have to define what you " -"want to do with the traffic of that class, what specific Traffic-Control " -"treatment you want to give it. You will have different possibilities " -"depending on the Traffic Policy you are configuring." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:254 -#: a9acd81de51b46e3bc5ec0b3bb8c21ba -msgid "" -"For instance, with :code:`set traffic-policy shaper MY-SHAPER class 30 set-" -"dscp EF` you would be modifying the DSCP field value of packets in that " -"class to Expedite Forwarding." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:259 -#: 1c59e42db3de491aabe33cf86328d171 -msgid "DSCP values as per :rfc:`2474` and :rfc:`4595`:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:262 -#: 0378928b2a1e4e4c95edfef87e4dfd7f -msgid "Binary value" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:262 -#: 87375a2d8698487c8bc5b222884d179d -msgid "Configured value" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:262 -#: 4e04c75c453347158e157ee30a928c5b -msgid "Drop rate" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:262 -#: 9152b07e9e0a41b3831fbb7c5c6e75f7 -msgid "Description" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:265 -#: 7f8861dbc18840c7adc761359aeda92a -msgid "101110" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:265 -#: 7f4faf2290e947d8ad6f26120d5e446a -msgid "46" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:265 -#: 81f6d371855f4e6f827a46031e3afdf7 -msgid "Expedited forwarding (EF)" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:267 -#: fbe1334c09eb48e39a6064be25802c96 -msgid "000000" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:267 -#: ../../configuration/trafficpolicy/index.rst:803 -#: ../../configuration/trafficpolicy/index.rst:878 -#: 2c508a4593ce455ca7bd7e6d372500ae 4a1f42c55335462ebb4a3d643ee16a8e -#: 163f3139d11342ba85a87e6f0056738e -msgid "0" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:267 -#: bde50debfeb843ff9edc44341112c32d -msgid "Best effort traffic, default" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:269 -#: 624d6ae413f34191b08f1617f6b76544 -msgid "001010" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:269 -#: ../../configuration/trafficpolicy/index.rst:876 -#: 9e9b35c8b41c42bebdc573d88858a3b9 614751c0c341411588dd44c4c7f1e323 -msgid "10" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:269 -#: ../../configuration/trafficpolicy/index.rst:275 -#: ../../configuration/trafficpolicy/index.rst:281 -#: ../../configuration/trafficpolicy/index.rst:287 -#: ca9f2723fc3b41b2972d841be4f10dc8 e9fdf92facbb40aaa5c0698db72a98bd -#: 23efdd77545e4aa48bbedddfd11110fb 6f08c1fe88f74d2b878d4a7f2c3940ef -msgid "Low" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:269 -#: 1ad2259ab03c4175bf3af0704bf7ebcf -msgid "Assured Forwarding(AF) 11" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:271 -#: bdd7128f770d4cf78aa655116e8c86af -msgid "001100" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:271 -#: ../../configuration/trafficpolicy/index.rst:872 -#: 2db0060506c4489d8b31291d72cc6a9e d7cd2cc6d609441083dfab220c1d44fd -msgid "12" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:271 -#: ../../configuration/trafficpolicy/index.rst:277 -#: ../../configuration/trafficpolicy/index.rst:283 -#: ../../configuration/trafficpolicy/index.rst:289 -#: d658410fd171453c9e4fa98ebd8d4405 a954f5ac107d41d287325a9daef126a5 -#: 94c77369f139466185aa959a124dd6ff db61c63a009b49b9a26d2bc5807634ab -msgid "Medium" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:271 -#: 250be957cc10481a8edc473191c87f80 -msgid "Assured Forwarding(AF) 12" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:273 -#: 2c3d6ed7ae4549d89321b978bcdc2a1a -msgid "001110" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:273 -#: ../../configuration/trafficpolicy/index.rst:868 -#: 928682a11a2e46f290cfcc98e87b2081 4f57f40027a44904a6c31a4b23c4eaf9 -msgid "14" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:273 -#: ../../configuration/trafficpolicy/index.rst:279 -#: ../../configuration/trafficpolicy/index.rst:285 -#: ../../configuration/trafficpolicy/index.rst:291 -#: c728ae3c08f14bfda8a18004d5a1e8a4 5bd7c9dd4b1d496db3e85830a9480852 -#: 6294976b96a74604b8b1c5d7ec655f12 7bb000490eff4a779b6010ad352d9fcd -msgid "High" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:273 -#: 01073e420f574b89a7437266a4840fd4 -msgid "Assured Forwarding(AF) 13" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:275 -#: 0cb26a7d69a946289f1af48c9059fce9 -msgid "010010" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:275 -#: a65444d8d1844cbd91f2c471de55b8e2 -msgid "18" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:275 -#: 8306d6054ae34d5d8ed07170ba7e4428 -msgid "Assured Forwarding(AF) 21" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:277 -#: 8362f1432b334f81885857a48446d578 -msgid "010100" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:277 -#: e03e97f94c984fe488d73d6714c72597 -msgid "20" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:277 -#: f70b4c0245044979b5ee11063d97885a -msgid "Assured Forwarding(AF) 22" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:279 -#: 11f72f8818ed4515b876719ffc1c1c5c -msgid "010110" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:279 -#: bf3ef2d33e7e440a84570683702fbda3 -msgid "22" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:279 -#: 44ad385ffa4b418dba2450487ff6fc0d -msgid "Assured Forwarding(AF) 23" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:281 -#: cf7a61987f07467b8ce96a7fbb00e180 -msgid "011010" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:281 -#: 2b8fef42d90145aa944660ef8cf12ca7 -msgid "26" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:281 -#: 7ee0fd2e30df4e2c95a0d2e508d52fc9 -msgid "Assured Forwarding(AF) 31" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:283 -#: b7df08925f0b4ef7b5128786f700f935 -msgid "011100" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:283 -#: 57d783ba13ce407e963748ccdd381232 -msgid "28" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:283 -#: 2cd9c107a68d454399fcbcf2e18a7ab7 -msgid "Assured Forwarding(AF) 32" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:285 -#: a0bd6be126ab4322be4fa65b2c2aa4b8 -msgid "011110" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:285 -#: bf997cd4c5324ae89da56cd7c326b1d1 -msgid "30" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:285 -#: 10525538708c405f80f86650cb18ddb8 -msgid "Assured Forwarding(AF) 33" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:287 -#: 1867aeaf1da4474d84f6d77cd8ac4b6f -msgid "100010" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:287 -#: ff0c425aa904410eb570f6f6ad51dc9a -msgid "34" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:287 -#: 4f7d879071344c128781400993d77af6 -msgid "Assured Forwarding(AF) 41" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:289 -#: 8b33b187d6844fc480e99ce769e683a6 -msgid "100100" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:289 -#: 5603464bc84746789e3e367ba4809793 -msgid "36" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:289 -#: 2b90bf99bace4ce1ab3fd4c0ee9741ee -msgid "Assured Forwarding(AF) 42" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:291 -#: d8d459f6bd0a439ea6bf5ff7c6a784b9 -msgid "100110" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:291 -#: 23e4f58dc20844ef87aca4f66f5e63eb -msgid "38" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:291 -#: 22b0fc700bbc451f9baa51dfb63d1ab0 -msgid "Assured Forwarding(AF) 43" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:300 -#: ab5eb1fd4ae247e18b7d6706cecaecf8 -msgid "Embedding one policy into another one" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:302 -#: beb2d8b557a84f4cac61c0501fe39144 -msgid "" -"Often we need to embed one policy into another one. It is possible to do so " -"on classful policies, by attaching a new policy into a class. For instance, " -"you might want to apply different policies to the different classes of a " -"Round-Robin policy you have configured." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:307 -#: 1527858507e746dca5d61c9a4b36257c -msgid "" -"A common example is the case of some policies which, in order to be " -"effective, they need to be applied to an interface that is directly " -"connected where the bottleneck is. If your router is not directly connected " -"to the bottleneck, but some hop before it, you can emulate the bottleneck by" -" embedding your non-shaping policy into a classful shaping one so that it " -"takes effect." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:314 -#: 14c136ad29184d21abb8ceda81b70426 -msgid "" -"You can configure a policy into a class through the ``queue-type`` setting." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:323 -#: d402a8c67a344417b221c8a16363dc3b -msgid "" -"As shown in the last command of the example above, the `queue-type` setting " -"allows these combinations. You will be able to use it in many policies." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:327 -#: 1d2285888f5144f1bc3491fe8b92b8e9 -msgid "" -"Some policies already include other embedded policies inside. That is the " -"case of Shaper_: each of its classes use fair-queue unless you change it." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:335 -#: 3422374c84af404aaa552b50b34f3164 -msgid "Creating a traffic policy" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:337 -#: 2a09c178df0d4aa6a43e1b79daa22aa2 -msgid "" -"VyOS lets you control traffic in many different ways, here we will cover " -"every possibility. You can configure as many policies as you want, but you " -"will only be able to apply one policy per interface and direction (inbound " -"or outbound)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:342 -#: 696e844c1e4b4f4f964433228e8e19f2 -msgid "" -"Some policies can be combined, you will be able to embed_ a different policy" -" that will be applied to a class of the main policy." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:345 -#: a82eaa7199274692a199db26854617be -msgid "" -"**If you are looking for a policy for your outbound traffic** but you don't " -"know which one you need and you don't want to go through every possible " -"policy shown here, **our bet is that highly likely you are looking for a** " -"Shaper_ **policy and you want to** :ref:`set its queues <embed>` **as FQ-" -"CoDel**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:352 -#: 9d038f8420e84af091d5fd47e2679d86 -msgid "Drop Tail" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:354 -#: 556ced294024417dbb424f8fc415d118 -msgid "**Queueing discipline:** PFIFO (Packet First In First Out)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:355 -#: ../../configuration/trafficpolicy/index.rst:387 -#: ../../configuration/trafficpolicy/index.rst:622 -#: ../../configuration/trafficpolicy/index.rst:691 -#: ../../configuration/trafficpolicy/index.rst:767 -#: ../../configuration/trafficpolicy/index.rst:916 -#: ../../configuration/trafficpolicy/index.rst:961 -#: ../../configuration/trafficpolicy/index.rst:1018 -#: f8e1aa15d2eb4b63aff592fe4cb52300 0234d836b20c4f508829d8180f1b3149 -#: f1a4028ebe924be79f55ebfaf2041e61 5ee08687e97148ccb01e00bdb0c50a1a -#: f33e706fbbf04dc697619d6b049bc1ea 36f68476f5b34e2fa66529e0af9e0396 -#: e40834bb14074137ade0459724bd3587 6bfd864b8b8941519364a486fce1d606 -msgid "**Applies to:** Outbound traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:357 -#: 799cece092f649b297306771b2a744eb -msgid "" -"This the simplest queue possible you can apply to your traffic. Traffic must" -" go through a finite queue before it is actually sent. You must define how " -"many packets that queue can contain." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:361 -#: 70a7bb29523d47b590efb1d3a62fb477 -msgid "" -"When a packet is to be sent, it will have to go through that queue, so the " -"packet will be placed at the tail of it. When the packet completely goes " -"through it, it will be dequeued emptying its place in the queue and being " -"eventually handed to the NIC to be actually sent out." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:366 -#: 8ce0a3442f8d4d30ac1c6d72b260f872 -msgid "" -"Despite the Drop-Tail policy does not slow down packets, if many packets are" -" to be sent, they could get dropped when trying to get enqueued at the tail." -" This can happen if the queue has still not been able to release enough " -"packets from its head." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:371 -#: b7fd60ba7d8a419fa2597fd4bbd94e9f -msgid "" -"This is the policy that requieres the lowest resources for the same amount " -"of traffic. But **very likely you do not need it as you cannot get much from" -" it. Sometimes it is used just to enable logging.**" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:378 -#: b09be3767c614a62808fc694c91d802b -msgid "" -"Use this command to configure a drop-tail policy (PFIFO). Choose a unique " -"name for this policy and the size of the queue by setting the number of " -"packets it can contain (maximum 4294967295)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:384 -#: 2c2b92d8dd664d3fb05e37c0c3ac6378 -msgid "Fair Queue" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:386 -#: a3e5395b9e8242ff8f178072882ecc90 -msgid "**Queueing discipline:** SFQ (Stochastic Fairness Queuing)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:389 -#: 8031d91dc4654980a7f23e99fa38a543 -msgid "" -"Fair Queue is a work-conserving scheduler which schedules the transmission " -"of packets based on flows, that is, it balances traffic distributing it " -"through different sub-queues in order to ensure fairness so that each flow " -"is able to send data in turn, preventing any single one from drowning out " -"the rest." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:398 -#: 086427f3037b4005ad54993247918160 -msgid "" -"Use this command to create a Fair-Queue policy and give it a name. It is " -"based on the Stochastic Fairness Queueing and can be applied to outbound " -"traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:402 -#: 909f08c51bc74f468d2acb7f93704130 -msgid "" -"In order to separate traffic, Fair Queue uses a classifier based on source " -"address, destination address and source port. The algorithm enqueues packets" -" to hash buckets based on those tree parameters. Each of these buckets " -"should represent a unique flow. Because multiple flows may get hashed to the" -" same bucket, the hashing algorithm is perturbed at configurable intervals " -"so that the unfairness lasts only for a short while. Perturbation may " -"however cause some inadvertent packet reordering to occur. An advisable " -"value could be 10 seconds." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:411 -#: 587a3fbd4e1e4157882145b7d20f7bce -msgid "" -"One of the uses of Fair Queue might be the mitigation of Denial of Service " -"attacks." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:416 -#: 46f0331f592c4332915f86c74c24e2a5 -msgid "" -"Use this command to define a Fair-Queue policy, based on the Stochastic " -"Fairness Queueing, and set the number of seconds at which a new queue " -"algorithm perturbation will occur (maximum 4294967295)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:420 -#: 84ec36bd95844d4aa54460c82cbe625b -msgid "" -"When dequeuing, each hash-bucket with data is queried in a round robin " -"fashion. You can configure the length of the queue." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:425 -#: 52f5098789c245bba0efd52ad2a96640 -msgid "" -"Use this command to define a Fair-Queue policy, based on the Stochastic " -"Fairness Queueing, and set the number of maximum packets allowed to wait in " -"the queue. Any other packet will be dropped." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:429 -#: a7c2a913b8ed46dc8afd9c7f86134d2d -msgid "" -"Fair Queue is a non-shaping (work-conserving) policy, so it will only be " -"useful if your outgoing interface is really full. If it is not, VyOS will " -"not own the queue and Fair Queue will have no effect. If there is bandwidth " -"available on the physical link, you can embed_ Fair-Queue into a classful " -"shaping policy to make sure it owns the queue." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:441 -#: b8bc8f694542463d8638c47107201a94 -msgid "FQ-CoDel" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:443 -#: 4b934008264f40aaa59fc1c32cdce03b -msgid "**Queueing discipline** Fair/Flow Queue CoDel." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:444 -#: cbb990eb1741483c983d5200dc0b7471 -msgid "**Applies to:** Outbound Traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:446 -#: 2a2809b1b6d840428f2de1a8caa67db6 -msgid "" -"The FQ-CoDel policy distributes the traffic into 1024 FIFO queues and tries " -"to provide good service between all of them. It also tries to keep the " -"length of all the queues short." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:450 -#: 0c590ae32ed947b2bd0d244dc13b568e -msgid "" -"FQ-CoDel fights bufferbloat and reduces latency without the need of complex " -"configurations. It has become the new default Queueing Discipline for the " -"interfaces of some GNU/Linux distributions." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:454 -#: 5ac912b3376e4c5389dd09b0c0bc8474 -msgid "" -"It uses a stochastic model to classify incoming packets into different flows" -" and is used to provide a fair share of the bandwidth to all the flows using" -" the queue. Each flow is managed by the CoDel queuing discipline. " -"Reordering within a flow is avoided since Codel internally uses a FIFO " -"queue." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:460 -#: a17ebb4ab2be4d72ab6c8229eb34ac87 -msgid "" -"FQ-CoDel is based on a modified Deficit Round Robin (DRR_) queue scheduler " -"with the CoDel Active Queue Management (AQM) algorithm operating on each " -"queue." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:465 -#: 08a708a6b3ae455c8623a7fd5b0a65a8 -msgid "" -"FQ-Codel is a non-shaping (work-conserving) policy, so it will only be " -"useful if your outgoing interface is really full. If it is not, VyOS will " -"not own the queue and FQ-Codel will have no effect. If there is bandwidth " -"available on the physical link, you can embed_ FQ-Codel into a classful " -"shaping policy to make sure it owns the queue. If you are not sure if you " -"need to embed your FQ-CoDel policy into a Shaper, do it." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:474 -#: 399e9f8fce164251b91016dc7c2b6872 -msgid "" -"FQ-CoDel is tuned to run ok with its default parameters at 10Gbit speeds. It" -" might work ok too at other speeds without configuring anything, but here we" -" will explain some cases when you might want to tune its parameters." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:479 -#: 7a72d0578a87432e9f8e36c3de65a119 -msgid "" -"When running it at 1Gbit and lower, you may want to reduce the `queue-limit`" -" to 1000 packets or less. In rates like 10Mbit, you may want to set it to " -"600 packets." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:483 -#: 84d6ca15e2754a898461268271469cba -msgid "" -"If you are using FQ-CoDel embedded into Shaper_ and you have large rates " -"(100Mbit and above), you may consider increasing `quantum` to 8000 or higher" -" so that the scheduler saves CPU." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:487 -#: abf3f531795043e7a95fc2d0efd2a7eb -msgid "" -"On low rates (below 40Mbit) you may want to tune `quantum` down to something" -" like 300 bytes." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:490 -#: 4be4e8307699418a9dd5d095655ff66e -msgid "" -"At very low rates (below 3Mbit), besides tuning `quantum` (300 keeps being " -"ok) you may also want to increase `target` to something like 15ms and " -"increase `interval` to something around 150 ms." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:497 -#: c20fa46321304441a1e0ca94162e7531 -msgid "" -"Use this command to configure an fq-codel policy, set its name and the " -"maximum number of bytes (default: 1514) to be dequeued from a queue at once." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:503 -#: 7fd4d3dc8619418988c7e24f3ecd9c56 -msgid "" -"Use this command to configure an fq-codel policy, set its name and the " -"number of sub-queues (default: 1024) into which packets are classified." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:509 -#: da279fd2e2204c779d49bd6417383925 -msgid "" -"Use this command to configure an fq-codel policy, set its name and the time " -"period used by the control loop of CoDel to detect when a persistent queue " -"is developing, ensuring that the measured minimum delay does not become too " -"stale (default: 100ms)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:517 -#: 756d71d426564c309f2414b8e8f3c84b -msgid "" -"Use this command to configure an fq-codel policy, set its name, and define a" -" hard limit on the real queue size. When this limit is reached, new packets " -"are dropped (default: 10240 packets)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:523 -#: 13122c64fd2a4797bc403e42219c9a21 -msgid "" -"Use this command to configure an fq-codel policy, set its name, and define " -"the acceptable minimum standing/persistent queue delay. This minimum delay " -"is identified by tracking the local minimum queue delay that packets " -"experience (default: 5ms)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:530 -#: ../../configuration/trafficpolicy/index.rst:1120 -#: 236b6a9df8db45f6bfce68217abb130f 29ecb54c9afa447289ef92e7cc707bab -msgid "Example" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:532 -#: 12d018428c7c4d68829184933064a21b -msgid "A simple example of an FQ-CoDel policy working inside a Shaper one." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:544 -#: ebf050cede3943ad995b37cda16480df -msgid "Limiter" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:546 -#: 819cc7bc5eaa43cbb01f7cb486689818 -msgid "**Queueing discipline:** Ingress policer." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:547 -#: ../../configuration/trafficpolicy/index.rst:1188 -#: 7e4aaecc6ac543ed9e9e9e9c76eaf736 8cdd2d843ac94d95bda8b1e5a937fdaf -msgid "**Applies to:** Inbound traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:549 -#: 59bd2897e5cf4af59f7f50f965320f39 -msgid "" -"Limiter is one of those policies that uses classes_ (Ingress qdisc is " -"actually a classless policy but filters do work in it)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:552 -#: 058d5be4dcbf4cb28297ff878399cf09 -msgid "" -"The limiter performs basic ingress policing of traffic flows. Multiple " -"classes of traffic can be defined and traffic limits can be applied to each " -"class. Although the policer uses a token bucket mechanism internally, it " -"does not have the capability to delay a packet as a shaping mechanism does. " -"Traffic exceeding the defined bandwidth limits is directly dropped. A " -"maximum allowed burst can be configured too." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:559 -#: c172e74fe44b45beb233d1fa3c97cb75 -msgid "" -"You can configure classes (up to 4090) with different settings and a default" -" policy which will be applied to any traffic not matching any of the " -"configured classes." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:564 -#: 3c75c9ad8c2846f0bd8468e8cb6d9618 -msgid "" -"In the case you want to apply some kind of **shaping** to your **inbound** " -"traffic, check the ingress-shaping_ section." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:571 -#: 9704dacbd9a849febe36b3b638aa6906 -msgid "" -"Use this command to configure an Ingress Policer, defining its name, a class" -" identifier (1-4090), a class matching rule name and its description." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:576 -#: 7d06a044756f49d58f5d50f8a20b76c9 -msgid "" -"Once the matching rules are set for a class, you can start configuring how " -"you want matching traffic to behave." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:583 -#: d3411b9d783a40d197e8191992a2a0e4 -msgid "" -"Use this command to configure an Ingress Policer, defining its name, a class" -" identifier (1-4090) and the maximum allowed bandwidth for this class." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:591 -#: 3a71268739df4e78ab512ab418ec0643 -msgid "" -"Use this command to configure an Ingress Policer, defining its name, a class" -" identifier (1-4090) and the burst size in bytes for this class (default: " -"15)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:598 -#: 28b6866b9d694b4fa8fdefdf0356d426 -msgid "" -"Use this command to configure an Ingress Policer, defining its name and the " -"maximum allowed bandwidth for its default policy." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:604 -#: db146dbfca504e57a8f44a2f114fc401 -msgid "" -"Use this command to configure an Ingress Policer, defining its name and the " -"burst size in bytes (default: 15) for its default policy." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:611 -#: 5e646627fa734fa5a1ce8023e18ddd59 -msgid "" -"Use this command to configure an Ingress Policer, defining its name, a class" -" identifier (1-4090), and the priority (0-20, default 20) in which the rule " -"is evaluated (the lower the number, the higher the priority)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:619 -#: 17f1b5076e634101992e7570df46d5f9 -msgid "Network Emulator" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:621 -#: ee2dec03440148aa9dd9df58620a376e -msgid "" -"**Queueing discipline:** netem (Network Emulator) + TBF (Token Bucket " -"Filter)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:624 -#: 57ca17fb81ca49aabf6d0ec1024dfa5c -msgid "" -"VyOS Network Emulator policy emulates the conditions you can suffer in a " -"real network. You will be able to configure things like rate, burst, delay, " -"packet loss, packet corruption or packet reordering." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:628 -#: ca6e683e5bd2457dae257e569460a9ff -msgid "" -"This could be helpful if you want to test how an application behaves under " -"certain network conditions." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:634 -#: e2da2ac4a86645189f09a66a8088e066 -msgid "" -"Use this command to configure the maximum rate at which traffic will be " -"shaped in a Network Emulator policy. Define the name of the policy and the " -"rate." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:640 -#: e997eb89a9f34c64b8bcd4dbff8c52c2 -msgid "" -"Use this command to configure the burst size of the traffic in a Network " -"Emulator policy. Define the name of the Network Emulator policy and its " -"traffic burst size (it will be configured through the Token Bucket Filter " -"qdisc). Default:15kb. It will only take effect if you have configured its " -"bandwidth too." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:649 -#: 2dd8f198290342f68fd2819de9ecab3c -msgid "" -"Use this command to configure a Network Emulator policy defining its name " -"and the fixed amount of time you want to add to all packet going out of the " -"interface. The latency will be added through the Token Bucket Filter qdisc. " -"It will only take effect if you have configured its bandwidth too. You can " -"use secs, ms and us. Default: 50ms." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:659 -#: b55579c2810d41369bfb6c2cf6474b8b -msgid "" -"Use this command to emulate noise in a Network Emulator policy. Set the " -"policy name and the percentage of corrupted packets you want. A random error" -" will be introduced in a random position for the chosen percent of packets." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:667 -#: aa9875bd7a0146ab810dcc2462152ac3 -msgid "" -"Use this command to emulate packet-loss conditions in a Network Emulator " -"policy. Set the policy name and the percentage of loss packets your traffic " -"will suffer." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:674 -#: f8feabaa77f141e99eef6cf23ecf053e -msgid "" -"Use this command to emulate packet-reordering conditions in a Network " -"Emulator policy. Set the policy name and the percentage of reordered packets" -" your traffic will suffer." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:681 -#: 74df5ca6ec3d4ecc84556951ea14160f -msgid "" -"Use this command to define the length of the queue of your Network Emulator " -"policy. Set the policy name and the maximum number of packets (1-4294967295)" -" the queue may hold queued at a time." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:688 -#: 1f93b7d8c40941b5bdf5911b8636109f -msgid "Priority Queue" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:690 -#: 6e4383b1a76a40dfba2557750ef8b906 -msgid "**Queueing discipline:** PRIO." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:694 -#: 29e29a4e10cc4441857a12d8c574fc8e -msgid "" -"The Priority Queue is a classful scheduling policy. It does not delay " -"packets (Priority Queue is not a shaping policy), it simply dequeues packets" -" according to their priority." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:698 -#: 9bd3f7bed5b74a4ab943129c08e9fa3a -msgid "" -"Priority Queue, as other non-shaping policies, is only useful if your " -"outgoing interface is really full. If it is not, VyOS will not own the queue" -" and Priority Queue will have no effect. If there is bandwidth available on " -"the physical link, you can embed_ Priority Queue into a classful shaping " -"policy to make sure it owns the queue. In that case packets can be " -"prioritized based on DSCP." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:705 -#: 1c85180079f548109b5f669e2fec7438 -msgid "" -"Up to seven queues -defined as classes_ with different priorities- can be " -"configured. Packets are placed into queues based on associated match " -"criteria. Packets are transmitted from the queues in priority order. If " -"classes with a higher priority are being filled with packets continuously, " -"packets from lower priority classes will only be transmitted after traffic " -"volume from higher priority classes decreases." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:713 -#: 47dbadb20ce641be976dae0612997b35 -msgid "" -"In Priority Queue we do not define clases with a meaningless class ID number" -" but with a class priority number (1-7). The lower the number, the higher " -"the priority." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:718 -#: 5ab3e22c840a47ce82922629e7405149 -msgid "" -"As with other policies, you can define different type of matching rules for " -"your classes:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:734 -#: 2f2afa7aa6804b0080cde56d87226636 -msgid "" -"As with other policies, you can embed_ other policies into the classes (and " -"default) of your Priority Queue policy through the ``queue-type`` setting:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:753 -#: 3974873e33824c84a4cc09b4e3c5432a -msgid "" -"Use this command to configure a Priority Queue policy, set its name, set a " -"class with a priority from 1 to 7 and define a hard limit on the real queue " -"size. When this limit is reached, new packets are dropped." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:763 -#: c54bce50c5c04f8c8a6ff59e77a7d93b -msgid "Random-Detect" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:766 -#: 8166f8a4c6aa4469837666ad29f1eaa9 -msgid "**Queueing discipline:** Generalized Random Early Drop." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:769 -#: 4eb81e30b6f9418ab13f4b29088a7096 -msgid "" -"A simple Random Early Detection (RED) policy would start randomly dropping " -"packets from a queue before it reaches its queue limit thus avoiding " -"congestion. That is good for TCP connections as the gradual dropping of " -"packets acts as a signal for the sender to decrease its transmission rate." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:775 -#: 45776341d51542c78fa0ba4b2f9d0c37 -msgid "" -"In contrast to simple RED, VyOS' Random-Detect uses a Generalized Random " -"Early Detect policy that provides different virtual queues based on the IP " -"Precedence value so that some virtual queues can drop more packets than " -"others." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:780 -#: fb02b4baa9d7434b94e73b2292e41849 -msgid "" -"This is achieved by using the first three bits of the ToS (Type of Service) " -"field to categorize data streams and, in accordance with the defined " -"precedence parameters, a decision is made." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:784 -#: fdbddcc8e53b48e28f4e49134b97ac4b -msgid "IP precedence as defined in :rfc:`791`:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:787 -#: ../../configuration/trafficpolicy/index.rst:862 -#: e57ae3b63a544900965caaaccdffe29c 8e70d18d9d1740c1b0a5df6963a4464d -msgid "Precedence" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:787 -#: ../../configuration/trafficpolicy/index.rst:801 -#: 014c2cbf58624686b7d2ca89f2cca074 a162c6579719414aba4b8513ae9f0c5d -msgid "Priority" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:789 -#: ../../configuration/trafficpolicy/index.rst:864 -#: 75abc331d6da44b1ad0b03ea38fa44cd c10dfcfa97b94637b82513d5660abb30 -msgid "7" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:789 -#: d114a9bf27db4d47bd6c1c78dac22b54 -msgid "Network Control" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:791 -#: ../../configuration/trafficpolicy/index.rst:866 -#: ddfe38e8459447429e5f7dd25f29ccbe f4be5428044e41ddbd04c0ac20d3f96a -msgid "6" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:791 -#: e260699785114966aff670c15c2a3dda -msgid "Internetwork Control" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:793 -#: ../../configuration/trafficpolicy/index.rst:868 -#: 5b3edd0db36240a69f9dd1356b2d39ad 96f4db9bb90e4a1a82f565453cbf56a9 -msgid "5" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:793 -#: 5ae13585649b45b2b29e0becc2ec055c -msgid "CRITIC/ECP" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:795 -#: ../../configuration/trafficpolicy/index.rst:870 -#: 0f5ab94c11b94254b2650c8f1dc8dc38 d747c18f9bd54182b3c73798f2e77c5e -msgid "4" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:795 -#: 61bfc23cd4fd40eaa97d586fd0b483a2 -msgid "Flash Override" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:797 -#: ../../configuration/trafficpolicy/index.rst:872 -#: 6534d23645534512a49478734f621bf8 866fc1e954d14e44b2276ed3a302326c -msgid "3" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:797 -#: db12bfce36b647fa95f2b8f3a551b8c0 -msgid "Flash" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:799 -#: ../../configuration/trafficpolicy/index.rst:874 -#: 3fdae921f0dc43fa8b2651e0dd861f96 4053167ad4354a9e8f9d3d1197e0c3d7 -msgid "2" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:799 -#: da98985221ba40ee924f6d34b55f3fbe -msgid "Immediate" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:801 -#: ../../configuration/trafficpolicy/index.rst:876 -#: eb3a23bf102a43ea9a2a3fc71e938d58 41a66c54507e4df79b576fa15d18d8b9 -msgid "1" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:803 -#: 43c9f33691a640068c2857d52f77fc73 -msgid "Routine" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:807 -#: 632a9746e20c410c94f8ae3c070ec6f5 -msgid "" -"Random-Detect could be useful for heavy traffic. One use of this algorithm " -"might be to prevent a backbone overload. But only for TCP (because dropped " -"packets could be retransmitted), not for UDP." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:814 -#: 74ef2429a7d942e2a34de92cff0c7275 -msgid "" -"Use this command to configure a Random-Detect policy, set its name and set " -"the available bandwidth for this policy. It is used for calculating the " -"average queue size after some idle time. It should be set to the bandwidth " -"of your interface. Random Detect is not a shaping policy, this command will " -"not shape." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:823 -#: af7420a3cfae4b7ba39a5f1c1a3607a1 -msgid "" -"Use this command to configure a Random-Detect policy and set its name, then " -"state the IP Precedence for the virtual queue you are configuring and what " -"the size of its average-packet should be (in bytes, default: 1024)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:828 -#: d9074e0d65984ae38570ef5dba793385 -msgid "" -"When configuring a Random-Detect policy: **the higher the precedence number," -" the higher the priority**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:834 -#: ef5202fe2d9a487590d28d208200758b -msgid "" -"Use this command to configure a Random-Detect policy and set its name, then " -"state the IP Precedence for the virtual queue you are configuring and what " -"its mark (drop) probability will be. Set the probability by giving the N " -"value of the fraction 1/N (default: 10)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:843 -#: 2887f3d2cff445e6acbfa6205290d01c -msgid "" -"Use this command to configure a Random-Detect policy and set its name, then " -"state the IP Precedence for the virtual queue you are configuring and what " -"its maximum threshold for random detection will be (from 0 to 4096 packets, " -"default: 18). At this size, the marking (drop) probability is maximal." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:852 -#: cf08515de810484a8c6dfdecdcba6e65 -msgid "" -"Use this command to configure a Random-Detect policy and set its name, then " -"state the IP Precedence for the virtual queue you are configuring and what " -"its minimum threshold for random detection will be (from 0 to 4096 packets)." -" If this value is exceeded, packets start being eligible for being dropped." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:859 -#: 627d87503daa47efb890d0504a0ebd14 -msgid "The default values for the minimum-threshold depend on IP precedence:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:862 -#: c97dfb19489c428bb46b45d4cb0e3cb7 -msgid "default min-threshold" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:864 -#: bc7d22bce6a84f5cb1f3fcb5b4644c90 -msgid "16" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:866 -#: 4ee3fd1383864152a8a00a4fa47a9647 -msgid "15" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:870 -#: d150aaff8e094c569ae8ce6398f4b225 -msgid "13" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:874 -#: 9db524b330ed472c925cea56a5856f09 -msgid "11" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:878 -#: d586ee6c86194963a1da7e057cb7eddd -msgid "9" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:885 -#: f96eb05058b848c486e120e73f4fbd0f -msgid "" -"Use this command to configure a Random-Detect policy and set its name, then " -"name the IP Precedence for the virtual queue you are configuring and what " -"the maximum size of its queue will be (from 1 to 1-4294967295 packets). " -"Packets are dropped when the current queue length reaches this value." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:892 -#: 2f5d55c8cad342589e2f0a153fa108ca -msgid "" -"If the average queue size is lower than the **min-threshold**, an arriving " -"packet will be placed in the queue." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:895 -#: 106876e2b98940baad26c4e0e1e9b1ca -msgid "" -"In the case the average queue size is between **min-threshold** and **max-" -"threshold**, then an arriving packet would be either dropped or placed in " -"the queue, it will depend on the defined **mark-probability**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:899 -#: 9267c138c3c342f2b04f716caa0b9612 -msgid "" -"If the current queue size is larger than **queue-limit**, then packets will " -"be dropped. The average queue size depends on its former average size and " -"its current one." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:903 -#: b4dc392ff3ab4294ac320eb6a77fbdb0 -msgid "" -"If **max-threshold** is set but **min-threshold is not, then **min-" -"threshold** is scaled to 50% of **max-threshold**." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:906 -#: 6088f19bdf28427e981f2e971ebbba07 -msgid "" -"In principle, values must be :code:`min-threshold` < :code:`max-threshold` <" -" :code:`queue-limit`." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:913 -#: 8a418cbab91046e6953cb06cb8817343 -msgid "Rate Control" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:915 -#: bff6fe6f335e4f4aab167800394b97d3 -msgid "**Queueing discipline:** Tocken Bucket Filter." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:918 -#: b53a66bda5fe4cf9884bea90d313b2b4 -msgid "" -"Rate-Control is a classless policy that limits the packet flow to a set " -"rate. It is a pure shaper, it does not schedule traffic. Traffic is filtered" -" based on the expenditure of tokens. Tokens roughly correspond to bytes." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:923 -#: 05dc26e3f0d2475e982e2bca1030a412 -msgid "" -"Short bursts can be allowed to exceed the limit. On creation, the Rate-" -"Control traffic is stocked with tokens which correspond to the amount of " -"traffic that can be burst in one go. Tokens arrive at a steady rate, until " -"the bucket is full." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:930 -#: 6b4fff066585435e93814a3f3739f364 -msgid "" -"Use this command to configure a Rate-Control policy, set its name and the " -"rate limit you want to have." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:935 -#: 3a1f04797db54164aab93e10748e0676 -msgid "" -"Use this command to configure a Rate-Control policy, set its name and the " -"size of the bucket in bytes which will be available for burst." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:940 -#: fe2892fc1f1e4ab8a9ce397d226ff760 -msgid "" -"As a reference: for 10mbit/s on Intel, you might need at least 10kbyte " -"buffer if you want to reach your configured rate." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:943 -#: a72609280e45474e9a2c4c5846262b07 -msgid "A very small buffer will soon start dropping packets." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:947 -#: ccf2251b0d4b4ea5a7d3eac836e49d10 -msgid "" -"Use this command to configure a Rate-Control policy, set its name and the " -"maximum amount of time a packet can be queued (default: 50 ms)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:952 -#: 03416899f716474eae9865203f8d6d5d -msgid "" -"Rate-Control is a CPU-friendly policy. You might consider using it when you " -"just simply want to slow traffic down." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:958 -#: 96d4e2a99e0f4139b1efad2cdfe593aa -msgid "Round Robin" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:960 -#: 1589b07c47244235b8a39ca0b6445871 -msgid "**Queueing discipline:** Deficit Round Robin." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:963 -#: 4cb179214ab94068852d4508dcd639b7 -msgid "" -"The round-robin policy is a classful scheduler that divides traffic in " -"different classes_ you can configure (up to 4096). You can embed_ a new " -"policy into each of those classes (default included)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:967 -#: 6cae5c2b623b44f38bf646893754f161 -msgid "" -"Each class is assigned a deficit counter (the number of bytes that a flow is" -" allowed to transmit when it is its turn) initialized to quantum. Quantum is" -" a parameter you configure which acts like a credit of fix bytes the counter" -" receives on each round. Then the Round-Robin policy starts moving its Round" -" Robin pointer through the queues. If the deficit counter is greater than " -"the packet's size at the head of the queue, this packet will be sent and the" -" value of the counter will be decremented by the packet size. Then, the size" -" of the next packet will be compared to the counter value again, repeating " -"the process. Once the queue is empty or the value of the counter is " -"insufficient, the Round-Robin pointer will move to the next queue. If the " -"queue is empty, the value of the deficit counter is reset to 0." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:980 -#: bc636b2f42a3400f936e8dddc49e4916 -msgid "" -"At every round, the deficit counter adds the quantum so that even large " -"packets will have their opportunity to be dequeued." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:987 -#: c5282fd168fb47edb0be574e8a23ff5f -msgid "" -"Use this command to configure a Round-Robin policy, set its name, set a " -"class ID, and the quantum for that class. The deficit counter will add that " -"value each round." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:994 -#: d38ed6a380f44c60855ae70f023517d7 -msgid "" -"Use this command to configure a Round-Robin policy, set its name, set a " -"class ID, and the queue size in packets." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:997 -#: e94a6802783a484cb369c1db4f154ad1 -msgid "" -"As with other policies, Round-Robin can embed_ another policy into a class " -"through the ``queue-type`` setting." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1015 -#: e3122bab0ab14146b5e59dde6a9c8bea -msgid "Shaper" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1017 -#: 4973ace6952645e8a8b1bf635f9ffeb0 -msgid "**Queueing discipline:** Hierarchical Token Bucket." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1021 -#: b12b63bfe15141c7a57200796134036f -msgid "" -"The Shaper policy does not guarantee a low delay, but it does guarantee " -"bandwidth to different traffic classes and also lets you decide how to " -"allocate more traffic once the guarantees are met." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1025 -#: 5e4e723fa49c4ea1a277463304f1cb5d -msgid "" -"Each class can have a guaranteed part of the total bandwidth defined for the" -" whole policy, so all those shares together should not be higher than the " -"policy's whole bandwidth." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1029 -#: b332f092425e4014a187a50a462c3662 -msgid "" -"If guaranteed traffic for a class is met and there is room for more traffic," -" the ceiling parameter can be used to set how much more bandwidth could be " -"used. If guaranteed traffic is met and there are several classes willing to " -"use their ceilings, the priority parameter will establish the order in which" -" that additional traffic will be allocated. Priority can be any number from " -"0 to 7. The lower the number, the higher the priority." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1040 -#: 02609d0e47a141418d8286c5a0839033 -msgid "" -"Use this command to configure a Shaper policy, set its name and the maximum " -"bandwidth for all combined traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1047 -#: ce660b4980a7431e8cd8bf21588d3115 -msgid "" -"Use this command to configure a Shaper policy, set its name, define a class " -"and set the guaranteed traffic you want to allocate to that class." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1054 -#: 277ba29ba72a4aea9f66dd355bdae9a9 -msgid "" -"Use this command to configure a Shaper policy, set its name, define a class " -"and set the size of the `tocken bucket`_ in bytes, which will be available " -"to be sent at ceiling speed (default: 15Kb)." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1061 -#: c81b68c249d14520b79f3d02c121cbde -msgid "" -"Use this command to configure a Shaper policy, set its name, define a class " -"and set the maximum speed possible for this class. The default ceiling value" -" is the bandwidth value." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1068 -#: 1c570bbad96d448d9e2dae36c26e9edb -msgid "" -"Use this command to configure a Shaper policy, set its name, define a class " -"and set the priority for usage of available bandwidth once guarantees have " -"been met. The lower the priority number, the higher the priority. The " -"default priority value is 0, the highest priority." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1074 -#: 3dacd2d920034f78a20bc0d599e7dc82 -msgid "" -"As with other policies, Shaper can embed_ other policies into its classes " -"through the ``queue-type`` setting and then configure their parameters." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1112 -#: 787be02d15694aea9cc45629169935fa -msgid "" -"If you configure a class for **VoIP traffic**, don't give it any *ceiling*, " -"otherwise new VoIP calls could start when the link is available and get " -"suddenly dropped when other classes start using their assigned *bandwidth* " -"share." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1122 -#: 8dcc1e952d434d43ad92a743098fad3d -msgid "A simple example of Shaper using priorities." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1148 -#: 2e7c469624794aeb96aa8be5e207b4fe -msgid "Applying a traffic policy" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1150 -#: dc5b7692164c4043902cc093bd93de92 -msgid "Once a traffic-policy is created, you can apply it to an interface:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1156 -#: e44dceb67a7e4c95a1bf3524ca922d5c -msgid "" -"You can only apply one policy per interface and direction, but you could " -"reuse a policy on different interfaces and directions:" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1173 -#: 02a49fa9b95047e5bc7a9f907ed89736 -msgid "Getting queueing information" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1177 -#: 25f5f83156274897b0c39c1808c82b47 -msgid "" -"Use this command to see the queueing information for an interface. You will " -"be able to see a packet counter (Sent, Dropped, Overlimit and Backlog) per " -"policy and class configured." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1186 -#: f84ec3eb958c494ea7f3df5a80c6e813 -msgid "The case of ingress shaping" -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1190 -#: 386987b35e9444d0ac41f42cd93c0ff3 -msgid "" -"For the ingress traffic of an interface, there is only one policy you can " -"directly apply, a **Limiter** policy. You cannot apply a shaping policy " -"directly to the ingress traffic of any interface because shaping only works " -"for outbound traffic." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1195 -#: 9f9a520c3a4443b6b3a2f21b2fd7951a -msgid "" -"This workaround lets you apply a shaping policy to the ingress traffic by " -"first redirecting it to an in-between virtual interface (`Intermediate " -"Functional Block`_). There, in that virtual interface, you will be able to " -"apply any of the policies that work for outbound traffic, for instance, a " -"shaping one." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1201 -#: 9995de6d4e2741899a475c1b30e2fa46 -msgid "That is how it is possible to do the so-called \"ingress shaping\"." -msgstr "" - -#: ../../configuration/trafficpolicy/index.rst:1215 -#: 6d2e8ae9f63d4d2dad1d12d620eb4b01 -msgid "" -"Do not configure IFB as the first step. First create everything else of your" -" traffic-policy, and then you can configure IFB. Otherwise you might get the" -" ``RTNETLINK answer: File exists`` error, which can be solved with ``sudo ip" -" link delete ifb0``." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/dmvpn.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/dmvpn.po deleted file mode 100644 index a6a7f596..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/dmvpn.po +++ /dev/null @@ -1,303 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/dmvpn.rst:5 7c9a8cf410c54ea28596e11c9df7bb56 -msgid "DMVPN" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:7 729e9e6c6d1f4d3fbbf8a02158d428bb -msgid "" -":abbr:`DMVPN (Dynamic Multipoint Virtual Private Network)` is a dynamic " -":abbr:`VPN (Virtual Private Network)` technology originally developed by " -"Cisco. While their implementation was somewhat proprietary, the underlying " -"technologies are actually standards based. The three technologies are:" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:12 60abdda3dd7d4343b2019df7b3796794 -msgid ":abbr:`NHRP (Next Hop Resolution Protocol)` :rfc:`2332`" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:13 6185670591084c1c845cb98ba2e26af2 -msgid ":abbr:`mGRE (Multipoint Generic Routing Encapsulation)` :rfc:`1702`" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:14 f210aeaadb9a449eb1cf52a72c59912e -msgid "" -":abbr:`IPSec (IP Security)` - too many RFCs to list, but start with " -":rfc:`4301`" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:17 aea04aded5d64f8ea48a62a18ccea475 -msgid "" -"NHRP provides the dynamic tunnel endpoint discovery mechanism (endpoint " -"registration, and endpoint discovery/lookup), mGRE provides the tunnel " -"encapsulation itself, and the IPSec protocols handle the key exchange, and " -"crypto mechanism." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:22 e85c511ef9884b1884e19bed3ef2aad4 -msgid "" -"In short, DMVPN provides the capability for creating a dynamic-mesh VPN " -"network without having to pre-configure (static) all possible tunnel end-" -"point peers." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:26 e7dd589078ab46099a00cc45e04a6ab2 -msgid "" -"DMVPN only automates the tunnel endpoint discovery and setup. A complete " -"solution also incorporates the use of a routing protocol. BGP is " -"particularly well suited for use with DMVPN." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:34 ../../configuration/vpn/dmvpn.rst:34 -#: 173e9ebcf23740689befef2590a1ed62 8e52d6609cd647e98ecf95e59c19bc89 -msgid "Baseline DMVPN topology" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:38 ../../configuration/vpn/dmvpn.rst:182 -#: fae3cca7593c49d5980e00b8a3aea90b 040cb2747cf64ded9634b1b89ac9d301 -msgid "Configuration" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:40 e3477d0706834f84a17b55aba4da6fb9 -msgid "" -"Please refer to the :ref:`tunnel-interface` documentation for the individual" -" tunnel related options." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:43 eb73026f3be9426e8cb7f62d2dc3b57c -msgid "" -"Please refer to the :ref:`ipsec` documentation for the individual IPSec " -"related options." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:48 1ba7a426d64a4c2e9b9f83c3d44a454b -msgid "" -"Enables Cisco style authentication on NHRP packets. This embeds the secret " -"plaintext password to the outgoing NHRP packets. Incoming NHRP packets on " -"this interface are discarded unless the secret password is present. Maximum " -"length of the secret is 8 characters." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:56 ce3bd628e83648808fa2a432598a704a -msgid "" -"Specifies that the :abbr:`NBMA (Non-broadcast multiple-access network)` " -"addresses of the next hop servers are defined in the domain name nbma-" -"domain-name. For each A record opennhrp creates a dynamic NHS entry." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:60 b374bebd3cce4f00b8a18fde3d86e843 -msgid "" -"Each dynamic NHS will get a peer entry with the configured network address " -"and the discovered NBMA address." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:63 0d0ac199ba934cc68e99644f98828414 -msgid "" -"The first registration request is sent to the protocol broadcast address, " -"and the server's real protocol address is dynamically detected from the " -"first registration reply." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:69 ../../configuration/vpn/dmvpn.rst:155 -#: ca24c98405f34017b0d5f098e002e9bd 8158fa5841bd44b2a30a5f9538c32754 -msgid "" -"Specifies the holding time for NHRP Registration Requests and Resolution " -"Replies sent from this interface or shortcut-target. The holdtime is " -"specified in seconds and defaults to two hours." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:75 26ef440f83f64d58ad66aec552796c46 -msgid "" -"If the statically mapped peer is running Cisco IOS, specify the cisco " -"keyword. It is used to fix statically the Registration Request ID so that a " -"matching Purge Request can be sent if NBMA address has changed. This is to " -"work around broken IOS which requires Purge Request ID to match the original" -" Registration Request ID." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:83 d111a5eeccb545dc8c56f398a40ab2c1 -msgid "" -"Creates static peer mapping of protocol-address to :abbr:`NBMA (Non-" -"broadcast multiple-access network)` address." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:86 f4b8e24653e64d1288f0760611f3783e -msgid "" -"If the IP prefix mask is present, it directs opennhrp to use this peer as a " -"next hop server when sending Resolution Requests matching this subnet." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:89 1d60fe96c7a44fe88086e695528a44ea -msgid "This is also known as the HUBs IP address or FQDN." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:93 9c44cfaf5ab8480eae9e11197aee697b -msgid "" -"The optional parameter register specifies that Registration Request should " -"be sent to this peer on startup." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:96 870929c86ca1483ca6c44b498e01f6aa -msgid "This option is required when running a DMVPN spoke." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:100 ed86b5d20c6845c3be1f7975565b2b17 -msgid "" -"Determines how opennhrp daemon should soft switch the multicast traffic. " -"Currently, multicast traffic is captured by opennhrp daemon using a packet " -"socket, and resent back to proper destinations. This means that multicast " -"packet sending is CPU intensive." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:105 f11cc73f88f949d5948b1df91da04471 -msgid "" -"Specfying nhs makes all multicast packets to be repeated to each statically " -"configured next hop." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:108 bca0df235fbe4ca98d4034741bba43cd -msgid "" -"Synamic instructs to forward to all peers which we have a direct connection " -"with. Alternatively, you can specify the directive multiple times for each " -"protocol-address the multicast traffic should be sent to." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:112 bb7d1d00c13b43eea58fb050c895ce2a -msgid "" -"It is very easy to misconfigure multicast repeating if you have multiple " -"NHSes." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:117 9ba345a1becf4d30aece029d3fc1cf08 -msgid "" -"Disables caching of peer information from forwarded NHRP Resolution Reply " -"packets. This can be used to reduce memory consumption on big NBMA subnets." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:120 af54e7607e16481a8422f7a4ac64d38d -msgid "Currently does not do much as caching is not implemented." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:124 2506d5f594d740dcae3bd133021ebd25 -msgid "" -"Enable sending of Cisco style NHRP Traffic Indication packets. If this is " -"enabled and opennhrp detects a forwarded packet, it will send a message to " -"the original sender of the packet instructing it to create a direct " -"connection with the destination. This is basically a protocol independent " -"equivalent of ICMP redirect." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:132 fc0982f8173c4c8495c798ac7ba18a27 -msgid "Enable creation of shortcut routes." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:134 626a96c7a8e243b2a6fe1a879c49887b -msgid "" -"A received NHRP Traffic Indication will trigger the resolution and " -"establishment of a shortcut route." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:139 efa45731f220400292a54e71afd15666 -msgid "" -"This instructs opennhrp to reply with authorative answers on NHRP Resolution" -" Requests destinied to addresses in this interface (instead of forwarding " -"the packets). This effectively allows the creation of shortcut routes to " -"subnets located on the interface." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:144 61049e19a2f846e8b0977a65b9e2e062 -msgid "When specified, this should be the only keyword for the interface." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:148 2dffec4031fb4c34950acaaaab8662b9 -msgid "" -"Defines an off-NBMA network prefix for which the GRE interface will act as a" -" gateway. This an alternative to defining local interfaces with shortcut-" -"destination flag." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:161 0df2145ab8084108b3647ca89870d6ca -msgid "Example" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:164 3d55493edaec4954ba955aaa65112281 -msgid "" -"This blueprint uses VyOS as the DMVPN Hub and Cisco (7206VXR) and VyOS as " -"multiple spoke sites. The lab was build using :abbr:`EVE-NG (Emulated " -"Virtual Environment NG)`." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:171 c829c429e34c4b39ac82ce642889d245 -msgid "DMVPN network" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:171 efbbe29693ef4d19ae1663128de50184 -msgid "DMVPN example network" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:173 216fa70d8bbc4d78a761ca604f9235bb -msgid "" -"Each node (Hub and Spoke) uses an IP address from the network " -"172.16.253.128/29." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:175 39bd5306b83848f4b32be49afbc696e6 -msgid "" -"The below referenced IP address `192.0.2.1` is used as example address " -"representing a global unicast address under which the HUB can be contacted " -"by each and every individual spoke." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:185 c9a114232cb84a6c997ca475e1a3e224 -msgid "Hub" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:229 68ccd3eef4cb4560839b960004649066 -msgid "" -"Setting this up on AWS will require a \"Custom Protocol Rule\" for protocol " -"number \"47\" (GRE) Allow Rule in TWO places. Firstly on the VPC Network " -"ACL, and secondly on the security group network ACL attached to the EC2 " -"instance. This has been tested as working for the official AMI image on the " -"AWS Marketplace. (Locate the correct VPC and security group by navigating " -"through the details pane below your EC2 instance in the AWS console)." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:237 c913f5989ce045bd98768fb7e5b74c55 -msgid "Spoke" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:239 39e7bc5380e64d24810a80cd6a46aeee -msgid "" -"The individual spoke configurations only differ in the local IP address on " -"the ``tun10`` interface. See the above diagram for the individual IP " -"addresses." -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:243 3debe7d75ea543d497aea945019e0c51 -msgid "spoke01-spoke04" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:290 b39f794a81b147708becc21a750a8739 -msgid "spoke05" -msgstr "" - -#: ../../configuration/vpn/dmvpn.rst:292 14fbbce353384871bd8dc1023a55299d -msgid "VyOS can also run in DMVPN spoke mode." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/index.po deleted file mode 100644 index 06f26d4f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/index.po +++ /dev/null @@ -1,26 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/index.rst:3 3622f8ff87bb41f091c4ad3beaff2d45 -msgid "VPN" -msgstr "" - -#: ../../configuration/vpn/index.rst:18 bb1076d0e8184f7991b52ad9375f09d4 -msgid "pages to sort" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/ipsec.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/ipsec.po deleted file mode 100644 index 6154d975..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/ipsec.po +++ /dev/null @@ -1,456 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/ipsec.rst:5 0426c206839e482caf5828a8a6ecd64a -msgid "IPsec" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:7 d5923f7abdda41f8a7c3d75a0aa5e95f -msgid "" -":abbr:`GRE (Generic Routing Encapsulation)`, GRE/IPsec (or IPIP/IPsec, " -"SIT/IPsec, or any other stateless tunnel protocol over IPsec) is the usual " -"way to protect the traffic inside a tunnel." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:11 c8017d4b246a4e56b643b28b7fc11012 -msgid "" -"An advantage of this scheme is that you get a real interface with its own " -"address, which makes it easier to setup static routes or use dynamic routing" -" protocols without having to modify IPsec policies. The other advantage is " -"that it greatly simplifies router to router communication, which can be " -"tricky with plain IPsec because the external outgoing address of the router " -"usually doesn't match the IPsec policy of typical site-to-site setup and you" -" need to add special configuration for it, or adjust the source address for " -"outgoing traffic of your applications. GRE/IPsec has no such problem and is " -"completely transparent for the applications." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:21 882fda153429452b84626823434ffad6 -msgid "" -"GRE/IPIP/SIT and IPsec are widely accepted standards, which make this scheme" -" easy to implement between VyOS and virtually any other router." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:24 3f2407239939435798a328d10b64c72c -msgid "" -"For simplicity we'll assume that the protocol is GRE, it's not hard to guess" -" what needs to be changed to make it work with a different protocol. We " -"assume that IPsec will use pre-shared secret authentication and will use " -"AES128/SHA1 for the cipher and hash. Adjust this as necessary." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:29 86ac051da1d84d9da400e9cb92e84b11 -msgid "" -"VMware users should ensure that a VMXNET3 adapter is used. E1000 adapters " -"have known issues with GRE processing." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:34 c1e70e8716e14257aabf078b9217e001 -msgid "IKE (Internet Key Exchange) Attributes" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:35 e010a9bedc7c4dfd9286925b3e010b22 -msgid "" -"IKE performs mutual authentication between two parties and establishes an " -"IKE security association (SA) that includes shared secret information that " -"can be used to efficiently establish SAs for Encapsulating Security Payload " -"(ESP) or Authentication Header (AH) and a set of cryptographic algorithms to" -" be used by the SAs to protect the traffic that they carry. " -"https://datatracker.ietf.org/doc/html/rfc5996" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:42 11c9cb0277f4419ab7fcf2b0c29853fb -msgid "" -"In VyOS, IKE attributes are specified through IKE groups. Multiple proposals" -" can be specified in a single group." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:45 acf474a8c0da4be98493e7158c11a6b0 -msgid "VyOS IKE group has the next options:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:47 b0729caad7774b72a96e8d6922501bd9 -msgid "" -"``close-action`` defines the action to take if the remote peer unexpectedly " -"closes a CHILD_SA:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:50 fbb650fa5c584da4b91f905047edc494 -msgid "``none`` set action to none (default);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:52 284a2d27842e4ce0b87485cfd5d41ca6 -msgid "``hold`` set action to hold;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:54 ../../configuration/vpn/ipsec.rst:67 -#: fac3f9c7913d4a93aed22c04d7ff6168 89a6cda1c9a44a2da2102301aedf5e5b -msgid "``clear`` set action to clear;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:56 ../../configuration/vpn/ipsec.rst:69 -#: acff2ecef323430d9ebdedde86ff121e cea16f8b6d0a439ca21bcbba899ea562 -msgid "``restart`` set action to restart;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:58 9b92c6212e35449fb0d0521742ebc81b -msgid "" -"``dead-peer-detection`` controls the use of the Dead Peer Detection protocol" -" (DPD, RFC 3706) where R_U_THERE notification messages (IKEv1) or empty " -"INFORMATIONAL messages (IKEv2) are periodically sent in order to check the " -"liveliness of the IPsec peer:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:63 d531c2b87f6e44caae9e86c4b07c845c -msgid "``action`` keep-alive failure action:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:65 746f23f7c48c42e7a9c6980d8349296c -msgid "``hold`` set action to hold (default)" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:71 ad58d7cacaba43f1a958c79af5785ffd -msgid "``interval`` keep-alive interval in seconds <2-86400> (default 30);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:73 4ef19ed4a5e34775b1c37513f363b3f4 -msgid "" -"``timeout`` keep-alive timeout in seconds <2-86400> (default 120) IKEv1 only" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:75 b632d893870f41de8b1af2ac703f73ca -msgid "" -"``ikev2-reauth`` whether rekeying of an IKE_SA should also reauthenticate " -"the peer. In IKEv1, reauthentication is always done:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:78 76ac7f6fddfc44a898d7761e04baf6c9 -msgid "``yes`` enable remote host re-authentication during an IKE rekey;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:80 d0269c78af2a410b8886057952fb8b76 -msgid "``no`` disable remote host re-authenticaton during an IKE rekey;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:82 cd6d1e81e75846c7bf3790edc58fb729 -msgid "" -"``key-exchange`` which protocol should be used to initialize the connection " -"If not set both protocols are handled and connections will use IKEv2 when " -"initiating, but accept any protocol version when responding:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:86 45186fed70214d7a86f08b2002f6a479 -msgid "``ikev1`` use IKEv1 for Key Exchange;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:88 d9d7a3dc23dc4327bc8208f1ec333dee -msgid "``ikev2`` use IKEv2 for Key Exchange;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:90 fade554e20c34f029b3c8f2849dabd1e -msgid "``lifetime`` IKE lifetime in seconds <30-86400> (default 28800);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:92 4ce2fd765456474aa6791e50c4640513 -msgid "``mobike`` enable MOBIKE Support. MOBIKE is only available for IKEv2:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:94 177eabc4369742b8a6e8039b67ee6bde -msgid "``enable`` enable MOBIKE (default for IKEv2);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:96 e581649ccdf44438ab03ae5f442e14a8 -msgid "``disable`` disable MOBIKE;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:98 891fb2ff85444510b02b48028360d007 -msgid "``mode`` IKEv1 Phase 1 Mode Selection:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:100 2d5025161f87455583644ea793b5f218 -msgid "" -"``main`` use Main mode for Key Exchanges in the IKEv1 Protocol (Recommended " -"Default);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:103 941ca785860a40e58ab2209eb78ead08 -msgid "" -"``aggressive`` use Aggressive mode for Key Exchanges in the IKEv1 protocol " -"aggressive mode is much more insecure compared to Main mode;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:106 a728b83acb284649b78d4b00468bd424 -msgid "``proposal`` the list of proposals and their parameters:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:108 25519f0eb6f24e3e94b46d3c2b6b9353 -msgid "``dh-group`` dh-group;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:110 cf1ccb160a2640d09cdac6326383d5a8 -msgid "``encryption`` encryption algorithm;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:112 d15c3be7fb1e4146b7e725a1a8d46c91 -msgid "``hash`` hash algorithm." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:116 87f18fe9627348ec9244436533009f9c -msgid "ESP (Encapsulating Security Payload) Attributes" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:117 691bf2a6baf5463081ac7bd96ff6b75d -msgid "" -"ESP is used to provide confidentiality, data origin authentication, " -"connectionless integrity, an anti-replay service (a form of partial sequence" -" integrity), and limited traffic flow confidentiality. " -"https://datatracker.ietf.org/doc/html/rfc4303" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:122 8ce7a785e67249f7b8fcc89d4c32acc9 -msgid "" -"In VyOS, ESP attributes are specified through ESP groups. Multiple proposals" -" can be specified in a single group." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:125 e1fd5bb354c844c095089f6483d1f860 -msgid "VyOS ESP group has the next options:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:127 307782bcc6a3428f96afa301f38942f6 -msgid "" -"``compression`` whether IPComp compression of content is proposed on the " -"connection:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:130 38dad27261fa4843a63e96ae2e2fc211 -msgid "``disable`` disable IPComp compression (default);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:132 0ea62861cdc64c8f9f70374edece2e2c -msgid "``enable`` enable IPComp compression;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:134 cb54f49c7fa242d78f39289583d46cb3 -msgid "" -"``life-bytes`` ESP life in bytes <1024-26843545600000>. Number of bytes " -"transmitted over an IPsec SA before it expires;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:137 2a4c516a31be49ce9cf6547e4819f22a -msgid "" -"``life-packets`` ESP life in packets <1000-26843545600000>. Number of " -"packets transmitted over an IPsec SA before it expires;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:140 32ea1f6e571c4c7cb8f4451383c4cb37 -msgid "" -"``lifetime`` ESP lifetime in seconds <30-86400> (default 3600). How long a " -"particular instance of a connection (a set of encryption/authentication keys" -" for user packets) should last, from successful negotiation to expiry;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:145 647039aeb65944e18bb8e2ce30bae6b7 -msgid "``mode`` the type of the connection:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:147 49ec9458e9ee4b428aee77aad389c56b -msgid "``tunnel`` tunnel mode (default);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:149 e112e82d1314443a8a555ffb6cb2a2cd -msgid "``transport`` transport mode;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:151 91078feebbef4fc2baff038eceb33ff0 -msgid "" -"``pfs`` whether Perfect Forward Secrecy of keys is desired on the " -"connection's keying channel and defines a Diffie-Hellman group for PFS:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:154 7914786925164d14bae86c814c94392a -msgid "``enable`` Inherit Diffie-Hellman group from IKE group (default);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:156 9a745702854c4c48a319ade70a4d8f56 -msgid "``disable`` Disable PFS;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:158 35eea63e75eb41f9922d799d4dea293f -msgid "``< dh-group >`` defines a Diffie-Hellman group for PFS;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:160 1d56928a809f43a4b2201a010525e8e4 -msgid "``proposal`` ESP-group proposal with number <1-65535>:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:162 fce2c7e30b1f4a96a5f8cca114bf67f7 -msgid "``encryption`` encryption algorithm (default 128 bit AES-CBC);" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:164 fed5780b6f764bc99baba5225bf80dd8 -msgid "``hash`` hash algorithm (default sha1)." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:168 f571168e320c42e19905c9216630e084 -msgid "Options (Global IPsec settings) Attributes" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:169 511ce5102caa41fa8dcb44360d2720d7 -msgid "``options`` IPsec settings:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:171 bc9689a8d87c431d976804862b120d38 -msgid "" -"``disable-route-autoinstall`` Do not automatically install routes to remote " -"networks;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:173 ce5744907677412ca592f7ffa6f648c0 -msgid "" -"``flexvpn`` Allow FlexVPN vendor ID payload (IKEv2 only). Send the Cisco " -"FlexVPN vendor ID payload (IKEv2 only), which is required in order to make " -"Cisco brand devices allow negotiating a local traffic selector (from " -"strongSwan's point of view) that is not the assigned virtual IP address if " -"such an address is requested by strongSwan. Sending the Cisco FlexVPN vendor" -" ID prevents the peer from narrowing the initiator's local traffic selector " -"and allows it to e.g. negotiate a TS of 0.0.0.0/0 == 0.0.0.0/0 instead. This" -" has been tested with a \"tunnel mode ipsec ipv4\" Cisco template but should" -" also work for GRE encapsulation;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:175 9591943bae9c47e0a424c11c82096125 -msgid "" -"``interface`` Interface Name to use. The name of the interface on which " -"virtual IP addresses should be installed. If not specified the addresses " -"will be installed on the outbound interface;" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:177 302c9c48b01c41398e7b109669a00b4f -msgid "" -"``virtual-ip`` Allow install virtual-ip addresses. Comma separated list of " -"virtual IPs to request in IKEv2 configuration payloads or IKEv1 Mode Config." -" The wildcard addresses 0.0.0.0 and :: request an arbitrary address, " -"specific addresses may be defined. The responder may return a different " -"address, though, or none at all." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:181 9e774328104a40daac3c059ab66928fa -msgid "IPsec policy matching GRE" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:183 544d70b452b34e7dacc2385b6186b2b5 -msgid "" -"The first and arguably cleaner option is to make your IPsec policy match GRE" -" packets between external addresses of your routers. This is the best option" -" if both routers have static external addresses." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:187 b7e4d07595e6431883c4930c6d5c928e -msgid "" -"Suppose the LEFT router has external address 192.0.2.10 on its eth0 " -"interface, and the RIGHT router is 203.0.113.45" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:190 ../../configuration/vpn/ipsec.rst:240 -#: ../../configuration/vpn/ipsec.rst:300 9e463858aef34c6387a6092f80ca833b -#: 4515bb487bba42cdaa704df8bae9675c 3ba933bf5b70495f83f64f21d3e5ea6e -msgid "On the LEFT:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:224 76a6fbca9033404d8a476b6cdd128c7c -msgid "On the RIGHT, setup by analogy and swap local and remote addresses." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:228 2573875713d3405e975398710d2e037c -msgid "Source tunnel from loopbacks" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:230 d3658c9c9c3b495da76f30ac76139987 -msgid "" -"The scheme above doesn't work when one of the routers has a dynamic external" -" address though. The classic workaround for this is to setup an address on a" -" loopback interface and use it as a source address for the GRE tunnel, then " -"setup an IPsec policy to match those loopback addresses." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:235 a96d4c5f30064e24bac1a4f9367cce7d -msgid "" -"We assume that the LEFT router has static 192.0.2.10 address on eth0, and " -"the RIGHT router has a dynamic address on eth0." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:238 17d098c8c6d54b01be448edb7b2d42e7 -msgid "**Setting up the GRE tunnel**" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:251 ../../configuration/vpn/ipsec.rst:306 -#: e3633ad1bba04df5b928e8a394fae8b0 d85d82f14656425f8219697be1521a75 -msgid "On the RIGHT:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:262 9ae97b206e1f4fb0ac7d6367f23f79f6 -msgid "**Setting up IPSec**" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:264 1d5484275629410585677c86dc38f68f -msgid "" -"However, now you need to make IPsec work with dynamic address on one side. " -"The tricky part is that pre-shared secret authentication doesn't work with " -"dynamic address, so we'll have to use RSA keys." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:268 10a8b87dbd8d4ed99151a5d589afa570 -msgid "" -"First, on both routers run the operational command \"generate pki key-pair " -"install <key-pair name>\". You may choose different length than 2048 of " -"course." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:285 d27414d66cb54e7ea03bc6c70b65b63a -msgid "" -"Configuration commands for the private and public key will be displayed on " -"the screen which needs to be set on the router first. Note the command with " -"the public key (set pki key-pair ipsec-LEFT public key 'MIIBIjANBgkqh...'). " -"Then do the same on the opposite router:" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:295 35d6ece3db024253a7fcfd338eaef2d2 -msgid "" -"Note the command with the public key (set pki key-pair ipsec-RIGHT public " -"key 'FAAOCAQ8AMII...')." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:298 34e73c2ea7e14eeeaacf3baf7feadb72 -msgid "Now the noted public keys should be entered on the opposite routers." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:312 ebd7b117cd1442d3b5c7a091e2d4dc4b -msgid "" -"Now you are ready to setup IPsec. You'll need to use an ID instead of " -"address for the peer." -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:315 ff4b695d95524125bba22ee1cf42cf41 -msgid "On the LEFT (static address):" -msgstr "" - -#: ../../configuration/vpn/ipsec.rst:340 f1a4c528d84a4ca28ba21f3683df03ea -msgid "On the RIGHT (dynamic address):" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/l2tp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/l2tp.po deleted file mode 100644 index 12bbc768..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/l2tp.po +++ /dev/null @@ -1,244 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/l2tp.rst:4 0312a9ff077941589d8c45c82d96ab1e -msgid "L2TP" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:6 d6aa1e6b79094a1b840a9b3c80b2eeba -msgid "" -"VyOS utilizes accel-ppp_ to provide L2TP server functionality. It can be " -"used with local authentication or a connected RADIUS server." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:10 f06bb113de714627af750e006b1a51cd -msgid "L2TP over IPsec" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:12 1685b8008875427c9ba3d8c1f28eecaa -msgid "" -"Example for configuring a simple L2TP over IPsec VPN for remote access " -"(works with native Windows and Mac VPN clients):" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:27 0fad303606a542c6bc1dac5d7db341a7 -msgid "In the above example, an external IP of 192.0.2.2 is assumed." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:29 888988247adb4c91b8578c2bb11b1a92 -msgid "" -"If a local firewall policy is in place on your external interface you will " -"need to allow the ports below:" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:32 b2ba8ed3002343b4af637676b72ba553 -msgid "UDP port 500 (IKE)" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:33 e874ee33937c4fdaa59e7ce4eb8b272c -msgid "IP protocol number 50 (ESP)" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:34 8dc89c56bba94c74899e0658645fb407 -msgid "UDP port 1701 for IPsec" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:36 290a38cce9c844f4903fd6e263fdbc9b -msgid "" -"As well as the below to allow NAT-traversal (when NAT is detected by the VPN" -" client, ESP is encapsulated in UDP for NAT-traversal):" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:39 afe4628f3a324e209434380cb3a80289 -msgid "UDP port 4500 (NAT-T)" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:41 26cef9b12cea4d95b580e9e03101b16b -msgid "Example:" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:58 293854763133405487ebc80cb3a0c5a9 -msgid "" -"To allow VPN-clients access via your external address, a NAT rule is " -"required:" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:68 eeb7a7d4d9894d35922118bb8fe406e5 -msgid "" -"VPN-clients will request configuration parameters, optionally you can DNS " -"parameter to the client." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:76 9f7a387a34344367b030b02927d4b6f2 -msgid "" -"Established sessions can be viewed using the **show vpn remote-access** " -"operational command, or **show l2tp-server sessions**" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:88 360ba87d51bf4dc6a9428b23b8319ce8 -msgid "LNS (L2TP Network Server)" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:90 6caea873d7fe4150aba54a71b866f875 -msgid "LNS are often used to connect to a LAC (L2TP Access Concentrator)." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:92 563e6a63ee2b4994b4d234ae790495eb -msgid "Below is an example to configure a LNS:" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:104 fadf801541534614b36b133390ad4211 -msgid "" -"The example above uses 192.0.2.2 as external IP address. A LAC normally " -"requires an authentication password, which is set in the example " -"configuration to ``lns shared-secret 'secret'``. This setup requires the " -"Compression Control Protocol (CCP) being disabled, the command ``set vpn " -"l2tp remote-access ccp-disable`` accomplishes that." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:112 ab3f6e19105645539de8229b6d6f6bd5 -msgid "Bandwidth Shaping" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:114 e705ba4d16ed467eadf74b63a3f22f10 -msgid "" -"Bandwidth rate limits can be set for local users or via RADIUS based " -"attributes." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:117 05624025ccd24fa08457f733ea4247eb -msgid "Bandwidth Shaping for local users" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:119 02b415aab7314de6aa84c24b495410bc -msgid "The rate-limit is set in kbit/sec." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:137 38776952c2994e40b514a0f7927e2bf2 -msgid "RADIUS authentication" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:139 1b846dd38aaa4b5d852b576cc5450510 -msgid "" -"To enable RADIUS based authentication, the authentication mode needs to be " -"changed within the configuration. Previous settings like the local users, " -"still exists within the configuration, however they are not used if the mode" -" has been changed from local to radius. Once changed back to local, it will " -"use all local accounts again." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:149 5cf2020a023a4b0380282d3a08c029eb -msgid "" -"Since the RADIUS server would be a single point of failure, multiple RADIUS " -"servers can be setup and will be used subsequentially." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:157 5c582e97c2424f0a8d220dd2fc946413 -msgid "" -"Some RADIUS_ severs use an access control list which allows or denies " -"queries, make sure to add your VyOS router to the allowed client list." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:161 d6b4c13e331c45398639a292fb8102d4 -msgid "RADIUS source address" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:163 b62ebd03dac1497c8f920bfed6c6c7cf -msgid "" -"If you are using OSPF as IGP, always the closest interface connected to the " -"RADIUS server is used. With VyOS 1.2 you can bind all outgoing RADIUS " -"requests to a single source IP e.g. the loopback interface." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:171 daba1a7edcc64620b01ec9ec0524e298 -msgid "" -"Above command will use `10.0.0.3` as source IPv4 address for all RADIUS " -"queries on this NAS." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:174 a26d0c63d55843cdbac820fe7e69b9e2 -msgid "" -"The ``source-address`` must be configured on one of VyOS interface. Best " -"practice would be a loopback or dummy interface." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:178 86241466178f475ea05c6cfb97a9a942 -msgid "RADIUS bandwidth shaping attribute" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:180 cf39edb6c13e423faa13ceb01121a64f -msgid "" -"To enable bandwidth shaping via RADIUS, the option rate-limit needs to be " -"enabled." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:187 f69daa0303754f04827b2c1f6e049676 -msgid "" -"The default RADIUS attribute for rate limiting is ``Filter-Id``, but you may" -" also redefine it." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:194 7853faefa6754b67a26aaf046e5161a3 -msgid "" -"If you set a custom RADIUS attribute you must define it on both dictionaries" -" at RADIUS server and client, which is the vyos router in our example." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:198 e49fda5345614631bf8e83fe4102d018 -msgid "" -"The RADIUS dictionaries in VyOS are located at ``/usr/share/accel-" -"ppp/radius/``" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:201 16f273a3f06f433fb72efacdab8563f1 -msgid "RADIUS advanced features" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:203 3e5a1883011149af9bc8b767fae95598 -msgid "" -"Received RADIUS attributes have a higher priority than parameters defined " -"within the CLI configuration, refer to the explanation below." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:207 5ae439b9bde848beb8a6417861550078 -msgid "Allocation clients ip addresses by RADIUS" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:209 db0a61a018c242eeaa24ae06c3b39be4 -msgid "" -"If the RADIUS server sends the attribute ``Framed-IP-Address`` then this IP " -"address will be allocated to the client and the option ip-pool within the " -"CLI config is being ignored." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:214 938f299690ef4722bb30ad1030717bf6 -msgid "Renaming clients interfaces by RADIUS" -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:216 7a545eac95034bd48da879bd79457d46 -msgid "" -"If the RADIUS server uses the attribute ``NAS-Port-Id``, ppp tunnels will be" -" renamed." -msgstr "" - -#: ../../configuration/vpn/l2tp.rst:219 204c9ce104194a45b7f1d5870e69fcdb -msgid "" -"The value of the attribute ``NAS-Port-Id`` must be less than 16 characters, " -"otherwise the interface won't be renamed." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/openconnect.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/openconnect.po deleted file mode 100644 index 9997cd65..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/openconnect.po +++ /dev/null @@ -1,167 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/openconnect.rst:5 058235bb76b749a1bc74c22f08bb177d -msgid "OpenConnect" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:7 879805bd64b94494bfbd4297be0af7f2 -msgid "" -"OpenConnect-compatible server feature is available from this release. " -"Openconnect VPN supports SSL connection and offers full network access. SSL " -"VPN network extension connects the end-user system to the corporate network " -"with access controls based only on network layer information, such as " -"destination IP address and port number. So, it provides safe communication " -"for all types of device traffic across public networks and private networks," -" also encrypts the traffic with SSL protocol." -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:15 479a061e9f424a71963c073ba673b387 -msgid "" -"The remote user will use the openconnect client to connect to the router and" -" will receive an IP address from a VPN pool, allowing full access to the " -"network." -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:21 379988dd5cc24ea986861ad5d59ceec1 -msgid "Configuration" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:24 5c6dbb806d6a4e87b0ce7f11d60193d5 -msgid "SSL Certificates" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:26 fa1977b2132842ff9db5f77ec5e89d5e -msgid "" -"We need to generate the certificate which authenticates users who attempt to" -" access the network resource through the SSL VPN tunnels. The following " -"commands will create a self signed certificates and will be stored in " -"configuration:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:35 0d3b2e5d7079480ea04515b1bba8dff1 -msgid "" -"We can also create the certificates using Cerbort which is an easy-to-use " -"client that fetches a certificate from Let's Encrypt an open certificate " -"authority launched by the EFF, Mozilla, and others and deploys it to a web " -"server." -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:45 17e2bb7c76a04dd098293bcfb6e82757 -msgid "Server Configuration" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:59 43785cac73f443fc9809961cfc6405e2 -msgid "2FA OTP support" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:61 91231dbc0f7a408c86ab578c3fee110e -msgid "" -"Instead of password only authentication, 2FA password authentication + OTP " -"key can be used. Alternatively, OTP authentication only, without a password," -" can be used. To do this, an OTP configuration must be added to the " -"configuration above:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:74 8126e87f5c11424ba0b80e86e58f4eb9 -msgid "" -"For generating an OTP key in VyOS, you can use the CLI command (operational " -"mode):" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:83 c73a1b43e8cb461881039529ed963008 -msgid "Verification" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:93 eff6437ab6fb44bda98b2dd2ac9073ed -msgid "It is compatible with Cisco (R) AnyConnect (R) clients." -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:97 edf693e7f9724d14bc62d35cfb4aa2a8 -msgid "Example" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:100 -#: 70c05be9e7314aae80ac141d62559d06 -msgid "SSL Certificates generation" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:102 -#: 42266b2cb5ca448c8617c7bc7d05a263 -msgid "Follow the instructions to generate CA cert (in configuration mode):" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:120 -#: e6f0210dfe774d72831124f4eb528095 -msgid "" -"Follow the instructions to generate server cert (in configuration mode):" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:141 -#: 4510ed85dd0f473f95e6eaf7a6704a5d -msgid "" -"Each of the install command should be applied to the configuration and " -"commited before using under the openconnect configuration:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:154 -#: c084739bc78a4195a5f5866cd70ce7a7 -msgid "Openconnect Configuration" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:156 -#: d17a79c1a47b4cc5a8998eb95b1109e4 -msgid "Simple setup with one user added and password authentication:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:169 -#: 6918f19064914f4a87c8303b96fadae9 -msgid "Adding a 2FA with an OTP-key" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:171 -#: 47025b83fbae4a8cac64df00a589371d -msgid "" -"First the OTP keys must be generated and sent to the user and to the " -"configuration:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:205 -#: 74239418ee2a41949bbec8d5d60e0c89 -msgid "Next it is necessary to configure 2FA for OpenConnect:" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:212 -#: c141db3dc468433bb54b27133742adca -msgid "" -"Now when connecting the user will first be asked for the password and then " -"the OTP key." -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:215 -#: 81337d31de41427abb972dec19f65f7e -msgid "" -"When using Time-based one-time password (TOTP) (OTP HOTP-time), be sure that" -" the time on the server and the OTP token generator are synchronized by NTP" -msgstr "" - -#: ../../configuration/vpn/openconnect.rst:219 -#: 57d0b72237be47c9855df8bc5b03feca -msgid "To display the configured OTP user settings, use the command:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/pptp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/pptp.po deleted file mode 100644 index b2f9791a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/pptp.po +++ /dev/null @@ -1,61 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/pptp.rst:4 c0498611d52343318dc2d561fda0ac53 -msgid "PPTP-Server" -msgstr "" - -#: ../../configuration/vpn/pptp.rst:6 32c4e0431cc1440299fa708e4be89602 -msgid "" -"The Point-to-Point Tunneling Protocol (PPTP_) has been implemented in VyOS " -"only for backwards compatibility. PPTP has many well known security issues " -"and you should use one of the many other new VPN implementations." -msgstr "" - -#: ../../configuration/vpn/pptp.rst:10 865b344ef9f44743bbeff900fb6efb8f -msgid "" -"As per default and if not otherwise defined, mschap-v2 is being used for " -"authentication and mppe 128-bit (stateless) for encryption. If no gateway-" -"address is set within the configuration, the lowest IP out of the /24 " -"client-ip-pool is being used. For instance, in the example below it would be" -" 192.168.0.1." -msgstr "" - -#: ../../configuration/vpn/pptp.rst:17 6cc1a7c5b2fa46b4990c7a217c5d9adb -msgid "server example" -msgstr "" - -#: ../../configuration/vpn/pptp.rst:30 d84cc51537f2456fbc84bcae1e7a442e -msgid "client example (debian 9)" -msgstr "" - -#: ../../configuration/vpn/pptp.rst:32 4fd57df580284e5b98d41368a3a645d4 -msgid "" -"Install the client software via apt and execute pptpsetup to generate the " -"configuration." -msgstr "" - -#: ../../configuration/vpn/pptp.rst:42 546fc96f7de244ec9dfaf83a1e2fa471 -msgid "" -"The command pon TESTUNNEL establishes the PPTP tunnel to the remote system." -msgstr "" - -#: ../../configuration/vpn/pptp.rst:45 87a307348037424eb8d63876ee4627f8 -msgid "All tunnel sessions can be checked via:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/rsa-keys.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/rsa-keys.po deleted file mode 100644 index 34c69778..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/rsa-keys.po +++ /dev/null @@ -1,98 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/rsa-keys.rst:4 00dbec42e92049b0aa6a0ad2dcce0d75 -msgid "RSA-Keys" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:5 735e28b0ac4d496f8e8714295e980ba8 -msgid "" -"RSA can be used for services such as key exchanges and for encryption " -"purposes. To make IPSec work with dynamic address on one/both sides, we will" -" have to use RSA keys for authentication. They are very fast and easy to " -"setup." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:9 f979352eac6e4751868783a819408e45 -msgid "" -"First, on both routers run the operational command \"generate pki key-pair " -"install <key-pair nam>>\". You may choose different length than 2048 of " -"course." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:26 34dd0b9071144d4cbe26fd22d2599449 -msgid "" -"Configuration commands will display. Note the command with the public key " -"(set pki key-pair ipsec-LEFT public key 'MIIBIjANBgkqh...'). Then do the " -"same on the opposite router:" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:35 fe9e4ad97c9442598bfbeea8dcc8a12d -msgid "" -"Note the command with the public key (set pki key-pair ipsec-RIGHT public " -"key 'FAAOCAQ8AMII...')." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:38 19826d136ab942dbb9a394ee72497535 -msgid "The noted public keys should be entered on the opposite routers." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:40 3bd8a0c9e9d8402ab79a951365f1c2e1 -msgid "On the LEFT:" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:46 c0f0c68cf4f344178a821534e723debc -msgid "On the RIGHT:" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:52 614d61f701244c21b105f686158a9090 -msgid "Now you are ready to setup IPsec. The key points:" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:54 979aa2c988184a2d869e1ba61191769b -msgid "" -"Since both routers do not know their effective public addresses, we set the " -"local-address of the peer to \"any\"." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:55 bb7da7ceda6c462eb4f1a409326b4dc8 -msgid "" -"On the initiator, we set the peer address to its public address, but on the " -"responder we only set the id." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:56 a066edada96042648b98a3e0421522f5 -msgid "" -"On the initiator, we need to set the remote-id option so that it can " -"identify IKE traffic from the responder correctly." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:57 d5d30491479c4984b26b7f118616dea4 -msgid "" -"On the responder, we need to set the local id so that initiator can know " -"who's talking to it for the point #3 to work." -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:59 96890f643ed54d519bda48dc78d24613 -msgid "On the LEFT (static address):" -msgstr "" - -#: ../../configuration/vpn/rsa-keys.rst:84 7ec7e009d79744789cfd93769ee5ea02 -msgid "On the RIGHT (dynamic address):" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/site2site_ipsec.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/site2site_ipsec.po deleted file mode 100644 index 67afdd47..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/site2site_ipsec.po +++ /dev/null @@ -1,513 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/site2site_ipsec.rst:4 -#: 772dc345df714c6fa129c8be633fe918 -msgid "Site-to-Site" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:6 -#: c957164073ed47dba679404d72192ac1 -msgid "" -"Site-to-site mode provides a way to add remote peers, which could be " -"configured to exchange encrypted information between them and VyOS itself or" -" connected/routed networks." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:10 -#: fbeb4d3b84f24b35a9ffaa848ecf33b7 -msgid "" -"To configure site-to-site connection you need to add peers with the ``set " -"vpn ipsec site-to-site`` command." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:13 -#: 827f6500b7434be7a08aeabc62d2eacc -msgid "You can identify a remote peer with:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:15 -#: 81849068b67e4dd88859385f33fa16f0 -msgid "" -"IPv4 or IPv6 address. This mode is easiest for configuration and mostly used" -" when a peer has a public static IP address;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:17 -#: 5f3b106386674171a67177eb8b3d3357 -msgid "" -"Hostname. This mode is similar to IP address, only you define DNS name " -"instead of an IP. Could be used when a peer has a public IP address and DNS " -"name, but an IP address could be changed from time to time;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:20 -#: 97cb615a3974480eb19bc868987e8e66 -msgid "" -"Remote ID of the peer. In this mode, there is no predefined remote address " -"nor DNS name of the peer. This mode is useful when a peer doesn't have a " -"publicly available IP address (NAT between it and VyOS), or IP address could" -" be changed." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:25 -#: cedb4376a20c4a3c93f4755b3834da32 -msgid "Each site-to-site peer has the next options:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:27 -#: 916b8dcf17e6485ea66e5bb8aedc1988 -msgid "" -"``authentication`` - configure authentication between VyOS and a remote " -"peer. Suboptions:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:30 -#: 3a99e555007948578d4bf8b62c2edbfc -msgid "" -"``local-id`` - ID for the local VyOS router. If defined, during the " -"authentication it will be send to remote peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:34 -#: 5286b621677c4db1b0a874a442d6090a -msgid "``mode`` - mode for authentication between VyOS and remote peer:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:36 -#: fb56b1bb1c524e9794ea5dcdd96afe5f -msgid "" -"``pre-shared-secret`` - use predefined shared secret phrase, must be the " -"same for local and remote side;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:39 -#: c4bd398d3f2a4a4db1d8f6f85f285cc0 -msgid "" -"``rsa`` - use simple shared RSA key. The key must be defined in the ``set " -"vpn rsa-keys`` section;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:42 -#: b377c158fec4432ab69e06d3414a85db -msgid "``x509`` - use certificates infrastructure for authentication." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:44 -#: 5286b7bc098e42f8b220cbd88e1c0b37 -msgid "" -"``pre-shared-secret`` - predefined shared secret. Used if configured ``mode " -"pre-shared-secret``;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:47 -#: d0910042fde040bcbfa97708758afaf1 -msgid "" -"``remote-id`` - define an ID for remote peer, instead of using peer name or " -"address. Useful in case if the remote peer is behind NAT or if ``mode x509``" -" is used;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:51 -#: e4a840d77dc0413794a473a8386a1054 -msgid "" -"``rsa-key-name`` - shared RSA key for authentication. The key must be " -"defined in the ``set vpn rsa-keys`` section;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:54 -#: 91d03d484541425d931da2cdb442d65b -msgid "" -"``use-x509-id`` - use local ID from x509 certificate. Cannot be used when " -"``id`` is defined;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:57 -#: b74546926fa84cbbbc232b07dcb73904 -msgid "``x509`` - options for x509 authentication mode:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:59 -#: fb5706e3358144978e76aab352cf0c0d -msgid "" -"``ca-cert-file`` - CA certificate file. Using for authenticating remote " -"peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:62 -#: c4ffda08656e4e58a0b3a1f7376a9448 -msgid "" -"``cert-file`` - certificate file, which will be used for authenticating " -"local router on remote peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:65 -#: fdf81ba73fe548dcbd05a5f3d13eed16 -msgid "" -"``crl-file`` - file with the Certificate Revocation List. Using to check if " -"a certificate for the remote peer is valid or revoked;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:68 -#: 684808a5bb09466b93e30c19790db365 -msgid "" -"``key`` - a private key, which will be used for authenticating local router " -"on remote peer:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:71 -#: 5d5688189bb44919ad97ab0ed7de1364 -msgid "``file`` - path to the key file;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:73 -#: 03f1b866f1fc416ab4dcea010d7c929b -msgid "``password`` - passphrase private key, if needed." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:75 -#: a940f669b93d4be099bd1e97fe9c1745 -msgid "" -"``connection-type`` - how to handle this connection process. Possible " -"variants:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:78 -#: 8e886c7a98e84a5fb8b0a7636d6169e5 -msgid "" -"``initiate`` - does initial connection to remote peer immediately after " -"configuring and after boot. In this mode the connection will not be " -"restarted in case of disconnection, therefore should be used only together " -"with DPD or another session tracking methods;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:83 -#: 2954883e6e85439793553dd6450fe861 -msgid "" -"``respond`` - does not try to initiate a connection to a remote peer. In " -"this mode, the IPSec session will be established only after initiation from " -"a remote peer. Could be useful when there is no direct connectivity to the " -"peer due to firewall or NAT in the middle of the local and remote side." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:88 -#: e188f0ff529242f0aa0c95db45e479fd -msgid "" -"``none`` - loads the connection only, which then can be manually initiated " -"or used as a responder configuration." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:91 -#: 3bab5364360c49aa8ef916df118cee8c -msgid "" -"``default-esp-group`` - ESP group to use by default for traffic encryption. " -"Might be overwritten by individual settings for tunnel or VTI interface " -"binding;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:95 -#: 1741f07cbaf5457796244eab9f4d5ed7 -msgid "``description`` - description for this peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:97 -#: 83225dfa61c94da0a7d4dcd606cf5a7e -msgid "" -"``dhcp-interface`` - use an IP address, received from DHCP for IPSec " -"connection with this peer, instead of ``local-address``;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:100 -#: f4fb4f84f9e3433dae32f978632f0bb9 -msgid "" -"``force-udp-encapsulation`` - force encapsulation of ESP into UDP datagrams." -" Useful in case if between local and remote side is firewall or NAT, which " -"not allows passing plain ESP packets between them;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:104 -#: e419fa07250f450db0001d10bfbdfcfd -msgid "``ike-group`` - IKE group to use for key exchanges;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:106 -#: 071179dd9c3141d3a74bcbe16d7023de -msgid "" -"``ikev2-reauth`` - reauthenticate remote peer during the rekeying process. " -"Can be used only with IKEv2. Create a new IKE_SA from the scratch and try to" -" recreate all IPsec SAs;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:110 -#: e43da42393d846b09247b0c9d7f2e3e2 -msgid "" -"``local-address`` - local IP address for IPSec connection with this peer. If" -" defined ``any``, then an IP address which configured on interface with " -"default route will be used;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:114 -#: 457f72e06e8344ee9343f5ace8e0b142 -msgid "" -"``tunnel`` - define criteria for traffic to be matched for encrypting and " -"send it to a peer:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:117 -#: 15b7848b580d457592e0d6b92fec62b7 -msgid "``disable`` - disable this tunnel;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:119 -#: f6a7cda407f84517b7e32abe0e0c2b23 -msgid "" -"``esp-group`` - define ESP group for encrypt traffic, defined by this " -"tunnel;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:121 -#: 872a770960d5486d87e5e6f0c00df2c1 -msgid "" -"``local`` - define a local source for match traffic, which should be " -"encrypted and send to this peer:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:124 -#: ../../configuration/vpn/site2site_ipsec.rst:134 -#: 60a878c63a4d4db083c17cb65f5f717f 7f4d23ecaecf4a57becfc76f59ba68f6 -msgid "" -"``port`` - define port. Have effect only when used together with ``prefix``;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:126 -#: c4c8c17ff71648d1995b30debb4603e2 -msgid "``prefix`` - IP network at local side." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:128 -#: 8089bee5185f496aa5ebf9fd2af1a203 -msgid "" -"``protocol`` - define the protocol for match traffic, which should be " -"encrypted and send to this peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:131 -#: 498d3bbb068a411885bae480c65da5b3 -msgid "" -"``remote`` - define the remote destination for match traffic, which should " -"be encrypted and send to this peer:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:136 -#: f0dc09756a27470e8c266c5eec235450 -msgid "``prefix`` - IP network at remote side." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:138 -#: 702fc4f0513b4865a0208bcfce2f3810 -msgid "" -"``vti`` - use a VTI interface for traffic encryption. Any traffic, which " -"will be send to VTI interface will be encrypted and send to this peer. Using" -" VTI makes IPSec configuration much flexible and easier in complex " -"situation, and allows to dynamically add/delete remote networks, reachable " -"via a peer, as in this mode router don't need to create additional SA/policy" -" for each remote network:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:145 -#: 56118826b29f420ab3c531b1d7e05b72 -msgid "``bind`` - select a VTI interface to bind to this peer;" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:147 -#: c05bea56cc2349a4951a119d56234bc9 -msgid "" -"``esp-group`` - define ESP group for encrypt traffic, passed this VTI " -"interface." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:151 -#: d0cb152a3e11445386d720cf9719a148 -msgid "Examples:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:154 -#: 981e3618b9864ac4a8d8909be6e1d59a -msgid "IKEv1" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:156 -#: ../../configuration/vpn/site2site_ipsec.rst:261 -#: 5be2f792efba428a82d4d5db0a30af07 1d885b96847b4aa7a228014e6220ef0d -msgid "Example:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:158 -#: 4c35b2128ecb482295fdf621b9626cc9 -msgid "WAN interface on `eth1`" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:159 -#: fd99726b04574a01a276ee9f7ebf30d3 -msgid "" -"left subnet: `192.168.0.0/24` site1, server side (i.e. locality, actually " -"there is no client or server roles)" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:161 -#: d377cc9fadf749c7ba6835d1724a6883 -msgid "left local_ip: `198.51.100.3` # server side WAN IP" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:162 -#: 399d51146fff4319829dff78da56e467 -msgid "right subnet: `10.0.0.0/24` site2,remote office side" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:163 -#: b274d4f34f67498eb7fea769717a0baa -msgid "right local_ip: `203.0.113.2` # remote office side WAN IP" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:209 -#: 24b2e58133e24cc6a58c0bd2216f2e46 -msgid "Show status of new setup:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:229 -#: f90aacb033ee47ce84df2fbc98a15330 -msgid "If there is SNAT rules on eth1, need to add exclude rule" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:245 -#: f3f7fda7d8684fc897f2ad2d341ac122 -msgid "" -"To allow traffic to pass through to clients, you need to add the following " -"rules. (if you used the default configuration at the top of this page)" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:259 -#: a822f82f86734160bce76e61bd2dca29 -msgid "IKEv2" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:263 -#: 90150f0782db4be5b5c65f92bd027fbb -msgid "left local_ip: 192.168.0.10 # VPN Gateway, behind NAT device" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:264 -#: 053a4c22a89342b9ab5c23b2b619d52a -msgid "left public_ip:172.18.201.10" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:265 -#: 91ab2b0d6f004789902b43ad8a391884 -msgid "right local_ip: 172.18.202.10 # right side WAN IP" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:267 -#: 0f5b917b87784f359d53b7ae65de1964 -msgid "Imagine the following topology" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:273 -#: 2155f7cd3b614b419d4cbd7cd8bd4182 -msgid "IPSec IKEv2 site2site VPN" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:273 -#: 18f4b3f166764071980c17cea58b3525 -msgid "IPSec IKEv2 site2site VPN (source ./draw.io/vpn_s2s_ikev2.drawio)" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:276 -#: 8962b17f663d4717a8968b2e8ccd2454 -msgid "" -"Don't get confused about the used /31 tunnel subnet. :rfc:`3021` gives you " -"additional information for using /31 subnets on point-to-point links." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:280 -#: 09b5295c5f904059b71943ad33940c45 -msgid "**left**" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:309 -#: 2dce1a348b9549cea89cefbef3929176 -msgid "**right**" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:341 -#: 53f85bef485847ea8d2f3fe092c1caee -msgid "Key Parameters:" -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:343 -#: ca0ab024a9e041f3be69568e08a1bef0 -msgid "" -"``authentication local-id/remote-id`` - IKE identification is used for " -"validation of VPN peer devices during IKE negotiation. If you do not " -"configure local/remote-identity, the device uses the IPv4 or IPv6 address " -"that corresponds to the local/remote peer by default. In certain network " -"setups (like ipsec interface with dynamic address, or behind the NAT ), the " -"IKE ID received from the peer does not match the IKE gateway configured on " -"the device. This can lead to a Phase 1 validation failure. So, make sure to " -"configure the local/remote id explicitly and ensure that the IKE ID is the " -"same as the remote-identity configured on the peer device." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:354 -#: de36d001286a4489b8ddcde46c1d54d9 -msgid "" -"``disable-route-autoinstall`` - This option when configured disables the " -"routes installed in the default table 220 for site-to-site ipsec. It is " -"mostly used with VTI configuration." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:358 -#: 13fcdb8e94b24abfaeef0ac24576cd55 -msgid "" -"``dead-peer-detection action = clear | hold | restart`` - R_U_THERE " -"notification messages(IKEv1) or empty INFORMATIONAL messages (IKEv2) are " -"periodically sent in order to check the liveliness of theIPsec peer. The " -"values clear, hold, and restart all activate DPD and determine the action to" -" perform on a timeout. With ``clear`` the connection is closed with no " -"further actions taken. ``hold`` installs a trap policy, which will catch " -"matching traffic and tries to re-negotiate the connection on demand. " -"``restart`` will immediately trigger an attempt to re-negotiate the " -"connection." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:369 -#: e7f33a23a21f477c9e6d9207519286bd -msgid "" -"``close-action = none | clear | hold | restart`` - defines the action to " -"take if the remote peer unexpectedly closes a CHILD_SA (see above for " -"meaning of values). A closeaction should not be used if the peer uses " -"reauthentication or uniqueids." -msgstr "" - -#: ../../configuration/vpn/site2site_ipsec.rst:374 -#: f570226ec19c4133938ef95ee12b671d -msgid "" -"For a responder, close-action or dead-peer-detection must not be enabled. " -"For an initiator DPD with `restart` action, and `close-action 'restart'` is " -"recommended in IKE profile." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/sstp.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/sstp.po deleted file mode 100644 index dff36b0d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vpn/sstp.po +++ /dev/null @@ -1,348 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vpn/sstp.rst:5 d0b9647836024291ad96001fcbd8da50 -msgid "SSTP" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:7 c5206681aabc487fa529d0f708812900 -msgid "" -":abbr:`SSTP (Secure Socket Tunneling Protocol)` is a form of :abbr:`VPN " -"(Virtual Private Network)` tunnel that provides a mechanism to transport PPP" -" traffic through an SSL/TLS channel. SSL/TLS provides transport-level " -"security with key negotiation, encryption and traffic integrity checking. " -"The use of SSL/TLS over TCP port 443 allows SSTP to pass through virtually " -"all firewalls and proxy servers except for authenticated web proxies." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:14 1ec614a77a574f8892ae6f5c8716e9f7 -msgid "SSTP is available for Linux, BSD, and Windows." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:16 264ec910f06f4940bd59e17d785d4b65 -msgid "" -"VyOS utilizes accel-ppp_ to provide SSTP server functionality. We support " -"both local and RADIUS authentication." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:19 379da90c740c496a9ea842b85bae5f76 -msgid "" -"As SSTP provides PPP via a SSL/TLS channel the use of either publically " -"signed certificates as well as a private PKI is required." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:22 2da5817e537b458980fa85fbe99ee5fe -msgid "" -"All certificates should be stored on VyOS under ``/config/auth``. If " -"certificates are not stored in the ``/config`` directory they will not be " -"migrated during a software update." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:27 a56dcd8626304370887c6a17e3e7f3c3 -msgid "Certificates" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:30 debc74badab5408bb1932ba0d1932b59 -msgid "Self Signed CA" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:32 451090cfd350449bba4db216625772f9 -msgid "" -"To generate the CA, the server private key and certificates the following " -"commands can be used." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:65 e36fcc8e7d61432389a30c589214e3cf -msgid "Configuration" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:70 19d3cde7d2f640a1b1bbe7554496931b -msgid "" -"Create `<user>` for local authentication on this system. The users password " -"will be set to `<pass>`." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:75 ca58b2fd482441f3afb6b559b7e1f53d -msgid "Disable `<user>` account." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:80 0708f702e45145df9803b79e16e90e4e -msgid "Assign static IP address to `<user>` account." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:85 94dd9279512e4ae4a7c773cb7527fe4a -msgid "Download bandwidth limit in kbit/s for `<user>`." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:90 c42178a26ca34c95aceb636663c6b179 -msgid "Upload bandwidth limit in kbit/s for `<user>`." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:95 2dfc984c4b084e099c134b85915b9570 -msgid "" -"Require the peer to authenticate itself using one of the following " -"protocols: pap, chap, mschap, mschap-v2." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:100 06e761ced4a243c58d440d25860d19ad -msgid "" -"Set authentication backend. The configured authentication backend is used " -"for all queries." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:103 a5ff1e176a93475c82ae3a335e420dee -msgid "" -"**radius**: All authentication queries are handled by a configured RADIUS " -"server." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:105 61f82ce55da94ba5acd08f97caa5165b -msgid "**local**: All authentication queries are handled locally." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:110 2a80c1a5ae394519b3da85c53bfcf388 -msgid "" -"Specifies single `<gateway>` IP address to be used as local address of PPP " -"interfaces." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:116 ef5f1a56f1c849c8bd43d5f5bedde841 -msgid "" -"Specifies the port `<port>` that the SSTP port will listen on (default 443)." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:121 cf882757bfca47a480d274ea1fd9a407 -msgid "Use `<subnet>` as the IP pool for all connecting clients." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:126 dbed696839804349af795ce1c865bea4 -msgid "" -"Use this comand to set the IPv6 address pool from which an SSTP client will " -"get an IPv6 prefix of your defined length (mask) to terminate the SSTP " -"endpoint at their side. The mask length can be set from 48 to 128 bit long, " -"the default value is 64." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:135 9eb4a5b4f541429797ef6ecb37960821 -msgid "" -"Use this command to configure DHCPv6 Prefix Delegation (RFC3633) on SSTP. " -"You will have to set your IPv6 pool and the length of the delegation prefix." -" From the defined IPv6 pool you will be handing out networks of the defined " -"length (delegation-prefix). The length of the delegation prefix can be set " -"from 32 to 64 bit long." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:144 cbffa659d23d4780abed08daea92b854 -msgid "" -"Connected client should use `<address>` as their DNS server. This command " -"accepts both IPv4 and IPv6 addresses. Up to two nameservers can be " -"configured for IPv4, up to three for IPv6." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:148 a3905be4443f42a1aff00be7d67f4f3a -msgid "Maximum number of IPv4 nameservers" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:151 174b6c71ddee47d692f76ffa87e5a839 -msgid "SSL Certificates" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:155 b0b30f0e73954a40824dc0d19d2e763f -msgid "Path to `<file>` pointing to the certificate authority certificate." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:159 dc52ef40e80343189c07bc601920c02b -msgid "Path to `<file>` pointing to the servers certificate (public portion)." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:163 d4687f495c094631b858d4390e661752 -msgid "PPP Settings" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:167 a6204b56c5b34a60aa45c083452fa7c6 -msgid "" -"Defines the maximum `<number>` of unanswered echo requests. Upon reaching " -"the value `<number>`, the session will be reset." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:172 2d8557a45ea64ad88f2120851b2dc5cf -msgid "" -"If this option is specified and is greater than 0, then the PPP module will " -"send LCP pings of the echo request every `<interval>` seconds." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:177 087ad9af054b4b2a82bc1ad0b4900173 -msgid "" -"Specifies timeout in seconds to wait for any peer activity. If this option " -"specified it turns on adaptive lcp echo functionality and \"lcp-echo-" -"failure\" is not used." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:183 0e9654ef9781498bbaa69c74ba065480 -msgid "" -"Specifies :abbr:`MPPE (Microsoft Point-to-Point Encryption)` negotioation " -"preference." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:186 67906b5a35a44c6099a5177bb9bb711c -msgid "**require** - ask client for mppe, if it rejects drop connection" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:187 968ca56837f644a9ab4af54958e5e603 -msgid "**prefer** - ask client for mppe, if it rejects don't fail" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:188 03a6df3ae35a4f57979b6845a15b16e5 -msgid "**deny** - deny mppe" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:190 d93e5be93d534d9ba9f7381b751a418b -msgid "" -"Default behavior - don't ask client for mppe, but allow it if client wants. " -"Please note that RADIUS may override this option by MS-MPPE-Encryption-" -"Policy attribute." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:196 80d0d83fb0d04bcbaa139763dcc91930 -msgid "RADIUS" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:199 ef7aeaa74a68405abb6a6fafcd0fdeeb -msgid "Server" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:203 394ad1964cd24e8eb5fca70ac7e826d1 -msgid "" -"Configure RADIUS `<server>` and its required port for authentication " -"requests." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:207 604c0335a28b4b6aacdcc1e5aaa5ff68 -msgid "" -"Configure RADIUS `<server>` and its required shared `<secret>` for " -"communicating with the RADIUS server." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:212 c248dd8170a74df4a6970c7270bc3e4a -msgid "Mark RADIUS server as offline for this given `<time>` in seconds." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:216 c30cdcfb79894d2b880c1918468c9b02 -msgid "Temporary disable this RADIUS server." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:219 9ca399b671d04d99aae197e3c6fa7ed1 -msgid "Options" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:223 efd1560dac14483a9fc5d259ac34830e -msgid "Timeout to wait reply for Interim-Update packets. (default 3 seconds)" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:227 92a74c668adf4e5eb7820b13d0919353 -msgid "" -"Specifies IP address for Dynamic Authorization Extension server (DM/CoA)" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:231 8215911c2ca54a5b8f71239cda8674c0 -msgid "Port for Dynamic Authorization Extension server (DM/CoA)" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:235 58575b1175ee4dd39a93c064c4f1f6f1 -msgid "Secret for Dynamic Authorization Extension server (DM/CoA)" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:239 76ec5f2dedf0496d8082acc87b975fa6 -msgid "" -"Maximum number of tries to send Access-Request/Accounting-Request queries" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:243 1aab6c1956894214bdcd9e542a90b978 -msgid "Timeout to wait response from server (seconds)" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:247 5509841e37ea47b48a9124a009806fb3 -msgid "" -"Value to send to RADIUS server in NAS-Identifier attribute and to be matched" -" in DM/CoA requests." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:252 700850eac32240e4a09758db93ab1532 -msgid "" -"Value to send to RADIUS server in NAS-IP-Address attribute and to be matched" -" in DM/CoA requests. Also DM/CoA server will bind to that address." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:257 d8d77b932e0f4678a0183abc29f2ba20 -msgid "Source IPv4 address used in all RADIUS server queires." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:261 8e15a6da24374c33895cda02099c2f03 -msgid "" -"Specifies which RADIUS server attribute contains the rate limit information." -" The default attribute is `Filter-Id`." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:266 d3e79cf794c14a5fa50cbee14922acd7 -msgid "Enables bandwidth shaping via RADIUS." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:270 1be217882c4349849705a3903b5f3fa6 -msgid "" -"Specifies the vendor dictionary, dictionary needs to be in /usr/share/accel-" -"ppp/radius." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:275 704d237226254a578e623b06cd0cba35 -msgid "Example" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:277 b2855ea8dba848bbbb81cde0afb1f881 -msgid "Use local user `foo` with password `bar`" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:278 bad4224417c74f0fb20a1085ba653d9c -msgid "Client IP addresses will be provided from pool `192.0.2.0/25`" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:293 2461493dfa5a41ca95109349f20ba2d5 -msgid "Testing SSTP" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:295 b65822d07cb84f2886dc6aafdf0a0737 -msgid "" -"Once you have setup your SSTP server there comes the time to do some basic " -"testing. The Linux client used for testing is called sstpc_. sstpc_ requires" -" a PPP configuration/peer file." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:299 5109f7359e5446bfba3777a7449261db -msgid "The following PPP configuration tests MSCHAP-v2:" -msgstr "" - -#: ../../configuration/vpn/sstp.rst:320 0fd045b2c0834f7c86393cb578fb197a -msgid "" -"You can now \"dial\" the peer with the follwoing command: ``sstpc --log-" -"level 4 --log-stderr --user vyos --password vyos vpn.example.com -- call " -"vyos``." -msgstr "" - -#: ../../configuration/vpn/sstp.rst:323 4cd9730886d7448e9f439f91f8d6926c -msgid "A connection attempt will be shown as:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configuration/vrf/index.po b/docs/_locale/de_DE/LC_MESSAGES/configuration/vrf/index.po deleted file mode 100644 index 40ad5d20..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configuration/vrf/index.po +++ /dev/null @@ -1,392 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:03+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configuration/vrf/index.rst:7 7d761814c7d748748ca9ff3448151643 -msgid "VRF" -msgstr "" - -#: ../../configuration/vrf/index.rst:9 7ecc74eed4ef40ca921d21f519faebe7 -msgid "" -":abbr:`VRF (Virtual Routing and Forwarding)` devices combined with ip rules " -"provides the ability to create virtual routing and forwarding domains (aka " -"VRFs, VRF-lite to be specific) in the Linux network stack. One use case is " -"the multi-tenancy problem where each tenant has their own unique routing " -"tables and in the very least need different default gateways." -msgstr "" - -#: ../../configuration/vrf/index.rst:16 ../../configuration/vrf/index.rst:216 -#: ../../configuration/vrf/index.rst:361 9b9ed76ed7e040f1b508dd419e6ef863 -#: 2e8beb8193a54e87884f5040f27744aa 6baaa474425f4b5a960e7e5d331ab180 -msgid "Configuration" -msgstr "" - -#: ../../configuration/vrf/index.rst:18 61621b00c4204c73b89b26a98ca7594e -msgid "" -"A VRF device is created with an associated route table. Network interfaces " -"are then enslaved to a VRF device." -msgstr "" - -#: ../../configuration/vrf/index.rst:23 74308367e24143eda443807983b4bedd -msgid "" -"Create new VRF instance with `<name>`. The name is used when placing " -"individual interfaces into the VRF." -msgstr "" - -#: ../../configuration/vrf/index.rst:28 3ad5233400b5479aaacc6957cae216d3 -msgid "Configured routing table `<id>` is used by VRF `<name>`." -msgstr "" - -#: ../../configuration/vrf/index.rst:30 df8b5fe5b1084459bb8764de0aaec403 -msgid "" -"A routing table ID can not be modified once it is assigned. It can only be " -"changed by deleting and re-adding the VRF instance." -msgstr "" - -#: ../../configuration/vrf/index.rst:36 1299bcdb976c4355bb471d13ef8250bd -msgid "" -"By default the scope of the port bindings for unbound sockets is limited to " -"the default VRF. That is, it will not be matched by packets arriving on " -"interfaces enslaved to a VRF and processes may bind to the same port if they" -" bind to a VRF." -msgstr "" - -#: ../../configuration/vrf/index.rst:41 f92ca6b9359946788e73a96bf5b4a577 -msgid "" -"TCP & UDP services running in the default VRF context (ie., not bound to any" -" VRF device) can work across all VRF domains by enabling this option." -msgstr "" - -#: ../../configuration/vrf/index.rst:45 31ba69922d094ef994df09589e195643 -msgid "Interfaces" -msgstr "" - -#: ../../configuration/vrf/index.rst:47 817f51cf082f4901b3774c3c6ce825d4 -msgid "" -"When VRFs are used it is not only mandatory to create a VRF but also the VRF" -" itself needs to be assigned to an interface." -msgstr "" - -#: ../../configuration/vrf/index.rst:53 ec4e46ac9d5e463dbf836a28d7d67534 -msgid "Assign interface identified by `<interface>` to VRF named `<name>`." -msgstr "" - -#: ../../configuration/vrf/index.rst:56 030855681ec24f02942aa9698617f0b0 -msgid "Routing" -msgstr "" - -#: ../../configuration/vrf/index.rst:58 4fa761c083bd4ebe84e32bda588d8964 -msgid "VyOS 1.4 (sagitta) introduced dynamic routing support for VRFs." -msgstr "" - -#: ../../configuration/vrf/index.rst:60 acec433d33de40b68b8d0c962eb25f33 -msgid "Currently dynamic routing is supported for the following protocols:" -msgstr "" - -#: ../../configuration/vrf/index.rst:62 06b99f568f0141d19ec6150f50febc6a -msgid ":ref:`routing-bgp`" -msgstr "" - -#: ../../configuration/vrf/index.rst:63 aea7c0c3c71b4a2a93b4182caa6a9832 -msgid ":ref:`routing-isis`" -msgstr "" - -#: ../../configuration/vrf/index.rst:64 4c7a31846d1e4cc083805c58ac041de7 -msgid ":ref:`routing-ospf`" -msgstr "" - -#: ../../configuration/vrf/index.rst:65 9bf16542853a47348922a24836a13471 -msgid ":ref:`routing-ospfv3`" -msgstr "" - -#: ../../configuration/vrf/index.rst:66 ff57bda3be4c4756896f2a82b7063421 -msgid ":ref:`routing-static`" -msgstr "" - -#: ../../configuration/vrf/index.rst:68 f1c5f2f1970d43f7b0858240c5025ee7 -msgid "" -"The CLI configuration is same as mentioned in above articles. The only " -"difference is, that each routing protocol used, must be prefixed with the " -"`vrf name <name>` command." -msgstr "" - -#: ../../configuration/vrf/index.rst:73 ../../configuration/vrf/index.rst:195 -#: f1b96234a3ae450cbf4de15c9be250f8 5ba8e9699f654c83b4eb42e39b947e71 -msgid "Example" -msgstr "" - -#: ../../configuration/vrf/index.rst:75 317cc686eec14c2a8c32e2b3bef89df8 -msgid "" -"The following commands would be required to set options for a given dynamic " -"routing protocol inside a given vrf:" -msgstr "" - -#: ../../configuration/vrf/index.rst:78 28d2bf5789e34304aa03b2139c14b2df -msgid ":ref:`routing-bgp`: ``set vrf name <name> protocols bgp ...``" -msgstr "" - -#: ../../configuration/vrf/index.rst:79 73f6111303e044b28cf0072789e04ce1 -msgid ":ref:`routing-isis`: ``set vrf name <name> protocols isis ...``" -msgstr "" - -#: ../../configuration/vrf/index.rst:80 79afdf830d924ec2bc106973c7279d95 -msgid ":ref:`routing-ospf`: ``set vrf name <name> protocols ospf ...``" -msgstr "" - -#: ../../configuration/vrf/index.rst:81 19d4f4222f5e4d978cb68f63dff52baa -msgid ":ref:`routing-ospfv3`: ``set vrf name <name> protocols ospfv3 ...``" -msgstr "" - -#: ../../configuration/vrf/index.rst:82 c4389d11b1294257a2645b438b05172d -msgid ":ref:`routing-static`: ``set vrf name <name> protocols static ...``" -msgstr "" - -#: ../../configuration/vrf/index.rst:85 ../../configuration/vrf/index.rst:248 -#: ../../configuration/vrf/index.rst:413 b2a1d23763494c8d931a4c10327cc560 -#: 01b91407df7a4d45b97f9a0df342865c af49ae17fb86491e8e6787764760f4b3 -msgid "Operation" -msgstr "" - -#: ../../configuration/vrf/index.rst:87 a71f5b28d2ed42a6971fbe1e5f05e37c -msgid "" -"It is not sufficient to only configure a VRF but VRFs must be maintained, " -"too. For VRF maintenance the following operational commands are in place." -msgstr "" - -#: ../../configuration/vrf/index.rst:92 a490343d3c084a568f61ace8a47a629c -msgid "Lists VRFs that have been created" -msgstr "" - -#: ../../configuration/vrf/index.rst:102 ddb282cbf9db483c99f9b44c77876d5a -msgid "" -"Command should probably be extended to list also the real interfaces " -"assigned to this one VRF to get a better overview." -msgstr "" - -#: ../../configuration/vrf/index.rst:116 493adc9dedae48199cd1e498c7949f2d -msgid "Display IPv4 routing table for VRF identified by `<name>`." -msgstr "" - -#: ../../configuration/vrf/index.rst:135 626f19bb4b334340a8936c5a1d71abc6 -msgid "Display IPv6 routing table for VRF identified by `<name>`." -msgstr "" - -#: ../../configuration/vrf/index.rst:155 24aca736b51349c496b9360158892f36 -msgid "" -"The ping command is used to test whether a network host is reachable or not." -msgstr "" - -#: ../../configuration/vrf/index.rst:157 510df0c7a4a940ebbbae0ce48c001c97 -msgid "" -"Ping uses ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP " -"ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (pings) will " -"have an IP and ICMP header, followed by \"struct timeval\" and an arbitrary " -"number of pad bytes used to fill out the packet." -msgstr "" - -#: ../../configuration/vrf/index.rst:162 4cdee88f5cf843b596038b67c5595257 -msgid "" -"When doing fault isolation with ping, you should first run it on the local " -"host, to verify that the local network interface is up and running. Then, " -"continue with hosts and gateways further down the road towards your " -"destination. Round-trip time and packet loss statistics are computed." -msgstr "" - -#: ../../configuration/vrf/index.rst:167 2aa9067f1ef7480eb59979f43304936b -msgid "" -"Duplicate packets are not included in the packet loss calculation, although " -"the round-trip time of these packets is used in calculating the minimum/ " -"average/maximum round-trip time numbers." -msgstr "" - -#: ../../configuration/vrf/index.rst:171 c6c2dc0b0a7248b28b47c4434e2c5581 -msgid "" -"Ping command can be interrupted at any given time using `<Ctrl>+c`- A brief " -"statistic is shown afterwards." -msgstr "" - -#: ../../configuration/vrf/index.rst:187 01381f302fff45af8258e197b8e92202 -msgid "" -"Displays the route packets taken to a network host utilizing VRF instance " -"identified by `<name>`. When using the IPv4 or IPv6 option, displays the " -"route packets taken to the given hosts IP address family. This option is " -"useful when the host is specified as a hostname rather than an IP address." -msgstr "" - -#: ../../configuration/vrf/index.rst:198 ../../configuration/vrf/index.rst:205 -#: 6ec5cff6507e401982ec84a7259f541d d11d886d6b904d71b90ae07c707abb2c -msgid "VRF route leaking" -msgstr "" - -#: ../../configuration/vrf/index.rst:200 00d3c6f99c45454ba68f0426ef0efbf3 -msgid "The following example topology was built using EVE-NG." -msgstr "" - -#: ../../configuration/vrf/index.rst:205 14c8db18a4194e86bb8493a2d5133716 -msgid "VRF topology example" -msgstr "" - -#: ../../configuration/vrf/index.rst:207 6216aaa53f164049bff77a478db8bd71 -msgid "PC1 is in the ``default`` VRF and acting as e.g. a \"fileserver\"" -msgstr "" - -#: ../../configuration/vrf/index.rst:208 0c4260075db946aaa7af4cdcc693a03e -msgid "PC2 is in VRF ``blue`` which is the development department" -msgstr "" - -#: ../../configuration/vrf/index.rst:209 ff4037cdc9d9459398e7c32aa4dc6282 -msgid "" -"PC3 and PC4 are connected to a bridge device on router ``R1`` which is in " -"VRF ``red``. Say this is the HR department." -msgstr "" - -#: ../../configuration/vrf/index.rst:211 926c252502c44fb09fdfa0400b741bde -msgid "" -"R1 is managed through an out-of-band network that resides in VRF ``mgmt``" -msgstr "" - -#: ../../configuration/vrf/index.rst:250 f5363d39ac5c40afbe4fc4022ea12f04 -msgid "" -"After committing the configuration we can verify all leaked routes are " -"installed, and try to ICMP ping PC1 from PC3." -msgstr "" - -#: ../../configuration/vrf/index.rst:272 fffc413d921c40aa8f402fe8021ed599 -msgid "VRF default routing table" -msgstr "" - -#: ../../configuration/vrf/index.rst:288 bdadbd1ddca64a2abae1d2996b21fe5c -msgid "VRF red routing table" -msgstr "" - -#: ../../configuration/vrf/index.rst:305 9363fe69cfc94f9689d90689c009cdb0 -msgid "VRF blue routing table" -msgstr "" - -#: ../../configuration/vrf/index.rst:324 2de726d9d2054e07b357ffa7de994323 -msgid "L3VPN VRFs" -msgstr "" - -#: ../../configuration/vrf/index.rst:326 847eaf908e594f708b8c67f1bd1fe073 -msgid "" -":abbr:`L3VPN VRFs ( Layer 3 Virtual Private Networks )` bgpd supports for " -"IPv4 RFC 4364 and IPv6 RFC 4659. L3VPN routes, and their associated VRF MPLS" -" labels, can be distributed to VPN SAFI neighbors in the default, i.e., non " -"VRF, BGP instance. VRF MPLS labels are reached using core MPLS labels which " -"are distributed using LDP or BGP labeled unicast. bgpd also supports inter-" -"VRF route leaking." -msgstr "" - -#: ../../configuration/vrf/index.rst:336 77ff5331b496455c8c1ce1059e13d014 -msgid "VRF Route Leaking" -msgstr "" - -#: ../../configuration/vrf/index.rst:338 3ceaf3190b114e7d87c8681f4d010835 -msgid "" -"BGP routes may be leaked (i.e. copied) between a unicast VRF RIB and the VPN" -" SAFI RIB of the default VRF for use in MPLS-based L3VPNs. Unicast routes " -"may also be leaked between any VRFs (including the unicast RIB of the " -"default BGP instance). A shortcut syntax is also available for specifying " -"leaking from one VRF to another VRF using the default instance’s VPN RIB as " -"the intemediary . A common application of the VRF-VRF feature is to connect " -"a customer’s private routing domain to a provider’s VPN service. Leaking is " -"configured from the point of view of an individual VRF: import refers to " -"routes leaked from VPN to a unicast VRF, whereas export refers to routes " -"leaked from a unicast VRF to VPN." -msgstr "" - -#: ../../configuration/vrf/index.rst:350 ba2c3d1b024b402d91b54d8f6924f192 -msgid "" -"Routes exported from a unicast VRF to the VPN RIB must be augmented by two " -"parameters:" -msgstr "" - -#: ../../configuration/vrf/index.rst:353 6784799133c5442492a1cc649c90bf23 -msgid "an RD / RTLIST" -msgstr "" - -#: ../../configuration/vrf/index.rst:355 600ffddcba364fb6bd5717da9d8cc718 -msgid "" -"Configuration for these exported routes must, at a minimum, specify these " -"two parameters." -msgstr "" - -#: ../../configuration/vrf/index.rst:363 79d2c843e7b34cf4b575c9574af95a3b -msgid "" -"Configuration of route leaking between a unicast VRF RIB and the VPN SAFI " -"RIB of the default VRF is accomplished via commands in the context of a VRF " -"address-family." -msgstr "" - -#: ../../configuration/vrf/index.rst:370 e263ca1be65342f5b6f274cc18d0509d -msgid "" -"Specifies the route distinguisher to be added to a route exported from the " -"current unicast VRF to VPN." -msgstr "" - -#: ../../configuration/vrf/index.rst:377 b7864249eae64faea2937d78a7deac56 -msgid "" -"Specifies the route-target list to be attached to a route (export) or the " -"route-target list to match against (import) when exporting/importing between" -" the current unicast VRF and VPN.The RTLIST is a space-separated list of " -"route-targets, which are BGP extended community values as described in " -"Extended Communities Attribute." -msgstr "" - -#: ../../configuration/vrf/index.rst:386 75192081e1974e49953a4590e46c0d69 -msgid "" -"Enables an MPLS label to be attached to a route exported from the current " -"unicast VRF to VPN. If the value specified is auto, the label value is " -"automatically assigned from a pool maintained." -msgstr "" - -#: ../../configuration/vrf/index.rst:394 931d1fcabf014d11971011188d45e028 -msgid "" -"Specifies an optional route-map to be applied to routes imported or exported" -" between the current unicast VRF and VPN." -msgstr "" - -#: ../../configuration/vrf/index.rst:400 4556ffd9c8e9447a9175de384372aab1 -msgid "" -"Enables import or export of routes between the current unicast VRF and VPN." -msgstr "" - -#: ../../configuration/vrf/index.rst:405 001eb3ef87c0483eb046838e7acad218 -msgid "" -"Shortcut syntax for specifying automatic leaking from vrf VRFNAME to the " -"current VRF using the VPN RIB as intermediary. The RD and RT are auto " -"derived and should not be specified explicitly for either the source or " -"destination VRF’s." -msgstr "" - -#: ../../configuration/vrf/index.rst:415 0c3d4e32e3fd4df295c066e3f3fd9b46 -msgid "" -"It is not sufficient to only configure a L3VPN VRFs but L3VPN VRFs must be " -"maintained, too.For L3VPN VRF maintenance the following operational commands" -" are in place." -msgstr "" - -#: ../../configuration/vrf/index.rst:421 cc6b1b5a3e764ec78bc1f54491eee717 -msgid "Print active IPV4 or IPV6 routes advertised via the VPN SAFI." -msgstr "" - -#: ../../configuration/vrf/index.rst:442 f94f3971ae8148bbadbc698397d9c1dd -msgid "" -"Print a summary of neighbor connections for the specified AFI/SAFI " -"combination." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/build-vyos.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/build-vyos.po deleted file mode 100644 index 82c09950..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/build-vyos.po +++ /dev/null @@ -1,582 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/build-vyos.rst:5 f9b434efcd7a47e6ba9e7a6aaa04434d -msgid "Build VyOS" -msgstr "" - -#: ../../contributing/build-vyos.rst:9 e7859dcaaf73449f97a0e48a37f86172 -msgid "Prerequisites" -msgstr "" - -#: ../../contributing/build-vyos.rst:11 17de3ba2c45340499b63d4f5d27bf877 -msgid "There are different ways you can build VyOS." -msgstr "" - -#: ../../contributing/build-vyos.rst:13 18040e9a029542619d890b955a7da385 -msgid "" -"Building using a :ref:`build_docker` container, although not the only way, " -"is the easiest way as all dependencies are managed for you. However, you can" -" also set up your own build machine and run a :ref:`build_native`." -msgstr "" - -#: ../../contributing/build-vyos.rst:17 34f1314ec9ef47cdb4942d747072dcaf -msgid "" -"Starting with VyOS 1.2 the release model of VyOS has changed. VyOS is now " -"**free as in speech, but not as in beer**. This means that while VyOS is " -"still an open source project, the release ISOs are no longer free and can " -"only be obtained via subscription, or by contributing to the community." -msgstr "" - -#: ../../contributing/build-vyos.rst:23 6567d7d0b0064e7cbb1b19a7937a0a2e -msgid "" -"The source code remains public and an ISO can be built using the process " -"outlined in this chapter." -msgstr "" - -#: ../../contributing/build-vyos.rst:26 8d50098cac234918806bbf90d7c43e77 -msgid "" -"This will guide you through the process of building a VyOS ISO using " -"Docker_. This process has been tested on clean installs of Debian Jessie, " -"Stretch, and Buster." -msgstr "" - -#: ../../contributing/build-vyos.rst:33 a5e42057b3ae42fd9dd69626c8d3427b -msgid "Docker" -msgstr "" - -#: ../../contributing/build-vyos.rst:35 b441cd3eaafb4687bcfd3e21158b3277 -msgid "Installing Docker_ and prerequisites:" -msgstr "" - -#: ../../contributing/build-vyos.rst:46 911751b4040444788ef2bf7f7e02d612 -msgid "" -"To be able to use Docker_ without ``sudo``, the current non-root user must " -"be added to the ``docker`` group by calling: ``sudo usermod -aG docker " -"yourusername``." -msgstr "" - -#: ../../contributing/build-vyos.rst:50 05146ea1c05d4c0db6e76b87276c43eb -msgid "" -"Doing so grants privileges equivalent to the ``root`` user! It is " -"recommended to remove the non-root user from the ``docker`` group after " -"building the VyOS ISO. See also `Docker as non-root`_." -msgstr "" - -#: ../../contributing/build-vyos.rst:54 900c5ddbe9174950ab52565784843ba9 -msgid "" -"The build process needs to be built on a local file system, building on SMB " -"or NFS shares will result in the container failing to build properly! " -"VirtualBox Drive Share is also not an option as block device operations are " -"not implemented and the drive is always mounted as \"nodev\"" -msgstr "" - -#: ../../contributing/build-vyos.rst:60 b4b73dd959f849828a9640ee6564615e -msgid "Build Container" -msgstr "" - -#: ../../contributing/build-vyos.rst:62 073648837b614bed812f5e2883bff835 -msgid "" -"The container can be built by hand or by fetching the pre-built one from " -"DockerHub. Using the pre-built containers from the `VyOS DockerHub " -"organisation`_ will ensure that the container is always up-to-date. A " -"rebuild is triggered once the container changes (please note this will take " -"2-3 hours after pushing to the vyos-build repository)." -msgstr "" - -#: ../../contributing/build-vyos.rst:73 640cb63c32944b0bae642bbbf713260f -msgid "Dockerhub" -msgstr "" - -#: ../../contributing/build-vyos.rst:75 f351d2c9e39544438bc481283aee2750 -msgid "To manually download the container from DockerHub, run:" -msgstr "" - -#: ../../contributing/build-vyos.rst:83 a5327e673a0247d4acc9734cef314b0d -msgid "Build from source" -msgstr "" - -#: ../../contributing/build-vyos.rst:85 1c11cd53a55b49f497db759f5931b167 -msgid "The container can also be built directly from source:" -msgstr "" - -#: ../../contributing/build-vyos.rst:98 50d70f507ae740c6a1393ceb353f1b57 -msgid "" -"Since VyOS has switched to Debian (11) Bullseye in its ``current`` branch, " -"you will require individual container for `current`, `equuleus` and `crux` " -"builds." -msgstr "" - -#: ../../contributing/build-vyos.rst:103 25325d646f134653bcd53a9e67939997 -msgid "Tips and Tricks" -msgstr "" - -#: ../../contributing/build-vyos.rst:105 3335f88bb36f454f9e6fdf9fed044450 -msgid "" -"You can create yourself some handy Bash aliases to always launch the latest " -"- per release train (`current` or `crux`) - container. Add the following to " -"your ``.bash_aliases`` file:" -msgstr "" - -#: ../../contributing/build-vyos.rst:129 05c7bec68a46426791346de5999e0537 -msgid "" -"Now you are prepared with two new aliases ``vybld`` and ``vybld_crux`` to " -"spawn your development containers in your current working directory." -msgstr "" - -#: ../../contributing/build-vyos.rst:132 189ec31e898b4bbbadf749952f753b00 -msgid "" -"Some VyOS packages (namely vyos-1x) come with build-time tests which verify " -"some of the internal library calls that they work as expected. Those tests " -"are carried out through the Python Unittest module. If you want to build the" -" ``vyos-1x`` package (which is our main development package) you need to " -"start your Docker container using the following argument: ``--sysctl " -"net.ipv6.conf.lo.disable_ipv6=0``, otherwise those tests will fail." -msgstr "" - -#: ../../contributing/build-vyos.rst:142 c09bcecd4164410f87484de8a531cbae -msgid "Native Build" -msgstr "" - -#: ../../contributing/build-vyos.rst:144 0dffd1bda041451c8f52e52195fd2e89 -msgid "" -"To build VyOS natively you require a properly configured build host with the" -" following Debian versions installed:" -msgstr "" - -#: ../../contributing/build-vyos.rst:147 bc54d4f524704452af0d5498640e59d2 -msgid "Debian Jessie for VyOS 1.2 (crux)" -msgstr "" - -#: ../../contributing/build-vyos.rst:148 6bbd23b0a6c842639f5265e9ff79c214 -msgid "" -"Debian Buster for VyOS 1.3 (equuleus, current) - aka the rolling release" -msgstr "" - -#: ../../contributing/build-vyos.rst:150 fcdeba9a35e64863ae7eda72cb5514d1 -msgid "To start, clone the repository to your local machine:" -msgstr "" - -#: ../../contributing/build-vyos.rst:160 3c61095c1ab14dcf94b5c9529eaf3754 -msgid "" -"For the packages required, you can refer to the ``docker/Dockerfile`` file " -"in the repository_. The ``./configure`` script will also warn you if any " -"dependencies are missing." -msgstr "" - -#: ../../contributing/build-vyos.rst:164 31e329aa835e41429ed4dc1a75f15174 -msgid "" -"Once you have the required dependencies installed, you may proceed with the " -"steps described in :ref:`build_iso`." -msgstr "" - -#: ../../contributing/build-vyos.rst:172 8e95321ef391422a85155e9840aa810f -msgid "Build ISO" -msgstr "" - -#: ../../contributing/build-vyos.rst:174 b789f79b043744b0a88da222720d3754 -msgid "" -"Now as you are aware of the prerequisites we can continue and build our own " -"ISO from source. For this we have to fetch the latest source code from " -"GitHub. Please note as this will differ for both `current` and `crux`." -msgstr "" - -#: ../../contributing/build-vyos.rst:186 c59724b4d1bd4e39b68b822e653242ef -msgid "" -"Now a fresh build of the VyOS ISO can begin. Change directory to the ``vyos-" -"build`` directory and run:" -msgstr "" - -#: ../../contributing/build-vyos.rst:213 83359a6fcc8b45a2a2850676e858f09e -msgid "Start the build:" -msgstr "" - -#: ../../contributing/build-vyos.rst:220 813652e166e14361ad000f77ce3c3a76 -msgid "" -"When the build is successful, the resulting iso can be found inside the " -"``build`` directory as ``live-image-[architecture].hybrid.iso``." -msgstr "" - -#: ../../contributing/build-vyos.rst:223 b6621b905b94486888fc75685dfa79ba -msgid "Good luck!" -msgstr "" - -#: ../../contributing/build-vyos.rst:225 ce7b1c2e720c417eaa2fff65a9910a83 -msgid "" -"Building VyOS on Windows WSL2 with Docker integrated into WSL2 will work " -"like a charm. No problems are known so far!" -msgstr "" - -#: ../../contributing/build-vyos.rst:234 54aee8b029ce4144a48bfe6d396716f9 -msgid "Customize" -msgstr "" - -#: ../../contributing/build-vyos.rst:236 7df61c4ffd844f6dab126ca4f1d041cd -msgid "" -"This ISO can be customized with the following list of configure options. The" -" full and current list can be generated with ``./configure --help``:" -msgstr "" - -#: ../../contributing/build-vyos.rst:281 29d46fec07694c14926803dd88c9631f -msgid "ISO Build Issues" -msgstr "" - -#: ../../contributing/build-vyos.rst:283 2b860168d39a485ca40730cd97021857 -msgid "" -"There are (rare) situations where building an ISO image is not possible at " -"all due to a broken package feed in the background. APT is not very good at " -"reporting the root cause of the issue. Your ISO build will likely fail with " -"a more or less similar looking error message:" -msgstr "" - -#: ../../contributing/build-vyos.rst:306 111028887cdf451aaf5085b1c5bb3eb9 -msgid "" -"To debug the build process and gain additional information of what could be " -"the root cause, you need to use `chroot` to change into the build directry. " -"This is explained in the following step by step procedure:" -msgstr "" - -#: ../../contributing/build-vyos.rst:314 b91798ddcb664dd0afc0c3e5dc5d22b0 -msgid "We now need to mount some required, volatile filesystems" -msgstr "" - -#: ../../contributing/build-vyos.rst:322 13f1f727c4cc44838022d0201b1663ee -msgid "" -"We now are free to run any command we would like to use for debugging, e.g. " -"re-installing the failed package after updating the repository." -msgstr "" - -#: ../../contributing/build-vyos.rst:357 99bf13c8aae4486d9b18181cc2ef828e -msgid "" -"Now it's time to fix the package mirror and rerun the last step until the " -"package installation succeeds again!" -msgstr "" - -#: ../../contributing/build-vyos.rst:363 9a84c0d47fdd4b168bf3b531a204ead8 -msgid "Linux Kernel" -msgstr "" - -#: ../../contributing/build-vyos.rst:365 b6132ca1c1cc4ca2b987f401909b0624 -msgid "" -"The Linux kernel used by VyOS is heavily tied to the ISO build process. The " -"file ``data/defaults.json`` hosts a JSON definition of the kernel version " -"used ``kernel_version`` and the ``kernel_flavor`` of the kernel which " -"represents the kernel's LOCAL_VERSION. Both together form the kernel version" -" variable in the system:" -msgstr "" - -#: ../../contributing/build-vyos.rst:376 5f8e92525fa444fd840775e9b1941c7b -msgid "" -"Other packages (e.g. vyos-1x) add dependencies to the ISO build procedure on" -" e.g. the wireguard-modules package which itself adds a dependency on the " -"kernel version used due to the module it ships. This may change (for " -"WireGuard) in future kernel releases but as long as we have out-of-tree " -"modules." -msgstr "" - -#: ../../contributing/build-vyos.rst:381 ../../contributing/build-vyos.rst:570 -#: 2f53ab64046d40618abfa33fc5f91ed1 6c8fe0f76a79488fb1d9a21c41334902 -msgid "WireGuard" -msgstr "" - -#: ../../contributing/build-vyos.rst:382 ../../contributing/build-vyos.rst:618 -#: 698978e34d5244558896024b11bcc12b f27c76294f614a5397ea7dd435954de6 -msgid "Accel-PPP" -msgstr "" - -#: ../../contributing/build-vyos.rst:383 9daedc35e77f42ba9870cdd7adffb9fb -msgid "Intel NIC drivers" -msgstr "" - -#: ../../contributing/build-vyos.rst:384 2e7c0a9f85544e6695d278414e90e2b9 -msgid "Inter QAT" -msgstr "" - -#: ../../contributing/build-vyos.rst:386 27289b3878224bd7b7254f1daed3ee7e -msgid "" -"Each of those modules holds a dependency on the kernel version and if you " -"are lucky enough to receive an ISO build error which sounds like:" -msgstr "" - -#: ../../contributing/build-vyos.rst:404 09ba89747d10433c848a262d4f50ee42 -msgid "The most obvious reasons could be:" -msgstr "" - -#: ../../contributing/build-vyos.rst:406 db2b650375644a649f6297dd8afc026d -msgid "" -"``vyos-build`` repo is outdated, please ``git pull`` to update to the latest" -" release kernel version from us." -msgstr "" - -#: ../../contributing/build-vyos.rst:409 6046e08b28dd417f974505d3b0a3c40b -msgid "" -"You have your own custom kernel `*.deb` packages in the `packages` folder " -"but neglected to create all required out-of tree modules like Accel-PPP, " -"WireGuard, Intel QAT, Intel NIC" -msgstr "" - -#: ../../contributing/build-vyos.rst:414 a2f814ee71fb49aaa7a5c4623df52c78 -msgid "Building The Kernel" -msgstr "" - -#: ../../contributing/build-vyos.rst:416 9516ca81a94d41f98227a52c1e721f1b -msgid "" -"The kernel build is quite easy, most of the required steps can be found in " -"the ``vyos-build/packages/linux-kernel/Jenkinsfile`` but we will walk you " -"through it." -msgstr "" - -#: ../../contributing/build-vyos.rst:420 cdd6bfbaf88242f18fffe5e9bcf18fbb -msgid "Clone the kernel source to `vyos-build/packages/linux-kernel/`:" -msgstr "" - -#: ../../contributing/build-vyos.rst:427 d4dc7278e7a84f8c8152e34cbd574939 -msgid "" -"Check out the required kernel version - see ``vyos-" -"build/data/defaults.json`` file (example uses kernel 4.19.146):" -msgstr "" - -#: ../../contributing/build-vyos.rst:448 8778f37392a942048d61a1a7ccc1fa0e -msgid "" -"Now we can use the helper script ``build-kernel.sh`` which does all the " -"necessary voodoo by applying required patches from the `vyos-" -"build/packages/linux-kernel/patches` folder, copying our kernel " -"configuration ``x86_64_vyos_defconfig`` to the right location, and finally " -"building the Debian packages." -msgstr "" - -#: ../../contributing/build-vyos.rst:454 bc21b4fbf014442e828a814ad6125e88 -msgid "" -"Building the kernel will take some time depending on the speed and quantity " -"of your CPU/cores and disk speed. Expect 20 minutes (or even longer) on " -"lower end hardware." -msgstr "" - -#: ../../contributing/build-vyos.rst:533 c6a344996c504a93a3bbca90e8770e52 -msgid "" -"In the end you will be presented with the kernel binary packages which you " -"can then use in your custom ISO build process, by placing all the `*.deb` " -"files in the vyos-build/packages folder where they will be used " -"automatically when building VyOS as documented above." -msgstr "" - -#: ../../contributing/build-vyos.rst:539 936f19a82df5456f9288c58ec80a1425 -msgid "Firmware" -msgstr "" - -#: ../../contributing/build-vyos.rst:541 9330cf56b314426a9b809003a7f698e5 -msgid "" -"If you upgrade your kernel or include new drivers you may need new firmware." -" Build a new ``vyos-linux-firmware`` package with the included helper " -"scripts." -msgstr "" - -#: ../../contributing/build-vyos.rst:551 1163d0a81d2947cb88c5fa0912944c3b -msgid "" -"This tries to automatically detect which blobs are needed based on which " -"drivers were built. If it fails to find the correct files you can add them " -"manually to ``vyos-build/packages/linux-kernel/build-linux-firmware.sh``:" -msgstr "" - -#: ../../contributing/build-vyos.rst:561 736268b6ee684258b753e15f46f98568 -msgid "Building Out-Of-Tree Modules" -msgstr "" - -#: ../../contributing/build-vyos.rst:563 47b278781793406692070098433d50db -msgid "" -"Building the kernel is one part, but now you also need to build the required" -" out-of-tree modules so everything is lined up and the ABIs match. To do so," -" you can again take a look at ``vyos-build/packages/linux-" -"kernel/Jenkinsfile`` to see all of the required modules and their selected " -"versions. We will show you how to build all the current required modules." -msgstr "" - -#: ../../contributing/build-vyos.rst:572 ../../contributing/build-vyos.rst:620 -#: 3784c59cab18425c939c7eac26664604 b5760a364c314ce6b0f41f69a3ae386b -msgid "" -"First, clone the source code and check out the appropriate version by " -"running:" -msgstr "" - -#: ../../contributing/build-vyos.rst:581 ../../contributing/build-vyos.rst:627 -#: 4f7da575ba2b41ad9601e543f7232a99 1fb50119001f4deb8dc2f499be966a7d -msgid "" -"We again make use of a helper script and some patches to make the build " -"work. Just run the following command:" -msgstr "" - -#: ../../contributing/build-vyos.rst:613 ../../contributing/build-vyos.rst:654 -#: ../../contributing/build-vyos.rst:683 ../../contributing/build-vyos.rst:718 -#: e16a0aa8ede84c2d974e5f1a3fa3a05c 942733a6786a4c90888b48e3258925fb -#: 96de1ad1ca564306874ca693b64ed2f2 2b4b177225ea4ffaa7d921bdaa18f21f -msgid "" -"After compiling the packages you will find yourself the newly generated " -"`*.deb` binaries in ``vyos-build/packages/linux-kernel`` from which you can " -"copy them to the ``vyos-build/packages`` folder for inclusion during the ISO" -" build." -msgstr "" - -#: ../../contributing/build-vyos.rst:659 09c99b056d4b4b208113b5fd1cf3c178 -msgid "Intel NIC" -msgstr "" - -#: ../../contributing/build-vyos.rst:661 8514daf0ed214cc08bcc8362d8ad78f0 -msgid "" -"The Intel NIC drivers do not come from a Git repository, instead we just " -"fetch the tarballs from our mirror and compile them." -msgstr "" - -#: ../../contributing/build-vyos.rst:664 ../../contributing/build-vyos.rst:693 -#: 26953b5adaaa477884145ddedc79283a 3250ff3979494fd79a01a57e35e38e90 -msgid "Simply use our wrapper script to build all of the driver modules." -msgstr "" - -#: ../../contributing/build-vyos.rst:688 4ca472da70ed40c2ba31ea481c27d2e9 -msgid "Intel QAT" -msgstr "" - -#: ../../contributing/build-vyos.rst:689 432251d26cbe43ee84f637d19538fa2e -msgid "" -"The Intel QAT (Quick Assist Technology) drivers do not come from a Git " -"repository, instead we just fetch the tarballs from 01.org, Intel's open-" -"source website." -msgstr "" - -#: ../../contributing/build-vyos.rst:724 ../../contributing/build-vyos.rst:793 -#: 0863473aebad423e9ca45ed5d9e9821d a173df96275148daa3d0aaf02801d23c -msgid "Packages" -msgstr "" - -#: ../../contributing/build-vyos.rst:726 a7072cbb80e449e88ce611ec3b84f7a2 -msgid "" -"If you are brave enough to build yourself an ISO image containing any " -"modified package from our GitHub organisation - this is the place to be." -msgstr "" - -#: ../../contributing/build-vyos.rst:729 8116e03a23d04c309b363093ce82621d -msgid "" -"Any \"modified\" package may refer to an altered version of e.g. vyos-1x " -"package that you would like to test before filing a pull request on GitHub." -msgstr "" - -#: ../../contributing/build-vyos.rst:732 5c1d80f2550243af93c07c134bcc56e8 -msgid "" -"Building an ISO with any customized package is in no way different than " -"building a regular (customized or not) ISO image. Simply place your modified" -" `*.deb` package inside the `packages` folder within `vyos-build`. The build" -" process will then pickup your custom package and integrate it into your " -"ISO." -msgstr "" - -#: ../../contributing/build-vyos.rst:738 0e5753f4c8af477787450aeb71bb7657 -msgid "Troubleshooting" -msgstr "" - -#: ../../contributing/build-vyos.rst:740 7b10ee6f0426415bb71660552ccf413a -msgid "" -"Debian APT is not very verbose when it comes to errors. If your ISO build " -"breaks for whatever reason and you suspect it's a problem with APT " -"dependencies or installation you can add this small patch which increases " -"the APT verbosity during ISO build." -msgstr "" - -#: ../../contributing/build-vyos.rst:769 694253006ae1488aa93431b9a8a80aec -msgid "Virtualization Platforms" -msgstr "" - -#: ../../contributing/build-vyos.rst:772 c480920ab1f5426eaf8983d73d3190b2 -msgid "QEMU" -msgstr "" - -#: ../../contributing/build-vyos.rst:774 2a108d6c3e804d0eaa95325f12aaa514 -msgid "Run the following command after building the ISO image." -msgstr "" - -#: ../../contributing/build-vyos.rst:781 0db23ac276b14114b934de5ca75a3247 -msgid "VMware" -msgstr "" - -#: ../../contributing/build-vyos.rst:783 825e9f45a5ac4f1da0948de25c6dc888 -msgid "Run the following command after building the QEMU image." -msgstr "" - -#: ../../contributing/build-vyos.rst:795 bfecae5db1254d4686abf116ac4a761d -msgid "" -"VyOS itself comes with a bunch of packages that are specific to our system " -"and thus cannot be found in any Debian mirror. Those packages can be found " -"at the `VyOS GitHub project`_ in their source format can easily be compiled " -"into a custom Debian (`*.deb`) package." -msgstr "" - -#: ../../contributing/build-vyos.rst:800 ad250e9952604cce8f18577aff2fe5dd -msgid "" -"The easiest way to compile your package is with the above mentioned " -":ref:`build_docker` container, it includes all required dependencies for all" -" VyOS related packages." -msgstr "" - -#: ../../contributing/build-vyos.rst:804 7557ad729d0944729ad7efcc559ca6b3 -msgid "" -"Assume we want to build the vyos-1x package on our own and modify it to our " -"needs. We first need to clone the repository from GitHub." -msgstr "" - -#: ../../contributing/build-vyos.rst:812 c9bd4af0c6864730ac3f1b9783c47f2e -msgid "Build" -msgstr "" - -#: ../../contributing/build-vyos.rst:814 47f948a1262c4b01a4bc222308a3abee -msgid "Launch Docker container and build package" -msgstr "" - -#: ../../contributing/build-vyos.rst:827 677fe0e847b04bdfa0cfc3b3a64ff9a0 -msgid "" -"After a minute or two you will find the generated DEB packages next to the " -"vyos-1x source directory:" -msgstr "" - -#: ../../contributing/build-vyos.rst:837 54fbfde9deac4d58b273469b9ec25d31 -msgid "Install" -msgstr "" - -#: ../../contributing/build-vyos.rst:839 2b42e8916d7a455f84ab2bd89c556b53 -msgid "" -"To take your newly created package on a test drive you can simply SCP it to " -"a running VyOS instance and install the new `*.deb` package over the current" -" running one." -msgstr "" - -#: ../../contributing/build-vyos.rst:843 16e510091299422e952a2fd36740b4e8 -msgid "Just install using the following commands:" -msgstr "" - -#: ../../contributing/build-vyos.rst:854 d9c6c6a8d29f43778d826b759a763067 -msgid "" -"You can also place the generated `*.deb` into your ISO build environment to " -"include it in a custom iso, see :ref:`build_custom_packages` for more " -"information." -msgstr "" - -#: ../../contributing/build-vyos.rst:858 406e3d0896054894af4661516b0e1cc2 -msgid "" -"Any packages in the packages directory will be added to the iso during " -"build, replacing the upstream ones. Make sure you delete them (both the " -"source directories and built deb packages) if you want to build an iso from " -"purely upstream packages." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/debugging.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/debugging.po deleted file mode 100644 index fc42604f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/debugging.po +++ /dev/null @@ -1,310 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/debugging.rst:5 d9abb064d6ec46698758d0f175f7b250 -msgid "Debugging" -msgstr "" - -#: ../../contributing/debugging.rst:7 7fb551891e1a4f0c8ac9917eb715e178 -msgid "" -"There are two flags available to aid in debugging configuration scripts. " -"Since configuration loading issues will manifest during boot, the flags are " -"passed as kernel boot parameters." -msgstr "" - -#: ../../contributing/debugging.rst:12 19772cc03d234060bb88c9b6d1c6ce3a -msgid "ISO image build" -msgstr "" - -#: ../../contributing/debugging.rst:14 c23659ab849a46b59d6b774017f364eb -msgid "" -"When having trouble compiling your own ISO image or debugging Jenkins issues" -" you can follow the steps at :ref:`iso_build_issues`." -msgstr "" - -#: ../../contributing/debugging.rst:18 f711dd3a740242ca9155020137c35f77 -msgid "System Startup" -msgstr "" - -#: ../../contributing/debugging.rst:20 1954ad919001400681578eed03136e5e -msgid "" -"The system startup can be debugged (like loading in the configuration file " -"from ``/config/config.boot``. This can be achieve by extending the Kernel " -"command-line in the bootloader." -msgstr "" - -#: ../../contributing/debugging.rst:25 f865988e532244acbdfb851b45b734a2 -msgid "Kernel" -msgstr "" - -#: ../../contributing/debugging.rst:27 7917e5ed63eb4ebbb3632ace2f89edd8 -msgid "" -"``vyos-debug`` - Adding the parameter to the linux boot line will produce " -"timing results for the execution of scripts during commit. If one is seeing " -"an unexpected delay during manual or boot commit, this may be useful in " -"identifying bottlenecks. The internal flag is ``VYOS_DEBUG``, and is found " -"in vyatta-cfg_. Output is directed to ``/var/log/vyatta/cfg-stdout.log``." -msgstr "" - -#: ../../contributing/debugging.rst:33 bc15a266694b4c6c9b9e1c7bf9996f1c -msgid "" -"``vyos-config-debug`` - During development, coding errors can lead to a " -"commit failure on boot, possibly resulting in a failed initialization of the" -" CLI. In this circumstance, the kernel boot parameter ``vyos-config-debug`` " -"will ensure access to the system as user ``vyos``, and will log a Python " -"stack trace to the file ``/tmp/boot-config-trace``. File ``boot-config-" -"trace`` will generate only if config loaded with a failure status." -msgstr "" - -#: ../../contributing/debugging.rst:42 927250c6b0fb4a99a77084985694f7c8 -msgid "Live System" -msgstr "" - -#: ../../contributing/debugging.rst:44 12a2672d770344088afbffa70ffc74cc -msgid "" -"A number of flags can be set up to change the behaviour of VyOS at runtime. " -"These flags can be toggled using either environment variables or creating " -"files." -msgstr "" - -#: ../../contributing/debugging.rst:48 b29d56dc00ec4533b6636c8778d70099 -msgid "" -"For each feature, a file called ``vyos.feature.debug`` can be created to " -"toggle the feature on. If a parameter is required it can be placed inside " -"the file as its first line." -msgstr "" - -#: ../../contributing/debugging.rst:52 e466228a7cae4312883ae8bbefa4fdf5 -msgid "" -"The file can be placed in ``/tmp`` for one time debugging (as the file will " -"be removed on reboot) or placed in '/config' to stay permanently." -msgstr "" - -#: ../../contributing/debugging.rst:55 f370c2cf80634831956e8734a9ae24b1 -msgid "" -"For example, ``/tmp/vyos.ifconfig.debug`` can be created to enable interface" -" debugging." -msgstr "" - -#: ../../contributing/debugging.rst:58 e71ea39e57f54e92b55270142994fc09 -msgid "" -"It is also possible to set up the debugging using environment variables. In " -"that case, the name will be (in uppercase) VYOS_FEATURE_DEBUG." -msgstr "" - -#: ../../contributing/debugging.rst:61 cb30841880024964a3fcbf7b9fdd0946 -msgid "" -"For example running, ``export VYOS_IFCONFIG_DEBUG=\"\"`` on your vbash, will" -" have the same effect as ``touch /tmp/vyos.ifconfig.debug``." -msgstr "" - -#: ../../contributing/debugging.rst:64 731e8847dcd44bfe92fdda526ff194b4 -msgid "" -"``ifconfig`` - Once set, all commands used, and their responses received " -"from the OS, will be presented on the screen for inspection." -msgstr "" - -#: ../../contributing/debugging.rst:67 27e26aae8d964b249b9a190ef75da061 -msgid "" -"``command`` - Once set, all commands used, and their responses received from" -" the OS, will be presented on the screen for inspection." -msgstr "" - -#: ../../contributing/debugging.rst:70 5ef22224a4fc44e2a79717a9a957ca1d -msgid "" -"``developer`` - Should a command fail, instead of printing a message to the " -"user explaining how to report issues, the python interpreter will start a " -"PBD post-mortem session to allow the developer to debug the issue. As the " -"debugger will wait from input from the developer, it has the capacity to " -"prevent a router to boot and therefore should only be permanently set up on " -"production if you are ready to see the OS fail to boot." -msgstr "" - -#: ../../contributing/debugging.rst:77 18e8907f0d36479ea5161e45c5ec576d -msgid "" -"``log`` - In some rare cases, it may be useful to see what the OS is doing, " -"including during boot. This option sends all commands used by VyOS to a " -"file. The default file is ``/tmp/full-log`` but it can be changed." -msgstr "" - -#: ../../contributing/debugging.rst:81 e8bcb010512d4fba8d59c97d869321a7 -msgid "" -"In order to retrieve the debug output on the command-line you need to " -"disable ``vyos-configd`` in addition. This can be run either one-time by " -"calling ``sudo systemctl stop vyos-configd`` or make this reboot-safe by " -"calling ``sudo systemctl disable vyos-configd``." -msgstr "" - -#: ../../contributing/debugging.rst:87 867c3d7496274fe79c97081b7e704248 -msgid "FRR" -msgstr "" - -#: ../../contributing/debugging.rst:89 812b9cd9ae6e4a4fb2c73eedea6b7b49 -msgid "" -"Recent versions use the ``vyos.frr`` framework. The Python class is located " -"inside our ``vyos-1x:python/vyos/frr.py``. It comes with an embedded " -"debugging/ (print style) debugger as vyos.ifconfig does." -msgstr "" - -#: ../../contributing/debugging.rst:93 038ea4d82d7d4c918310759e41c190e5 -msgid "To enable debugging just run: ``$ touch /tmp/vyos.frr.debug``" -msgstr "" - -#: ../../contributing/debugging.rst:96 dceda9b7f48d4884a1e0a004b936eb7c -msgid "Debugging Python Code with PDB" -msgstr "" - -#: ../../contributing/debugging.rst:98 cd88176ad7d142448cf6ac2d8e455e39 -msgid "" -"Sometimes it might be useful to debug Python code interactively on the live " -"system rather than a IDE. This can be achieved using pdb." -msgstr "" - -#: ../../contributing/debugging.rst:101 c07c3d6e486c44669f5b3b3ec8ca96f1 -msgid "" -"Let us assume you want to debug a Python script that is called by an op-mode" -" command. After you found the script by looking up the op-mode-defitions you" -" can edit the script in the live system using e.g. vi: ``vi " -"/usr/libexec/vyos/op_mode/show_xyz.py``" -msgstr "" - -#: ../../contributing/debugging.rst:106 514228796e6c40b0b3256acb705bfcc2 -msgid "" -"Insert the following statement right before the section where you want to " -"investigate a problem (e.g. a statement you see in a backtrace): ``import " -"pdb; pdb.set_trace()`` Optionally you can surrounded this statement by an " -"``if`` which only triggers under the condition you are interested in." -msgstr "" - -#: ../../contributing/debugging.rst:112 c4311e64a9744e4080d75c4c5db2b92d -msgid "" -"Once you run ``show xyz`` and your condition is triggered you should be " -"dropped into the python debugger:" -msgstr "" - -#: ../../contributing/debugging.rst:122 dc107ce6ee184239bafa54bdd9d70500 -msgid "" -"You can type ``help`` to get an overview of the available commands, and " -"``help command`` to get more information on each command." -msgstr "" - -#: ../../contributing/debugging.rst:125 6f979c80ad2c4e72a1b51dca2d47d967 -msgid "Useful commands are:" -msgstr "" - -#: ../../contributing/debugging.rst:127 88b8de755a664a7498ec6fc3ff4cf17c -msgid "examine variables using ``pp(var)``" -msgstr "" - -#: ../../contributing/debugging.rst:128 e507a6e6fe2f453bae93a6ff56230a2c -msgid "contine execution using ``cont``" -msgstr "" - -#: ../../contributing/debugging.rst:129 916108c9344b4dbdae1c1f711a832939 -msgid "get a backtrace using ``bt``" -msgstr "" - -#: ../../contributing/debugging.rst:132 a9fe7dad4d714d4e8d03e427443b2470 -msgid "Config Migration Scripts" -msgstr "" - -#: ../../contributing/debugging.rst:134 ae021de2a9594b20a143453fe35f91dc -msgid "" -"When writing a new configuration migrator it may happen that you see an " -"error when you try to invoke it manually on a development system. This error" -" will look like:" -msgstr "" - -#: ../../contributing/debugging.rst:148 23268f450e6a4ddcaa2f7d06e3ec5b81 -msgid "" -"The reason is that the configuration migration backend is rewritten and uses" -" a new form of \"magic string\" which is applied on demand when real config " -"migration is run on boot. When runnint individual migrators for testing, you" -" need to convert the \"magic string\" on your own by:" -msgstr "" - -#: ../../contributing/debugging.rst:158 8ea3762fb0844be0882803885c0eda19 -msgid "Configuration Error on System Boot" -msgstr "" - -#: ../../contributing/debugging.rst:160 b5a16f1b27f04b00871631f0b3bde437 -msgid "" -"Beeing brave and running the latest rolling releases will sometimes trigger " -"bugs due to corner cases we missed in our design. Those bugs should be filed" -" via Phabricator_ but you can help us to narrow doen the issue. Login to " -"your VyOS system and change into configuration mode by typing ``configure``." -" Now re-load your boot configuration by simply typing ``load`` followed by " -"return." -msgstr "" - -#: ../../contributing/debugging.rst:166 eb0d350d49b54104b57d23f9e360c7b8 -msgid "" -"You shoudl now see a Python backtrace which will help us to handle the " -"issue, please attach it to the Phabricator_ task." -msgstr "" - -#: ../../contributing/debugging.rst:170 0d4185dd8b384bd281a9bdcb9f6a1cc8 -msgid "Boot Timing" -msgstr "" - -#: ../../contributing/debugging.rst:172 62039345d4e04c6296b6e614a2f5c333 -msgid "" -"During the migration and extensive rewrite of functionality from Perl into " -"Python a significant increase in the overall system boottime was noticed. " -"The system boot time can be analysed and a graph can be generated in the end" -" which shows in detail who called whom during the system startup phase." -msgstr "" - -#: ../../contributing/debugging.rst:177 9817ac9f29a5498c973c3a224f01dc7f -msgid "" -"This is done by utilizing the ``systemd-bootchart`` package which is now " -"installed by default on the VyOS 1.3 (equuleus) branch. The configuration is" -" also versioned so we get comparable results. ``systemd-bootchart`` is " -"configured using this file: bootchart.conf_" -msgstr "" - -#: ../../contributing/debugging.rst:182 556676d2db2c4b3c82dee76fa99d570b -msgid "" -"To enable boot time graphing change the Kernel commandline and add the " -"folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" -msgstr "" - -#: ../../contributing/debugging.rst:185 d946cf69e7364195b4a57b9743dc0a8a -msgid "This can also be done permanently by changing ``/boot/grub/grub.cfg``." -msgstr "" - -#: ../../contributing/debugging.rst:188 11ace3b44bff4e62b514f7e511f19bb8 -msgid "Priorities" -msgstr "" - -#: ../../contributing/debugging.rst:190 4383613095884c7e96f71695b1575997 -msgid "" -"VyOS CLI is all about priorities. Every CLI node has a corresponding " -"``node.def`` file and possibly an attached script that is executed when the " -"node is present. Nodes can have a priority, and on system bootup - or any " -"other ``commit`` to the config all scripts are executed from lowest to " -"higest priority. This is good as this gives a deterministic behavior." -msgstr "" - -#: ../../contributing/debugging.rst:196 6236dba2871a4a6b85a73550abc56e8d -msgid "" -"To debug issues in priorities or to see what's going on in the background " -"you can use the ``/opt/vyatta/sbin/priority.pl`` script which lists to you " -"the execution order of the scripts." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/development.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/development.po deleted file mode 100644 index b92c397b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/development.po +++ /dev/null @@ -1,1019 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/development.rst:5 13f6a7fcaf664b70b688682893ae0e83 -msgid "Development" -msgstr "" - -#: ../../contributing/development.rst:7 bca53b364a914bce877b500ae541ff18 -msgid "" -"All VyOS source code is hosted on GitHub under the VyOS organization which " -"can be found here: https://github.com/vyos" -msgstr "" - -#: ../../contributing/development.rst:10 33a075fffdd64ce491df5c96ef021c4f -msgid "" -"Our code is split into several modules. VyOS is composed of multiple " -"individual packages, some of them are forks of upstream packages and are " -"periodically synced with upstream, so keeping the whole source under a " -"single repository would be very inconvenient and slow. There is now an " -"ongoing effort to consolidate all VyOS-specific framework/config packages " -"into vyos-1x package, but the basic structure is going to stay the same, " -"just with fewer and fewer packages while the base code is rewritten from " -"Perl/BASH into Python using and XML based interface definition for the CLI." -msgstr "" - -#: ../../contributing/development.rst:19 495a976e071d4dd69db319e18c61b25c -msgid "" -"The repository that contains all the ISO build scripts is: " -"https://github.com/vyos/vyos-build" -msgstr "" - -#: ../../contributing/development.rst:22 89dd9bf9c5ee41e19e60ab3f5da1a8bc -msgid "" -"The README.md file will guide you to use the this top level repository." -msgstr "" - -#: ../../contributing/development.rst:25 6e4a1b07b19e4427befa188a40f6a904 -msgid "Submit a Patch" -msgstr "" - -#: ../../contributing/development.rst:27 0f4667f35277442aaaae849d2e67af0d -msgid "" -"Patches are always more than welcome. To have a clean and easy to maintain " -"repository we have some guidelines when working with Git. A clean repository" -" eases the automatic generation of a changelog file." -msgstr "" - -#: ../../contributing/development.rst:31 6132f60414b14d07be6626db55d39c96 -msgid "" -"A good approach for writing commit messages is actually to have a look at " -"the file(s) history by invoking ``git log path/to/file.txt``." -msgstr "" - -#: ../../contributing/development.rst:37 c5541522f1854c0a89696d4bdac27d43 -msgid "Prepare patch/commit" -msgstr "" - -#: ../../contributing/development.rst:39 567f89dd00c545d3b940d01e0240f85c -msgid "" -"In a big system, such as VyOS, that is comprised of multiple components, " -"it's impossible to keep track of all the changes and bugs/feature requests " -"in one's head. We use a bugtracker known as Phabricator_ for it (\"issue " -"tracker\" would be a better term, but this one stuck)." -msgstr "" - -#: ../../contributing/development.rst:44 4c02c609c4364dcbaf99318a1b0de8e5 -msgid "The information is used in three ways:" -msgstr "" - -#: ../../contributing/development.rst:46 182bf37a0da641da9e72c341a930313e -msgid "" -"Keep track of the progress (what we've already done in this branch and what " -"we still need to do)." -msgstr "" - -#: ../../contributing/development.rst:49 3441bca232f341cd9fd36ded1b8a7d9a -msgid "Prepare release notes for upcoming releases" -msgstr "" - -#: ../../contributing/development.rst:51 dd91874c6e484dffbb9f007186e77068 -msgid "" -"Help future maintainers of VyOS (it could be you!) to find out why certain " -"things have been changed in the codebase or why certain features have been " -"added" -msgstr "" - -#: ../../contributing/development.rst:55 3d262f62e2824207a5336028aacbb014 -msgid "" -"To make this approach work, every change must be associated with a task " -"number (prefixed with **T**) and a component. If there is no bug " -"report/feature request for the changes you are going to make, you have to " -"create a Phabricator_ task first. Once there is an entry in Phabricator_, " -"you should reference its id in your commit message, as shown below:" -msgstr "" - -#: ../../contributing/development.rst:61 47e4acaf426145008b6fd8ab91bd82fa -msgid "``ddclient: T1030: auto create runtime directories``" -msgstr "" - -#: ../../contributing/development.rst:62 3c338c90678541c591296fd27890f079 -msgid "``Jenkins: add current Git commit ID to build description``" -msgstr "" - -#: ../../contributing/development.rst:64 c7830178939b4a0189fcc2f20822ebd3 -msgid "" -"If there is no Phabricator_ reference in the commits of your pull request, " -"we have to ask you to amend the commit message. Otherwise we will have to " -"reject it." -msgstr "" - -#: ../../contributing/development.rst:69 ed8e41d2420a401092165cce77771c92 -msgid "Writing good commit messages" -msgstr "" - -#: ../../contributing/development.rst:71 84ed04eae60d4146ae29846f909fcd4c -msgid "" -"The format should be and is inspired by: https://git-scm.com/book/ch5-2.html" -" It is also worth reading https://chris.beams.io/posts/git-commit/" -msgstr "" - -#: ../../contributing/development.rst:74 a534e6ffa0414c95943fd95381621982 -msgid "" -"A single, short, summary of the commit (recommended 50 characters or less, " -"not exceeding 80 characters) containing a prefix of the changed component " -"and the corresponding Phabricator_ reference e.g. ``snmp: T1111:`` or " -"``ethernet: T2222:`` - multiple components could be concatenated as in " -"``snmp: ethernet: T3333``" -msgstr "" - -#: ../../contributing/development.rst:80 6b72dc852a05479b82e4682f7aa54cba -msgid "" -"In some contexts, the first line is treated as the subject of an email and " -"the rest of the text as the body. The blank line separating the summary from" -" the body is critical (unless you omit the body entirely); tools like rebase" -" can get confused if you run the two together." -msgstr "" - -#: ../../contributing/development.rst:85 f5af85d4f0434ac6acb2329942d002e8 -msgid "Followed by a message which describes all the details like:" -msgstr "" - -#: ../../contributing/development.rst:87 5770782710354b32a60879e0166ef185 -msgid "" -"What/why/how something has been changed, makes everyone's life easier when " -"working with `git bisect`" -msgstr "" - -#: ../../contributing/development.rst:90 d409491e1b0b4fa1b7786c2353c56400 -msgid "" -"All text of the commit message should be wrapped at 72 characters if " -"possible which makes reading commit logs easier with ``git log`` on a " -"standard terminal (which happens to be 80x25)" -msgstr "" - -#: ../../contributing/development.rst:94 7aaf86fe66e8470584b71ef895e7a273 -msgid "" -"If applicable a reference to a previous commit should be made linking those " -"commits nicely when browsing the history: ``After commit abcd12ef (\"snmp: " -"this is a headline\") a Python import statement is missing, throwing the " -"following exception: ABCDEF``" -msgstr "" - -#: ../../contributing/development.rst:99 1ea5d06d73934128aa343519d5697279 -msgid "" -"Always use the ``-x`` option to the ``git cherry-pick`` command when back or" -" forward porting an individual commit. This automatically appends the line: " -"``(cherry picked from commit <ID>)`` to the original authors commit message " -"making it easier when bisecting problems." -msgstr "" - -#: ../../contributing/development.rst:104 b8149340cde0423fbd040efaab204019 -msgid "" -"Every change set must be consistent (self containing)! Do not fix multiple " -"bugs in a single commit. If you already worked on multiple fixes in the same" -" file use `git add --patch` to only add the parts related to the one issue " -"into your upcoming commit." -msgstr "" - -#: ../../contributing/development.rst:109 5ef784f4960e4a82a5bddaa415944c61 -msgid "Limits:" -msgstr "" - -#: ../../contributing/development.rst:111 112a6d6a4c8c4d32b0e052cf60e26573 -msgid "" -"We only accept bugfixes in packages other than " -"https://github.com/vyos/vyos-1x as no new functionality should use the old " -"style templates (``node.def`` and Perl/BASH code. Use the new style " -"XML/Python interface instead." -msgstr "" - -#: ../../contributing/development.rst:115 b0bb964fb0764e2f9f958335ea287868 -msgid "" -"Please submit your patches using the well-known GitHub pull-request against " -"our repositories found in the VyOS GitHub organisation at " -"https://github.com/vyos" -msgstr "" - -#: ../../contributing/development.rst:120 c38eca26eca14a4daf60ac8dc815cc5b -msgid "Determinine source package" -msgstr "" - -#: ../../contributing/development.rst:122 3ac68249f169449ebffe37b33abac85a -msgid "" -"Suppose you want to make a change in the webproxy script but yet you do not " -"know which of the many VyOS packages ship this file. You can determine the " -"VyOS package name in question by using Debian's ``dpkg -S`` command of your " -"running VyOS installation." -msgstr "" - -#: ../../contributing/development.rst:132 09de05f3b665422cab77b5808e5b2585 -msgid "" -"This means the file in question (``/opt/vyatta/sbin/vyatta-update-" -"webproxy.pl``) is located in the ``vyatta-webproxy`` package which can be " -"found here: https://github.com/vyos/vyatta-webproxy" -msgstr "" - -#: ../../contributing/development.rst:138 abf1cbb03527490db9d36348be3f9fb7 -msgid "Fork Repository and submit Patch" -msgstr "" - -#: ../../contributing/development.rst:140 cf2f695e771e4da7afcbe7f4e6be4764 -msgid "" -"Forking the repository and submitting a GitHub pull-request is the preferred" -" way of submitting your changes to VyOS. You can fork any VyOS repository to" -" your very own GitHub account by just appending ``/fork`` to any " -"repository's URL on GitHub. To e.g. fork the ``vyos-1x`` repository, open " -"the following URL in your favourite browser: " -"https://github.com/vyos/vyos-1x/fork" -msgstr "" - -#: ../../contributing/development.rst:146 47d1dec79b274c96bae18c564fffc8d4 -msgid "" -"You then can proceed with cloning your fork or add a new remote to your " -"local repository:" -msgstr "" - -#: ../../contributing/development.rst:149 473607ea52524136bd35ff89877b461d -msgid "Clone: ``git clone https://github.com/<user>/vyos-1x.git``" -msgstr "" - -#: ../../contributing/development.rst:151 eb23e4735532454a812e977f4e1f64e0 -msgid "Fork: ``git remote add myfork https://github.com/<user>/vyos-1x.git``" -msgstr "" - -#: ../../contributing/development.rst:153 51a8dee2722546f5a1a8b841bf0d47d1 -msgid "" -"In order to record you as the author of the fix please identify yourself to " -"Git by setting up your name and email. This can be done local for this one " -"and only repository ``git config`` or globally using ``git config " -"--global``." -msgstr "" - -#: ../../contributing/development.rst:162 08945358e29443e1b768547e707f4dff -msgid "" -"Make your changes and save them. Do the following for all changes files to " -"record them in your created Git commit:" -msgstr "" - -#: ../../contributing/development.rst:165 be8ecf3e5c9242b0be78f476cb82ca8f -msgid "" -"Add file to Git index using ``git add myfile``, or for a whole directory: " -"``git add somedir/*``" -msgstr "" - -#: ../../contributing/development.rst:168 29625b4d7af94c28a91c85596b4cb1de -msgid "" -"Commit the changes by calling ``git commit``. Please use a meaningful commit" -" headline (read above) and don't forget to reference the Phabricator_ ID." -msgstr "" - -#: ../../contributing/development.rst:171 48466af0f86c48b096143233ded58de4 -msgid "Submit the patch ``git push`` and create the GitHub pull-request." -msgstr "" - -#: ../../contributing/development.rst:175 36bcc1288264449a8bad68f6e2565f80 -msgid "Attach patch to Phabricator task" -msgstr "" - -#: ../../contributing/development.rst:177 ae16033e6e7c4914aa0406204a1591f5 -msgid "" -"Follow the above steps on how to \"Fork repository to submit a Patch\". " -"Instead of uploading \"pushing\" your changes to GitHub you can export the " -"patches/ commits and send it to maintainers@vyos.net or attach it directly " -"to the bug (preferred over email)" -msgstr "" - -#: ../../contributing/development.rst:182 6fe17a5c6e0f48ca809ad82aaab5d704 -msgid "" -"Export last commit to patch file: ``git format-patch`` or export the last " -"two commits into its appropriate patch files: ``git format-patch -2``" -msgstr "" - -#: ../../contributing/development.rst:187 7200a007c67c4e238e709557dcea986a -msgid "Coding Guidelines" -msgstr "" - -#: ../../contributing/development.rst:189 962d647556e8434c93a1e524737691c2 -msgid "" -"Like any other project we have some small guidelines about our source code, " -"too. The rules we have are not there to punish you - the rules are in place " -"to help us all. By having a consistent coding style it becomes very easy for" -" new and also longtime contributors to navigate through the sources and all " -"the implied logic of any one source file.." -msgstr "" - -#: ../../contributing/development.rst:195 8702ba3737a94b18902caf95e9c3f75e -msgid "" -"Python 3 **shall** be used. How long can we keep Python 2 alive anyway? No " -"considerations for Python 2 compatibility **should** be taken at any time." -msgstr "" - -#: ../../contributing/development.rst:200 bf829c06036e44e29a94a0109251e344 -msgid "Formatting" -msgstr "" - -#: ../../contributing/development.rst:202 c3cbbf35ce07497ca96a4c1e1a543730 -msgid "" -"Python: Tabs **shall not** be used. Every indentation level should be 4 " -"spaces" -msgstr "" - -#: ../../contributing/development.rst:203 0edd04481e594ff09ee893c010cd881e -msgid "" -"XML: Tabs **shall not** be used. Every indentation level should be 2 spaces" -msgstr "" - -#: ../../contributing/development.rst:205 f201706450d645999e1edd4c2558bce9 -msgid "" -"There are extensions to e.g. VIM (xmllint) which will help you to get your " -"indention levels correct. Add to following to your .vimrc file: ``au " -"FileType xml setlocal equalprg=xmllint\\ --format\\ --recover\\ -\\ " -"2>/dev/null`` now you can call the linter using ``gg=G`` in command mode." -msgstr "" - -#: ../../contributing/development.rst:212 660e9fc0c3ab489392b6ec6ab967a33b -msgid "Text generation" -msgstr "" - -#: ../../contributing/development.rst:214 a46c47306cf44f3fa51fb0e183d33d60 -msgid "" -"Template processor **should** be used for generating config files. Built-in " -"string formatting **may** be used for simple line-oriented formats where " -"every line is self-contained, such as iptables rules. Template processor " -"**must** be used for structured, multi-line formats such as those used by " -"ISC DHCPd." -msgstr "" - -#: ../../contributing/development.rst:219 f97220818b4f4d38bc701b54beb1f26e -msgid "The default template processor for VyOS code is Jinja2_." -msgstr "" - -#: ../../contributing/development.rst:223 c70da7d925ae4993834091de6a0dc12b -msgid "Summary" -msgstr "" - -#: ../../contributing/development.rst:225 cc3153e1c9bf4429ae228461552f1b13 -msgid "" -"When modifying the source code, remember these rules of the legacy " -"elimination campaign:" -msgstr "" - -#: ../../contributing/development.rst:228 d65f761886d94c4486c6286959ae4bb1 -msgid "No new features in Perl" -msgstr "" - -#: ../../contributing/development.rst:229 b551d79de6b34b199e66e99ac128e3e2 -msgid "No old style command definitions" -msgstr "" - -#: ../../contributing/development.rst:230 52734945788945b69e2fe8834950a01c -msgid "No code incompatible with Python3" -msgstr "" - -#: ../../contributing/development.rst:234 c9418116422b4b579870438fdd2830d6 -msgid "Python" -msgstr "" - -#: ../../contributing/development.rst:236 ec8641ba5d0d4d9980b63b5d9e90345d -msgid "" -"The switch to the Python programming language for new code is not merely a " -"change of the language, but a chance to rethink and improve the programming " -"approach." -msgstr "" - -#: ../../contributing/development.rst:240 53852f2af01f40039b618f0bd0dec169 -msgid "" -"Let's face it: VyOS is full of spaghetti code where logic for reading the " -"VyOS config, generating daemon configs, and restarting processes is all " -"mixed up." -msgstr "" - -#: ../../contributing/development.rst:243 15a4a1df6d5c466889aebfed7616c29f -msgid "" -"Python (or any other language, for that matter) does not provide automatic " -"protection from bad design, so we need to also devise design guidelines and " -"follow them to keep the system extensible and maintainable." -msgstr "" - -#: ../../contributing/development.rst:247 b444574c9f1f48d79335a6a87f6289d1 -msgid "" -"But we are here to assist you and want to guide you through how you can " -"become a good VyOS contributor. The rules we have are not there to punish " -"you - the rules are in place to help us all. What does it mean? By having a " -"consistent coding style it becomes very easy for new contributors and also " -"longtime contributors to navigate through the sources and all the implied " -"logic of the spaghetti code." -msgstr "" - -#: ../../contributing/development.rst:254 5177502a9cd44b96beca39366de4eb20 -msgid "" -"Please use the following template as good starting point when developing new" -" modules or even rewrite a whole bunch of code in the new style XML/Pyhon " -"interface." -msgstr "" - -#: ../../contributing/development.rst:260 26aa43f8ad9e4dbdbdfaa474e66358f8 -msgid "Configuration Script Structure and Behaviour" -msgstr "" - -#: ../../contributing/development.rst:262 2c7cb8e45c9e4ad990aa8e0961958d81 -msgid "" -"Your configuration script or operation mode script which is also written in " -"Python3 should have a line break on 80 characters. This seems to be a bit " -"odd nowadays but as some people also work remotely or program using vi(m) " -"this is a fair good standard which I hope we can rely on." -msgstr "" - -#: ../../contributing/development.rst:267 83c054697c564ea78e266afd9ea4d371 -msgid "" -"In addition this also helps when browsing the GitHub codebase on a mobile " -"device if you happen to be a crazy scientist." -msgstr "" - -#: ../../contributing/development.rst:328 2a7679b8b46543ff801735bf23a2b6a2 -msgid "" -"The ``get_config()`` function must convert the VyOS config to an abstract, " -"internal representation. No other function is allowed to call the " -"``vyos.config. Config`` object method directly. The rationale for it is that" -" when config reads are mixed with other logic, it's very hard to change the " -"config syntax since you need to weed out every occurrence of the old syntax." -" If syntax-specific code is confined to a single function, the rest of the " -"code can be left untouched as long as the internal representation remains " -"compatible." -msgstr "" - -#: ../../contributing/development.rst:336 6da990d2f8104f1289c1b08c6add7c7a -msgid "" -"Another advantage is testability of the code. Mocking the entire config " -"subsystem is hard, while constructing an internal representation by hand is " -"way simpler." -msgstr "" - -#: ../../contributing/development.rst:340 7e64a2d3f8104a778f29a4017feddc41 -msgid "" -"The ``verify()`` function takes your internal representation of the config " -"and checks if it's valid, otherwise it must raise ``ConfigError`` with an " -"error message that describes the problem and possibly suggests how to fix " -"it. It must not make any changes to the system. The rationale for it is " -"again testability and, in the future when the config backend is ready and " -"every script is rewritten in this fashion, ability to execute commit dry run" -" (\"commit test\" like in JunOS) and abort commit before making any changes " -"to the system if an error is found in any component." -msgstr "" - -#: ../../contributing/development.rst:349 bd667197d6bf44adbcc9eeae47406de5 -msgid "" -"The ``generate()`` function generates config files for system components." -msgstr "" - -#: ../../contributing/development.rst:351 e8d9af1c502e437ba433f3687ffd7ae0 -msgid "" -"The ``apply()`` function applies the generated configuration to the live " -"system. It should use non-disruptive reload whenever possible. It may " -"execute disruptive operations such as daemon process restart if a particular" -" component does not support non-disruptive reload, or when the expected " -"service degradation is minimal (for example, in case of auxiliary services " -"such as LLDPd). In case of high impact services such as VPN daemon and " -"routing protocols, when non- disruptive reload is supported for some but not" -" all types of configuration changes, scripts authors should make effort to " -"determine if a configuration change can be done in a non-disruptive way and " -"only resort to disruptive restart if it cannot be avoided." -msgstr "" - -#: ../../contributing/development.rst:362 976cb9f3d9814554b2d10496826e3078 -msgid "" -"Unless absolutely necessary, configuration scripts should not modify the " -"active configuration of system components directly. Whenever at all " -"possible, scripts should generate a configuration file or files that can be " -"applied with a single command such as reloading a service through systemd " -"init. Inserting statements one by one is particularly discouraged, for " -"example, when configuring netfilter rules, saving them to a file and loading" -" it with iptables-restore should always be preferred to executing iptables " -"directly." -msgstr "" - -#: ../../contributing/development.rst:370 6fe2ed80e6804a4e922703668c95efb8 -msgid "" -"The ``apply()`` and ``generate()`` functions may ``raise ConfigError`` if, " -"for example, the daemon failed to start with the updated config. It " -"shouldn't be a substitute for proper config checking in the ``verify()`` " -"function. All reasonable effort should be made to verify that generated " -"configuration is valid and will be accepted by the daemon, including, when " -"necessary, cross- checks with other VyOS configuration subtrees." -msgstr "" - -#: ../../contributing/development.rst:377 f1efcf352ca74fd99b34a443c1d086ad -msgid "" -"Exceptions, including ``VyOSError`` (which is raised by " -"``vyos.config.Config`` on improper config operations, such as trying to use " -"``list_nodes()`` on a non-tag node) should not be silenced or caught and re-" -"raised as config error. Sure this will not look pretty on user's screen, but" -" it will make way better bug reports, and help users (and most VyOS users " -"are IT professionals) do their own debugging as well." -msgstr "" - -#: ../../contributing/development.rst:384 0c989b22ba6341049eeff36f354faabb -msgid "" -"For easy orientation we suggest you take a look on the ``ntp.py`` or " -"``interfaces-bonding.py`` (for tag nodes) implementation. Both files can be " -"found in the vyos-1x_ repository." -msgstr "" - -#: ../../contributing/development.rst:390 753ac897e3044181977a217d93c293dd -msgid "XML (used for CLI definitions)" -msgstr "" - -#: ../../contributing/development.rst:392 80257fc611834dbba73ec93a5e12124a -msgid "" -"The bash (or better vbash) completion in VyOS is defined in *templates*. " -"Templates are text files (called ``node.def``) stored in a directory tree. " -"The directory names define the command names, and template files define the " -"command behaviour. Before VyOS 1.2 (crux) this files were created by hand. " -"After a complex redesign process_ the new style template are automatically " -"generated from a XML input file." -msgstr "" - -#: ../../contributing/development.rst:399 b957e501d42942e4a5002cafeead50e9 -msgid "" -"XML interface definitions for VyOS come with a RelaxNG schema and are " -"located in the vyos-1x_ module. This schema is a slightly modified schema " -"from VyConf_ alias VyOS 2.0 So VyOS 1.2.x interface definitions will be " -"reusable in Nextgen VyOS Versions with very minimal changes." -msgstr "" - -#: ../../contributing/development.rst:404 87ee6c860692439c85189b514a35064a -msgid "" -"The great thing about schemas is not only that people can know the complete " -"grammar for certain, but also that it can be automatically verified. The " -"`scripts/build-command-templates` script that converts the XML definitions " -"to old style templates also verifies them against the schema, so a bad " -"definition will cause the package build to fail. I do agree that the format " -"is verbose, but there is no other format now that would allow this. Besides," -" a specialized XML editor can alleviate the issue with verbosity." -msgstr "" - -#: ../../contributing/development.rst:412 8ddcf1750176485fa0d58071eadd993e -msgid "Example:" -msgstr "" - -#: ../../contributing/development.rst:490 ecb47c0f1ea9452c842c08e7975d1d9a -msgid "" -"Command definitions are purely declarative, and cannot contain any logic. " -"All logic for generating config files for target applications, restarting " -"services and so on is implemented in configuration scripts instead." -msgstr "" - -#: ../../contributing/development.rst:495 cc22cb46c89c4de19ffb0afb032c3fdb -msgid "GNU Preprocessor" -msgstr "" - -#: ../../contributing/development.rst:497 b7e5943f25fb40f3912acaaf54f35334 -msgid "" -"XML interface definition files use the `xml.in` file extension which was " -"implemented in :vytask:`T1843`. XML interface definitions tend to have a lot" -" of duplicated code in areas such as:" -msgstr "" - -#: ../../contributing/development.rst:501 ab255f82577842e68117818cf6ebbaeb -msgid "VIF (incl. VIF-S/VIF-C)" -msgstr "" - -#: ../../contributing/development.rst:502 b0107af78f194974882efa229e16d549 -msgid "Address" -msgstr "" - -#: ../../contributing/development.rst:503 5e420ecfba134a6c95ee6263a33862c9 -msgid "Description" -msgstr "" - -#: ../../contributing/development.rst:504 8460407ee3f9477ebcc971d5c2ced47d -msgid "Enabled/Disabled" -msgstr "" - -#: ../../contributing/development.rst:506 8610850201c44d678df80cdbb4effc51 -msgid "" -"Instead of supplying all those XML nodes multiple times there are now " -"include files with predefined features. Brief overview:" -msgstr "" - -#: ../../contributing/development.rst:509 36a0a931d83a45829cc8ecc9b09cc96a -msgid "`IPv4, IPv6 and DHCP(v6)`_ address assignment" -msgstr "" - -#: ../../contributing/development.rst:510 def3132d1e21443c85b21dd1fa2f3e6a -msgid "`IPv4, IPv6`_ address assignment" -msgstr "" - -#: ../../contributing/development.rst:511 61ce6f0a4cb3462d8bc48d384b506913 -msgid "`VLAN (VIF)`_ definition" -msgstr "" - -#: ../../contributing/development.rst:512 781e8c44179a431da25e8fe060a04080 -msgid "`MAC address`_ assignment" -msgstr "" - -#: ../../contributing/development.rst:514 067bc714fc1a45de9fcc0a5b009b9d90 -msgid "" -"All interface definition XML input files (.in suffix) will be sent to the " -"GCC preprocess and the output is stored in the `build/interface-definitions`" -" folder. The previously mentioned `scripts/build-command-templates` script " -"operates on the `build/interface-definitions` folder to generate all " -"required CLI nodes." -msgstr "" - -#: ../../contributing/development.rst:535 9be60615915942eeaf9a1e0b049eaf27 -msgid "Guidelines" -msgstr "" - -#: ../../contributing/development.rst:538 14786773fcee449da1c62ba5c1a64a0a -msgid "Use of numbers" -msgstr "" - -#: ../../contributing/development.rst:540 da524dea88274a22832af93181402987 -msgid "" -"Use of numbers in command names **should** be avoided unless a number is a " -"part of a protocol name or similar. Thus, ``protocols ospfv3`` is perfectly " -"fine, but something like ``server-1`` is questionable at best." -msgstr "" - -#: ../../contributing/development.rst:545 8aa1c3880cfc40a3bc1eab5426951cc7 -msgid "Help String" -msgstr "" - -#: ../../contributing/development.rst:547 b5fe3cf51bdc4504a9f20d93a02ffb21 -msgid "" -"To ensure uniform look and feel, and improve readability, we should follow a" -" set of guidelines consistently." -msgstr "" - -#: ../../contributing/development.rst:551 346e85e9486045c086a92ba1ff4064a6 -msgid "Capitalization and punctuation" -msgstr "" - -#: ../../contributing/development.rst:553 5f17c826c42e4d878388bcef714cd361 -msgid "" -"The first word of every help string **must** be capitalized. There **must " -"not** be a period at the end of help strings." -msgstr "" - -#: ../../contributing/development.rst:556 32aebf2319834080a10eb82c4fa3eb5b -msgid "" -"Rationale: this seems to be the unwritten standard in network device CLIs, " -"and a good aesthetic compromise." -msgstr "" - -#: ../../contributing/development.rst:559 -#: ../../contributing/development.rst:571 -#: ../../contributing/development.rst:580 -#: ../../contributing/development.rst:591 -#: ../../contributing/development.rst:602 -#: ../../contributing/development.rst:616 b658373b852b4a609c0134af02aa0c2e -#: b020e944556843c0be34cfa715d51f75 55720daa53754cd992e6a7188b3c98b1 -#: 21c7e859df8f46429e239198ece35d81 3e50eb2086654ad99a7fe20d247d5bd6 -#: fef35b651890497090c26be05c88d465 -msgid "Examples:" -msgstr "" - -#: ../../contributing/development.rst:561 cd0282b12e1547b48638e9b97e797bba -msgid "Good: \"Frobnication algorithm\"" -msgstr "" - -#: ../../contributing/development.rst:562 24a84860978448649189947b280a8e70 -msgid "Bad: \"frobnication algorithm\"" -msgstr "" - -#: ../../contributing/development.rst:563 af8d7ef416ab47dc8b6dc2bde95fb3e9 -msgid "Bad: \"Frobnication algorithm.\"" -msgstr "" - -#: ../../contributing/development.rst:564 f160d2d45016433aaa5e3fbd609c3558 -msgid "Horrible: \"frobnication algorithm.\"" -msgstr "" - -#: ../../contributing/development.rst:567 40e524d8fd2c49d7b34bb899ae644116 -msgid "Use of abbreviations and acronyms" -msgstr "" - -#: ../../contributing/development.rst:569 50af60e0123b458e9fed80ea7be1076c -msgid "Abbreviations and acronyms **must** be capitalized." -msgstr "" - -#: ../../contributing/development.rst:573 -#: ../../contributing/development.rst:604 b0946251124045b6bf97ae3875f948e2 -#: 6a299471787141aaa3a108e2a48f59b1 -msgid "Good: \"TCP connection timeout\"" -msgstr "" - -#: ../../contributing/development.rst:574 8372511294954ee881facc029cdafcb2 -msgid "Bad: \"tcp connection timeout\"" -msgstr "" - -#: ../../contributing/development.rst:575 01429f1227664923acf4a6f149c63e45 -msgid "Horrible: \"Tcp connection timeout\"" -msgstr "" - -#: ../../contributing/development.rst:577 a7f34af1c0154c989e3375aa460e337a -msgid "" -"Acronyms also **must** be capitalized to visually distinguish them from " -"normal words:" -msgstr "" - -#: ../../contributing/development.rst:582 243ffd888b2f4f839b4ce6c6bbbe8ced -msgid "Good: RADIUS (as in remote authentication for dial-in user services)" -msgstr "" - -#: ../../contributing/development.rst:583 d9536a7cef704f19806ff14f207fe5a3 -msgid "" -"Bad: radius (unless it's about the distance between a center of a circle and" -" any of its points)" -msgstr "" - -#: ../../contributing/development.rst:586 598992d29c3948ce8b9daf8136ef6f3e -msgid "" -"Some abbreviations are traditionally written in mixed case. Generally, if it" -" contains words \"over\" or \"version\", the letter **should** be lowercase." -" If there's an accepted spelling (especially if defined by an RFC or another" -" standard), it **must** be followed." -msgstr "" - -#: ../../contributing/development.rst:593 27c7117975c041fdaf4e23e9f07dd527 -msgid "Good: PPPoE, IPsec" -msgstr "" - -#: ../../contributing/development.rst:594 88c045836ff14ecba67f923acfdb69b2 -msgid "Bad: PPPOE, IPSEC" -msgstr "" - -#: ../../contributing/development.rst:595 ff188a95155a4a6d85c440ec112470b3 -msgid "Bad: pppoe, ipsec" -msgstr "" - -#: ../../contributing/development.rst:598 26901f5cbcfc4cfeb69da88966604704 -msgid "Use of verbs" -msgstr "" - -#: ../../contributing/development.rst:600 84ad88808fcd41389ab5a8384be44351 -msgid "Verbs **should** be avoided. If a verb can be omitted, omit it." -msgstr "" - -#: ../../contributing/development.rst:605 5831b1d1b4014dd9aa36d7a64a3c789a -msgid "Bad: \"Set TCP connection timeout\"" -msgstr "" - -#: ../../contributing/development.rst:607 b6ade6844d5647ad97e6856ca1041917 -msgid "" -"If a verb is essential, keep it. For example, in the help text of ``set " -"system ipv6 disable-forwarding``, \"Disable IPv6 forwarding on all " -"interfaces\" is a perfectly justified wording." -msgstr "" - -#: ../../contributing/development.rst:612 b6581bc8632d4b51868fb7bb484d2a2d -msgid "Prefer infinitives" -msgstr "" - -#: ../../contributing/development.rst:614 c0fac675ba34446fb6f8d474ddfdcfd2 -msgid "" -"Verbs, when they are necessary, **should** be in their infinitive form." -msgstr "" - -#: ../../contributing/development.rst:618 39e33e702b2e410ebf16bd02cfb070d3 -msgid "Good: \"Disable IPv6 forwarding\"" -msgstr "" - -#: ../../contributing/development.rst:619 4a2e1fff7f8543b8bbe833f719f226a7 -msgid "Bad: \"Disables IPv6 forwarding\"" -msgstr "" - -#: ../../contributing/development.rst:622 09e1a88b6428413fa6337164fa4871a7 -msgid "Migrating old CLI" -msgstr "" - -#: ../../contributing/development.rst:628 7cc4489e656f403dbf220ae4b79a0b0c -msgid "Old concept/syntax" -msgstr "" - -#: ../../contributing/development.rst:629 f72b04fe25894237a0958a5af8d662f7 -msgid "New syntax" -msgstr "" - -#: ../../contributing/development.rst:630 4325ebdacbc9451bad8ea85c3042e95c -msgid "Notes" -msgstr "" - -#: ../../contributing/development.rst:631 b22ec3d4accd4dabb22f2df06947e955 -msgid "mynode/node.def" -msgstr "" - -#: ../../contributing/development.rst:632 813c64088d3a4faea8df9fe6674c8896 -msgid "<node name=\"mynode\"> </node>" -msgstr "" - -#: ../../contributing/development.rst:633 0cbc70a2a3274db4a02e28acc75595ba -msgid "Leaf nodes (nodes with values) use <leafNode> tag instead" -msgstr "" - -#: ../../contributing/development.rst:634 7ff7be20e53b481a8916e6d09a247075 -msgid "mynode/node.tag , tag:" -msgstr "" - -#: ../../contributing/development.rst:635 d97d99660bb241d5b67e8a512404fd90 -msgid "<tagNode name=\"mynode> </node>" -msgstr "" - -#: ../../contributing/development.rst:637 e3fba8ff692a4819937093306b7bbfa3 -msgid "help: My node" -msgstr "" - -#: ../../contributing/development.rst:638 219da58427f64cf6813b5e62944eef14 -msgid "<properties> <help>My node</help>" -msgstr "" - -#: ../../contributing/development.rst:640 6b1d4eb28c9348f78bad00c0d36d8197 -msgid "val_help: <format>; some string" -msgstr "" - -#: ../../contributing/development.rst:641 b12810695e7a4ca0b5e89f0895691b71 -msgid "" -"<properties> <valueHelp> <format> format </format> <description> some string" -" </description>" -msgstr "" - -#: ../../contributing/development.rst:643 3d228a4ecdda42c5bcac5beda63079d8 -msgid "" -"Do not add angle brackets around the format, they will be inserted " -"automatically" -msgstr "" - -#: ../../contributing/development.rst:645 197955c5e68d4c169c2b3646fe5fab07 -msgid "syntax:expression: pattern" -msgstr "" - -#: ../../contributing/development.rst:646 f54ac7b073ba4aaca03d931f0dafab21 -msgid "<properties> <constraint> <regex> ..." -msgstr "" - -#: ../../contributing/development.rst:647 bb848432f84745389e12d3420fd9b200 -msgid "<constraintErrorMessage> will be displayed on failure" -msgstr "" - -#: ../../contributing/development.rst:648 318f28f6358641319bd6bd73ade0a5ce -msgid "syntax:expression: $VAR(@) in \"foo\", \"bar\", \"baz\"" -msgstr "" - -#: ../../contributing/development.rst:649 -#: ../../contributing/development.rst:656 -#: ../../contributing/development.rst:676 -#: ../../contributing/development.rst:679 -#: ../../contributing/development.rst:682 848f62017cff42f48932eec178fca271 -#: 5409dd2a521b48988e2711e3b1cb9ecb e2b50ef0506242328052488e3c20eef9 -#: 7d71973bda64400db9774df185a7bc69 077c812f057a447bbf7909f4db0f1fee -msgid "None" -msgstr "" - -#: ../../contributing/development.rst:650 f437eb411a6545939babd65caf3d54f8 -msgid "Use regex" -msgstr "" - -#: ../../contributing/development.rst:651 f3226b9b99e94e7c90617691c1b3db82 -msgid "syntax:expression: exec ..." -msgstr "" - -#: ../../contributing/development.rst:652 f0f39c43c9d24035b7799ddee422ec16 -msgid "<properties> <constraint> <validator> <name =\"foo\" argument=\"bar\">" -msgstr "" - -#: ../../contributing/development.rst:653 80caa3fd0b414be5948828228f8f56bc -msgid "" -"\"${vyos_libexecdir}/validators/foo bar $VAR(@)\" will be executed, " -"<constraintErrorMessage> will be displayed on failure" -msgstr "" - -#: ../../contributing/development.rst:655 cfaefb230d494308868c1a2b1ccd0cbd -msgid "syntax:expression: (arithmetic expression)" -msgstr "" - -#: ../../contributing/development.rst:657 12d7c3f6f5674daeaace5931c0ca8efd -msgid "" -"External arithmetic validator may be added if there's demand, complex " -"validation is better left to commit-time scripts" -msgstr "" - -#: ../../contributing/development.rst:659 55a9e6825cf24261909a2a1865bee2a1 -msgid "priority: 999" -msgstr "" - -#: ../../contributing/development.rst:660 359045dbc11949d2846edcbb1823d4b2 -msgid "<properties> <priority>999</priority>" -msgstr "" - -#: ../../contributing/development.rst:661 b35d3f18f65b447baea445023b722c2f -msgid "" -"Please leave a comment explaining why the priority was chosen (e.g. \"after " -"interfaces are configured\")" -msgstr "" - -#: ../../contributing/development.rst:663 f2fc7e7db46d410a8d5a7fd01488447f -msgid "multi:" -msgstr "" - -#: ../../contributing/development.rst:664 a5c47353b4e240a897d9989c6b4cc418 -msgid "<properties> <multi/>" -msgstr "" - -#: ../../contributing/development.rst:665 d22bd39f7baa49ac828aff803f93a5b3 -msgid "Only applicable to leaf nodes" -msgstr "" - -#: ../../contributing/development.rst:666 8b603494e75748a5950b48cf7bdc1e76 -msgid "allowed: echo foo bar" -msgstr "" - -#: ../../contributing/development.rst:667 31b948d3cf3e49aba60122c0e5b18fa7 -msgid "<properties> <completionHelp> <list> foo bar </list>" -msgstr "" - -#: ../../contributing/development.rst:669 ae1fa30e898b4b9880386b11c2656d88 -msgid "allowed: cli-shell-api listNodes vpn ipsec esp-group" -msgstr "" - -#: ../../contributing/development.rst:670 34ff9f59e15f4b0c89fdc50bf26ae5cf -msgid "<properties> <completionHelp> <path> vpn ipsec esp-group </path> ..." -msgstr "" - -#: ../../contributing/development.rst:672 0acda12d528c4983a8bc24e215e2e938 -msgid "allowed: /path/to/script" -msgstr "" - -#: ../../contributing/development.rst:673 e50fd5d7b645484e9f85438fcaeee425 -msgid "<properties> <completionHelp> <script> /path/to/script </script> ..." -msgstr "" - -#: ../../contributing/development.rst:675 88e7993d35574ae28c11ed123d2892d0 -msgid "default:" -msgstr "" - -#: ../../contributing/development.rst:677 989f6e68960c448b9b140d8422bea4c7 -msgid "Move default values to scripts" -msgstr "" - -#: ../../contributing/development.rst:678 1f79f35408e34bd28365ef547a70792b -msgid "commit:expression:" -msgstr "" - -#: ../../contributing/development.rst:680 1a95ffbafac2474cb1822de847539037 -msgid "" -"All commit time checks should be in the verify() function of the script" -msgstr "" - -#: ../../contributing/development.rst:681 6abc6c67084f4588993c0ad9fdf45c6c -msgid "begin:/create:/delete:" -msgstr "" - -#: ../../contributing/development.rst:683 dae250339d384fe998af358aeaa8edc1 -msgid "All logic should be in the scripts" -msgstr "" - -#: ../../contributing/development.rst:686 0a761544b2394577b208ceae0173ee7d -msgid "Continuous Integration" -msgstr "" - -#: ../../contributing/development.rst:688 15570252713643b9b14be94fe82afaf3 -msgid "" -"VyOS makes use of Jenkins_ as our Continuous Integration (CI) service. Our " -"`VyOS CI`_ server is publicly accessible here: https://ci.vyos.net. You can " -"get a brief overview of all required components shipped in a VyOS ISO." -msgstr "" - -#: ../../contributing/development.rst:692 316fa05e045744999e29a99d37461ab6 -msgid "" -"To build our modules we utilize a CI/CD Pipeline script. Each and every VyOS" -" component comes with it's own ``Jenkinsfile`` which is (more or less) a " -"copy. The Pipeline utilizes the Docker container from the :ref:`build_iso` " -"section - but instead of building it from source on every run, we rather " -"always fetch a fresh copy (if needed) from Dockerhub_." -msgstr "" - -#: ../../contributing/development.rst:698 529a7e068b0f411c9e71f107c09baac3 -msgid "" -"Each module is build on demand if a new commit on the branch in question is " -"found. After a successful run the resulting Debian Package(s) will be " -"deployed to our Debian repository which is used during build time. It is " -"located here: http://dev.packages.vyos.net/repositories/." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/issues-features.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/issues-features.po deleted file mode 100644 index 0aba0553..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/issues-features.po +++ /dev/null @@ -1,141 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/issues-features.rst:5 67ed87b152074a30a52d46af521b5ef5 -msgid "Issues/Feature requests" -msgstr "" - -#: ../../contributing/issues-features.rst:10 66cf2839261a4020b3d554105560c21c -msgid "Bug Report/Issue" -msgstr "" - -#: ../../contributing/issues-features.rst:12 7e605712d1664ad5ae7232b6372f5997 -msgid "" -"Issues or bugs are found in any software project. VyOS is not an exception." -msgstr "" - -#: ../../contributing/issues-features.rst:14 771a1b0e62d54ec3bb263a682bbc5df4 -msgid "" -"All issues should be reported to the developers. This lets the developers " -"know what is not working properly. Without this sort of feedback every " -"developer will believe that everything is working correctly." -msgstr "" - -#: ../../contributing/issues-features.rst:19 650c1b3dcd57474db2ecd269b8bb874b -msgid "I have found a bug, what should I do?" -msgstr "" - -#: ../../contributing/issues-features.rst:21 32fce891abf04dbc913dfa89cddea7a4 -msgid "" -"When you believe you have found a bug, it is always a good idea to verify " -"the issue prior to opening a bug request." -msgstr "" - -#: ../../contributing/issues-features.rst:24 adc43f7363c34865a593d8f1c95e87ab -msgid "" -"Consult the documentation_ to ensure that you have configured your system " -"correctly" -msgstr "" - -#: ../../contributing/issues-features.rst:26 d7d0062602d044d1bdb3a2b8b3be7fe5 -msgid "Get community support via Slack_ or our Forum_" -msgstr "" - -#: ../../contributing/issues-features.rst:29 dc5cbde3e57d4f27b2e5d89f5f4a105d -msgid "Ensure the problem is reproducible" -msgstr "" - -#: ../../contributing/issues-features.rst:31 9a7189709ac8461fa72b85625deaa646 -msgid "" -"When you are able to verify that it is actually a bug, spend some time to " -"document how to reproduce the issue. This documentation can be invaluable." -msgstr "" - -#: ../../contributing/issues-features.rst:34 e061de570c9e4ce485cb77ba307960aa -msgid "" -"When you wish to have a developer fix a bug that you found, helping them " -"reproduce the issue is beneficial to everyone. Be sure to include " -"information about the hardware you are using, commands that you were " -"running, any other activities that you may have been doing at the time. This" -" additional information can be very useful." -msgstr "" - -#: ../../contributing/issues-features.rst:40 b70152a95f8e443fbbd256328613dfa4 -msgid "What were you attempting to achieve?" -msgstr "" - -#: ../../contributing/issues-features.rst:41 7affcbd7b6314551adfdb34013ba0222 -msgid "What was the configuration prior to the change?" -msgstr "" - -#: ../../contributing/issues-features.rst:42 dcae4f45bff447fb898f662b3b90cc32 -msgid "" -"What commands did you use? Use e.g. ``run show configuration commands``" -msgstr "" - -#: ../../contributing/issues-features.rst:45 f85302174c954225ab6721e5091ed2f3 -msgid "Include output" -msgstr "" - -#: ../../contributing/issues-features.rst:47 a8fbc693065a4312be095f3823b74bf7 -msgid "" -"The output you get when you find a bug can provide lots of information. If " -"you get an error message on the screen, copy it exactly. Having the exact " -"message can provide detail that the developers can use. Like wise if you " -"have any log messages that also are from the time of the issue, include " -"those. They may also contain information that is helpful for the development" -" team." -msgstr "" - -#: ../../contributing/issues-features.rst:54 b339c27e8fd8412ea0e694d4dc08b799 -msgid "Report a Bug" -msgstr "" - -#: ../../contributing/issues-features.rst:56 90b1d77fbe6c4fc09eda77bd5f518ce4 -msgid "" -"In order to open up a bug-report/feature request you need to create yourself" -" an account on VyOS Phabricator_. On the left side of the specific project " -"(VyOS 1.2 or VyOS 1.3) you will find quick-links for opening a bug-" -"report/feature request." -msgstr "" - -#: ../../contributing/issues-features.rst:61 ff1adaa26a3e485a93296c900310eb54 -msgid "Provide as much information as you can" -msgstr "" - -#: ../../contributing/issues-features.rst:62 b8d57159162a4be3b93be5e59f4c6209 -msgid "Which version of VyOS are you using? ``run show version``" -msgstr "" - -#: ../../contributing/issues-features.rst:63 ad99ad1ff73149518a83f91af52eaf8a -msgid "How can we reproduce this Bug?" -msgstr "" - -#: ../../contributing/issues-features.rst:68 2a4ee93179b843fb8f015b834f353086 -msgid "Feature Request" -msgstr "" - -#: ../../contributing/issues-features.rst:70 13e17cc27e5d42c182a9bdf532a61797 -msgid "" -"You have an idea of how to make VyOS better or you are in need of a specific" -" feature which all users of VyOS would benefit from? To send a feature " -"request please search Phabricator_ if there is already a request pending. " -"You can enhance it or if you don't find one, create a new one by use the " -"quick link in the left side under the specific project." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/testing.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/testing.po deleted file mode 100644 index 7548acdc..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/testing.po +++ /dev/null @@ -1,231 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/testing.rst:5 12f678d43bd94c489aa570e0c4ca556e -msgid "Testing" -msgstr "" - -#: ../../contributing/testing.rst:7 f01ded081f2343928f839bb0cab1db56 -msgid "" -"One of the major advantages introduced in VyOS 1.3 is an autmated test " -"framework. When assembling an ISO image multiple things can go wrong badly " -"and publishing a faulty ISO makes no sense. The user is disappointed by the " -"quality of the image and the developers get flodded with bug reports over " -"and over again." -msgstr "" - -#: ../../contributing/testing.rst:12 0dfb498ddebc4d768ced32229293e682 -msgid "" -"As the VyOS documentation is not only for users but also for the developers " -"- and we keep no secret documentation - this section describes how the " -"automated testing works." -msgstr "" - -#: ../../contributing/testing.rst:17 9dbc2349b1a84132887c40f32c547d70 -msgid "Jenkins CI" -msgstr "" - -#: ../../contributing/testing.rst:19 bc6c0084cd434bf0aab4728193354604 -msgid "" -"Our `VyOS CI`_ system is based on Jenkins and builds all our required " -"packages for VyOS 1.2 to 1.4. In addition to the package build, there is the" -" vyos-build Job which builds and tests the VyOS ISO image which is published" -" after a successfull test drive." -msgstr "" - -#: ../../contributing/testing.rst:24 9b7434772d0a429aaa2938e74a895de1 -msgid "" -"We differentiate in two independent tests, which are both run in parallel by" -" two separate QEmu instances which are launched via ``make test`` and ``make" -" testc`` from within the vyos-build_ repository." -msgstr "" - -#: ../../contributing/testing.rst:29 74b920e0bd134fa988efdec86b23d357 -msgid "Smoketests" -msgstr "" - -#: ../../contributing/testing.rst:31 c12843ff659149af976fdefd7ea393ef -msgid "" -"Smoketests executes predefined VyOS CLI commands and checks if the desired " -"daemon/service configuration is rendert - that is how to put it \"short\"." -msgstr "" - -#: ../../contributing/testing.rst:34 00d52833413c4a318da64b20fc7ba1a7 -msgid "" -"When and ISO image is assembled by the `VyOS CI`_, the ``BUILD_SMOKETEST`` " -"parameter is enabled by default, which will extend the ISO configuration " -"line with the following packages:" -msgstr "" - -#: ../../contributing/testing.rst:44 37eedf5c4a604af781cedd13458f8e5e -msgid "" -"So if you plan to build your own custom ISO image and wan't to make use of " -"our smoketests, ensure that you have the `vyos-1x-smoketest` package " -"installed." -msgstr "" - -#: ../../contributing/testing.rst:47 da014d1914214bcaab3956a92c81bf48 -msgid "" -"The ``make test`` command from the vyos-build_ repository will launch a new " -"QEmu instance and the ISO image is first installed to the virtual harddisk." -msgstr "" - -#: ../../contributing/testing.rst:50 fd8bcaef78c9475e88f07247c4a34e8f -msgid "" -"After its first boot into the newly installed system the main Smoketest " -"script is executed, it can be found here: `/usr/bin/vyos-smoketest`" -msgstr "" - -#: ../../contributing/testing.rst:53 d29e928983634961b080fe7c8604694d -msgid "" -"The script only searches for executable \"test-cases\" under " -"``/usr/libexec/vyos/tests/smoke/cli/`` and executes them one by one." -msgstr "" - -#: ../../contributing/testing.rst:56 a68164b072394a8daf96e84a7a196c0c -msgid "" -"As Smoketests will alter the system configuration and you are logged in " -"remote you may loose your connection to the system." -msgstr "" - -#: ../../contributing/testing.rst:60 14fe375078034abfb14b552724557ae7 -msgid "Manual Smoketest Run" -msgstr "" - -#: ../../contributing/testing.rst:62 48458c32bdd24b839fced729143b04e4 -msgid "" -"On the other hand - as each test is contain in its own file - one can always" -" execute a single Smoketest by hand by simply running the Python test " -"scripts." -msgstr "" - -#: ../../contributing/testing.rst:65 8f9365c2d06f4b818faa18a0951447af -msgid "Example:" -msgstr "" - -#: ../../contributing/testing.rst:90 96a57240744b4485b78bedb198064a87 -msgid "Interface based tests" -msgstr "" - -#: ../../contributing/testing.rst:92 a53042041eaa4a07b44f7fe6a3ca88c8 -msgid "" -"Our smoketests not only test daemons and serives, but also check if what we " -"configure for an interface works. Thus there is a common base classed named:" -" ``base_interfaces_test.py`` which holds all the common code that an " -"interface supports and is tested." -msgstr "" - -#: ../../contributing/testing.rst:97 edc3bb0938f140cd8e9087ce2d0d2adf -msgid "Those common tests consists out of:" -msgstr "" - -#: ../../contributing/testing.rst:99 ff30b0f5d774470b89dea6d5b0a8ecc7 -msgid "Add one or more IP addresses" -msgstr "" - -#: ../../contributing/testing.rst:100 fd357f424d154e57a1d1990529a1e255 -msgid "DHCP client and DHCPv6 prefix delegation" -msgstr "" - -#: ../../contributing/testing.rst:101 24e70da5dff347b6820a175f6bb6a0af -msgid "MTU size" -msgstr "" - -#: ../../contributing/testing.rst:102 1940344c3e8b4f7793780e32ec0f843c -msgid "IP and IPv6 options" -msgstr "" - -#: ../../contributing/testing.rst:103 f7ce56b3c8d042768b32349da21f1cc0 -msgid "Port description" -msgstr "" - -#: ../../contributing/testing.rst:104 c24b306b179e4cfeb1602f4c43e74626 -msgid "Port disable" -msgstr "" - -#: ../../contributing/testing.rst:105 6a744f5f6064443298a29a6c903fd81c -msgid "VLANs (QinQ and regular 802.1q)" -msgstr "" - -#: ../../contributing/testing.rst:106 73bc9780c5694384b0d9f09c24c4daf1 -msgid "..." -msgstr "" - -#: ../../contributing/testing.rst:108 e76b5f62ef9b4d58875686621b54283a -msgid "" -"When you are working on interface configuration and you also wan't to test " -"if the Smoketests pass you would normally loose the remote SSH connection to" -" your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the " -"interface based tests can be called with an environment variable beforehand " -"to limit the number of interfaces used in the test. By default all interface" -" e.g. all Ethernet interfaces are used." -msgstr "" - -#: ../../contributing/testing.rst:147 d1e0e72d711c43679c7f4f07abcd20eb -msgid "" -"This will limit the `bond` interface test to only make use of `eth1` and " -"`eth2` as member ports." -msgstr "" - -#: ../../contributing/testing.rst:151 e0946dbd689b436897ae38ea0620c4d5 -msgid "Config Load Tests" -msgstr "" - -#: ../../contributing/testing.rst:153 15cca66010514b56a714892d1e371145 -msgid "" -"The other part of our tests are called \"config load tests\". The config " -"load tests will load - one after another - arbitrary configuration files to " -"test if the configuration migration scripts work as designed and that a " -"given set of functionality still can be loaded with a fresh VyOS ISO image." -msgstr "" - -#: ../../contributing/testing.rst:158 d71157cea333454fb83ca4420c378fd7 -msgid "" -"The configurations are all derived from production systems and can not only " -"act as a testcase but also as reference if one wants to enable a certain " -"feature. The configurations can be found here: " -"https://github.com/vyos/vyos-1x/tree/current/smoketest/configs" -msgstr "" - -#: ../../contributing/testing.rst:163 db34600555b3424a9b1f086bfc8a2c1a -msgid "" -"The entire test is controlled by the main wrapper script ``/usr/bin/vyos-" -"configtest`` which behaves in the same way as the main smoketest script. It " -"scans the folder for potential configuration files and issues a ``load`` " -"command one after another." -msgstr "" - -#: ../../contributing/testing.rst:168 f205e96b0e574f7aa73a44521ee55ae0 -msgid "Manual config load test" -msgstr "" - -#: ../../contributing/testing.rst:170 87a92c6df15e43ad89c4a07203664740 -msgid "" -"One is not bound to load all configurations one after another but can also " -"load individual test configurations on his own." -msgstr "" - -#: ../../contributing/testing.rst:201 80c566100698466e8a18a599df3a5fa0 -msgid "" -"Some of the configurations have preconditions which need to be met. Those " -"most likely include generation of crypographic keys before the config can be" -" applied - you will get a commit error otherwise. If you are interested how " -"those preconditions are fulfilled check the vyos-build_ repository and the " -"``scripts/check-qemu-install`` file." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/contributing/upstream-packages.po b/docs/_locale/de_DE/LC_MESSAGES/contributing/upstream-packages.po deleted file mode 100644 index e08f47e3..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/contributing/upstream-packages.po +++ /dev/null @@ -1,211 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../contributing/upstream-packages.rst:4 9b4ae0ac1ea24c0ebb7c2ff74c9d87ff -msgid "Upstream packages" -msgstr "" - -#: ../../contributing/upstream-packages.rst:6 a558c26feb7541eba474107211fd1139 -msgid "" -"Many base system packages are pulled straight from Debian's main and contrib" -" repositories, but there are exceptions." -msgstr "" - -#: ../../contributing/upstream-packages.rst:9 c1a0875f437c48bcbfc5bdabc51ae0a9 -msgid "" -"This chapter lists those exceptions and gives you a brief overview what we " -"have done on those packages. If you only want to build yourself a fresh ISO " -"you can completely skip this chapter. It may become interesting once you " -"have a VyOS deep dive." -msgstr "" - -#: ../../contributing/upstream-packages.rst:15 -#: 65b83944a66442f7b7c2899ba488806a -msgid "vyos-netplug" -msgstr "" - -#: ../../contributing/upstream-packages.rst:17 -#: 0d4f8c22ba1c41a59688d8daf4b5cdea -msgid "" -"Due to issues in the upstream version that sometimes set interfaces down, a " -"modified version is used." -msgstr "" - -#: ../../contributing/upstream-packages.rst:20 -#: 183453c93d374021a88b4302f35cd6ef -msgid "The source is located at https://github.com/vyos/vyos-netplug" -msgstr "" - -#: ../../contributing/upstream-packages.rst:22 -#: ae1f220be3fb41698f8f941e8384100c -msgid "" -"In the future, we may switch to using systemd infrastructure instead. " -"Building it doesn't require a special procedure." -msgstr "" - -#: ../../contributing/upstream-packages.rst:26 -#: e2e10b338baf406c884afc2aef56c7b0 -msgid "keepalived" -msgstr "" - -#: ../../contributing/upstream-packages.rst:28 -#: 8b06b5c620734e2aae0aa1117fa2d58f -msgid "" -"Keepalived normally isn't updated to newer feature releases between Debian " -"versions, so we are building it from source." -msgstr "" - -#: ../../contributing/upstream-packages.rst:31 -#: fc8753e785b0479d88f64613b8b333c2 -msgid "" -"Debian does keep their package in git, but it's upstream tarball imported " -"into git without its original commit history. To be able to merge new tags " -"in, we keep a fork of the upstream repository with packaging files imported " -"from Debian at https://github.com/vyos/keepalived-upstream" -msgstr "" - -#: ../../contributing/upstream-packages.rst:37 -#: db84775608f348dbbb6be1fa9a36c613 -msgid "strongswan" -msgstr "" - -#: ../../contributing/upstream-packages.rst:39 -#: 0b59cbc4f5194cd5ad8ce50486351639 -msgid "Our StrongSWAN build differs from the upstream:" -msgstr "" - -#: ../../contributing/upstream-packages.rst:41 -#: 3136121b130a47b0a54e777a1e654824 -msgid "" -"strongswan-nm package build is disabled since we don't use NetworkManager" -msgstr "" - -#: ../../contributing/upstream-packages.rst:42 -#: 3f4bf7625b6543a2b61d21eca1033324 -msgid "Patches for DMVPN are merged in" -msgstr "" - -#: ../../contributing/upstream-packages.rst:44 -#: 3078be3341be468f9a8d521381cfe986 -msgid "The source is at https://github.com/vyos/vyos-strongswan" -msgstr "" - -#: ../../contributing/upstream-packages.rst:46 -#: 821c606accad40ab84f391182fc9ed66 -msgid "" -"DMVPN patches are added by this commit: https://github.com/vyos/vyos-" -"strongswan/commit/1cf12b0f2f921bfc51affa3b81226" -msgstr "" - -#: ../../contributing/upstream-packages.rst:49 -#: a3281c9ed3fb4b409cd1c79493d8177c -msgid "" -"Our op mode scripts use the python-vici module, which is not included in " -"Debian's build, and isn't quite easy to integrate in that build. For this " -"reason we debianize that module by hand now, using this procedure:" -msgstr "" - -#: ../../contributing/upstream-packages.rst:53 -#: 5c6f25aa4b644e349e25cd3880d85c24 -msgid "Install https://pypi.org/project/stdeb/" -msgstr "" - -#: ../../contributing/upstream-packages.rst:54 -#: 0f41c2d30bd049e39b5f7c8e0c487cbb -msgid "`cd vyos-strongswan`" -msgstr "" - -#: ../../contributing/upstream-packages.rst:55 -#: 76a28644f37e4132b58f282541198b7e -msgid "`./configure --enable-python-eggs`" -msgstr "" - -#: ../../contributing/upstream-packages.rst:56 -#: 9e6e31f88f5145b3a2ea81e42e6999ee -msgid "`cd src/libcharon/plugins/vici/python`" -msgstr "" - -#: ../../contributing/upstream-packages.rst:57 -#: 4d878cf8e5aa47a7b873ab8b6aa93071 -msgid "`make`" -msgstr "" - -#: ../../contributing/upstream-packages.rst:58 -#: 292eb22ff927426e859c35e14d46b5b4 -msgid "`python3 setup.py --command-packages=stdeb.command bdist_deb`" -msgstr "" - -#: ../../contributing/upstream-packages.rst:60 -#: 2178b97610de4642ad03b2ebad7aa254 -msgid "The package ends up in deb_dist dir." -msgstr "" - -#: ../../contributing/upstream-packages.rst:63 -#: 32da7f654db94f66bb2b30a74c5f9c9c -msgid "mdns-repeater" -msgstr "" - -#: ../../contributing/upstream-packages.rst:65 -#: ee629cfc4d894707a7ca0501750bedd3 -msgid "" -"This package doesn't exist in Debian. A debianized fork is kept at " -"https://github.com/vyos/mdns-repeater" -msgstr "" - -#: ../../contributing/upstream-packages.rst:68 -#: ../../contributing/upstream-packages.rst:76 -#: 3a3c7365c26b44d5941e3224e6b1012d f4becab36b5e45b88877c38e0f72ccd6 -msgid "No special build procedure is required." -msgstr "" - -#: ../../contributing/upstream-packages.rst:71 -#: aee16c64e47e452c8632bb8b811c0125 -msgid "udp-broadcast-relay" -msgstr "" - -#: ../../contributing/upstream-packages.rst:73 -#: 5f3b26af3a7d418a9a34453d7defbb6c -msgid "" -"This package doesn't exist in Debian. A debianized fork is kept at " -"https://github.com/vyos/udp-broadcast-relay" -msgstr "" - -#: ../../contributing/upstream-packages.rst:79 -#: 635325753817483f956e1daeef70e9ed -msgid "hvinfo" -msgstr "" - -#: ../../contributing/upstream-packages.rst:81 -#: ad10113bf94a43fb8873aa37bb8b3f29 -msgid "" -"A fork with packaging changes for VyOS is kept at " -"https://github.com/vyos/hvinfo" -msgstr "" - -#: ../../contributing/upstream-packages.rst:83 -#: ed8ccc1234b741efb0dc076cc2bfea8f -msgid "The original repo is at https://github.com/dmbaturin/hvinfo" -msgstr "" - -#: ../../contributing/upstream-packages.rst:85 -#: 22d6bd34b22f486dbd103dc1dd969801 -msgid "" -"It's an Ada program and requires GNAT and gprbuild for building, " -"dependencies are properly specified so just follow debuild's suggestions." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/copyright.po b/docs/_locale/de_DE/LC_MESSAGES/copyright.po deleted file mode 100644 index 1b5c3429..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/copyright.po +++ /dev/null @@ -1,49 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:55+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../copyright.md:1 4740f6e030ab4525933b68ca47bce42e -msgid "Copyright Notice" -msgstr "" - -#: ../../copyright.md:3 5ad5d2d6ed62427292e9655cf5a83611 -msgid "Copyright (C) 2018-2022 VyOS maintainers and contributors" -msgstr "" - -#: ../../copyright.md:5 1148abf315254c0eb25b79970999ad8d -msgid "" -"Permission is granted to make and distribute verbatim copies of this manual " -"provided the copyright notice and this permission notice are preserved on " -"all copies." -msgstr "" - -#: ../../copyright.md:9 22005a87cf5041f5815c4261277777e9 -msgid "" -"Permission is granted to copy and distribute modified versions of this " -"manual under the conditions for verbatim copying, provided that the entire " -"resulting derived work is distributed under the terms of a permission notice" -" identical to this one." -msgstr "" - -#: ../../copyright.md:14 ca0620038d744b3abeae3d45e4fee537 -msgid "" -"Permission is granted to copy and distribute translations of this manual " -"into another language, under the above conditions for modified versions, " -"except that this permission notice may be stated in a translation approved " -"by the VyOS maintainers." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/coverage.po b/docs/_locale/de_DE/LC_MESSAGES/coverage.po deleted file mode 100644 index 412bf654..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/coverage.po +++ /dev/null @@ -1,117 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:54+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../coverage.rst:3 ad57df571147462598e56ecbe5bfcd46 -msgid "Coverage" -msgstr "" - -#: ../../coverage.rst:5 4efd99c6d3464ce9843b40b8a0a69afe -msgid "" -"Overview over all commands, which are documented in the ``.. cfgcmd::`` or " -"``.. opcmd::`` Directives." -msgstr "" - -#: ../../coverage.rst:8 faa3b55382014eafb37de91866d31a86 -msgid "" -"The build process take all xml definition files from `vyos-1x " -"<https://github.com/vyos/vyos-1x>`_ and a periodical export of all VyOS " -"commands and extract each leaf command or executable command. After this the" -" commands are compare and shown in the following two tables. The script " -"compare only the fixed part of a command. All varables or values will be " -"erase and then compare:" -msgstr "" - -#: ../../coverage.rst:15 0e20965b4853403bbdec585165733a2a -msgid "for example there are these two commands:" -msgstr "" - -#: ../../coverage.rst:17 bedee26d1be14250904f29bc92753de9 -msgid "" -"documentation: ``interfaces ethernet <interface> address <address | dhcp | " -"dhcpv6>``" -msgstr "" - -#: ../../coverage.rst:19 a8079b9fcf6f459db96d53a59f36e855 -msgid "xml: ``interfaces ethernet <ethernet> address <address>``" -msgstr "" - -#: ../../coverage.rst:20 696d1160a0a34ff3bdc3257869f000c9 -msgid "VyOS: ``interfaces ethernet <text> address <value>``" -msgstr "" - -#: ../../coverage.rst:22 601927718c7d4f238beed0c5eb918d97 -msgid "" -"Now the script earse all in between ``<`` and ``>`` and simply compare the " -"strings." -msgstr "" - -#: ../../coverage.rst:25 21832f1b30434f1da6bd92f2a2a90ad8 -msgid "**There are 3 kind of problems:**" -msgstr "" - -#: ../../coverage.rst:27 d8edc94ed112498ea0ef4e14e8d39c79 -msgid "``Not documented yet``" -msgstr "" - -#: ../../coverage.rst:29 4e6378dbd4c14ced83e0bc0b7d000d7d -msgid "" -"A XML command are not found in ``.. cfgcmd::`` or ``.. opcmd::`` Commands" -msgstr "" - -#: ../../coverage.rst:30 95c0f5795a574dd6b6dc567d4bc810de -msgid "The command should be documented" -msgstr "" - -#: ../../coverage.rst:32 1d603a5cff724e6bb51d58ced4d9a07a -msgid "``Nothing found in XML Definitions``" -msgstr "" - -#: ../../coverage.rst:34 bb8abe4c56df4202ae378bd68c3cd683 -msgid "" -"``.. cfgcmd::`` or ``.. opcmd::`` Command are not found in a XML command" -msgstr "" - -#: ../../coverage.rst:35 ed160abf99ab4dfd83673d6707b76176 -msgid "" -"Maybe the command where changed in the XML Definition, the feature is not " -"anymore in VyOS, or there is a typo" -msgstr "" - -#: ../../coverage.rst:38 6e70ff80d20342b687f5653e0c742404 -msgid "``Nothing found in VyOS``" -msgstr "" - -#: ../../coverage.rst:40 b4df3d5303d44dfa9b464034c6c8981c -msgid "" -"``.. cfgcmd::`` or ``.. opcmd::`` Command are not found in a VyOS command" -msgstr "" - -#: ../../coverage.rst:41 ab7cb7b1fdec457d9ff112da2be60a0e -msgid "" -"Maybe the command where changed, the feature is not anymore in VyOS, or " -"there is a typo" -msgstr "" - -#: ../../coverage.rst:46 06702248c2394b4a86ea357f524bed47 -msgid "Configuration Commands" -msgstr "" - -#: ../../coverage.rst:53 5a9770ca31f64f7d811ff4283c4edad8 -msgid "Operational Commands" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/documentation.po b/docs/_locale/de_DE/LC_MESSAGES/documentation.po deleted file mode 100644 index ea8042d5..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/documentation.po +++ /dev/null @@ -1,575 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:55+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../documentation.rst:7 94964c95ff7d439ea652112198572568 -msgid "Write Documentation" -msgstr "" - -#: ../../documentation.rst:9 3b7e55144593453a9a26923fe4af07fd -msgid "" -"We encourage every VyOS user to help us improve our documentation as we have" -" a deficit like most software projects. This not only helps you when " -"reading but also everyone else." -msgstr "" - -#: ../../documentation.rst:13 95e4fdf1bb5446b4a518da55d6d852c6 -msgid "" -"If you are willing to contribute to our documentation this is the definite " -"guide how to do so." -msgstr "" - -#: ../../documentation.rst:16 ededc47dd4c042239dbf608c66f954dd -msgid "" -"In contrast to submitting code patches, there is no requirement that you " -"open up a Phabricator_ task prior to submitting a Pull-Request to the " -"documentation." -msgstr "" - -#: ../../documentation.rst:20 782eaae7a5d644e19bad45e9076af20e -msgid "" -"VyOS documentation is written in reStructuredText and generated to Read the " -"Docs pages with Sphinx, as per the Python tradition, as well as PDF files " -"for offline use through LaTeX. We welcome all sorts of contributions to the " -"documentation. Not just new additions but also corrections to existing " -"documentation." -msgstr "" - -#: ../../documentation.rst:25 efa2880fb8334caa872042aa612c65e6 -msgid "" -"The documentation source is kept in the Git repository at " -"https://github.com/vyos/vyos-documentation and you can follow the " -"instructions in the README.md_ to build and test your changes." -msgstr "" - -#: ../../documentation.rst:29 3969612f13a74092ba456e01b5f2775b -msgid "" -"You can either install Sphinx (and TeX Live for PDF output) and build the " -"documentation locally, or use the Dockerfile_ to build it in a container." -msgstr "" - -#: ../../documentation.rst:33 f12c9bd0789146b6927342b50643b789 -msgid "Guidelines" -msgstr "" - -#: ../../documentation.rst:35 55bbc87304e44ad9a7ce2d2125f95ab0 -msgid "" -"There are a few things to keep in mind when contributing to the " -"documentation, for the sake of consistency and readability." -msgstr "" - -#: ../../documentation.rst:38 fae514909a9b46119242e33379c9b632 -msgid "" -"Take a look at the :doc:`/documentation` page for an intricate explanation " -"of the documentation process." -msgstr "" - -#: ../../documentation.rst:41 28fc3fcc02a348798eb126a224e07041 -msgid "The following is a quick summary of the rules:" -msgstr "" - -#: ../../documentation.rst:43 b3f38a7e7223447bae8c02e06cc0e102 -msgid "" -"Use American English at all times. It's always a good idea to run your text " -"through a grammar and spell checker, such as `Grammarly`_." -msgstr "" - -#: ../../documentation.rst:45 13aaa37cf1cc4b719eb5c155e51e8d2e -msgid "Don't forget to update ``index.rst`` when adding a new node." -msgstr "" - -#: ../../documentation.rst:46 77b3380c330e4182b2f2d66a05d011ee -msgid "" -"Try not to exceed 80 characters per line, but don't break URLs over this." -msgstr "" - -#: ../../documentation.rst:47 6077a30ed5bd40bbbd999618b230c28c -msgid "" -"Properly quote commands, filenames and brief code snippets with double " -"backticks." -msgstr "" - -#: ../../documentation.rst:48 45b676374e4e454db5a6ea24fdd17982 -msgid "Use literal blocks for longer snippets." -msgstr "" - -#: ../../documentation.rst:49 e4f4d4a80c574b07920f54618feae6b9 -msgid "Leave a newline before and after a header." -msgstr "" - -#: ../../documentation.rst:50 d28915a162f64416a195a7adf1bec625 -msgid "Indent with two spaces." -msgstr "" - -#: ../../documentation.rst:51 84be4f78516a420e96766acf956dd013 -msgid "When in doubt, follow the style of existing documentation." -msgstr "" - -#: ../../documentation.rst:53 5bc1e63a78604c78937ba4206c484dc4 -msgid "" -"And finally, remember that the reStructuredText files aren't exclusively for" -" generating HTML and PDF. They should be human-readable and easily perused " -"from a console." -msgstr "" - -#: ../../documentation.rst:58 c5a11ac11c5745db83c5c2ed36a826ae -msgid "Forking Workflow" -msgstr "" - -#: ../../documentation.rst:60 e1378b2863b0470ca1efa1708ba17e18 -msgid "" -"The Forking Workflow is fundamentally different from other popular Git " -"workflows. Instead of using a single server-side repository to act as the " -"\"central\" codebase, it gives every developer their own server-side " -"repository. This means that each contributor has not one, but two Git " -"repositories: a private local one and a public server-side one." -msgstr "" - -#: ../../documentation.rst:66 5e9cb792bac94393907571454d1afb34 -msgid "" -"The main advantage of the Forking Workflow is that contributions can be " -"integrated without the need for everybody to push to a single central " -"repository. Developers push to their own server-side repositories, and only " -"the project maintainer can push to the official repository. This allows the " -"maintainer to accept commits from any developer without giving them write " -"access to the official codebase." -msgstr "" - -#: ../../documentation.rst:73 b1bfb8e5fc444b75ab56aa02da7cd2ce -msgid "" -"Updates to our documentation should be delivered by a GitHub pull-request. " -"This requires you already have a GitHub account." -msgstr "" - -#: ../../documentation.rst:76 62c01f88d8f445b9a839710637474afa -msgid "" -"Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork" -msgstr "" - -#: ../../documentation.rst:78 bf808d9ed35b472abbed287c8254caba -msgid "" -"Clone fork to local machine, then change to that directory ``$ cd vyos-" -"documentation``" -msgstr "" - -#: ../../documentation.rst:81 c5b19341bfbb49ef85f13de91dcf407e -msgid "" -"Install the requirements ``$ pip install -r requirements.txt`` (or something" -" similar)" -msgstr "" - -#: ../../documentation.rst:84 52e056f411734c0a813394727352608c -msgid "" -"Create a new branch for your work, use a descriptive name of your work: ``$ " -"git checkout -b <branch-name>``" -msgstr "" - -#: ../../documentation.rst:87 ffb8f5590f774000aa35721b83755e09 -msgid "" -"Make all your changes - please keep our commit rules in mind " -"(:ref:`prepare_commit`). This mainly applies to proper commit messages " -"describing your change (how and why). Please check out the documentation of " -"Sphinx-doc_ or reStructuredText_ if you are not familiar with it. This is " -"used for writing our docs. Additional directives how to write in RST can be " -"obtained from reStructuredTextDirectives_." -msgstr "" - -#: ../../documentation.rst:94 b3679b2330164a859572ce47a0514187 -msgid "" -"Check your changes by locally building the documentation ``$ make " -"livehtml``. Sphinx will build the html files in the ``docs/_build`` folder. " -"We provide you with a Docker container for an easy-to-use user experience. " -"Check the README.md_ file of this repository." -msgstr "" - -#: ../../documentation.rst:99 7aefe7e395d648c9bcb4c6de629ab9bd -msgid "" -"View modified files by calling ``$ git status``. You will get an overview of" -" all files modified by you. You can add individual files to the Git Index in" -" the next step." -msgstr "" - -#: ../../documentation.rst:103 15e596bb33174be49011b2652294c899 -msgid "" -"Add modified files to Git index ``$ git add path/to/filename`` or add all " -"unstaged files ``$ git add .``. All files added to the Git index will be " -"part of you following Git commit." -msgstr "" - -#: ../../documentation.rst:107 dc4cf1b118b34639aa4af512d4a97ea3 -msgid "" -"Commit your changes with the message, ``$ git commit -m \"<commit " -"message>\"`` or use ``$ git commit -v`` to have your configured editor " -"launched. You can type in a commit message. Again please make yourself " -"comfortable without rules (:ref:`prepare_commit`)." -msgstr "" - -#: ../../documentation.rst:112 edffb9d383bd4e318339a50b23882152 -msgid "" -"Push commits to your GitHub project: ``$ git push -u origin <branch-name>``" -msgstr "" - -#: ../../documentation.rst:114 36ab7ea3abbc42bbbba40116858ea614 -msgid "" -"Submit pull-request. In GitHub visit the main repository and you should see " -"a banner suggesting to make a pull request. Fill out the form and describe " -"what you do." -msgstr "" - -#: ../../documentation.rst:118 93fc93da17a5470f8d2d27aea68c4f4e -msgid "" -"Once pull requests have been approved, you may want to locally update your " -"forked repository too. First you'll have to add a second remote called " -"`upstream` which points to our main repository. ``$ git remote add upstream " -"https://github.com/vyos/vyos-documentation.git``" -msgstr "" - -#: ../../documentation.rst:123 4cf28b23ad054e3e8bfb11d3f231d1d7 -msgid "Check your configured remote repositories:" -msgstr "" - -#: ../../documentation.rst:133 a99b75cb10e541be9c348b4c2f470942 -msgid "" -"Your remote repo on Github is called ``origin``, while the original repo you" -" have forked is called ``upstream``. Now you can locally update your forked " -"repo." -msgstr "" - -#: ../../documentation.rst:143 ece87fc5565e4380a6d9d86faee1b2cf -msgid "" -"If you also want to update your fork on GitHub, use the following: ``$ git " -"push origin master``" -msgstr "" - -#: ../../documentation.rst:147 96a770c0c6344caf9990a995a0dce07f -msgid "Style Guide" -msgstr "" - -#: ../../documentation.rst:150 ce35171d5abb48f38c630ab183f5d17f -msgid "Formating and Sphinxmarkup" -msgstr "" - -#: ../../documentation.rst:153 180aa5aeaeab4b03b70442e407ef004c -msgid "TOC Level" -msgstr "" - -#: ../../documentation.rst:155 c5a0e8a7d6bb401f9c8db6e86a9ddd25 -msgid "We use the following syntax for Headlines." -msgstr "" - -#: ../../documentation.rst:180 18e9696b72734c4a9447589baff11d98 -msgid "Cross-References" -msgstr "" - -#: ../../documentation.rst:182 afb0da1b9c6b467a97e3ecd28f161264 -msgid "" -"A plugin will be used to generate a reference label for each headline. To " -"reference a page or a section in the documentation use the ``:ref:`` " -"command." -msgstr "" - -#: ../../documentation.rst:186 782d82e3d77242c5b8702dbe9ad9015c -msgid "" -"For example, you want to reference the headline **VLAN** in the " -"**ethernet.rst** page. The plugin generates the label based on the headline " -"and the file path." -msgstr "" - -#: ../../documentation.rst:190 0d809507de9d426fac3b363898ccfb3d -msgid "``:ref:`configuration/interfaces/ethernet:vlan``" -msgstr "" - -#: ../../documentation.rst:192 ad8171eeebd649238dcbb3a710dc5b7e -msgid "to use an alternative hyperlink use it this way:" -msgstr "" - -#: ../../documentation.rst:194 479178da660e48a2921a96eab1814a4c -msgid "``:ref:`Check out VLAN<configuration/interfaces/ethernet:vlan>``" -msgstr "" - -#: ../../documentation.rst:197 480b006d02b84e9a9702e1b54df9f9a2 -msgid "handle build errors" -msgstr "" - -#: ../../documentation.rst:199 98ea702ff805489bb7c3e7ea3b7ae917 -msgid "" -"The plugin will warn on build if a headline has a duplicate name in the same" -" document. To prevent this warning, you have to put a custom link on top of " -"the headline." -msgstr "" - -#: ../../documentation.rst:229 ead0a9ff4939478098a747a716aa97fd -msgid "Address space" -msgstr "" - -#: ../../documentation.rst:231 679cf6c2fc774666b795be27e4ce079c -msgid "" -"Note the following RFCs (:rfc:`5737`, :rfc:`3849`, :rfc:`5389` and " -":rfc:`7042`), which describe the reserved public IP addresses and autonomous" -" system numbers for the documentation:" -msgstr "" - -#: ../../documentation.rst:235 0611f1bd52a24b328cc8b2dd66e293f9 -msgid "``192.0.2.0/24``" -msgstr "" - -#: ../../documentation.rst:236 104be7c19ff3491e8bc325953aee1c8a -msgid "``198.51.100.0/24``" -msgstr "" - -#: ../../documentation.rst:237 942a3d760bec48bfbaae6c1f0a8c113d -msgid "``203.0.113.0/24``" -msgstr "" - -#: ../../documentation.rst:238 c62d58ea9cfa4a35821ba38bc92a9be2 -msgid "``2001:db8::/32``" -msgstr "" - -#: ../../documentation.rst:239 5fd11e6dabd04b95948f356979d12992 -msgid "16bit ASN: ``64496 - 64511``" -msgstr "" - -#: ../../documentation.rst:240 5bf414c887514d96b320efda0fc286da -msgid "32bit ASN: ``65536 - 65551``" -msgstr "" - -#: ../../documentation.rst:241 f5b33645b8124b638f771776a404f0ff -msgid "Unicast MAC Addresses: ``00-53-00`` to ``00-53-FF``" -msgstr "" - -#: ../../documentation.rst:242 a32298f007de4b95a1df392ca3bb0a51 -msgid "Multicast MAC-Addresses: ``90-10-00`` to ``90-10-FF``" -msgstr "" - -#: ../../documentation.rst:244 a666a88a512b4e24a774ae53412b8597 -msgid "Please do not use other public address space." -msgstr "" - -#: ../../documentation.rst:248 4d2d64f1a6ba4bbcbc1c9eda933f1ed9 -msgid "Line length" -msgstr "" - -#: ../../documentation.rst:250 03a4e439a9674a11aacaaacca502c43c -msgid "Limit all lines to a maximum of 80 characters." -msgstr "" - -#: ../../documentation.rst:252 176a3ee3983d42b0bf163974c82f4d30 -msgid "" -"Except in ``.. code-block::`` because it uses the html tag ``<pre>`` and " -"renders the same line format from the source rst file." -msgstr "" - -#: ../../documentation.rst:257 a5ac440b498648d68fbd6b166d70285c -msgid "Autolinter" -msgstr "" - -#: ../../documentation.rst:259 f13fcca1cecc455984fd6ecca63cb04c -msgid "" -"Each GitHub pull request is automatically linted to check the address space " -"and line length." -msgstr "" - -#: ../../documentation.rst:262 cf7badd6f7624ebe8fabfd43921e0362 -msgid "" -"Sometimes it is necessary to provide real IP addresses like in the " -":ref:`examples`. For this, please use the sphinx comment syntax ``.. " -"stop_vyoslinter`` to stop the linter and ``.. start_vyoslinter`` to start." -msgstr "" - -#: ../../documentation.rst:268 3f9fdf47afcc4766b5024f4a5d9f92f9 -msgid "Custom Sphinx-doc Markup" -msgstr "" - -#: ../../documentation.rst:270 d81442f618624c9a9e6d631d76f9cf9c -msgid "" -"Custom commands have been developed for writing the documentation. Please " -"make yourself comfortable with those commands as this eases the way we " -"render the documentation." -msgstr "" - -#: ../../documentation.rst:275 20a6bc0a50b34f608dd1a94b48235e21 -msgid "cfgcmd" -msgstr "" - -#: ../../documentation.rst:277 91902cd7f0bf46efa8aecd511ddd6fd5 -msgid "" -"When documenting CLI commands, use the ``.. cfgcmd::`` directive for all " -"configuration mode commands. An explanation of the described command should " -"be added below this statement. Replace all variable contents with <value> or" -" something similar." -msgstr "" - -#: ../../documentation.rst:282 a833a4416f634f5597b56c19514ac476 -msgid "" -"With those custom commands, it will be possible to render them in a more " -"descriptive way in the resulting HTML/PDF manual." -msgstr "" - -#: ../../documentation.rst:292 d8b6168aee0a46c0ac1d563f5de13f10 -msgid "For an inline configuration level command, use ``:cfgcmd:``" -msgstr "" - -#: ../../documentation.rst:299 445c9bd2dcc948088d46b8e6c1571665 -msgid "" -"To extract a defaultvalue from the XML definitions add a ``:defaultvalue:`` " -"to ``.. cfgcmd::`` directive. To have this feature locally, the vyos-1x " -"submodule must be initialized before. Please be aware to not update the " -"submodule in your PR." -msgstr "" - -#: ../../documentation.rst:314 f1d07cc20de04b2782a21eb9749b2646 -msgid "opcmd" -msgstr "" - -#: ../../documentation.rst:316 6e2d006837434db3b020592720f8d3b6 -msgid "" -"When documenting operational level commands, use the ``.. opcmd::`` " -"directive. An explanation of the described command should be added below " -"this statement." -msgstr "" - -#: ../../documentation.rst:319 bd92a75286674617842d1fa6858d4a9b -msgid "" -"With those custom commands, it is possible to render them in a more " -"descriptive way in the resulting HTML/PDF manual." -msgstr "" - -#: ../../documentation.rst:328 270866faefbe4632884dbf5a930adf40 -msgid "For an inline operational level command, use ``:opcmd:``" -msgstr "" - -#: ../../documentation.rst:335 3429ba857fc24422ad11b75497fefd3a -msgid "cmdinclude" -msgstr "" - -#: ../../documentation.rst:337 00849875c2cd4d2e891a37f401f8158a -msgid "" -"To minimize redundancy, there is a special include directive. It includes a " -"txt file and replace the ``{{ var0 }}`` - ``{{ var9 }}`` with the correct " -"value." -msgstr "" - -#: ../../documentation.rst:346 4b978dc344d24f4a8e1369fc6563ed76 -msgid "the content of interface-address.txt looks like this" -msgstr "" - -#: ../../documentation.rst:373 2ad81153f30a4d9c92ffaca186a6f298 -msgid "vytask" -msgstr "" - -#: ../../documentation.rst:375 3e3f4bdb039a49359509f677749cd471 -msgid "" -"When referencing to VyOS Phabricator Tasks, there is a custom Sphinx Markup " -"command called ``vytask`` that automatically renders to a proper Phabricator" -" URL. This is heavily used in the :ref:`release-notes` section." -msgstr "" - -#: ../../documentation.rst:385 06e68cff507c410a9ce2f9b302b354b6 -msgid "Page content" -msgstr "" - -#: ../../documentation.rst:387 78abdcd7186c46d2b9bc5c0027f6ae6b -msgid "" -"The documentation has 3 different types of pages. The same kind of pages " -"must have the same structure to achieve a recognition factor." -msgstr "" - -#: ../../documentation.rst:390 04e865df23e4415a929390a0f17edf33 -msgid "" -"All RST files must follow the same TOC Level syntax and have to start with" -msgstr "" - -#: ../../documentation.rst:399 49f1322f7fbb4d398926ae2c552de75b -msgid "Configuration mode pages" -msgstr "" - -#: ../../documentation.rst:401 6674bad9eb4c45af81673c89d768f06b -msgid "" -"The configuration mode folder and the articles cover the specific level of " -"the commands. The exact level depends on the command. This should provide " -"stability for URLs used in the forum or blogpost." -msgstr "" - -#: ../../documentation.rst:405 e1f15b8d4b7f44ca8446fd7d94c17ab2 -msgid "For example:" -msgstr "" - -#: ../../documentation.rst:407 c3236f51d7844beb9864e651a2a38dd3 -msgid "``set firewall zone`` is written in ``firewall/zone.rst``" -msgstr "" - -#: ../../documentation.rst:408 d06871e602cd4ebca42768151b6f53fd -msgid "``set interfaces ethernet`` is written in ``interfaces/ethernet.rst``" -msgstr "" - -#: ../../documentation.rst:410 1dcc48cf2c9f47d982ef6d909824ef85 -msgid "" -"The article starts with a short introduction about the command or the " -"technology. Please include some helpful links or background information." -msgstr "" - -#: ../../documentation.rst:413 c0e3c76ac5a0432fa664ffaa22245ad9 -msgid "" -"An optional section follows. Some commands have requirements like compatible" -" hardware (e.g. Wifi) or some commands you have to set before. For example, " -"it is recommended to set a route-map before configuring BGP." -msgstr "" - -#: ../../documentation.rst:417 906906edc5b1476e8e90e47ef6a8cf24 -msgid "" -"In the configuration part of the page, all possible configuration options " -"should be documented. Use ``.. cfgcmd::`` described above." -msgstr "" - -#: ../../documentation.rst:420 e90cb08881db48a1b9ba29d026bd5bf9 -msgid "" -"Related operation command must be documented in the next part of the " -"article. Use ``::opcmd..`` for these commands." -msgstr "" - -#: ../../documentation.rst:423 4f7507f8857d4f61a750aae5e4d19a83 -msgid "" -"If there some troubleshooting guides related to the commands. Explain it in " -"the next optional part." -msgstr "" - -#: ../../documentation.rst:427 efd1894eba394a22a9f1b636f7cb6339 -msgid "Operation mode pages" -msgstr "" - -#: ../../documentation.rst:429 116d1678c2ca4e3cb9c760595291ded3 -msgid "" -"Operation mode commands that do not fit in a related configuration mode " -"command must be documented in this part of the documentation." -msgstr "" - -#: ../../documentation.rst:432 c98b393f766f42808e78d0e60c62b5e9 -msgid "" -"General concepts for troubleshooting and detailed process descriptions " -"belong here." -msgstr "" - -#: ../../documentation.rst:436 88fdcd3b3dcf4161ba5c4bc51922b688 -msgid "Anything else" -msgstr "" - -#: ../../documentation.rst:438 54c4ece207164ff3ab5a1a18245f68e9 -msgid "" -"Anything else that is not a configuration or an operation command has no " -"predefined structure." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/index.po b/docs/_locale/de_DE/LC_MESSAGES/index.po deleted file mode 100644 index 660c439b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/index.po +++ /dev/null @@ -1,128 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -# Translators: -# Robert Göhler, 2022 -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:55+0000\n" -"Last-Translator: Robert Göhler, 2022\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../index.rst:61 -msgid "First Steps" -msgstr "Erste Schritte" - -#: ../../index.rst:70 -msgid "Adminguide" -msgstr "" - -#: ../../index.rst:83 -msgid "Development" -msgstr "" - -#: ../../index.rst:96 -msgid "Misc" -msgstr "" - -#: ../../index.rst:5 027c26e1b9a04df59d4868b9388732b1 -msgid "VyOS User Guide" -msgstr "VyOS Benutzer Dokumentation" - -#: ../../index.rst:11 22d8aeff9ba64e3e98bfa1fc241564e5 -msgid "Get / Build VyOS" -msgstr "" - -#: ../../index.rst:13 265a3e71835b4456884b203c277a1d63 -msgid "" -"Quickly :ref:`Build<contributing/build-vyos:build vyos>` your own Image or " -"take a look at how to :ref:`download<installation/install:download>` a free " -"or supported version." -msgstr "" - -#: ../../index.rst:16 3e4bcd0ab847413ab1a2c24a1aa8f4dc -msgid "Install VyOS" -msgstr "" - -#: ../../index.rst:18 0e40316e794f44dcbf0fddec4bebebeb -msgid "" -"Read about how to install VyOS on :ref:`Bare " -"Metall<installation/install:installation>` or in a :ref:`Virtual " -"Environment<installation/virtual/index:running vyos in virtual " -"environments>` and how to use an image with the usual " -":ref:`cloud<installation/cloud/index:running VyOS in Cloud Environments>` " -"providers" -msgstr "" - -#: ../../index.rst:23 1bd08ec371e6466b940aba4832915858 -msgid "Configuration and Operation" -msgstr "" - -#: ../../index.rst:25 72a1a9df64ed41698187d5ca8ff7c0a1 -msgid "" -"Use the :ref:`Quickstart Guide<quick-start:Quick Start>`, to have a fast " -"overview. Or go deeper and set up :ref:`advanced " -"routing<configuration/protocols/index:protocols>`, " -":ref:`VRFs<configuration/vrf/index:vrf>`, or " -":ref:`VPNs<configuration/vpn/index:vpn>` for example." -msgstr "" - -#: ../../index.rst:31 423b3786cd1f4b5ca27399e991baec29 -msgid "Automate" -msgstr "" - -#: ../../index.rst:33 6a60ea1214f84947a09fc55d72910780 -msgid "" -"Integrate VyOS in your automation Workflow with :ref:`Ansible<vyos-" -"ansible>`, have your own :ref:`local scripts<command-scripting>`, or " -"configure VyOS with the :ref:`HTTPS-API<vyosapi>`." -msgstr "" - -#: ../../index.rst:38 4b07758c9a2e454a8959819fbf8b0d65 -msgid "Examples" -msgstr "" - -#: ../../index.rst:40 3c6c3598163e4ec99e88b939271abd75 -msgid "" -"Get some inspiration from the :ref:`Configuration " -"Blueprints<configexamples/index:Configuration Blueprints>` to build your " -"infrastructure." -msgstr "" - -#: ../../index.rst:44 83ae3d1ec6f74d89accf46d1b10753ef -msgid "Contribute and Community" -msgstr "" - -#: ../../index.rst:0 e19122c3605c41f3bdc7af93807c6319 -msgid "There are many ways to contribute to the project." -msgstr "" - -#: ../../index.rst:0 7bbf1fd6bce64b1999f16898c1318292 -msgid "" -"Add missing parts or improve the :ref:`Documentation<documentation:Write " -"Documentation>`." -msgstr "" - -#: ../../index.rst:0 234c5cbdc1364b8c88436c521c22bc35 -msgid "" -"Discuss in `Slack <https://slack.vyos.io/>`_ or the `Forum " -"<https://forum.vyos.io>`_." -msgstr "" - -#: ../../index.rst:0 c09f193ccaa64918976569c16b3d70c5 -msgid "" -"Or you can pick up a `Task <https://phabricator.vyos.net/>`_ and fix the " -":ref:`code<contributing/development:development>`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/aws.po b/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/aws.po deleted file mode 100644 index da64e524..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/aws.po +++ /dev/null @@ -1,81 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/cloud/aws.rst:3 fa54664093364a39981e14f44ddf95cf -msgid "Amazon AWS" -msgstr "" - -#: ../../installation/cloud/aws.rst:6 bc00657bf70a4765923f6abeb9824406 -msgid "Deploy VM" -msgstr "" - -#: ../../installation/cloud/aws.rst:8 c251a0991fd14e0aba028e50cab126f5 -msgid "Deploy VyOS on Amazon :abbr:`AWS (Amazon Web Services)`" -msgstr "" - -#: ../../installation/cloud/aws.rst:10 95d0e1abb47a4fd4bb576f7ec4bd7b86 -msgid "Click to ``Instances`` and ``Launch Instance``" -msgstr "" - -#: ../../installation/cloud/aws.rst:14 aaf0d9b48f8740fe9f69e609c7f67ef9 -msgid "On the marketplace search \"VyOS\"" -msgstr "" - -#: ../../installation/cloud/aws.rst:18 0ba2d2fd5d3f4619b436a224e804e222 -msgid "" -"Choose the instance type. Minimum recommendation start from ``m3.medium``" -msgstr "" - -#: ../../installation/cloud/aws.rst:22 0c7217547f5545788abcf4d833267f69 -msgid "" -"Configure instance for your requirements. Select number of instances / " -"network / subnet" -msgstr "" - -#: ../../installation/cloud/aws.rst:27 80d26657149242d09d4c045e57576bd9 -msgid "" -"Additional storage. You can remove additional storage ``/dev/sdb``. First " -"root device will be ``/dev/xvda``. You can skeep this step." -msgstr "" - -#: ../../installation/cloud/aws.rst:32 8d4641263b1c43cbafa717391878a128 -msgid "" -"Configure Security Group. It's recommended that you configure ssh access " -"only from certain address sources. Or permit any (by default)." -msgstr "" - -#: ../../installation/cloud/aws.rst:37 55624226e6a94f6cae246dd58fdb9a05 -msgid "Select SSH key pair and click ``Launch Instances``" -msgstr "" - -#: ../../installation/cloud/aws.rst:41 8bf6b966d0fe4d65abfb45134940422d -msgid "Find out your public IP address." -msgstr "" - -#: ../../installation/cloud/aws.rst:45 69b926ee7952477f85c5e5ad8e84b60f -msgid "Connect to the instance by SSH key." -msgstr "" - -#: ../../installation/cloud/aws.rst:56 df6c5fc7addb4a20b850a8c4403ec668 -msgid "References" -msgstr "" - -#: ../../installation/cloud/aws.rst:57 7d0ed3dd62674dd48b55e965ea424038 -msgid "https://console.aws.amazon.com/" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/azure.po b/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/azure.po deleted file mode 100644 index 9af5ce25..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/azure.po +++ /dev/null @@ -1,133 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/cloud/azure.rst:3 0aaa9965575f41f588385c1638c8f6c7 -msgid "Azure" -msgstr "" - -#: ../../installation/cloud/azure.rst:6 5237a81cf48d49d6ab984a1ede986e86 -msgid "Deploy VM" -msgstr "" - -#: ../../installation/cloud/azure.rst:8 353153b44bff42728f033bb7a1b23559 -msgid "Deploy VyOS on Azure." -msgstr "" - -#: ../../installation/cloud/azure.rst:10 b1897ca6c8404501a663cf36af3b8cce -msgid "Go to the Azure services and Click to **Add new Virtual machine**" -msgstr "" - -#: ../../installation/cloud/azure.rst:12 57293dbfe13a4ab3bdb3b46c510f43c8 -msgid "" -"Choose vm name, resource group, region and click **Browse all public and " -"private images**" -msgstr "" - -#: ../../installation/cloud/azure.rst:17 6e97c3b548f54db18e6cfc31639684ca -msgid "" -"On the marketplace search ``VyOS`` and choose the appropriate subscription" -msgstr "" - -#: ../../installation/cloud/azure.rst:21 458be5d9548541dc9c4dade679870ba6 -msgid "Generate new SSH key pair or use existing." -msgstr "" - -#: ../../installation/cloud/azure.rst:25 a545ba81319940efa7079d28176ec5ba -msgid "Define network, subnet, Public IP. Or it will be created by default." -msgstr "" - -#: ../../installation/cloud/azure.rst:29 0c45da39c2784e59b553f79592bb5778 -msgid "" -"Click ``Review + create``. After a few seconds your deployment will be " -"complete" -msgstr "" - -#: ../../installation/cloud/azure.rst:33 81b0a14b9f394c5ba6ac0d2aa9e28c61 -msgid "Click to your new vm and find out your Public IP address." -msgstr "" - -#: ../../installation/cloud/azure.rst:37 1fe4c58e32f94bd3a33bd1da93af26a3 -msgid "Connect to the instance by SSH key." -msgstr "" - -#: ../../installation/cloud/azure.rst:45 60d6b70ebcf64c619e1b9aa0a53fa18c -msgid "Add interface" -msgstr "" - -#: ../../installation/cloud/azure.rst:47 4e9ce53d5a5c4083b885e4c1f5bc3af7 -msgid "" -"If instance was deployed with one **eth0** ``WAN`` interface and want to add" -" new one. To add new interface an example **eth1** ``LAN`` you need shutdown" -" the instance. Attach the interface in the Azure portal and then start the " -"instance." -msgstr "" - -#: ../../installation/cloud/azure.rst:51 bee8ddd1caf34155b5645bf239e66959 -msgid "" -"Azure does not allow you attach interface when the instance in the " -"**Running** state." -msgstr "" - -#: ../../installation/cloud/azure.rst:55 bc6a372d51434b868278b0824daf4f07 -msgid "Absorbing Routes" -msgstr "" - -#: ../../installation/cloud/azure.rst:57 1944563bc52d4b5b9a676300dff9f6dd -msgid "" -"If using as a router, you will want your LAN interface to absorb some or all" -" of the traffic from your VNET by using a route table applied to the subnet." -msgstr "" - -#: ../../installation/cloud/azure.rst:59 866265225ebd49ac912985eb7a5aa4ad -msgid "Create a route table and browse to **Configuration**" -msgstr "" - -#: ../../installation/cloud/azure.rst:61 d061ec4af8dd4591bc5ec3daf53fdf3c -msgid "" -"Add one or more routes for networks you want to pass through the VyOS VM. " -"Next hop type **Virtual Appliance** with the **Next Hop Address** of the " -"VyOS ``LAN`` interface." -msgstr "" - -#: ../../installation/cloud/azure.rst:63 cf3b24245c01437d93057cd01dfc2155 -msgid "" -"If you want to create a new default route for VMs on the subnet, use " -"**Address Prefix** ``0.0.0.0/0`` Also note that if you want to use this as a" -" typical edge device, you'll want masquerade NAT for the ``WAN`` interface." -msgstr "" - -#: ../../installation/cloud/azure.rst:66 2417762f0c4242db890a65cd3bdc9635 -msgid "Serial Console" -msgstr "" - -#: ../../installation/cloud/azure.rst:68 d3e43559241944fba4d76b94507a9d44 -msgid "" -"Azure has a way to access the serial console of a VM, but this needs to be " -"configured on the VyOS. It's there by default, but keep it in mind if you " -"are replacing config.boot and rebooting: ``set system console device ttyS0 " -"speed '9600'``" -msgstr "" - -#: ../../installation/cloud/azure.rst:71 0de8f7832126455abc50c73799b185bc -msgid "References" -msgstr "" - -#: ../../installation/cloud/azure.rst:72 752ea4fdd756425cb1b85180812a8da4 -msgid "https://azure.microsoft.com" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/gcp.po b/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/gcp.po deleted file mode 100644 index 314e390e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/gcp.po +++ /dev/null @@ -1,84 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/cloud/gcp.rst:3 29b26f15e7f748f1b466543a18a3b4c3 -msgid "Google Cloud Platform" -msgstr "" - -#: ../../installation/cloud/gcp.rst:6 654ac50fb3594673935b63dc2a0b440c -msgid "Deploy VM" -msgstr "" - -#: ../../installation/cloud/gcp.rst:8 824ff11aab6846f09998da12e9d4f520 -msgid "To deploy VyOS on GCP (Google Cloud Platform)" -msgstr "" - -#: ../../installation/cloud/gcp.rst:10 65206bbef8df4509a3ad6904e6164bf1 -msgid "" -"Generate SSH key pair type **ssh-rsa** from the host that will connect to " -"VyOS." -msgstr "" - -#: ../../installation/cloud/gcp.rst:13 c6723c5fd1dd4ddd916cb662b9a37b87 -msgid "Example:" -msgstr "" - -#: ../../installation/cloud/gcp.rst:20 637f6b97bb07488a9ed985d0552ad68e -msgid "" -"In name \"vyos@mypc\" The first value must be \"**vyos**\". Because default " -"user is vyos and google api uses this option." -msgstr "" - -#: ../../installation/cloud/gcp.rst:24 2210aa7c3be34afbbbd3948578f0f1a1 -msgid "" -"Open GCP console and navigate to the menu **Metadata**. Choose **SSH Keys** " -"and click ``edit``." -msgstr "" - -#: ../../installation/cloud/gcp.rst:30 a0c3238c790c4be58e2ea72525d232c5 -msgid "Click **Add item** and paste your public ssh key. Click ``Save``." -msgstr "" - -#: ../../installation/cloud/gcp.rst:35 625c434e3e424928a4db7fca12c0babc -msgid "On marketplace search \"VyOS\"" -msgstr "" - -#: ../../installation/cloud/gcp.rst:37 dd43c33369684a1bb19d450963fd403c -msgid "Change Deployment name/Zone/Machine type and click ``Deploy``" -msgstr "" - -#: ../../installation/cloud/gcp.rst:41 84b028ddd69b4a0da06166d2ebf5a4f4 -msgid "After few seconds click to ``instance``" -msgstr "" - -#: ../../installation/cloud/gcp.rst:45 bd6a921f1d0544c9bf3c522c4f23d5bc -msgid "Find out your external IP address" -msgstr "" - -#: ../../installation/cloud/gcp.rst:49 3760c0b6b038450583383666136ced6f -msgid "Connect to the instance. SSH key was generated in the first step." -msgstr "" - -#: ../../installation/cloud/gcp.rst:57 f0438e2f4e354413b3b8ea4842f44ea1 -msgid "References" -msgstr "" - -#: ../../installation/cloud/gcp.rst:58 3109982013ca496a99fca54ffa851780 -msgid "https://console.cloud.google.com/" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/index.po b/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/index.po deleted file mode 100644 index a8f1601e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/index.po +++ /dev/null @@ -1,27 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/cloud/index.rst:7 ../../installation/cloud/index.rst:7 -#: 88133b4b11e64cce8db0180d5d49724d -msgid "Content" -msgstr "" - -#: ../../installation/cloud/index.rst:3 9cf5ca3e9cbb4cbb93726dfe064cf4d4 -msgid "Running VyOS in Cloud Environments" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/oracel.po b/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/oracel.po deleted file mode 100644 index 0b970533..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/cloud/oracel.po +++ /dev/null @@ -1,30 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/cloud/oracel.rst:3 dec3951487f04d86b141f2c6ea2ff4bc -msgid "Oracle" -msgstr "" - -#: ../../installation/cloud/oracel.rst:7 0f9f82003cd342638b57c5404fb33e3a -msgid "References" -msgstr "" - -#: ../../installation/cloud/oracel.rst:8 dc965300be65460d9649d72f529a513f -msgid "https://www.oracle.com/cloud/" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/image.po b/docs/_locale/de_DE/LC_MESSAGES/installation/image.po deleted file mode 100644 index e690d1e6..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/image.po +++ /dev/null @@ -1,99 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/image.rst:5 d55b27df9ba84eeaa454d74699338615 -msgid "Image Management" -msgstr "" - -#: ../../installation/image.rst:7 28775d23a2524673b995006550da426a -msgid "" -"The VyOS image-based installation is implemented by creating a directory for" -" each image on the storage device selected during the install process." -msgstr "" - -#: ../../installation/image.rst:10 20894f7e712745318172112f1f6ca095 -msgid "The directory structure of the boot device:" -msgstr "" - -#: ../../installation/image.rst:19 2a02295dc7f945dcbd425e3816a20c4c -msgid "" -"The image directory contains the system kernel, a compressed image of the " -"root filesystem for the OS, and a directory for persistent storage, such as " -"configuration. On boot, the system will extract the OS image into memory and" -" mount the appropriate live-rw sub-directories to provide persistent storage" -" system configuration." -msgstr "" - -#: ../../installation/image.rst:25 17555ebc8f404196950d5a94a1a71b92 -msgid "" -"This process allows for a system to always boot to a known working state, as" -" the OS image is fixed and non-persistent. It also allows for multiple " -"releases of VyOS to be installed on the same storage device. The image can " -"be selected manually at boot if needed, but the system will otherwise boot " -"the image configured to be the default." -msgstr "" - -#: ../../installation/image.rst:33 a64a67012ee54fb9a80d2702c9f4b28e -msgid "" -"List all available system images which can be booted on the current system." -msgstr "" - -#: ../../installation/image.rst:47 f2365101ab604fe49e569b0437707f64 -msgid "" -"Delete no longer needed images from the system. You can specify an optional " -"image name to delete, the image name can be retrieved via a list of " -"available images can be shown using the :opcmd:`show system image`." -msgstr "" - -#: ../../installation/image.rst:70 0b39152868194db589fbbbdef69699f8 -msgid "Show current system image version." -msgstr "" - -#: ../../installation/image.rst:97 817f05cce17640cfa76a8788dd1a26cb -msgid "System rollback" -msgstr "" - -#: ../../installation/image.rst:99 72a34a676f144c2a88030f8adddb151e -msgid "" -"If you need to rollback to a previous image, you can easily do so. First " -"check the available images through the :opcmd:`show system image` command " -"and then select your image with the following command:" -msgstr "" - -#: ../../installation/image.rst:105 88c2ee41877b409c9599749abb742bcc -msgid "" -"Select the default boot image which will be started on the next boot of the " -"system." -msgstr "" - -#: ../../installation/image.rst:108 fcd45ad4a562427fa1ca1bf9c28724a6 -msgid "Then reboot the system." -msgstr "" - -#: ../../installation/image.rst:110 127c13bbbb6a433cbe839bb120d18b71 -msgid "" -"VyOS automatically associates the configuration to the image, so you don't " -"need to worry about that. Each image has a unique copy of its configuration." -msgstr "" - -#: ../../installation/image.rst:114 7c56e6eab6ab4cbba1b8afb02888f892 -msgid "" -"If you have access to the console, there is a another way to select your " -"booting image: reboot and use the GRUB menu at startup." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/index.po b/docs/_locale/de_DE/LC_MESSAGES/installation/index.po deleted file mode 100644 index d5c947c6..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/index.po +++ /dev/null @@ -1,27 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/index.rst:7 ../../installation/index.rst:7 -#: d30c66374549432b8565c288442c7672 -msgid "Content" -msgstr "" - -#: ../../installation/index.rst:3 ddc382c7afee4fad920f47300912c67b -msgid "Installation and Image Management" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/install.po b/docs/_locale/de_DE/LC_MESSAGES/installation/install.po deleted file mode 100644 index 51567e2b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/install.po +++ /dev/null @@ -1,775 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/install.rst:5 4697f3d343284baf823c522a5f921526 -msgid "Installation" -msgstr "" - -#: ../../installation/install.rst:7 7974dae482ba439c810541b99c457c0d -msgid "" -"VyOS installation requires a downloaded VyOS .iso file. That file is a live " -"install image that lets you boot a live VyOS. From the live system, you can " -"proceed to a permanent installation on a hard drive or any other type of " -"storage." -msgstr "" - -#: ../../installation/install.rst:12 bb8f831ab2f443dc8db1d53b39f36db4 -msgid "Comparison of VyOS image releases" -msgstr "" - -#: ../../installation/install.rst:15 3d05be6a315f42b79f9d792170250861 -msgid "Release Type" -msgstr "" - -#: ../../installation/install.rst:15 f39c333f1131471f89cc1b35ee730b69 -msgid "Description" -msgstr "" - -#: ../../installation/install.rst:15 628daa74e3e14e4cb35774f3c7cdcae9 -msgid "Release Cycle" -msgstr "" - -#: ../../installation/install.rst:15 aef72635d6f8490691c97f89bc494101 -msgid "Intended Use" -msgstr "" - -#: ../../installation/install.rst:15 1a46af99cff04708b7ae9e85822e9654 -msgid "Access to Images" -msgstr "" - -#: ../../installation/install.rst:15 93b69721ccbf48828eaf19530c055da4 -msgid "Access to Source" -msgstr "" - -#: ../../installation/install.rst:17 036511dafada4af69569139870d1ce5e -msgid "**Nightly (Current)**" -msgstr "" - -#: ../../installation/install.rst:17 866a52e5d9ac4ccd80033941f2f2ceca -msgid "" -"Automatically built from the current branch. Always up to date with cutting " -"edge development but guaranteed to contain bugs." -msgstr "" - -#: ../../installation/install.rst:17 ../../installation/install.rst:21 -#: 9c163561cfba43b78be0453e76f0e8b8 946b3f13c40c4dd7b2133f40230b9f9c -msgid "Every night" -msgstr "" - -#: ../../installation/install.rst:17 b9b2c77eb35745c196ce102510cba788 -msgid "Developing VyOS, testing new features, experimenting." -msgstr "" - -#: ../../installation/install.rst:17 ../../installation/install.rst:17 -#: ../../installation/install.rst:21 ../../installation/install.rst:21 -#: ../../installation/install.rst:25 ../../installation/install.rst:25 -#: ../../installation/install.rst:29 ../../installation/install.rst:29 -#: ../../installation/install.rst:33 ../../installation/install.rst:33 -#: ../../installation/install.rst:37 7d159d569f2b4d11a6864fdabefef4ba -#: 5d572ad4348b4a04bfd41a04b9ad0951 d538b9eb80064efd9d0ae84cf8e04faa -#: 9bbf1fb06d3045869c43eb185ff6a603 4731fcf7d9af48e7bf148682379741fb -#: ebde41ce82e14149b6f99cc1682384cb b0e66accf04a4d049dc93726019e56b9 -#: 19f09669e659440e876b9dc3ca8c4fb7 0c40ccb9284443e3ad7099b9a29356f8 -#: 8b9e703b2ce949d58a3f935640ebdac1 ca09aa34d51d4758b6c72e9333bbf493 -msgid "Everyone" -msgstr "" - -#: ../../installation/install.rst:21 4551b30a9b8944299071351ec49e454f -msgid "**Nightly (Beta)**" -msgstr "" - -#: ../../installation/install.rst:21 961b280931b7408380ef0a2bac52a55e -msgid "" -"Automatically built from the development branch and released alongside " -"snapshots. Most likely contains bugs." -msgstr "" - -#: ../../installation/install.rst:21 ff4b3b4e252a4659bda3589bf0836de2 -msgid "Developing and testing the latest major version under development." -msgstr "" - -#: ../../installation/install.rst:25 e64e9847c3b34694a72e5687807d3632 -msgid "**Snapshot**" -msgstr "" - -#: ../../installation/install.rst:25 44ea660e9e9b41b68abfa54f8f6ea669 -msgid "" -"A particularly stable release frozen from nightly each month after manual " -"testing. Still contains experimental code." -msgstr "" - -#: ../../installation/install.rst:25 ea7f87dc4adf4a3e801106fe9c053775 -msgid "Every month until RC comes out" -msgstr "" - -#: ../../installation/install.rst:25 e71c65ef4d3f4aeaa3a1dfa0fbf74351 -msgid "Home labs and simple networks that call for new features." -msgstr "" - -#: ../../installation/install.rst:29 4c4e33fa52054d02ab9b055926749fac -msgid "**Release Candidate**" -msgstr "" - -#: ../../installation/install.rst:29 c7d1297685ab4bb289c2cd0c7d215c97 -msgid "" -"Rather stable. All development focuses on testing and hunting down remaining" -" bugs following the feature freeze." -msgstr "" - -#: ../../installation/install.rst:29 829c2c564dad433298554627b8781504 -msgid "Irregularly until EPA comes out" -msgstr "" - -#: ../../installation/install.rst:29 faa1f1a0a27940bebc5157beb12fcc39 -msgid "" -"Labs, small offices and non-critical production systems backed by a high-" -"availability setup." -msgstr "" - -#: ../../installation/install.rst:33 85e42a3ea69e4ba8ad5c55672099430b -msgid "**Early Production Access**" -msgstr "" - -#: ../../installation/install.rst:33 cbad3edb18484f87b969d05352b65529 -msgid "" -"Highly stable with no known bugs. Needs to be tested repeatedly under " -"different conditions before it can become the final release." -msgstr "" - -#: ../../installation/install.rst:33 38b8cddd7328403781d6b39cf0142db6 -msgid "Irregularly until LTS comes out" -msgstr "" - -#: ../../installation/install.rst:33 e0743db588b04e038d722c32b6aae9f8 -msgid "Non-critical production environments, preparing for the LTS release." -msgstr "" - -#: ../../installation/install.rst:37 e268aa03fb6b458e93dd2e0e3507cf46 -msgid "**Long-Term Support**" -msgstr "" - -#: ../../installation/install.rst:37 2959f709d21e4c53b255b62cf7c58f4e -msgid "" -"Guaranteed to be stable and carefully maintained for several years after the" -" release. No features are introduced but security updates are released in a " -"timely manner." -msgstr "" - -#: ../../installation/install.rst:37 80c0218feca04782abb4b2dd192a0a5d -msgid "Every major version" -msgstr "" - -#: ../../installation/install.rst:37 bf8a8ecfa9954b06976e78b909fe9365 -msgid "" -"Large-scale enterprise networks, internet service providers, critical " -"production environments that call for minimum downtime." -msgstr "" - -#: ../../installation/install.rst:37 f90206fd823c4ed8943d1dd4ccae0d60 -msgid "" -"Subscribers, contributors, non-profits, emergency services, academic " -"institutions" -msgstr "" - -#: ../../installation/install.rst:45 599e8fb473cc4488aa5bc4883a81270f -msgid "Hardware requirements" -msgstr "" - -#: ../../installation/install.rst:47 276e7c6f4dfd44ed9a3421ac061a44ce -msgid "" -"The minimum system requirements are 1024 MiB RAM and 2 GiB storage. " -"Depending on your use, you might need additional RAM and CPU resources e.g. " -"when having multiple BGP full tables in your system." -msgstr "" - -#: ../../installation/install.rst:52 62b585b51aaf4c408ad9b9b532c7bcf8 -msgid "Download" -msgstr "" - -#: ../../installation/install.rst:55 f453629f72a7468bb17c239ceac31d79 -msgid "Registered Subscribers" -msgstr "" - -#: ../../installation/install.rst:57 6d2335d59fef48d6b93b9aa10f108007 -msgid "" -"Registered subscribers can log into https://support.vyos.io/ to access a " -"variety of different downloads via the \"Downloads\" link. These downloads " -"include LTS (Long-Term Support), the associated hot-fix releases, early " -"public access releases, pre-built VM images, as well as device specific " -"installation ISOs." -msgstr "" - -#: ../../installation/install.rst:66 42a2b77bd2344c53809f37cce7e75af7 -msgid "Building from source" -msgstr "" - -#: ../../installation/install.rst:68 55abb9e50add450099c93af697b8e473 -msgid "" -"Non-subscribers can always get the LTS release by building it from source. " -"Instructions can be found in the :ref:`build` section of this manual. VyOS " -"source code repository is available for everyone at " -"https://github.com/vyos/vyos-build." -msgstr "" - -#: ../../installation/install.rst:74 99c08df070c44ae09ea3866cccd3e319 -msgid "Rolling Release" -msgstr "" - -#: ../../installation/install.rst:76 60b51ab0cb25412db248c99e1accd2c0 -msgid "" -"Everyone can download bleeding-edge VyOS rolling images from: " -"https://downloads.vyos.io/" -msgstr "" - -#: ../../installation/install.rst:79 fef65063b3c84f6c9b7981e6fcb4e58c -msgid "" -"Rolling releases contain all the latest enhancements and fixes. This means " -"that there will be new bugs of course. If you think you hit a bug please " -"follow the guide at :ref:`bug_report`. We depend on your feedback to improve" -" vyOS!" -msgstr "" - -#: ../../installation/install.rst:84 a69e606e01354e26a6ca6ab9fd4fe64b -msgid "" -"The following link will always fetch the most recent VyOS build for AMD64 " -"systems from the current branch: " -"https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso" -msgstr "" - -#: ../../installation/install.rst:90 2e7cd72a18d14bc1801d34f975876989 -msgid "Download Verification" -msgstr "" - -#: ../../installation/install.rst:92 dc2d19bebcf74e45954cf8490750f13a -msgid "" -"LTS images are signed by the VyOS lead package-maintainer private key. With " -"the official public key, the authenticity of the package can be verified. " -":abbr:`GPG (GNU Privacy Guard)` is used for verification." -msgstr "" - -#: ../../installation/install.rst:96 5d866e91ae59412184f7c28e92835f6e -msgid "" -"This subsection only applies to LTS images, for Rolling images please jump " -"to :ref:`live_installation`." -msgstr "" - -#: ../../installation/install.rst:100 c3b308b517cb43d693b1a9ad4b3ff561 -msgid "Preparing for the verification" -msgstr "" - -#: ../../installation/install.rst:102 95b9a8908ec44a3c9c7a93e5e056e012 -msgid "" -"First, install GPG or another OpenPGP implementation. On most GNU+Linux " -"distributions it is installed by default as package managers use it to " -"verify package signatures. If not pre-installed, it will need to be " -"downloaded and installed." -msgstr "" - -#: ../../installation/install.rst:107 b2220f4679f946948b03d3ea9330dff4 -msgid "" -"The official VyOS public key can be retrieved in a number of ways. Skip to " -":ref:`gpg-verification` if the key is already present." -msgstr "" - -#: ../../installation/install.rst:110 a43fa400b0e64112af2a9789c546a0bd -msgid "It can be retrieved directly from a key server:" -msgstr "" - -#: ../../installation/install.rst:112 77d08cbc2e514fadaa4a6cdefa3e82ba -msgid "``gpg --recv-keys FD220285A0FE6D7E``" -msgstr "" - -#: ../../installation/install.rst:114 a59df5a110c64fdfbbdebbe94d46211e -msgid "Or it can be accessed via a web browser:" -msgstr "" - -#: ../../installation/install.rst:116 cbdc6ca8522b49c5bb020c299031b678 -msgid "https://pgp.mit.edu/pks/lookup?op=get&search=0xFD220285A0FE6D7E" -msgstr "" - -#: ../../installation/install.rst:118 6f092165879b4045a0e890da6b046dc1 -msgid "Or from the following block:" -msgstr "" - -#: ../../installation/install.rst:175 1d1512b69502416fbd9466f40bc755e9 -msgid "" -"Store the key in a new text file and import it into GPG via: ``gpg --import " -"file_with_the_public_key``" -msgstr "" - -#: ../../installation/install.rst:178 87e045356a414af695a99b5e19710287 -msgid "The import can be verified with:" -msgstr "" - -#: ../../installation/install.rst:192 29c59500327f40bc94f6bc92730a637f -msgid "GPG verification" -msgstr "" - -#: ../../installation/install.rst:194 eebc6b4fad544d6a91e1209392f76f1a -msgid "" -"With the public key imported, the signature for the desired image needs to " -"be downloaded." -msgstr "" - -#: ../../installation/install.rst:197 e77512e2030543aeaaf730c445163afd -msgid "" -"The signature can be downloaded by appending `.asc` to the URL of the " -"downloaded VyOS image. That small *.asc* file is the signature for the " -"associated image." -msgstr "" - -#: ../../installation/install.rst:201 d67224806e1e4be49706c4520fd72b57 -msgid "Finally, verify the authenticity of the downloaded image:" -msgstr "" - -#: ../../installation/install.rst:214 0c19c3f32e064a608d21f7d65b86c2b6 -msgid "Minisign verification" -msgstr "" - -#: ../../installation/install.rst:216 3784baafee5d417ebae792a1307365e0 -msgid "" -"Currently we are using GPG for release signing (pretty much like everyone " -"else)." -msgstr "" - -#: ../../installation/install.rst:218 f0dda48d10c74668836623c873b89d87 -msgid "" -"Popularity of GPG for release signing comes from the fact that many people " -"already had it installed for email encryption/signing. Inside a VyOS image, " -"signature checking is the only reason to have it installed. However, it " -"still comes with all the features no one needs, such as support for multiple" -" outdated cipher suits and ability to embed a photo in the key file. More " -"importantly, web of trust, the basic premise of PGP, is never used in " -"release signing context. Once you have a knowingly authentic image, " -"authenticity of upgrades is checked using a key that comes in the image, and" -" to get their first image people never rely on keyservers either." -msgstr "" - -#: ../../installation/install.rst:228 798aa4ce21e74cc8abf96f493684e735 -msgid "" -"Another point is that we are using RSA now, which requires absurdly large " -"keys to be secure." -msgstr "" - -#: ../../installation/install.rst:231 bb1a1cdf41ed4b3b9553d6084bc65a08 -msgid "" -"In 2015, OpenBSD introduced signify. An alternative implementation of the " -"same protocol is minisign, which is also available for Windows and macOS, " -"and in most GNU/Linux distros it's in the repositories now." -msgstr "" - -#: ../../installation/install.rst:235 2aabda8d2a35493ca4b8e15e6a018300 -msgid "" -"Its installed size (complete with libsodium) is less than that of GPG binary" -" alone (not including libgcrypt and some other libs, which I think we only " -"use for GPG). Since it uses elliptic curves, it gets away with much smaller " -"keys, and it doesn't include as much metadata to begin with." -msgstr "" - -#: ../../installation/install.rst:240 60ed8279c10a406baf6527d939f28025 -msgid "" -"Another issue of GPG is that it creates a /root/.gnupg directory just for " -"release checking. The dir is small so the fact that it's never used again is" -" an aesthetic problem, but we've had that process fail in the past. But, " -"small key size of the Ed25519 algorithm allows passing public keys in " -"command line arguments, so verification process can be completely stateless:" -msgstr "" - -#: ../../installation/install.rst:246 c1dfea9a8c7548b2bb5a4d9f89ec9340 -msgid "" -":vytask:`T2108` switched the validation system to prefer minisign over GPG " -"keys." -msgstr "" - -#: ../../installation/install.rst:248 4c3c092b3caa4a40a45f2ca086172633 -msgid "To verify a VyOS image starting off with VyOS 1.3.0-rc6 you can run:" -msgstr "" - -#: ../../installation/install.rst:256 9a8a82f635064f8795a0391922de8aeb -msgid "During an image upgrade VyOS performas the following command:" -msgstr "" - -#: ../../installation/install.rst:267 f28633931a064c44848d0ae1a1d30181 -msgid "Live installation" -msgstr "" - -#: ../../installation/install.rst:269 37baa8e6c7c9455abb55f4638e9716ee -msgid "" -"A permanent VyOS installation always requires to go first through a live " -"installation." -msgstr "" - -#: ../../installation/install.rst:272 a4058da6fa504df69340e5ef520c4a8f -msgid "" -"VyOS, as other GNU+Linux distributions, can be tested without installing it " -"in your hard drive. **With your downloaded VyOS .iso file you can create a " -"bootable USB drive that will let you boot into a fully functional VyOS " -"system**. Once you have tested it, you can either decide to begin a " -":ref:`permanent_installation` in your hard drive or power your system off, " -"remove the USB drive, and leave everything as it was." -msgstr "" - -#: ../../installation/install.rst:280 f4b84be2b833403fa7ffc38fca2fbf80 -msgid "" -"If you have a GNU+Linux system, you can create your VyOS bootable USB stick " -"with with the ``dd`` command:" -msgstr "" - -#: ../../installation/install.rst:283 d68b896701f949aba8818702d30e7f4f -msgid "Open your terminal emulator." -msgstr "" - -#: ../../installation/install.rst:285 ddb69f0142ee435f982c5098e162f37d -msgid "" -"Find out the device name of your USB drive (you can use the ``lsblk`` " -"command)" -msgstr "" - -#: ../../installation/install.rst:288 808781dd34d3478f881a57c10fa6fa37 -msgid "" -"Unmount the USB drive. Replace X in the example below with the letter of " -"your device and keep the asterisk (wildcard) to unmount all partitions." -msgstr "" - -#: ../../installation/install.rst:296 42e4274bb534421abc7a68d9c066971c -msgid "" -"Write the image (your VyOS .iso file) to the USB drive. Note that here you " -"want to use the device name (e.g. /dev/sdb), not the partition name (e.g. " -"/dev/sdb1)." -msgstr "" - -#: ../../installation/install.rst:300 8bab48bde7644a59a9908e2258a6019b -msgid "**Warning**: This will destroy all data on the USB drive!" -msgstr "" - -#: ../../installation/install.rst:306 a55d73aa4382475a916a2647bd531418 -msgid "" -"Wait until you get the outcome (bytes copied). Be patient, in some computers" -" it might take more than one minute." -msgstr "" - -#: ../../installation/install.rst:309 8d954695d706419881d1183d406ff18e -msgid "" -"Once ``dd`` has finished, pull the USB drive out and plug it into the " -"powered-off computer where you want to install (or test) VyOS." -msgstr "" - -#: ../../installation/install.rst:312 5e21c372517d4a78ab9212580b4dc618 -msgid "" -"Power the computer on, making sure it boots from the USB drive (you might " -"need to select booting device or change booting settings)." -msgstr "" - -#: ../../installation/install.rst:315 9320aa595bef4dba85fe59dc17b6cdb4 -msgid "" -"Once VyOS is completely loaded, enter the default credentials (login: vyos, " -"password: vyos)." -msgstr "" - -#: ../../installation/install.rst:319 2a8634f7d8d04a8fa7c93c4c694bb979 -msgid "" -"If you find difficulties with this method, prefer to use a GUI program, or " -"have a different operating system, there are other programs you can use to " -"create a bootable USB drive, like balenaEtcher_ (for GNU/Linux, macOS and " -"Windows), Rufus_ (for Windows) and `many others`_. You can follow their " -"instructions to create a bootable USB drive from an .iso file." -msgstr "" - -#: ../../installation/install.rst:326 4f940e9b00da488693ae3e49c8d047b7 -msgid "The default username and password for the live system is *vyos*." -msgstr "" - -#: ../../installation/install.rst:332 5402cd3ce58d4fd5bed4bf6ba954e728 -msgid "Permanent installation" -msgstr "" - -#: ../../installation/install.rst:334 92d01a9628c44b1b922d6acd9500ebfe -msgid "" -"Before a permanent installation, VyOS requires a :ref:`live_installation`." -msgstr "" - -#: ../../installation/install.rst:337 92fb364e254144408f757da39754953f -msgid "" -"Unlike general purpose Linux distributions, VyOS uses \"image installation\"" -" that mimics the user experience of traditional hardware routers and allows " -"keeping multiple VyOS versions installed simultaneously. This makes it " -"possible to switch to a previous version if something breaks or miss-behaves" -" after an image upgrade." -msgstr "" - -#: ../../installation/install.rst:343 6e2e3490eedf4c12953f4ef0bc7a570d -msgid "" -"Every version is contained in its own squashfs image that is mounted in a " -"union filesystem together with a directory for mutable data such as " -"configurations, keys, or custom scripts." -msgstr "" - -#: ../../installation/install.rst:347 4f1fe59b7fa14431bd707e9625f7cfce -msgid "" -"Older versions (prior to VyOS 1.1) used to support non-image installation " -"(``install system`` command). Support for this has been removed from VyOS " -"1.2 and newer releases. Older releases can still be upgraded via the general" -" ``add system image <image_path>`` upgrade command (consult :ref:`image-" -"mgmt` for further information)." -msgstr "" - -#: ../../installation/install.rst:354 1d13008a6cef4388af256070be286436 -msgid "In order to proceed with a permanent installation:" -msgstr "" - -#: ../../installation/install.rst:356 b62d44e0a93a4f3dacb7c2bae4458b79 -msgid "" -"Log into the VyOS live system (use the default credentials: vyos, vyos)" -msgstr "" - -#: ../../installation/install.rst:359 0e3140c712d8421d9289590fd6e1ab27 -msgid "Run the ``install image`` command and follow the wizard:" -msgstr "" - -#: ../../installation/install.rst:413 f8400b3c3bf04f6983571c30751c259a -msgid "After the installation is completed, remove the live USB stick or CD." -msgstr "" - -#: ../../installation/install.rst:416 29dcf1b8ecf64e6cadd8f450d813638f -msgid "Reboot the system." -msgstr "" - -#: ../../installation/install.rst:423 058304c2d4b1438d8fe0ab599f3ddb37 -msgid "You will boot now into a permanent VyOS system." -msgstr "" - -#: ../../installation/install.rst:427 b348f9a0b86343589233d0bb712ac1b4 -msgid "PXE Boot" -msgstr "" - -#: ../../installation/install.rst:429 1c77c0f8f36e4caa9442ae0bc4ab8c55 -msgid "" -"VyOS can also be installed through PXE. This is a more complex installation " -"method that allows deploying VyOS through the network." -msgstr "" - -#: ../../installation/install.rst:432 95aed3c6ef9f472cb6e19d7cf586c78e -msgid "**Requirements**" -msgstr "" - -#: ../../installation/install.rst:434 db3686856aef4cd8b42c20041a8b31cb -msgid "Clients (where VyOS is to be installed) with a PXE-enabled NIC" -msgstr "" - -#: ../../installation/install.rst:435 751d219d938c41e28f42e54dc60664ce -msgid ":ref:`dhcp-server`" -msgstr "" - -#: ../../installation/install.rst:436 4acc656a38ef40319ce334c559370752 -msgid ":ref:`tftp-server`" -msgstr "" - -#: ../../installation/install.rst:437 9cd5dbefdeb94a0fa3f35ce32bd02d25 -msgid "" -"Webserver (HTTP) - optional, but we will use it to speed up installation" -msgstr "" - -#: ../../installation/install.rst:438 b113ebed03c5454da8273ca7fab727e9 -msgid "VyOS ISO image to be installed (do not use images prior to VyOS 1.2.3)" -msgstr "" - -#: ../../installation/install.rst:439 3cf5e9606ae349bb92a1236c3ce98b0a -msgid "" -"Files *pxelinux.0* and *ldlinux.c32* `from the Syslinux distribution " -"<https://kernel.org/pub/linux/utils/boot/syslinux/>`_" -msgstr "" - -#: ../../installation/install.rst:443 2d09550bf3cf407280bea878881548ea -msgid "Configuration" -msgstr "" - -#: ../../installation/install.rst:446 183cf6fbee624992a3913dc2a09f3123 -msgid "Step 1: DHCP" -msgstr "" - -#: ../../installation/install.rst:448 63acdd02ffd8434c812b6c803584e5be -msgid "Configure a DHCP server to provide the client with:" -msgstr "" - -#: ../../installation/install.rst:450 21e5fa45742144768fb9756668e85c5d -msgid "An IP address" -msgstr "" - -#: ../../installation/install.rst:451 798da3f07b7c4f939fd43778980fa7c2 -msgid "" -"The TFTP server address (DHCP option 66). Sometimes referred as *boot " -"server*" -msgstr "" - -#: ../../installation/install.rst:452 642bf175ac8a4d1bac90821d6e4ec6c7 -msgid "The *bootfile name* (DHCP option 67), which is *pxelinux.0*" -msgstr "" - -#: ../../installation/install.rst:454 e85c641ed79d4d30bef170f3747313cc -msgid "In this example we configured an existent VyOS as the DHCP server:" -msgstr "" - -#: ../../installation/install.rst:474 bacf328675604b2da698310be70c774d -msgid "Step 2: TFTP" -msgstr "" - -#: ../../installation/install.rst:476 f491c1b2544c4f718216d38c480911b8 -msgid "Configure a TFTP server so that it serves the following:" -msgstr "" - -#: ../../installation/install.rst:478 39540401636740a8bb476b182b2d3ff0 -msgid "The *pxelinux.0* file from the Syslinux distribution" -msgstr "" - -#: ../../installation/install.rst:479 10421ba1898d4fed8f1b4d2289925a45 -msgid "The *ldlinux.c32* file from the Syslinux distribution" -msgstr "" - -#: ../../installation/install.rst:480 7b375de997da49d39bc5dcf6a6e669de -msgid "" -"The kernel of the VyOS software you want to deploy. That is the *vmlinuz* " -"file inside the */live* directory of the extracted contents from the ISO " -"file." -msgstr "" - -#: ../../installation/install.rst:483 d685ee3b0d4d4b079b2ad08e19f9efe3 -msgid "" -"The initial ramdisk of the VyOS ISO you want to deploy. That is the " -"*initrd.img* file inside the */live* directory of the extracted contents " -"from the ISO file. Do not use an empty (0 bytes) initrd.img file you might " -"find, the correct file may have a longer name." -msgstr "" - -#: ../../installation/install.rst:487 1d03ce83bdb84cb2950d083a00259e0f -msgid "" -"A directory named pxelinux.cfg which must contain the configuration file. We" -" will use the configuration_ file shown below, which we named default_." -msgstr "" - -#: ../../installation/install.rst:491 9b524233146845ecbfbb385ebdc14e42 -msgid "In the example we configured our existent VyOS as the TFTP server too:" -msgstr "" - -#: ../../installation/install.rst:499 0d9cf1fda6534cfb8902a4a3a00a67b4 -msgid "Example of the contents of the TFTP server:" -msgstr "" - -#: ../../installation/install.rst:519 a7446be9a93942cabf8fc8281eb3bd09 -msgid "Example of simple (no menu) configuration file:" -msgstr "" - -#: ../../installation/install.rst:531 9099cfadfdd74308b8df47c767052573 -msgid "Step 3: HTTP" -msgstr "" - -#: ../../installation/install.rst:533 56ecf83ac77146e09844fef2b41a7a06 -msgid "" -"We also need to provide the *filesystem.squashfs* file. That is a heavy file" -" and TFTP is slow, so you could send it through HTTP to speed up the " -"transfer. That is how it is done in our example, you can find that in the " -"configuration file above." -msgstr "" - -#: ../../installation/install.rst:538 d014438381564bce8557146d5b74c4a5 -msgid "" -"**First** run a web server - you can use a simple one like `Python's " -"SimpleHTTPServer`_ and start serving the `filesystem.squashfs` file. The " -"file can be found inside the `/live` directory of the extracted contents of " -"the ISO file." -msgstr "" - -#: ../../installation/install.rst:543 b9af7347312f42e9b30055dc3dfaa6e5 -msgid "" -"**Second**, edit the configuration file of the :ref:`install_from_tftp` so " -"that it shows the correct URL at " -"``fetch=http://<address_of_your_HTTP_server>/filesystem.squashfs``." -msgstr "" - -#: ../../installation/install.rst:547 caf8e161979449f3b9d02838ba475468 -msgid "" -"Do not change the name of the *filesystem.squashfs* file. If you are working" -" with different versions, you can create different directories instead." -msgstr "" - -#: ../../installation/install.rst:551 1967c2124d844668a40411b6e369ef77 -msgid "" -"And **third**, restart the TFTP service. If you are using VyOS as your TFTP " -"Server, you can restart the service with ``sudo service tftpd-hpa restart``." -msgstr "" - -#: ../../installation/install.rst:555 ac0682ac6a7b4da6b315b5604e69654a -msgid "" -"Make sure the available directories and files in both TFTP and HTTP server " -"have the right permissions to be accessed from the booting clients." -msgstr "" - -#: ../../installation/install.rst:562 c0a46c7586914eeb848eec6e77bc6afb -msgid "Client Boot" -msgstr "" - -#: ../../installation/install.rst:564 b33d783034a2470bbc7bca2115117ea2 -msgid "" -"Finally, turn on your PXE-enabled client or clients. They will automatically" -" get an IP address from the DHCP server and start booting into VyOS live " -"from the files automatically taken from the TFTP and HTTP servers." -msgstr "" - -#: ../../installation/install.rst:569 77da66e6952d4375bf59933ba844c220 -msgid "" -"Once finished you will be able to proceed with the ``install image`` command" -" as in a regular VyOS installation." -msgstr "" - -#: ../../installation/install.rst:575 17b8ccb81b5e42eaae0b1fb53bf3c760 -msgid "Known Issues" -msgstr "" - -#: ../../installation/install.rst:577 72f6a5b3a848479e9f64ace2f494d312 -msgid "This is a list of known issues that can arise during installation." -msgstr "" - -#: ../../installation/install.rst:580 2a729bc304604f4e81f171acac8e6b41 -msgid "Black screen on install" -msgstr "" - -#: ../../installation/install.rst:582 3196bd4e706b42b88aae8f857759d85d -msgid "" -"GRUB attempts to redirect all output to a serial port for ease of " -"installation on headless hosts. This appears to cause an hard lockup on some" -" hardware that lacks a serial port, with the result being a black screen " -"after selecting the `Live system` option from the installation image." -msgstr "" - -#: ../../installation/install.rst:587 7970447bb4c8497c8c8f7712f71378c2 -msgid "" -"The workaround is to type `e` when the boot menu appears and edit the GRUB " -"boot options. Specifically, remove the:" -msgstr "" - -#: ../../installation/install.rst:590 320636747e604a29ae8ada6f669642d8 -msgid "`console=ttyS0,115200`" -msgstr "" - -#: ../../installation/install.rst:592 c863f9c5dbab44458349136354715dcc -msgid "option, and type CTRL-X to boot." -msgstr "" - -#: ../../installation/install.rst:594 f231d84d789e46549e806e34654cbbc4 -msgid "Installation can then continue as outlined above." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/migrate-from-vyatta.po b/docs/_locale/de_DE/LC_MESSAGES/installation/migrate-from-vyatta.po deleted file mode 100644 index f670d644..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/migrate-from-vyatta.po +++ /dev/null @@ -1,112 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/migrate-from-vyatta.rst:4 -#: 7ef61af476f6489b80796adae5ef35c0 -msgid "Migrate from Vyatta Core" -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:6 -#: 80c26479d61f4d0ab807836c305fa9d2 -msgid "" -"VyOS 1.x line aims to preserve backward compatibility and provide a safe " -"upgrade path for existing Vyatta Core users. You may think of VyOS 1.0.0 as " -"VC7.0." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:11 -#: 8e4590cb4a8e4f35bcba3314b9456759 -msgid "Vyatta release compatibility" -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:13 -#: 47ab7130e69c47f5ab6bd65e6fb433db -msgid "Vyatta Core releases from 6.5 to 6.6 should be 100% compatible." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:15 -#: 660d5b807489403ca8d8e92ce924b680 -msgid "" -"Vyatta Core 6.4 and earlier may have incompatibilities. In Vyatta 6.5 the " -"\"modify\" firewall was removed and replaced with the ``set policy route`` " -"command family, old configs can not be automatically converted. You will " -"have to adapt it to post-6.5 Vyatta syntax manually." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:20 -#: 170078bafb6a4fbda31a833ca79a66af -msgid "" -"Also, in Vyatta Core 6.5 remote access VPN interfaces have been renamed from" -" ``pppX`` to ``l2tpX`` and ``pptpX``. If you are using zone based " -"firewalling in Vyatta Core pre-6.5 versions, make sure to change interface " -"names in rules for remote access VPN." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:26 -#: 3317257ed59c43f89263f1435c8be987 -msgid "Upgrade procedure" -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:28 -#: 731dd3a1894a41ba95c464d56b5d4ee5 -msgid "" -"You just use ``add system image``, as if it was a new VC release (see " -":ref:`update_vyos` for additional information). The only thing you want to " -"do is to verify the new images digital signature. You will have to add the " -"public key manually once as it is not shipped the first time." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:42 -#: d65d3e8001694acdba92a48e420c1399 -msgid "" -"For completion the key below corresponds to the key listed in the URL above." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:99 -#: 153cb6e23c43451cb3ba771f17255c3a -msgid "Next add the VyOS image." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:101 -#: 2e1edef2f1d24fd0bb7678486dad4e3c -msgid "" -"This example uses VyOS 1.0.0, however, it's better to install the latest " -"release." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:156 -#: bdb5b68183cf4f0ea57b1b17a3d14f70 -msgid "Upon reboot, you should have a working installation of VyOS." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:158 -#: 7b2413f627504b8a960ce6214b0fa7ad -msgid "" -"You can go back to your Vyatta install using the ``set system image default-" -"boot`` command and selecting the your previous Vyatta Core image." -msgstr "" - -#: ../../installation/migrate-from-vyatta.rst:161 -#: 42645fe755824dbdb3face7d175806d6 -msgid "" -"Future releases of VyOS will break the direct upgrade path from Vyatta core." -" Please upgrade through an intermediate VyOS version e.g. VyOS 1.2. After " -"this you can continue upgrading to newer releases once you bootet into VyOS " -"1.2 once." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/update.po b/docs/_locale/de_DE/LC_MESSAGES/installation/update.po deleted file mode 100644 index defc3424..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/update.po +++ /dev/null @@ -1,98 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/update.rst:4 4bc5dd3bb9754bbd93b1c8ab33bfbe8e -msgid "Update VyOS" -msgstr "" - -#: ../../installation/update.rst:6 2c9913c0eab849b5b385f91f50e460d2 -msgid "" -"New system images can be added using the :opcmd:`add system image` command. " -"The command will extract the chosen image and will prompt you to use the " -"current system configuration and SSH security keys, allowing for the new " -"image to boot using the current configuration." -msgstr "" - -#: ../../installation/update.rst:11 05d145d97c464397b34046571b6d3ddf -msgid "Only LTS releases are PGP-signed." -msgstr "" - -#: ../../installation/update.rst:16 7e5df5fbf3ab461ba2915cadd5106d19 -msgid "" -"Use this command to install a new system image. You can reach the image from" -" the web (``http://``, ``https://``) or from your local system, e.g. " -"/tmp/vyos-1.2.3-amd64.iso." -msgstr "" - -#: ../../installation/update.rst:20 9c18ec3117204a44838e354b958c6d03 -msgid "" -"The `add system image` command also supports installing new versions of VyOS" -" through an optional given VRF. Also if URL in question requires " -"authentication, you can specify an optional username and password via the " -"commandline which will be passed as \"Basic-Auth\" to the server." -msgstr "" - -#: ../../installation/update.rst:25 3bd24934870940749266b676c1155f5b -msgid "" -"If there is not enough **free disk space available**, the installation will " -"be canceled. To delete images use the :opcmd:`delete system image` command." -msgstr "" - -#: ../../installation/update.rst:29 059337f189cb4483ace29f3ba214ddce -msgid "" -"VyOS configuration is associated to each image, and **each image has a " -"unique copy of its configuration**. This is different than a traditional " -"network router where the configuration is shared across all images." -msgstr "" - -#: ../../installation/update.rst:33 955eaf213662477bb905c0d835f51f43 -msgid "" -"If you have any personal files, like some scripts you created, and you don't" -" want them to be lost during the upgrade, make sure those files are stored " -"in ``/config`` as this directory is always copied to newer installed images." -msgstr "" - -#: ../../installation/update.rst:38 11b4d8caacd5449bb9dce5a736da0b62 -msgid "" -"You can access files from a previous installation and copy them to your " -"current image if they were located in the ``/config`` directory. This can be" -" done using the :opcmd:`copy` command. So, for instance, in order to copy " -"``/config/config.boot`` from VyOS 1.2.1 image, you would use the following " -"command:" -msgstr "" - -#: ../../installation/update.rst:50 994b192022b1498ea780dfad64ad1fb0 -msgid "Example" -msgstr "" - -#: ../../installation/update.rst:76 f8e9ec6c51bf42559f2a4a77e99e5d91 -msgid "" -"The most up-do-date Rolling Release for AMD64 can be accessed using the " -"following URL:" -msgstr "" - -#: ../../installation/update.rst:79 77f511fb439b493db7ff4469006798a4 -msgid "https://vyos.net/get/nightly-builds/" -msgstr "" - -#: ../../installation/update.rst:81 5670c6b63d1e4d9a933c46f87b331c12 -msgid "" -"After reboot you might want to verify the version you are running with the " -":opcmd:`show version` command." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/docker.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/docker.po deleted file mode 100644 index 3d13743e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/docker.po +++ /dev/null @@ -1,82 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/docker.rst:5 b9cb33d119cb47269243489deb36f905 -msgid "Running in Docker Container" -msgstr "" - -#: ../../installation/virtual/docker.rst:7 a2c0ff7cf4864271aea70bc2fc63b745 -msgid "" -"Docker is an open-source project for deploying applications as standardized " -"units called containers. Deploying VyOS in a container provides a simple and" -" lightweight mechanism for both testing and packet routing for container " -"workloads." -msgstr "" - -#: ../../installation/virtual/docker.rst:13 84f148bf84a846d397e35d1f888d6549 -msgid "IPv6 Support for docker" -msgstr "" - -#: ../../installation/virtual/docker.rst:15 be845628cd2f44578d02134052b0a8d7 -msgid "" -"VyOS requires an IPv6-enabled docker network. Currently linux distributions " -"do not enable docker IPv6 support by default. You can enable IPv6 support in" -" two ways." -msgstr "" - -#: ../../installation/virtual/docker.rst:20 91a65a10a2554c3c82594eb192d2c712 -msgid "Method 1: Create a docker network with IPv6 support" -msgstr "" - -#: ../../installation/virtual/docker.rst:22 1834e4e5ac72458aa81c4ea6bddab6e4 -msgid "Here is a example using the macvlan driver." -msgstr "" - -#: ../../installation/virtual/docker.rst:29 d2fae4c6ba8e480ba148547341c95419 -msgid "Method 2: Add IPv6 support to the docker daemon" -msgstr "" - -#: ../../installation/virtual/docker.rst:31 f61b9914be4247f4a551f2002f1c96d0 -msgid "" -"Edit /etc/docker/daemon.json to set the ``ipv6`` key to ``true`` and to " -"specify the ``fixed-cidr-v6`` to your desired IPv6 subnet." -msgstr "" - -#: ../../installation/virtual/docker.rst:41 dd3e765ed2ca41bbbf8c0b39ac2d5800 -msgid "Reload the docker configuration." -msgstr "" - -#: ../../installation/virtual/docker.rst:49 6d22cf8536174389a2c9e9aa1ed78063 -msgid "Deploy container from ISO" -msgstr "" - -#: ../../installation/virtual/docker.rst:51 0bfbb4b066f949fd82d843e214f01a5b -msgid "" -"Download the ISO on which you want to base the container. In this example, " -"the name of the ISO is ``vyos-1.4-rolling-202111281249-amd64.iso``. If you " -"created a custom IPv6-enabled network, the ``docker run`` command below will" -" require that this network be included as the ``--net`` parameter to " -"``docker run``." -msgstr "" - -#: ../../installation/virtual/docker.rst:74 19b0b9e733bc4fe1bd8c364d3247eeb1 -msgid "" -"You can execute ``docker stop vyos`` when you are finished with the " -"container." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/eve-ng.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/eve-ng.po deleted file mode 100644 index 94cc1833..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/eve-ng.po +++ /dev/null @@ -1,30 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/eve-ng.rst:3 8a2f4a3cb3cb4a91a0ca32508a024d9c -msgid "EVE-NG" -msgstr "" - -#: ../../installation/virtual/eve-ng.rst:6 33c97cad6d284078b32a6f34c763bf73 -msgid "References" -msgstr "" - -#: ../../installation/virtual/eve-ng.rst:8 24195848319a475d970d2115ded14ef1 -msgid "https://www.eve-ng.net/" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/gns3.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/gns3.po deleted file mode 100644 index 6c98a0fe..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/gns3.po +++ /dev/null @@ -1,259 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/gns3.rst:5 59f9f91b73204eb1b1ed3bdfc08cfaef -msgid "Running on GNS3" -msgstr "" - -#: ../../installation/virtual/gns3.rst:7 9612e309f2584c87b4648e9517b67eb0 -msgid "" -"Sometimes you may want to test VyOS in a lab environment. `GNS3 " -"<http://www.gns3.com>`__ is a network emulation software you might use for " -"it." -msgstr "" - -#: ../../installation/virtual/gns3.rst:11 5d27c0c433034219b7e593b335038366 -msgid "" -"This guide will provide the necessary steps for installing and setting up " -"VyOS on GNS3." -msgstr "" - -#: ../../installation/virtual/gns3.rst:15 5f367653ce954824a9778c6fc7d0370f -msgid "Requirements" -msgstr "" - -#: ../../installation/virtual/gns3.rst:17 b73e58dff5ca4376953a057a099dffe4 -msgid "The following items are required:" -msgstr "" - -#: ../../installation/virtual/gns3.rst:19 731cb2a742d943689c57f13cc05b39ea -msgid "" -"A VyOS installation image (.iso file). You can find how to get it on the " -":ref:`installation` page" -msgstr "" - -#: ../../installation/virtual/gns3.rst:22 a68cb60d89634816a86b9f918ab6944a -msgid "" -"A working GNS3 installation. For further information see the `GNS3 " -"documentation <https://docs.gns3.com/>`__." -msgstr "" - -#: ../../installation/virtual/gns3.rst:28 c303f61291084965be90084781338f2f -msgid "VM setup" -msgstr "" - -#: ../../installation/virtual/gns3.rst:30 5723b11407a243d9aa0217483ea78f91 -msgid "" -"First, a virtual machine (VM) for the VyOS installation must be created in " -"GNS3." -msgstr "" - -#: ../../installation/virtual/gns3.rst:33 fea664653f1c4d7fb0081fa91a524fd4 -msgid "" -"Go to the GNS3 **File** menu, click **New template** and choose select " -"**Manually create a new Template**." -msgstr "" - -#: ../../installation/virtual/gns3.rst:38 51421048827b497692ac5c2972332167 -msgid "Select **Quemu VMs** and then click on the ``New`` button." -msgstr "" - -#: ../../installation/virtual/gns3.rst:42 e4020f06acae4d43ae0da0b383f2db7d -msgid "Write a name for your VM, for instance \"VyOS\", and click ``Next``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:46 32a4a277c4334766a95d45c5f30b2f93 -msgid "" -"Select **qemu-system-x86_64** as Quemu binary, then **512MB** of RAM and " -"click ``Next``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:51 d997f22a23d04f4ab51d3259a32df3c6 -msgid "Select **telnet** as your console type and click ``Next``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:55 3d88cddb879d493e93b2c43f0486c8f4 -msgid "" -"Select **New image** for the base disk image of your VM and click " -"``Create``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:60 ea9e73422a7d4457a26d8f1e875e7ddc -msgid "" -"Use the defaults in the **Binary and format** window and click ``Next``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:65 b3aad0a0fbd9428483c9755abf6c0fed -msgid "Use the defaults in the **Qcow2 options** window and click ``Next``." -msgstr "" - -#: ../../installation/virtual/gns3.rst:69 2d46a8e8b2fb4c42b79b72af64a46d87 -msgid "" -"Set the disk size to 2000 MiB, and click ``Finish`` to end the **Quemu image" -" creator**." -msgstr "" - -#: ../../installation/virtual/gns3.rst:74 57980132242c41f7847f96511f7864a0 -msgid "Click ``Finish`` to end the **New QEMU VM template** wizard." -msgstr "" - -#: ../../installation/virtual/gns3.rst:78 9e42c685a4f04e1ca029ed25177c367b -msgid "Now the VM settings have to be edited." -msgstr "" - -#: ../../installation/virtual/gns3.rst:80 594c44a3609948a5be5cfd76bef3ca03 -msgid "" -"Being again at the **Preferences** window, having **Qemu VMs** selected and " -"having our new VM selected, click the ``Edit`` button." -msgstr "" - -#: ../../installation/virtual/gns3.rst:85 dea19552d9dc4fa38123006cb62bbf85 -msgid "" -"In the **General settings** tab of your **QEMU VM template configuration**, " -"do the following:" -msgstr "" - -#: ../../installation/virtual/gns3.rst:88 5b7159e6245b496d80dedcc9ccd03cd4 -msgid "" -"Click on the ``Browse...`` button to choose the **Symbol** you want to have " -"representing your VM." -msgstr "" - -#: ../../installation/virtual/gns3.rst:90 2d0ef5e0b1a84477906dccedf12672a9 -msgid "In **Category** select in which group you want to find your VM." -msgstr "" - -#: ../../installation/virtual/gns3.rst:91 e6ff44d2cdc54528a013354bbd4c912c -msgid "Set the **Boot priority** to **CD/DVD-ROM**." -msgstr "" - -#: ../../installation/virtual/gns3.rst:95 1f629b6e6ac6465594fc705c4849da28 -msgid "" -"At the **HDD** tab, change the Disk interface to **sata** to speed up the " -"boot process." -msgstr "" - -#: ../../installation/virtual/gns3.rst:100 001d9251bfcf4b89b58a301fdfeef3c8 -msgid "" -"At the **CD/DVD** tab click on ``Browse...`` and locate the VyOS image you " -"want to install." -msgstr "" - -#: ../../installation/virtual/gns3.rst:105 eae9f37ff483461a840a3bf270deaf95 -msgid "" -"You probably will want to accept to copy the .iso file to your default image" -" directory when you are asked." -msgstr "" - -#: ../../installation/virtual/gns3.rst:108 890f523013494c0d91680bc4bd25e94e -msgid "" -"In the **Network** tab, set **0** as the number of adapters, set the **Name" -" format** to **eth{0}** and the **Type** to **Paravirtualized Network I/O " -"(virtio-net-pci)**." -msgstr "" - -#: ../../installation/virtual/gns3.rst:114 248a7d78425745fc870e7fb8b7a22f4f -msgid "" -"In the **Advanced** tab, unmark the checkbox **Use as a linked base VM** and" -" click ``OK``, which will save and close the **QEMU VM template " -"configuration** window." -msgstr "" - -#: ../../installation/virtual/gns3.rst:120 eab096f81def44528aa5cc6a42033a43 -msgid "At the general **Preferences** window, click ``OK`` to save and close." -msgstr "" - -#: ../../installation/virtual/gns3.rst:128 b21171fa3c3c4399b80b7dc46f86fdb8 -msgid "VyOS installation" -msgstr "" - -#: ../../installation/virtual/gns3.rst:130 7969432b0ff5436ca4214ad4e2630a9a -msgid "Create a new project." -msgstr "" - -#: ../../installation/virtual/gns3.rst:131 f7f3ecc9a05d4424b10a288f8d45448c -msgid "Drag the newly created VyOS VM into it." -msgstr "" - -#: ../../installation/virtual/gns3.rst:132 2160544141e2421ca6dbf7e78364b9ef -msgid "Start the VM." -msgstr "" - -#: ../../installation/virtual/gns3.rst:133 e39f1f4303ee4dafae0e820347879114 -msgid "" -"Open a console. The console should show the system booting. It will ask for " -"the login credentials, you are at the VyOS live system." -msgstr "" - -#: ../../installation/virtual/gns3.rst:136 118f0f467c8749ebaba3a8b3ea92f4e0 -msgid "" -":ref:`Install VyOS <installation>` as normal (that is, using the ``install " -"image`` command)." -msgstr "" - -#: ../../installation/virtual/gns3.rst:139 8f543a9741a943d2ab594d1fb6d39926 -msgid "" -"After a successful installation, shutdown the VM with the ``poweroff`` " -"command." -msgstr "" - -#: ../../installation/virtual/gns3.rst:142 cbe7f865ad8341b3985578738b0676d6 -msgid "**Delete the VM** from the GNS3 project." -msgstr "" - -#: ../../installation/virtual/gns3.rst:144 1b6c466497914ee0872ac08a2be6aed8 -msgid "" -"The *VyOS-hda.qcow2* file now contains a working VyOS image and can be used " -"as a template. But it still needs some fixes before we can deploy VyOS in " -"our labs." -msgstr "" - -#: ../../installation/virtual/gns3.rst:151 ab7dffc08b9c4cd9971918547dbcc5bd -msgid "VyOS VM configuration" -msgstr "" - -#: ../../installation/virtual/gns3.rst:153 2d7191527c3f4d1c9403c0dca86d7d29 -msgid "" -"To turn the template into a working VyOS machine, further steps are " -"necessary as outlined below:" -msgstr "" - -#: ../../installation/virtual/gns3.rst:156 e308eafc6665484e8f9548a50fa467f3 -msgid "**General settings** tab: Set the boot priority to **HDD**" -msgstr "" - -#: ../../installation/virtual/gns3.rst:160 cadf4c7803ef4421ae22d52d4bf84e0d -msgid "" -"**CD/DVD** tab: Unmount the installation image file by clearing the " -"**Image** entry field." -msgstr "" - -#: ../../installation/virtual/gns3.rst:165 9cbd825376ff4f0c9644bfee0c701565 -msgid "Set the number of required network adapters, for example **4**." -msgstr "" - -#: ../../installation/virtual/gns3.rst:169 f3632f8c0d2f4a67a40ba08748db0af0 -msgid "" -"**Advanced** settings tab: Mark the checkbox **Use as a linked base VM** and" -" click ``OK`` to save the changes." -msgstr "" - -#: ../../installation/virtual/gns3.rst:174 4af8928d3af6409d8a8daa4e0cdd2e80 -msgid "The VyOS VM is now ready to be deployed." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/index.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/index.po deleted file mode 100644 index 33d5e60a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/index.po +++ /dev/null @@ -1,27 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/index.rst:5 -#: ../../installation/virtual/index.rst:5 8d13ea4974c84a9fbbf395d81784b069 -msgid "Content" -msgstr "" - -#: ../../installation/virtual/index.rst:3 965e6196f8a340e5b2eab3c81fafed87 -msgid "Running VyOS in Virtual Environments" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/libvirt.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/libvirt.po deleted file mode 100644 index a9f9b1e8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/libvirt.po +++ /dev/null @@ -1,145 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/libvirt.rst:5 f0008572e88445bcb096f0246384dd98 -msgid "Running on Libvirt Qemu/KVM" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:7 47f10157b71a4da78dfc3020f2bd7c99 -msgid "" -"Libvirt is an open-source API, daemon and management tool for managing " -"platform virtualization. There are several ways to deploy VyOS on libvirt " -"kvm. Use Virt-manager and native CLI. In an example we will be use use 4 " -"gigabytes of memory, 2 cores CPU and default network virbr0." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:13 5c22744a65364b9c8192ac8248477728 -msgid "CLI" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:16 -#: ../../installation/virtual/libvirt.rst:106 37701fa021344783a5eb1bea3d36c7a5 -#: 8ffdfd17fce449a28ce0b9e76f31444a -msgid "Deploy from ISO" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:18 a0e33271964d47348a9b1c30d2b478bc -msgid "" -"Create VM name ``vyos_r1``. You must specify the path to the ``ISO`` image, " -"the disk ``qcow2`` will be created automatically. The ``default`` network is" -" the virtual network (type Virtio) created by the hypervisor with NAT." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:37 4006d21c45ff441185a4efc6b007b595 -msgid "Connect to VM with command ``virsh console vyos_r1``" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:51 2a148a4f7e71456d996a9fa1907d5f76 -msgid "" -"After installation - exit from the console using the key combination ``Ctrl " -"+ ]`` and reboot the system." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:55 -#: ../../installation/virtual/libvirt.rst:138 2027bdfe29784926a2e1660690717f2b -#: 6ed6dadaf30141eaae76e5507fae6bc4 -msgid "Deploy from qcow2" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:56 9293bb985ef846e78bb09a104494d3d0 -msgid "" -"The convenience of using :abbr:`KVM (Kernel-based Virtual Machine)` images " -"is that they don't need to be installed. Download predefined VyOS.qcow2 " -"image for ``KVM``" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:64 0abd6ba4f44647cabf2932f3ba98edd1 -msgid "Create VM with ``import`` qcow2 disk option." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:81 5412292fb4f247259f7403c884c0e387 -msgid "Connect to VM with command ``virsh console vyos_r2``" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:95 4b25d4e3f7da4488955acbb964028637 -msgid "The system is fully operational." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:98 7ed2ae6789fd4c2ab671eba9ac022830 -msgid "Virt-manager" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:99 f52816d100a141b1ace9e5f9bed12baf -msgid "" -"The virt-manager application is a desktop user interface for managing " -"virtual machines through libvirt. On the linux open :abbr:`VMM (Virtual " -"Machine Manager)`." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:108 -#: ../../installation/virtual/libvirt.rst:147 6b57a9b7bd9b4049b46198feb8c5cc31 -#: 4e58333c3e064708865af997fe67e292 -msgid "" -"Open :abbr:`VMM (Virtual Machine Manager)` and Create a new :abbr:`VM " -"(Virtual Machine)`" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:111 2c33ed8e9a9d4b769ee04a3d7a41c4df -msgid "Choose ``Local install media`` (ISO)" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:115 1ba707bd549741059753804d78c08b70 -msgid "Choose path to iso vyos.iso. Operating System can be any Debian based." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:119 -#: ../../installation/virtual/libvirt.rst:159 40b1e7fb74514a34bbd74735eb8c2db4 -#: 180fd9e34d80460499ae86a906bc648f -msgid "Choose Memory and CPU" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:123 043a94f2ad184a54b85cfe122df80c51 -msgid "Disk size" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:127 -#: ../../installation/virtual/libvirt.rst:163 a51c645b60294e24b691c5b00674887a -#: e4c575f734144b078706f8d761524b13 -msgid "Name of VM and network selection" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:131 -#: ../../installation/virtual/libvirt.rst:167 af2b088cd73b4863af1d46e0a71ca137 -#: d357b5879faf46539dea7ce34897689e -msgid "Then you will be taken to the console." -msgstr "" - -#: ../../installation/virtual/libvirt.rst:140 17d5dfa1c676452fb1751d92f820d3da -msgid "Download predefined VyOS.qcow2 image for ``KVM``" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:150 a8bc50e19568419db10b3f3cce916484 -msgid "Choose ``Import existing disk`` image" -msgstr "" - -#: ../../installation/virtual/libvirt.rst:154 5ba3c762d3d34790a02348f924e57eca -msgid "" -"Choose the path to the image ``vyos_kvm.qcow2`` that was previously " -"downloaded . Operation System can be any Debian based." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/proxmox.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/proxmox.po deleted file mode 100644 index d959ad4b..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/proxmox.po +++ /dev/null @@ -1,109 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/proxmox.rst:5 b3e9aad681dd447887ae9140347f21b2 -msgid "Running on Proxmox" -msgstr "" - -#: ../../installation/virtual/proxmox.rst:7 7194da3ee9ea43ec8a564cf9b6a4e7d3 -msgid "" -"Proxmox is an open-source platform for virtualization. Please visit " -"https://vyos.io to see how to get a qcow2 image that can be imported into " -"Proxmox." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:12 bc9c9e95eced40b3ae46198ac58eef57 -msgid "Deploy VyOS from CLI with qcow2 image" -msgstr "" - -#: ../../installation/virtual/proxmox.rst:14 a94887add5464a1d9d93c4cf4e0704b3 -msgid "Copy the qcow2 image to a temporary directory on the Proxmox server." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:15 fe36c17aa6604d778f1a3755c815702f -msgid "" -"The commands below assume that virtual machine ID 200 is unused and that the" -" user wants the disk stored in a storage pool called `local-lvm`." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:24 22b8595494784c2b9a0bbed0bd9c9862 -msgid "" -"Optionally, the user can attach a CDROM with an ISO as a cloud-init data " -"source. The below command assumes the ISO has been uploaded to the `local` " -"storage pool with the name `seed.iso`." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:30 acf8c1d592794237b457cdbe7ac9e567 -msgid "" -"Start the virtual machine in the proxmox GUI or CLI using ``qm start 200``." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:35 cac9f4730d8c4fb69e0cfd86e684a2b9 -msgid "Deploy VyOS from CLI with rolling release ISO" -msgstr "" - -#: ../../installation/virtual/proxmox.rst:37 14dce67382db4ed99b531fb351a78e32 -msgid "" -"Download the rolling release iso from https://vyos.net/get/nightly-builds/. " -"Non-subscribers can always get the LTS release by building it from source. " -"Instructions can be found in the :ref:`build` section of this manual. VyOS " -"source code repository is available https://github.com/vyos/vyos-build." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:38 619685ca109841d1b988e3ec546ca660 -msgid "" -"Prepare VM for installation from ISO media. The commands below assume that " -"your iso is available in a storage pool 'local', that you want it to have a " -"VM ID '200' and want to create a new disk on storage pool 'local-lvm' of " -"size 15GB." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:44 ddd5751e6a6d441ca71cfa9ee430010a -msgid "" -"Start the VM using the command ``qm start 200`` or using the start button " -"located in the proxmox GUI." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:45 dc53b4df10bd485aaf143c4a6466e7f0 -msgid "" -"Using the proxmox webGUI, open the virtual console for your newly created " -"vm. Login username/password is ``vyos/vyos``." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:46 9054cf21d938426f9c41db249eab92c0 -msgid "" -"Once booted into the live system, type ``install image`` into the command " -"line and follow the prompts to install VyOS to the virtual drive." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:47 da3dc20f35c248fb94e8352f61a820b3 -msgid "" -"After installation has completed, remove the installation iso using the GUI " -"or ``qm set 200 --ide2 none``." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:48 7ed6619780424d4a8a02ae3994f5b5ca -msgid "Reboot the virtual machine using the GUI or ``qm reboot 200``." -msgstr "" - -#: ../../installation/virtual/proxmox.rst:54 60df13d93faa49df813fab3520bf6e20 -msgid "" -"Visit https://www.proxmox.com/en/ for more information about the download " -"and installation of this hypervisor." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/vmware.po b/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/vmware.po deleted file mode 100644 index 3f0e7393..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/virtual/vmware.po +++ /dev/null @@ -1,77 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/virtual/vmware.rst:4 a2b3cf871b5044be993a3addf745b9ba -msgid "Running on VMware ESXi" -msgstr "" - -#: ../../installation/virtual/vmware.rst:7 473774cecd0340de9895c4e06ae58c65 -msgid "ESXi 5.5 or later" -msgstr "" - -#: ../../installation/virtual/vmware.rst:9 38ef355b44814e6d9e1149e7d8ad6bbf -msgid "" -".ova files are available for supporting users, and a VyOS can also be stood " -"up using a generic Linux instance, and attaching the bootable ISO file and " -"installing from the ISO using the normal process around `install image`." -msgstr "" - -#: ../../installation/virtual/vmware.rst:13 a5013b0cc45d465daf2cc3afa30dfd70 -msgid "" -"There have been previous documented issues with GRE/IPSEC tunneling using " -"the E1000 adapter on the VyOS guest, and use of the VMXNET3 has been " -"advised." -msgstr "" - -#: ../../installation/virtual/vmware.rst:18 446e59e446464404bdc1e4961a6157af -msgid "Memory Contention Considerations" -msgstr "" - -#: ../../installation/virtual/vmware.rst:19 06ffc58e4e5145d7b22820fa538f9b8d -msgid "" -"When the underlying ESXi host is approaching ~92% memory utilisation it will" -" start the balloon process in a 'soft' state to start reclaiming memory " -"from guest operating systems. This causes an artificial pressure using the " -"vmmemctl driver on memory usage on the virtual guest. As VyOS by default " -"does not have a swap file, this vmmemctl pressure is unable to force " -"processes to move in memory data to the paging file, and blindly consumes " -"memory forcing the virtual guest into a low memory state with no way to " -"escape. The balloon can expand to 65% of guest allocated memory, so a VyOS " -"guest running >35% of memory usage, can encounter an out of memory " -"situation, and trigger the kernel oom_kill process. At this point a weighted" -" lottery favouring memory hungry processes will be run with the unlucky " -"winner being terminated by the kernel." -msgstr "" - -#: ../../installation/virtual/vmware.rst:31 39109531e93a4492857884e1380a0591 -msgid "" -"It is advised that VyOS routers are configured in a resource group with " -"adequate memory reservations so that ballooning is not inflicted on virtual " -"VyOS guests." -msgstr "" - -#: ../../installation/virtual/vmware.rst:40 df3f0648ee1746588cad5a6b6bbcb671 -msgid "References" -msgstr "" - -#: ../../installation/virtual/vmware.rst:44 ed21fcd7f7ee43fdbf90533fda71ac08 -msgid "" -"https://muralidba.blogspot.com/2018/03/how-does-linux-out-of-memory-oom-" -"killer.html" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/installation/vyos-on-baremetal.po b/docs/_locale/de_DE/LC_MESSAGES/installation/vyos-on-baremetal.po deleted file mode 100644 index 637aa071..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/installation/vyos-on-baremetal.po +++ /dev/null @@ -1,721 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../installation/vyos-on-baremetal.rst:5 8e7a32eec98743bda7ab40f8a68d61e2 -msgid "Running on Bare Metal" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:8 c124e8a9a6a64e4490245b987d824f21 -msgid "Supermicro A2SDi (Atom C3000)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:10 -#: 95f65d3535a9454a9e18276749bcfba1 -msgid "" -"I opted to get one of the new Intel Atom C3000 CPUs to spawn VyOS on it. " -"Running VyOS on an UEFI only device is supported as of VyOS release 1.2." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:14 -#: ../../installation/vyos-on-baremetal.rst:99 -#: 27c704bb667c4136b7d59b0dc302f061 0e83e49a53e64642b563b0474691e0d2 -msgid "Shopping Cart" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:16 -#: d7afe8a90ad54b61b93ab2458154cd11 -msgid "1x Supermicro CSE-505-203B (19\" 1U chassis, inkl. 200W PSU)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:17 -#: a25594b867d54336a292448e2b3f6155 -msgid "1x Supermicro MCP-260-00085-0B (I/O Shield for A2SDi-2C-HLN4F)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:18 -#: 063d4775673044a69eb41aeb9f901e49 -msgid "" -"1x Supermicro A2SDi-2C-HLN4F (Intel Atom C3338, 2C/2T, 4MB cache, Quad LAN " -"with Intel C3000 SoC 1GbE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:20 -#: c341cca9d2224b3ba73532daf249f6de -msgid "1x Crucial CT4G4DFS824A (4GB DDR4 RAM 2400 MT/s, PC4-19200)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:21 -#: 010e2f44a626433fbef867b194c3462c -msgid "" -"1x SanDisk Ultra Fit 32GB (USB-A 3.0 SDCZ43-032G-G46 mass storage for OS)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:22 -#: 144f73c3dbcb4d66bc9ec750e530633e -msgid "1x Supermicro MCP-320-81302-0B (optional FAN tray)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:25 -#: 9c4a0173e69643b4af1f8a663a07a024 -msgid "Optional (10GE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:26 -#: c2e3e2cf5c414125a8246f85b4573ce1 -msgid "" -"If you want to get additional ethernet ports or even 10GE connectivity the " -"following optional parts will be required:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:29 -#: ae5fa5af8ec94cb6a7294037a23a0902 -msgid "1x Supermicro RSC-RR1U-E8 (Riser Card)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:30 -#: 2b900ae5b72343a68b9df602868e6a93 -msgid "1x Supermicro MCP-120-00063-0N (Riser Card Bracket)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:32 -#: 2f923d1dbbeb4a3dba0bd749d3afbad4 -msgid "" -"Latest VyOS rolling releases boot without any problem on this board. You " -"also receive a nice IPMI interface realized with an ASPEED AST2400 BMC (no " -"information about `OpenBMC <https://www.openbmc.org/>`_ so far on this " -"motherboard)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:38 -#: ../../installation/vyos-on-baremetal.rst:234 -#: 52c9d4d599744b729f1f77efc7c2f187 3ac41c66b7f14d32aba12667f766c629 -msgid "Pictures" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: ea345bca59804c74b29ab0f8fa29337a -msgid "CSE-505-203B Back" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: b4a56fc0b6e8455f8d752197c7113118 -msgid "CSE-505-203B Front" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: e34fe33bf3924df0a078bd0f47d4e45c -msgid "CSE-505-203B Open 1" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 7249cfcd4ce044b192227711b35ec20e -msgid "CSE-505-203B Open 2" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: fd17c347a54c496aa0d0da58b9868365 -msgid "CSE-505-203B Open 3" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 9c76655df31b4954b61d10913108685c -msgid "CSE-505-203B w/ 10GE Open 1" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: d926a47486fb465bb97cdfa74df18a17 -msgid "CSE-505-203B w/ 10GE Open 2" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: a2dec518d81b4fb5bda40e38491e773a -msgid "CSE-505-203B w/ 10GE Open 3" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 29b4a8f350dc443ba015e7da4ffefb79 -msgid "CSE-505-203B w/ 10GE Open" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:80 -#: 2c38c6c90bd6429bbbd3927857d8cf41 -msgid "PC Engines APU4" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:82 -#: 0dc4a02909fb4c89bbe8dc5e835a80bc -msgid "" -"As this platform seems to be quite common in terms of noise, cost, power and" -" performance it makes sense to write a small installation manual." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:85 -#: d5e52b352a174c399726984bf290a61d -msgid "" -"This guide was developed using an APU4C4 board with the following specs:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:87 -#: c22daed8beec4bf29c2aee339acb2e53 -msgid "" -"AMD Embedded G series GX-412TC, 1 GHz quad Jaguar core with 64 bit and AES-" -"NI support, 32K data + 32K instruction cache per core, shared 2MB L2 cache." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:89 -#: 29ceb5c8944244d8834fabfaf27813d1 -msgid "4 GB DDR3-1333 DRAM, with optional ECC support" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:90 -#: 5a1c30feffc64aa1a31551c0bb3f9b50 -msgid "About 6 to 10W of 12V DC power depending on CPU load" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:91 -#: c471341bf58f4140b156723411ce1ec7 -msgid "2 miniPCI express (one with SIM socket for 3G modem)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:92 -#: f8ec2a08aac94956876eaec078c84b71 -msgid "4 Gigabit Ethernet channels using Intel i211AT NICs" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:94 -#: 8951e2b33cc643e09d881c54b991d509 -msgid "" -"The board can be powered via 12V from the front or via a 5V onboard " -"connector." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:101 -#: d284cf2eea034cc89e03e35566087334 -msgid "1x apu4c4 = 4 i211AT LAN / AMD GX-412TC CPU / 4 GB DRAM / dual SIM" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:102 -#: 54fbc4b07b7c48bdba72e3514da310b7 -msgid "1x Kingston SUV500MS/120G" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:103 -#: 1e85d2acd76a4f899357b8cd4f4d6e8a -msgid "1x VARIA Group Item 326745 19\" dual rack for APU4" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:105 -#: 0109280c296e4904b729e1d45195741b -msgid "" -"The 19\" enclosure can accommodate up to two APU4 boards - there is a single" -" and dual front cover." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:109 -#: 457f47ea4e154826b84fcd056273c007 -msgid "Extension Modules" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:112 -#: 983f803974ca4b678ea84618a9d6b13c -msgid "WiFi" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:114 -#: 6a194f41901b4afaa974aa1844cf0abf -msgid "" -"Refer to :ref:`wireless-interface` for additional information, below listed " -"modules have been tested successfully on this Hardware platform:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:117 -#: 3be831e611714b58b16ff211eb6c455e -msgid "Compex WLE900VX mini-PCIe WiFi module, only supported in mPCIe slot 1." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:118 -#: 664456ed80f94277aee202b02e09e9ff -msgid "" -"Intel Corporation AX200 mini-PCIe WiFi module, only supported in mPCIe slot " -"1. (see :ref:`wireless-interface-intel-ax200`)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:122 -#: 117a976116cc448f8b953d3ddaa5e046 -msgid "WWAN" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:124 -#: f869c80817274c21ab36e2e1ac93d942 -msgid "" -"Refer to :ref:`wwan-interface` for additional information, below listed " -"modules have been tested successfully on this Hardware platform using VyOS " -"1.3 (equuleus):" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:128 -#: 5177f6c2235540008c75c2f10ff14391 -msgid "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:129 -#: a2b67bed3ddc4a1c829bf0b3cf4ddd26 -msgid "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:130 -#: 26b8efbcd29f43ec84a4dbf04a028ad4 -msgid "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:131 -#: a82d18b3d06e4025a2b5d939b680dd7a -msgid "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:132 -#: 869c3b53134c4a219cfc05e87d39f9fe -msgid "Huawei ME909u-521 miniPCIe card (LTE)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:135 -#: 7df089afdd8d4834983b6598332d5a48 -msgid "VyOS 1.2 (crux)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:137 -#: 2d92a94ed5204f158c62352f4931e57b -msgid "" -"Depending on the VyOS versions you intend to install there is a difference " -"in the serial port settings (:vytask:`T1327`)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:140 -#: 0b550cc205e649aebaf71bbc37a52806 -msgid "Create a bootable USB pendrive using e.g. Rufus_ on a Windows machine." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:142 -#: 1f4b2a8ca78647fb9870283ae6bb4657 -msgid "" -"Connect serial port to a PC through null modem cable (RXD / TXD crossed " -"over). Set terminal emulator to 115200 8N1." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:166 -#: f3fc029ae7534cd78b815e632e87b6b1 -msgid "" -"Now boot from the ``USB MSC Drive Generic Flash Disk 8.07`` media by " -"pressing ``2``, the VyOS boot menu will appear, just wait 10 seconds or " -"press ``Enter`` to continue." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:180 -#: c53bc9d3bb19476db28ff47cc20fa814 -msgid "The image will be loaded and the last lines you will get will be:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:187 -#: 9d3224e040e54519af4acad6aedaae71 -msgid "" -"The Kernel will now spin up using a different console setting. Set terminal " -"emulator to 9600 8N1 and after a while your console will show:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:198 -#: 8f00c4a86b4543698d6356aac8a959c0 -msgid "" -"You can now proceed with a regular image installation as described in " -":ref:`installation`." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:201 -#: 1f7a365fd188432a9883fc37ef2b15f7 -msgid "" -"As the APU board itself still used a serial setting of 115200 8N1 it is " -"strongly recommended that you change the VyOS serial interface settings " -"after your first successful boot." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:205 -#: f18e2c9ccb5e4df9b76ccf1398d34fde -msgid "" -"Use the following command to adjust the :ref:`serial-console` settings:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:211 -#: c7e72a8dfc0d4136b1e1f3fcf24cd2c8 -msgid "" -"Once you ``commit`` the above changes access to the serial interface is lost" -" until you set your terminal emulator to 115200 8N1 again." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:222 -#: daed4aafadd949f59feb171832cef053 -msgid "VyOS 1.2 (rolling)" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:224 -#: 91df2b91131a40ffaca76243a788cc7a -msgid "" -"Installing the rolling release on an APU2 board does not require any change " -"on the serial console from your host side as :vytask:`T1327` was " -"successfully implemented." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:228 -#: c8b3f00d00844e588f664c8df7999457 -msgid "" -"Simply proceed with a regular image installation as described in " -":ref:`installation`." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:236 -#: 11d482874cf84affb94ccee27e456ff5 -msgid "" -"Both device types operate without any moving parts and emit zero noise." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:240 -#: d37dd0a2d49f4c6180670a881632dfa3 -msgid "Rack Mount" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: c104e1b7b84e476197ca5b65b6fa6c57 -msgid "APU4 rack closed" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 6f8c203e0e3d46fcb28572bcba5a419b -msgid "APU4 rack front" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 23b05cb8f739453e9d411ff3cfb559d7 -msgid "APU4 rack module #1" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: b2f0adc7819e49ff9702f2fdf55a8b09 -msgid "APU4 rack module #2" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 012bcb71f0f047d0a5302b07c0f9bc44 -msgid "APU4 rack module #3 with PSU" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:263 -#: daa73d10f7754512a31d8b991b008ae5 -msgid "VyOS custom print" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: 3fcc86b62a7043ee868683836831e8c7 -msgid "APU4 custom VyOS powder coat" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:270 -#: e246d0972fab42d9ba5b5b2bcf9b0b44 -msgid "Desktop / Bench Top" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: ../../installation/vyos-on-baremetal.rstNone -#: 89bd6da3ee2b499aa15709cccb7c9b61 09fae7f32dc343bf8efebaae1d687709 -msgid "APU4 desktop closed" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rstNone -#: ../../installation/vyos-on-baremetal.rstNone -#: 564838002aa6489b9c94fc36b3d044c7 77c08acd2bb34af28767dcc76a975bf4 -msgid "APU4 desktop back" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:291 -#: 185f527c34094e5290f6bb13fa383a43 -msgid "Qotom Q355G4" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:293 -#: 5616fabffaea49f78d94a9220c76943a -msgid "" -"The install on this Q355G4 box is pretty much plug and play. The port " -"numbering the OS does might differ from the labels on the outside, but the " -"UEFI firmware has a port blink test built in with MAC addresses so you can " -"very quickly identify which is which. MAC labels are on the inside as well, " -"and this test can be done from VyOS or plain Linux too. Default settings in " -"the UEFI will make it boot, but depending on your installation wishes (i.e. " -"storage type, boot type, console type) you might want to adjust them. This " -"Qotom company seems to be the real OEM/ODM for many other relabelling " -"companies like Protectli." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:304 -#: c7af81d47fb34b6cad4c642a75ea1752 -msgid "Hardware" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:306 -#: 0698586eb101487483957fd02792d42f -msgid "" -"There are a number of other options, but they all seem to be close to Intel " -"reference designs, with added features like more serial ports, more network " -"interfaces and the likes. Because they don't deviate too much from standard " -"designs all the hardware is well-supported by mainline. It accepts one " -"LPDDR3 SO-DIMM, but chances are that if you need more than that, you'll also" -" want something even beefier than an i5. There are options for antenna " -"holes, and SIM slots, so you could in theory add an LTE/Cell modem (not " -"tested so far)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:314 -#: 1bfefde38d5b408388f8543557528b82 -msgid "" -"The chassis is a U-shaped alu extrusion with removable I/O plates and " -"removable bottom plate. Cooling is completely passive with a heatsink on the" -" SoC with internal and external fins, a flat interface surface, thermal pad " -"on top of that, which then directly attaches to the chassis, which has fins " -"as well. It comes with mounting hardware and rubber feet, so you could place" -" it like a desktop model or mount it on a VESA mount, or even wall mount it " -"with the provided mounting plate. The closing plate doubles as internal " -"2.5\" mounting place for an HDD or SSD, and comes supplied with a small SATA" -" cable and SATA power cable." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:324 -#: 23db9024dd4b41a58e0bf7d2a57c52cb -msgid "" -"Power supply is a 12VDC barrel jack, and included switching power supply, " -"which is why SATA power regulation is on-board. Internally it has a NUC-" -"board-style on-board 12V input header as well, the molex locking style." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:328 -#: e3ac4d52dbf2455d95548f9886a905b9 -msgid "" -"There are WDT options and auto-boot on power enable, which is great for " -"remote setups. Firmware is reasonably secure (no backdoors found, BootGuard " -"is enabled in enforcement mode, which is good but also means no coreboot " -"option), yet has most options available to configure (so it's not locked out" -" like most firmwares are)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:334 -#: d47bef1aca884a2b81726bc1246d9168 -msgid "" -"An external RS232 serial port is available, internally a GPIO header as " -"well. It does have Realtek based audio on board for some reason, but you can" -" disable that. Booting works on both USB2 and USB3 ports. Switching between " -"serial BIOS mode and HDMI BIOS mode depends on what is connected at startup;" -" it goes into serial mode if you disconnect HDMI and plug in serial, in all " -"other cases it's HDMI mode." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:342 -#: c44f862a5e7b41838c5c7f777c5d4046 -msgid "Partaker i5" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:346 -#: 66e8c7471d1e4094bf8c49b89263c05f -msgid "" -"I believe this is actually the same hardware as the Protectli. I purchased " -"it in June 2018. It came pre-loaded with pfSense." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:349 -#: 1b267ff0539b4121b740d8d95dfa3371 -msgid "" -"`Manufacturer product page " -"<http://www.inctel.com.cn/product/detail/338.html>`_." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:352 -#: 408929c2e7554bcf8cded0671b454a60 -msgid "Installation" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:354 -#: 0d466c39265c45f683231dc9a1bc1ecd -msgid "Write VyOS ISO to USB drive of some sort" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:355 -#: 77ab3d1a2c854b77b6a298e7c2cc2cb1 -msgid "Plug in VGA, power, USB keyboard, and USB drive" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:356 -#: 38a45a7215464976adf38c186d0c1ebb -msgid "" -"Press \"SW\" button on the front (this is the power button; I don't know " -"what \"SW\" is supposed to mean)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:358 -#: b116fd8faf184dcc8e8b7257ec2fbbd0 -msgid "" -"Begin rapidly pressing delete on the keyboard. The boot prompt is very " -"quick, but with a few tries you should be able to get into the BIOS." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:360 -#: d6966a1c06d243f69601a83562a6aa94 -msgid "" -"Chipset > South Bridge > USB Configuration: set XHCI to Disabled and USB 2.0" -" (EHCI) to Enabled. Without doing this, the USB drive won't boot." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:362 -#: bd6e4a58cc3143918e5f9db7458ff958 -msgid "Boot to the VyOS installer and install as usual." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:364 -#: 6a3b402c793740dfae1b88145a4a9fdd -msgid "" -"Warning the interface labels on my device are backwards; the left-most " -"\"LAN4\" port is eth0 and the right-most \"LAN1\" port is eth3." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:368 -#: 830486cce6e44d1d94b95ced4e031b78 -msgid "Acrosser AND-J190N1" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:374 -#: 7e8b04b458f14a9e9311963d21bb040c -msgid "" -"This microbox network appliance was build to create OpenVPN bridges. It can " -"saturate a 100Mbps link. It is a small (serial console only) PC with 6 Gb " -"LAN" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:377 -#: d4c963c5070940b4ad5c2662e1b2b020 -msgid "" -"You may have to add your own RAM and HDD/SSD. There is no VGA connector. But" -" Acrosser provides a DB25 adapter for the VGA header on the motherboard (not" -" used)." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:382 -#: 76d6b00902e940feae962ea15aa7a159 -msgid "BIOS Settings:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:384 -#: 0e2ee6388ffc4afe8fd7ba1986abeea0 -msgid "" -"First thing you want to do is getting a more user friendly console to " -"configure BIOS. Default VT100 brings a lot of issues. Configure VT100+ " -"instead." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:387 -#: 60461d76182748f18e6207e20aa67341 -msgid "" -"For practical issues change speed from 115200 to 9600. 9600 is the default " -"speed at which both linux kernel and VyOS will reconfigure the serial port " -"when loading." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:391 -#: c859a82e0e6a4f788a180294f022bb30 -msgid "" -"Connect to serial (115200bps). Power on the appliance and press Del in the " -"console when requested to enter BIOS settings." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:394 -#: 77b22ac0281b49f59f35181e90d94b61 -msgid "" -"Advanced > Serial Port Console Redirection > Console Redirection Settings:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:396 -#: 981486c6a69f4594884e6daa60c2185f -msgid "Terminal Type : VT100+" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:397 -#: 6fe2e7252e00499ba96f30df1e49ca60 -msgid "Bits per second : 9600" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:399 -#: 73a8c07a8ae643eb95c255bfa0e5de68 -msgid "Save, reboot and change serial speed to 9600 on your client." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:401 -#: 6839e64e4a0a4e5ea4240b13ff377baf -msgid "" -"Some options have to be changed for VyOS to boot correctly. With XHCI " -"enabled the installer can’t access the USB key. Enable EHCI instead." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:404 -#: f94e8aa026d44d5882a0e2c7131af45b -msgid "Reboot into BIOS, Chipset > South Bridge > USB Configuration:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:406 -#: 5e868101e2e54d249efafd09fdc9258d -msgid "Disable XHCI" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:407 -#: ac48de7d4c864d5194f77ed1aa93f51c -msgid "Enable USB 2.0 (EHCI) Support" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:410 -#: 9e3bf468cfb245c590a238052ce71377 -msgid "Install VyOS:" -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:412 -#: fb03c6f2015f49a3840a95839d795cdb -msgid "" -"Create a VyOS bootable USB key. I used the 64-bit ISO (VyOS 1.1.7) and " -"`LinuxLive USB Creator <http://www.linuxliveusb.com/>`_." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:415 -#: 84566bccc11b402faa1049f925e8653e -msgid "" -"I'm not sure if it helps the process but I changed default option to live-" -"serial (line “default xxxx”) on the USB key under syslinux/syslinux.cfg." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:418 -#: a764445499a0425f9dc3193247ff0efa -msgid "" -"I connected the key to one black USB port on the back and powered on. The " -"first VyOS screen has some readability issues. Press :kbd:`Enter` to " -"continue." -msgstr "" - -#: ../../installation/vyos-on-baremetal.rst:421 -#: ddd942d787aa4a4e8fc5394f78894b90 -msgid "Then VyOS should boot and you can perform the ``install image``" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/introducing/about.po b/docs/_locale/de_DE/LC_MESSAGES/introducing/about.po deleted file mode 100644 index 6c52a6df..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/introducing/about.po +++ /dev/null @@ -1,59 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../introducing/about.rst:5 7ef92e409d124283ba3c08b3004fc559 -msgid "About" -msgstr "" - -#: ../../introducing/about.rst:7 7e645e3be5fc4edea864643b5025bc64 -msgid "" -"VyOS is an open source network operating system based on Debian GNU/Linux." -msgstr "" - -#: ../../introducing/about.rst:9 39564ec52b2f41daa74d831af3501d7e -msgid "" -"VyOS provides a free routing platform that competes directly with other " -"commercially available solutions from well known network providers. Because " -"VyOS runs on standard amd64, i586 and ARM systems, it is able to be used as " -"a router and firewall platform for cloud deployments." -msgstr "" - -#: ../../introducing/about.rst:14 f271e24ebb6d4e1485ff7daeba3c9023 -msgid "" -"We use multiple live versions of our manual, hosted thankfully by " -"https://readthedocs.org. We will provide one version of the manual for every" -" VyOS major version starting with VyOS 1.2 which will receive Long-term " -"support (LTS)." -msgstr "" - -#: ../../introducing/about.rst:19 80530d22f74047d499183c8f57e16ddf -msgid "" -"The manual version is selected/specified by it's Git branch name. You can " -"switch between versions of the documentation by selecting the appropriate " -"branch on the bottom left corner." -msgstr "" - -#: ../../introducing/about.rst:23 69d9cca9615f440d979b5eae71bc4ddb -msgid "" -"VyOS CLI syntax may change between major (and sometimes minor) versions. " -"Please always refer to the documentation matching your current, running " -"installation. If a change in the CLI is required, VyOS will ship a so called" -" migration script which will take care of adjusting the syntax. No action " -"needs to be taken by you." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/introducing/history.po b/docs/_locale/de_DE/LC_MESSAGES/introducing/history.po deleted file mode 100644 index 214841bd..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/introducing/history.po +++ /dev/null @@ -1,204 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:04+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../introducing/history.rst:5 92679ba521274fa488e7f46efaa13edd -msgid "History" -msgstr "" - -#: ../../introducing/history.rst:8 f64b9617922c4c58b0574a5894bf14ab -msgid "In the beginning..." -msgstr "" - -#: ../../introducing/history.rst:10 fe07111ca6964938acf22ebe39ccc9cb -msgid "" -"There once was a network operating system based on Debian GNU/Linux, called " -"Vyatta. [*]_ 2006 onwards, it was a great free software alternative to Cisco" -" IOS and Jupiter JUNOS. It came in two editions: Vyatta Core (previously " -"Vyatta Community Edition) that was completely free software, and Vyatta " -"Subscription Edition that had proprietary features and was only available to" -" paying customers. [*]_" -msgstr "" - -#: ../../introducing/history.rst:17 ab01178e86ac4dcdb5df1cd048240165 -msgid "" -"Vyatta was acquired by Brocade Communication Systems in 2012. Shortly after," -" Brocade renamed Vyatta Subscription Edition to Brocade vRouter, " -"discontinued Vyatta Core and shut down the community forum without a notice." -" The bug tracker and Git repositories followed next year." -msgstr "" - -#: ../../introducing/history.rst:22 189b2976f4d84d249d1c86f959eee8f5 -msgid "" -"It's worth noting that by the time Brocade acquired Vyatta, development of " -"Vyatta Core was already stagnated. Vyatta Subscription Edition (and thus, " -"Vyatta development as a whole) had been replacing core components with " -"proprietary software, meaning few features made it to Vyatta Core, and those" -" that did were bug-ridden and hamstrung." -msgstr "" - -#: ../../introducing/history.rst:28 3bbb983d8287496f85bef2c694b73521 -msgid "" -"In 2013, soon after Vyatta Core was abandoned, the community forked the last" -" Vyatta Core version (6.6R1) and VyOS Project came into being. `Sentrium SL " -"<https://blog.vyos.io/sentrium-what-sentrium>`_ was established by VyOS " -"maintainers in 2014 to fund VyOS development by selling support, consulting " -"services and prebuilt long-term support images." -msgstr "" - -#: ../../introducing/history.rst:35 b9e25927bc674f32adb14055ac7e81e3 -msgid "" -"Brocade was acquired by Broadcom in 2016 and sold what remains of erstwhile " -"Vyatta to AT&T in 2017, who in turn sold it to Ciena in 2021." -msgstr "" - -#: ../../introducing/history.rst:40 796f0422308642d697bf3d305478b08c -msgid "Major releases" -msgstr "" - -#: ../../introducing/history.rst:42 02dc2bf11c564fbeb47a184a4a124289 -msgid "" -"VyOS major versions used to be named after elements in order of atomic " -"numbers. With 1.2, this naming scheme was replaced with the much cooler " -"scheme of Latin names of IAU designated constellations by solid angle area, " -"starting from the smallest." -msgstr "" - -#: ../../introducing/history.rst:48 e917d0650eef44f2aa968f436bab5863 -msgid "Hydrogen (1.0)" -msgstr "" - -#: ../../introducing/history.rst:50 9926dc4ce61c41979530a1889b712138 -msgid "" -"Released just in time for holidays on 22 December 2013, Hydrogen was the " -"first major VyOS release. It fixed features that were broken in Vyatta Core " -"6.6 (such as IPv4 BGP peer groups and DHCPv6 relay) and introduced command " -"scripting, a task scheduler and web proxy LDAP authentication." -msgstr "" - -#: ../../introducing/history.rst:57 e215b713cb2b4500a79ecc2a35aada52 -msgid "Helium (1.1)" -msgstr "" - -#: ../../introducing/history.rst:59 61aac3cc2f4141108b184810eb929da3 -msgid "" -"Helium was released on 9 October 2014, exactly on the day VyOS Project first" -" came into being in the previous year. Helium came with a lot of new " -"features, including an event handler and support for L2TPv3, 802.1ad QinQ " -"and IGMP proxy, as well as experimental support for VXLAN and DMVPN (the " -"latter of which was also broken in Vyatta Core due to its reliance on a " -"proprietary NHRP implementation)." -msgstr "" - -#: ../../introducing/history.rst:67 0e87f2f287d44423b7c070f56f29308f -msgid "Crux (1.2)" -msgstr "" - -#: ../../introducing/history.rst:69 4e04657879494617843f21aefb310e7a -msgid "" -"Crux (the Southern Cross) came out on 28 January 2019 and was the first " -"major release of VyOS as we know it today. The underlying Debian base was " -"upgraded from Squeeze (6) to Jessie (8)." -msgstr "" - -#: ../../introducing/history.rst:73 48eaa988a5cf4f58820a8eb4a0e85e12 -msgid "" -"Although Crux came with too many new features to mention here, some " -"noteworthy ones are: an mDNS repeater, a broadcast relay, a high-performance" -" PPPoE server, an HFSC scheduler, as well as support for Wireguard, unicast " -"VRRP, RPKI for BGP and fully 802.1ad-compliant QinQ ethertype. The telnet " -"server and support for P2P filtering were removed." -msgstr "" - -#: ../../introducing/history.rst:80 d53ba7d46aaa40e88ef8974256f505e5 -msgid "" -"Crux is the first version to feature the modular image build system. CLI " -"definitions began to be written in the modern, verifiable XML templates. " -"Python APIs were introduced for command scripting and configuration " -"migration. Introduction of new Perl and shell code was proscribed and the " -"rewriting of legacy Perl code in pure Python began with Crux." -msgstr "" - -#: ../../introducing/history.rst:87 b0975c9e10124a3ca79e24bc2b2e1b23 -msgid "As of 2022, Crux is still supported and maintained." -msgstr "" - -#: ../../introducing/history.rst:90 a7974e8357654b12846fe7b73f5f11b5 -msgid "Equuleus (1.3)" -msgstr "" - -#: ../../introducing/history.rst:92 96758ceaaa8143e2ae43c3f2e4a16153 -msgid "" -"The current long-term support version of VyOS, Equuleus (the Pony) came out " -"on 21 December 2021, once again in time for the winter holidays." -msgstr "" - -#: ../../introducing/history.rst:96 d57924aa6dd44dacbaa7a9d632037ef2 -msgid "" -"Equuleus brought many long-desired features with it, most notably an SSTP " -"VPN server, an IPoE server, an OpenConnect VPN server and a serial console " -"server, in addition to reworked support for WWAN interfaces, support for " -"GENEVE and MACSec interfaces, VRF, IS-IS routing, preliminary support for " -"MPLS and LDP, and many other initialisms." -msgstr "" - -#: ../../introducing/history.rst:103 b8cddced81114e9cb7585d130e0d8c27 -msgid "As of 2022, Equuleus is in the stable." -msgstr "" - -#: ../../introducing/history.rst:106 b5b9b8044acb4810a07643643907d02d -msgid "Sagitta (1.4)" -msgstr "" - -#: ../../introducing/history.rst:108 c6ed9b82778148e4bad8ee6d2cb37a42 -msgid "" -"Sagitta (the Arrow) is the codename of the current development branch, so " -"there's no VyOS 1.4 yet." -msgstr "" - -#: ../../introducing/history.rst:112 397e1ad0e1344ffba177c12aeee3d23d -msgid "A note on copyright" -msgstr "" - -#: ../../introducing/history.rst:114 3339946a4e72456791c32fe028811eb8 -msgid "" -"Unlike Vyatta, VyOS never had (nor will ever have) proprietary code. The " -"only proprietary material in VyOS is non-code assets, such as graphics and " -"the trademark \"VyOS\". [*]_ This means you can build your own long-term " -"support images (as the entire toolchain we use is free software) and even " -"distribute them, given you rename it and remove such assets before building." -" Although note that we do not provide support for images distributed by a " -"third-party. See the `artwork license <https://github.com/vyos/vyos-" -"build/blob/current/LICENSE.artwork>`_ and the end-user license agreement at " -"``/usr/share/vyos/EULA`` in any pre-built image for more precise " -"information." -msgstr "" - -#: ../../introducing/history.rst:126 edb6aabfd1a14491bf565a12e3b13a77 -msgid "From the Sanskrit adjective \"Vyātta\" (व्यात्त), meaning opened." -msgstr "" - -#: ../../introducing/history.rst:127 95a94268612646a2afc9821b4c4f3e55 -msgid "" -"A business model comparable to that of Redis, rather than that of VyOS " -"today." -msgstr "" - -#: ../../introducing/history.rst:129 3aef4a673d9249ecade246fd53f6243d -msgid "This is not unlike how Linus Torvalds owns the trademark \"Linux\"." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/operation/boot-options.po b/docs/_locale/de_DE/LC_MESSAGES/operation/boot-options.po deleted file mode 100644 index 00b685ed..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/operation/boot-options.po +++ /dev/null @@ -1,81 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../operation/boot-options.rst:6 34b7aabe1aac4016b8ba784085f880e2 -msgid "Boot Options" -msgstr "" - -#: ../../operation/boot-options.rst:8 5e60c3a947ea45f88678169821c6d2bd -msgid "" -"This function may be highly disruptive. It may cause major service " -"interruption, so make sure you really need it and verify your input " -"carefully." -msgstr "" - -#: ../../operation/boot-options.rst:14 44b378c12565441d8e8b93cc89dfc525 -msgid "" -"VyOS has several kernel command line options to modify the normal boot " -"process. To add an option, select the desired image in GRUB menu at load " -"time, press **e**, edit the first line, and press **Ctrl-x** to boot when " -"ready." -msgstr "" - -#: ../../operation/boot-options.rst:26 c8ee85e7861b4d5c8d7864f77d7cec32 -msgid "Specify custom config file" -msgstr "" - -#: ../../operation/boot-options.rst:28 ac051ace16b340d1bd5137e80e669926 -msgid "" -"Tells the system to use specified file instead of ``/config/config.boot``. " -"If specified file does not exist or is not readable, fall back to default " -"config. No additional verification is performed, so make sure you specify a " -"valid config file." -msgstr "" - -#: ../../operation/boot-options.rst:37 5a29fcef15cb453d9278c986cf92d392 -msgid "To load the *factory default* config, use:" -msgstr "" - -#: ../../operation/boot-options.rst:45 8fadf41c77054a4098b4676c8a98ce53 -msgid "Disable specific boot process steps" -msgstr "" - -#: ../../operation/boot-options.rst:47 27fc00209a43448195723cb19e162ad4 -msgid "" -"These options disable some boot steps. Make sure you understand the " -":ref:`boot process <boot-steps>` well before using them!" -msgstr "" - -#: ../../operation/boot-options.rst:51 d1c88ec49cb74b0fb288da67e66f3ed5 -msgid "no-vyos-migrate" -msgstr "" - -#: ../../operation/boot-options.rst:53 069e129f92b444baaf5c1dc74ec39696 -msgid "Do not perform config migration." -msgstr "" - -#: ../../operation/boot-options.rst:54 36e2abe3dfd644be971681c110270abe -msgid "no-vyos-firewall" -msgstr "" - -#: ../../operation/boot-options.rst:56 265ccf0c13d94cc09c669bc089b59cb9 -msgid "" -"Do not initialize default firewall chains, renders any firewall " -"configuration unusable." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/operation/index.po b/docs/_locale/de_DE/LC_MESSAGES/operation/index.po deleted file mode 100644 index 2cfd057e..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/operation/index.po +++ /dev/null @@ -1,22 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../operation/index.rst:3 598a552503b341b3a4545a257d54b34e -msgid "Operation Mode" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/operation/information.po b/docs/_locale/de_DE/LC_MESSAGES/operation/information.po deleted file mode 100644 index a5a6341c..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/operation/information.po +++ /dev/null @@ -1,100 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../operation/information.rst:7 3e04c2ede5f4434e9802db2bb2ed1026 -msgid "Information" -msgstr "" - -#: ../../operation/information.rst:9 d17527c82e9b4f46976ca7ee2856f0a8 -msgid "" -"VyOS features a rich set of operational level commands to retrieve arbitrary" -" information about your running system." -msgstr "" - -#: ../../operation/information.rst:14 f6eede6579304a4eab883028a6274c5d -msgid "Hardware" -msgstr "" - -#: ../../operation/information.rst:19 1bda04084ddd495883df9dfa56a73e08 -msgid "USB" -msgstr "" - -#: ../../operation/information.rst:21 f21e0dac284d48d083dd90f93a7bd682 -msgid "" -"In the past serial interface have been defined as ttySx and ttyUSBx where x " -"was an instance number of the serial interface. It was discovered that from " -"system boot to system boot the mapping of USB based serial interfaces will " -"differ, depending which driver was loaded first by the operating system. " -"This will become rather painful if you not only have serial interfaces for a" -" console server connected but in addition also a serial backed :ref:`wwan-" -"interface`." -msgstr "" - -#: ../../operation/information.rst:28 f4abded20255426ca29936f25cae169f -msgid "" -"To overcome this issue and the fact that in almost 50% of all cheap USB to " -"serial converters there is no serial number programmed, the USB to serial " -"interface is now directly identified by the USB root bridge and bus it " -"connects to. This somehow mimics the new network interface definitions we " -"see in recent Linux distributions." -msgstr "" - -#: ../../operation/information.rst:34 3e9e5b53a47b427dae863bc4b7dc59ef -msgid "" -"For additional details you can refer to https://phabricator.vyos.net/T2490." -msgstr "" - -#: ../../operation/information.rst:38 dab1c26159c944a2a9415bc5a46ead5b -msgid "Retrieve a tree like representation of all connected USB devices." -msgstr "" - -#: ../../operation/information.rst:40 55e3b4b303bc46d48e7dae99cc6ad5ae -msgid "" -"If a device is unplugged and re-plugged it will receive a new Port, Dev, If " -"identification." -msgstr "" - -#: ../../operation/information.rst:74 726b10114caf4175a72ff746a2ffcaf6 -msgid "" -"Retrieve a list and description of all connected USB serial devices. The " -"device name displayed, e.g. `usb0b2.4p1.0` can be directly used when " -"accessing the serial console as console-server device." -msgstr "" - -#: ../../operation/information.rst:104 96156f55c3f141c78afa624bee302afe -msgid "Version" -msgstr "" - -#: ../../operation/information.rst:108 42c437f45340431db595d59b3f211076 -msgid "" -"Return the current running VyOS version and build information. This includes" -" also the name of the release train which is ``crux`` on VyOS 1.2, " -"``equuleus`` on VyOS 1.3 and ``sagitta`` on VyOS 1.4." -msgstr "" - -#: ../../operation/information.rst:137 35d65ed18a1a493dbb12f32d884b3263 -msgid "Return version number of the Linux Kernel used in this release." -msgstr "" - -#: ../../operation/information.rst:146 abf8aa944c7c43e6871c0cd4637869b3 -msgid "" -"Return version number of FRR (Free Range Routing - https://frrouting.org/) " -"used in this release. This is the routing control plane and a successor to " -"GNU Zebra and Quagga." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/operation/password-recovery.po b/docs/_locale/de_DE/LC_MESSAGES/operation/password-recovery.po deleted file mode 100644 index d10b9437..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/operation/password-recovery.po +++ /dev/null @@ -1,35 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../operation/password-recovery.rst:5 822c2ee1471d4325b8b501089bdc9333 -msgid "Password Recovery" -msgstr "" - -#: ../../operation/password-recovery.rst:7 a55e82fae54b49c9b8d1e28a93ca4da1 -msgid "" -"Using the console, restart the VyOS router. The GRUB menu appears. Select " -"the relevant option from the GRUB menu and press Enter. The option must " -"start with “Lost password change.”" -msgstr "" - -#: ../../operation/password-recovery.rst:14 126e8bd305e644a09d26c3bbc841ac14 -msgid "" -"The stand-alone user-password recovery tool starts running and prompts you " -"to reset the local system user password." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/operation/raid.po b/docs/_locale/de_DE/LC_MESSAGES/operation/raid.po deleted file mode 100644 index 12e3f7d3..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/operation/raid.po +++ /dev/null @@ -1,292 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:02+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../operation/raid.rst:5 8abe2416e4c54a95898e5045af714fa2 -msgid "RAID-1" -msgstr "" - -#: ../../operation/raid.rst:7 31b7f797acdd496881d3d456c00500e8 -msgid "" -"A Redundant Array of Independent Disks (RAID) uses two or more hard disk " -"drives to improve disk speed, store more data, and/or provide fault " -"tolerance. There are several storage schemes possible in a RAID array, each " -"offering a different combination of storage, reliability, and/or " -"performance. The VyOS system supports a “RAID 1” deployment. RAID 1 allows " -"two or more disks to mirror one another to provide system fault tolerance. " -"In a RAID 1 solution, every sector of one disk is duplicated onto every " -"sector of all disks in the array. Provided even one disk in the RAID 1 set " -"is operational, the system continues to run, even through disk replacement " -"(provided that the hardware supports in-service replacement of drives). RAID" -" 1 can be implemented using special hardware or it can be implemented in " -"software. The VyOS system supports software RAID 1 on two disks. The VyOS " -"implementation of RAID 1 allows the following:" -msgstr "" - -#: ../../operation/raid.rst:21 4788db78c4d340969d99270ae08cbb65 -msgid "Detection and reporting of disk failure" -msgstr "" - -#: ../../operation/raid.rst:22 55b0150c476f4b3493cea47002404e35 -msgid "The ability to maintain system operation with one failed disk" -msgstr "" - -#: ../../operation/raid.rst:23 d1086f6db7a64c05884982eda55bcf0b -msgid "The ability to boot the system with one failed disk" -msgstr "" - -#: ../../operation/raid.rst:24 024971a9abae449d940a39896da17180 -msgid "The ability to replace a failed disk and initiate re-mirroring" -msgstr "" - -#: ../../operation/raid.rst:25 39410eacfb6d4bc38fe02c2b35358c1a -msgid "The ability to monitor the status of remirroring" -msgstr "" - -#: ../../operation/raid.rst:30 79d828193aa5404fa6e4ee563bd7dab0 -msgid "Installation Implications" -msgstr "" - -#: ../../operation/raid.rst:32 ccb8bfa2250946b39c9ccf53dd52a058 -msgid "" -"The VyOS systems installation utility provides several options for " -"installing to a RAID 1 set. You can:" -msgstr "" - -#: ../../operation/raid.rst:35 f384089c069b45489f7851be80562aea -msgid "Use the install system to create the RAID 1 set" -msgstr "" - -#: ../../operation/raid.rst:36 969d512106294e97a9d295a9348ee785 -msgid "" -"Use the underlying Linux commands to create a RAID 1 set before running the " -"install system command." -msgstr "" - -#: ../../operation/raid.rst:38 3b4e260039c148efa4bc50595bec5255 -msgid "Use a previously-created RAID 1 set." -msgstr "" - -#: ../../operation/raid.rst:40 12f4b1891ad645b4b01019dff98bbd9d -msgid "Before a permanent installation, VyOS runs a live installation" -msgstr "" - -#: ../../operation/raid.rst:43 f18e70b3e08645c6b7eb1131d6973804 -msgid "Configuration" -msgstr "" - -#: ../../operation/raid.rst:46 fe0720c2fbaf4df9b1fd1eb22d694be9 -msgid "Single disk, install as normal" -msgstr "" - -#: ../../operation/raid.rst:48 8346d05daa2c49feb841d76efd00aade -msgid "" -"When the VyOS system is installed, it automatically detects the presence of " -"two disks not currently part of a RAID array. In these cases, the VyOS " -"installation utility automatically offers you the option of configuring RAID" -" 1 mirroring for the drives, with the following prompt." -msgstr "" - -#: ../../operation/raid.rst:57 bd4d74601a174e0bb7d10a181a3b83bc -msgid "" -"If you do not want to configure RAID 1 mirroring, enter “No” at the prompt " -"and continue with installation in the normal way." -msgstr "" - -#: ../../operation/raid.rst:61 fd1ebff1312041d083124a13b363d486 -msgid "Empty 2+ Disk" -msgstr "" - -#: ../../operation/raid.rst:63 1cd151d9e58d46b1962b41f8ca28e934 -msgid "" -"If VyOS system detect two identical disks that are not currently part of a " -"RAID-1 set, the VyOS installation utility automatically offers you the " -"option of configuring RAID 1 mirroring for the drives, with the following " -"prompt." -msgstr "" - -#: ../../operation/raid.rst:71 5841471aeeb24aa98ac6b3268655a75e -msgid "" -"1 - To create a new RAID 1 array, enter “Yes” at the prompt. If the system " -"detects a filesystem on the partitions being used for RAID 1 it will prompt " -"you to indicate whether you want to continue creating the RAID 1 array." -msgstr "" - -#: ../../operation/raid.rst:79 5d4869f90582472eb02342d1b12d0bb6 -msgid "2 - To overwrite the old filesystem, enter “Yes”." -msgstr "" - -#: ../../operation/raid.rst:81 0b105e01f6704142b22bfb920bb621ce -msgid "" -"3 - The system informs you that all data on both drives will be erased. You " -"are prompted to confirm that you want to continue" -msgstr "" - -#: ../../operation/raid.rst:88 ../../operation/raid.rst:139 -#: cc138b5d85f5473788b29826f887e5e4 291b9edb4d2d4d42b72a269eedad1e11 -msgid "" -"4 - Enter “Yes” at the prompt to retain the current VyOS configuration once " -"installation is complete. Enter “No” to delete the current VyOS " -"configuration." -msgstr "" - -#: ../../operation/raid.rst:96 5c438e5d5dbe440da2f2b24a428dc4b0 -msgid "" -"5 - Enter “Yes” at the prompt to retain the current VyOS configuration once " -"installation is complete. Enter “No” to delete the current VyOS " -"configuration." -msgstr "" - -#: ../../operation/raid.rst:99 216dd9724d8d4d43a0ee8fe42a4c0cb1 -msgid "6 - Continue with installation in the normal way." -msgstr "" - -#: ../../operation/raid.rst:103 cfc585da3a3243968028fa2a7a8907fd -msgid "Present RAID-1" -msgstr "" - -#: ../../operation/raid.rst:105 d0b6e258e359431b8e6871e8634b02ce -msgid "" -"When the VyOS software on a system with a RAID 1 set already configured, the" -" installation utility will detect the array and will display the following " -"prompt:" -msgstr "" - -#: ../../operation/raid.rst:113 fea82c29a4c04d3aa8bf297b671e7353 -msgid "" -"1 - To break apart the current RAID 1 set, enter “No” at the prompt. The" -msgstr "" - -#: ../../operation/raid.rst:115 426f28a4f3e546f7b70e5252bc117d34 -msgid "" -"installation utility detects that there are two identical disks and offers " -"you the option of configuring RAID 1 mirroring on them, displaying the " -"following prompt:" -msgstr "" - -#: ../../operation/raid.rst:123 92b55f0ded11482f88f6dc7a1af08179 -msgid "" -"2 - To decline to set up a new RAID 1 configuration on the disks, enter “No”" -" at the prompt. The system prompts you to indicate which partition you would" -" like the system installed on." -msgstr "" - -#: ../../operation/raid.rst:131 b6fb87ffce4f4801ae7844400ed2cc39 -msgid "" -"3 - Enter the partition where you would like the system installed. The " -"system then prompts you to indicate whether you want to save the old " -"configuration data. This represents the current VyOS configuration." -msgstr "" - -#: ../../operation/raid.rst:142 03208977211a4719b09e2d83ef356ed4 -msgid "5 - Continue with installation in the normal way." -msgstr "" - -#: ../../operation/raid.rst:146 7705c479049f483a904bc2b2f2e35a14 -msgid "Detecting and Replacing a Failed RAID 1 Disk" -msgstr "" - -#: ../../operation/raid.rst:148 1eb8bb0fdd8d4f3a89be1ed9dc3e30eb -msgid "" -"The VyOS system automatically detects a disk failure within a RAID 1 set and" -" reports it to the system console. You can verify the failure by issuing the" -" show raid command." -msgstr "" - -#: ../../operation/raid.rst:152 7c31217d95824b99a6fe2760cd766a5e -msgid "" -"To replace a bad disk within a RAID 1 set, perform the following steps:" -msgstr "" - -#: ../../operation/raid.rst:154 ccee9802198440f78e0ac2f810ef8a84 -msgid "" -"1 - Remove the failed disk from the RAID 1 set by issuing the following " -"command:" -msgstr "" - -#: ../../operation/raid.rst:159 ac2d2b70af5c41d298ab9776c4b517cb -msgid "" -"where RAID-1-device is the name of the RAID 1 device (for example, md0) and " -"disk-partition is the name of the failed disk partition (for example, sdb2)." -msgstr "" - -#: ../../operation/raid.rst:162 c128a8085ac44e28b71eab48feb7edac -msgid "" -"2- Physically remove the failed disk from the system. If the drives are not " -"hot-swappable, then you must shut down the system before removing the disk." -msgstr "" - -#: ../../operation/raid.rst:165 8ac3205c869a4ed28c4d94533fb8c640 -msgid "3 - Replace the failed drive with a drive of the same size or larger." -msgstr "" - -#: ../../operation/raid.rst:167 06327ba6cc44456981056752d5627690 -msgid "4 - Format the new disk for RAID 1 by issuing the following command:" -msgstr "" - -#: ../../operation/raid.rst:171 5134ffbe82824c03a5bfa17ac94f8bc4 -msgid "" -"where disk-device1 is the replacement disk (for example, sdb) and disk-" -"device2 is the existing healthy disk (for example, sda)." -msgstr "" - -#: ../../operation/raid.rst:174 d6cb6f83dd214db5aff872af888a8ab5 -msgid "" -"5-Add the replacement disk to the RAID 1 set by issuing the following " -"command:" -msgstr "" - -#: ../../operation/raid.rst:178 f13dc45bed31465ca275ce18cdc71c8a -msgid "" -"where RAID-1-device is the name of the RAID 1 device (for example, md0) and " -"disk-partition is the name of the replacement disk partition (for example, " -"sdb2)." -msgstr "" - -#: ../../operation/raid.rst:183 fb1b5f7e98ed489dac1a04dddf8d7c2d -msgid "Operation" -msgstr "" - -#: ../../operation/raid.rst:185 22bfa805009f418a8c8124a357a580e5 -msgid "" -"This part introduces how to add a disk partition to a RAID-1 set initiates " -"mirror synchronization, check and display information." -msgstr "" - -#: ../../operation/raid.rst:190 36c04e2a41274a86b233584f9bf195e4 -msgid "" -"Use this command to add a member disk partition to the RAID 1 set. Adding a " -"disk partition to a RAID 1 set initiates mirror synchronization, where all " -"data on the existing member partition is copied to the new partition." -msgstr "" - -#: ../../operation/raid.rst:196 717bf326991b4fb09de524f8166459d8 -msgid "" -"This command is typically used to prepare a disk to be added to a " -"preexisting RAID 1 set (of which disk-device2 is already a member)." -msgstr "" - -#: ../../operation/raid.rst:201 cea60e704d024699b6834b9aab159ab5 -msgid "" -"shows output for show raid md0 as sdb1 is being added to the RAID 1 set and " -"is in the process of being resynchronized." -msgstr "" - -#: ../../operation/raid.rst:232 5c2b9eff875444b0baea20af431e36f8 -msgid "Use this command to display the formatting of a hard disk." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/quick-start.po b/docs/_locale/de_DE/LC_MESSAGES/quick-start.po deleted file mode 100644 index 8606648a..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/quick-start.po +++ /dev/null @@ -1,217 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 09:55+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../quick-start.rst:5 ced00d9a872b438da0aa9116ca3bab93 -msgid "Quick Start" -msgstr "" - -#: ../../quick-start.rst:7 f9b3f5183a764e54aa6a23b5cdb71fd0 -msgid "" -"This chapter will guide you on how to get up to speed quickly using your new" -" VyOS system. It will show you a very basic configuration example that will " -"provide a :ref:`nat` gateway for a device with two network interfaces " -"(`eth0` and `eth1`)." -msgstr "" - -#: ../../quick-start.rst:15 a76ddf433c70478fb82d1fb3fcb52291 -msgid "Configuration Mode" -msgstr "" - -#: ../../quick-start.rst:17 4c3f1e2bd78544f2a8c7879b4dbc571d -msgid "" -"By default, VyOS is in operational mode, and the command prompt displays a " -"`$`. To configure VyOS, you will need to enter configuration mode, resulting" -" in the command prompt displaying a `#`, as demonstrated below:" -msgstr "" - -#: ../../quick-start.rst:27 c12b4b9c378c4216bb8e397ca27774b3 -msgid "Commit and Save" -msgstr "" - -#: ../../quick-start.rst:29 b4ee10e25442436db2e3ee6b9be361a5 -msgid "" -"After every configuration change, you need to apply the changes by using the" -" following command:" -msgstr "" - -#: ../../quick-start.rst:36 15efdc20e85b48f296f9c6e858eea689 -msgid "" -"Once your configuration works as expected, you can save it permanently by " -"using the following command:" -msgstr "" - -#: ../../quick-start.rst:44 39928bbb75374cb79e531615c78f11c2 -msgid "Interface Configuration" -msgstr "" - -#: ../../quick-start.rst:46 ed056fe464804060be1a439b88151cad -msgid "" -"Your outside/WAN interface will be `eth0`. It will receive its interface " -"address via DHCP." -msgstr "" - -#: ../../quick-start.rst:48 4912e3774ad74a39a9912c81aef012ce -msgid "" -"Your internal/LAN interface will be `eth1`. It will use a static IP address " -"of `192.168.0.1/24`." -msgstr "" - -#: ../../quick-start.rst:51 bf418104e3e245e2aa26f2d8792a9a3c -msgid "" -"After switching to :ref:`quick-start-configuration-mode` issue the following" -" commands:" -msgstr "" - -#: ../../quick-start.rst:63 38d4e3ae9ce748549f0a71b28407fea6 -msgid "SSH Management" -msgstr "" - -#: ../../quick-start.rst:65 efed8f184bf244f7aada5f2d47779efb -msgid "" -"After switching to :ref:`quick-start-configuration-mode` issue the following" -" commands, and your system will listen on every interface for incoming SSH " -"connections. You might want to check the :ref:`ssh` chapter on how to listen" -" on specific addresses only." -msgstr "" - -#: ../../quick-start.rst:78 a20b06ab8f13490bb98456f73f14cab0 -msgid "DHCP/DNS quick-start" -msgstr "" - -#: ../../quick-start.rst:80 1e6e02525b214cb2b19687d28e15b6b0 -msgid "" -"The following settings will configure DHCP and DNS services on your " -"internal/LAN network, where VyOS will act as the default gateway and DNS " -"server." -msgstr "" - -#: ../../quick-start.rst:84 f410600b061a48fbada8e792e77be8c2 -msgid "The default gateway and DNS recursor address will be `192.168.0.1/24`" -msgstr "" - -#: ../../quick-start.rst:85 04d779b2f5ae480ab0c58a0cd2994372 -msgid "" -"The address range `192.168.0.2/24 - 192.168.0.8/24` will be reserved for " -"static assignments" -msgstr "" - -#: ../../quick-start.rst:87 61c75136d69e4208b2bcf1bcc160d371 -msgid "" -"DHCP clients will be assigned IP addresses within the range of `192.168.0.9 " -"- 192.168.0.254` and have a domain name of `internal-network`" -msgstr "" - -#: ../../quick-start.rst:89 4b2a897af025417183c14771bc8946ae -msgid "DHCP leases will hold for one day (86400 seconds)" -msgstr "" - -#: ../../quick-start.rst:90 a7e648d7e2ba43069d8718a5b384e3f7 -msgid "" -"VyOS will serve as a full DNS recursor, replacing the need to utilize " -"Google, Cloudflare, or other public DNS servers (which is good for privacy)" -msgstr "" - -#: ../../quick-start.rst:92 1c1607b1156149308c15a9c6c8a73c89 -msgid "Only hosts from your internal/LAN network can use the DNS recursor" -msgstr "" - -#: ../../quick-start.rst:109 7ad183e1aa9648de9fc5bbc549ca8feb -msgid "NAT" -msgstr "" - -#: ../../quick-start.rst:111 c47487cfdb5144688488579cf9e6061c -msgid "" -"The following settings will configure :ref:`source-nat` rules for our " -"internal/LAN network, allowing hosts to communicate through the outside/WAN " -"network via IP masquerade." -msgstr "" - -#: ../../quick-start.rst:123 d2454d23a6284040a6b8a5b7f9b5934d -msgid "Firewall" -msgstr "" - -#: ../../quick-start.rst:125 336fdebef2d24d7dada566d09eb7c772 -msgid "Add a set of firewall policies for our outside/WAN interface." -msgstr "" - -#: ../../quick-start.rst:127 73685c38ed3945268a539ea3b9076e38 -msgid "" -"This configuration creates a proper stateful firewall that blocks all " -"traffic which was not initiated from the internal/LAN side first." -msgstr "" - -#: ../../quick-start.rst:146 8e4764bd3407430c8f051f75cda7e872 -msgid "" -"If you wanted to enable SSH access to your firewall from the outside/WAN " -"interface, you could create some additional rules to allow that kind of " -"traffic." -msgstr "" - -#: ../../quick-start.rst:150 b2afc0791183467a898c920cc331d78f -msgid "" -"These rules allow SSH traffic and rate limit it to 4 requests per minute. " -"This blocks brute-forcing attempts:" -msgstr "" - -#: ../../quick-start.rst:167 70f1d8a95a964d76be5bd76bacf32911 -msgid "Apply the firewall policies:" -msgstr "" - -#: ../../quick-start.rst:174 1c02685eca6d411c92b1d394e8756393 -msgid "Commit changes, save the configuration, and exit configuration mode:" -msgstr "" - -#: ../../quick-start.rst:187 da3fc1891b7f4857af9c8c9f4ecb9785 -msgid "Hardening" -msgstr "" - -#: ../../quick-start.rst:189 8c1a62935d9b450f80c0ccd856864e98 -msgid "" -"Especially if you are allowing SSH remote access from the outside/WAN " -"interface, there are a few additional configuration steps that should be " -"taken." -msgstr "" - -#: ../../quick-start.rst:192 5e1850cdacb8491ea56449c8108ee778 -msgid "Replace the default `vyos` system user:" -msgstr "" - -#: ../../quick-start.rst:198 b35e97b0ede1418ab6951bad98cc1290 -msgid "Set up :ref:`ssh_key_based_authentication`:" -msgstr "" - -#: ../../quick-start.rst:205 342f59779ee64e7a8e53d58613e247b0 -msgid "" -"Finally, try and SSH into the VyOS install as your new user. Once you have " -"confirmed that your new user can access your router without a password, " -"delete the original ``vyos`` user and completely disable password " -"authentication for :ref:`ssh`:" -msgstr "" - -#: ../../quick-start.rst:215 8fd010b7349542c2bed3e774281460c7 -msgid "" -"As above, commit your changes, save the configuration, and exit " -"configuration mode:" -msgstr "" - -#: ../../quick-start.rst:227 ae75935dcbfa40e0bc45bd0ce3169aca -msgid "" -"You now should have a simple yet secure and functioning router to experiment" -" with further. Enjoy!" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/troubleshooting/index.po b/docs/_locale/de_DE/LC_MESSAGES/troubleshooting/index.po deleted file mode 100644 index 97dd67ad..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/troubleshooting/index.po +++ /dev/null @@ -1,369 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../troubleshooting/index.rst:5 009f1b64fea942fcbe998c2556b798fe -msgid "Troubleshooting" -msgstr "" - -#: ../../troubleshooting/index.rst:7 301268c1f885420f842c4f45ea8aa9d4 -msgid "" -"Sometimes things break or don't work as expected. This section describes " -"several troubleshooting tools provided by VyOS that can help when something " -"goes wrong." -msgstr "" - -#: ../../troubleshooting/index.rst:13 5e79c49b4ba046ceabb2132a071aca55 -msgid "Connectivity Tests" -msgstr "" - -#: ../../troubleshooting/index.rst:16 265ce731ad1049a1b92d85f97b0b2d79 -msgid "Basic Connectivity Tests" -msgstr "" - -#: ../../troubleshooting/index.rst:18 f2632ae198bb42fb979bcbe39354142a -msgid "" -"Verifying connectivity can be done with the familiar `ping` and `traceroute`" -" commands. The options for each are shown (the options for each command were" -" displayed using the built-in help as described in the :ref:`cli` section " -"and are omitted from the output here):" -msgstr "" - -#: ../../troubleshooting/index.rst:25 07c4c0be68fd4988a949ebe7f69b64d7 -msgid "" -"Send ICMP echo requests to destination host. There are multiple options to " -"ping, inkl. VRF support." -msgstr "" - -#: ../../troubleshooting/index.rst:59 0a3335ee529c451f9b1320ac31fe6e43 -msgid "Trace path to target." -msgstr "" - -#: ../../troubleshooting/index.rst:73 6d499878bfc9434a8e00317671b1e572 -msgid "Advanced Connectivity Tests" -msgstr "" - -#: ../../troubleshooting/index.rst:77 4a305dd757b946caaeff45f6b3bcf36e -msgid "" -"However, another helper is available which combines ping and traceroute into" -" a single tool. An example of its output is shown:" -msgstr "" - -#: ../../troubleshooting/index.rst:94 3b25efcefdc84d19adbb91da390d6bf0 -msgid "The output consumes the screen and will replace your command prompt." -msgstr "" - -#: ../../troubleshooting/index.rst:97 71ec2df515c14dcab3292f560fd36cec -msgid "" -"Several options are available for changing the display output. Press `h` to " -"invoke the built in help system. To quit, just press `q` and you'll be " -"returned to the VyOS command prompt." -msgstr "" - -#: ../../troubleshooting/index.rst:102 dc2e0563a23c466cbdf07e635f59ce82 -msgid "IPv6 Topology Discovery" -msgstr "" - -#: ../../troubleshooting/index.rst:104 36f1358be2834603b9eacb83794db4d1 -msgid "IPv6 uses different techniques to discover its Neighbors/topology." -msgstr "" - -#: ../../troubleshooting/index.rst:107 73ade147654846c1bc3554efc069d0b4 -msgid "Router Discovery" -msgstr "" - -#: ../../troubleshooting/index.rst:111 74ce17c2dc2f400ebc1197d8abeaed62 -msgid "Discover routers via eth0." -msgstr "" - -#: ../../troubleshooting/index.rst:113 ../../troubleshooting/index.rst:150 -#: 5be816631722458fb079115b3c2a58c2 00fcbdbabb954b16983a2c7c2b87a534 -msgid "Example:" -msgstr "" - -#: ../../troubleshooting/index.rst:145 61a69428a5174d618b9f49278c19ed3d -msgid "Neighbor Discovery" -msgstr "" - -#: ../../troubleshooting/index.rst:162 7b66e897c07e41acb21c27e1ead7dcf5 -msgid "Interface names" -msgstr "" - -#: ../../troubleshooting/index.rst:164 489fcfbca0ac45e2b64ffb7a502f4e97 -msgid "" -"If you find the names of your interfaces have changed, this could be because" -" your MAC addresses have changed." -msgstr "" - -#: ../../troubleshooting/index.rst:167 6efbdc036dd0402b956bd34b5a44a171 -msgid "" -"For example, you have a VyOS VM with 4 Ethernet interfaces named eth0, eth1," -" eth2 and eth3. Then, you migrate your VyOS VM to a different host and find " -"your interfaces now are eth4, eth5, eth6 and eth7." -msgstr "" - -#: ../../troubleshooting/index.rst:171 edd57af5d3d14d8398ec8d474de61e7e -msgid "One way to fix this issue **taking control of the MAC addresses** is:" -msgstr "" - -#: ../../troubleshooting/index.rst:173 4f7ce3e3466d4dc9a46ee017e0e9ca80 -msgid "Log into VyOS and run this command to display your interface settings." -msgstr "" - -#: ../../troubleshooting/index.rst:179 3de6a592a2024334adf3f4682796fa4b -msgid "Take note of MAC addresses." -msgstr "" - -#: ../../troubleshooting/index.rst:181 d9e685c92bb34ebd858073cce95b3205 -msgid "" -"Now, in order to update a MAC address in the configuration, run this command" -" specifying the interface name and MAC address you want." -msgstr "" - -#: ../../troubleshooting/index.rst:188 94899b2cf6984b6ea923640b41b98dfe -msgid "" -"If it is a VM, go into the settings of the host and set the MAC address to " -"the settings found in the config.boot file. You can also set the MAC to " -"static if the host allows so." -msgstr "" - -#: ../../troubleshooting/index.rst:193 7981d5b3b70244d4803e08e0653eed58 -msgid "" -"Another example could be when cloning VyOS VMs in GNS3 and you get into the " -"same issue: interface names have changed." -msgstr "" - -#: ../../troubleshooting/index.rst:196 fd82fa04ceb54db68ef3e58a72c2a0a3 -msgid "" -"And **a more generic way to fix it** is just deleting every MAC address at " -"the configuration file of the cloned machine. They will be correctly " -"regenerated automatically." -msgstr "" - -#: ../../troubleshooting/index.rst:203 e57f77f173334a0a991d2e3051707dba -msgid "Monitoring" -msgstr "" - -#: ../../troubleshooting/index.rst:205 2a41326aa8534dfb8b46e81a66b251a9 -msgid "VyOS features several monitoring tools." -msgstr "" - -#: ../../troubleshooting/index.rst:240 4dc9b241667d4662817a7a22e2bce80d -msgid "Traffic Dumps" -msgstr "" - -#: ../../troubleshooting/index.rst:242 21b777a46b12442190f0496aa096827b -msgid "" -"To monitor interface traffic, issue the :code:`monitor traffic interface " -"<name>` command, replacing `<name>` with your chosen interface." -msgstr "" - -#: ../../troubleshooting/index.rst:260 173b94bd47dc44d1a49a1b6b8d622e65 -msgid "" -"To quit monitoring, press `Ctrl-c` and you'll be returned to the VyOS " -"command prompt." -msgstr "" - -#: ../../troubleshooting/index.rst:263 31df0aa6c14449aba81345d21639c667 -msgid "Traffic can be filtered and saved." -msgstr "" - -#: ../../troubleshooting/index.rst:275 d23710b7e89b4f1790795885b98388e7 -msgid "Interface Bandwidth Usage" -msgstr "" - -#: ../../troubleshooting/index.rst:277 9c1f4cb9ce694980861a08deb7ae0c5e -msgid "" -"to take a quick view on the used bandwidth of an interface use the ``monitor" -" bandwidth`` command" -msgstr "" - -#: ../../troubleshooting/index.rst:284 ad3a4c5001d54995a6aa3af4b911b583 -msgid "show the following:" -msgstr "" - -#: ../../troubleshooting/index.rst:307 802b9b02432440939e337548123a0d13 -msgid "Interface Performance" -msgstr "" - -#: ../../troubleshooting/index.rst:309 b7bdc5fe500244ff8d101c16c0e5b149 -msgid "" -"To take a look on the network bandwidth between two nodes, the ``monitor " -"bandwidth-test`` command is used to run iperf." -msgstr "" - -#: ../../troubleshooting/index.rst:319 b48e94bf695a464387e9799ddd26aee3 -msgid "The ``accept`` command opens a listening iperf server on TCP Port 5001" -msgstr "" - -#: ../../troubleshooting/index.rst:320 c85dc229d7a84f079236bd09e36dd266 -msgid "The ``initiate`` command connects to that server to perform the test." -msgstr "" - -#: ../../troubleshooting/index.rst:332 430e5b3ce91f48f9ab04094950466518 -msgid "Monitor command" -msgstr "" - -#: ../../troubleshooting/index.rst:334 a2e44f03a6b54c82b7779e14d408c8b5 -msgid "" -"The ``monitor command`` command allows you to repeatedly run a command to " -"view a continuously refreshed output. The command is run and output every 2 " -"seconds, allowing you to monitor the output continuously without having to " -"re-run the command. This can be useful to follow routing adjacency " -"formation." -msgstr "" - -#: ../../troubleshooting/index.rst:343 d261d2eddc664c39a23c144984d7cd0f -msgid "" -"Will clear the screen and show you the output of ``show interfaces`` every 2" -" seconds." -msgstr "" - -#: ../../troubleshooting/index.rst:362 97f75e31334f4930be94a5034d4cd25a -msgid "Terminal/Console" -msgstr "" - -#: ../../troubleshooting/index.rst:364 6ebb8b8f70744e04840f30e51480afe9 -msgid "" -"Sometimes you need to clear counters or statistics to troubleshoot better." -msgstr "" - -#: ../../troubleshooting/index.rst:366 9aab1a0fa62f443fa5abcea1c9a9539c -msgid "To do this use the ``clear`` command in Operational mode." -msgstr "" - -#: ../../troubleshooting/index.rst:368 87cde020b6af483cb4e059e13c39f6a9 -msgid "to clear the console output" -msgstr "" - -#: ../../troubleshooting/index.rst:374 3bd5dadaf7214cb78a05156175adf720 -msgid "to clear interface counters" -msgstr "" - -#: ../../troubleshooting/index.rst:383 b64254e5d1ed4fb2b2d108ed7a10db10 -msgid "" -"The command follow the same logic as the ``set`` command in configuration " -"mode." -msgstr "" - -#: ../../troubleshooting/index.rst:393 51d01df053254f84bd4bae74b4c382be -msgid "to clear counters on firewall rulesets or single rules" -msgstr "" - -#: ../../troubleshooting/index.rst:406 9f26016fd2884b8dae75b4858983d0d4 -msgid "System Information" -msgstr "" - -#: ../../troubleshooting/index.rst:411 66013e15f8b54f3e956f18aaf51d6de8 -msgid "Boot Steps" -msgstr "" - -#: ../../troubleshooting/index.rst:413 2a32598ebc1f45a4a5ee8f28aad8d94d -msgid "" -"VyOS 1.2 uses `Debian Jessie`_ as the base Linux operating system. Jessie " -"was the first version of Debian that uses systemd_ as the default init " -"system." -msgstr "" - -#: ../../troubleshooting/index.rst:416 aa2967797c2042839f50d3674ca9df6e -msgid "These are the boot steps for VyOS 1.2" -msgstr "" - -#: ../../troubleshooting/index.rst:418 d53a55b133cf483398b2cd6950710289 -msgid "The BIOS loads Grub (or isolinux for the Live CD)" -msgstr "" - -#: ../../troubleshooting/index.rst:419 b3385526393e4413b0ffddab88e03cd6 -msgid "" -"Grub then starts the Linux boot and loads the Linux Kernel ``/boot/vmlinuz``" -msgstr "" - -#: ../../troubleshooting/index.rst:420 585e7188ed7046658de5457b427298e7 -msgid "Kernel Launches Systemd ``/lib/systemd/systemd``" -msgstr "" - -#: ../../troubleshooting/index.rst:421 18b2fae859644184a3454537513220a6 -msgid "" -"Systemd loads the VyOS service file ``/lib/systemd/system/vyos-" -"router.service``" -msgstr "" - -#: ../../troubleshooting/index.rst:423 34efee49606143faa2f37e223d9761cb -msgid "" -"The service file launches the VyOS router init script " -"``/usr/libexec/vyos/init/vyos-router`` - this is part of the vyatta-cfg_ " -"Debian package" -msgstr "" - -#: ../../troubleshooting/index.rst:427 a0d5f5ab96cc4f85b75eb21819aaa9c0 -msgid "Starts FRR_ - successor to `GNU Zebra`_ and Quagga_" -msgstr "" - -#: ../../troubleshooting/index.rst:429 5e555f91b5194f15a56ad5aea86f60c1 -msgid "" -"Initialises the boot configuration file - copies over " -"``config.boot.default`` if there is no configuration" -msgstr "" - -#: ../../troubleshooting/index.rst:431 93073656864548248b50cf14d4bcad14 -msgid "" -"Runs the configuration migration, if the configuration is for an older " -"version of VyOS" -msgstr "" - -#: ../../troubleshooting/index.rst:433 ad9c85f7527a43ba87f5b64d7aad751a -msgid "" -"Runs The pre-config script, if there is one ``/config/scripts/vyos-" -"preconfig-bootup.script``" -msgstr "" - -#: ../../troubleshooting/index.rst:435 41f768ea433f41d195479ffaa1b781e3 -msgid "" -"If the config file was upgraded, runs any post upgrade scripts " -"``/config/scripts/post-upgrade.d``" -msgstr "" - -#: ../../troubleshooting/index.rst:437 45ec9a80856e4fcf84fd47f643663df5 -msgid "Starts ``rl-system`` and ``firewall``" -msgstr "" - -#: ../../troubleshooting/index.rst:438 e0add66c0c014f25843c689f9d905dc8 -msgid "Mounts the ``/boot`` partition" -msgstr "" - -#: ../../troubleshooting/index.rst:439 f386595b797d46d497fb168bcd392e15 -msgid "" -"The boot configuration file is then applied by ``/opt/vyatta/sbin/ vyatta-" -"boot-config-loader/opt/vyatta/etc/config/config.boot``" -msgstr "" - -#: ../../troubleshooting/index.rst:442 9a70df9d21f54e0586646599701fe84e -msgid "" -"The config loader script writes log entries to ``/var/log/vyatta-config-" -"loader.log``" -msgstr "" - -#: ../../troubleshooting/index.rst:445 e2a837520b684875abd5689801d7e47b -msgid "Runs ``telinit q`` to tell the init system to reload ``/etc/inittab``" -msgstr "" - -#: ../../troubleshooting/index.rst:446 cc2fdc6ad4ee4757a712865a6a691390 -msgid "" -"Finally it runs the post-config script ``/config/scripts/vyos-postconfig-" -"bootup.script``" -msgstr "" |