diff options
Diffstat (limited to 'docs/_locale/ja')
28 files changed, 30215 insertions, 0 deletions
diff --git a/docs/_locale/ja/404.pot b/docs/_locale/ja/404.pot new file mode 100644 index 00000000..3284d833 --- /dev/null +++ b/docs/_locale/ja/404.pot @@ -0,0 +1,29 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../404.rst:4 +msgid "Page Not Found" +msgstr "Page Not Found" + +#: ../../404.rst:6 +msgid "Sorry, We could not find a page. Try using the search box or go to the release homepage:" +msgstr "Sorry, We could not find a page. Try using the search box or go to the release homepage:" + +#: ../../404.rst:9 +msgid "`1.2.x (crux) <https://docs.vyos.io/en/crux/>`_" +msgstr "`1.2.x (crux) <https://docs.vyos.io/en/crux/>`_" + +#: ../../404.rst:10 +msgid "`1.3.x (equuleus) <https://docs.vyos.io/en/equuleus/>`_" +msgstr "`1.3.x (equuleus) <https://docs.vyos.io/en/equuleus/>`_" + +#: ../../404.rst:11 +msgid "`rolling release (sagitta) <https://docs.vyos.io/en/latest/>`_" +msgstr "`rolling release (sagitta) <https://docs.vyos.io/en/latest/>`_" diff --git a/docs/_locale/ja/LC_MESSAGES/404.mo b/docs/_locale/ja/LC_MESSAGES/404.mo Binary files differnew file mode 100644 index 00000000..9d4f5a00 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/404.mo diff --git a/docs/_locale/ja/LC_MESSAGES/automation.mo b/docs/_locale/ja/LC_MESSAGES/automation.mo Binary files differnew file mode 100644 index 00000000..58268446 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/automation.mo diff --git a/docs/_locale/ja/LC_MESSAGES/cli.mo b/docs/_locale/ja/LC_MESSAGES/cli.mo Binary files differnew file mode 100644 index 00000000..e7c0bd13 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/cli.mo diff --git a/docs/_locale/ja/LC_MESSAGES/configexamples.mo b/docs/_locale/ja/LC_MESSAGES/configexamples.mo Binary files differnew file mode 100644 index 00000000..cfe1f8d7 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/configexamples.mo diff --git a/docs/_locale/ja/LC_MESSAGES/configuration.mo b/docs/_locale/ja/LC_MESSAGES/configuration.mo Binary files differnew file mode 100644 index 00000000..3dfcc76c --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/configuration.mo diff --git a/docs/_locale/ja/LC_MESSAGES/contributing.mo b/docs/_locale/ja/LC_MESSAGES/contributing.mo Binary files differnew file mode 100644 index 00000000..1c6a7c73 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/contributing.mo diff --git a/docs/_locale/ja/LC_MESSAGES/copyright.mo b/docs/_locale/ja/LC_MESSAGES/copyright.mo Binary files differnew file mode 100644 index 00000000..fe27b843 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/copyright.mo diff --git a/docs/_locale/ja/LC_MESSAGES/documentation.mo b/docs/_locale/ja/LC_MESSAGES/documentation.mo Binary files differnew file mode 100644 index 00000000..9de91eff --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/documentation.mo diff --git a/docs/_locale/ja/LC_MESSAGES/index.mo b/docs/_locale/ja/LC_MESSAGES/index.mo Binary files differnew file mode 100644 index 00000000..d8d8f7c9 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/index.mo diff --git a/docs/_locale/ja/LC_MESSAGES/installation.mo b/docs/_locale/ja/LC_MESSAGES/installation.mo Binary files differnew file mode 100644 index 00000000..f8904cde --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/installation.mo diff --git a/docs/_locale/ja/LC_MESSAGES/introducing.mo b/docs/_locale/ja/LC_MESSAGES/introducing.mo Binary files differnew file mode 100644 index 00000000..6855be96 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/introducing.mo diff --git a/docs/_locale/ja/LC_MESSAGES/operation.mo b/docs/_locale/ja/LC_MESSAGES/operation.mo Binary files differnew file mode 100644 index 00000000..20592119 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/operation.mo diff --git a/docs/_locale/ja/LC_MESSAGES/quick-start.mo b/docs/_locale/ja/LC_MESSAGES/quick-start.mo Binary files differnew file mode 100644 index 00000000..badfd0af --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/quick-start.mo diff --git a/docs/_locale/ja/LC_MESSAGES/troubleshooting.mo b/docs/_locale/ja/LC_MESSAGES/troubleshooting.mo Binary files differnew file mode 100644 index 00000000..238635e7 --- /dev/null +++ b/docs/_locale/ja/LC_MESSAGES/troubleshooting.mo diff --git a/docs/_locale/ja/automation.pot b/docs/_locale/ja/automation.pot new file mode 100644 index 00000000..7bea74ac --- /dev/null +++ b/docs/_locale/ja/automation.pot @@ -0,0 +1,817 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../automation/cloud-init.rst:363 +msgid "**NOTE**: be carefull while copying and pasting previous commands. Doble quotes may need to be corrected." +msgstr "**NOTE**: be carefull while copying and pasting previous commands. Doble quotes may need to be corrected." + +#: ../../automation/cloud-init.rst:305 +msgid "**meta-data**: empty file (required)." +msgstr "**meta-data**: empty file (required)." + +#: ../../automation/cloud-init.rst:300 +msgid "**network-config**: file that will indicate to avoid dhcp client on first interface." +msgstr "**network-config**: file that will indicate to avoid dhcp client on first interface." + +#: ../../automation/cloud-init.rst:333 +msgid "**network-config** file only has configuration that disables the automatic dhcp client on first interface." +msgstr "**network-config** file only has configuration that disables the automatic dhcp client on first interface." + +#: ../../automation/cloud-init.rst:303 +msgid "**user-data**: includes vyos-commands." +msgstr "**user-data**: includes vyos-commands." + +#: ../../automation/cloud-init.rst:314 +msgid "**user-data** file must start with ``#cloud-config`` and contains vyos-commands. For example:" +msgstr "**user-data** file must start with ``#cloud-config`` and contains vyos-commands. For example:" + +#: ../../automation/vyos-api.rst:285 +msgid "/config-file" +msgstr "/config-file" + +#: ../../automation/vyos-api.rst:228 +msgid "/configure" +msgstr "/configure" + +#: ../../automation/vyos-api.rst:209 +msgid "/generate" +msgstr "/generate" + +#: ../../automation/vyos-api.rst:147 +msgid "/image" +msgstr "/image" + +#: ../../automation/vyos-api.rst:129 +msgid "/reset" +msgstr "/reset" + +#: ../../automation/vyos-api.rst:44 +msgid "/retrieve" +msgstr "/retrieve" + +#: ../../automation/vyos-api.rst:185 +msgid "/show" +msgstr "/show" + +#: ../../automation/vyos-api.rst:41 +msgid "API Endpoints" +msgstr "API Endpoints" + +#: ../../automation/cloud-init.rst:270 +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 "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." + +#: ../../automation/cloud-init.rst:63 +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 "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." + +#: ../../automation/command-scripting.rst:159 +msgid "A simple example is shown below, where the ops command executed in the post-hook script is \"show interfaces\"." +msgstr "A simple example is shown below, where the ops command executed in the post-hook script is \"show interfaces\"." + +#: ../../automation/cloud-init.rst:82 +msgid "A single-quote symbol is not allowed inside command or value." +msgstr "A single-quote symbol is not allowed inside command or value." + +#: ../../automation/vyos-salt.rst:32 +msgid "Accept minion key" +msgstr "Accept minion key" + +#: ../../automation/vyos-api.rst:15 +msgid "All endpoints only listen on HTTP POST requests and the API KEY must set as ``key`` in the formdata." +msgstr "All endpoints only listen on HTTP POST requests and the API KEY must set as ``key`` in the formdata." + +#: ../../automation/cloud-init.rst:115 +msgid "All of these can be overridden using the configuration in user-data." +msgstr "All of these can be overridden using the configuration in user-data." + +#: ../../automation/cloud-init.rst:256 +msgid "Also, this lab considers:" +msgstr "Also, this lab considers:" + +#: ../../automation/vyos-ansible.rst:6 +msgid "Ansible" +msgstr "Ansible" + +#: ../../automation/command-scripting.rst:181 +#: ../../automation/command-scripting.rst:200 +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 "Any modifications were done to work around unfixed bugs and implement enhancements that are not complete in the VyOS system can be placed here." + +#: ../../automation/vyos-salt.rst:55 +msgid "At this step we can get some op-mode information from VyOS nodes:" +msgstr "At this step we can get some op-mode information from VyOS nodes:" + +#: ../../automation/vyos-api.rst:13 +msgid "Authentication" +msgstr "Authentication" + +#: ../../automation/cloud-init.rst:241 +msgid "Before starting, please refer to cloud-init `network-config-docs`_ in order to know how to import user and network configurations." +msgstr "Before starting, please refer to cloud-init `network-config-docs`_ in order to know how to import user and network configurations." + +#: ../../automation/vyos-api.rst:18 +msgid "Below see one example for curl and one for python. The rest of the documentation is reduced to curl." +msgstr "Below see one example for curl and one for python. The rest of the documentation is reduced to curl." + +#: ../../automation/vyos-salt.rst:20 +msgid "Check salt-keys on the salt master" +msgstr "Check salt-keys on the salt master" + +#: ../../automation/vyos-salt.rst:161 +msgid "Check that proxy minion is alive:" +msgstr "Check that proxy minion is alive:" + +#: ../../automation/vyos-salt.rst:45 +msgid "Check that salt master can communicate with minions" +msgstr "Check that salt master can communicate with minions" + +#: ../../automation/cloud-init.rst:47 +msgid "Cloud-config modules" +msgstr "Cloud-config modules" + +#: ../../automation/cloud-init.rst:420 +msgid "Cloud-init `network-config-docs`_." +msgstr "Cloud-init `network-config-docs`_." + +#: ../../automation/cloud-init.rst:239 +msgid "Cloud-init on Proxmox" +msgstr "Cloud-init on Proxmox" + +#: ../../automation/cloud-init.rst:9 +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 "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." + +#: ../../automation/cloud-init.rst:120 +msgid "Command Execution at Initial Boot" +msgstr "Command Execution at Initial Boot" + +#: ../../automation/command-scripting.rst:6 +msgid "Command Scripting" +msgstr "Command Scripting" + +#: ../../automation/cloud-init.rst:356 +msgid "Command for generating ``seed.iso``" +msgstr "Command for generating ``seed.iso``" + +#: ../../automation/cloud-init.rst:78 +msgid "Commands requirements:" +msgstr "Commands requirements:" + +#: ../../automation/cloud-init.rst:16 +msgid "Config Sources" +msgstr "Config Sources" + +#: ../../automation/vyos-napalm.rst:85 +#: ../../automation/vyos-salt.rst:104 +msgid "Configuration" +msgstr "Configuration" + +#: ../../automation/command-scripting.rst:23 +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 "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:" + +#: ../../automation/vyos-napalm.rst:89 +msgid "Content of commands.conf" +msgstr "Content of commands.conf" + +#: ../../automation/cloud-init.rst:337 +msgid "Content of network-config file:" +msgstr "Content of network-config file:" + +#: ../../automation/cloud-init.rst:351 +msgid "Create seed.iso" +msgstr "Create seed.iso" + +#: ../../automation/cloud-init.rst:189 +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 "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." + +#: ../../automation/cloud-init.rst:368 +msgid "Creating the VM" +msgstr "Creating the VM" + +#: ../../automation/command-scripting.rst:156 +msgid "Custom scripts are not executed with root privileges (Use sudo inside if this is necessary)." +msgstr "Custom scripts are not executed with root privileges (Use sudo inside if this is necessary)." + +#: ../../automation/cloud-init.rst:113 +msgid "DHCP on first Ethernet interface if no network configuration is provided." +msgstr "DHCP on first Ethernet interface if no network configuration is provided." + +#: ../../automation/vyos-netmiko.rst:12 +msgid "Example" +msgstr "Example" + +#: ../../automation/vyos-salt.rst:185 +msgid "Example of configuration:" +msgstr "Example of configuration:" + +#: ../../automation/vyos-salt.rst:199 +msgid "Example of configuration commands from the file \"/srv/salt/states/commands.txt\"" +msgstr "Example of configuration commands from the file \"/srv/salt/states/commands.txt\"" + +#: ../../automation/vyos-salt.rst:173 +msgid "Example of op-mode:" +msgstr "Example of op-mode:" + +#: ../../automation/vyos-salt.rst:171 +msgid "Examples" +msgstr "Examples" + +#: ../../automation/command-scripting.rst:102 +msgid "Executing Configuration Scripts" +msgstr "Executing Configuration Scripts" + +#: ../../automation/command-scripting.rst:138 +msgid "Executing pre-hooks/post-hooks Scripts" +msgstr "Executing pre-hooks/post-hooks Scripts" + +#: ../../automation/vyos-ansible.rst:24 +msgid "File contents" +msgstr "File contents" + +#: ../../automation/cloud-init.rst:284 +msgid "File generated with previous command: ``/tmp/vyos-1.3.0-cloud-init-10G-qemu.qcow2``" +msgstr "File generated with previous command: ``/tmp/vyos-1.3.0-cloud-init-10G-qemu.qcow2``" + +#: ../../automation/cloud-init.rst:347 +msgid "Finaly, file **meta-data** has no content, but it's required." +msgstr "Finaly, file **meta-data** has no content, but it's required." + +#: ../../automation/command-scripting.rst:212 +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 "For configuration/upgrade management issues, modification of this script should be the last option. Always try to find solutions based on CLI commands first." + +#: ../../automation/vyos-api.rst:9 +msgid "For configuration and enabling the API see :ref:`http-api`" +msgstr "For configuration and enabling the API see :ref:`http-api`" + +#: ../../automation/vyos-api.rst:109 +msgid "For example, get the addresses of a ``dum0`` interface." +msgstr "For example, get the addresses of a ``dum0`` interface." + +#: ../../automation/vyos-api.rst:189 +msgid "For example, show which images are installed." +msgstr "For example, show which images are installed." + +#: ../../automation/cloud-init.rst:217 +msgid "For more information on the NoCloud data source, visit its `page <https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html>`_ in the cloud-init documentation." +msgstr "For more information on the NoCloud data source, visit its `page <https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html>`_ in the cloud-init documentation." + +#: ../../automation/cloud-init.rst:411 +msgid "From cli or GUI, power on VM, and after it boots, verify configuration" +msgstr "From cli or GUI, power on VM, and after it boots, verify configuration" + +#: ../../automation/cloud-init.rst:268 +msgid "Generate qcow image" +msgstr "Generate qcow image" + +#: ../../automation/command-scripting.rst:82 +msgid "Here is a simple example:" +msgstr "Here is a simple example:" + +#: ../../automation/cloud-init.rst:91 +msgid "Here is an example cloud-config that appends configuration at the time of first boot." +msgstr "Here is an example cloud-config that appends configuration at the time of first boot." + +#: ../../automation/cloud-init.rst:377 +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 "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``." + +#: ../../automation/cloud-init.rst:81 +msgid "If command ends in a value, it must be inside single quotes." +msgstr "If command ends in a value, it must be inside single quotes." + +#: ../../automation/cloud-init.rst:250 +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 "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." + +#: ../../automation/cloud-init.rst:225 +msgid "If you encounter problems, verify that the cloud-config document contains valid YAML. Online resources such as https://www.yamllint.com/ provide a simple tool for validating YAML." +msgstr "If you encounter problems, verify that the cloud-config document contains valid YAML. Online resources such as https://www.yamllint.com/ provide a simple tool for validating YAML." + +#: ../../automation/cloud-init.rst:153 +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 "If you need to gather information from linux commands to configure VyOS, you can execute commands and then configure VyOS in the same script." + +#: ../../automation/command-scripting.rst:79 +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 "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." + +#: ../../automation/cloud-init.rst:298 +msgid "In Proxmox server three files are going to be used for this setup:" +msgstr "In Proxmox server three files are going to be used for this setup:" + +#: ../../automation/cloud-init.rst:49 +msgid "In VyOS, by default, enables only two modules:" +msgstr "In VyOS, by default, enables only two modules:" + +#: ../../automation/cloud-init.rst:307 +msgid "In this lab, all files are located in ``/tmp/``. So, before going on, lets move to that directory:" +msgstr "In this lab, all files are located in ``/tmp/``. So, before going on, lets move to that directory:" + +#: ../../automation/cloud-init.rst:274 +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 "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:" + +#: ../../automation/cloud-init.rst:71 +msgid "Initial Configuration" +msgstr "Initial Configuration" + +#: ../../automation/cloud-init.rst:180 +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 "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." + +#: ../../automation/vyos-napalm.rst:11 +msgid "Install ``napalm-vyos`` module" +msgstr "Install ``napalm-vyos`` module" + +#: ../../automation/vyos-salt.rst:98 +msgid "It is possible to configure VyOS via netmiko_ proxy module. It requires a minion with installed packet ``python3-netmiko`` module who has a connection to VyOS nodes. Salt-minion have to communicate with salt master" +msgstr "It is possible to configure VyOS via netmiko_ proxy module. It requires a minion with installed packet ``python3-netmiko`` module who has a connection to VyOS nodes. Salt-minion have to communicate with salt master" + +#: ../../automation/cloud-init.rst:36 +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 "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." + +#: ../../automation/cloud-init.rst:20 +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 "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``." + +#: ../../automation/cloud-init.rst:244 +msgid "Most important keys that needs to be considered:" +msgstr "Most important keys that needs to be considered:" + +#: ../../automation/vyos-napalm.rst:6 +msgid "Napalm" +msgstr "Napalm" + +#: ../../automation/vyos-netmiko.rst:6 +msgid "Netmiko" +msgstr "Netmiko" + +#: ../../automation/vyos-salt.rst:96 +msgid "Netmiko-proxy" +msgstr "Netmiko-proxy" + +#: ../../automation/cloud-init.rst:24 +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 "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." + +#: ../../automation/cloud-init.rst:248 +msgid "Networking configurations shouldn't be passed in user-data file." +msgstr "Networking configurations shouldn't be passed in user-data file." + +#: ../../automation/cloud-init.rst:178 +msgid "NoCloud" +msgstr "NoCloud" + +#: ../../automation/index.rst:6 +msgid "Nornir" +msgstr "Nornir" + +#: ../../automation/cloud-init.rst:131 +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 "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." + +#: ../../automation/cloud-init.rst:370 +msgid "Notes for this particular example, that may need to be modified in other setups:" +msgstr "Notes for this particular example, that may need to be modified in other setups:" + +#: ../../automation/cloud-init.rst:287 +msgid "Now, that file needs to be copied to proxmox server:" +msgstr "Now, that file needs to be copied to proxmox server:" + +#: ../../automation/command-scripting.rst:108 +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 "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:" + +#: ../../automation/cloud-init.rst:390 +msgid "On proxmox server:" +msgstr "On proxmox server:" + +#: ../../automation/cloud-init.rst:353 +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 "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." + +#: ../../automation/cloud-init.rst:80 +msgid "One command per line." +msgstr "One command per line." + +#: ../../automation/vyos-napalm.rst:21 +msgid "Op-mode" +msgstr "Op-mode" + +#: ../../automation/command-scripting.rst:77 +msgid "Other script languages" +msgstr "Other script languages" + +#: ../../automation/vyos-napalm.rst:129 +#: ../../automation/vyos-netmiko.rst:47 +msgid "Output" +msgstr "Output" + +#: ../../automation/vyos-napalm.rst:48 +msgid "Output op-mode" +msgstr "Output op-mode" + +#: ../../_include/need_improvement.txt:13 +msgid "Please take a look at the Contributing Guide for our :ref:`documentation`." +msgstr "Please take a look at the Contributing Guide for our :ref:`documentation`." + +#: ../../automation/command-scripting.rst:195 +msgid "Postconfig on boot" +msgstr "Postconfig on boot" + +#: ../../automation/cloud-init.rst:409 +msgid "Power on VM and verifications" +msgstr "Power on VM and verifications" + +#: ../../automation/command-scripting.rst:176 +msgid "Preconfig on boot" +msgstr "Preconfig on boot" + +#: ../../automation/cloud-init.rst:296 +msgid "Prepare cloud-init files" +msgstr "Prepare cloud-init files" + +#: ../../automation/cloud-init.rst:258 +msgid "Proxmox IP address: **192.168.0.253/24**" +msgstr "Proxmox IP address: **192.168.0.253/24**" + +#: ../../automation/cloud-init.rst:422 +msgid "Proxmox `Cloud-init-Support`_." +msgstr "Proxmox `Cloud-init-Support`_." + +#: ../../automation/cloud-init.rst:416 +msgid "References" +msgstr "References" + +#: ../../automation/cloud-init.rst:263 +msgid "Remove default dhcp client on first interface, and load other configuration during first boot, using cloud-init." +msgstr "Remove default dhcp client on first interface, and load other configuration during first boot, using cloud-init." + +#: ../../automation/vyos-ansible.rst:80 +msgid "Run ansible" +msgstr "Run ansible" + +#: ../../automation/command-scripting.rst:50 +msgid "Run commands remotely" +msgstr "Run commands remotely" + +#: ../../automation/command-scripting.rst:21 +msgid "Run configuration commands" +msgstr "Run configuration commands" + +#: ../../automation/command-scripting.rst:37 +msgid "Run operational commands" +msgstr "Run operational commands" + +#: ../../automation/cloud-init.rst:111 +msgid "SSH is configured on port 22." +msgstr "SSH is configured on port 22." + +#: ../../automation/vyos-salt.rst:8 +msgid "Salt" +msgstr "Salt" + +#: ../../automation/vyos-salt.rst:106 +msgid "Salt master configuration:" +msgstr "Salt master configuration:" + +#: ../../automation/vyos-api.rst:307 +msgid "Save a running configuration to a file." +msgstr "Save a running configuration to a file." + +#: ../../automation/vyos-api.rst:289 +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 "Save a running configuration to the startup configuration. When you don't specify the file when saving, it saves to ``/config/config.boot``." + +#: ../../automation/vyos-napalm.rst:99 +msgid "Script vyos-napalm.py" +msgstr "Script vyos-napalm.py" + +#: ../../automation/command-scripting.rst:152 +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 "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." + +#: ../../automation/command-scripting.rst:52 +msgid "Sometimes you simply wan't to execute a bunch of op-mode commands via SSH on a remote VyOS system." +msgstr "Sometimes you simply wan't to execute a bunch of op-mode commands via SSH on a remote VyOS system." + +#: ../../automation/cloud-init.rst:260 +msgid "Storaged used: volume local, which is mounted on directory **/var/lib/vz**, and contains all type of content, including snippets." +msgstr "Storaged used: volume local, which is mounted on directory **/var/lib/vz**, and contains all type of content, including snippets." + +#: ../../automation/vyos-salt.rst:119 +msgid "Structure of /srv/salt:" +msgstr "Structure of /srv/salt:" + +#: ../../automation/vyos-ansible.rst:11 +msgid "Structure of files" +msgstr "Structure of files" + +#: ../../automation/cloud-init.rst:107 +msgid "System Defaults/Fallbacks" +msgstr "System Defaults/Fallbacks" + +#: ../../automation/vyos-api.rst:264 +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 "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." + +#: ../../automation/command-scripting.rst:197 +msgid "The ``/config/scripts/vyos-postconfig-bootup.script`` script is called on boot after the VyOS configuration is fully applied." +msgstr "The ``/config/scripts/vyos-postconfig-bootup.script`` script is called on boot after the VyOS configuration is fully applied." + +#: ../../automation/command-scripting.rst:178 +msgid "The ``/config/scripts/vyos-preconfig-bootup.script`` script is called on boot before the VyOS configuration during boot process." +msgstr "The ``/config/scripts/vyos-preconfig-bootup.script`` script is called on boot before the VyOS configuration during boot process." + +#: ../../automation/vyos-api.rst:187 +msgid "The ``/show`` endpoint is to show everything in the operational mode." +msgstr "The ``/show`` endpoint is to show everything in the operational mode." + +#: ../../automation/vyos-api.rst:211 +msgid "The ``generate`` endpoint run a ``generate`` command." +msgstr "The ``generate`` endpoint run a ``generate`` command." + +#: ../../automation/vyos-api.rst:131 +msgid "The ``reset`` endpoint run a ``reset`` command." +msgstr "The ``reset`` endpoint run a ``reset`` command." + +#: ../../automation/cloud-init.rst:84 +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 "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." + +#: ../../automation/cloud-init.rst:88 +msgid "The configuration specified in the cloud-config document overwrites default configuration values and values configured via Metadata." +msgstr "The configuration specified in the cloud-config document overwrites default configuration values and values configured via Metadata." + +#: ../../automation/command-scripting.rst:142 +msgid "The default directories where your custom Scripts should be located are:" +msgstr "The default directories where your custom Scripts should be located are:" + +#: ../../automation/command-scripting.rst:184 +#: ../../automation/command-scripting.rst:203 +msgid "The default file looks like this:" +msgstr "The default file looks like this:" + +#: ../../automation/cloud-init.rst:42 +msgid "The easiest way to configure the system via user-data is the Cloud-config syntax described below." +msgstr "The easiest way to configure the system via user-data is the Cloud-config syntax described below." + +#: ../../automation/vyos-api.rst:287 +msgid "The endpoint ``/config-file`` is to save or load a configuration." +msgstr "The endpoint ``/config-file`` is to save or load a configuration." + +#: ../../automation/cloud-init.rst:156 +msgid "The following example sets the hostname based on the instance identifier obtained from the EC2 metadata service." +msgstr "The following example sets the hostname based on the instance identifier obtained from the EC2 metadata service." + +#: ../../automation/cloud-init.rst:136 +msgid "The following example shows how to execute commands after the initial configuration." +msgstr "The following example shows how to execute commands after the initial configuration." + +#: ../../automation/cloud-init.rst:74 +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 "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." + +#: ../../automation/cloud-init.rst:197 +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 "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." + +#: ../../automation/command-scripting.rst:104 +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 "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." + +#: ../../automation/cloud-init.rst:109 +msgid "These are the VyOS defaults and fallbacks." +msgstr "These are the VyOS defaults and fallbacks." + +#: ../../_include/need_improvement.txt:11 +msgid "This section needs improvements, examples and explanations." +msgstr "This section needs improvements, examples and explanations." + +#: ../../automation/command-scripting.rst:118 +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 "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." + +#: ../../automation/vyos-api.rst:323 +msgid "To Load a configuration file." +msgstr "To Load a configuration file." + +#: ../../automation/vyos-api.rst:149 +msgid "To add or delete an image, use the ``/image`` endpoint." +msgstr "To add or delete an image, use the ``/image`` endpoint." + +#: ../../automation/command-scripting.rst:121 +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 "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:" + +#: ../../automation/vyos-api.rst:48 +msgid "To get the whole configuration, pass an empty list to the ``path`` field" +msgstr "To get the whole configuration, pass an empty list to the ``path`` field" + +#: ../../automation/command-scripting.rst:11 +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 "To include VyOS specific functions and aliases you need to ``source /opt/vyatta/etc/functions/script-template`` files at the top of your script." + +#: ../../automation/command-scripting.rst:128 +msgid "To make sure that a script is not accidentally called without the ``vyattacfg`` group, the script can be safeguarded like this:" +msgstr "To make sure that a script is not accidentally called without the ``vyattacfg`` group, the script can be safeguarded like this:" + +#: ../../automation/vyos-api.rst:79 +msgid "To only get a part of the configuration, for example ``system syslog``." +msgstr "To only get a part of the configuration, for example ``system syslog``." + +#: ../../automation/cloud-init.rst:223 +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#: ../../automation/command-scripting.rst:39 +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 "Unlike a normal configuration session, all operational commands must be prepended with ``run``, even if you haven't created a session with configure." + +#: ../../automation/cloud-init.rst:34 +msgid "User-data" +msgstr "User-data" + +#: ../../automation/cloud-init.rst:28 +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 "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." + +#: ../../automation/cloud-init.rst:373 +msgid "VM ID: in this example, VM ID used is 555." +msgstr "VM ID: in this example, VM ID used is 555." + +#: ../../automation/cloud-init.rst:381 +msgid "VM Resources: these parameters can be modified as needed." +msgstr "VM Resources: these parameters can be modified as needed." + +#: ../../automation/cloud-init.rst:375 +msgid "VM Storage: ``local`` volume is used." +msgstr "VM Storage: ``local`` volume is used." + +#: ../../automation/vyos-api.rst:7 +msgid "VyOS API" +msgstr "VyOS API" + +#: ../../automation/index.rst:3 +msgid "VyOS Automation" +msgstr "VyOS Automation" + +#: ../../automation/cloud-init.rst:418 +msgid "VyOS `cloud-init-docs`_." +msgstr "VyOS `cloud-init-docs`_." + +#: ../../automation/cloud-init.rst:7 +msgid "VyOS cloud-init" +msgstr "VyOS cloud-init" + +#: ../../automation/cloud-init.rst:246 +msgid "VyOS configuration commands are defined in user-data file." +msgstr "VyOS configuration commands are defined in user-data file." + +#: ../../automation/command-scripting.rst:140 +msgid "VyOS has the ability to run custom scripts before and after each commit" +msgstr "VyOS has the ability to run custom scripts before and after each commit" + +#: ../../automation/cloud-init.rst:18 +msgid "VyOS support three types of config sources." +msgstr "VyOS support three types of config sources." + +#: ../../automation/vyos-ansible.rst:8 +msgid "VyOS supports configuration via ansible. Need to install ``ansible`` and ``python3-paramiko`` module" +msgstr "VyOS supports configuration via ansible. Need to install ``ansible`` and ``python3-paramiko`` module" + +#: ../../automation/vyos-netmiko.rst:8 +msgid "VyOS supports configuration via netmiko_. It requires to install ``python3-netmiko`` module." +msgstr "VyOS supports configuration via netmiko_. It requires to install ``python3-netmiko`` module." + +#: ../../automation/command-scripting.rst:8 +msgid "VyOS supports executing configuration and operational commands non-interactively from shell scripts." +msgstr "VyOS supports executing configuration and operational commands non-interactively from shell scripts." + +#: ../../automation/vyos-salt.rst:10 +msgid "VyOS supports op-mode and configuration via salt_." +msgstr "VyOS supports op-mode and configuration via salt_." + +#: ../../automation/vyos-napalm.rst:8 +msgid "VyOS supports some napalm_ functions for configuration and op-mode. It requires more tests." +msgstr "VyOS supports some napalm_ functions for configuration and op-mode. It requires more tests." + +#: ../../automation/cloud-init.rst:122 +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 "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." + +#: ../../automation/vyos-napalm.rst:87 +msgid "We need 2 files, commands.conf and script itself." +msgstr "We need 2 files, commands.conf and script itself." + +#: ../../automation/cloud-init.rst:184 +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 "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\"." + +#: ../../automation/command-scripting.rst:63 +msgid "Will return:" +msgstr "Will return:" + +#: ../../automation/vyos-api.rst:46 +msgid "With the ``retrieve`` endpoint you get parts or the whole configuration." +msgstr "With the ``retrieve`` endpoint you get parts or the whole configuration." + +#: ../../automation/vyos-salt.rst:12 +msgid "Without proxy it requires VyOS minion configuration and support op-mode data:" +msgstr "Without proxy it requires VyOS minion configuration and support op-mode data:" + +#: ../../automation/vyos-salt.rst:12 +msgid "Without proxy it requires VyOS minion configuration and supports op-mode data:" +msgstr "Without proxy it requires VyOS minion configuration and supports op-mode data:" + +#: ../../automation/vyos-api.rst:230 +msgid "You can pass a ``set``, ``delete`` or ``comment`` command to the ``/configure`` endpoint." +msgstr "You can pass a ``set``, ``delete`` or ``comment`` command to the ``/configure`` endpoint." + +#: ../../automation/vyos-api.rst:249 +msgid "``delete`` a single command" +msgstr "``delete`` a single command" + +#: ../../automation/cloud-init.rst:383 +msgid "``seed.iso`` was previously created in directory ``/tmp/``. It's necessary to move it to ``/var/lib/vz/template/iso``" +msgstr "``seed.iso`` was previously created in directory ``/tmp/``. It's necessary to move it to ``/var/lib/vz/template/iso``" + +#: ../../automation/vyos-api.rst:233 +msgid "``set`` a single command" +msgstr "``set`` a single command" + +#: ../../automation/cloud-init.rst:55 +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 "``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." + +#: ../../automation/cloud-init.rst:112 +msgid "``vyos``/``vyos`` credentials if no others specified by data source." +msgstr "``vyos``/``vyos`` credentials if no others specified by data source." + +#: ../../automation/cloud-init.rst:51 +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 "``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`_." + +#: ../../automation/vyos-api.rst:151 +msgid "add an image" +msgstr "add an image" + +#: ../../automation/vyos-ansible.rst:26 +msgid "ansible.cfg" +msgstr "ansible.cfg" + +#: ../../automation/cloud-init.rst:61 +msgid "cloud-config file format" +msgstr "cloud-config file format" + +#: ../../automation/cloud-init.rst:229 +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 "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:" + +#: ../../automation/vyos-salt.rst:153 +msgid "commands.txt" +msgstr "commands.txt" + +#: ../../automation/vyos-api.rst:168 +msgid "delete an image, for example ``1.3-rolling-202006070117``" +msgstr "delete an image, for example ``1.3-rolling-202006070117``" + +#: ../../automation/vyos-ansible.rst:42 +msgid "hosts" +msgstr "hosts" + +#: ../../automation/vyos-ansible.rst:35 +msgid "id_rsa_docker.pub. Needs to declare only public key exactly." +msgstr "id_rsa_docker.pub. Needs to declare only public key exactly." + +#: ../../automation/vyos-api.rst:106 +msgid "if you just want the Value of a multi-valued node, use the ``returnValues`` operation." +msgstr "if you just want the Value of a multi-valued node, use the ``returnValues`` operation." + +#: ../../automation/vyos-ansible.rst:56 +msgid "main.yml" +msgstr "main.yml" + +#: ../../automation/vyos-salt.rst:141 +msgid "r11-proxy.sls Includes parameters for connecting to salt-proxy minion" +msgstr "r11-proxy.sls Includes parameters for connecting to salt-proxy minion" + +#: ../../automation/index.rst:7 +msgid "startup scripts" +msgstr "startup scripts" + +#: ../../automation/vyos-salt.rst:131 +msgid "top.sls" +msgstr "top.sls" diff --git a/docs/_locale/ja/cli.pot b/docs/_locale/ja/cli.pot new file mode 100644 index 00000000..c5981e8e --- /dev/null +++ b/docs/_locale/ja/cli.pot @@ -0,0 +1,437 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../cli.rst:115 +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 "**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." + +#: ../../cli.rst:382 +msgid "**Example:**" +msgstr "**Example:**" + +#: ../../cli.rst:126 +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 "**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``." + +#: ../../cli.rst:120 +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 "**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." + +#: ../../cli.rst:113 +msgid "A VyOS system has three major types of configurations:" +msgstr "A VyOS system has three major types of configurations:" + +#: ../../cli.rst:576 +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 "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." + +#: ../../cli.rst:690 +msgid "Access opmode from config mode" +msgstr "Access opmode from config mode" + +#: ../../cli.rst:697 +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 "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." + +#: ../../cli.rst:651 +msgid "Add comment as an annotation to a configuration node." +msgstr "Add comment as an annotation to a configuration node." + +#: ../../cli.rst:539 +msgid "All changes in the working config will thus be lost." +msgstr "All changes in the working config will thus be lost." + +#: ../../cli.rst:355 +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 "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." + +#: ../../cli.rst:676 +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 "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." + +#: ../../cli.rst:493 +msgid "Any change you do on the configuration, will not take effect until committed using the :cfgcmd:`commit` command in configuration mode." +msgstr "Any change you do on the configuration, will not take effect until committed using the :cfgcmd:`commit` command in configuration mode." + +#: ../../cli.rst:221 +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 "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`." + +#: ../../cli.rst:193 +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 "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." + +#: ../../cli.rst:5 +msgid "Command Line Interface" +msgstr "Command Line Interface" + +#: ../../cli.rst:701 +msgid "Command completion and syntax help with ``?`` and ``[tab]`` will also work." +msgstr "Command completion and syntax help with ``?`` and ``[tab]`` will also work." + +#: ../../cli.rst:754 +msgid "Compare configurations" +msgstr "Compare configurations" + +#: ../../cli.rst:75 +msgid "Configuration Mode" +msgstr "Configuration Mode" + +#: ../../cli.rst:102 +msgid "Configuration Overview" +msgstr "Configuration Overview" + +#: ../../cli.rst:457 +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 "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." + +#: ../../cli.rst:535 +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 "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." + +#: ../../cli.rst:583 +msgid "Copy a configuration element." +msgstr "Copy a configuration element." + +#: ../../cli.rst:447 +msgid "Editing the configuration" +msgstr "Editing the configuration" + +#: ../../cli.rst:662 +msgid "Example:" +msgstr "Example:" + +#: ../../cli.rst:30 +msgid "Example showing possible show commands:" +msgstr "Example showing possible show commands:" + +#: ../../cli.rst:433 +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 "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." + +#: ../../cli.rst:21 +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 "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." + +#: ../../cli.rst:201 +msgid "Get a collection of all the set commands required which led to the running configuration." +msgstr "Get a collection of all the set commands required which led to the running configuration." + +#: ../../cli.rst:930 +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 "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." + +#: ../../cli.rst:916 +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 "In the case you want to completely delete your configuration and restore the default one, you can enter the following command in configuration mode:" + +#: ../../cli.rst:413 +msgid "It is also possible to display all `set` commands within configuration mode using :cfgcmd:`show | commands`" +msgstr "It is also possible to display all `set` commands within configuration mode using :cfgcmd:`show | commands`" + +#: ../../cli.rst:723 +msgid "Local Archive" +msgstr "Local Archive" + +#: ../../cli.rst:714 +msgid "Managing configurations" +msgstr "Managing configurations" + +#: ../../cli.rst:627 +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 "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." + +#: ../../cli.rst:11 +msgid "Operational Mode" +msgstr "Operational Mode" + +#: ../../cli.rst:13 +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 "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." + +#: ../../cli.rst:85 +msgid "Prompt changes from ``$`` to ``#``. To exit configuration mode, type ``exit``." +msgstr "Prompt changes from ``$`` to ``#``. To exit configuration mode, type ``exit``." + +#: ../../cli.rst:850 +msgid "Remote Archive" +msgstr "Remote Archive" + +#: ../../cli.rst:616 +msgid "Rename a configuration element." +msgstr "Rename a configuration element." + +#: ../../cli.rst:914 +msgid "Restore Default" +msgstr "Restore Default" + +#: ../../cli.rst:725 +msgid "Revisions are stored on disk. You can view, compare and rollback them to any previous revisions if something goes wrong." +msgstr "Revisions are stored on disk. You can view, compare and rollback them to any previous revisions if something goes wrong." + +#: ../../cli.rst:828 +msgid "Rollback Changes" +msgstr "Rollback Changes" + +#: ../../cli.rst:835 +msgid "Rollback to revision N (currently requires reboot)" +msgstr "Rollback to revision N (currently requires reboot)" + +#: ../../cli.rst:881 +msgid "Saving and loading manually" +msgstr "Saving and loading manually" + +#: ../../cli.rst:94 +msgid "See the configuration section of this document for more information on configuration mode." +msgstr "See the configuration section of this document for more information on configuration mode." + +#: ../../cli.rst:133 +msgid "Seeing and navigating the configuration" +msgstr "Seeing and navigating the configuration" + +#: ../../cli.rst:810 +msgid "Show commit revision difference." +msgstr "Show commit revision difference." + +#: ../../cli.rst:861 +msgid "Specify remote location of commit archive as any of the below :abbr:`URI (Uniform Resource Identifier)`" +msgstr "Specify remote location of commit archive as any of the below :abbr:`URI (Uniform Resource Identifier)`" + +#: ../../cli.rst:111 +msgid "Terminology" +msgstr "Terminology" + +#: ../../cli.rst:17 +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 "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." + +#: ../../cli.rst:7 +msgid "The VyOS :abbr:`CLI (Command-Line Interface)` comprises an operational and a configuration mode." +msgstr "The VyOS :abbr:`CLI (Command-Line Interface)` comprises an operational and a configuration mode." + +#: ../../cli.rst:378 +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 "The :cfgcmd:`show` command within configuration mode will show the working configuration indicating line changes with ``+`` for additions, ``>`` for replacements and ``-`` for deletions." + +#: ../../cli.rst:653 +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 "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." + +#: ../../cli.rst:784 +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 "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." + +#: ../../cli.rst:813 +msgid "The command above also lets you see the difference between two commits. By default the difference with the running config is shown." +msgstr "The command above also lets you see the difference between two commits. By default the difference with the running config is shown." + +#: ../../cli.rst:338 +msgid "The config mode" +msgstr "The config mode" + +#: ../../cli.rst:449 +msgid "The configuration can be edited by the use of :cfgcmd:`set` and :cfgcmd:`delete` commands from within configuration mode." +msgstr "The configuration can be edited by the use of :cfgcmd:`set` and :cfgcmd:`delete` commands from within configuration mode." + +#: ../../cli.rst:359 +msgid "The current hierarchy level can be changed by the :cfgcmd:`edit` command." +msgstr "The current hierarchy level can be changed by the :cfgcmd:`edit` command." + +#: ../../cli.rst:869 +msgid "The number of revisions don't affect the commit-archive." +msgstr "The number of revisions don't affect the commit-archive." + +#: ../../cli.rst:927 +msgid "Then you may want to :cfgcmd:`save` in order to delete the saved configuration too." +msgstr "Then you may want to :cfgcmd:`save` in order to delete the saved configuration too." + +#: ../../cli.rst:422 +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 "These commands are also relative to the level you are inside and only relevant configuration blocks will be displayed when entering a sub-level." + +#: ../../cli.rst:475 +msgid "These two commands above are essentially the same, just executed from different levels in the hierarchy." +msgstr "These two commands above are essentially the same, just executed from different levels in the hierarchy." + +#: ../../cli.rst:824 +msgid "This means four commits ago we did ``set system ipv6 disable-forwarding``." +msgstr "This means four commits ago we did ``set system ipv6 disable-forwarding``." + +#: ../../cli.rst:480 +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 "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." + +#: ../../cli.rst:77 +msgid "To enter configuration mode use the ``configure`` command:" +msgstr "To enter configuration mode use the ``configure`` command:" + +#: ../../cli.rst:658 +msgid "To remove an existing comment from your current configuration, specify an empty string enclosed in double quote marks (``\"\"``) as the comment text." +msgstr "To remove an existing comment from your current configuration, specify an empty string enclosed in double quote marks (``\"\"``) as the comment text." + +#: ../../cli.rst:225 +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 "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`_." + +#: ../../cli.rst:892 +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 "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." + +#: ../../cli.rst:508 +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 "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." + +#: ../../cli.rst:454 +msgid "Use this command to set the value of a parameter or to create a new element." +msgstr "Use this command to set the value of a parameter or to create a new element." + +#: ../../cli.rst:760 +msgid "Use this command to spot what the differences are between different configurations." +msgstr "Use this command to spot what the differences are between different configurations." + +#: ../../cli.rst:552 +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 "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." + +#: ../../cli.rst:730 +msgid "View all existing revisions on the local system." +msgstr "View all existing revisions on the local system." + +#: ../../cli.rst:137 +msgid "View the current active configuration, also known as the running configuration, from the operational mode." +msgstr "View the current active configuration, also known as the running configuration, from the operational mode." + +#: ../../cli.rst:233 +msgid "View the current active configuration in JSON format." +msgstr "View the current active configuration in JSON format." + +#: ../../cli.rst:241 +msgid "View the current active configuration in readable JSON format." +msgstr "View the current active configuration in readable JSON format." + +#: ../../cli.rst:852 +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 "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``." + +#: ../../cli.rst:716 +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 "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." + +#: ../../cli.rst:756 +msgid "VyOS lets you compare different configurations." +msgstr "VyOS lets you compare different configurations." + +#: ../../cli.rst:104 +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 "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." + +#: ../../cli.rst:558 +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 "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." + +#: ../../cli.rst:340 +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 "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." + +#: ../../cli.rst:351 +msgid "When going into configuration mode, prompt changes from ``$`` to ``#``." +msgstr "When going into configuration mode, prompt changes from ``$`` to ``#``." + +#: ../../cli.rst:692 +msgid "When inside configuration mode you are not directly able to execute operational commands." +msgstr "When inside configuration mode you are not directly able to execute operational commands." + +#: ../../cli.rst:61 +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 "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." + +#: ../../cli.rst:886 +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 "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:" + +#: ../../cli.rst:72 +msgid "When viewing in page mode the following commands are available:" +msgstr "When viewing in page mode the following commands are available:" + +#: ../../cli.rst:370 +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 "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." + +#: ../../cli.rst:618 +msgid "You can also rename config subtrees:" +msgstr "You can also rename config subtrees:" + +#: ../../cli.rst:585 +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 "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." + +#: ../../cli.rst:830 +msgid "You can rollback configuration changes using the rollback command. This will apply the selected revision and trigger a system reboot." +msgstr "You can rollback configuration changes using the rollback command. This will apply the selected revision and trigger a system reboot." + +#: ../../cli.rst:58 +msgid "You can scroll up with the keys ``[Shift]+[PageUp]`` and scroll down with ``[Shift]+[PageDown]``." +msgstr "You can scroll up with the keys ``[Shift]+[PageUp]`` and scroll down with ``[Shift]+[PageDown]``." + +#: ../../cli.rst:747 +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 "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." + +#: ../../cli.rst:883 +msgid "You can use the ``save`` and ``load`` commands if you want to manually manage specific configuration files." +msgstr "You can use the ``save`` and ``load`` commands if you want to manually manage specific configuration files." + +#: ../../cli.rst:871 +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 "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:" + +#: ../../cli.rst:924 +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 "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." + +#: ../../cli.rst:67 +msgid "``b`` will scroll back one page" +msgstr "``b`` will scroll back one page" + +#: ../../cli.rst:866 +msgid "``ftp://<user>:<passwd>@<host>/<dir>``" +msgstr "``ftp://<user>:<passwd>@<host>/<dir>``" + +#: ../../cli.rst:71 +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 "``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." + +#: ../../cli.rst:65 +msgid "``q`` key can be used to cancel output" +msgstr "``q`` key can be used to cancel output" + +#: ../../cli.rst:68 +msgid "``return`` will scroll down one line" +msgstr "``return`` will scroll down one line" + +#: ../../cli.rst:864 +msgid "``scp://<user>:<passwd>@<host>:/<dir>``" +msgstr "``scp://<user>:<passwd>@<host>:/<dir>``" + +#: ../../cli.rst:865 +msgid "``sftp://<user>:<passwd>@<host>/<dir>``" +msgstr "``sftp://<user>:<passwd>@<host>/<dir>``" + +#: ../../cli.rst:66 +msgid "``space`` will scroll down one page" +msgstr "``space`` will scroll down one page" + +#: ../../cli.rst:867 +msgid "``tftp://<host>/<dir>``" +msgstr "``tftp://<host>/<dir>``" + +#: ../../cli.rst:69 +msgid "``up-arrow`` and ``down-arrow`` will scroll up or down one line at a time respectively" +msgstr "``up-arrow`` and ``down-arrow`` will scroll up or down one line at a time respectively" diff --git a/docs/_locale/ja/configexamples.pot b/docs/_locale/ja/configexamples.pot new file mode 100644 index 00000000..c1c956cc --- /dev/null +++ b/docs/_locale/ja/configexamples.pot @@ -0,0 +1,2773 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../configexamples/zone-policy.rst:162 +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 "''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.''" + +#: ../../configexamples/azure-vpn-bgp.rst:117 +msgid "**Important**: Add an interface route to reach Azure's BGP listener" +msgstr "**Important**: Add an interface route to reach Azure's BGP listener" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:134 +msgid "**Important**: Add an interface route to reach both Azure's BGP listeners" +msgstr "**Important**: Add an interface route to reach both Azure's BGP listeners" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:156 +msgid "**Important**: Disable connected check, otherwise the routes learned from Azure will not be imported into the routing table." +msgstr "**Important**: Disable connected check, otherwise the routes learned from Azure will not be imported into the routing table." + +#: ../../configexamples/azure-vpn-bgp.rst:133 +msgid "**Important**: Disable connected check \\" +msgstr "**Important**: Disable connected check \\" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:46 +msgid "**NOTE:** VyOS Router (tested with VyOS 1.4-rolling-202110310317) – The configurations below are specifically for VyOS 1.4.x." +msgstr "**NOTE:** VyOS Router (tested with VyOS 1.4-rolling-202110310317) – The configurations below are specifically for VyOS 1.4.x." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:1123 +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 "**Note:** At the moment, trace mpls doesn’t show labels/paths. So we’ll see * * * for the transit routers of the mpls backbone." + +#: ../../configexamples/zone-policy.rst:34 +msgid "**This specific example is for a router on a stick, but is very easily adapted for however many NICs you have**:" +msgstr "**This specific example is for a router on a stick, but is very easily adapted for however many NICs you have**:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:5 +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 "**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." + +#: ../../configexamples/ha.rst:389 +msgid "**offsite1**" +msgstr "**offsite1**" + +#: ../../configexamples/ha.rst:201 +#: ../../configexamples/ha.rst:237 +#: ../../configexamples/ha.rst:366 +#: ../../configexamples/ha.rst:540 +msgid "**router1**" +msgstr "**router1**" + +#: ../../configexamples/ha.rst:215 +#: ../../configexamples/ha.rst:250 +#: ../../configexamples/ha.rst:581 +msgid "**router2**" +msgstr "**router2**" + +#: ../../configexamples/ha.rst:70 +msgid "100: 'Public' network, using our 203.0.113.0/24 network." +msgstr "100: 'Public' network, using our 203.0.113.0/24 network." + +#: ../../configexamples/azure-vpn-bgp.rst:38 +#: ../../configexamples/azure-vpn-dual-bgp.rst:35 +msgid "10.0.0.0/16" +msgstr "10.0.0.0/16" + +#: ../../configexamples/azure-vpn-bgp.rst:46 +msgid "10.0.0.4" +msgstr "10.0.0.4" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:45 +msgid "10.0.0.4,10.0.0.5" +msgstr "10.0.0.4,10.0.0.5" + +#: ../../configexamples/azure-vpn-bgp.rst:36 +#: ../../configexamples/azure-vpn-dual-bgp.rst:33 +msgid "10.10.0.0/16" +msgstr "10.10.0.0/16" + +#: ../../configexamples/azure-vpn-bgp.rst:42 +#: ../../configexamples/azure-vpn-dual-bgp.rst:39 +msgid "10.10.0.5" +msgstr "10.10.0.5" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 +msgid "10.1.1.0/30" +msgstr "10.1.1.0/30" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 +msgid "10.2.2.0/30" +msgstr "10.2.2.0/30" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +msgid "10.50.50.1:1011" +msgstr "10.50.50.1:1011" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "10.60.60.1:1011" +msgstr "10.60.60.1:1011" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +msgid "10.80.80.1:1011" +msgstr "10.80.80.1:1011" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 +msgid "172.16.2.0/30" +msgstr "172.16.2.0/30" + +#: ../../configexamples/qos.rst:136 +msgid "172.17.1.2/24 CS0" +msgstr "172.17.1.2/24 CS0" + +#: ../../configexamples/qos.rst:143 +msgid "172.17.1.2/24 CS0 - > CS4" +msgstr "172.17.1.2/24 CS0 - > CS4" + +#: ../../configexamples/qos.rst:150 +msgid "172.17.1.2/24 CS4 - > CS5" +msgstr "172.17.1.2/24 CS4 - > CS5" + +#: ../../configexamples/qos.rst:26 +msgid "172.17.1.2 CS0 -> CS4" +msgstr "172.17.1.2 CS0 -> CS4" + +#: ../../configexamples/qos.rst:27 +msgid "172.17.1.3 CS0 -> CS5" +msgstr "172.17.1.3 CS0 -> CS5" + +#: ../../configexamples/qos.rst:29 +msgid "172.17.1.40 CS0 by default" +msgstr "172.17.1.40 CS0 by default" + +#: ../../configexamples/qos.rst:28 +msgid "172.17.1.4 CS0 -> CS6" +msgstr "172.17.1.4 CS0 -> CS6" + +#: ../../configexamples/zone-policy.rst:45 +msgid "192.168.100.10/2001:0DB8:0:AAAA::10 is the administrator's console. It can SSH to VyOS." +msgstr "192.168.100.10/2001:0DB8:0:AAAA::10 is the administrator's console. It can SSH to VyOS." + +#: ../../configexamples/zone-policy.rst:43 +msgid "192.168.200.200/2001:0DB8:0:BBBB::200 is an internal/external DNS, web and mail (SMTP/IMAP) server." +msgstr "192.168.200.200/2001:0DB8:0:BBBB::200 is an internal/external DNS, web and mail (SMTP/IMAP) server." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 +msgid "192.168.3.0/30" +msgstr "192.168.3.0/30" + +#: ../../configexamples/azure-vpn-bgp.rst:40 +#: ../../configexamples/azure-vpn-dual-bgp.rst:37 +msgid "198.51.100.3" +msgstr "198.51.100.3" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 +msgid "2001:db8::/127" +msgstr "2001:db8::/127" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 +msgid "2001:db8::2/127" +msgstr "2001:db8::2/127" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 +msgid "2001:db8::4/127" +msgstr "2001:db8::4/127" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 +msgid "2001:db8::6/127" +msgstr "2001:db8::6/127" + +#: ../../configexamples/ha.rst:71 +msgid "201: 'Internal' network, using 10.200.201.0/24" +msgstr "201: 'Internal' network, using 10.200.201.0/24" + +#: ../../configexamples/azure-vpn-bgp.rst:44 +#: ../../configexamples/azure-vpn-dual-bgp.rst:41 +msgid "203.0.113.2" +msgstr "203.0.113.2" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:43 +msgid "203.0.113.3" +msgstr "203.0.113.3" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:20 +msgid "2 private subnets on each site." +msgstr "2 private subnets on each site." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:35 +msgid "2 x Route reflectors (VyOS-RRx)" +msgstr "2 x Route reflectors (VyOS-RRx)" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:38 +msgid "3 x Customer Edge (VyOS-CEx)" +msgstr "3 x Customer Edge (VyOS-CEx)" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:37 +msgid "3 x Provider Edge (VyOs-PEx)" +msgstr "3 x Provider Edge (VyOs-PEx)" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:36 +msgid "4 x Provider routers (VyOS-Px)" +msgstr "4 x Provider routers (VyOS-Px)" + +#: ../../configexamples/ha.rst:69 +msgid "50: Upstream, using the 192.0.2.0/24 network allocated by them." +msgstr "50: Upstream, using the 192.0.2.0/24 network allocated by them." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 +msgid "64496:1" +msgstr "64496:1" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 +msgid "64496:100" +msgstr "64496:100" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 +msgid "64496:2" +msgstr "64496:2" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 +msgid "64496:50" +msgstr "64496:50" + +#: ../../configexamples/azure-vpn-bgp.rst:50 +#: ../../configexamples/azure-vpn-dual-bgp.rst:49 +msgid "64499" +msgstr "64499" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "65035:1011" +msgstr "65035:1011" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +msgid "65035:1011 65035:1030" +msgstr "65035:1011 65035:1030" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "65035:1030" +msgstr "65035:1030" + +#: ../../configexamples/azure-vpn-bgp.rst:52 +#: ../../configexamples/azure-vpn-dual-bgp.rst:51 +msgid "65540" +msgstr "65540" + +#: ../../configexamples/qos.rst:62 +msgid "ADDRESS10 change CS0 -> CS4 source 172.17.1.2/32" +msgstr "ADDRESS10 change CS0 -> CS4 source 172.17.1.2/32" + +#: ../../configexamples/qos.rst:63 +msgid "ADDRESS20 change CS0 -> CS5 source 172.17.1.3/32" +msgstr "ADDRESS20 change CS0 -> CS5 source 172.17.1.3/32" + +#: ../../configexamples/qos.rst:64 +msgid "ADDRESS30 change CS0 -> CS6 source 172.17.1.4/32" +msgstr "ADDRESS30 change CS0 -> CS6 source 172.17.1.4/32" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:28 +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 "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." + +#: ../../configexamples/azure-vpn-bgp.rst:26 +#: ../../configexamples/azure-vpn-dual-bgp.rst:23 +msgid "A connection resource deployed in Azure linking the Azure VNet gateway and the local network gateway representing the Vyos device." +msgstr "A connection resource deployed in Azure linking the Azure VNet gateway and the local network gateway representing the Vyos device." + +#: ../../configexamples/index.rst:35 +msgid "A host ``vyos-oobm`` will use as a ssh proxy. This host is just necessary for the Lab test." +msgstr "A host ``vyos-oobm`` will use as a ssh proxy. This host is just necessary for the Lab test." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:312 +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 "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." + +#: ../../configexamples/azure-vpn-bgp.rst:21 +#: ../../configexamples/azure-vpn-dual-bgp.rst:18 +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 "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" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:15 +msgid "A pair of Azure VNet Gateways deployed in active-active configuration with BGP enabled." +msgstr "A pair of Azure VNet Gateways deployed in active-active configuration with BGP enabled." + +#: ../../configexamples/azure-vpn-bgp.rst:18 +msgid "A pair of Azure VNet Gateways deployed in active-passive configuration with BGP enabled." +msgstr "A pair of Azure VNet Gateways deployed in active-passive configuration with BGP enabled." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:16 +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 "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." + +#: ../../configexamples/wan-load-balancing.rst:126 +#: ../../configexamples/wan-load-balancing.rst:136 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:41 +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 "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:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:19 +msgid "Account at https://www.tunnelbroker.net/" +msgstr "Account at https://www.tunnelbroker.net/" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:21 +msgid "Active Directory on Windows server" +msgstr "Active Directory on Windows server" + +#: ../../configexamples/ha.rst:161 +msgid "Add (temporary) default route" +msgstr "Add (temporary) default route" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:47 +msgid "Add the LDAP plugin configuration file `/config/auth/ldap-auth.config`" +msgstr "Add the LDAP plugin configuration file `/config/auth/ldap-auth.config`" + +#: ../../configexamples/wan-load-balancing.rst:167 +msgid "Adding a rule for the second interface" +msgstr "Adding a rule for the second interface" + +#: ../../configexamples/ha.rst:498 +msgid "Advertise connected routes" +msgstr "Advertise connected routes" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:87 +msgid "After all is done and commit, let's take a look if the Wireguard interface is up and running." +msgstr "After all is done and commit, let's take a look if the Wireguard interface is up and running." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:324 +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 "After configured all the VRFs involved in this topology we take a deeper look at both BGP and Routing table for the VRF LAN1" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:206 +msgid "After some testing, we can check ipsec status, and counter on every tunnel:" +msgstr "After some testing, we can check ipsec status, and counter on every tunnel:" + +#: ../../configexamples/qos.rst:81 +msgid "After the interface eth0 on router VyOS3" +msgstr "After the interface eth0 on router VyOS3" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:51 +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 "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." + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:52 +msgid "After you have each public key. The wireguard interfaces can be setup." +msgstr "After you have each public key. The wireguard interfaces can be setup." + +#: ../../configexamples/wan-load-balancing.rst:28 +msgid "All outgoing packets are assigned the source address of the assigned interface (SNAT)." +msgstr "All outgoing packets are assigned the source address of the assigned interface (SNAT)." + +#: ../../configexamples/wan-load-balancing.rst:24 +msgid "All traffic coming in through eth2 is balanced between eth0 and eth1 on the router." +msgstr "All traffic coming in through eth2 is balanced between eth0 and eth1 on the router." + +#: ../../configexamples/pppoe-ipv6-basic.rst:88 +msgid "Allow DHCPv6 packets for router" +msgstr "Allow DHCPv6 packets for router" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:32 +msgid "Allow access to the router only from trusted networks." +msgstr "Allow access to the router only from trusted networks." + +#: ../../configexamples/pppoe-ipv6-basic.rst:86 +msgid "Allow all established and related traffic for router and LAN" +msgstr "Allow all established and related traffic for router and LAN" + +#: ../../configexamples/pppoe-ipv6-basic.rst:87 +msgid "Allow all icmpv6 packets for router and LAN" +msgstr "Allow all icmpv6 packets for router and LAN" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:38 +msgid "Allow all new connections from local subnets." +msgstr "Allow all new connections from local subnets." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:40 +msgid "Allow connections from LANs to LANs throught the tunnel." +msgstr "Allow connections from LANs to LANs throught the tunnel." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:34 +msgid "Allow dns requests only only for local networks." +msgstr "Allow dns requests only only for local networks." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:36 +msgid "Allow icmp on all interfaces." +msgstr "Allow icmp on all interfaces." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:220 +msgid "Also, we can check firewall counters:" +msgstr "Also, we can check firewall counters:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:716 +msgid "Also we can verify how PE devices receives VPNv4 networks from the RRs and installing them to the specific customer VRFs:" +msgstr "Also we can verify how PE devices receives VPNv4 networks from the RRs and installing them to the specific customer VRFs:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:20 +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 "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." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:191 +msgid "And NAT Configuration:" +msgstr "And NAT Configuration:" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:99 +msgid "And ping the Branch PC from your central router to check the response." +msgstr "And ping the Branch PC from your central router to check the response." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:90 +msgid "And show all DHCP Leases" +msgstr "And show all DHCP Leases" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:132 +msgid "And the ``client`` to receive an IPv6 address with stateless autoconfig." +msgstr "And the ``client`` to receive an IPv6 address with stateless autoconfig." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:None +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:None +msgid "Ansible Example topology image" +msgstr "Ansible Example topology image" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:10 +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 "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**." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:611 +msgid "Appendix-A" +msgstr "Appendix-A" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:764 +msgid "Appendix-B" +msgstr "Appendix-B" + +#: ../../configexamples/ha.rst:500 +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 "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!" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:853 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:417 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:52 +msgid "As we can see this is unpractical." +msgstr "As we can see this is unpractical." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:67 +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 "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." + +#: ../../configexamples/qos.rst:182 +msgid "As we see shaper is working and the traffic will not work over 5 Mbit/s." +msgstr "As we see shaper is working and the traffic will not work over 5 Mbit/s." + +#: ../../configexamples/ha.rst:141 +msgid "Assign external IP addresses" +msgstr "Assign external IP addresses" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:74 +msgid "Assuming the pings are successful, you need to add some DNS servers. Some options:" +msgstr "Assuming the pings are successful, you need to add some DNS servers. Some options:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:107 +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 "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:" + +#: ../../configexamples/ha.rst:516 +msgid "At this point, you now need to create the X link between all four routers. Use amdifferent /30 for each link." +msgstr "At this point, you now need to create the X link between all four routers. Use amdifferent /30 for each link." + +#: ../../configexamples/ha.rst:184 +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 "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!)" + +#: ../../configexamples/ha.rst:278 +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 "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)." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:102 +msgid "At this point, your VyOS install should have full IPv6, but now your LAN devices need access." +msgstr "At this point, your VyOS install should have full IPv6, but now your LAN devices need access." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:324 +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 "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:" + +#: ../../configexamples/azure-vpn-bgp.rst:52 +#: ../../configexamples/azure-vpn-dual-bgp.rst:51 +msgid "Azure ASN" +msgstr "Azure ASN" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:41 +msgid "Azure VNet Gateway 1 public IP" +msgstr "Azure VNet Gateway 1 public IP" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:43 +msgid "Azure VNet Gateway 2 public IP" +msgstr "Azure VNet Gateway 2 public IP" + +#: ../../configexamples/azure-vpn-bgp.rst:46 +#: ../../configexamples/azure-vpn-dual-bgp.rst:45 +msgid "Azure VNet Gateway BGP IP" +msgstr "Azure VNet Gateway BGP IP" + +#: ../../configexamples/azure-vpn-bgp.rst:44 +msgid "Azure VNet Gateway public IP" +msgstr "Azure VNet Gateway public IP" + +#: ../../configexamples/azure-vpn-bgp.rst:38 +#: ../../configexamples/azure-vpn-dual-bgp.rst:35 +msgid "Azure address space" +msgstr "Azure address space" + +#: ../../configexamples/ha.rst:534 +msgid "BGP" +msgstr "BGP" + +#: ../../configexamples/bgp-ipv6-unnumbered.rst:7 +msgid "BGP IPv6 unnumbered with extended nexthop" +msgstr "BGP IPv6 unnumbered with extended nexthop" + +#: ../../configexamples/ha.rst:536 +msgid "BGP is an extremely complex network protocol. An example is provided here." +msgstr "BGP is an extremely complex network protocol. An example is provided here." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +msgid "BLUE_HUB" +msgstr "BLUE_HUB" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "BLUE_SPOKE" +msgstr "BLUE_SPOKE" + +#: ../../configexamples/wan-load-balancing.rst:169 +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 "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:" + +#: ../../configexamples/pppoe-ipv6-basic.rst:82 +msgid "Basic Firewall" +msgstr "Basic Firewall" + +#: ../../configexamples/ha.rst:108 +msgid "Basic Setup (via console)" +msgstr "Basic Setup (via console)" + +#: ../../configexamples/qos.rst:74 +msgid "Before the interface eth0 on router VyOS3" +msgstr "Before the interface eth0 on router VyOS3" + +#: ../../configexamples/ha.rst:125 +msgid "Bonding on Hardware Router" +msgstr "Bonding on Hardware Router" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:32 +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 "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." + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:35 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:61 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:77 +msgid "Branch" +msgstr "Branch" + +#: ../../configexamples/zone-policy.rst:151 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 +msgid "CE Hub device" +msgstr "CE Hub device" + +#: ../../configexamples/qos.rst:33 +msgid "CS4 -> CS5" +msgstr "CS4 -> CS5" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:29 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:55 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:71 +msgid "Central" +msgstr "Central" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:48 +msgid "Check all possible settings `here <https://github.com/threerings/openvpn-auth-ldap/blob/master/auth-ldap.conf>`_" +msgstr "Check all possible settings `here <https://github.com/threerings/openvpn-auth-ldap/blob/master/auth-ldap.conf>`_" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:252 +msgid "Check the BGP VRF table and verify if the static routes are injected showing the correct next-hop information." +msgstr "Check the BGP VRF table and verify if the static routes are injected showing the correct next-hop information." + +#: ../../configexamples/qos.rst:67 +msgid "Check the result" +msgstr "Check the result" + +#: ../../configexamples/qos.rst:175 +msgid "Check the result." +msgstr "Check the result." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:164 +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 "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." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:204 +msgid "Checking through op-mode commands" +msgstr "Checking through op-mode commands" + +#: ../../configexamples/ha.rst:90 +msgid "Cisco VPC Crossconnect - Ports 39 and 40 bonded between each switch" +msgstr "Cisco VPC Crossconnect - Ports 39 and 40 bonded between each switch" + +#: ../../configexamples/azure-vpn-bgp.rst:92 +#: ../../configexamples/azure-vpn-dual-bgp.rst:94 +msgid "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." +msgstr "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:94 +msgid "Client configuration" +msgstr "Client configuration" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:24 +msgid "Communication between private subnets should be done through ipsec tunnel without nat." +msgstr "Communication between private subnets should be done through ipsec tunnel without nat." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:601 +msgid "Conclusions" +msgstr "Conclusions" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:26 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:25 +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:37 +#: ../../configexamples/bgp-ipv6-unnumbered.rst:12 +#: ../../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 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:100 +#: ../../configexamples/ospf-unnumbered.rst:12 +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:47 +#: ../../configexamples/segment-routing-isis.rst:24 +msgid "Configuration" +msgstr "Configuration" + +#: ../../configexamples/qos.rst:38 +msgid "Configuration:" +msgstr "Configuration:" + +#: ../../configexamples/nmp.rst:26 +msgid "Configuration 'NMP'" +msgstr "Configuration 'NMP'" + +#: ../../configexamples/nmp.rst:13 +msgid "Configuration 'VyOS'" +msgstr "Configuration 'VyOS'" + +#: ../../configexamples/qos.rst:10 +msgid "Configuration 'dcsp' and shaper using QoS" +msgstr "Configuration 'dcsp' and shaper using QoS" + +#: ../../configexamples/index.rst:4 +msgid "Configuration Blueprints" +msgstr "Configuration Blueprints" + +#: ../../configexamples/index.rst:28 +msgid "Configuration Blueprints (autotest)" +msgstr "Configuration Blueprints (autotest)" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:40 +msgid "Configuration VyOS as OpenVPN Server" +msgstr "Configuration VyOS as OpenVPN Server" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:27 +msgid "Configuration of basic firewall in one site, in order to:" +msgstr "Configuration of basic firewall in one site, in order to:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:113 +#: ../../configexamples/pppoe-ipv6-basic.rst:26 +msgid "Configurations" +msgstr "Configurations" + +#: ../../configexamples/ha.rst:358 +msgid "Configure Wireguard" +msgstr "Configure Wireguard" + +#: ../../configexamples/azure-vpn-bgp.rst:85 +msgid "Configure a VTI with a dummy IP address" +msgstr "Configure a VTI with a dummy IP address" + +#: ../../configexamples/ha.rst:312 +msgid "Configure conntrack-sync and enable helpers" +msgstr "Configure conntrack-sync and enable helpers" + +#: ../../configexamples/azure-vpn-bgp.rst:58 +#: ../../configexamples/azure-vpn-dual-bgp.rst:57 +msgid "Configure the IKE and ESP settings to match a subset of those supported by Azure:" +msgstr "Configure the IKE and ESP settings to match a subset of those supported by Azure:" + +#: ../../configexamples/azure-vpn-bgp.rst:98 +msgid "Configure the VPN tunnel" +msgstr "Configure the VPN tunnel" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:101 +msgid "Configure the VPN tunnels" +msgstr "Configure the VPN tunnels" + +#: ../../configexamples/wan-load-balancing.rst:47 +msgid "Configure the WAN load balancer with the parameters described above:" +msgstr "Configure the WAN load balancer with the parameters described above:" + +#: ../../configexamples/wan-load-balancing.rst:46 +msgid "Configure the load balancer" +msgstr "Configure the load balancer" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:84 +msgid "Configure two VTIs with a dummy IP address each" +msgstr "Configure two VTIs with a dummy IP address each" + +#: ../../configexamples/azure-vpn-bgp.rst:123 +#: ../../configexamples/azure-vpn-dual-bgp.rst:141 +msgid "Configure your BGP settings" +msgstr "Configure your BGP settings" + +#: ../../configexamples/ha.rst:314 +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 "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." + +#: ../../configexamples/nmp.rst:9 +msgid "Consider how to quickly set up NMP and VyOS for monitoring. NMP is multi-vendor network monitoring from 'SolarWinds' built to scale and expand with the needs of your network." +msgstr "Consider how to quickly set up NMP and VyOS for monitoring. NMP is multi-vendor network monitoring from 'SolarWinds' built to scale and expand with the needs of your network." + +#: ../../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 +msgid "Core" +msgstr "Core" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:134 +msgid "Core Router" +msgstr "Core Router" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:62 +msgid "Core network" +msgstr "Core network" + +#: ../../configexamples/ha.rst:417 +msgid "Create Export Filter" +msgstr "Create Export Filter" + +#: ../../configexamples/ha.rst:448 +msgid "Create Import Filter" +msgstr "Create Import Filter" + +#: ../../configexamples/ha.rst:265 +msgid "Create VRRP sync-group" +msgstr "Create VRRP sync-group" + +#: ../../configexamples/ha.rst:127 +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 "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." + +#: ../../configexamples/ha.rst:117 +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 "Create an 'All VLANs' network group, that passes all trunked traffic through to the VM. Attach this network group to router1 as eth0." + +#: ../../configexamples/wan-load-balancing.rst:81 +msgid "Create interface weight based configuration" +msgstr "Create interface weight based configuration" + +#: ../../configexamples/wan-load-balancing.rst:111 +msgid "Create rule order based configuration" +msgstr "Create rule order based configuration" + +#: ../../configexamples/wan-load-balancing.rst:142 +msgid "Create rule order based configuration with low speed secondary link" +msgstr "Create rule order based configuration with low speed secondary link" + +#: ../../configexamples/wan-load-balancing.rst:35 +msgid "Create static routes through the two ISPs towards the ping targets and commit the changes:" +msgstr "Create static routes through the two ISPs towards the ping targets and commit the changes:" + +#: ../../configexamples/wan-load-balancing.rst:34 +msgid "Create static routes to ping targets" +msgstr "Create static routes to ping targets" + +#: ../../configexamples/ha.rst:110 +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 "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." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:44 +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:62 +msgid "DHCP-Relay" +msgstr "DHCP-Relay" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:37 +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:55 +msgid "DHCP-Server" +msgstr "DHCP-Server" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:3 +msgid "DHCP Relay trough GRE-Bridge" +msgstr "DHCP Relay trough GRE-Bridge" + +#: ../../configexamples/pppoe-ipv6-basic.rst:42 +msgid "DHCPv6-PD Setup" +msgstr "DHCPv6-PD Setup" + +#: ../../configexamples/zone-policy.rst:374 +msgid "DMZ-LAN policy is LAN-DMZ. You can get a rhythm to it when you build out a bunch at one time." +msgstr "DMZ-LAN policy is LAN-DMZ. You can get a rhythm to it when you build out a bunch at one time." + +#: ../../configexamples/zone-policy.rst:49 +msgid "DMZ cannot access LAN resources." +msgstr "DMZ cannot access LAN resources." + +#: ../../configexamples/ha.rst:18 +msgid "Design" +msgstr "Design" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 +msgid "Device-A" +msgstr "Device-A" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 +msgid "Device-B" +msgstr "Device-B" + +#: ../../configexamples/ha.rst:514 +msgid "Duplicate configuration" +msgstr "Duplicate configuration" + +#: ../../configexamples/pppoe-ipv6-basic.rst:44 +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 "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)." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:484 +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 "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." + +#: ../../configexamples/zone-policy.rst:91 +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 "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." + +#: ../../configexamples/index.rst:32 +msgid "Each lab will build an test from an external script. The page content will generate, so changes will not take an effect." +msgstr "Each lab will build an test from an external script. The page content will generate, so changes will not take an effect." + +#: ../../configexamples/azure-vpn-bgp.rst:79 +#: ../../configexamples/azure-vpn-dual-bgp.rst:78 +msgid "Enable IPsec on eth0" +msgstr "Enable IPsec on eth0" + +#: ../../configexamples/ha.rst:470 +msgid "Enable OSPF" +msgstr "Enable OSPF" + +#: ../../configexamples/ha.rst:174 +msgid "Enable SSH" +msgstr "Enable SSH" + +#: ../../configexamples/ha.rst:176 +msgid "Enable SSH so you can now SSH into the routers, rather than using the console." +msgstr "Enable SSH so you can now SSH into the routers, rather than using the console." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:140 +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 "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." + +#: ../../configexamples/zone-policy.rst:253 +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 "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." + +#: ../../configexamples/ha.rst:472 +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 "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." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:114 +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 "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." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:108 +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 "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." + +#: ../../configexamples/azure-vpn-bgp.rst:31 +#: ../../configexamples/azure-vpn-dual-bgp.rst:28 +msgid "Example" +msgstr "Example" + +#: ../../configexamples/wan-load-balancing.rst:12 +msgid "Example 1: Distributing load evenly" +msgstr "Example 1: Distributing load evenly" + +#: ../../configexamples/wan-load-balancing.rst:68 +msgid "Example 2: Failover based on interface weights" +msgstr "Example 2: Failover based on interface weights" + +#: ../../configexamples/wan-load-balancing.rst:95 +msgid "Example 3: Failover based on rule order" +msgstr "Example 3: Failover based on rule order" + +#: ../../configexamples/wan-load-balancing.rst:124 +msgid "Example 4: Failover based on rule order - priority traffic" +msgstr "Example 4: Failover based on rule order - priority traffic" + +#: ../../configexamples/wan-load-balancing.rst:156 +msgid "Example 5: Exclude traffic from load balancing" +msgstr "Example 5: Exclude traffic from load balancing" + +#: ../../configexamples/ha.rst:43 +msgid "Example Network" +msgstr "Example Network" + +#: ../../configexamples/pppoe-ipv6-basic.rst:38 +msgid "Fill ``password`` and ``user`` with the credential provided by your ISP." +msgstr "Fill ``password`` and ``user`` with the credential provided by your ISP." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:202 +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 "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`." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:985 +msgid "Finally, let’s check the reachability between CEs:" +msgstr "Finally, let’s check the reachability between CEs:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:200 +msgid "Firewall" +msgstr "Firewall" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:123 +msgid "Firewall Configuration:" +msgstr "Firewall Configuration:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:39 +msgid "First, we configure the ``vyos-wan`` interface to get a DHCP address." +msgstr "First, we configure the ``vyos-wan`` interface to get a DHCP address." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:28 +msgid "First, we configure the transport network and the Tunnel interface." +msgstr "First, we configure the transport network and the Tunnel interface." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:44 +msgid "First a CA, a signed server and client ceftificate and a Diffie-Hellman parameter musst be generated and installed. Please look :ref:`here <configuration/pki/index:pki>` for more information." +msgstr "First a CA, a signed server and client ceftificate and a Diffie-Hellman parameter musst be generated and installed. Please look :ref:`here <configuration/pki/index:pki>` for more information." + +#: ../../configexamples/nmp.rst:15 +msgid "First prepare our VyOS router for connection to NMP. We have to set up the SNMP protocol and connectivity between the router and NMP." +msgstr "First prepare our VyOS router for connection to NMP. We have to set up the SNMP protocol and connectivity between the router and NMP." + +#: ../../configexamples/ha.rst:60 +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 "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" + +#: ../../configexamples/pppoe-ipv6-basic.rst:56 +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 "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." + +#: ../../configexamples/azure-vpn-bgp.rst:11 +msgid "For redundant / active-active configurations see :ref:`examples-azure-vpn-dual-bgp`" +msgstr "For redundant / active-active configurations see :ref:`examples-azure-vpn-dual-bgp`" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:10 +msgid "For simplicity, configuration and tests are done only using ipv4, and firewall configuration in done only on one router." +msgstr "For simplicity, configuration and tests are done only using ipv4, and firewall configuration in done only on one router." + +#: ../../configexamples/ha.rst:146 +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 "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." + +#: ../../configexamples/ha.rst:88 +msgid "From Datacenter - This connects into port 1 on both switches, and is tagged as VLAN 50" +msgstr "From Datacenter - This connects into port 1 on both switches, and is tagged as VLAN 50" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:427 +msgid "From Management to LAN1/LAN2" +msgstr "From Management to LAN1/LAN2" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:469 +msgid "From Management to Outside (fails as intended)" +msgstr "From Management to Outside (fails as intended)" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:614 +msgid "Full configuration from all devices" +msgstr "Full configuration from all devices" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:19 +msgid "General information about L3VPNs can be found in the :ref:`configuration/vrf/index:L3VPN VRFs` chapter." +msgstr "General information about L3VPNs can be found in the :ref:`configuration/vrf/index:L3VPN VRFs` chapter." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:49 +msgid "General information can be found in the :ref:`configuration/vrf/index:L3VPN VRFs` chapter." +msgstr "General information can be found in the :ref:`configuration/vrf/index:L3VPN VRFs` chapter." + +#: ../../configexamples/bgp-ipv6-unnumbered.rst:9 +msgid "General information can be found in the :ref:`routing-bgp` chapter." +msgstr "General information can be found in the :ref:`routing-bgp` chapter." + +#: ../../configexamples/ospf-unnumbered.rst:9 +msgid "General information can be found in the :ref:`routing-ospf` chapter." +msgstr "General information can be found in the :ref:`routing-ospf` chapter." + +#: ../../configexamples/ha.rst:74 +msgid "Hardware" +msgstr "Hardware" + +#: ../../configexamples/ha.rst:91 +msgid "Hardware Router - Port 8 of each switch" +msgstr "Hardware Router - Port 8 of each switch" + +#: ../../configexamples/zone-policy.rst:282 +msgid "Here is an example of an IPv6 DMZ-WAN ruleset." +msgstr "Here is an example of an IPv6 DMZ-WAN ruleset." + +#: ../../configexamples/segment-routing-isis.rst:178 +msgid "Here is the routing tables showing the MPLS segment routing label operations:" +msgstr "Here is the routing tables showing the MPLS segment routing label operations:" + +#: ../../configexamples/pppoe-ipv6-basic.rst:76 +msgid "Here we set the prefix to ``::/64`` to indicate advertising any /64 prefix the LAN interface is assigned." +msgstr "Here we set the prefix to ``::/64`` to indicate advertising any /64 prefix the LAN interface is assigned." + +#: ../../configexamples/pppoe-ipv6-basic.rst:54 +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 "Here we use the prefix to configure the address of eth1 (LAN) to form ``<prefix>::64``, where ``64`` is hexadecimal of address 100." + +#: ../../configexamples/ha.rst:7 +msgid "High Availability Walkthrough" +msgstr "High Availability Walkthrough" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:65 +msgid "How does it work?" +msgstr "How does it work?" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +msgid "Hub" +msgstr "Hub" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:6 +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 "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." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:65 +msgid "IPSec configuration:" +msgstr "IPSec configuration:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:82 +msgid "IP Schema" +msgstr "IP Schema" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 +msgid "IPv4 Network" +msgstr "IPv4 Network" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 +msgid "IPv6 Network" +msgstr "IPv6 Network" + +#: ../../configexamples/zone-policy.rst:383 +msgid "IPv6 Tunnel" +msgstr "IPv6 Tunnel" + +#: ../../configexamples/segment-routing-isis.rst:17 +msgid "ISIS-SR example network" +msgstr "ISIS-SR example network" + +#: ../../configexamples/segment-routing-isis.rst:17 +msgid "ISIS-SR network" +msgstr "ISIS-SR network" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:739 +msgid "ISP" +msgstr "ISP" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:64 +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 "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." + +#: ../../configexamples/zone-policy.rst:171 +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 "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." + +#: ../../configexamples/zone-policy.rst:100 +msgid "I name rule sets to indicate which zone-pair-direction they represent. eg. ZoneA-ZoneB or ZoneB-ZoneA. LAN-DMZ, DMZ-LAN." +msgstr "I name rule sets to indicate which zone-pair-direction they represent. eg. ZoneA-ZoneB or ZoneB-ZoneA. LAN-DMZ, DMZ-LAN." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:14 +msgid "I named the customers blue, red and green which is common practice in VRF (Virtual Routing and Forwarding) documentation scenarios." +msgstr "I named the customers blue, red and green which is common practice in VRF (Virtual Routing and Forwarding) documentation scenarios." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:9 +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 "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." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:256 +msgid "If the client is connect successfully you can check the output with" +msgstr "If the client is connect successfully you can check the output with" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:236 +msgid "If we need to retrieve information about a specific host/network inside the EVPN network we need to run" +msgstr "If we need to retrieve information about a specific host/network inside the EVPN network we need to run" + +#: ../../configexamples/ha.rst:34 +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 "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." + +#: ../../configexamples/zone-policy.rst:385 +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 "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." + +#: ../../configexamples/ha.rst:354 +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 "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." + +#: ../../configexamples/zone-policy.rst:110 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:44 +msgid "Image name: vyos-1.4-rolling-202110310317-amd64.iso" +msgstr "Image name: vyos-1.4-rolling-202110310317-amd64.iso" + +#: ../../configexamples/zone-policy.rst:103 +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 "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." + +#: ../../configexamples/zone-policy.rst:167 +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 "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." + +#: ../../configexamples/zone-policy.rst:18 +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 "In :vytask:`T2199` the syntax of the zone configuration was changed. The zone configuration moved from ``zone-policy zone <name>`` to ``firewall zone <name>``." + +#: ../../configexamples/zone-policy.rst:115 +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 "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." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:176 +msgid "In the above examples, 1,2,ffff are all chosen by you. You can use 1-ffff (1-65535)." +msgstr "In the above examples, 1,2,ffff are all chosen by you. You can use 1-ffff (1-65535)." + +#: ../../configexamples/qos.rst:157 +msgid "In the end, on the router “VyOS2” we will set outgoing bandwidth limits between the “VyOS3” and “VyOS1” routers. Let's set a limit for IP 10.1.1.100 = 5 Mbps(Tx). We will check the result of the work with the help of the “iPerf” utility." +msgstr "In the end, on the router “VyOS2” we will set outgoing bandwidth limits between the “VyOS3” and “VyOS1” routers. Let's set a limit for IP 10.1.1.100 = 5 Mbps(Tx). We will check the result of the work with the help of the “iPerf” utility." + +#: ../../configexamples/qos.rst:35 +msgid "In the end, we will configure the traffic shaper using QoS mechanisms on the “VYOS2” router." +msgstr "In the end, we will configure the traffic shaper using QoS mechanisms on the “VYOS2” router." + +#: ../../configexamples/nmp.rst:66 +msgid "In the end, you'll get a powerful instrument for monitoring the VyOS systems." +msgstr "In the end, you'll get a powerful instrument for monitoring the VyOS systems." + +#: ../../configexamples/zone-policy.rst:377 +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 "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." + +#: ../../configexamples/ha.rst:154 +msgid "In this case, the hardware router has a different IP, so it would be" +msgstr "In this case, the hardware router has a different IP, so it would be" + +#: ../../configexamples/qos.rst:12 +msgid "In this case, we'll try to make a simple lab using QoS and the general ability of the VyOS system. We recommend you to go through the main article about `QoS <https://docs.vyos.io/en/latest/configuration/trafficpolicy/index.html>`_ first." +msgstr "In this case, we'll try to make a simple lab using QoS and the general ability of the VyOS system. We recommend you to go through the main article about `QoS <https://docs.vyos.io/en/latest/configuration/trafficpolicy/index.html>`_ first." + +#: ../../configexamples/zone-policy.rst:365 +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 "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." + +#: ../../configexamples/ha.rst:45 +msgid "In this document, we have been allocated 203.0.113.0/24 by our upstream provider, which we are publishing on VLAN100." +msgstr "In this document, we have been allocated 203.0.113.0/24 by our upstream provider, which we are publishing on VLAN100." + +#: ../../configexamples/wan-load-balancing.rst:76 +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 "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." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:42 +msgid "In this example OpenVPN will be setup with a client certificate and username / password authentication." +msgstr "In this example OpenVPN will be setup with a client certificate and username / password authentication." + +#: ../../configexamples/wan-load-balancing.rst:158 +msgid "In this example two LAN interfaces exist in different subnets instead of one like in the previous examples:" +msgstr "In this example two LAN interfaces exist in different subnets instead of one like in the previous examples:" + +#: ../../configexamples/zone-policy.rst:107 +msgid "In this example we have 4 zones. LAN, WAN, DMZ, Local. The local zone is the firewall itself." +msgstr "In this example we have 4 zones. LAN, WAN, DMZ, Local. The local zone is the firewall itself." + +#: ../../configexamples/zone-policy.rst:50 +msgid "Inbound WAN connect to DMZ host." +msgstr "Inbound WAN connect to DMZ host." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:189 +msgid "Information about Ethernet Virtual Private Networks" +msgstr "Information about Ethernet Virtual Private Networks" + +#: ../../configexamples/segment-routing-isis.rst:223 +msgid "Information about prefix-sid and label-operation from VyOS" +msgstr "Information about prefix-sid and label-operation from VyOS" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:3 +msgid "Inter-VRF Routing over VRF Lite" +msgstr "Inter-VRF Routing over VRF Lite" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:603 +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 "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." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:49 +msgid "Interface and routing configuration:" +msgstr "Interface and routing configuration:" + +#: ../../configexamples/ha.rst:195 +msgid "Internal Network" +msgstr "Internal Network" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:30 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 +msgid "Internet" +msgstr "Internet" + +#: ../../configexamples/zone-policy.rst:40 +msgid "Internet - 192.168.200.100 - TCP/25" +msgstr "Internet - 192.168.200.100 - TCP/25" + +#: ../../configexamples/zone-policy.rst:39 +msgid "Internet - 192.168.200.100 - TCP/443" +msgstr "Internet - 192.168.200.100 - TCP/443" + +#: ../../configexamples/zone-policy.rst:41 +msgid "Internet - 192.168.200.100 - TCP/53" +msgstr "Internet - 192.168.200.100 - TCP/53" + +#: ../../configexamples/zone-policy.rst:38 +msgid "Internet - 192.168.200.100 - TCP/80" +msgstr "Internet - 192.168.200.100 - TCP/80" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:79 +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 "It's important to note that all your existing configurations will be migrated automatically on image upgrade. Nothing to do on your side." + +#: ../../configexamples/ha.rst:163 +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 "It is assumed that the routers provided by upstream are capable of acting as a default router, add that as a static route." + +#: ../../configexamples/zone-policy.rst:140 +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 "It is good practice to log both accepted and denied traffic. It can save you significant headaches when trying to troubleshoot a connectivity issue." + +#: ../../configexamples/zone-policy.rst:60 +msgid "It will look something like this:" +msgstr "It will look something like this:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:13 +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 "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." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:4 +msgid "L3VPN EVPN with VyOS" +msgstr "L3VPN EVPN with VyOS" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:None +msgid "L3VPN EVPN with VyOS topology image" +msgstr "L3VPN EVPN with VyOS topology image" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:83 +msgid "L3VPN configuration parameters table:" +msgstr "L3VPN configuration parameters table:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:4 +msgid "L3VPN for Hub-and-Spoke connectivity with VyOS" +msgstr "L3VPN for Hub-and-Spoke connectivity with VyOS" + +#: ../../configexamples/zone-policy.rst:392 +msgid "LAN, WAN, DMZ, local and TUN (tunnel)" +msgstr "LAN, WAN, DMZ, local and TUN (tunnel)" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:701 +msgid "LAN1" +msgstr "LAN1" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:575 +msgid "LAN1 to LAN2" +msgstr "LAN1 to LAN2" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:520 +msgid "LAN1 to Outside" +msgstr "LAN1 to Outside" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:713 +msgid "LAN2" +msgstr "LAN2" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:27 +msgid "LAN 1" +msgstr "LAN 1" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:28 +msgid "LAN 2" +msgstr "LAN 2" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:100 +msgid "LAN Configuration" +msgstr "LAN Configuration" + +#: ../../configexamples/zone-policy.rst:47 +msgid "LAN and DMZ hosts have basic outbound access: Web, FTP, SSH." +msgstr "LAN and DMZ hosts have basic outbound access: Web, FTP, SSH." + +#: ../../configexamples/zone-policy.rst:48 +msgid "LAN can access DMZ resources." +msgstr "LAN can access DMZ resources." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:551 +msgid "Let’s check IPv4 routing and MPLS information on provider nodes (same procedure for all P nodes):" +msgstr "Let’s check IPv4 routing and MPLS information on provider nodes (same procedure for all P nodes):" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:25 +msgid "Let’s say we have a requirement to have multiple networks." +msgstr "Let’s say we have a requirement to have multiple networks." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:22 +msgid "Local subnets should be able to reach internet using source nat." +msgstr "Local subnets should be able to reach internet using source nat." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:58 +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 "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." + +#: ../../configexamples/qos.rst:60 +msgid "Main rules:" +msgstr "Main rules:" + +#: ../../configexamples/ha.rst:414 +msgid "Make sure you can ping 10.254.60.1 and .2 from both routers." +msgstr "Make sure you can ping 10.254.60.1 and .2 from both routers." + +#: ../../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 +msgid "Management" +msgstr "Management" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:26 +msgid "Management VRF" +msgstr "Management VRF" + +#: ../../configexamples/ha.rst:114 +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 "Many other Hypervisors do this, and I'm hoping that this document will be expanded to document how to do this for others." + +#: ../../configexamples/ha.rst:297 +msgid "Masquerade Traffic originating from 10.200.201.0/24 that is heading out the public interface." +msgstr "Masquerade Traffic originating from 10.200.201.0/24 that is heading out the public interface." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:254 +msgid "Monitoring" +msgstr "Monitoring" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:162 +msgid "Multiple LAN/DMZ Setup" +msgstr "Multiple LAN/DMZ Setup" + +#: ../../configexamples/ha.rst:295 +msgid "NAT and conntrack-sync" +msgstr "NAT and conntrack-sync" + +#: ../../configexamples/nmp.rst:7 +msgid "NMP example" +msgstr "NMP example" + +#: ../../configexamples/zone-policy.rst:23 +msgid "Native IPv4 and IPv6" +msgstr "Native IPv4 and IPv6" + +#: ../../configexamples/ha.rst:86 +msgid "Network Cabling" +msgstr "Network Cabling" + +#: ../../configexamples/pppoe-ipv6-basic.rst:18 +msgid "Network Topology" +msgstr "Network Topology" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:None +#: ../../configexamples/l3vpn-hub-and-spoke.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/nmp.rst:None +#: ../../configexamples/pppoe-ipv6-basic.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/qos.rst:None +#: ../../configexamples/wan-load-balancing.rst:None +#: ../../configexamples/wan-load-balancing.rst:None +#: ../../configexamples/zone-policy.rst:None +msgid "Network Topology Diagram" +msgstr "Network Topology Diagram" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:14 +msgid "Network Topology and requirements" +msgstr "Network Topology and requirements" + +#: ../../configexamples/qos.rst:31 +msgid "Next, we will replace only all CS4 labels on the “VyOS2” router." +msgstr "Next, we will replace only all CS4 labels on the “VyOS2” router." + +#: ../../configexamples/nmp.rst:28 +msgid "Next, you just should follow the pictures:" +msgstr "Next, you just should follow the pictures:" + +#: ../../configexamples/qos.rst:106 +msgid "Next on the router VyOS2 we will change labels on all incoming traffic only from CS4-> CS6" +msgstr "Next on the router VyOS2 we will change labels on all incoming traffic only from CS4-> CS6" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:42 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "Node" +msgstr "Node" + +#: ../../configexamples/ha.rst:83 +msgid "Note that router1 is a VM that runs on one of the compute nodes." +msgstr "Note that router1 is a VM that runs on one of the compute nodes." + +#: ../../configexamples/pppoe-ipv6-basic.rst:111 +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 "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)." + +#: ../../configexamples/zone-policy.rst:411 +msgid "Notice, none go to WAN since WAN wouldn't have a v6 address on it." +msgstr "Notice, none go to WAN since WAN wouldn't have a v6 address on it." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:831 +msgid "Now, let’s check routing information on out Hub PE:" +msgstr "Now, let’s check routing information on out Hub PE:" + +#: ../../configexamples/ha.rst:322 +msgid "Now enable replication between nodes. Replace eth0.201 with bond0.201 on the hardware router." +msgstr "Now enable replication between nodes. Replace eth0.201 with bond0.201 on the hardware router." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:54 +msgid "Now generate all required certificates on the ovpn-server:" +msgstr "Now generate all required certificates on the ovpn-server:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:144 +msgid "Now the Client is able to ping a public IPv6 address" +msgstr "Now the Client is able to ping a public IPv6 address" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:45 +msgid "Now we are able to setup the tunnel interface." +msgstr "Now we are able to setup the tunnel interface." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:425 +msgid "Now we perform some end-to-end testing" +msgstr "Now we perform some end-to-end testing" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:636 +msgid "Now we’re checking iBGP status and routes from route-reflector nodes to other devices:" +msgstr "Now we’re checking iBGP status and routes from route-reflector nodes to other devices:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:57 +msgid "Now you should be able to ping a public IPv6 Address" +msgstr "Now you should be able to ping a public IPv6 Address" + +#: ../../configexamples/ha.rst:348 +msgid "OSPF Over WireGuard" +msgstr "OSPF Over WireGuard" + +#: ../../configexamples/ospf-unnumbered.rst:7 +msgid "OSPF unnumbered with ECMP" +msgstr "OSPF unnumbered with ECMP" + +#: ../../configexamples/azure-vpn-bgp.rst:36 +#: ../../configexamples/azure-vpn-dual-bgp.rst:33 +msgid "On-premises address space" +msgstr "On-premises address space" + +#: ../../configexamples/qos.rst:88 +msgid "On the router, VyOS4 set all traffic as CS4. We have to configure the default class and class for changing all labels from CS0 to CS4" +msgstr "On the router, VyOS4 set all traffic as CS4. We have to configure the default class and class for changing all labels from CS0 to CS4" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:105 +msgid "Once all routers can be safely remotely managed and the core network is operational, we can now setup the tenant networks." +msgstr "Once all routers can be safely remotely managed and the core network is operational, we can now setup the tenant networks." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:87 +msgid "Once all the required certificates and keys are installed, the remaining OpenVPN Server configuration can be carried out." +msgstr "Once all the required certificates and keys are installed, the remaining OpenVPN Server configuration can be carried out." + +#: ../../configexamples/zone-policy.rst:355 +msgid "Once you have all of your rulesets built, then you need to create your zone-policy." +msgstr "Once you have all of your rulesets built, then you need to create your zone-policy." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:96 +msgid "One advantage of having the client certificate stored is the ability to create the client configuration." +msgstr "One advantage of having the client certificate stored is the ability to create the client configuration." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:47 +msgid "One cable/logical connection between LAN1 and Internet" +msgstr "One cable/logical connection between LAN1 and Internet" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:46 +msgid "One cable/logical connection between LAN1 and LAN2" +msgstr "One cable/logical connection between LAN1 and LAN2" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:49 +msgid "One cable/logical connection between LAN1 and Management" +msgstr "One cable/logical connection between LAN1 and Management" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:48 +msgid "One cable/logical connection between LAN2 and Internet" +msgstr "One cable/logical connection between LAN2 and Internet" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:50 +msgid "One cable/logical connection between LAN2 and Management" +msgstr "One cable/logical connection between LAN2 and Management" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:5 +msgid "OpenVPN with LDAP" +msgstr "OpenVPN with LDAP" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:None +msgid "OpenVPN with LDAP topology image" +msgstr "OpenVPN with LDAP topology image" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:42 +msgid "Operating system: VyOS" +msgstr "Operating system: VyOS" + +#: ../../configexamples/ha.rst:100 +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 "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." + +#: ../../configexamples/ha.rst:52 +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 "Our routers are going to have a floating IP address of 203.0.113.1, and use .2 and .3 as their fixed IPs." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:23 +#: ../../configexamples/wan-load-balancing.rst:23 +#: ../../configexamples/wan-load-balancing.rst:75 +#: ../../configexamples/wan-load-balancing.rst:104 +#: ../../configexamples/wan-load-balancing.rst:135 +msgid "Overview" +msgstr "Overview" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:82 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:123 +msgid "PE1" +msgstr "PE1" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:17 +msgid "PE1 is located in an industrial area that holds multiple office buildings. All customers have a site in this area." +msgstr "PE1 is located in an industrial area that holds multiple office buildings. All customers have a site in this area." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:88 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:129 +msgid "PE2" +msgstr "PE2" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:19 +msgid "PE2 is located in a smaller area where by coincidence two customers (blue and red) share an office building." +msgstr "PE2 is located in a smaller area where by coincidence two customers (blue and red) share an office building." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:94 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:135 +msgid "PE3" +msgstr "PE3" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:21 +msgid "PE3 is located in a smaller area where by coincidence two customers (blue and green) are located." +msgstr "PE3 is located in a smaller area where by coincidence two customers (blue and green) are located." + +#: ../../configexamples/pppoe-ipv6-basic.rst:7 +msgid "PPPoE IPv6 Basic Setup for Home Network" +msgstr "PPPoE IPv6 Basic Setup for Home Network" + +#: ../../configexamples/pppoe-ipv6-basic.rst:29 +msgid "PPPoE Setup" +msgstr "PPPoE Setup" + +#: ../../configexamples/segment-routing-isis.rst:255 +msgid "Ping between VyOS-P1 / VyOS-P2 to confirm reachability:" +msgstr "Ping between VyOS-P1 / VyOS-P2 to confirm reachability:" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:73 +msgid "Ping the Client from the DHCP Server." +msgstr "Ping the Client from the DHCP Server." + +#: ../../configexamples/wan-load-balancing.rst:26 +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 "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)." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:128 +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:195 +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 "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." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:5 +msgid "Policy-Based Site-to-Site VPN and Firewall Configuration" +msgstr "Policy-Based Site-to-Site VPN and Firewall Configuration" + +#: ../../configexamples/azure-vpn-bgp.rst:48 +#: ../../configexamples/azure-vpn-dual-bgp.rst:47 +msgid "Pre-shared key" +msgstr "Pre-shared key" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:14 +#: ../../configexamples/azure-vpn-bgp.rst:16 +#: ../../configexamples/azure-vpn-dual-bgp.rst:13 +msgid "Prerequisites" +msgstr "Prerequisites" + +#: ../../configexamples/ha.rst:520 +msgid "Priorities" +msgstr "Priorities" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:29 +msgid "Protect the router on 'WAN' interface, allowing only ipsec connections and ssh access from trusted ips." +msgstr "Protect the router on 'WAN' interface, allowing only ipsec connections and ssh access from trusted ips." + +#: ../../configexamples/ha.rst:230 +msgid "Public Network" +msgstr "Public Network" + +#: ../../configexamples/qos.rst:7 +msgid "QoS example" +msgstr "QoS example" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "RD" +msgstr "RD" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:97 +msgid "RD & RT Schema" +msgstr "RD & RT Schema" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 +msgid "RT" +msgstr "RT" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "RT export" +msgstr "RT export" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "RT import" +msgstr "RT import" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:73 +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 "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)." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:120 +msgid "Remote Networks" +msgstr "Remote Networks" + +#: ../../configexamples/ha.rst:368 +msgid "Replace the 203.0.113.3 with whatever the other router's IP address is." +msgstr "Replace the 203.0.113.3 with whatever the other router's IP address is." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:20 +msgid "Requested a \"Regular Tunnel\". You want to choose a location that is closest to your physical location for the best response time." +msgstr "Requested a \"Regular Tunnel\". You want to choose a location that is closest to your physical location for the best response time." + +#: ../../configexamples/bgp-ipv6-unnumbered.rst:55 +#: ../../configexamples/ospf-unnumbered.rst:50 +msgid "Results" +msgstr "Results" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "Role" +msgstr "Role" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:6 +msgid "Route-Based Redundant Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" +msgstr "Route-Based Redundant Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" + +#: ../../configexamples/azure-vpn-bgp.rst:6 +msgid "Route-Based Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" +msgstr "Route-Based Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:767 +msgid "Route-Filtering" +msgstr "Route-Filtering" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:110 +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 "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" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:107 +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 "Routed /64. This is the default assignment. In IPv6-land, it's good for a single \"LAN\", and is somewhat equivalent to a /24." + +#: ../../configexamples/bgp-ipv6-unnumbered.rst:14 +#: ../../configexamples/bgp-ipv6-unnumbered.rst:57 +#: ../../configexamples/ospf-unnumbered.rst:14 +#: ../../configexamples/ospf-unnumbered.rst:52 +msgid "Router A:" +msgstr "Router A:" + +#: ../../configexamples/pppoe-ipv6-basic.rst:61 +msgid "Router Advertisement" +msgstr "Router Advertisement" + +#: ../../configexamples/bgp-ipv6-unnumbered.rst:34 +#: ../../configexamples/bgp-ipv6-unnumbered.rst:118 +#: ../../configexamples/ospf-unnumbered.rst:31 +#: ../../configexamples/ospf-unnumbered.rst:87 +msgid "Router B:" +msgstr "Router B:" + +#: ../../configexamples/ha.rst:538 +msgid "Router id's must be unique." +msgstr "Router id's must be unique." + +#: ../../configexamples/zone-policy.rst:98 +msgid "Ruleset are created per zone-pair-direction." +msgstr "Ruleset are created per zone-pair-direction." + +#: ../../configexamples/segment-routing-isis.rst:7 +msgid "Segment-routing IS-IS example" +msgstr "Segment-routing IS-IS example" + +#: ../../configexamples/pppoe-ipv6-basic.rst:73 +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 "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." + +#: ../../configexamples/qos.rst:40 +msgid "Set IP addresses on all VPCs and a default gateway 172.17.1.1. We'll use in this case only static routes. On the VyOS3 router, we need to change the 'dscp' labels for the VPCs. To do this, we use this configuration." +msgstr "Set IP addresses on all VPCs and a default gateway 172.17.1.1. We'll use in this case only static routes. On the VyOS3 router, we need to change the 'dscp' labels for the VPCs. To do this, we use this configuration." + +#: ../../configexamples/pppoe-ipv6-basic.rst:72 +msgid "Set MTU in advertisement to 1492 because of PPPoE header overhead." +msgstr "Set MTU in advertisement to 1492 because of PPPoE header overhead." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:143 +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 "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." + +#: ../../configexamples/ha.rst:522 +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 "Set the cost on the secondary links to be 200. This means that they will not be used unless the primary links are down." + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:27 +msgid "Set the local subnet on eth2 and the public ip address eth1 on each site." +msgstr "Set the local subnet on eth2 and the public ip address eth1 on each site." + +#: ../../configexamples/qos.rst:159 +msgid "Set up bandwidth limits on the eth2 interface of the router “VyOS2”." +msgstr "Set up bandwidth limits on the eth2 interface of the router “VyOS2”." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:139 +msgid "Sets your LAN interface's IP address" +msgstr "Sets your LAN interface's IP address" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:235 +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 "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." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:51 +msgid "Setup the ipv6 default route to the tunnel interface" +msgstr "Setup the ipv6 default route to the tunnel interface" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:148 +msgid "Show routes for all VRFs" +msgstr "Show routes for all VRFs" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:206 +msgid "Similarly, to attach the firewall, you would use `set interfaces ethernet eth0 firewall in ipv6-name` or `et firewall zone LOCAL from WAN firewall ipv6-name`." +msgstr "Similarly, to attach the firewall, you would use `set interfaces ethernet eth0 firewall in ipv6-name` or `et firewall zone LOCAL from WAN firewall ipv6-name`." + +#: ../../configexamples/pppoe-ipv6-basic.rst:78 +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 "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." + +#: ../../configexamples/zone-policy.rst:236 +msgid "Since we have 4 zones, we need to setup the following rulesets." +msgstr "Since we have 4 zones, we need to setup the following rulesets." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:119 +msgid "Single LAN Setup" +msgstr "Single LAN Setup" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:121 +msgid "Single LAN setup where eth2 is your LAN interface. Use the Tunnelbroker Routed /64 prefix:" +msgstr "Single LAN setup where eth2 is your LAN interface. Use the Tunnelbroker Routed /64 prefix:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:179 +msgid "So, when your LAN is eth1, your DMZ is eth2, your cameras are on eth3, etc:" +msgstr "So, when your LAN is eth1, your DMZ is eth2, your cameras are on eth3, etc:" + +#: ../../configexamples/zone-policy.rst:416 +msgid "Something like:" +msgstr "Something like:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "Spoke" +msgstr "Spoke" + +#: ../../configexamples/zone-policy.rst:358 +msgid "Start by setting the interface and default action for each zone." +msgstr "Start by setting the interface and default action for each zone." + +#: ../../configexamples/zone-policy.rst:8 +msgid "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos instalations, and zone based firewall is no longer supported. Documentation for most of the new firewall CLI can be found in the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html>`_ chapter. The legacy firewall is still available for versions before 1.4-rolling-202308040557 and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the legacy firewall configuration commands, since this feature has been removed in earlier releases." +msgstr "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos instalations, and zone based firewall is no longer supported. Documentation for most of the new firewall CLI can be found in the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html>`_ chapter. The legacy firewall is still available for versions before 1.4-rolling-202308040557 and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the legacy firewall configuration commands, since this feature has been removed in earlier releases." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:105 +msgid "Step-1: Configuring IGP and enabling MPLS LDP" +msgstr "Step-1: Configuring IGP and enabling MPLS LDP" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:322 +msgid "Step-2: Configuring iBGP for L3VPN control-plane" +msgstr "Step-2: Configuring iBGP for L3VPN control-plane" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:407 +msgid "Step-3: Configuring L3VPN VRFs on PE nodes" +msgstr "Step-3: Configuring L3VPN VRFs on PE nodes" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:482 +msgid "Step-4: Configuring CE nodes" +msgstr "Step-4: Configuring CE nodes" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:545 +msgid "Step-5: Verification" +msgstr "Step-5: Verification" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:137 +msgid "Step 1: VRF and Configurations to remote networks" +msgstr "Step 1: VRF and Configurations to remote networks" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:228 +msgid "Step 2: BGP Configuration for VRF-Lite" +msgstr "Step 2: BGP Configuration for VRF-Lite" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:287 +msgid "Step 3: VPN Configuration" +msgstr "Step 3: VPN Configuration" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:422 +msgid "Step 4: End to End verification" +msgstr "Step 4: End to End verification" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:103 +msgid "Tenant networks (VRFs)" +msgstr "Tenant networks (VRFs)" + +#: ../../configexamples/ha.rst:489 +msgid "Test OSPF" +msgstr "Test OSPF" + +#: ../../configexamples/ha.rst:412 +msgid "Test WireGuard" +msgstr "Test WireGuard" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:71 +msgid "Test the result" +msgstr "Test the result" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:6 +msgid "Testdate: 2023-02-24" +msgstr "Testdate: 2023-02-24" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:6 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:6 +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:7 +msgid "Testdate: 2023-05-11" +msgstr "Testdate: 2023-05-11" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:6 +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:7 +msgid "Testdate: 2023-08-31" +msgstr "Testdate: 2023-08-31" + +#: ../../configexamples/ha.rst:276 +#: ../../configexamples/ha.rst:337 +msgid "Testing" +msgstr "Testing" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:143 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:85 +msgid "Testing and debugging" +msgstr "Testing and debugging" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:164 +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 "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." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:23 +msgid "The Lab asume a full running Active Directory on the Windows Server. Here are some PowerShell commands to quickly add a Test Active Directory." +msgstr "The Lab asume a full running Active Directory on the Windows Server. Here are some PowerShell commands to quickly add a Test Active Directory." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:15 +msgid "The Topology are consists of:" +msgstr "The Topology are consists of:" + +#: ../../configexamples/zone-policy.rst:57 +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 "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." + +#: ../../configexamples/ha.rst:30 +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 "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." + +#: ../../configexamples/ha.rst:543 +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 "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." + +#: ../../configexamples/segment-routing-isis.rst:19 +msgid "The below configuration is used as example where we keep focus on VyOS-P1/VyOS-P2/XRv-P3 which we share the settings." +msgstr "The below configuration is used as example where we keep focus on VyOS-P1/VyOS-P2/XRv-P3 which we share the settings." + +#: ../../configexamples/wan-load-balancing.rst:82 +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 "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:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:28 +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 "The example topology has 2 VyOS routers. One as The WAN Router and on as a Client, to test a single LAN setup" + +#: ../../configexamples/zone-policy.rst:133 +msgid "The first two rules are to deal with the idiosyncrasies of VyOS and iptables." +msgstr "The first two rules are to deal with the idiosyncrasies of VyOS and iptables." + +#: ../../configexamples/zone-policy.rst:182 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:40 +msgid "The following software was used in the creation of this document:" +msgstr "The following software was used in the creation of this document:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:122 +msgid "The following template configuration can be used in each remote router based in our topology." +msgstr "The following template configuration can be used in each remote router based in our topology." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:169 +msgid "The format of these addresses:" +msgstr "The format of these addresses:" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:42 +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 "The lab I built is using a VRF (called **mgmt**) to provide out-of-band SSH access to the PE (Provider Edge) routers." + +#: ../../configexamples/index.rst:30 +msgid "The next pages contains automatic full tested configuration examples." +msgstr "The next pages contains automatic full tested configuration examples." + +#: ../../configexamples/wan-load-balancing.rst:97 +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 "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." + +#: ../../configexamples/index.rst:38 +msgid "The process will do the following steps:" +msgstr "The process will do the following steps:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:16 +msgid "The scope of this document is to cover such cases in a dynamic way without the use of MPLS-LDP." +msgstr "The scope of this document is to cover such cases in a dynamic way without the use of MPLS-LDP." + +#: ../../configexamples/wan-load-balancing.rst:14 +msgid "The setup used in this example is shown in the following diagram:" +msgstr "The setup used in this example is shown in the following diagram:" + +#: ../../configexamples/ha.rst:339 +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 "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." + +#: ../../configexamples/ha.rst:267 +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 "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``." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:17 +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 "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." + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:17 +msgid "The topology have a central and a branch VyOS router and one client, to test, in each site." +msgstr "The topology have a central and a branch VyOS router and one client, to test, in each site." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:803 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:820 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:317 +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 "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." + +#: ../../configexamples/ha.rst:360 +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 "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." + +#: ../../configexamples/ha.rst:67 +msgid "These are the vlans we will be using:" +msgstr "These are the vlans we will be using:" + +#: ../../configexamples/ha.rst:48 +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 "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." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:10 +msgid "This LAB show how to uwe OpenVPN with a Active Directory authentication backend." +msgstr "This LAB show how to uwe OpenVPN with a Active Directory authentication backend." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:137 +msgid "This accomplishes a few things:" +msgstr "This accomplishes a few things:" + +#: ../../configexamples/index.rst:6 +msgid "This chapter contains various configuration examples:" +msgstr "This chapter contains various configuration examples:" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:16 +msgid "This configuration example and the requirments consists on:" +msgstr "This configuration example and the requirments consists on:" + +#: ../../configexamples/ha.rst:13 +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 "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." + +#: ../../configexamples/pppoe-ipv6-basic.rst:9 +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 "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." + +#: ../../configexamples/ha.rst:9 +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 "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." + +#: ../../configexamples/ha.rst:38 +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 "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." + +#: ../../configexamples/wan-load-balancing.rst:70 +msgid "This example uses the failover mode." +msgstr "This example uses the failover mode." + +#: ../../configexamples/segment-routing-isis.rst:112 +msgid "This gives us MPLS segment routing enabled and labels forwarding :" +msgstr "This gives us MPLS segment routing enabled and labels forwarding :" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:8 +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 "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." + +#: ../../configexamples/azure-vpn-bgp.rst:8 +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 "This guide shows an example of a route-based IKEv2 site-to-site VPN to Azure using VTI and BGP for dynamic routing updates." + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:7 +msgid "This guide shows an example policy-based IKEv2 site-to-site VPN between two VyOS routers, and firewall configiuration." +msgstr "This guide shows an example policy-based IKEv2 site-to-site VPN between two VyOS routers, and firewall configiuration." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:10 +msgid "This guide walks through the setup of https://www.tunnelbroker.net/ for an IPv6 Tunnel." +msgstr "This guide walks through the setup of https://www.tunnelbroker.net/ for an IPv6 Tunnel." + +#: ../../configexamples/ha.rst:197 +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 "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." + +#: ../../configexamples/ha.rst:232 +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 "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." + +#: ../../configexamples/zone-policy.rst:258 +msgid "This is an example of the three base rules." +msgstr "This is an example of the three base rules." + +#: ../../configexamples/ha.rst:20 +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 "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." + +#: ../../configexamples/ha.rst:391 +msgid "This is connecting back to the STATIC IP of router1, not the floating." +msgstr "This is connecting back to the STATIC IP of router1, not the floating." + +#: ../../configexamples/ha.rst:583 +msgid "This is identical, but you use the BGPPREPENDOUT route-map to advertise the route with a longer path." +msgstr "This is identical, but you use the BGPPREPENDOUT route-map to advertise the route with a longer path." + +#: ../../configexamples/ha.rst:96 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:38 +msgid "This scenario could be a nightmare applying regular routing and might need filtering in multiple interfaces." +msgstr "This scenario could be a nightmare applying regular routing and might need filtering in multiple interfaces." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:547 +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 "This section describes verification commands for MPLS/BGP/LDP protocols and L3VPN related routes as well as diagnosis and reachability checks between CE nodes." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:409 +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 "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." + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:10 +msgid "This simple structure show how to connect two offices. One remote branch and the central office." +msgstr "This simple structure show how to connect two offices. One remote branch and the central office." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:10 +msgid "This simple structure shows how to configure a DHCP Relay over a GRE Bridge interface." +msgstr "This simple structure shows how to configure a DHCP Relay over a GRE Bridge interface." + +#: ../../configexamples/ha.rst:531 +msgid "This will be visible in 'show ip route'." +msgstr "This will be visible in 'show ip route'." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:112 +msgid "Thus you can easily match it to one of the devices/networks below." +msgstr "Thus you can easily match it to one of the devices/networks below." + +#: ../../configexamples/pppoe-ipv6-basic.rst:14 +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 "To achieve this, your ISP is required to support DHCPv6-PD. If you're not sure, please contact your ISP for more information." + +#: ../../configexamples/zone-policy.rst:144 +msgid "To add logging to the default rule, do:" +msgstr "To add logging to the default rule, do:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:54 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:31 +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 "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:" + +#: ../../configexamples/pppoe-ipv6-basic.rst:84 +msgid "To have basic protection while keeping IPv6 network functional, we need to:" +msgstr "To have basic protection while keeping IPv6 network functional, we need to:" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:68 +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 "To reach the network, a route must be set on each VyOS host. In this structure, a static interface route will fit the requirements." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:15 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:52 +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:15 +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:26 +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:72 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:55 +msgid "Topology" +msgstr "Topology" + +#: ../../configexamples/zone-policy.rst:95 +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 "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." + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:31 +msgid "Transport:" +msgstr "Transport:" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:5 +msgid "Tunnelbroker.net (IPv6)" +msgstr "Tunnelbroker.net (IPv6)" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:None +msgid "Tunnelbroker topology image" +msgstr "Tunnelbroker topology image" + +#: ../../configexamples/policy-based-ipsec-and-firewall.rst:18 +msgid "Two VyOS routers with public IP address." +msgstr "Two VyOS routers with public IP address." + +#: ../../configexamples/wan-load-balancing.rst:105 +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 "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." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:113 +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 "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." + +#: ../../configexamples/qos.rst:16 +msgid "Using the general schema for example:" +msgstr "Using the general schema for example:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:783 +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 "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):" + +#: ../../configexamples/ha.rst:143 +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 "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." + +#: ../../configexamples/ha.rst:65 +msgid "VLANs" +msgstr "VLANs" + +#: ../../configexamples/ha.rst:120 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 +msgid "VRF" +msgstr "VRF" + +#: ../../configexamples/ha.rst:189 +msgid "VRRP Configuration" +msgstr "VRRP Configuration" + +#: ../../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 +msgid "Verification" +msgstr "Verification" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:43 +msgid "Version: 1.4-rolling-202110310317" +msgstr "Version: 1.4-rolling-202110310317" + +#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:7 +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:7 +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:8 +msgid "Version: 1.4-rolling-202305100734" +msgstr "Version: 1.4-rolling-202305100734" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:7 +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:8 +msgid "Version: 1.4-rolling-202308240020" +msgstr "Version: 1.4-rolling-202308240020" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:7 +msgid "Version: vyos-1.4-rolling-202302150317" +msgstr "Version: vyos-1.4-rolling-202302150317" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:1025 +msgid "VyOS-CE-HUB -------> VyOS-CE1-SPOKE" +msgstr "VyOS-CE-HUB -------> VyOS-CE1-SPOKE" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:1026 +msgid "VyOS-CE-HUB -------> VyOS-CE2-SPOKE" +msgstr "VyOS-CE-HUB -------> VyOS-CE2-SPOKE" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:507 +msgid "VyOS-CE1-HUB:" +msgstr "VyOS-CE1-HUB:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:490 +msgid "VyOS-CE1-SPOKE:" +msgstr "VyOS-CE1-SPOKE:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:987 +msgid "VyOS-CE1-SPOKE -----> VyOS-CE-HUB" +msgstr "VyOS-CE1-SPOKE -----> VyOS-CE-HUB" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:525 +msgid "VyOS-CE2-SPOKE:" +msgstr "VyOS-CE2-SPOKE:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:1085 +msgid "VyOS-CE2-SPOKE -------> VyOS-CE-HUB" +msgstr "VyOS-CE2-SPOKE -------> VyOS-CE-HUB" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:112 +#: ../../configexamples/segment-routing-isis.rst:26 +msgid "VyOS-P1:" +msgstr "VyOS-P1:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:142 +#: ../../configexamples/segment-routing-isis.rst:90 +msgid "VyOS-P2:" +msgstr "VyOS-P2:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:168 +msgid "VyOS-P3:" +msgstr "VyOS-P3:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:194 +msgid "VyOS-P4:" +msgstr "VyOS-P4:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 +msgid "VyOS-PE1" +msgstr "VyOS-PE1" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:224 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:362 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:413 +msgid "VyOS-PE1:" +msgstr "VyOS-PE1:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 +msgid "VyOS-PE2" +msgstr "VyOS-PE2" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:241 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:376 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:435 +msgid "VyOS-PE2:" +msgstr "VyOS-PE2:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 +msgid "VyOS-PE3" +msgstr "VyOS-PE3" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:262 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:390 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:457 +msgid "VyOS-PE3:" +msgstr "VyOS-PE3:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 +msgid "VyOS-RR1/RR2" +msgstr "VyOS-RR1/RR2" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:279 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:328 +msgid "VyOS-RR1:" +msgstr "VyOS-RR1:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:299 +#: ../../configexamples/l3vpn-hub-and-spoke.rst:345 +msgid "VyOS-RR2:" +msgstr "VyOS-RR2:" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:38 +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 "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." + +#: ../../configexamples/zone-policy.rst:42 +msgid "VyOS acts as DHCP, DNS forwarder, NAT, router and firewall." +msgstr "VyOS acts as DHCP, DNS forwarder, NAT, router and firewall." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:15 +msgid "VyOS as Client" +msgstr "VyOS as Client" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:14 +msgid "VyOS as a OpenVPN Server" +msgstr "VyOS as a OpenVPN Server" + +#: ../../configexamples/segment-routing-isis.rst:148 +msgid "VyOS is able to check MSD per devices:" +msgstr "VyOS is able to check MSD per devices:" + +#: ../../configexamples/azure-vpn-bgp.rst:50 +#: ../../configexamples/azure-vpn-dual-bgp.rst:49 +msgid "Vyos ASN" +msgstr "Vyos ASN" + +#: ../../configexamples/azure-vpn-bgp.rst:56 +#: ../../configexamples/azure-vpn-dual-bgp.rst:55 +msgid "Vyos configuration" +msgstr "Vyos configuration" + +#: ../../configexamples/azure-vpn-bgp.rst:42 +#: ../../configexamples/azure-vpn-dual-bgp.rst:39 +msgid "Vyos private IP" +msgstr "Vyos private IP" + +#: ../../configexamples/azure-vpn-bgp.rst:40 +#: ../../configexamples/azure-vpn-dual-bgp.rst:37 +msgid "Vyos public IP" +msgstr "Vyos public IP" + +#: ../../configexamples/azure-vpn-bgp.rst:34 +#: ../../configexamples/azure-vpn-dual-bgp.rst:31 +msgid "WAN Interface" +msgstr "WAN Interface" + +#: ../../configexamples/wan-load-balancing.rst:8 +msgid "WAN Load Balancer examples" +msgstr "WAN Load Balancer examples" + +#: ../../configexamples/ha.rst:28 +msgid "Walkthrough suggestion" +msgstr "Walkthrough suggestion" + +#: ../../configexamples/ha.rst:55 +msgid "We are going to use 10.200.201.0/24 for an 'internal' network on VLAN201." +msgstr "We are going to use 10.200.201.0/24 for an 'internal' network on VLAN201." + +#: ../../configexamples/ha.rst:191 +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 "We are setting up VRRP so that it does NOT fail back when a machine returns into service, and it prioritizes router1 over router2." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:815 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:778 +msgid "We create a prefix-list first and add all the routes we need to." +msgstr "We create a prefix-list first and add all the routes we need to." + +#: ../../configexamples/ha.rst:300 +msgid "We explicitly exclude the primary upstream network so that BGP or OSPF traffic doesn't accidentally get NAT'ed." +msgstr "We explicitly exclude the primary upstream network so that BGP or OSPF traffic doesn't accidentally get NAT'ed." + +#: ../../configexamples/qos.rst:23 +msgid "We have four hosts on the local network 172.17.1.0/24. All hosts are labeled CS0 by default. We need to replace labels on all hosts except vpc8. We will replace the labels on the nearest router “VyOS3” using the IP addresses of the sources." +msgstr "We have four hosts on the local network 172.17.1.0/24. All hosts are labeled CS0 by default. We need to replace labels on all hosts except vpc8. We will replace the labels on the nearest router “VyOS3” using the IP addresses of the sources." + +#: ../../configexamples/zone-policy.rst:25 +msgid "We have three networks." +msgstr "We have three networks." + +#: ../../configexamples/wan-load-balancing.rst:112 +msgid "We keep the configuration from the previous example, delete rule 10 and create the two new rules as described:" +msgstr "We keep the configuration from the previous example, delete rule 10 and create the two new rules as described:" + +#: ../../configexamples/wan-load-balancing.rst:143 +msgid "We keep the configuration from the previous example, delete rule 20 and create a new rule as described:" +msgstr "We keep the configuration from the previous example, delete rule 20 and create a new rule as described:" + +#: ../../configexamples/pppoe-ipv6-basic.rst:63 +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 "We need to enable router advertisement for LAN network so that PC can receive the prefix and use SLAAC to configure the address automatically." + +#: ../../configexamples/ha.rst:419 +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 "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'." + +#: ../../configexamples/ha.rst:450 +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 "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." + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:115 +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 "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." + +#: ../../configexamples/ha.rst:364 +msgid "We use small /30's from 10.254.60/24 for the point-to-point links." +msgstr "We use small /30's from 10.254.60/24 for the point-to-point links." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:54 +msgid "We use the following network topology in this example:" +msgstr "We use the following network topology in this example:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:770 +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 "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." + +#: ../../configexamples/ha.rst:57 +msgid "When traffic is originated from the 10.200.201.0/24 network, it will be masqueraded to 203.0.113.1" +msgstr "When traffic is originated from the 10.200.201.0/24 network, it will be masqueraded to 203.0.113.1" + +#: ../../configexamples/segment-routing-isis.rst:9 +msgid "When utilizing VyOS in an environment with Cisco IOS-XR gear you can use this blue print as an initial setup to get MPLS ISIS-SR working between those two devices.The lab was build using :abbr:`EVE-NG (Emulated Virtual Environment NG)`." +msgstr "When utilizing VyOS in an environment with Cisco IOS-XR gear you can use this blue print as an initial setup to get MPLS ISIS-SR working between those two devices.The lab was build using :abbr:`EVE-NG (Emulated Virtual Environment NG)`." + +#: ../../configexamples/ha.rst:343 +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 "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." + +#: ../../configexamples/ha.rst:491 +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 "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``" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:13 +msgid "Windows Server 2019 with a running Active Directory" +msgstr "Windows Server 2019 with a running Active Directory" + +#: ../../configexamples/autotest/Wireguard/Wireguard.rst:3 +msgid "Wireguard" +msgstr "Wireguard" + +#: ../../configexamples/ha.rst:350 +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 "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." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:105 +msgid "With Tunnelbroker.net, you have two options:" +msgstr "With Tunnelbroker.net, you have two options:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:907 +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 "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" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:293 +msgid "Within the VRF we set the Route-Distinguisher (RD) and Route-Targets (RT), then we enable the export/import VPN." +msgstr "Within the VRF we set the Route-Distinguisher (RD) and Route-Targets (RT), then we enable the export/import VPN." + +#: ../../configexamples/segment-routing-isis.rst:48 +msgid "XRv-P3:" +msgstr "XRv-P3:" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:145 +msgid "You managed to come this far, now we want to see the network and routing tables in action." +msgstr "You managed to come this far, now we want to see the network and routing tables in action." + +#: ../../configexamples/ha.rst:292 +msgid "You should be able to ping to and from all the IPs you have allocated." +msgstr "You should be able to ping to and from all the IPs you have allocated." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:81 +msgid "You should now be able to ping something by IPv6 DNS name:" +msgstr "You should now be able to ping something by IPv6 DNS name:" + +#: ../../configexamples/ha.rst:511 +msgid "You should now be able to see the advertised network on the other host." +msgstr "You should now be able to see the advertised network on the other host." + +#: ../../configexamples/zone-policy.rst:388 +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 "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." + +#: ../../configexamples/zone-policy.rst:413 +msgid "You would have to add a couple of rules on your wan-local ruleset to allow protocol 41 in." +msgstr "You would have to add a couple of rules on your wan-local ruleset to allow protocol 41 in." + +#: ../../configexamples/zone-policy.rst:6 +msgid "Zone-Policy example" +msgstr "Zone-Policy example" + +#: ../../configexamples/zone-policy.rst:89 +msgid "Zones Basics" +msgstr "Zones Basics" + +#: ../../configexamples/zone-policy.rst:136 +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 "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." + +#: ../../configexamples/zone-policy.rst:175 +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 "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." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:172 +msgid "`2001:470:xxxx:1::/64`: A subnet suitable for a LAN" +msgstr "`2001:470:xxxx:1::/64`: A subnet suitable for a LAN" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:173 +msgid "`2001:470:xxxx:2::/64`: Another subnet" +msgstr "`2001:470:xxxx:2::/64`: Another subnet" + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:171 +msgid "`2001:470:xxxx::/48`: The whole subnet. xxxx should come from Tunnelbroker." +msgstr "`2001:470:xxxx::/48`: The whole subnet. xxxx should come from Tunnelbroker." + +#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:174 +msgid "`2001:470:xxxx:ffff:/64`: The last usable /64 subnet." +msgstr "`2001:470:xxxx:ffff:/64`: The last usable /64 subnet." + +#: ../../configexamples/pppoe-ipv6-basic.rst:39 +msgid "``service-name`` can be an arbitrary string." +msgstr "``service-name`` can be an arbitrary string." + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:75 +msgid "after all these steps the config look like this:" +msgstr "after all these steps the config look like this:" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:62 +msgid "after this create a signed server and a client certificate" +msgstr "after this create a signed server and a client certificate" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:69 +msgid "and last the DH Key" +msgstr "and last the DH Key" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:119 +msgid "blue uses local routing table id and VNI 2000" +msgstr "blue uses local routing table id and VNI 2000" + +#: ../../configexamples/azure-vpn-bgp.rst:48 +#: ../../configexamples/azure-vpn-dual-bgp.rst:47 +msgid "ch00s3-4-s3cur3-psk" +msgstr "ch00s3-4-s3cur3-psk" + +#: ../../configexamples/ha.rst:92 +msgid "compute1 - Port 9 of each switch" +msgstr "compute1 - Port 9 of each switch" + +#: ../../configexamples/ha.rst:78 +msgid "compute1 (VMware ESXi 6.5)" +msgstr "compute1 (VMware ESXi 6.5)" + +#: ../../configexamples/ha.rst:93 +msgid "compute2 - Port 10 of each switch" +msgstr "compute2 - Port 10 of each switch" + +#: ../../configexamples/ha.rst:79 +msgid "compute2 (VMware ESXi 6.5)" +msgstr "compute2 (VMware ESXi 6.5)" + +#: ../../configexamples/ha.rst:94 +msgid "compute3 - Port 11 of each switch" +msgstr "compute3 - Port 11 of each switch" + +#: ../../configexamples/ha.rst:80 +msgid "compute3 (VMware ESXi 6.5)" +msgstr "compute3 (VMware ESXi 6.5)" + +#: ../../configexamples/index.rst:41 +msgid "configure each host in the lab" +msgstr "configure each host in the lab" + +#: ../../configexamples/index.rst:40 +msgid "create the lab on a eve-ng server" +msgstr "create the lab on a eve-ng server" + +#: ../../configexamples/index.rst:42 +msgid "do some defined tests" +msgstr "do some defined tests" + +#: ../../configexamples/azure-vpn-bgp.rst:34 +#: ../../configexamples/azure-vpn-dual-bgp.rst:31 +msgid "eth0" +msgstr "eth0" + +#: ../../configexamples/wan-load-balancing.rst:30 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 +msgid "extended community and remote label of specific destination" +msgstr "extended community and remote label of specific destination" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:56 +msgid "first the PCA" +msgstr "first the PCA" + +#: ../../configexamples/index.rst:44 +msgid "generate the documentation and include files" +msgstr "generate the documentation and include files" + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:121 +msgid "green uses local routing table id and VNI 4000" +msgstr "green uses local routing table id and VNI 4000" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 +msgid "information between PE and CE:" +msgstr "information between PE and CE:" + +#: ../../configexamples/index.rst:43 +msgid "optional do an upgrade to a higher version and do step 3 again." +msgstr "optional do an upgrade to a higher version and do step 3 again." + +#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:120 +msgid "red uses local routing table id and VNI 3000" +msgstr "red uses local routing table id and VNI 3000" + +#: ../../configexamples/ha.rst:81 +msgid "router2 (Random 1RU machine with 4 NICs)" +msgstr "router2 (Random 1RU machine with 4 NICs)" + +#: ../../configexamples/autotest/OpenVPN_with_LDAP/OpenVPN_with_LDAP.rst:102 +msgid "save the output to a file and import it in nearly all openvpn clients." +msgstr "save the output to a file and import it in nearly all openvpn clients." + +#: ../../configexamples/index.rst:45 +msgid "shutdown and destroy the lab, if there is no error" +msgstr "shutdown and destroy the lab, if there is no error" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:806 +msgid "specific VPNv4 destination including extended community and remotelabel information. This procedure is the same on all Spoke nodes:" +msgstr "specific VPNv4 destination including extended community and remotelabel information. This procedure is the same on all Spoke nodes:" + +#: ../../configexamples/ha.rst:76 +msgid "switch1 (Nexus 10gb Switch)" +msgstr "switch1 (Nexus 10gb Switch)" + +#: ../../configexamples/ha.rst:77 +msgid "switch2 (Nexus 10gb Switch)" +msgstr "switch2 (Nexus 10gb Switch)" + +#: ../../configexamples/zone-policy.rst:394 +msgid "v6 pairs would be:" +msgstr "v6 pairs would be:" + +#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:571 +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 "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." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 +msgid "within VRFs:" +msgstr "within VRFs:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:639 +msgid "“show bgp ipv4 vpn summary” for checking BGP VPNv4 neighbors:" +msgstr "“show bgp ipv4 vpn summary” for checking BGP VPNv4 neighbors:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 +msgid "“show bgp ipv4 vpn summary” for checking iBGP neighbors again" +msgstr "“show bgp ipv4 vpn summary” for checking iBGP neighbors again" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:719 +msgid "“show bgp ipv4 vpn summary” for checking iBGP neighbors against route-reflector devices:" +msgstr "“show bgp ipv4 vpn summary” for checking iBGP neighbors against route-reflector devices:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 +msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking best-path," +msgstr "“show bgp ipv4 vpn x.x.x.x/32” for checking best-path," + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:807 +msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking the best-path to the" +msgstr "“show bgp ipv4 vpn x.x.x.x/32” for checking the best-path to the" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:698 +msgid "“show bgp ipv4 vpn x.x.x.x/x” for checking best path selected for specific VPNv4 destination" +msgstr "“show bgp ipv4 vpn x.x.x.x/x” for checking best path selected for specific VPNv4 destination" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:658 +msgid "“show bgp ipv4 vpn” for checking all VPNv4 prefixes information:" +msgstr "“show bgp ipv4 vpn” for checking all VPNv4 prefixes information:" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 +msgid "“show bgp vrf BLUE_HUB summary” for checking EBGP neighbor" +msgstr "“show bgp vrf BLUE_HUB summary” for checking EBGP neighbor" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 +msgid "“show bgp vrf BLUE_SPOKE summary” for checking EBGP neighbor" +msgstr "“show bgp vrf BLUE_SPOKE summary” for checking EBGP neighbor" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 +msgid "“show bgp vrf all” for checking all the prefix learning on BGP" +msgstr "“show bgp vrf all” for checking all the prefix learning on BGP" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:851 +msgid "“show bgp vrf all” for checking all the prefixes learning on BGP" +msgstr "“show bgp vrf all” for checking all the prefixes learning on BGP" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:554 +msgid "“show ip ospf neighbor” for checking ospf relationship" +msgstr "“show ip ospf neighbor” for checking ospf relationship" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:909 +msgid "“show ip route vrf BLUE_HUB” to view the RIB in our Hub PE." +msgstr "“show ip route vrf BLUE_HUB” to view the RIB in our Hub PE." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:784 +msgid "“show ip route vrf BLUE_SPOKE” for viewing the RIB in our Spoke PE." +msgstr "“show ip route vrf BLUE_SPOKE” for viewing the RIB in our Spoke PE." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:579 +msgid "“show mpls ldp binding” for checking mpls label assignment" +msgstr "“show mpls ldp binding” for checking mpls label assignment" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:567 +msgid "“show mpls ldp neighbor “ for checking ldp neighbors" +msgstr "“show mpls ldp neighbor “ for checking ldp neighbors" diff --git a/docs/_locale/ja/configuration.pot b/docs/_locale/ja/configuration.pot new file mode 100644 index 00000000..bb68320f --- /dev/null +++ b/docs/_locale/ja/configuration.pot @@ -0,0 +1,20839 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../configuration/policy/route.rst:74 +msgid "!<h:h:h:h:h:h:h:h/x>: Match everything except the specified prefix." +msgstr "!<h:h:h:h:h:h:h:h/x>: Match everything except the specified prefix." + +#: ../../configuration/policy/route.rst:75 +msgid "!<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: Match everything except the specified range." +msgstr "!<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: Match everything except the specified range." + +#: ../../configuration/policy/route.rst:73 +msgid "!<h:h:h:h:h:h:h:h>: Match everything except the specified address." +msgstr "!<h:h:h:h:h:h:h:h>: Match everything except the specified address." + +#: ../../configuration/policy/route.rst:66 +msgid "!<x.x.x.x/x>: Match everything except the specified subnet." +msgstr "!<x.x.x.x/x>: Match everything except the specified subnet." + +#: ../../configuration/policy/route.rst:67 +msgid "!<x.x.x.x>-<x.x.x.x>: Match everything except the specified range." +msgstr "!<x.x.x.x>-<x.x.x.x>: Match everything except the specified range." + +#: ../../configuration/policy/route.rst:65 +msgid "!<x.x.x.x>: Match everything except the specified address." +msgstr "!<x.x.x.x>: Match everything except the specified address." + +#: ../../configuration/service/router-advert.rst:1 +msgid "\"Managed address configuration\" flag" +msgstr "\"Managed address configuration\" flag" + +#: ../../configuration/service/router-advert.rst:1 +msgid "\"Other configuration\" flag" +msgstr "\"Other configuration\" flag" + +#: ../../configuration/protocols/babel.rst:146 +msgid "**1-254** – interfaces with a channel number interfere with interfering interfaces and interfaces with the same channel number. **interfering** – interfering interfaces are assumed to interfere with all other channels except noninterfering channels. **noninterfering** – noninterfering interfaces are assumed to only interfere with themselves." +msgstr "**1-254** – interfaces with a channel number interfere with interfering interfaces and interfaces with the same channel number. **interfering** – interfering interfaces are assumed to interfere with all other channels except noninterfering channels. **noninterfering** – noninterfering interfaces are assumed to only interfere with themselves." + +#: ../../configuration/system/flow-accounting.rst:102 +msgid "**10** - :abbr:`IPFIX (IP Flow Information Export)` as per :rfc:`3917`" +msgstr "**10** - :abbr:`IPFIX (IP Flow Information Export)` as per :rfc:`3917`" + +#: ../../configuration/interfaces/tunnel.rst:235 +msgid "**1. Confirm IP connectivity between tunnel source-address and remote:**" +msgstr "**1. Confirm IP connectivity between tunnel source-address and remote:**" + +#: ../../configuration/interfaces/tunnel.rst:250 +msgid "**2. Confirm the link type has been set to GRE:**" +msgstr "**2. Confirm the link type has been set to GRE:**" + +#: ../../configuration/interfaces/tunnel.rst:267 +msgid "**3. Confirm IP connectivity across the tunnel:**" +msgstr "**3. Confirm IP connectivity across the tunnel:**" + +#: ../../configuration/system/flow-accounting.rst:100 +msgid "**5** - Most common version, but restricted to IPv4 flows only" +msgstr "**5** - Most common version, but restricted to IPv4 flows only" + +#: ../../configuration/system/flow-accounting.rst:101 +msgid "**9** - NetFlow version 9 (default)" +msgstr "**9** - NetFlow version 9 (default)" + +#: ../../configuration/protocols/bgp.rst:75 +msgid "**AS path length check**" +msgstr "**AS path length check**" + +#: ../../configuration/protocols/bgp.rst:106 +msgid "**Already-selected external check**" +msgstr "**Already-selected external check**" + +#: ../../configuration/trafficpolicy/index.rst:547 +#: ../../configuration/trafficpolicy/index.rst:1181 +msgid "**Applies to:** Inbound traffic." +msgstr "**Applies to:** Inbound traffic." + +#: ../../configuration/trafficpolicy/index.rst:444 +msgid "**Applies to:** Outbound Traffic." +msgstr "**Applies to:** Outbound Traffic." + +#: ../../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:1020 +msgid "**Applies to:** Outbound traffic." +msgstr "**Applies to:** Outbound traffic." + +#: ../../configuration/trafficpolicy/index.rst:32 +msgid "**Apply the traffic policy to an interface ingress or egress**." +msgstr "**Apply the traffic policy to an interface ingress or egress**." + +#: ../../configuration/interfaces/tunnel.rst:137 +msgid "**Cisco IOS Router:**" +msgstr "**Cisco IOS Router:**" + +#: ../../configuration/service/pppoe-server.rst:69 +msgid "**Client IP address via IP range definition**" +msgstr "**Client IP address via IP range definition**" + +#: ../../configuration/service/pppoe-server.rst:89 +msgid "**Client IP subnets via CIDR notation**" +msgstr "**Client IP subnets via CIDR notation**" + +#: ../../configuration/protocols/bgp.rst:120 +msgid "**Cluster-List length check**" +msgstr "**Cluster-List length check**" + +#: ../../configuration/trafficpolicy/index.rst:30 +msgid "**Create a traffic policy**." +msgstr "**Create a traffic policy**." + +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-vlan-8021ad.txt:121 +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-vlan-8021ad.txt:121 +#: ../../_include/interface-common-with-dhcp.txt:9 +#: ../../_include/interface-vlan-8021q.txt:97 +#: ../../_include/interface-vlan-8021ad.txt:121 +#: ../../configuration/interfaces/wwan.rst:53 +msgid "**DHCP(v6)**" +msgstr "**DHCP(v6)**" + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:1 +msgid "**DHCPv6 Prefix Delegation (PD)**" +msgstr "**DHCPv6 Prefix Delegation (PD)**" + +#: ../../configuration/trafficpolicy/index.rst:169 +msgid "**Ethernet (protocol, destination address or source address)**" +msgstr "**Ethernet (protocol, destination address or source address)**" + +#: ../../configuration/service/dhcp-server.rst:235 +#: ../../configuration/service/dhcp-server.rst:657 +#: ../../configuration/service/dhcp-server.rst:694 +msgid "**Example:**" +msgstr "**Example:**" + +#: ../../configuration/protocols/bgp.rst:89 +msgid "**External check**" +msgstr "**External check**" + +#: ../../configuration/trafficpolicy/index.rst:175 +msgid "**Firewall mark**" +msgstr "**Firewall mark**" + +#: ../../configuration/firewall/index.rst:41 +msgid "**For more information** of Netfilter hooks and Linux networking packet flows can be found in `Netfilter-Hooks <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_" +msgstr "**For more information** of Netfilter hooks and Linux networking packet flows can be found in `Netfilter-Hooks <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_" + +#: ../../configuration/protocols/bgp.rst:94 +msgid "**IGP cost check**" +msgstr "**IGP cost check**" + +#: ../../configuration/trafficpolicy/index.rst:171 +msgid "**IPv4 (DSCP value, maximum packet length, protocol, source address,** **destination address, source port, destination port or TCP flags)**" +msgstr "**IPv4 (DSCP value, maximum packet length, protocol, source address,** **destination address, source port, destination port or TCP flags)**" + +#: ../../configuration/trafficpolicy/index.rst:173 +msgid "**IPv6 (DSCP value, maximum payload length, protocol, source address,** **destination address, source port, destination port or TCP flags)**" +msgstr "**IPv6 (DSCP value, maximum payload length, protocol, source address,** **destination address, source port, destination port or TCP flags)**" + +#: ../../configuration/trafficpolicy/index.rst:345 +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 "**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**." + +#: ../../configuration/firewall/general-legacy.rst:9 +msgid "**Important note:** This documentation is valid only for VyOS Sagitta prior to 1.4-rolling-202308040557" +msgstr "**Important note:** This documentation is valid only for VyOS Sagitta prior to 1.4-rolling-202308040557" + +#: ../../configuration/firewall/general-legacy.rst:9 +msgid "**Important note:** This documentation is valid only for VyOS Sagitta prior to 1.4-rolling-YYYYMMDDHHmm" +msgstr "**Important note:** This documentation is valid only for VyOS Sagitta prior to 1.4-rolling-YYYYMMDDHHmm" + +#: ../../configuration/firewall/general.rst:72 +msgid "**Important note about default-actions:** If default action for any chain is not defined, then the default action is set to **accept** for that chain. Only for custom chains, the default action is set to **drop**." +msgstr "**Important note about default-actions:** If default action for any chain is not defined, then the default action is set to **accept** for that chain. Only for custom chains, the default action is set to **drop**." + +#: ../../configuration/firewall/general.rst:404 +msgid "**Important note about default-actions:** If default action for any chain is not defined, then the default action is set to **drop** for that chain." +msgstr "**Important note about default-actions:** If default action for any chain is not defined, then the default action is set to **drop** for that chain." + +#: ../../configuration/firewall/general.rst:20 +msgid "**Important note on usage of terms:** The firewall makes use of the terms `forward`, `input`, and `output` for firewall policy. More information of Netfilter hooks and Linux networking packet flows can be found in `Netfilter-Hooks <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_" +msgstr "**Important note on usage of terms:** The firewall makes use of the terms `forward`, `input`, and `output` for firewall policy. More information of Netfilter hooks and Linux networking packet flows can be found in `Netfilter-Hooks <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_" + +#: ../../configuration/firewall/general-legacy.rst:24 +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 "**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." + +#: ../../configuration/trafficpolicy/index.rst:170 +msgid "**Interface name**" +msgstr "**Interface name**" + +#: ../../configuration/interfaces/vxlan.rst:214 +msgid "**Leaf2 configuration:**" +msgstr "**Leaf2 configuration:**" + +#: ../../configuration/interfaces/vxlan.rst:239 +msgid "**Leaf3 configuration:**" +msgstr "**Leaf3 configuration:**" + +#: ../../configuration/interfaces/tunnel.rst:159 +msgid "**Linux systemd-networkd:**" +msgstr "**Linux systemd-networkd:**" + +#: ../../configuration/protocols/bgp.rst:67 +msgid "**Local preference check**" +msgstr "**Local preference check**" + +#: ../../configuration/protocols/bgp.rst:71 +msgid "**Local route check**" +msgstr "**Local route check**" + +#: ../../configuration/protocols/bgp.rst:84 +msgid "**MED check**" +msgstr "**MED check**" + +#: ../../configuration/protocols/bgp.rst:98 +msgid "**Multi-path check**" +msgstr "**Multi-path check**" + +#: ../../configuration/protocols/bgp.rst:1192 +msgid "**Node1:**" +msgstr "**Node1:**" + +#: ../../configuration/protocols/bgp.rst:1220 +msgid "**Node2:**" +msgstr "**Node2:**" + +#: ../../configuration/protocols/ospf.rst:840 +#: ../../configuration/protocols/ospf.rst:913 +#: ../../configuration/protocols/ospf.rst:985 +#: ../../configuration/protocols/ospf.rst:1348 +#: ../../configuration/protocols/segment-routing.rst:281 +msgid "**Node 1**" +msgstr "**Node 1**" + +#: ../../configuration/protocols/babel.rst:192 +#: ../../configuration/protocols/bgp.rst:1102 +#: ../../configuration/protocols/bgp.rst:1129 +#: ../../configuration/protocols/bgp.rst:1147 +#: ../../configuration/protocols/bgp.rst:1175 +#: ../../configuration/protocols/isis.rst:313 +#: ../../configuration/protocols/isis.rst:388 +#: ../../configuration/protocols/isis.rst:429 +#: ../../configuration/protocols/isis.rst:467 +#: ../../configuration/protocols/ospf.rst:948 +#: ../../configuration/protocols/ospf.rst:1318 +#: ../../configuration/protocols/rip.rst:243 +#: ../../configuration/protocols/segment-routing.rst:195 +msgid "**Node 1:**" +msgstr "**Node 1:**" + +#: ../../configuration/protocols/ospf.rst:850 +#: ../../configuration/protocols/ospf.rst:930 +#: ../../configuration/protocols/ospf.rst:1001 +#: ../../configuration/protocols/ospf.rst:1363 +#: ../../configuration/protocols/segment-routing.rst:296 +msgid "**Node 2**" +msgstr "**Node 2**" + +#: ../../configuration/protocols/babel.rst:202 +#: ../../configuration/protocols/bgp.rst:1113 +#: ../../configuration/protocols/bgp.rst:1135 +#: ../../configuration/protocols/bgp.rst:1159 +#: ../../configuration/protocols/bgp.rst:1181 +#: ../../configuration/protocols/isis.rst:324 +#: ../../configuration/protocols/isis.rst:404 +#: ../../configuration/protocols/isis.rst:483 +#: ../../configuration/protocols/ospf.rst:1327 +#: ../../configuration/protocols/rip.rst:251 +#: ../../configuration/protocols/segment-routing.rst:211 +msgid "**Node 2:**" +msgstr "**Node 2:**" + +#: ../../configuration/policy/examples.rst:136 +msgid "**OPTIONAL:** Exclude Inter-VLAN traffic (between VLAN10 and VLAN11) from PBR" +msgstr "**OPTIONAL:** Exclude Inter-VLAN traffic (between VLAN10 and VLAN11) from PBR" + +#: ../../configuration/protocols/ospf.rst:731 +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 "**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." + +#: ../../configuration/protocols/failover.rst:65 +msgid "**One gateway:**" +msgstr "**One gateway:**" + +#: ../../configuration/protocols/bgp.rst:79 +msgid "**Origin check**" +msgstr "**Origin check**" + +#: ../../configuration/protocols/bgp.rst:125 +msgid "**Peer address**" +msgstr "**Peer address**" + +#: ../../configuration/policy/examples.rst:5 +msgid "**Policy definition:**" +msgstr "**Policy definition:**" + +#: ../../configuration/service/dhcp-server.rst:450 +msgid "**Primary**" +msgstr "**Primary**" + +#: ../../configuration/trafficpolicy/index.rst:443 +msgid "**Queueing discipline** Fair/Flow Queue CoDel." +msgstr "**Queueing discipline** Fair/Flow Queue CoDel." + +#: ../../configuration/trafficpolicy/index.rst:960 +msgid "**Queueing discipline:** Deficit Round Robin." +msgstr "**Queueing discipline:** Deficit Round Robin." + +#: ../../configuration/trafficpolicy/index.rst:766 +msgid "**Queueing discipline:** Generalized Random Early Drop." +msgstr "**Queueing discipline:** Generalized Random Early Drop." + +#: ../../configuration/trafficpolicy/index.rst:1019 +msgid "**Queueing discipline:** Hierarchical Token Bucket." +msgstr "**Queueing discipline:** Hierarchical Token Bucket." + +#: ../../configuration/trafficpolicy/index.rst:546 +msgid "**Queueing discipline:** Ingress policer." +msgstr "**Queueing discipline:** Ingress policer." + +#: ../../configuration/trafficpolicy/index.rst:354 +msgid "**Queueing discipline:** PFIFO (Packet First In First Out)." +msgstr "**Queueing discipline:** PFIFO (Packet First In First Out)." + +#: ../../configuration/trafficpolicy/index.rst:690 +msgid "**Queueing discipline:** PRIO." +msgstr "**Queueing discipline:** PRIO." + +#: ../../configuration/trafficpolicy/index.rst:386 +msgid "**Queueing discipline:** SFQ (Stochastic Fairness Queuing)." +msgstr "**Queueing discipline:** SFQ (Stochastic Fairness Queuing)." + +#: ../../configuration/trafficpolicy/index.rst:915 +msgid "**Queueing discipline:** Tocken Bucket Filter." +msgstr "**Queueing discipline:** Tocken Bucket Filter." + +#: ../../configuration/trafficpolicy/index.rst:621 +msgid "**Queueing discipline:** netem (Network Emulator) + TBF (Token Bucket Filter)." +msgstr "**Queueing discipline:** netem (Network Emulator) + TBF (Token Bucket Filter)." + +#: ../../configuration/interfaces/bonding.rst:407 +#: ../../configuration/interfaces/macsec.rst:159 +msgid "**R1**" +msgstr "**R1**" + +#: ../../configuration/interfaces/macsec.rst:215 +msgid "**R1 Static Key**" +msgstr "**R1 Static Key**" + +#: ../../configuration/interfaces/bonding.rst:425 +#: ../../configuration/interfaces/macsec.rst:171 +msgid "**R2**" +msgstr "**R2**" + +#: ../../configuration/interfaces/macsec.rst:228 +msgid "**R2 Static Key**" +msgstr "**R2 Static Key**" + +#: ../../configuration/service/pppoe-server.rst:104 +msgid "**RADIUS based IP pools (Framed-IP-Address)**" +msgstr "**RADIUS based IP pools (Framed-IP-Address)**" + +#: ../../configuration/service/pppoe-server.rst:128 +msgid "**RADIUS sessions management DM/CoA**" +msgstr "**RADIUS sessions management DM/CoA**" + +#: ../../configuration/protocols/bgp.rst:113 +msgid "**Router-ID check**" +msgstr "**Router-ID check**" + +#: ../../configuration/protocols/igmp.rst:46 +msgid "**Router 1**" +msgstr "**Router 1**" + +#: ../../configuration/protocols/igmp.rst:74 +msgid "**Router 2**" +msgstr "**Router 2**" + +#: ../../configuration/protocols/igmp.rst:59 +msgid "**Router 3**" +msgstr "**Router 3**" + +#: ../../configuration/policy/examples.rst:36 +msgid "**Routes learned after routing policy applied:**" +msgstr "**Routes learned after routing policy applied:**" + +#: ../../configuration/policy/examples.rst:21 +msgid "**Routes learned before routing policy applied:**" +msgstr "**Routes learned before routing policy applied:**" + +#: ../../configuration/interfaces/bonding.rst:443 +msgid "**SW1**" +msgstr "**SW1**" + +#: ../../configuration/interfaces/bonding.rst:474 +msgid "**SW2**" +msgstr "**SW2**" + +#: ../../configuration/service/dhcp-server.rst:459 +msgid "**Secondary**" +msgstr "**Secondary**" + +#: ../../configuration/vpn/ipsec.rst:261 +msgid "**Setting up IPSec**" +msgstr "**Setting up IPSec**" + +#: ../../configuration/vpn/ipsec.rst:237 +msgid "**Setting up the GRE tunnel**" +msgstr "**Setting up the GRE tunnel**" + +#: ../../configuration/interfaces/vxlan.rst:191 +msgid "**Spine1 Configuration:**" +msgstr "**Spine1 Configuration:**" + +#: ../../configuration/protocols/ospf.rst:1378 +msgid "**Status**" +msgstr "**Status**" + +#: ../../configuration/protocols/ospf.rst:1336 +msgid "**To see the redistributed routes:**" +msgstr "**To see the redistributed routes:**" + +#: ../../configuration/protocols/failover.rst:85 +msgid "**Two gateways and different metrics:**" +msgstr "**Two gateways and different metrics:**" + +#: ../../configuration/trafficpolicy/index.rst:176 +msgid "**VLAN ID**" +msgstr "**VLAN ID**" + +#: ../../configuration/interfaces/tunnel.rst:128 +#: ../../configuration/interfaces/tunnel.rst:149 +msgid "**VyOS Router:**" +msgstr "**VyOS Router:**" + +#: ../../configuration/protocols/bgp.rst:63 +msgid "**Weight check**" +msgstr "**Weight check**" + +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +#: ../../_include/interface-dhcp-options.txt:69 +msgid "**address** can be specified multiple times, e.g. 192.168.100.1 and/or 192.168.100.0/24" +msgstr "**address** can be specified multiple times, e.g. 192.168.100.1 and/or 192.168.100.0/24" + +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address.txt:6 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:7 +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 "**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" + +#: ../../configuration/container/index.rst:38 +msgid "**allow-host-networks** cannot be used with **network**" +msgstr "**allow-host-networks** cannot be used with **network**" + +#: ../../configuration/container/index.rst:102 +msgid "**always**: Restart containers when they exit, regardless of status, retrying indefinitely" +msgstr "**always**: Restart containers when they exit, regardless of status, retrying indefinitely" + +#: ../../configuration/service/dhcp-relay.rst:71 +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 "**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." + +#: ../../configuration/system/flow-accounting.rst:32 +msgid "**application**: analyzes received flow data in the context of intrusion detection or traffic profiling, for example" +msgstr "**application**: analyzes received flow data in the context of intrusion detection or traffic profiling, for example" + +#: ../../configuration/protocols/babel.rst:69 +msgid "**auto** – automatically determines the interface type. **wired** – enables optimisations for wired interfaces. **wireless** – disables a number of optimisations that are only correct on wired interfaces. Specifying wireless is always correct, but may cause slower convergence and extra routing traffic." +msgstr "**auto** – automatically determines the interface type. **wired** – enables optimisations for wired interfaces. **wireless** – disables a number of optimisations that are only correct on wired interfaces. Specifying wireless is always correct, but may cause slower convergence and extra routing traffic." + +#: ../../configuration/protocols/ospf.rst:435 +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 "**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." + +#: ../../configuration/protocols/ospf.rst:1175 +msgid "**broadcast** – broadcast IP addresses distribution. **point-to-point** – address distribution in point-to-point networks." +msgstr "**broadcast** – broadcast IP addresses distribution. **point-to-point** – address distribution in point-to-point networks." + +#: ../../configuration/protocols/ospf.rst:121 +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 "**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." + +#: ../../configuration/system/flow-accounting.rst:30 +msgid "**collector**: responsible for reception, storage and pre-processing of flow data received from a flow exporter" +msgstr "**collector**: responsible for reception, storage and pre-processing of flow data received from a flow exporter" + +#: ../../configuration/protocols/ospf.rst:329 +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 "**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." + +#: ../../configuration/protocols/babel.rst:82 +msgid "**default** – enable split-horizon on wired interfaces, and disable split-horizon on wireless interfaces. **enable** – enable split-horizon on this interfaces. **disable** – disable split-horizon on this interfaces." +msgstr "**default** – enable split-horizon on wired interfaces, and disable split-horizon on wireless interfaces. **enable** – enable split-horizon on this interfaces. **disable** – disable split-horizon on this interfaces." + +#: ../../configuration/vpn/sstp.rst:188 +msgid "**deny** - deny mppe" +msgstr "**deny** - deny mppe" + +#: ../../configuration/nat/nat44.rst:201 +msgid "**destination** - specify which packets the translation will be applied to, only based on the destination address and/or port number configured." +msgstr "**destination** - specify which packets the translation will be applied to, only based on the destination address and/or port number configured." + +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:9 +msgid "**dhcp** interface address is received by DHCP from a DHCP server on this segment." +msgstr "**dhcp** interface address is received by DHCP from a DHCP server on this segment." + +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +#: ../../_include/interface-address-with-dhcp.txt:11 +msgid "**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on this segment." +msgstr "**dhcpv6** interface address is received by DHCPv6 from a DHCPv6 server on this segment." + +#: ../../configuration/service/dhcp-relay.rst:75 +msgid "**discard:** Received packets which already contain relay information will be discarded." +msgstr "**discard:** Received packets which already contain relay information will be discarded." + +#: ../../configuration/protocols/igmp.rst:195 +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 "**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." + +#: ../../configuration/system/flow-accounting.rst:28 +msgid "**exporter**: aggregates packets into flows and exports flow records towards one or more flow collectors" +msgstr "**exporter**: aggregates packets into flows and exports flow records towards one or more flow collectors" + +#: ../../configuration/firewall/general-legacy.rst:51 +msgid "**firewall all-ping** affects only to LOCAL and it always behaves in the most restrictive way" +msgstr "**firewall all-ping** affects only to LOCAL and it always behaves in the most restrictive way" + +#: ../../configuration/firewall/general.rst:99 +msgid "**firewall global-options all-ping** affects only to LOCAL and it always behaves in the most restrictive way" +msgstr "**firewall global-options all-ping** affects only to LOCAL and it always behaves in the most restrictive way" + +#: ../../configuration/service/dhcp-relay.rst:78 +msgid "**forward:** All packets are forwarded, relay information already present will be ignored." +msgstr "**forward:** All packets are forwarded, relay information already present will be ignored." + +#: ../../configuration/nat/nat44.rst:159 +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 "**inbound-interface** - applicable only to :ref:`destination-nat`. It configures the interface which is used for the inside traffic the translation rule applies to." + +#: ../../configuration/interfaces/bonding.rst:161 +msgid "**layer2** - Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is" +msgstr "**layer2** - Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is" + +#: ../../configuration/interfaces/bonding.rst:174 +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 "**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:" + +#: ../../configuration/interfaces/bonding.rst:200 +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 "**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." + +#: ../../configuration/vpn/site2site_ipsec.rst:288 +msgid "**left**" +msgstr "**left**" + +#: ../../configuration/protocols/isis.rst:87 +msgid "**level-1** - Act as a station (Level 1) router only." +msgstr "**level-1** - Act as a station (Level 1) router only." + +#: ../../configuration/protocols/isis.rst:153 +msgid "**level-1** - Level-1 only adjacencies are formed." +msgstr "**level-1** - Level-1 only adjacencies are formed." + +#: ../../configuration/protocols/isis.rst:88 +msgid "**level-1-2** - Act as a station (Level 1) router and area (Level 2) router." +msgstr "**level-1-2** - Act as a station (Level 1) router and area (Level 2) router." + +#: ../../configuration/protocols/isis.rst:154 +msgid "**level-1-2** - Level-1-2 adjacencies are formed" +msgstr "**level-1-2** - Level-1-2 adjacencies are formed" + +#: ../../configuration/protocols/isis.rst:89 +msgid "**level-2-only** - Act as an area (Level 2) router only." +msgstr "**level-2-only** - Act as an area (Level 2) router only." + +#: ../../configuration/protocols/isis.rst:155 +msgid "**level-2-only** - Level-2 only adjacencies are formed" +msgstr "**level-2-only** - Level-2 only adjacencies are formed" + +#: ../../configuration/vpn/sstp.rst:105 +msgid "**local**: All authentication queries are handled locally." +msgstr "**local**: All authentication queries are handled locally." + +#: ../../configuration/interfaces/wireguard.rst:140 +msgid "**local side - commands**" +msgstr "**local side - commands**" + +#: ../../configuration/service/dns.rst:83 +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 "**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." + +#: ../../configuration/protocols/isis.rst:100 +msgid "**narrow** - Use old style of TLVs with narrow metric." +msgstr "**narrow** - Use old style of TLVs with narrow metric." + +#: ../../configuration/container/index.rst:119 +msgid "**net-admin**: Network operations (interface, firewall, routing tables)" +msgstr "**net-admin**: Network operations (interface, firewall, routing tables)" + +#: ../../configuration/container/index.rst:120 +msgid "**net-bind-service**: Bind a socket to privileged ports (port numbers less than 1024)" +msgstr "**net-bind-service**: Bind a socket to privileged ports (port numbers less than 1024)" + +#: ../../configuration/container/index.rst:121 +msgid "**net-raw**: Permission to create raw network sockets" +msgstr "**net-raw**: Permission to create raw network sockets" + +#: ../../configuration/container/index.rst:100 +msgid "**no**: Do not restart containers on exit" +msgstr "**no**: Do not restart containers on exit" + +#: ../../configuration/service/dns.rst:66 +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 "**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." + +#: ../../configuration/container/index.rst:101 +msgid "**on-failure**: Restart containers when they exit with a non-zero exit code, retrying indefinitely (default)" +msgstr "**on-failure**: Restart containers when they exit with a non-zero exit code, retrying indefinitely (default)" + +#: ../../configuration/nat/nat44.rst:149 +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 "**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." + +#: ../../configuration/vpn/sstp.rst:187 +msgid "**prefer** - ask client for mppe, if it rejects don't fail" +msgstr "**prefer** - ask client for mppe, if it rejects don't fail" + +#: ../../configuration/service/dns.rst:77 +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 "**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." + +#: ../../configuration/service/dns.rst:70 +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 "**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." + +#: ../../configuration/nat/nat44.rst:169 +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 "**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." + +#: ../../configuration/vpn/sstp.rst:103 +msgid "**radius**: All authentication queries are handled by a configured RADIUS server." +msgstr "**radius**: All authentication queries are handled by a configured RADIUS server." + +#: ../../configuration/interfaces/wireguard.rst:190 +msgid "**remote side - commands**" +msgstr "**remote side - commands**" + +#: ../../configuration/service/dhcp-relay.rst:81 +msgid "**replace:** Relay information already present in a packet is stripped and replaced with the router's own relay information set." +msgstr "**replace:** Relay information already present in a packet is stripped and replaced with the router's own relay information set." + +#: ../../configuration/vpn/sstp.rst:186 +msgid "**require** - ask client for mppe, if it rejects drop connection" +msgstr "**require** - ask client for mppe, if it rejects drop connection" + +#: ../../configuration/vpn/site2site_ipsec.rst:319 +msgid "**right**" +msgstr "**right**" + +#: ../../configuration/container/index.rst:122 +msgid "**setpcap**: Capability sets (from bounded or inherited set)" +msgstr "**setpcap**: Capability sets (from bounded or inherited set)" + +#: ../../configuration/nat/nat44.rst:183 +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 "**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." + +#: ../../configuration/container/index.rst:123 +msgid "**sys-admin**: Administation operations (quotactl, mount, sethostname, setdomainame)" +msgstr "**sys-admin**: Administation operations (quotactl, mount, sethostname, setdomainame)" + +#: ../../configuration/container/index.rst:124 +msgid "**sys-time**: Permission to set system clock" +msgstr "**sys-time**: Permission to set system clock" + +#: ../../configuration/protocols/isis.rst:101 +msgid "**transition** - Send and accept both styles of TLVs during transition." +msgstr "**transition** - Send and accept both styles of TLVs during transition." + +#: ../../configuration/protocols/igmp.rst:191 +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 "**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." + +#: ../../configuration/service/dns.rst:90 +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 "**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." + +#: ../../configuration/protocols/isis.rst:102 +msgid "**wide** - Use new style of TLVs to carry wider metric." +msgstr "**wide** - Use new style of TLVs to carry wider metric." + +#: ../../configuration/protocols/bgp.rst:143 +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 "*bgpd* supports Multiprotocol Extension for BGP. So if a remote peer supports the protocol, *bgpd* can exchange IPv6 and/or multicast routing information." + +#: ../../configuration/system/syslog.rst:112 +#: ../../configuration/system/syslog.rst:171 +#: ../../configuration/trafficpolicy/index.rst:267 +#: ../../configuration/trafficpolicy/index.rst:803 +#: ../../configuration/trafficpolicy/index.rst:878 +msgid "0" +msgstr "0" + +#: ../../configuration/trafficpolicy/index.rst:267 +msgid "000000" +msgstr "000000" + +#: ../../configuration/trafficpolicy/index.rst:269 +msgid "001010" +msgstr "001010" + +#: ../../configuration/trafficpolicy/index.rst:271 +msgid "001100" +msgstr "001100" + +#: ../../configuration/trafficpolicy/index.rst:273 +msgid "001110" +msgstr "001110" + +#: ../../configuration/trafficpolicy/index.rst:275 +msgid "010010" +msgstr "010010" + +#: ../../configuration/trafficpolicy/index.rst:277 +msgid "010100" +msgstr "010100" + +#: ../../configuration/trafficpolicy/index.rst:279 +msgid "010110" +msgstr "010110" + +#: ../../configuration/trafficpolicy/index.rst:281 +msgid "011010" +msgstr "011010" + +#: ../../configuration/trafficpolicy/index.rst:283 +msgid "011100" +msgstr "011100" + +#: ../../configuration/trafficpolicy/index.rst:285 +msgid "011110" +msgstr "011110" + +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +#: ../../_include/interface-ipv6.txt:79 +msgid "0: Disable DAD" +msgstr "0: Disable DAD" + +#: ../../configuration/highavailability/index.rst:267 +msgid "0 if not defined, which means no refreshing." +msgstr "0 if not defined, which means no refreshing." + +#: ../../configuration/highavailability/index.rst:249 +msgid "0 if not defined." +msgstr "0 if not defined." + +#: ../../configuration/service/dhcp-server.rst:270 +#: ../../configuration/system/syslog.rst:114 +#: ../../configuration/system/syslog.rst:173 +#: ../../configuration/trafficpolicy/index.rst:801 +#: ../../configuration/trafficpolicy/index.rst:876 +msgid "1" +msgstr "1" + +#: ../../configuration/nat/nat44.rst:588 +msgid "1-to-1 NAT" +msgstr "1-to-1 NAT" + +#: ../../configuration/system/syslog.rst:132 +#: ../../configuration/trafficpolicy/index.rst:269 +#: ../../configuration/trafficpolicy/index.rst:876 +msgid "10" +msgstr "10" + +#: ../../configuration/interfaces/ethernet.rst:51 +msgid "100000 - 100 GBit/s" +msgstr "100000 - 100 GBit/s" + +#: ../../configuration/interfaces/ethernet.rst:47 +msgid "10000 - 10 GBit/s" +msgstr "10000 - 10 GBit/s" + +#: ../../configuration/trafficpolicy/index.rst:287 +msgid "100010" +msgstr "100010" + +#: ../../configuration/interfaces/ethernet.rst:44 +msgid "1000 - 1 GBit/s" +msgstr "1000 - 1 GBit/s" + +#: ../../configuration/trafficpolicy/index.rst:289 +msgid "100100" +msgstr "100100" + +#: ../../configuration/trafficpolicy/index.rst:291 +msgid "100110" +msgstr "100110" + +#: ../../configuration/interfaces/ethernet.rst:43 +msgid "100 - 100 MBit/s" +msgstr "100 - 100 MBit/s" + +#: ../../configuration/trafficpolicy/index.rst:265 +msgid "101110" +msgstr "101110" + +#: ../../configuration/nat/nat44.rst:38 +msgid "10.0.0.0 to 10.255.255.255 (CIDR: 10.0.0.0/8)" +msgstr "10.0.0.0 to 10.255.255.255 (CIDR: 10.0.0.0/8)" + +#: ../../configuration/interfaces/ethernet.rst:42 +msgid "10 - 10 MBit/s" +msgstr "10 - 10 MBit/s" + +#: ../../configuration/system/syslog.rst:134 +#: ../../configuration/trafficpolicy/index.rst:874 +msgid "11" +msgstr "11" + +#: ../../configuration/service/dhcp-server.rst:352 +msgid "119" +msgstr "119" + +#: ../../configuration/system/syslog.rst:136 +#: ../../configuration/trafficpolicy/index.rst:271 +#: ../../configuration/trafficpolicy/index.rst:872 +msgid "12" +msgstr "12" + +#: ../../configuration/service/dhcp-server.rst:357 +msgid "121, 249" +msgstr "121, 249" + +#: ../../configuration/service/dhcp-server.rst:337 +#: ../../configuration/system/syslog.rst:138 +#: ../../configuration/trafficpolicy/index.rst:870 +msgid "13" +msgstr "13" + +#: ../../configuration/system/syslog.rst:140 +#: ../../configuration/trafficpolicy/index.rst:273 +#: ../../configuration/trafficpolicy/index.rst:868 +msgid "14" +msgstr "14" + +#: ../../configuration/service/dhcp-server.rst:297 +#: ../../configuration/system/syslog.rst:142 +#: ../../configuration/trafficpolicy/index.rst:866 +msgid "15" +msgstr "15" + +#: ../../configuration/system/syslog.rst:144 +#: ../../configuration/trafficpolicy/index.rst:864 +msgid "16" +msgstr "16" + +#: ../../configuration/system/syslog.rst:146 +msgid "17" +msgstr "17" + +#: ../../configuration/nat/nat44.rst:39 +msgid "172.16.0.0 to 172.31.255.255 (CIDR: 172.16.0.0/12)" +msgstr "172.16.0.0 to 172.31.255.255 (CIDR: 172.16.0.0/12)" + +#: ../../configuration/system/syslog.rst:148 +#: ../../configuration/trafficpolicy/index.rst:275 +msgid "18" +msgstr "18" + +#: ../../configuration/service/dhcp-server.rst:302 +#: ../../configuration/system/syslog.rst:150 +msgid "19" +msgstr "19" + +#: ../../configuration/nat/nat44.rst:40 +msgid "192.168.0.0 to 192.168.255.255 (CIDR: 192.168.0.0/16)" +msgstr "192.168.0.0 to 192.168.255.255 (CIDR: 192.168.0.0/16)" + +#: ../../configuration/service/eventhandler.rst:32 +msgid "1. Create an event handler" +msgstr "1. Create an event handler" + +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +#: ../../_include/interface-ipv6.txt:80 +msgid "1: Enable DAD (default)" +msgstr "1: Enable DAD (default)" + +#: ../../configuration/highavailability/index.rst:277 +msgid "1 if not defined." +msgstr "1 if not defined." + +#: ../../configuration/service/dhcp-server.rst:276 +#: ../../configuration/system/syslog.rst:116 +#: ../../configuration/system/syslog.rst:178 +#: ../../configuration/trafficpolicy/index.rst:799 +#: ../../configuration/trafficpolicy/index.rst:874 +msgid "2" +msgstr "2" + +#: ../../configuration/system/syslog.rst:152 +#: ../../configuration/trafficpolicy/index.rst:277 +msgid "20" +msgstr "20" + +#: ../../configuration/system/syslog.rst:154 +msgid "21" +msgstr "21" + +#: ../../configuration/system/syslog.rst:156 +#: ../../configuration/trafficpolicy/index.rst:279 +msgid "22" +msgstr "22" + +#: ../../configuration/system/syslog.rst:158 +msgid "23" +msgstr "23" + +#: ../../configuration/interfaces/ethernet.rst:48 +msgid "25000 - 25 GBit/s" +msgstr "25000 - 25 GBit/s" + +#: ../../configuration/interfaces/ethernet.rst:45 +msgid "2500 - 2.5 GBit/s" +msgstr "2500 - 2.5 GBit/s" + +#: ../../configuration/service/dhcp-server.rst:362 +msgid "252" +msgstr "252" + +#: ../../configuration/trafficpolicy/index.rst:281 +msgid "26" +msgstr "26" + +#: ../../configuration/trafficpolicy/index.rst:283 +msgid "28" +msgstr "28" + +#: ../../configuration/vpn/openconnect.rst:59 +msgid "2FA OTP support" +msgstr "2FA OTP support" + +#: ../../configuration/service/eventhandler.rst:40 +msgid "2. Add regex to the script" +msgstr "2. Add regex to the script" + +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +#: ../../_include/interface-ipv6.txt:81 +msgid "2: Enable DAD, and disable IPv6 operation if MAC-based duplicate link-local address has been found." +msgstr "2: Enable DAD, and disable IPv6 operation if MAC-based duplicate link-local address has been found." + +#: ../../configuration/service/dhcp-server.rst:282 +#: ../../configuration/system/syslog.rst:118 +#: ../../configuration/system/syslog.rst:181 +#: ../../configuration/trafficpolicy/index.rst:797 +#: ../../configuration/trafficpolicy/index.rst:872 +msgid "3" +msgstr "3" + +#: ../../configuration/trafficpolicy/index.rst:285 +msgid "30" +msgstr "30" + +#: ../../configuration/trafficpolicy/index.rst:287 +msgid "34" +msgstr "34" + +#: ../../configuration/trafficpolicy/index.rst:289 +msgid "36" +msgstr "36" + +#: ../../configuration/trafficpolicy/index.rst:291 +msgid "38" +msgstr "38" + +#: ../../configuration/service/eventhandler.rst:51 +msgid "3. Add a full path to the script" +msgstr "3. Add a full path to the script" + +#: ../../configuration/service/dhcp-server.rst:287 +#: ../../configuration/system/syslog.rst:120 +#: ../../configuration/system/syslog.rst:183 +#: ../../configuration/trafficpolicy/index.rst:795 +#: ../../configuration/trafficpolicy/index.rst:870 +msgid "4" +msgstr "4" + +#: ../../configuration/interfaces/ethernet.rst:49 +msgid "40000 - 40 GBit/s" +msgstr "40000 - 40 GBit/s" + +#: ../../configuration/interfaces/wireless.rst:170 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:307 +msgid "42" +msgstr "42" + +#: ../../configuration/service/dhcp-server.rst:312 +msgid "44" +msgstr "44" + +#: ../../configuration/trafficpolicy/index.rst:265 +msgid "46" +msgstr "46" + +#: ../../configuration/service/eventhandler.rst:60 +msgid "4. Add optional parameters" +msgstr "4. Add optional parameters" + +#: ../../configuration/system/syslog.rst:122 +#: ../../configuration/system/syslog.rst:185 +#: ../../configuration/trafficpolicy/index.rst:793 +#: ../../configuration/trafficpolicy/index.rst:868 +msgid "5" +msgstr "5" + +#: ../../configuration/interfaces/ethernet.rst:50 +msgid "50000 - 50 GBit/s" +msgstr "50000 - 50 GBit/s" + +#: ../../configuration/interfaces/ethernet.rst:46 +msgid "5000 - 5 GBit/s" +msgstr "5000 - 5 GBit/s" + +#: ../../configuration/service/dhcp-server.rst:317 +msgid "54" +msgstr "54" + +#: ../../configuration/highavailability/index.rst:257 +#: ../../configuration/highavailability/index.rst:288 +msgid "5 if not defined." +msgstr "5 if not defined." + +#: ../../configuration/service/dhcp-server.rst:292 +#: ../../configuration/system/syslog.rst:124 +#: ../../configuration/system/syslog.rst:189 +#: ../../configuration/trafficpolicy/index.rst:791 +#: ../../configuration/trafficpolicy/index.rst:866 +msgid "6" +msgstr "6" + +#: ../../configuration/service/dhcp-server.rst:327 +msgid "66" +msgstr "66" + +#: ../../configuration/loadbalancing/wan.rst:74 +msgid "66% of traffic is routed to eth0, eth1 gets 33% of traffic." +msgstr "66% of traffic is routed to eth0, eth1 gets 33% of traffic." + +#: ../../configuration/service/dhcp-server.rst:332 +msgid "67" +msgstr "67" + +#: ../../configuration/service/dhcp-server.rst:342 +msgid "69" +msgstr "69" + +#: ../../configuration/interfaces/tunnel.rst:81 +msgid "6in4 (SIT)" +msgstr "6in4 (SIT)" + +#: ../../configuration/interfaces/tunnel.rst:83 +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 "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`_." + +#: ../../configuration/system/syslog.rst:126 +#: ../../configuration/system/syslog.rst:191 +#: ../../configuration/trafficpolicy/index.rst:789 +#: ../../configuration/trafficpolicy/index.rst:864 +msgid "7" +msgstr "7" + +#: ../../configuration/service/dhcp-server.rst:347 +msgid "70" +msgstr "70" + +#: ../../configuration/system/syslog.rst:128 +msgid "8" +msgstr "8" + +#: ../../_include/interface-vlan-8021q.txt:21 +#: ../../_include/interface-vlan-8021q.txt:21 +#: ../../_include/interface-vlan-8021q.txt:21 +#: ../../_include/interface-vlan-8021q.txt:21 +#: ../../_include/interface-vlan-8021q.txt:21 +#: ../../_include/interface-vlan-8021q.txt:21 +msgid "802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. The term used for this is ``vif``." +msgstr "802.1q VLAN interfaces are represented as virtual sub-interfaces in VyOS. The term used for this is ``vif``." + +#: ../../configuration/system/syslog.rst:130 +#: ../../configuration/trafficpolicy/index.rst:878 +msgid "9" +msgstr "9" + +#: ../../configuration/policy/route.rst:98 +msgid "<1-65535>: Numbered port." +msgstr "<1-65535>: Numbered port." + +#: ../../configuration/policy/extcommunity-list.rst:38 +msgid "<aa:nn:nn>: Extended community list regular expression." +msgstr "<aa:nn:nn>: Extended community list regular expression." + +#: ../../configuration/policy/route.rst:71 +msgid "<h:h:h:h:h:h:h:h/x>: IPv6 prefix to match." +msgstr "<h:h:h:h:h:h:h:h/x>: IPv6 prefix to match." + +#: ../../configuration/policy/route.rst:72 +msgid "<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: IPv6 range to match." +msgstr "<h:h:h:h:h:h:h:h>-<h:h:h:h:h:h:h:h>: IPv6 range to match." + +#: ../../configuration/policy/route.rst:70 +msgid "<h:h:h:h:h:h:h:h>: IPv6 address to match." +msgstr "<h:h:h:h:h:h:h:h>: IPv6 address to match." + +#: ../../configuration/system/syslog.rst:230 +msgid "<lines>" +msgstr "<lines>" + +#: ../../configuration/interfaces/wireless.rst:251 +msgid "<number> must be from 34 - 173. For 80 MHz channels it should be channel + 6." +msgstr "<number> must be from 34 - 173. For 80 MHz channels it should be channel + 6." + +#: ../../configuration/protocols/ospf.rst:346 +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 "<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." + +#: ../../configuration/policy/route.rst:97 +msgid "<port name>: Named port (any name in /etc/services, e.g., http)." +msgstr "<port name>: Named port (any name in /etc/services, e.g., http)." + +#: ../../configuration/policy/extcommunity-list.rst:39 +msgid "<rt aa:nn:nn>: Route Target regular expression." +msgstr "<rt aa:nn:nn>: Route Target regular expression." + +#: ../../configuration/policy/extcommunity-list.rst:40 +msgid "<soo aa:nn:nn>: Site of Origin regular expression." +msgstr "<soo aa:nn:nn>: Site of Origin regular expression." + +#: ../../configuration/policy/route.rst:99 +msgid "<start>-<end>: Numbered port range (e.g., 1001-1005)." +msgstr "<start>-<end>: Numbered port range (e.g., 1001-1005)." + +#: ../../configuration/policy/route.rst:63 +msgid "<x.x.x.x/x>: Subnet to match." +msgstr "<x.x.x.x/x>: Subnet to match." + +#: ../../configuration/policy/route.rst:64 +msgid "<x.x.x.x>-<x.x.x.x>: IP range to match." +msgstr "<x.x.x.x>-<x.x.x.x>: IP range to match." + +#: ../../configuration/policy/route.rst:62 +msgid "<x.x.x.x>: IP address to match." +msgstr "<x.x.x.x>: IP address to match." + +#: ../../configuration/protocols/static.rst:150 +msgid "ARP" +msgstr "ARP" + +#: ../../configuration/firewall/general.rst:302 +#: ../../configuration/firewall/general-legacy.rst:257 +msgid "A **domain group** represents a collection of domains." +msgstr "A **domain group** represents a collection of domains." + +#: ../../configuration/firewall/general.rst:284 +#: ../../configuration/firewall/general-legacy.rst:242 +msgid "A **mac group** represents a collection of mac addresses." +msgstr "A **mac group** represents a collection of mac addresses." + +#: ../../configuration/firewall/general.rst:259 +#: ../../configuration/firewall/general-legacy.rst:217 +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 "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 `-`." + +#: ../../configuration/trafficpolicy/index.rst:84 +msgid "A *bit* is written as **bit**," +msgstr "A *bit* is written as **bit**," + +#: ../../configuration/protocols/rpki.rst:21 +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 "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`." + +#: ../../configuration/protocols/bgp.rst:929 +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 "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`" + +#: ../../configuration/interfaces/bridge.rst:9 +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 "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." + +#: ../../configuration/interfaces/tunnel.rst:108 +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 "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." + +#: ../../configuration/firewall/general-legacy.rst:749 +msgid "A Rule-Set can be applied to every interface:" +msgstr "A Rule-Set can be applied to every interface:" + +#: ../../configuration/service/dhcp-server.rst:631 +msgid "A SNTP server address can be specified for DHCPv6 clients." +msgstr "A SNTP server address can be specified for DHCPv6 clients." + +#: ../../configuration/vrf/index.rst:18 +msgid "A VRF device is created with an associated route table. Network interfaces are then enslaved to a VRF device." +msgstr "A VRF device is created with an associated route table. Network interfaces are then enslaved to a VRF device." + +#: ../../configuration/interfaces/tunnel.rst:114 +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 "A VyOS GRE tunnel can carry both IPv4 and IPv6 traffic and can also be created over either IPv4 (gre) or IPv6 (ip6gre)." + +#: ../../configuration/service/dns.rst:149 +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 "A VyOS router with two interfaces - eth0 (WAN) and eth1 (LAN) - is required to implement a split-horizon DNS configuration for example.com." + +#: ../../configuration/service/dhcp-server.rst:603 +msgid "A :abbr:`NIS (Network Information Service)` domain can be set to be used for DHCPv6 clients." +msgstr "A :abbr:`NIS (Network Information Service)` domain can be set to be used for DHCPv6 clients." + +#: ../../configuration/interfaces/tunnel.rst:121 +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 "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." + +#: ../../configuration/firewall/zone.rst:54 +msgid "A 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 "A 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`." + +#: ../../configuration/interfaces/bridge.rst:195 +#: ../../configuration/interfaces/bridge.rst:229 +msgid "A bridge named `br100`" +msgstr "A bridge named `br100`" + +#: ../../configuration/trafficpolicy/index.rst:147 +msgid "A class can have multiple match filters:" +msgstr "A class can have multiple match filters:" + +#: ../../configuration/trafficpolicy/index.rst:307 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:538 +msgid "A complete LDAP auth OpenVPN configuration could look like the following example:" +msgstr "A complete LDAP auth OpenVPN configuration could look like the following example:" + +#: ../../configuration/vpn/sstp.rst:323 +msgid "A connection attempt will be shown as:" +msgstr "A connection attempt will be shown as:" + +#: ../../configuration/interfaces/pppoe.rst:330 +msgid "A default route is automatically installed once the interface is up. To change this behavior use the ``no-default-route`` CLI option." +msgstr "A default route is automatically installed once the interface is up. To change this behavior use the ``no-default-route`` CLI option." + +#: ../../configuration/service/broadcast-relay.rst:22 +msgid "A description can be added for each and every unique relay ID. This is useful to distinguish between multiple different ports/appliactions." +msgstr "A description can be added for each and every unique relay ID. This is useful to distinguish between multiple different ports/appliactions." + +#: ../../configuration/highavailability/index.rst:78 +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 "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." + +#: ../../configuration/system/host-name.rst:34 +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 "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`." + +#: ../../configuration/nat/nat44.rst:685 +msgid "A dummy interface for the provider-assigned IP;" +msgstr "A dummy interface for the provider-assigned IP;" + +#: ../../configuration/highavailability/index.rst:426 +msgid "A firewall mark ``fwmark`` allows using multiple ports for high-availability virtual-server. It uses fwmark value." +msgstr "A firewall mark ``fwmark`` allows using multiple ports for high-availability virtual-server. It uses fwmark value." + +#: ../../configuration/interfaces/tunnel.rst:102 +msgid "A full example of a Tunnelbroker.net config can be found at :ref:`here <examples-tunnelbroker-ipv6>`." +msgstr "A full example of a Tunnelbroker.net config can be found at :ref:`here <examples-tunnelbroker-ipv6>`." + +#: ../../configuration/service/dhcp-server.rst:187 +msgid "A generic `<name>` referencing this sync service." +msgstr "A generic `<name>` referencing this sync service." + +#: ../../configuration/system/host-name.rst:18 +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 "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." + +#: ../../configuration/pki/index.rst:189 +msgid "A human readable description what this CA is about." +msgstr "A human readable description what this CA is about." + +#: ../../configuration/pki/index.rst:228 +msgid "A human readable description what this certificate is about." +msgstr "A human readable description what this certificate is about." + +#: ../../configuration/interfaces/loopback.rst:17 +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 "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." + +#: ../../configuration/service/snmp.rst:42 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:154 +msgid "A match filter can contain multiple criteria and will match traffic if all those criteria are true." +msgstr "A match filter can contain multiple criteria and will match traffic if all those criteria are true." + +#: ../../configuration/protocols/bfd.rst:138 +msgid "A monitored static route conditions the installation to the RIB on the BFD session running state: when BFD session is up the route is installed to RIB, but when the BFD session is down it is removed from the RIB." +msgstr "A monitored static route conditions the installation to the RIB on the BFD session running state: when BFD session is up the route is installed to RIB, but when the BFD session is down it is removed from the RIB." + +#: ../../configuration/service/snmp.rst:54 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:337 +msgid "A new interface becomes present ``Port-channel1``, all configuration like allowed VLAN interfaces, STP will happen here." +msgstr "A new interface becomes present ``Port-channel1``, all configuration like allowed VLAN interfaces, STP will happen here." + +#: ../../configuration/loadbalancing/wan.rst:79 +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 "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:" + +#: ../../configuration/protocols/bgp.rst:698 +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 "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." + +#: ../../configuration/interfaces/macsec.rst:44 +msgid "A physical interface is required to connect this MACsec instance to. Traffic leaving this interface will now be authenticated/encrypted." +msgstr "A physical interface is required to connect this MACsec instance to. Traffic leaving this interface will now be authenticated/encrypted." + +#: ../../configuration/nat/nat44.rst:360 +msgid "A pool of addresses can be defined by using a hyphen between two IP addresses:" +msgstr "A pool of addresses can be defined by using a hyphen between two IP addresses:" + +#: ../../configuration/firewall/general.rst:761 +#: ../../configuration/firewall/general-legacy.rst:506 +msgid "A port can be set with a port number or a name which is here defined: ``/etc/services``." +msgstr "A port can be set with a port number or a name which is here defined: ``/etc/services``." + +#: ../../configuration/service/dns.rst:115 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:134 +msgid "A received NHRP Traffic Indication will trigger the resolution and establishment of a shortcut route." +msgstr "A received NHRP Traffic Indication will trigger the resolution and establishment of a shortcut route." + +#: ../../configuration/vrf/index.rst:30 +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 "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." + +#: ../../configuration/firewall/general-legacy.rst:272 +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 "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." + +#: ../../configuration/policy/route.rst:12 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:250 +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 "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:" + +#: ../../configuration/protocols/segment-routing.rst:91 +#: ../../configuration/protocols/segment-routing.rst:169 +msgid "A segment ID that contains an IP address prefix calculated by an IGP in the service provider core network. Prefix SIDs are globally unique, this value indentify it" +msgstr "A segment ID that contains an IP address prefix calculated by an IGP in the service provider core network. Prefix SIDs are globally unique, this value indentify it" + +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +#: ../../_include/interface-disable-flow-control.txt:11 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:659 +msgid "A shared network named ``NET1`` serves subnet ``2001:db8::/64``" +msgstr "A shared network named ``NET1`` serves subnet ``2001:db8::/64``" + +#: ../../configuration/protocols/bgp.rst:1145 +msgid "A simple BGP configuration via IPv6." +msgstr "A simple BGP configuration via IPv6." + +#: ../../configuration/trafficpolicy/index.rst:769 +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 "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." + +#: ../../configuration/protocols/bgp.rst:1100 +msgid "A simple eBGP configuration:" +msgstr "A simple eBGP configuration:" + +#: ../../configuration/trafficpolicy/index.rst:1124 +msgid "A simple example of Shaper using priorities." +msgstr "A simple example of Shaper using priorities." + +#: ../../configuration/trafficpolicy/index.rst:532 +msgid "A simple example of an FQ-CoDel policy working inside a Shaper one." +msgstr "A simple example of an FQ-CoDel policy working inside a Shaper one." + +#: ../../configuration/nat/nat66.rst:28 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:19 +msgid "A station acts as a Wi-Fi client accessing the network through an available WAP" +msgstr "A station acts as a Wi-Fi client accessing the network through an available WAP" + +#: ../../configuration/highavailability/index.rst:110 +msgid "A sync group allows VRRP groups to transition together." +msgstr "A sync group allows VRRP groups to transition together." + +#: ../../configuration/protocols/ospf.rst:1316 +msgid "A typical configuration using 2 nodes." +msgstr "A typical configuration using 2 nodes." + +#: ../../configuration/nat/nat44.rst:400 +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 "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." + +#: ../../configuration/service/console-server.rst:40 +msgid "A user friendly alias for this connection. Can be used instead of the device name when connecting." +msgstr "A user friendly alias for this connection. Can be used instead of the device name when connecting." + +#: ../../configuration/service/console-server.rst:36 +msgid "A user friendly description identifying the connected peripheral." +msgstr "A user friendly description identifying the connected peripheral." + +#: ../../configuration/interfaces/bonding.rst:260 +msgid "A value of 0 disables ARP monitoring. The default value is 0." +msgstr "A value of 0 disables ARP monitoring. The default value is 0." + +#: ../../configuration/trafficpolicy/index.rst:943 +msgid "A very small buffer will soon start dropping packets." +msgstr "A very small buffer will soon start dropping packets." + +#: ../../configuration/firewall/zone.rst:33 +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 "A zone must be configured before an interface is assigned to it and an interface can be assigned to only a single zone." + +#: ../../configuration/vpn/l2tp.rst:173 +msgid "Above command will use `10.0.0.3` as source IPv4 address for all RADIUS queries on this NAS." +msgstr "Above command will use `10.0.0.3` as source IPv4 address for all RADIUS queries on this NAS." + +#: ../../configuration/system/acceleration.rst:5 +msgid "Acceleration" +msgstr "Acceleration" + +#: ../../configuration/service/console-server.rst:68 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:42 +msgid "Accept only certain protocols: You may want to replicate the state of flows depending on their layer 4 protocol." +msgstr "Accept only certain protocols: You may want to replicate the state of flows depending on their layer 4 protocol." + +#: ../../configuration/policy/access-list.rst:3 +msgid "Access List Policy" +msgstr "Access List Policy" + +#: ../../configuration/policy/access-list.rst:16 +msgid "Access Lists" +msgstr "Access Lists" + +#: ../../configuration/system/syslog.rst:173 +msgid "Action must be taken immediately - A condition that should be corrected immediately, such as a corrupted system database." +msgstr "Action must be taken immediately - A condition that should be corrected immediately, such as a corrupted system database." + +#: ../../configuration/system/option.rst:15 +msgid "Action which will be run once the ctrl-alt-del keystroke is received." +msgstr "Action which will be run once the ctrl-alt-del keystroke is received." + +#: ../../configuration/firewall/general.rst:327 +#: ../../configuration/policy/route.rst:238 +msgid "Actions" +msgstr "Actions" + +#: ../../configuration/interfaces/openvpn.rst:431 +msgid "Active Directory" +msgstr "Active Directory" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:135 +msgid "Active health check backend server" +msgstr "Active health check backend server" + +#: ../../configuration/service/dns.rst:45 +msgid "Add NTA (negative trust anchor) for this domain. This must be set if the domain does not support DNSSEC." +msgstr "Add NTA (negative trust anchor) for this domain. This must be set if the domain does not support DNSSEC." + +#: ../../configuration/interfaces/wireless.rst:105 +msgid "Add Power Constraint element to Beacon and Probe Response frames." +msgstr "Add Power Constraint element to Beacon and Probe Response frames." + +#: ../../configuration/interfaces/l2tpv3.rst:113 +msgid "Add a forwarding rule matching UDP port on your internet router." +msgstr "Add a forwarding rule matching UDP port on your internet router." + +#: ../../configuration/container/index.rst:113 +msgid "Add a host device to the container." +msgstr "Add a host device to the container." + +#: ../../configuration/service/ssh.rst:84 +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 "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``." + +#: ../../configuration/container/index.rst:58 +msgid "Add custom environment variables. Multiple environment variables are allowed. The following commands translate to \"-e key=value\" when the container is created." +msgstr "Add custom environment variables. Multiple environment variables are allowed. The following commands translate to \"-e key=value\" when the container is created." + +#: ../../configuration/policy/examples.rst:109 +msgid "Add default routes for routing ``table 10`` and ``table 11``" +msgstr "Add default routes for routing ``table 10`` and ``table 11``" + +#: ../../configuration/policy/examples.rst:176 +msgid "Add multiple source IP in one rule with same priority" +msgstr "Add multiple source IP in one rule with same priority" + +#: ../../configuration/service/webproxy.rst:147 +msgid "Add new port to SSL-ports acl. Ports included by default in SSL-ports acl: 443" +msgstr "Add new port to SSL-ports acl. Ports included by default in SSL-ports acl: 443" + +#: ../../configuration/service/webproxy.rst:142 +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 "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" + +#: ../../configuration/policy/route-map.rst:221 +msgid "Add or replace BGP community attribute in format ``<0-65535:0-65535>`` or from well-known community list" +msgstr "Add or replace BGP community attribute in format ``<0-65535:0-65535>`` or from well-known community list" + +#: ../../configuration/policy/route-map.rst:236 +msgid "Add or replace BGP large-community attribute in format ``<0-4294967295:0-4294967295:0-4294967295>``" +msgstr "Add or replace BGP large-community attribute in format ``<0-4294967295:0-4294967295:0-4294967295>``" + +#: ../../configuration/policy/examples.rst:116 +msgid "Add policy route matching VLAN source addresses" +msgstr "Add policy route matching VLAN source addresses" + +#: ../../configuration/pki/index.rst:217 +msgid "Add public key portion for the certificate named `name` to the VyOS CLI." +msgstr "Add public key portion for the certificate named `name` to the VyOS CLI." + +#: ../../configuration/pki/index.rst:193 +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 "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." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:163 +msgid "Add the commands from Snippet in the Windows side via PowerShell. Also import the root CA cert to the Windows “Trusted Root Certification Authorities” and establish the connection." +msgstr "Add the commands from Snippet in the Windows side via PowerShell. Also import the root CA cert to the Windows “Trusted Root Certification Authorities” and establish the connection." + +#: ../../configuration/pki/index.rst:232 +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 "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." + +#: ../../configuration/pki/index.rst:174 +msgid "Add the public CA certificate for the CA named `name` to the VyOS CLI." +msgstr "Add the public CA certificate for the CA named `name` to the VyOS CLI." + +#: ../../configuration/vpn/openconnect.rst:169 +msgid "Adding a 2FA with an OTP-key" +msgstr "Adding a 2FA with an OTP-key" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:260 +msgid "Additional global parameters are set, including the maximum number connection limit of 4000 and a minimum TLS version of 1.3." +msgstr "Additional global parameters are set, including the maximum number connection limit of 4000 and a minimum TLS version of 1.3." + +#: ../../configuration/service/tftp-server.rst:35 +msgid "Additional option to run TFTP server in the :abbr:`VRF (Virtual Routing and Forwarding)` context" +msgstr "Additional option to run TFTP server in the :abbr:`VRF (Virtual Routing and Forwarding)` context" + +#: ../../configuration/interfaces/openvpn.rst:415 +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 "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." + +#: ../../configuration/nat/nat44.rst:738 +msgid "Additionally, we want to use VPNs only on our eth1 interface (the external interface in the image above)" +msgstr "Additionally, we want to use VPNs only on our eth1 interface (the external interface in the image above)" + +#: ../../configuration/protocols/bgp.rst:296 +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 "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." + +#: ../../configuration/highavailability/index.rst:59 +msgid "Address" +msgstr "Address" + +#: ../../configuration/nat/nat44.rst:219 +msgid "Address Conversion" +msgstr "Address Conversion" + +#: ../../configuration/protocols/bgp.rst:48 +msgid "Address Families" +msgstr "Address Families" + +#: ../../configuration/firewall/general.rst:192 +#: ../../configuration/firewall/general-legacy.rst:168 +msgid "Address Groups" +msgstr "Address Groups" + +#: ../../configuration/service/dhcp-server.rst:662 +msgid "Address pool shall be ``2001:db8::100`` through ``2001:db8::199``." +msgstr "Address pool shall be ``2001:db8::100`` through ``2001:db8::199``." + +#: ../../configuration/service/dhcp-server.rst:652 +msgid "Address pools" +msgstr "Address pools" + +#: ../../configuration/service/https.rst:42 +msgid "Address to listen for HTTPS requests" +msgstr "Address to listen for HTTPS requests" + +#: ../../configuration/container/index.rst:136 +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 "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." + +#: ../../configuration/protocols/bgp.rst:647 +msgid "Administrative Distance" +msgstr "Administrative Distance" + +#: ../../configuration/nat/nat44.rst:289 +msgid "Advanced configuration can be used in order to apply source or destination NAT, and within a single rule, be able to define multiple translated addresses, so NAT balances the translations among them." +msgstr "Advanced configuration can be used in order to apply source or destination NAT, and within a single rule, be able to define multiple translated addresses, so NAT balances the translations among them." + +#: ../../configuration/interfaces/openvpn.rst:16 +msgid "Advantages of OpenVPN are:" +msgstr "Advantages of OpenVPN are:" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Advertise DNS server per https://tools.ietf.org/html/rfc6106" +msgstr "Advertise DNS server per https://tools.ietf.org/html/rfc6106" + +#: ../../configuration/service/router-advert.rst:53 +msgid "Advertising a Prefix" +msgstr "Advertising a Prefix" + +#: ../../configuration/service/snmp.rst:165 +msgid "After commit the plaintext passwords will be hashed and stored in your configuration. The resulting CLI config will look like:" +msgstr "After commit the plaintext passwords will be hashed and stored in your configuration. The resulting CLI config will look like:" + +#: ../../configuration/vrf/index.rst:323 +msgid "After committing the configuration we can verify all leaked routes are installed, and try to ICMP ping PC1 from PC3." +msgstr "After committing the configuration we can verify all leaked routes are installed, and try to ICMP ping PC1 from PC3." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:80 +msgid "After the PKI certs are all set up we can start configuring our IPSec/IKE proposals used for key-exchange end data encryption. The used encryption ciphers and integrity algorithms vary from operating system to operating system. The ones used in this example are validated to work on Windows 10." +msgstr "After the PKI certs are all set up we can start configuring our IPSec/IKE proposals used for key-exchange end data encryption. The used encryption ciphers and integrity algorithms vary from operating system to operating system. The ones used in this example are validated to work on Windows 10." + +#: ../../configuration/pki/index.rst:212 +msgid "After we have imported the CA certificate(s) we can now import and add certificates used by services on this router." +msgstr "After we have imported the CA certificate(s) we can now import and add certificates used by services on this router." + +#: ../../configuration/service/snmp.rst:39 +msgid "Agent - software which runs on managed devices" +msgstr "Agent - software which runs on managed devices" + +#: ../../configuration/system/syslog.rst:173 +msgid "Alert" +msgstr "Alert" + +#: ../../configuration/highavailability/index.rst:346 +msgid "Algorithm" +msgstr "Algorithm" + +#: ../../configuration/system/host-name.rst:13 +msgid "Aliases" +msgstr "Aliases" + +#: ../../configuration/service/dns.rst:154 +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 "All DNS requests for example.com must be forwarded to a DNS server at 192.0.2.254 and 2001:db8:cafe::1" + +#: ../../configuration/service/snmp.rst:204 +msgid "All SNMP MIBs are located in each image of VyOS here: ``/usr/share/snmp/mibs/``" +msgstr "All SNMP MIBs are located in each image of VyOS here: ``/usr/share/snmp/mibs/``" + +#: ../../configuration/interfaces/wwan.rst:323 +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 "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." + +#: ../../configuration/vpn/sstp.rst:22 +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 "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." + +#: ../../configuration/system/syslog.rst:110 +msgid "All facilities" +msgstr "All facilities" + +#: ../../configuration/service/dhcp-relay.rst:11 +msgid "All interfaces used for the DHCP relay must be configured. This includes the uplink to the DHCP server." +msgstr "All interfaces used for the DHCP relay must be configured. This includes the uplink to the DHCP server." + +#: ../../configuration/highavailability/index.rst:142 +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 "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." + +#: ../../configuration/service/dns.rst:156 +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 "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" + +#: ../../configuration/service/webproxy.rst:134 +msgid "All reply sizes are accepted by default." +msgstr "All reply sizes are accepted by default." + +#: ../../configuration/system/task-scheduler.rst:10 +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 "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." + +#: ../../configuration/protocols/bgp.rst:241 +msgid "All these rules with OTC will help to detect and mitigate route leaks and happen automatically if local-role is set." +msgstr "All these rules with OTC will help to detect and mitigate route leaks and happen automatically if local-role is set." + +#: ../../configuration/interfaces/tunnel.rst:15 +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 "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." + +#: ../../configuration/firewall/zone.rst:36 +msgid "All traffic between zones is affected by existing policies" +msgstr "All traffic between zones is affected by existing policies" + +#: ../../configuration/firewall/zone.rst:35 +msgid "All traffic to and from an interface within a zone is permitted." +msgstr "All traffic to and from an interface within a zone is permitted." + +#: ../../configuration/vpn/pptp.rst:45 +msgid "All tunnel sessions can be checked via:" +msgstr "All tunnel sessions can be checked via:" + +#: ../../configuration/vpn/l2tp.rst:209 +msgid "Allocation clients ip addresses by RADIUS" +msgstr "Allocation clients ip addresses by RADIUS" + +#: ../../configuration/service/ssh.rst:121 +msgid "Allow ``ssh`` dynamic-protection." +msgstr "Allow ``ssh`` dynamic-protection." + +#: ../../configuration/service/webproxy.rst:70 +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 "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." + +#: ../../configuration/protocols/bgp.rst:274 +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 "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." + +#: ../../configuration/service/dns.rst:346 +msgid "Allow explicit IPv6 address for the interface." +msgstr "Allow explicit IPv6 address for the interface." + +#: ../../configuration/container/index.rst:32 +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 "Allow host networking in a container. The network stack of the container is not isolated from the host and will use the host IP." + +#: ../../configuration/protocols/bfd.rst:34 +msgid "Allow this BFD peer to not be directly connected" +msgstr "Allow this BFD peer to not be directly connected" + +#: ../../configuration/firewall/general.rst:1137 +#: ../../configuration/firewall/general-legacy.rst:694 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:162 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:73 +msgid "Allows to define URL path matching rules for a specific service." +msgstr "Allows to define URL path matching rules for a specific service." + +#: ../../configuration/protocols/static.rst:69 +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 "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>`." + +#: ../../configuration/protocols/static.rst:89 +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 "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>`." + +#: ../../configuration/service/ssh.rst:157 +msgid "Already learned known_hosts files of clients need an update as the public key will change." +msgstr "Already learned known_hosts files of clients need an update as the public key will change." + +#: ../../configuration/firewall/general.rst:377 +msgid "Also, **default-action** is an action that takes place whenever a packet does not match any rule in it's chain. For base chains, possible options for **default-action** are **accept** or **drop**." +msgstr "Also, **default-action** is an action that takes place whenever a packet does not match any rule in it's chain. For base chains, possible options for **default-action** are **accept** or **drop**." + +#: ../../configuration/service/dhcp-relay.rst:110 +msgid "Also, for backwards compatibility this configuration, which uses generic interface definition, is still valid:" +msgstr "Also, for backwards compatibility this configuration, which uses generic interface definition, is still valid:" + +#: ../../configuration/firewall/index.rst:15 +msgid "Also, for those who haven't updated to newer version, legacy documentation is still present and valid for all sagitta version prior to VyOS 1.4-rolling-202308040557:" +msgstr "Also, for those who haven't updated to newer version, legacy documentation is still present and valid for all sagitta version prior to VyOS 1.4-rolling-202308040557:" + +#: ../../configuration/nat/nat44.rst:276 +msgid "Also, in :ref:`destination-nat`, redirection to localhost is supported. The redirect statement is a special form of dnat which always translates the destination address to the local host’s one." +msgstr "Also, in :ref:`destination-nat`, redirection to localhost is supported. The redirect statement is a special form of dnat which always translates the destination address to the local host’s one." + +#: ../../configuration/protocols/static.rst:138 +msgid "Alternate Routing Tables" +msgstr "Alternate Routing Tables" + +#: ../../configuration/protocols/static.rst:142 +msgid "Alternate routing tables are used with policy based routing by utilizing :ref:`vrf`." +msgstr "Alternate routing tables are used with policy based routing by utilizing :ref:`vrf`." + +#: ../../configuration/interfaces/vxlan.rst:321 +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 "Alternative to multicast, the remote IPv4 address of the VXLAN tunnel can be set directly. Let's change the Multicast example from above:" + +#: ../../configuration/service/dhcp-server.rst:130 +msgid "Always exclude this address from any defined range. This address will never be assigned by the DHCP server." +msgstr "Always exclude this address from any defined range. This address will never be assigned by the DHCP server." + +#: ../../configuration/firewall/general.rst:241 +msgid "An **interface group** represents a collection of interfaces." +msgstr "An **interface group** represents a collection of interfaces." + +#: ../../configuration/protocols/bgp.rst:26 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:208 +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 "An IPv4 TCP filter will only match packets with an IPv4 header length of 20 bytes (which is the majority of IPv4 packets anyway)." + +#: ../../configuration/service/snmp.rst:36 +msgid "An SNMP-managed network consists of three key components:" +msgstr "An SNMP-managed network consists of three key components:" + +#: ../../configuration/interfaces/bonding.rst:234 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:90 +msgid "An additional layer of symmetric-key crypto can be used on top of the asymmetric crypto." +msgstr "An additional layer of symmetric-key crypto can be used on top of the asymmetric crypto." + +#: ../../configuration/interfaces/wireguard.rst:103 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:247 +msgid "An additional layer of symmetric-key crypto can be used on top of the asymmetric crypto. This is optional." +msgstr "An additional layer of symmetric-key crypto can be used on top of the asymmetric crypto. This is optional." + +#: ../../configuration/vpn/ipsec.rst:11 +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 "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." + +#: ../../configuration/service/snmp.rst:50 +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 "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." + +#: ../../configuration/protocols/ospf.rst:211 +msgid "An alternate command could be \"mpls-te on\" (Traffic Engineering)" +msgstr "An alternate command could be \"mpls-te on\" (Traffic Engineering)" + +#: ../../configuration/firewall/general-legacy.rst:424 +msgid "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 and a zone-based firewall as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)" +msgstr "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 and a zone-based firewall as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)" + +#: ../../configuration/firewall/general-legacy.rst:424 +msgid "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 and a zone-based firewall as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)." +msgstr "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 and a zone-based firewall as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)." + +#: ../../configuration/firewall/general.rst:619 +msgid "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)" +msgstr "An arbitrary netmask can be applied to mask addresses to only match against a specific portion. This is particularly useful with IPv6 as rules will remain valid if the IPv6 prefix changes and the host portion of systems IPv6 address is static (for example, with SLAAC or `tokenised IPv6 addresses <https://datatracker.ietf.org/doc/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt>`_)" + +#: ../../configuration/firewall/zone.rst:43 +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 "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`." + +#: ../../configuration/interfaces/tunnel.rst:36 +#: ../../configuration/interfaces/tunnel.rst:54 +#: ../../configuration/interfaces/tunnel.rst:71 +#: ../../configuration/interfaces/tunnel.rst:93 +#: ../../configuration/interfaces/tunnel.rst:194 +#: ../../configuration/system/login.rst:195 +msgid "An example:" +msgstr "An example:" + +#: ../../configuration/service/monitoring.rst:136 +msgid "An example of a configuration that sends ``telegraf`` metrics to remote ``InfluxDB 2``" +msgstr "An example of a configuration that sends ``telegraf`` metrics to remote ``InfluxDB 2``" + +#: ../../configuration/interfaces/bridge.rst:227 +msgid "An example of creating a VLAN-aware bridge is as follows:" +msgstr "An example of creating a VLAN-aware bridge is as follows:" + +#: ../../configuration/system/login.rst:149 +msgid "An example of key generation:" +msgstr "An example of key generation:" + +#: ../../configuration/vpn/openconnect.rst:291 +msgid "An example of the data captured by a FREERADIUS server with sql accounting:" +msgstr "An example of the data captured by a FREERADIUS server with sql accounting:" + +#: ../../configuration/service/dhcp-server.rst:475 +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 "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\";``." + +#: ../../configuration/policy/route.rst:76 +msgid "And for ipv6:" +msgstr "And for ipv6:" + +#: ../../configuration/system/ip.rst:84 +msgid "And the different IPv4 **reset** commands available:" +msgstr "And the different IPv4 **reset** commands available:" + +#: ../../configuration/interfaces/bonding.rst:185 +#: ../../configuration/interfaces/bonding.rst:214 +msgid "And then hash is reduced modulo slave count." +msgstr "And then hash is reduced modulo slave count." + +#: ../../configuration/nat/nat44.rst:590 +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 "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." + +#: ../../configuration/protocols/mpls.rst:63 +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 "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." + +#: ../../configuration/vrf/index.rst:52 +#: ../../configuration/vrf/index.rst:62 +msgid "Apply a route-map filter to routes for the specified protocol." +msgstr "Apply a route-map filter to routes for the specified protocol." + +#: ../../configuration/system/ip.rst:39 +msgid "Apply a route-map filter to routes for the specified protocol. The following protocols can be used: any, babel, bgp, connected, eigrp, isis, kernel, ospf, rip, static, table" +msgstr "Apply a route-map filter to routes for the specified protocol. The following protocols can be used: any, babel, bgp, connected, eigrp, isis, kernel, ospf, rip, static, table" + +#: ../../configuration/system/ipv6.rst:35 +msgid "Apply a route-map filter to routes for the specified protocol. The following protocols can be used: any, babel, bgp, connected, isis, kernel, ospfv3, ripng, static, table" +msgstr "Apply a route-map filter to routes for the specified protocol. The following protocols can be used: any, babel, bgp, connected, isis, kernel, ospfv3, ripng, static, table" + +#: ../../configuration/policy/examples.rst:128 +msgid "Apply routing policy to **inbound** direction of out VLAN interfaces" +msgstr "Apply routing policy to **inbound** direction of out VLAN interfaces" + +#: ../../configuration/firewall/zone.rst:82 +msgid "Applying a Rule-Set to a Zone" +msgstr "Applying a Rule-Set to a Zone" + +#: ../../configuration/firewall/general-legacy.rst:747 +msgid "Applying a Rule-Set to an Interface" +msgstr "Applying a Rule-Set to an Interface" + +#: ../../configuration/trafficpolicy/index.rst:1150 +msgid "Applying a traffic policy" +msgstr "Applying a traffic policy" + +#: ../../configuration/protocols/ospf.rst:218 +#: ../../configuration/protocols/ospf.rst:1122 +msgid "Area Configuration" +msgstr "Area Configuration" + +#: ../../configuration/protocols/isis.rst:55 +msgid "Area identifier: ``0001`` IS-IS area number (numberical area ``1``)" +msgstr "Area identifier: ``0001`` IS-IS area number (numberical area ``1``)" + +#: ../../configuration/system/task-scheduler.rst:38 +msgid "Arguments which will be passed to the executable." +msgstr "Arguments which will be passed to the executable." + +#: ../../configuration/interfaces/bonding.rst:396 +msgid "Arista EOS" +msgstr "Arista EOS" + +#: ../../configuration/interfaces/bonding.rst:381 +msgid "Aruba/HP" +msgstr "Aruba/HP" + +#: ../../_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 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:4 +#: ../../_include/interface-ipv6.txt:60 +#: ../../configuration/interfaces/pppoe.rst:194 +#: ../../configuration/interfaces/pppoe.rst:240 +#: ../../_include/interface-ip.txt:4 +#: ../../_include/interface-ipv6.txt:60 +#: ../../_include/interface-ip.txt:4 +#: ../../_include/interface-ipv6.txt:60 +#: ../../configuration/interfaces/sstp-client.rst:79 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:4 +#: ../../_include/interface-ipv6.txt:60 +#: ../../_include/interface-ip.txt:4 +#: ../../_include/interface-ipv6.txt:60 +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 "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'." + +#: ../../configuration/vpn/sstp.rst:19 +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 "As SSTP provides PPP via a SSL/TLS channel the use of either publically signed certificates as well as a private PKI is required." + +#: ../../configuration/interfaces/vxlan.rst:61 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:34 +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 "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." + +#: ../../configuration/interfaces/wwan.rst:326 +msgid "As VyOS makes use of the QMI interface to connect to the WWAN modem cards, also the firmware can be reprogrammed." +msgstr "As VyOS makes use of the QMI interface to connect to the WWAN modem cards, also the firmware can be reprogrammed." + +#: ../../configuration/trafficpolicy/index.rst:940 +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 "As a reference: for 10mbit/s on Intel, you might need at least 10kbyte buffer if you want to reach your configured rate." + +#: ../../configuration/interfaces/openvpn.rst:666 +msgid "As a result, the processing of each packet becomes more efficient, potentially leveraging hardware encryption offloading support available in the kernel." +msgstr "As a result, the processing of each packet becomes more efficient, potentially leveraging hardware encryption offloading support available in the kernel." + +#: ../../configuration/firewall/zone.rst:49 +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 "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." + +#: ../../configuration/system/option.rst:80 +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 "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." + +#: ../../configuration/nat/nat44.rst:26 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:48 +msgid "As of VyOS 1.4, OpenVPN site-to-site mode can use either pre-shared keys or x.509 certificates." +msgstr "As of VyOS 1.4, OpenVPN site-to-site mode can use either pre-shared keys or x.509 certificates." + +#: ../../configuration/vpn/pptp.rst:10 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:196 +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 "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`_." + +#: ../../configuration/trafficpolicy/index.rst:323 +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 "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." + +#: ../../configuration/firewall/index.rst:81 +msgid "As the example image below shows, the device now needs rules to allow/block traffic to or from the services running on the device that have open connections on that interface." +msgstr "As the example image below shows, the device now needs rules to allow/block traffic to or from the services running on the device that have open connections on that interface." + +#: ../../configuration/firewall/index.rst:60 +msgid "As the example image below shows, the device was configured with rules blocking inbound or outbound traffic on each interface." +msgstr "As the example image below shows, the device was configured with rules blocking inbound or outbound traffic on each interface." + +#: ../../configuration/interfaces/tunnel.rst:69 +msgid "As the name implies, it's IPv4 encapsulated in IPv6, as simple as that." +msgstr "As the name implies, it's IPv4 encapsulated in IPv6, as simple as that." + +#: ../../configuration/vpn/l2tp.rst:36 +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 "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):" + +#: ../../configuration/trafficpolicy/index.rst:997 +msgid "As with other policies, Round-Robin can embed_ another policy into a class through the ``queue-type`` setting." +msgstr "As with other policies, Round-Robin can embed_ another policy into a class through the ``queue-type`` setting." + +#: ../../configuration/trafficpolicy/index.rst:1076 +msgid "As with other policies, Shaper can embed_ other policies into its classes through the ``queue-type`` setting and then configure their parameters." +msgstr "As with other policies, Shaper can embed_ other policies into its classes through the ``queue-type`` setting and then configure their parameters." + +#: ../../configuration/trafficpolicy/index.rst:718 +msgid "As with other policies, you can define different type of matching rules for your classes:" +msgstr "As with other policies, you can define different type of matching rules for your classes:" + +#: ../../configuration/trafficpolicy/index.rst:734 +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 "As with other policies, you can embed_ other policies into the classes (and default) of your Priority Queue policy through the ``queue-type`` setting:" + +#: ../../configuration/interfaces/vxlan.rst:264 +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 "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:" + +#: ../../configuration/firewall/general-legacy.rst:770 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:35 +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 "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`." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:86 +msgid "Assign a specific backend to a rule" +msgstr "Assign a specific backend to a rule" + +#: ../../configuration/vrf/index.rst:79 +msgid "Assign interface identified by `<interface>` to VRF named `<name>`." +msgstr "Assign interface identified by `<interface>` to VRF named `<name>`." + +#: ../../configuration/interfaces/bonding.rst:324 +msgid "Assign member interfaces to PortChannel" +msgstr "Assign member interfaces to PortChannel" + +#: ../../configuration/vpn/sstp.rst:80 +msgid "Assign static IP address to `<user>` account." +msgstr "Assign static IP address to `<user>` account." + +#: ../../configuration/service/dhcp-server.rst:111 +msgid "Assign the IP address to this machine for `<time>` seconds." +msgstr "Assign the IP address to this machine for `<time>` seconds." + +#: ../../configuration/system/login.rst:62 +msgid "Assign the SSH public key portion `<key>` identified by per-key `<identifier>` to the local user `<username>`." +msgstr "Assign the SSH public key portion `<key>` identified by per-key `<identifier>` to the local user `<username>`." + +#: ../../configuration/interfaces/wireguard.rst:174 +msgid "Associates the previously generated private key to a specific WireGuard interface. The private key can be generate via the command" +msgstr "Associates the previously generated private key to a specific WireGuard interface. The private key can be generate via the command" + +#: ../../configuration/interfaces/wireguard.rst:232 +msgid "Assure that your firewall rules allow the traffic, in which case you have a working VPN using WireGuard." +msgstr "Assure that your firewall rules allow the traffic, in which case you have a working VPN using WireGuard." + +#: ../../configuration/trafficpolicy/index.rst:269 +msgid "Assured Forwarding(AF) 11" +msgstr "Assured Forwarding(AF) 11" + +#: ../../configuration/trafficpolicy/index.rst:271 +msgid "Assured Forwarding(AF) 12" +msgstr "Assured Forwarding(AF) 12" + +#: ../../configuration/trafficpolicy/index.rst:273 +msgid "Assured Forwarding(AF) 13" +msgstr "Assured Forwarding(AF) 13" + +#: ../../configuration/trafficpolicy/index.rst:275 +msgid "Assured Forwarding(AF) 21" +msgstr "Assured Forwarding(AF) 21" + +#: ../../configuration/trafficpolicy/index.rst:277 +msgid "Assured Forwarding(AF) 22" +msgstr "Assured Forwarding(AF) 22" + +#: ../../configuration/trafficpolicy/index.rst:279 +msgid "Assured Forwarding(AF) 23" +msgstr "Assured Forwarding(AF) 23" + +#: ../../configuration/trafficpolicy/index.rst:281 +msgid "Assured Forwarding(AF) 31" +msgstr "Assured Forwarding(AF) 31" + +#: ../../configuration/trafficpolicy/index.rst:283 +msgid "Assured Forwarding(AF) 32" +msgstr "Assured Forwarding(AF) 32" + +#: ../../configuration/trafficpolicy/index.rst:285 +msgid "Assured Forwarding(AF) 33" +msgstr "Assured Forwarding(AF) 33" + +#: ../../configuration/trafficpolicy/index.rst:287 +msgid "Assured Forwarding(AF) 41" +msgstr "Assured Forwarding(AF) 41" + +#: ../../configuration/trafficpolicy/index.rst:289 +msgid "Assured Forwarding(AF) 42" +msgstr "Assured Forwarding(AF) 42" + +#: ../../configuration/trafficpolicy/index.rst:291 +msgid "Assured Forwarding(AF) 43" +msgstr "Assured Forwarding(AF) 43" + +#: ../../configuration/trafficpolicy/index.rst:980 +msgid "At every round, the deficit counter adds the quantum so that even large packets will have their opportunity to be dequeued." +msgstr "At every round, the deficit counter adds the quantum so that even large packets will have their opportunity to be dequeued." + +#: ../../configuration/firewall/general.rst:1489 +#: ../../configuration/firewall/general-legacy.rst:972 +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 "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``" + +#: ../../configuration/system/lcd.rst:31 +msgid "At the time of this writing the following displays are supported:" +msgstr "At the time of this writing the following displays are supported:" + +#: ../../configuration/trafficpolicy/index.rst:490 +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 "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." + +#: ../../configuration/container/index.rst:42 +msgid "Attaches user-defined network to a container. Only one network must be specified and must already exist." +msgstr "Attaches user-defined network to a container. Only one network must be specified and must already exist." + +#: ../../configuration/service/webproxy.rst:152 +msgid "Authentication" +msgstr "Authentication" + +#: ../../configuration/interfaces/ethernet.rst:99 +msgid "Authentication (EAPoL)" +msgstr "Authentication (EAPoL)" + +#: ../../configuration/service/monitoring.rst:10 +msgid "Authentication application client-id." +msgstr "Authentication application client-id." + +#: ../../configuration/service/monitoring.rst:14 +msgid "Authentication application client-secret." +msgstr "Authentication application client-secret." + +#: ../../configuration/service/monitoring.rst:18 +msgid "Authentication application tenant-id" +msgstr "Authentication application tenant-id" + +#: ../../configuration/interfaces/openvpn.rst:449 +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 "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" + +#: ../../configuration/service/monitoring.rst:114 +msgid "Authentication organization name" +msgstr "Authentication organization name" + +#: ../../configuration/service/monitoring.rst:118 +msgid "Authentication token" +msgstr "Authentication token" + +#: ../../configuration/service/snmp.rst:140 +msgid "Authentication – to verify that the message is from a valid source." +msgstr "Authentication – to verify that the message is from a valid source." + +#: ../../configuration/service/monitoring.rst:92 +msgid "Authorization token" +msgstr "Authorization token" + +#: ../../configuration/service/pppoe-server.rst:172 +msgid "Automatic VLAN Creation" +msgstr "Automatic VLAN Creation" + +#: ../../configuration/service/ipoe-server.rst:96 +msgid "Automatic VLAN creation" +msgstr "Automatic VLAN creation" + +#: ../../configuration/system/option.rst:19 +msgid "Automatically reboot system on kernel panic after 60 seconds." +msgstr "Automatically reboot system on kernel panic after 60 seconds." + +#: ../../configuration/protocols/bgp.rst:22 +msgid "Autonomous Systems" +msgstr "Autonomous Systems" + +#: ../../configuration/nat/nat44.rst:370 +msgid "Avoiding \"leaky\" NAT" +msgstr "Avoiding \"leaky\" NAT" + +#: ../../configuration/service/monitoring.rst:5 +msgid "Azure-data-explorer" +msgstr "Azure-data-explorer" + +#: ../../configuration/protocols/bfd.rst:9 +msgid "BFD" +msgstr "BFD" + +#: ../../configuration/protocols/bfd.rst:136 +msgid "BFD Static Route Monitoring" +msgstr "BFD Static Route Monitoring" + +#: ../../configuration/protocols/bfd.rst:17 +msgid "BFD sends lots of small UDP packets very quickly to ensures that the peer is still alive." +msgstr "BFD sends lots of small UDP packets very quickly to ensures that the peer is still alive." + +#: ../../configuration/protocols/bgp.rst:5 +msgid "BGP" +msgstr "BGP" + +#: ../../configuration/policy/as-path-list.rst:3 +msgid "BGP - AS Path Policy" +msgstr "BGP - AS Path Policy" + +#: ../../configuration/policy/community-list.rst:3 +msgid "BGP - Community List" +msgstr "BGP - Community List" + +#: ../../configuration/policy/extcommunity-list.rst:3 +msgid "BGP - Extended Community List" +msgstr "BGP - Extended Community List" + +#: ../../configuration/policy/large-community-list.rst:3 +msgid "BGP - Large Community List" +msgstr "BGP - Large Community List" + +#: ../../configuration/policy/examples.rst:3 +msgid "BGP Example" +msgstr "BGP Example" + +#: ../../configuration/protocols/bgp.rst:169 +msgid "BGP Router Configuration" +msgstr "BGP Router Configuration" + +#: ../../configuration/protocols/bgp.rst:888 +msgid "BGP Scaling Configuration" +msgstr "BGP Scaling Configuration" + +#: ../../configuration/policy/route-map.rst:197 +msgid "BGP aggregator attribute: AS number or IP address of an aggregation." +msgstr "BGP aggregator attribute: AS number or IP address of an aggregation." + +#: ../../configuration/policy/route-map.rst:41 +msgid "BGP as-path list to match." +msgstr "BGP as-path list to match." + +#: ../../configuration/policy/route-map.rst:216 +msgid "BGP atomic aggregate attribute." +msgstr "BGP atomic aggregate attribute." + +#: ../../configuration/policy/route-map.rst:46 +msgid "BGP community-list to match." +msgstr "BGP community-list to match." + +#: ../../configuration/policy/route-map.rst:56 +msgid "BGP extended community to match." +msgstr "BGP extended community to match." + +#: ../../configuration/protocols/bgp.rst:212 +msgid "BGP roles are defined in RFC :rfc:`9234` and provide an easy way to add route leak prevention, detection and mitigation. The local Role value is negotiated with the new BGP Role capability which has a built-in check of the corresponding value. In case of a mismatch the new OPEN Roles Mismatch Notification <2, 11> would be sent. The correct Role pairs are:" +msgstr "BGP roles are defined in RFC :rfc:`9234` and provide an easy way to add route leak prevention, detection and mitigation. The local Role value is negotiated with the new BGP Role capability which has a built-in check of the corresponding value. In case of a mismatch the new OPEN Roles Mismatch Notification <2, 11> would be sent. The correct Role pairs are:" + +#: ../../configuration/protocols/bgp.rst:890 +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 "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." + +#: ../../configuration/vrf/index.rst:411 +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 "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." + +#: ../../configuration/protocols/babel.rst:5 +msgid "Babel" +msgstr "Babel" + +#: ../../configuration/protocols/babel.rst:14 +msgid "Babel a dual stack protocol. A single Babel instance is able to perform routing for both IPv4 and IPv6." +msgstr "Babel a dual stack protocol. A single Babel instance is able to perform routing for both IPv4 and IPv6." + +#: ../../configuration/protocols/babel.rst:7 +msgid "Babel is a modern routing protocol designed to be robust and efficient both in ordinary wired networks and in wireless mesh networks. By default, it uses hop-count on wired networks and a variant of ETX on wireless links, It can be configured to take radio diversity into account and to automatically compute a link's latency and include it in the metric. It is defined in :rfc:`8966`." +msgstr "Babel is a modern routing protocol designed to be robust and efficient both in ordinary wired networks and in wireless mesh networks. By default, it uses hop-count on wired networks and a variant of ETX on wireless links, It can be configured to take radio diversity into account and to automatically compute a link's latency and include it in the metric. It is defined in :rfc:`8966`." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:95 +msgid "Backend" +msgstr "Backend" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:108 +msgid "Balance algorithms:" +msgstr "Balance algorithms:" + +#: ../../configuration/loadbalancing/wan.rst:36 +msgid "Balancing Rules" +msgstr "Balancing Rules" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:211 +msgid "Balancing based on domain name" +msgstr "Balancing based on domain name" + +#: ../../configuration/service/ipoe-server.rst:122 +#: ../../configuration/service/pppoe-server.rst:195 +#: ../../configuration/vpn/l2tp.rst:113 +msgid "Bandwidth Shaping" +msgstr "Bandwidth Shaping" + +#: ../../configuration/service/ipoe-server.rst:128 +#: ../../configuration/vpn/l2tp.rst:118 +msgid "Bandwidth Shaping for local users" +msgstr "Bandwidth Shaping for local users" + +#: ../../configuration/service/pppoe-server.rst:197 +msgid "Bandwidth rate limits can be set for local users or RADIUS based attributes." +msgstr "Bandwidth rate limits can be set for local users or RADIUS based attributes." + +#: ../../configuration/vpn/l2tp.rst:115 +msgid "Bandwidth rate limits can be set for local users or via RADIUS based attributes." +msgstr "Bandwidth rate limits can be set for local users or via RADIUS based attributes." + +#: ../../configuration/service/ipoe-server.rst:124 +msgid "Bandwidth rate limits can be set for local users within the configuration or via RADIUS based attributes." +msgstr "Bandwidth rate limits can be set for local users within the configuration or via RADIUS based attributes." + +#: ../../configuration/vpn/dmvpn.rst:34 +#: ../../configuration/vpn/dmvpn.rst:34 +msgid "Baseline DMVPN topology" +msgstr "Baseline DMVPN topology" + +#: ../../configuration/protocols/bgp.rst:17 +msgid "Basic Concepts" +msgstr "Basic Concepts" + +#: ../../configuration/protocols/igmp.rst:91 +#: ../../configuration/protocols/pim6.rst:26 +msgid "Basic commands" +msgstr "Basic commands" + +#: ../../configuration/policy/access-list.rst:9 +msgid "Basic filtering can be done using access-list and access-list6." +msgstr "Basic filtering can be done using access-list and access-list6." + +#: ../../configuration/policy/access-list.rst:46 +msgid "Basic filtering could also be applied to IPv6 traffic." +msgstr "Basic filtering could also be applied to IPv6 traffic." + +#: ../../configuration/highavailability/index.rst:26 +msgid "Basic setup" +msgstr "Basic setup" + +#: ../../configuration/vpn/openconnect.rst:255 +msgid "Be sure to set a sane default config in the default config file, this will be loaded in the case that a user is authenticated and no file is found in the configured directory matching the users username/group." +msgstr "Be sure to set a sane default config in the default config file, this will be loaded in the case that a user is authenticated and no file is found in the configured directory matching the users username/group." + +#: ../../configuration/interfaces/wireless.rst:235 +msgid "Beamforming capabilities:" +msgstr "Beamforming capabilities:" + +#: ../../configuration/interfaces/bonding.rst:142 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:235 +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 "Because existing sessions do not automatically fail over to a new path, the session table can be flushed on each connection state change:" + +#: ../../configuration/interfaces/ethernet.rst:70 +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 "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." + +#: ../../configuration/firewall/zone.rst:84 +msgid "Before you are able to apply a rule-set to a zone you have to create the zones first." +msgstr "Before you are able to apply a rule-set to a zone you have to create the zones first." + +#: ../../configuration/vpn/site2site_ipsec.rst:392 +msgid "Below flow-chart could be a quick reference for the close-action combination depending on how the peer is configured." +msgstr "Below flow-chart could be a quick reference for the close-action combination depending on how the peer is configured." + +#: ../../configuration/vpn/l2tp.rst:93 +msgid "Below is an example to configure a LNS:" +msgstr "Below is an example to configure a LNS:" + +#: ../../configuration/trafficpolicy/index.rst:267 +msgid "Best effort traffic, default" +msgstr "Best effort traffic, default" + +#: ../../configuration/service/console-server.rst:23 +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 "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." + +#: ../../configuration/nat/nat44.rst:104 +msgid "Bidirectional NAT" +msgstr "Bidirectional NAT" + +#: ../../configuration/trafficpolicy/index.rst:262 +msgid "Binary value" +msgstr "Binary value" + +#: ../../configuration/protocols/bfd.rst:39 +msgid "Bind listener to specific interface/address, mandatory for IPv6" +msgstr "Bind listener to specific interface/address, mandatory for IPv6" + +#: ../../configuration/interfaces/vxlan.rst:285 +msgid "Binds eth1.241 and vxlan241 to each other by making them both member interfaces of the same bridge." +msgstr "Binds eth1.241 and vxlan241 to each other by making them both member interfaces of the same bridge." + +#: ../../configuration/protocols/static.rst:108 +msgid "Blackhole" +msgstr "Blackhole" + +#: ../../configuration/service/ssh.rst:130 +msgid "Block source IP in seconds. Subsequent blocks increase by a factor of 1.5 The default is 120." +msgstr "Block source IP in seconds. Subsequent blocks increase by a factor of 1.5 The default is 120." + +#: ../../configuration/service/ssh.rst:139 +msgid "Block source IP when their cumulative attack score exceeds threshold. The default is 30." +msgstr "Block source IP when their cumulative attack score exceeds threshold. The default is 30." + +#: ../../configuration/loadbalancing/wan.rst:264 +msgid "Blocking call with no timeout. System will become unresponsive if script does not return!" +msgstr "Blocking call with no timeout. System will become unresponsive if script does not return!" + +#: ../../configuration/policy/route-map.rst:155 +msgid "Boarder Gateway Protocol (BGP) origin code to match." +msgstr "Boarder Gateway Protocol (BGP) origin code to match." + +#: ../../configuration/interfaces/bonding.rst:7 +msgid "Bond / Link Aggregation" +msgstr "Bond / Link Aggregation" + +#: ../../configuration/interfaces/bonding.rst:34 +msgid "Bond options" +msgstr "Bond options" + +#: ../../configuration/service/dhcp-server.rst:339 +msgid "Boot image length in 512-octet blocks" +msgstr "Boot image length in 512-octet blocks" + +#: ../../configuration/service/dhcp-server.rst:334 +msgid "Bootstrap file name" +msgstr "Bootstrap file name" + +#: ../../configuration/interfaces/vxlan.rst:102 +msgid "Both IPv4 and IPv6 multicast is possible." +msgstr "Both IPv4 and IPv6 multicast is possible." + +#: ../../configuration/system/login.rst:13 +msgid "Both local administered and remote administered :abbr:`RADIUS (Remote Authentication Dial-In User Service)` accounts are supported." +msgstr "Both local administered and remote administered :abbr:`RADIUS (Remote Authentication Dial-In User Service)` accounts are supported." + +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +#: ../../_include/interface-ip.txt:88 +msgid "Both replies and requests type gratuitous arp will trigger the ARP table to be updated, if this setting is on." +msgstr "Both replies and requests type gratuitous arp will trigger the ARP table to be updated, if this setting is on." + +#: ../../configuration/interfaces/openvpn.rst:428 +msgid "Branch 1's router might have the following lines:" +msgstr "Branch 1's router might have the following lines:" + +#: ../../configuration/interfaces/bridge.rst:7 +msgid "Bridge" +msgstr "Bridge" + +#: ../../configuration/interfaces/l2tpv3.rst:165 +msgid "Bridge:" +msgstr "Bridge:" + +#: ../../configuration/interfaces/bridge.rst:66 +msgid "Bridge Options" +msgstr "Bridge Options" + +#: ../../configuration/interfaces/bridge.rst:198 +#: ../../configuration/interfaces/bridge.rst:233 +msgid "Bridge answers on IP address 192.0.2.1/24 and 2001:db8::ffff/64" +msgstr "Bridge answers on IP address 192.0.2.1/24 and 2001:db8::ffff/64" + +#: ../../configuration/interfaces/bridge.rst:74 +msgid "Bridge maximum aging `<time>` in seconds (default: 20)." +msgstr "Bridge maximum aging `<time>` in seconds (default: 20)." + +#: ../../configuration/interfaces/pppoe.rst:41 +msgid "Business Users" +msgstr "Business Users" + +#: ../../configuration/trafficpolicy/index.rst:35 +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 "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." + +#: ../../configuration/protocols/bgp.rst:155 +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 "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." + +#: ../../configuration/protocols/bgp.rst:519 +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 "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." + +#: ../../configuration/system/login.rst:126 +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 "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." + +#: ../../configuration/service/dns.rst:380 +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 "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." + +#: ../../configuration/protocols/rpki.rst:91 +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 "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." + +#: ../../configuration/protocols/ospf.rst:534 +#: ../../configuration/protocols/ospf.rst:1246 +msgid "By default, it supports both planned and unplanned outages." +msgstr "By default, it supports both planned and unplanned outages." + +#: ../../configuration/service/https.rst:54 +msgid "By default, nginx exposes the local API on all virtual servers. Use this to restrict nginx to one or more virtual hosts." +msgstr "By default, nginx exposes the local API on all virtual servers. Use this to restrict nginx to one or more virtual hosts." + +#: ../../configuration/system/flow-accounting.rst:60 +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 "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:" + +#: ../../configuration/protocols/bgp.rst:507 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:73 +msgid "By default, this bridging is allowed." +msgstr "By default, this bridging is allowed." + +#: ../../configuration/firewall/general.rst:90 +#: ../../configuration/firewall/general-legacy.rst:42 +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 "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." + +#: ../../configuration/highavailability/index.rst:190 +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 "By default VRRP uses multicast packets. If your network does not support multicast for whatever reason, you can make VRRP use unicast communication instead." + +#: ../../configuration/highavailability/index.rst:155 +msgid "By default VRRP uses preemption. You can disable it with the \"no-preempt\" option:" +msgstr "By default VRRP uses preemption. You can disable it with the \"no-preempt\" option:" + +#: ../../configuration/protocols/ospf.rst:520 +#: ../../configuration/protocols/ospf.rst:1232 +msgid "By default `strict-lsa-checking` is configured then the helper will abort the Graceful Restart when a LSA change occurs which affects the restarting router." +msgstr "By default `strict-lsa-checking` is configured then the helper will abort the Graceful Restart when a LSA change occurs which affects the restarting router." + +#: ../../configuration/vrf/index.rst:35 +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 "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." + +#: ../../configuration/interfaces/pseudo-ethernet.rst:14 +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 "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." + +#: ../../configuration/service/webproxy.rst:393 +msgid "Bypassing the webproxy" +msgstr "Bypassing the webproxy" + +#: ../../configuration/pki/index.rst:170 +msgid "CA (Certificate Authority)" +msgstr "CA (Certificate Authority)" + +#: ../../configuration/trafficpolicy/index.rst:793 +msgid "CRITIC/ECP" +msgstr "CRITIC/ECP" + +#: ../../configuration/policy/route-map.rst:29 +msgid "Call another route-map policy on match." +msgstr "Call another route-map policy on match." + +#: ../../configuration/protocols/bgp.rst:133 +#: ../../configuration/protocols/bgp.rst:263 +msgid "Capability Negotiation" +msgstr "Capability Negotiation" + +#: ../../configuration/service/broadcast-relay.rst:7 +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 "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." + +#: ../../configuration/pki/index.rst:33 +msgid "Certificate Authority (CA)" +msgstr "Certificate Authority (CA)" + +#: ../../configuration/pki/index.rst:185 +msgid "Certificate revocation list in PEM format." +msgstr "Certificate revocation list in PEM format." + +#: ../../configuration/pki/index.rst:63 +#: ../../configuration/vpn/sstp.rst:27 +msgid "Certificates" +msgstr "Certificates" + +#: ../../configuration/system/option.rst:66 +msgid "Change system keyboard layout to given language." +msgstr "Change system keyboard layout to given language." + +#: ../../configuration/firewall/zone.rst:75 +msgid "Change the default-action with this setting." +msgstr "Change the default-action with this setting." + +#: ../../configuration/protocols/bgp.rst:387 +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 "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." + +#: ../../configuration/nat/nat44.rst:126 +msgid "Changes to the NAT system only affect newly established connections. Already established connections are not affected." +msgstr "Changes to the NAT system only affect newly established connections. Already established connections are not affected." + +#: ../../configuration/system/option.rst:70 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:44 +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 "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" + +#: ../../configuration/system/acceleration.rst:32 +msgid "Check if the Intel® QAT device is up and ready to do the job." +msgstr "Check if the Intel® QAT device is up and ready to do the job." + +#: ../../configuration/interfaces/openvpn.rst:706 +msgid "Check status" +msgstr "Check status" + +#: ../../configuration/system/ipv6.rst:64 +msgid "Check the many parameters available for the `show ipv6 route` command:" +msgstr "Check the many parameters available for the `show ipv6 route` command:" + +#: ../../configuration/service/pppoe-server.rst:320 +msgid "Checking connections" +msgstr "Checking connections" + +#: ../../configuration/service/tftp-server.rst:21 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:322 +msgid "Cisco Catalyst" +msgstr "Cisco Catalyst" + +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +#: ../../_include/interface-ip.txt:168 +msgid "Cisco and Allied Telesyn call it Private VLAN" +msgstr "Cisco and Allied Telesyn call it Private VLAN" + +#: ../../configuration/policy/examples.rst:187 +msgid "Clamp MSS for a specific IP" +msgstr "Clamp MSS for a specific IP" + +#: ../../configuration/trafficpolicy/index.rst:227 +msgid "Class treatment" +msgstr "Class treatment" + +#: ../../configuration/trafficpolicy/index.rst:107 +msgid "Classes" +msgstr "Classes" + +#: ../../configuration/service/dhcp-server.rst:359 +msgid "Classless static route" +msgstr "Classless static route" + +#: ../../configuration/policy/route-map.rst:269 +msgid "Clear all BGP extcommunities." +msgstr "Clear all BGP extcommunities." + +#: ../../configuration/interfaces/openvpn.rst:571 +msgid "Client" +msgstr "Client" + +#: ../../configuration/service/tftp-server.rst:67 +msgid "Client:" +msgstr "Client:" + +#: ../../configuration/service/pppoe-server.rst:57 +msgid "Client Address Pools" +msgstr "Client Address Pools" + +#: ../../configuration/interfaces/openvpn.rst:388 +msgid "Client Authentication" +msgstr "Client Authentication" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:137 +msgid "Client Configuration" +msgstr "Client Configuration" + +#: ../../configuration/vpn/sstp.rst:278 +msgid "Client IP addresses will be provided from pool `192.0.2.0/25`" +msgstr "Client IP addresses will be provided from pool `192.0.2.0/25`" + +#: ../../configuration/interfaces/openvpn.rst:614 +msgid "Client Side" +msgstr "Client Side" + +#: ../../configuration/service/ipoe-server.rst:184 +msgid "Client configuration" +msgstr "Client configuration" + +#: ../../configuration/service/dhcp-server.rst:299 +msgid "Client domain name" +msgstr "Client domain name" + +#: ../../configuration/service/dhcp-server.rst:354 +msgid "Client domain search" +msgstr "Client domain search" + +#: ../../configuration/interfaces/wireless.rst:70 +msgid "Client isolation can be used to prevent low-level bridging of frames between associated stations in the BSS." +msgstr "Client isolation can be used to prevent low-level bridging of frames between associated stations in the BSS." + +#: ../../configuration/interfaces/openvpn.rst:399 +msgid "Clients are identified by the CN field of their x.509 certificates, in this example the CN is ``client0``:" +msgstr "Clients are identified by the CN field of their x.509 certificates, in this example the CN is ``client0``:" + +#: ../../configuration/service/dhcp-server.rst:590 +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 "Clients receiving advertise messages from multiple servers choose the server with the highest preference value. The range for this value is ``0...255``." + +#: ../../configuration/system/syslog.rst:130 +msgid "Clock daemon" +msgstr "Clock daemon" + +#: ../../configuration/system/time-zone.rst:17 +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 "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." + +#: ../../configuration/firewall/general.rst:530 +msgid "Command for disabling a rule but keep it in the configuration." +msgstr "Command for disabling a rule but keep it in the configuration." + +#: ../../configuration/vrf/index.rst:128 +msgid "Command should probably be extended to list also the real interfaces assigned to this one VRF to get a better overview." +msgstr "Command should probably be extended to list also the real interfaces assigned to this one VRF to get a better overview." + +#: ../../configuration/firewall/general.rst:1544 +#: ../../configuration/firewall/general-legacy.rst:1054 +msgid "Command used to update GeoIP database and firewall sets." +msgstr "Command used to update GeoIP database and firewall sets." + +#: ../../configuration/service/dhcp-server.rst:438 +msgid "Common configuration, valid for both primary and secondary node." +msgstr "Common configuration, valid for both primary and secondary node." + +#: ../../configuration/interfaces/bonding.rst:20 +#: ../../configuration/interfaces/bridge.rst:24 +#: ../../configuration/interfaces/dummy.rst:31 +#: ../../configuration/interfaces/ethernet.rst:17 +#: ../../configuration/interfaces/geneve.rst:42 +#: ../../configuration/interfaces/l2tpv3.rst:34 +#: ../../configuration/interfaces/loopback.rst:29 +#: ../../configuration/interfaces/macsec.rst:23 +#: ../../configuration/interfaces/pppoe.rst:62 +#: ../../configuration/interfaces/pseudo-ethernet.rst:48 +#: ../../configuration/interfaces/sstp-client.rst:23 +#: ../../configuration/interfaces/tunnel.rst:19 +#: ../../configuration/interfaces/virtual-ethernet.rst:20 +#: ../../configuration/interfaces/vxlan.rst:42 +#: ../../configuration/interfaces/wireless.rst:33 +#: ../../configuration/interfaces/wwan.rst:19 +msgid "Common interface configuration" +msgstr "Common interface configuration" + +#: ../../configuration/protocols/bgp.rst:585 +msgid "Common parameters" +msgstr "Common parameters" + +#: ../../configuration/protocols/bgp.rst:927 +msgid "Confederation Configuration" +msgstr "Confederation Configuration" + +#: ../../configuration/service/snmp.rst:134 +msgid "Confidentiality – Encryption of packets to prevent snooping by an unauthorized source." +msgstr "Confidentiality – Encryption of packets to prevent snooping by an unauthorized source." + +#: ../../configuration/container/index.rst:12 +#: ../../configuration/firewall/zone.rst:47 +#: ../../configuration/interfaces/bonding.rst:17 +#: ../../configuration/interfaces/bridge.rst:21 +#: ../../configuration/interfaces/dummy.rst:28 +#: ../../configuration/interfaces/ethernet.rst:14 +#: ../../configuration/interfaces/geneve.rst:39 +#: ../../configuration/interfaces/l2tpv3.rst:31 +#: ../../configuration/interfaces/loopback.rst:26 +#: ../../configuration/interfaces/macsec.rst:20 +#: ../../configuration/interfaces/pppoe.rst:59 +#: ../../configuration/interfaces/pseudo-ethernet.rst:45 +#: ../../configuration/interfaces/sstp-client.rst:20 +#: ../../configuration/interfaces/tunnel.rst:119 +#: ../../configuration/interfaces/virtual-ethernet.rst:17 +#: ../../configuration/interfaces/vxlan.rst:39 +#: ../../configuration/interfaces/wireless.rst:30 +#: ../../configuration/interfaces/wwan.rst:16 +#: ../../configuration/loadbalancing/reverse-proxy.rst:13 +#: ../../configuration/nat/nat44.rst:681 +#: ../../configuration/policy/access-list.rst:13 +#: ../../configuration/policy/as-path-list.rst:10 +#: ../../configuration/policy/community-list.rst:10 +#: ../../configuration/policy/extcommunity-list.rst:10 +#: ../../configuration/policy/large-community-list.rst:10 +#: ../../configuration/policy/local-route.rst:9 +#: ../../configuration/policy/prefix-list.rst:16 +#: ../../configuration/policy/route-map.rst:10 +#: ../../configuration/protocols/bfd.rst:143 +#: ../../configuration/protocols/bgp.rst:164 +#: ../../configuration/protocols/igmp.rst:186 +#: ../../configuration/protocols/isis.rst:28 +#: ../../configuration/protocols/ospf.rst:22 +#: ../../configuration/protocols/ospf.rst:1076 +#: ../../configuration/protocols/rpki.rst:104 +#: ../../configuration/service/broadcast-relay.rst:18 +#: ../../configuration/service/conntrack-sync.rst:38 +#: ../../configuration/service/console-server.rst:21 +#: ../../configuration/service/dhcp-relay.rst:19 +#: ../../configuration/service/dhcp-relay.rst:137 +#: ../../configuration/service/dhcp-server.rst:22 +#: ../../configuration/service/dhcp-server.rst:586 +#: ../../configuration/service/dns.rst:8 +#: ../../configuration/service/dns.rst:214 +#: ../../configuration/service/https.rst:14 +#: ../../configuration/service/ipoe-server.rst:28 +#: ../../configuration/service/lldp.rst:36 +#: ../../configuration/service/mdns.rst:18 +#: ../../configuration/service/ntp.rst:40 +#: ../../configuration/service/pppoe-server.rst:17 +#: ../../configuration/service/salt-minion.rst:25 +#: ../../configuration/service/ssh.rst:36 +#: ../../configuration/service/tftp-server.rst:14 +#: ../../configuration/service/webproxy.rst:21 +#: ../../configuration/system/default-route.rst:12 +#: ../../configuration/system/flow-accounting.rst:43 +#: ../../configuration/system/lcd.rst:17 +#: ../../configuration/system/login.rst:241 +#: ../../configuration/system/login.rst:310 +#: ../../configuration/system/sflow.rst:12 +#: ../../configuration/vpn/dmvpn.rst:38 +#: ../../configuration/vpn/dmvpn.rst:182 +#: ../../configuration/vpn/openconnect.rst:21 +#: ../../configuration/vpn/sstp.rst:65 +#: ../../configuration/vrf/index.rst:16 +#: ../../configuration/vrf/index.rst:253 +#: ../../configuration/vrf/index.rst:286 +#: ../../configuration/vrf/index.rst:434 +msgid "Configuration" +msgstr "Configuration" + +#: ../../configuration/protocols/babel.rst:188 +#: ../../configuration/protocols/ospf.rst:1314 +#: ../../configuration/protocols/pim6.rst:78 +#: ../../configuration/protocols/rip.rst:239 +#: ../../configuration/protocols/segment-routing.rst:187 +#: ../../configuration/system/login.rst:279 +#: ../../configuration/system/login.rst:348 +msgid "Configuration Example" +msgstr "Configuration Example" + +#: ../../configuration/nat/nat44.rst:313 +#: ../../configuration/nat/nat66.rst:109 +msgid "Configuration Examples" +msgstr "Configuration Examples" + +#: ../../configuration/index.rst:3 +msgid "Configuration Guide" +msgstr "Configuration Guide" + +#: ../../configuration/protocols/mpls.rst:70 +msgid "Configuration Options" +msgstr "Configuration Options" + +#: ../../configuration/vpn/ipsec.rst:284 +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 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:" + +#: ../../configuration/vpn/rsa-keys.rst:26 +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 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:" + +#: ../../configuration/vrf/index.rst:428 +msgid "Configuration for these exported routes must, at a minimum, specify these two parameters." +msgstr "Configuration for these exported routes must, at a minimum, specify these two parameters." + +#: ../../configuration/system/default-route.rst:39 +msgid "Configuration of :ref:`routing-static`" +msgstr "Configuration of :ref:`routing-static`" + +#: ../../configuration/service/dhcp-server.rst:430 +msgid "Configuration of a DHCP failover pair" +msgstr "Configuration of a DHCP failover pair" + +#: ../../configuration/vrf/index.rst:436 +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 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." + +#: ../../configuration/protocols/static.rst:166 +#: ../../configuration/system/conntrack.rst:12 +msgid "Configure" +msgstr "Configure" + +#: ../../configuration/protocols/bfd.rst:22 +msgid "Configure BFD" +msgstr "Configure BFD" + +#: ../../configuration/service/dns.rst:245 +msgid "Configure DNS `<record>` which should be updated. This can be set multiple times." +msgstr "Configure DNS `<record>` which should be updated. This can be set multiple times." + +#: ../../configuration/service/dns.rst:240 +msgid "Configure DNS `<zone>` to be updated." +msgstr "Configure DNS `<zone>` to be updated." + +#: ../../configuration/interfaces/geneve.rst:53 +msgid "Configure GENEVE tunnel far end/remote tunnel endpoint." +msgstr "Configure GENEVE tunnel far end/remote tunnel endpoint." + +#: ../../configuration/protocols/ospf.rst:511 +#: ../../configuration/protocols/ospf.rst:1223 +msgid "Configure Graceful Restart :rfc:`3623` helper support. By default, helper support is disabled for all neighbours. This config enables/disables helper support on this router for all neighbours." +msgstr "Configure Graceful Restart :rfc:`3623` helper support. By default, helper support is disabled for all neighbours. This config enables/disables helper support on this router for all neighbours." + +#: ../../configuration/protocols/ospf.rst:502 +#: ../../configuration/protocols/ospf.rst:1214 +msgid "Configure Graceful Restart :rfc:`3623` restarting support. When enabled, the default grace period is 120 seconds." +msgstr "Configure Graceful Restart :rfc:`3623` restarting support. When enabled, the default grace period is 120 seconds." + +#: ../../configuration/service/dhcp-relay.rst:40 +msgid "Configure IP address of the DHCP `<server>` which will handle the relayed packets." +msgstr "Configure IP address of the DHCP `<server>` which will handle the relayed packets." + +#: ../../configuration/vpn/sstp.rst:203 +msgid "Configure RADIUS `<server>` and its required port for authentication requests." +msgstr "Configure RADIUS `<server>` and its required port for authentication requests." + +#: ../../configuration/vpn/sstp.rst:207 +msgid "Configure RADIUS `<server>` and its required shared `<secret>` for communicating with the RADIUS server." +msgstr "Configure RADIUS `<server>` and its required shared `<secret>` for communicating with the RADIUS server." + +#: ../../configuration/nat/nat44.rst:210 +msgid "Configure SNAT rule (40) to only NAT packets with a destination address of 192.0.2.1." +msgstr "Configure SNAT rule (40) to only NAT packets with a destination address of 192.0.2.1." + +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +#: ../../_include/interface-mtu.txt:4 +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 "Configure :abbr:`MTU (Maximum Transmission Unit)` on given `<interface>`. It is the size (in bytes) of the largest ethernet frame sent on this link." + +#: ../../configuration/system/login.rst:373 +msgid "Configure `<message>` which is shown after user has logged in to the system." +msgstr "Configure `<message>` which is shown after user has logged in to the system." + +#: ../../configuration/system/login.rst:368 +msgid "Configure `<message>` which is shown during SSH connect and before a user is logged in." +msgstr "Configure `<message>` which is shown during SSH connect and before a user is logged in." + +#: ../../configuration/service/dns.rst:328 +msgid "Configure `<password>` used when authenticating the update request for DynDNS service identified by `<service>`." +msgstr "Configure `<password>` used when authenticating the update request for DynDNS service identified by `<service>`." + +#: ../../configuration/service/dns.rst:321 +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 "Configure `<username>` used when authenticating the update request for DynDNS service identified by `<service>`. For Namecheap, set the <domain> you wish to update." + +#: ../../configuration/system/flow-accounting.rst:158 +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 "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." + +#: ../../configuration/protocols/bfd.rst:154 +#: ../../configuration/protocols/bfd.rst:167 +msgid "Configure a static route for <subnet> using gateway <address> , use source address to indentify the peer when is multi-hop session and the gateway address as BFD peer destination address." +msgstr "Configure a static route for <subnet> using gateway <address> , use source address to indentify the peer when is multi-hop session and the gateway address as BFD peer destination address." + +#: ../../configuration/protocols/bfd.rst:148 +#: ../../configuration/protocols/bfd.rst:161 +msgid "Configure a static route for <subnet> using gateway <address> and use the gateway address as BFD peer destination address." +msgstr "Configure a static route for <subnet> using gateway <address> and use the gateway address as BFD peer destination address." + +#: ../../configuration/system/flow-accounting.rst:106 +msgid "Configure address of NetFlow collector. NetFlow server at `<address>` can be both listening on an IPv4 or IPv6 address." +msgstr "Configure address of NetFlow collector. NetFlow server at `<address>` can be both listening on an IPv4 or IPv6 address." + +#: ../../configuration/system/sflow.rst:45 +msgid "Configure address of sFlow collector. sFlow server at <address> can be both listening on an IPv4 or IPv6 address." +msgstr "Configure address of sFlow collector. sFlow server at <address> can be both listening on an IPv4 or IPv6 address." + +#: ../../configuration/system/flow-accounting.rst:148 +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 "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!" + +#: ../../configuration/system/sflow.rst:21 +msgid "Configure agent IP address associated with this interface." +msgstr "Configure agent IP address associated with this interface." + +#: ../../configuration/protocols/ospf.rst:481 +msgid "Configure aggregation delay timer interval." +msgstr "Configure aggregation delay timer interval." + +#: ../../configuration/vpn/openconnect.rst:278 +msgid "Configure an accounting server and enable accounting with:" +msgstr "Configure an accounting server and enable accounting with:" + +#: ../../configuration/system/sflow.rst:30 +msgid "Configure and enable collection of flow information for the interface identified by <interface>." +msgstr "Configure and enable collection of flow information for the interface identified by <interface>." + +#: ../../configuration/system/flow-accounting.rst:50 +msgid "Configure and enable collection of flow information for the interface identified by `<interface>`." +msgstr "Configure and enable collection of flow information for the interface identified by `<interface>`." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:114 +msgid "Configure backend `<name>` mode TCP or HTTP" +msgstr "Configure backend `<name>` mode TCP or HTTP" + +#: ../../configuration/service/console-server.rst:49 +msgid "Configure either one or two stop bits. This defaults to one stop bits if left unconfigured." +msgstr "Configure either one or two stop bits. This defaults to one stop bits if left unconfigured." + +#: ../../configuration/service/console-server.rst:31 +msgid "Configure either seven or eight data bits. This defaults to eight data bits if left unconfigured." +msgstr "Configure either seven or eight data bits. This defaults to eight data bits if left unconfigured." + +#: ../../configuration/interfaces/bridge.rst:46 +msgid "Configure individual bridge port `<priority>`." +msgstr "Configure individual bridge port `<priority>`." + +#: ../../_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 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:59 +#: ../../_include/interface-ipv6.txt:48 +#: ../../configuration/interfaces/pppoe.rst:210 +#: ../../configuration/interfaces/pppoe.rst:256 +#: ../../_include/interface-ip.txt:59 +#: ../../_include/interface-ipv6.txt:48 +#: ../../_include/interface-ip.txt:59 +#: ../../_include/interface-ipv6.txt:48 +#: ../../configuration/interfaces/sstp-client.rst:95 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:59 +#: ../../_include/interface-ipv6.txt:48 +#: ../../_include/interface-ip.txt:59 +#: ../../_include/interface-ipv6.txt:48 +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 "Configure interface-specific Host/Router behaviour. If set, the interface will switch to host mode and IPv6 forwarding will be disabled on this interface." + +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address.txt:3 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +#: ../../_include/interface-address-with-dhcp.txt:5 +msgid "Configure interface `<interface>` with one or more interface addresses." +msgstr "Configure interface `<interface>` with one or more interface addresses." + +#: ../../configuration/service/snmp.rst:148 +msgid "Configure new SNMP user named \"vyos\" with password \"vyos12345678\"" +msgstr "Configure new SNMP user named \"vyos\" with password \"vyos12345678\"" + +#: ../../configuration/protocols/failover.rst:17 +msgid "Configure next-hop `<address>` and `<target-address>` for an IPv4 static route. Specify the target IPv4 address for health checking." +msgstr "Configure next-hop `<address>` and `<target-address>` for an IPv4 static route. Specify the target IPv4 address for health checking." + +#: ../../configuration/protocols/static.rst:24 +msgid "Configure next-hop `<address>` for an IPv4 static route. Multiple static routes can be created." +msgstr "Configure next-hop `<address>` for an IPv4 static route. Multiple static routes can be created." + +#: ../../configuration/protocols/static.rst:44 +msgid "Configure next-hop `<address>` for an IPv6 static route. Multiple static routes can be created." +msgstr "Configure next-hop `<address>` for an IPv6 static route. Multiple static routes can be created." + +#: ../../configuration/system/option.rst:95 +msgid "Configure one of the predefined system performance profiles." +msgstr "Configure one of the predefined system performance profiles." + +#: ../../configuration/service/ntp.rst:55 +msgid "Configure one or more attributes to the given NTP server." +msgstr "Configure one or more attributes to the given NTP server." + +#: ../../configuration/service/ntp.rst:44 +msgid "Configure one or more servers for synchronisation. Server name can be either an IP address or :abbr:`FQDN (Fully Qualified Domain Name)`." +msgstr "Configure one or more servers for synchronisation. Server name can be either an IP address or :abbr:`FQDN (Fully Qualified Domain Name)`." + +#: ../../configuration/service/dns.rst:251 +msgid "Configure optional TTL value on the given resource record. This defaults to 600 seconds." +msgstr "Configure optional TTL value on the given resource record. This defaults to 600 seconds." + +#: ../../configuration/interfaces/ethernet.rst:28 +msgid "Configure physical interface duplex setting." +msgstr "Configure physical interface duplex setting." + +#: ../../configuration/interfaces/ethernet.rst:39 +msgid "Configure physical interface speed setting." +msgstr "Configure physical interface speed setting." + +#: ../../_include/interface-mirror.txt:16 +#: ../../_include/interface-mirror.txt:16 +#: ../../_include/interface-mirror.txt:16 +msgid "Configure port mirroring for `interface` inbound traffic and copy the traffic to `monitor-interface`" +msgstr "Configure port mirroring for `interface` inbound traffic and copy the traffic to `monitor-interface`" + +#: ../../_include/interface-mirror.txt:28 +#: ../../_include/interface-mirror.txt:28 +#: ../../_include/interface-mirror.txt:28 +msgid "Configure port mirroring for `interface` outbound traffic and copy the traffic to `monitor-interface`" +msgstr "Configure port mirroring for `interface` outbound traffic and copy the traffic to `monitor-interface`" + +#: ../../configuration/interfaces/vxlan.rst:59 +msgid "Configure port number of remote VXLAN endpoint." +msgstr "Configure port number of remote VXLAN endpoint." + +#: ../../configuration/system/syslog.rst:73 +msgid "Configure protocol used for communication to remote syslog host. This can be either UDP or TCP." +msgstr "Configure protocol used for communication to remote syslog host. This can be either UDP or TCP." + +#: ../../configuration/system/proxy.rst:18 +msgid "Configure proxy port if it does not listen to the default port 80." +msgstr "Configure proxy port if it does not listen to the default port 80." + +#: ../../configuration/system/sflow.rst:16 +msgid "Configure sFlow agent IPv4 or IPv6 address" +msgstr "Configure sFlow agent IPv4 or IPv6 address" + +#: ../../configuration/system/sflow.rst:37 +msgid "Configure schedule counter-polling in seconds (default: 30)" +msgstr "Configure schedule counter-polling in seconds (default: 30)" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:36 +msgid "Configure service `<name>` mode TCP or HTTP" +msgstr "Configure service `<name>` mode TCP or HTTP" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:41 +msgid "Configure service `<name>` to use the backend <name>" +msgstr "Configure service `<name>` to use the backend <name>" + +#: ../../configuration/system/login.rst:392 +msgid "Configure session timeout after which the user will be logged out." +msgstr "Configure session timeout after which the user will be logged out." + +#: ../../configuration/system/host-name.rst:41 +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 "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." + +#: ../../configuration/service/dns.rst:234 +msgid "Configure the DNS `<server>` IP/FQDN used when updating this dynamic assignment." +msgstr "Configure the DNS `<server>` IP/FQDN used when updating this dynamic assignment." + +#: ../../configuration/service/tftp-server.rst:27 +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 "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." + +#: ../../configuration/system/conntrack.rst:43 +msgid "Configure the connection tracking protocol helper modules. All modules are enable by default." +msgstr "Configure the connection tracking protocol helper modules. All modules are enable by default." + +#: ../../configuration/system/login.rst:252 +msgid "Configure the discrete port under which the RADIUS server can be reached." +msgstr "Configure the discrete port under which the RADIUS server can be reached." + +#: ../../configuration/system/login.rst:321 +msgid "Configure the discrete port under which the TACACS server can be reached." +msgstr "Configure the discrete port under which the TACACS server can be reached." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:172 +msgid "Configure the load-balancing reverse-proxy service for HTTP." +msgstr "Configure the load-balancing reverse-proxy service for HTTP." + +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +#: ../../_include/interface-mac.txt:4 +msgid "Configure user defined :abbr:`MAC (Media Access Control)` address on given `<interface>`." +msgstr "Configure user defined :abbr:`MAC (Media Access Control)` address on given `<interface>`." + +#: ../../configuration/vrf/index.rst:28 +msgid "Configured routing table `<id>` is used by VRF `<name>`." +msgstr "Configured routing table `<id>` is used by VRF `<name>`." + +#: ../../configuration/trafficpolicy/index.rst:262 +msgid "Configured value" +msgstr "Configured value" + +#: ../../configuration/protocols/bgp.rst:455 +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 "Configures the BGP speaker so that it only accepts inbound connections from, but does not initiate outbound connections to the peer or peer group." + +#: ../../configuration/vpn/openconnect.rst:272 +msgid "Configuring RADIUS accounting" +msgstr "Configuring RADIUS accounting" + +#: ../../configuration/service/tftp-server.rst:39 +msgid "Configuring a listen-address is essential for the service to work." +msgstr "Configuring a listen-address is essential for the service to work." + +#: ../../configuration/interfaces/pppoe.rst:296 +#: ../../configuration/interfaces/sstp-client.rst:140 +msgid "Connect/Disconnect" +msgstr "Connect/Disconnect" + +#: ../../configuration/vpn/sstp.rst:144 +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 "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." + +#: ../../configuration/protocols/rpki.rst:129 +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 "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." + +#: ../../configuration/system/conntrack.rst:4 +msgid "Conntrack" +msgstr "Conntrack" + +#: ../../configuration/service/conntrack-sync.rst:5 +msgid "Conntrack Sync" +msgstr "Conntrack Sync" + +#: ../../configuration/service/conntrack-sync.rst:None +msgid "Conntrack Sync Example" +msgstr "Conntrack Sync Example" + +#: ../../configuration/system/syslog.rst:21 +msgid "Console" +msgstr "Console" + +#: ../../configuration/service/console-server.rst:5 +msgid "Console Server" +msgstr "Console Server" + +#: ../../configuration/container/index.rst:106 +msgid "Constrain the memory available to the container." +msgstr "Constrain the memory available to the container." + +#: ../../configuration/container/index.rst:5 +msgid "Container" +msgstr "Container" + +#: ../../configuration/nat/nat66.rst:98 +msgid "Convert the address prefix of a single `fc00::/64` network to `fc01::/64`" +msgstr "Convert the address prefix of a single `fc00::/64` network to `fc01::/64`" + +#: ../../configuration/nat/nat66.rst:80 +msgid "Convert the address prefix of a single `fc01::/64` network to `fc00::/64`" +msgstr "Convert the address prefix of a single `fc01::/64` network to `fc00::/64`" + +#: ../../configuration/interfaces/wireguard.rst:255 +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 "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," + +#: ../../configuration/interfaces/wireless.rst:49 +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 "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." + +#: ../../configuration/policy/community-list.rst:17 +msgid "Creat community-list policy identified by name <text>." +msgstr "Creat community-list policy identified by name <text>." + +#: ../../configuration/policy/extcommunity-list.rst:17 +msgid "Creat extcommunity-list policy identified by name <text>." +msgstr "Creat extcommunity-list policy identified by name <text>." + +#: ../../configuration/service/dhcp-server.rst:118 +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 "Create DHCP address range with a range id of `<n>`. DHCP leases are taken from this pool. The pool starts at address `<address>`." + +#: ../../configuration/service/dhcp-server.rst:124 +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 "Create DHCP address range with a range id of `<n>`. DHCP leases are taken from this pool. The pool stops with address `<address>`." + +#: ../../configuration/service/dhcp-server.rst:26 +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 "Create DNS record per client lease, by adding clients to /etc/hosts file. Entry will have format: `<shared-network-name>_<hostname>.<domain-name>`" + +#: ../../configuration/vpn/sstp.rst:70 +msgid "Create `<user>` for local authentication on this system. The users password will be set to `<pass>`." +msgstr "Create `<user>` for local authentication on this system. The users password will be set to `<pass>`." + +#: ../../configuration/interfaces/bridge.rst:190 +msgid "Create a basic bridge" +msgstr "Create a basic bridge" + +#: ../../configuration/service/snmp.rst:252 +msgid "Create a file named ``VyOS-1.3.6.1.4.1.44641.ConfigMgmt-Commands`` using the following content:" +msgstr "Create a file named ``VyOS-1.3.6.1.4.1.44641.ConfigMgmt-Commands`` using the following content:" + +#: ../../configuration/loadbalancing/wan.rst:44 +msgid "Create a load balancing rule, it can be a number between 1 and 9999:" +msgstr "Create a load balancing rule, it can be a number between 1 and 9999:" + +#: ../../configuration/service/dhcp-server.rst:218 +msgid "Create a new DHCP static mapping named `<description>` which is valid for the host identified by its MAC `<address>`." +msgstr "Create a new DHCP static mapping named `<description>` which is valid for the host identified by its MAC `<address>`." + +#: ../../_include/interface-vlan-8021q.txt:26 +#: ../../_include/interface-vlan-8021q.txt:26 +#: ../../_include/interface-vlan-8021q.txt:26 +#: ../../_include/interface-vlan-8021q.txt:26 +#: ../../_include/interface-vlan-8021q.txt:26 +#: ../../_include/interface-vlan-8021q.txt:26 +msgid "Create a new VLAN interface on interface `<interface>` using the VLAN number provided via `<vlan-id>`." +msgstr "Create a new VLAN interface on interface `<interface>` using the VLAN number provided via `<vlan-id>`." + +#: ../../configuration/pki/index.rst:40 +#: ../../configuration/pki/index.rst:45 +msgid "Create a new :abbr:`CA (Certificate Authority)` and output the CAs public and private key on the console." +msgstr "Create a new :abbr:`CA (Certificate Authority)` and output the CAs public and private key on the console." + +#: ../../configuration/pki/index.rst:67 +#: ../../configuration/pki/index.rst:71 +msgid "Create a new public/private keypair and output the certificate on the console." +msgstr "Create a new public/private keypair and output the certificate on the console." + +#: ../../configuration/pki/index.rst:89 +#: ../../configuration/pki/index.rst:94 +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 "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." + +#: ../../configuration/pki/index.rst:77 +#: ../../configuration/pki/index.rst:82 +msgid "Create a new self-signed certificate. The public/private is then shown on the console." +msgstr "Create a new self-signed certificate. The public/private is then shown on the console." + +#: ../../configuration/pki/index.rst:52 +msgid "Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it using the private key referenced by `ca-name`." +msgstr "Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it using the private key referenced by `ca-name`." + +#: ../../configuration/pki/index.rst:57 +msgid "Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it using the private key referenced by `name`." +msgstr "Create a new subordinate :abbr:`CA (Certificate Authority)` and sign it using the private key referenced by `name`." + +#: ../../configuration/protocols/bgp.rst:198 +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 "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." + +#: ../../configuration/protocols/bgp.rst:205 +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 "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." + +#: ../../configuration/system/host-name.rst:58 +msgid "Create a static hostname mapping which will always resolve the name `<hostname>` to IP address `<address>`." +msgstr "Create a static hostname mapping which will always resolve the name `<hostname>` to IP address `<address>`." + +#: ../../configuration/policy/as-path-list.rst:17 +msgid "Create as-path-policy identified by name <text>." +msgstr "Create as-path-policy identified by name <text>." + +#: ../../configuration/policy/large-community-list.rst:17 +msgid "Create large-community-list policy identified by name <text>." +msgstr "Create large-community-list policy identified by name <text>." + +#: ../../configuration/system/host-name.rst:64 +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 "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." + +#: ../../configuration/vrf/index.rst:23 +msgid "Create new VRF instance with `<name>`. The name is used when placing individual interfaces into the VRF." +msgstr "Create new VRF instance with `<name>`. The name is used when placing individual interfaces into the VRF." + +#: ../../configuration/service/dns.rst:221 +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 "Create new :rfc:`2136` DNS update configuration which will update the IP address assigned to `<interface>` on the service you configured under `<service-name>`." + +#: ../../configuration/system/login.rst:21 +msgid "Create new system user with username `<name>` and real-name specified by `<string>`." +msgstr "Create new system user with username `<name>` and real-name specified by `<string>`." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:31 +msgid "Create service `<name>` to listen on <port>" +msgstr "Create service `<name>` to listen on <port>" + +#: ../../configuration/container/index.rst:132 +msgid "Creates a named container network" +msgstr "Creates a named container network" + +#: ../../configuration/vpn/dmvpn.rst:83 +msgid "Creates static peer mapping of protocol-address to :abbr:`NBMA (Non-broadcast multiple-access network)` address." +msgstr "Creates static peer mapping of protocol-address to :abbr:`NBMA (Non-broadcast multiple-access network)` address." + +#: ../../configuration/interfaces/bridge.rst:192 +msgid "Creating a bridge interface is very simple. In this example, we will have:" +msgstr "Creating a bridge interface is very simple. In this example, we will have:" + +#: ../../configuration/trafficpolicy/index.rst:335 +msgid "Creating a traffic policy" +msgstr "Creating a traffic policy" + +#: ../../configuration/system/syslog.rst:178 +msgid "Critical" +msgstr "Critical" + +#: ../../configuration/system/syslog.rst:178 +msgid "Critical conditions - e.g. hard drive errors." +msgstr "Critical conditions - e.g. hard drive errors." + +#: ../../configuration/system/lcd.rst:33 +msgid "Crystalfontz CFA-533" +msgstr "Crystalfontz CFA-533" + +#: ../../configuration/system/lcd.rst:35 +msgid "Crystalfontz CFA-631" +msgstr "Crystalfontz CFA-631" + +#: ../../configuration/system/lcd.rst:37 +msgid "Crystalfontz CFA-633" +msgstr "Crystalfontz CFA-633" + +#: ../../configuration/system/lcd.rst:39 +msgid "Crystalfontz CFA-635" +msgstr "Crystalfontz CFA-635" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Cur Hop Limit" +msgstr "Cur Hop Limit" + +#: ../../configuration/vpn/dmvpn.rst:120 +msgid "Currently does not do much as caching is not implemented." +msgstr "Currently does not do much as caching is not implemented." + +#: ../../configuration/vrf/index.rst:86 +msgid "Currently dynamic routing is supported for the following protocols:" +msgstr "Currently dynamic routing is supported for the following protocols:" + +#: ../../configuration/system/syslog.rst:32 +msgid "Custom File" +msgstr "Custom File" + +#: ../../configuration/firewall/general.rst:77 +msgid "Custom firewall chains can be created, with commands ``set firewall [ipv4 | ipv6] [name | ipv6-name] <name> ...``. In order to use such custom chain, a rule with **action jump**, and the appropiate **target** should be defined in a base chain." +msgstr "Custom firewall chains can be created, with commands ``set firewall [ipv4 | ipv6] [name | ipv6-name] <name> ...``. In order to use such custom chain, a rule with **action jump**, and the appropiate **target** should be defined in a base chain." + +#: ../../configuration/highavailability/index.rst:373 +msgid "Custom health-check script allows checking real-server availability" +msgstr "Custom health-check script allows checking real-server availability" + +#: ../../configuration/system/conntrack.rst:167 +msgid "Customized ignore rules, based on a packet and flow selector." +msgstr "Customized ignore rules, based on a packet and flow selector." + +#: ../../configuration/interfaces/openvpn.rst:685 +msgid "DCO can be enabled for both new and existing tunnels,VyOS adds an option in each tunnel configuration where we can enable this function .The current best practice is to create a new tunnel with DCO to minimize the chance of problems with existing clients." +msgstr "DCO can be enabled for both new and existing tunnels,VyOS adds an option in each tunnel configuration where we can enable this function .The current best practice is to create a new tunnel with DCO to minimize the chance of problems with existing clients." + +#: ../../configuration/interfaces/openvpn.rst:681 +msgid "DCO support is a per-tunnel option and it is not automatically enabled by default for new or upgraded tunnels. Existing tunnels will continue to function as they have in the past." +msgstr "DCO support is a per-tunnel option and it is not automatically enabled by default for new or upgraded tunnels. Existing tunnels will continue to function as they have in the past." + +#: ../../configuration/service/dhcp-relay.rst:5 +msgid "DHCP Relay" +msgstr "DHCP Relay" + +#: ../../configuration/service/dhcp-server.rst:5 +msgid "DHCP Server" +msgstr "DHCP Server" + +#: ../../configuration/service/dhcp-server.rst:384 +msgid "DHCP failover parameters" +msgstr "DHCP failover parameters" + +#: ../../configuration/service/dhcp-server.rst:374 +msgid "DHCP lease range" +msgstr "DHCP lease range" + +#: ../../configuration/service/dhcp-server.rst:436 +msgid "DHCP range spans from `192.168.189.10` - `192.168.189.250`" +msgstr "DHCP range spans from `192.168.189.10` - `192.168.189.250`" + +#: ../../configuration/service/dhcp-relay.rst:96 +#: ../../configuration/service/dhcp-relay.rst:96 +msgid "DHCP relay example" +msgstr "DHCP relay example" + +#: ../../configuration/service/dhcp-relay.rst:88 +msgid "DHCP server is located at IPv4 address 10.0.1.4 on ``eth2``." +msgstr "DHCP server is located at IPv4 address 10.0.1.4 on ``eth2``." + +#: ../../configuration/service/dhcp-server.rst:654 +msgid "DHCPv6 address pools must be configured for the system to act as a DHCPv6 server. The following example describes a common scenario." +msgstr "DHCPv6 address pools must be configured for the system to act as a DHCPv6 server. The following example describes a common scenario." + +#: ../../configuration/service/dhcp-relay.rst:182 +#: ../../configuration/service/dhcp-relay.rst:182 +msgid "DHCPv6 relay example" +msgstr "DHCPv6 relay example" + +#: ../../configuration/service/dhcp-relay.rst:174 +msgid "DHCPv6 requests are received by the router on `listening interface` ``eth1``" +msgstr "DHCPv6 requests are received by the router on `listening interface` ``eth1``" + +#: ../../configuration/nat/nat44.rst:735 +msgid "DH Group 14" +msgstr "DH Group 14" + +#: ../../configuration/vpn/dmvpn.rst:5 +msgid "DMVPN" +msgstr "DMVPN" + +#: ../../configuration/vpn/dmvpn.rst:171 +msgid "DMVPN example network" +msgstr "DMVPN example network" + +#: ../../configuration/vpn/dmvpn.rst:171 +msgid "DMVPN network" +msgstr "DMVPN network" + +#: ../../configuration/vpn/dmvpn.rst:26 +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 "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." + +#: ../../configuration/nat/nat44.rst:89 +msgid "DNAT" +msgstr "DNAT" + +#: ../../configuration/nat/nat66.rst:53 +msgid "DNAT66" +msgstr "DNAT66" + +#: ../../configuration/nat/nat44.rst:494 +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 "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." + +#: ../../configuration/nat/nat44.rst:268 +msgid "DNAT rule 10 replaces the destination address of an inbound packet with 192.0.2.10" +msgstr "DNAT rule 10 replaces the destination address of an inbound packet with 192.0.2.10" + +#: ../../configuration/service/router-advert.rst:1 +msgid "DNSSL" +msgstr "DNSSL" + +#: ../../configuration/service/dns.rst:5 +msgid "DNS Forwarding" +msgstr "DNS Forwarding" + +#: ../../configuration/system/name-server.rst:12 +#: ../../configuration/system/name-server.rst:17 +msgid "DNS name servers" +msgstr "DNS name servers" + +#: ../../configuration/service/router-advert.rst:1 +msgid "DNS search list to advertise" +msgstr "DNS search list to advertise" + +#: ../../configuration/service/dhcp-server.rst:294 +msgid "DNS server IPv4 address" +msgstr "DNS server IPv4 address" + +#: ../../configuration/service/dhcp-server.rst:661 +msgid "DNS server is located at ``2001:db8::ffff``" +msgstr "DNS server is located at ``2001:db8::ffff``" + +#: ../../configuration/trafficpolicy/index.rst:259 +msgid "DSCP values as per :rfc:`2474` and :rfc:`4595`:" +msgstr "DSCP values as per :rfc:`2474` and :rfc:`4595`:" + +#: ../../configuration/interfaces/wireless.rst:182 +msgid "DSSS/CCK Mode in 40 MHz, this sets ``[DSSS_CCK-40]``" +msgstr "DSSS/CCK Mode in 40 MHz, this sets ``[DSSS_CCK-40]``" + +#: ../../configuration/firewall/general.rst:714 +#: ../../configuration/firewall/general-legacy.rst:480 +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 "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." + +#: ../../configuration/system/syslog.rst:191 +msgid "Debug" +msgstr "Debug" + +#: ../../configuration/system/syslog.rst:191 +msgid "Debug-level messages - Messages that contain information normally of use only when debugging a program." +msgstr "Debug-level messages - Messages that contain information normally of use only when debugging a program." + +#: ../../configuration/trafficpolicy/index.rst:217 +msgid "Default" +msgstr "Default" + +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +#: ../../_include/interface-ipv6.txt:94 +msgid "Default: 1" +msgstr "Default: 1" + +#: ../../configuration/protocols/failover.rst:58 +msgid "Default 1." +msgstr "Default 1." + +#: ../../configuration/system/default-route.rst:5 +msgid "Default Gateway/Route" +msgstr "Default Gateway/Route" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Default Router Preference" +msgstr "Default Router Preference" + +#: ../../configuration/vpn/sstp.rst:190 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:433 +msgid "Default gateway and DNS server is at `192.0.2.254`" +msgstr "Default gateway and DNS server is at `192.0.2.254`" + +#: ../../configuration/container/index.rst:108 +msgid "Default is 512 MB. Use 0 MB for unlimited memory." +msgstr "Default is 512 MB. Use 0 MB for unlimited memory." + +#: ../../configuration/protocols/failover.rst:46 +msgid "Default is ``any-available``." +msgstr "Default is ``any-available``." + +#: ../../configuration/protocols/failover.rst:33 +msgid "Default is ``icmp``." +msgstr "Default is ``icmp``." + +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +#: ../../_include/interface-disable-link-detect.txt:7 +msgid "Default is to detects physical link state changes." +msgstr "Default is to detects physical link state changes." + +#: ../../configuration/service/webproxy.rst:52 +msgid "Default port is 3128." +msgstr "Default port is 3128." + +#: ../../configuration/service/webproxy.rst:294 +msgid "Defaults to 'uid'" +msgstr "Defaults to 'uid'" + +#: ../../configuration/service/conntrack-sync.rst:85 +msgid "Defaults to 225.0.0.50." +msgstr "Defaults to 225.0.0.50." + +#: ../../configuration/system/option.rst:68 +msgid "Defaults to ``us``." +msgstr "Defaults to ``us``." + +#: ../../configuration/system/conntrack.rst:51 +msgid "Define Conection Timeouts" +msgstr "Define Conection Timeouts" + +#: ../../configuration/service/lldp.rst:44 +msgid "Define IPv4/IPv6 management address transmitted via LLDP. Multiple addresses can be defined. Only addresses connected to the system will be transmitted." +msgstr "Define IPv4/IPv6 management address transmitted via LLDP. Multiple addresses can be defined. Only addresses connected to the system will be transmitted." + +#: ../../configuration/firewall/general.rst:225 +#: ../../configuration/firewall/general-legacy.rst:201 +msgid "Define a IPv4 or IPv6 Network group." +msgstr "Define a IPv4 or IPv6 Network group." + +#: ../../configuration/firewall/general.rst:201 +#: ../../configuration/firewall/general-legacy.rst:177 +msgid "Define a IPv4 or a IPv6 address group" +msgstr "Define a IPv4 or a IPv6 address group" + +#: ../../configuration/firewall/zone.rst:59 +msgid "Define a Zone" +msgstr "Define a Zone" + +#: ../../configuration/nat/nat44.rst:246 +msgid "Define a discrete source IP address of 100.64.0.1 for SNAT rule 20" +msgstr "Define a discrete source IP address of 100.64.0.1 for SNAT rule 20" + +#: ../../configuration/firewall/general.rst:306 +#: ../../configuration/firewall/general-legacy.rst:261 +msgid "Define a domain group." +msgstr "Define a domain group." + +#: ../../configuration/firewall/general.rst:288 +#: ../../configuration/firewall/general-legacy.rst:246 +msgid "Define a mac group." +msgstr "Define a mac group." + +#: ../../configuration/firewall/general.rst:268 +#: ../../configuration/firewall/general-legacy.rst:226 +msgid "Define a port group. A port name can be any name defined in /etc/services. e.g.: http" +msgstr "Define a port group. A port name can be any name defined in /etc/services. e.g.: http" + +#: ../../configuration/service/ssh.rst:50 +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 "Define allowed ciphers used for the SSH connection. A number of allowed ciphers can be specified, use multiple occurrences to allow multiple ciphers." + +#: ../../configuration/firewall/general.rst:245 +msgid "Define an interface group. Wildcard are accepted too." +msgstr "Define an interface group. Wildcard are accepted too." + +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +#: ../../_include/interface-ip.txt:85 +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 "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." + +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +#: ../../_include/interface-ip.txt:69 +msgid "Define different modes for IP directed broadcast forwarding as described in :rfc:`1812` and :rfc:`2644`." +msgstr "Define different modes for IP directed broadcast forwarding as described in :rfc:`1812` and :rfc:`2644`." + +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +#: ../../_include/interface-ip.txt:121 +msgid "Define different modes for sending replies in response to received ARP requests that resolve local target IP addresses:" +msgstr "Define different modes for sending replies in response to received ARP requests that resolve local target IP addresses:" + +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +#: ../../_include/interface-ip.txt:101 +msgid "Define different restriction levels for announcing the local source IP address from IP packets in ARP requests sent on interface." +msgstr "Define different restriction levels for announcing the local source IP address from IP packets in ARP requests sent on interface." + +#: ../../configuration/firewall/general.rst:476 +#: ../../configuration/firewall/general-legacy.rst:361 +msgid "Define length of packet payload to include in netlink message. Only applicable if rule log is enable and log group is defined." +msgstr "Define length of packet payload to include in netlink message. Only applicable if rule log is enable and log group is defined." + +#: ../../configuration/firewall/general.rst:450 +#: ../../configuration/firewall/general-legacy.rst:347 +msgid "Define log-level. Only applicable if rule log is enable." +msgstr "Define log-level. Only applicable if rule log is enable." + +#: ../../configuration/firewall/general.rst:463 +#: ../../configuration/firewall/general-legacy.rst:354 +msgid "Define log group to send message to. Only applicable if rule log is enable." +msgstr "Define log group to send message to. Only applicable if rule log is enable." + +#: ../../configuration/firewall/general.rst:490 +#: ../../configuration/firewall/general-legacy.rst:369 +msgid "Define number of packets to queue inside the kernel before sending them to userspace. Only applicable if rule log is enable and log group is defined." +msgstr "Define number of packets to queue inside the kernel before sending them to userspace. Only applicable if rule log is enable and log group is defined." + +#: ../../configuration/protocols/rpki.rst:108 +msgid "Define the time interval to update the local cache" +msgstr "Define the time interval to update the local cache" + +#: ../../configuration/firewall/zone.rst:70 +msgid "Define the zone as a local zone. A local zone has no interfaces and will be applied to the router itself." +msgstr "Define the zone as a local zone. A local zone has no interfaces and will be applied to the router itself." + +#: ../../configuration/protocols/rpki.rst:114 +msgid "Defined the IPv4, IPv6 or FQDN and port number of the caching RPKI caching instance which is used." +msgstr "Defined the IPv4, IPv6 or FQDN and port number of the caching RPKI caching instance which is used." + +#: ../../configuration/protocols/igmp.rst:202 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:148 +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 "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." + +#: ../../configuration/protocols/static.rst:120 +#: ../../configuration/protocols/static.rst:133 +msgid "Defines blackhole distance for this route, routes with smaller administrative distance are elected prior to those with a higher distance." +msgstr "Defines blackhole distance for this route, routes with smaller administrative distance are elected prior to those with a higher distance." + +#: ../../configuration/protocols/static.rst:34 +#: ../../configuration/protocols/static.rst:54 +#: ../../configuration/protocols/static.rst:81 +#: ../../configuration/protocols/static.rst:101 +msgid "Defines next-hop distance for this route, routes with smaller administrative distance are elected prior to those with a higher distance." +msgstr "Defines next-hop distance for this route, routes with smaller administrative distance are elected prior to those with a higher distance." + +#: ../../configuration/protocols/failover.rst:31 +msgid "Defines protocols for checking ARP, ICMP, TCP" +msgstr "Defines protocols for checking ARP, ICMP, TCP" + +#: ../../configuration/vpn/sstp.rst:167 +msgid "Defines the maximum `<number>` of unanswered echo requests. Upon reaching the value `<number>`, the session will be reset." +msgstr "Defines the maximum `<number>` of unanswered echo requests. Upon reaching the value `<number>`, the session will be reset." + +#: ../../configuration/system/console.rst:21 +msgid "Defines the specified device as a system console. Available console devices can be (see completion helper):" +msgstr "Defines the specified device as a system console. Available console devices can be (see completion helper):" + +#: ../../configuration/protocols/bgp.rst:186 +msgid "Defining Peers" +msgstr "Defining Peers" + +#: ../../configuration/service/dhcp-server.rst:649 +msgid "Delegate prefixes from the range indicated by the start and stop qualifier." +msgstr "Delegate prefixes from the range indicated by the start and stop qualifier." + +#: ../../configuration/policy/route-map.rst:231 +msgid "Delete BGP communities matching the community-list." +msgstr "Delete BGP communities matching the community-list." + +#: ../../configuration/policy/route-map.rst:246 +msgid "Delete BGP communities matching the large-community-list." +msgstr "Delete BGP communities matching the large-community-list." + +#: ../../configuration/system/syslog.rst:240 +msgid "Delete Logs" +msgstr "Delete Logs" + +#: ../../configuration/policy/route-map.rst:226 +msgid "Delete all BGP communities" +msgstr "Delete all BGP communities" + +#: ../../configuration/policy/route-map.rst:241 +msgid "Delete all BGP large-communities" +msgstr "Delete all BGP large-communities" + +#: ../../configuration/system/default-route.rst:22 +msgid "Delete default route from the system." +msgstr "Delete default route from the system." + +#: ../../configuration/system/syslog.rst:244 +msgid "Deletes the specified user-defined file <text> in the /var/log/user directory" +msgstr "Deletes the specified user-defined file <text> in the /var/log/user directory" + +#: ../../configuration/interfaces/wireless.rst:161 +msgid "Depending on the location, not all of these channels may be available for use!" +msgstr "Depending on the location, not all of these channels may be available for use!" + +#: ../../configuration/service/router-advert.rst:1 +#: ../../configuration/service/router-advert.rst:1 +#: ../../configuration/system/syslog.rst:107 +#: ../../configuration/system/syslog.rst:167 +#: ../../configuration/trafficpolicy/index.rst:262 +msgid "Description" +msgstr "Description" + +#: ../../configuration/trafficpolicy/index.rst:366 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:485 +msgid "Despite the fact that AD is a superset of LDAP" +msgstr "Despite the fact that AD is a superset of LDAP" + +#: ../../configuration/nat/nat44.rst:261 +msgid "Destination Address" +msgstr "Destination Address" + +#: ../../configuration/nat/nat44.rst:492 +msgid "Destination NAT" +msgstr "Destination NAT" + +#: ../../configuration/nat/nat66.rst:90 +msgid "Destination Prefix" +msgstr "Destination Prefix" + +#: ../../configuration/protocols/ospf.rst:131 +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 "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`" + +#: ../../configuration/vpn/dmvpn.rst:100 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:141 +msgid "Device is incapable of 40 MHz, do not advertise. This sets ``[40-INTOLERANT]``" +msgstr "Device is incapable of 40 MHz, do not advertise. This sets ``[40-INTOLERANT]``" + +#: ../../configuration/nat/nat44.rst:63 +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 "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." + +#: ../../configuration/nat/nat44.rst:71 +#: ../../configuration/nat/nat66.rst:18 +msgid "Different NAT Types" +msgstr "Different NAT Types" + +#: ../../configuration/pki/index.rst:100 +msgid "Diffie-Hellman parameters" +msgstr "Diffie-Hellman parameters" + +#: ../../configuration/protocols/pim6.rst:37 +msgid "Disable MLD reports and query on the interface." +msgstr "Disable MLD reports and query on the interface." + +#: ../../configuration/vpn/sstp.rst:75 +msgid "Disable `<user>` account." +msgstr "Disable `<user>` account." + +#: ../../configuration/protocols/bfd.rst:57 +msgid "Disable a BFD peer" +msgstr "Disable a BFD peer" + +#: ../../configuration/container/index.rst:128 +msgid "Disable a container." +msgstr "Disable a container." + +#: ../../configuration/firewall/general.rst:1283 +msgid "Disable conntrack loose track option" +msgstr "Disable conntrack loose track option" + +#: ../../configuration/service/dhcp-relay.rst:50 +msgid "Disable dhcp-relay service." +msgstr "Disable dhcp-relay service." + +#: ../../configuration/service/dhcp-relay.rst:155 +msgid "Disable dhcpv6-relay service." +msgstr "Disable dhcpv6-relay service." + +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +#: ../../_include/interface-disable.txt:4 +msgid "Disable given `<interface>`. It will be placed in administratively down (``A/D``) state." +msgstr "Disable given `<interface>`. It will be placed in administratively down (``A/D``) state." + +#: ../../configuration/protocols/bgp.rst:616 +msgid "Disable immediate session reset if peer's connected link goes down." +msgstr "Disable immediate session reset if peer's connected link goes down." + +#: ../../configuration/service/ssh.rst:59 +msgid "Disable password based authentication. Login via SSH keys only. This hardens security!" +msgstr "Disable password based authentication. Login via SSH keys only. This hardens security!" + +#: ../../configuration/service/ssh.rst:64 +msgid "Disable the host validation through reverse DNS lookups - can speedup login time when reverse lookup is not possible." +msgstr "Disable the host validation through reverse DNS lookups - can speedup login time when reverse lookup is not possible." + +#: ../../configuration/interfaces/macsec.rst:69 +msgid "Disable the peer configuration" +msgstr "Disable the peer configuration" + +#: ../../configuration/protocols/static.rst:29 +msgid "Disable this IPv4 static route entry." +msgstr "Disable this IPv4 static route entry." + +#: ../../configuration/protocols/static.rst:49 +msgid "Disable this IPv6 static route entry." +msgstr "Disable this IPv6 static route entry." + +#: ../../configuration/protocols/igmp.rst:228 +msgid "Disable this service." +msgstr "Disable this service." + +#: ../../configuration/service/lldp.rst:54 +msgid "Disable transmit of LLDP frames on given `<interface>`. Useful to exclude certain interfaces from LLDP when ``all`` have been enabled." +msgstr "Disable transmit of LLDP frames on given `<interface>`. Useful to exclude certain interfaces from LLDP when ``all`` have been enabled." + +#: ../../configuration/interfaces/openvpn.rst:695 +msgid "Disabled by default - no kernel module loaded." +msgstr "Disabled by default - no kernel module loaded." + +#: ../../configuration/vpn/dmvpn.rst:117 +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 "Disables caching of peer information from forwarded NHRP Resolution Reply packets. This can be used to reduce memory consumption on big NBMA subnets." + +#: ../../configuration/protocols/static.rst:76 +msgid "Disables interface-based IPv4 static route." +msgstr "Disables interface-based IPv4 static route." + +#: ../../configuration/protocols/static.rst:96 +msgid "Disables interface-based IPv6 static route." +msgstr "Disables interface-based IPv6 static route." + +#: ../../configuration/protocols/igmp.rst:215 +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 "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." + +#: ../../configuration/service/webproxy.rst:322 +msgid "Disables web filtering without discarding configuration." +msgstr "Disables web filtering without discarding configuration." + +#: ../../configuration/service/webproxy.rst:93 +msgid "Disables web proxy transparent mode at a listening address." +msgstr "Disables web proxy transparent mode at a listening address." + +#: ../../configuration/service/router-advert.rst:73 +msgid "Disabling Advertisements" +msgstr "Disabling Advertisements" + +#: ../../configuration/highavailability/index.rst:70 +msgid "Disabling a VRRP group" +msgstr "Disabling a VRRP group" + +#: ../../configuration/interfaces/macsec.rst:199 +msgid "Disabling the encryption on the link by removing ``security encrypt`` will show the unencrypted but authenticated content." +msgstr "Disabling the encryption on the link by removing ``security encrypt`` will show the unencrypted but authenticated content." + +#: ../../configuration/interfaces/openvpn.rst:26 +msgid "Disadvantages are:" +msgstr "Disadvantages are:" + +#: ../../configuration/interfaces/wireless.rst:62 +msgid "Disassociate stations based on excessive transmission failures or other indications of connection loss." +msgstr "Disassociate stations based on excessive transmission failures or other indications of connection loss." + +#: ../../configuration/vrf/index.rst:142 +msgid "Display IPv4 routing table for VRF identified by `<name>`." +msgstr "Display IPv4 routing table for VRF identified by `<name>`." + +#: ../../configuration/vrf/index.rst:161 +msgid "Display IPv6 routing table for VRF identified by `<name>`." +msgstr "Display IPv6 routing table for VRF identified by `<name>`." + +#: ../../configuration/system/syslog.rst:198 +msgid "Display Logs" +msgstr "Display Logs" + +#: ../../configuration/system/login.rst:188 +msgid "Display OTP key for user" +msgstr "Display OTP key for user" + +#: ../../configuration/system/syslog.rst:222 +msgid "Display all authorization attempts of the specified image" +msgstr "Display all authorization attempts of the specified image" + +#: ../../configuration/protocols/static.rst:200 +msgid "Display all known ARP table entries on a given interface only (`eth1`):" +msgstr "Display all known ARP table entries on a given interface only (`eth1`):" + +#: ../../configuration/protocols/static.rst:188 +msgid "Display all known ARP table entries spanning across all interfaces" +msgstr "Display all known ARP table entries spanning across all interfaces" + +#: ../../configuration/system/syslog.rst:226 +msgid "Display contents of a specified user-defined log file of the specified image" +msgstr "Display contents of a specified user-defined log file of the specified image" + +#: ../../configuration/system/syslog.rst:220 +msgid "Display contents of all master log files of the specified image" +msgstr "Display contents of all master log files of the specified image" + +#: ../../configuration/system/syslog.rst:229 +msgid "Display last lines of the system log of the specified image" +msgstr "Display last lines of the system log of the specified image" + +#: ../../configuration/system/syslog.rst:224 +msgid "Display list of all user-defined log files of the specified image" +msgstr "Display list of all user-defined log files of the specified image" + +#: ../../configuration/system/syslog.rst:202 +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 "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" + +#: ../../configuration/service/lldp.rst:75 +msgid "Displays information about all neighbors discovered via LLDP." +msgstr "Displays information about all neighbors discovered via LLDP." + +#: ../../configuration/interfaces/pppoe.rst:286 +msgid "Displays queue information for a PPPoE interface." +msgstr "Displays queue information for a PPPoE interface." + +#: ../../configuration/vrf/index.rst:213 +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 "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." + +#: ../../configuration/system/host-name.rst:52 +msgid "Do *not* manually edit `/etc/hosts`. This file will automatically be regenerated on boot based on the settings in this section, which means you'll lose all your manual edits. Instead, configure static host mappings as follows." +msgstr "Do *not* manually edit `/etc/hosts`. This file will automatically be regenerated on boot based on the settings in this section, which means you'll lose all your manual edits. Instead, configure static host mappings as follows." + +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +#: ../../_include/interface-ipv6.txt:37 +msgid "Do not assign a link-local IPv6 address to this interface." +msgstr "Do not assign a link-local IPv6 address to this interface." + +#: ../../configuration/trafficpolicy/index.rst:1208 +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 "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``." + +#: ../../configuration/service/dns.rst:103 +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 "Do not use the local ``/etc/hosts`` file in name resolution. VyOS DHCP server will use this file to add resolvers to assigned addresses." + +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +#: ../../_include/interface-ip.txt:162 +msgid "Does not need to be used together with proxy_arp." +msgstr "Does not need to be used together with proxy_arp." + +#: ../../configuration/system/host-name.rst:11 +msgid "Domain" +msgstr "Domain" + +#: ../../configuration/firewall/general.rst:300 +#: ../../configuration/firewall/general-legacy.rst:255 +msgid "Domain Groups" +msgstr "Domain Groups" + +#: ../../configuration/system/host-name.rst:32 +msgid "Domain Name" +msgstr "Domain Name" + +#: ../../configuration/service/https.rst:59 +msgid "Domain name(s) for which to obtain certificate" +msgstr "Domain name(s) for which to obtain certificate" + +#: ../../configuration/system/name-server.rst:57 +msgid "Domain names can include letters, numbers, hyphens and periods with a maximum length of 253 characters." +msgstr "Domain names can include letters, numbers, hyphens and periods with a maximum length of 253 characters." + +#: ../../configuration/system/name-server.rst:13 +#: ../../configuration/system/name-server.rst:45 +msgid "Domain search order" +msgstr "Domain search order" + +#: ../../configuration/pki/index.rst:25 +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 "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!" + +#: ../../configuration/protocols/bgp.rst:1171 +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 "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:**" + +#: ../../configuration/protocols/bgp.rst:1125 +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 "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:**" + +#: ../../configuration/vpn/site2site_ipsec.rst:284 +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 "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." + +#: ../../configuration/service/webproxy.rst:346 +msgid "Download/Update complete blacklist" +msgstr "Download/Update complete blacklist" + +#: ../../configuration/service/webproxy.rst:377 +msgid "Download/Update partial blacklist." +msgstr "Download/Update partial blacklist." + +#: ../../configuration/vpn/sstp.rst:85 +msgid "Download bandwidth limit in kbit/s for `<user>`." +msgstr "Download bandwidth limit in kbit/s for `<user>`." + +#: ../../configuration/policy/route-map.rst:202 +msgid "Drop AS-NUMBER from the BGP AS path." +msgstr "Drop AS-NUMBER from the BGP AS path." + +#: ../../configuration/trafficpolicy/index.rst:352 +msgid "Drop Tail" +msgstr "Drop Tail" + +#: ../../configuration/trafficpolicy/index.rst:262 +msgid "Drop rate" +msgstr "Drop rate" + +#: ../../configuration/system/sflow.rst:26 +msgid "Dropped packets reported on DROPMON Netlink channel by Linux kernel are exported via the standard sFlow v5 extension for reporting dropped packets" +msgstr "Dropped packets reported on DROPMON Netlink channel by Linux kernel are exported via the standard sFlow v5 extension for reporting dropped packets" + +#: ../../configuration/service/pppoe-server.rst:380 +msgid "Dual-Stack IPv4/IPv6 provisioning with Prefix Delegation" +msgstr "Dual-Stack IPv4/IPv6 provisioning with Prefix Delegation" + +#: ../../configuration/interfaces/dummy.rst:7 +msgid "Dummy" +msgstr "Dummy" + +#: ../../configuration/nat/nat44.rst:692 +msgid "Dummy interface" +msgstr "Dummy interface" + +#: ../../configuration/interfaces/dummy.rst:13 +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 "Dummy interfaces can be used as interfaces that always stay up (in the same fashion to loopbacks in Cisco IOS), or for testing purposes." + +#: ../../configuration/vrf/index.rst:193 +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 "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." + +#: ../../configuration/service/ssh.rst:113 +msgid "Dynamic-protection" +msgstr "Dynamic-protection" + +#: ../../configuration/service/dns.rst:199 +msgid "Dynamic DNS" +msgstr "Dynamic DNS" + +#: ../../_include/interface-eapol.txt:6 +msgid "EAPoL comes with an identify option. We automatically use the interface MAC address as identity parameter." +msgstr "EAPoL comes with an identify option. We automatically use the interface MAC address as identity parameter." + +#: ../../configuration/nat/nat44.rst:731 +msgid "ESP Phase:" +msgstr "ESP Phase:" + +#: ../../configuration/vpn/ipsec.rst:111 +msgid "ESP (Encapsulating Security Payload) Attributes" +msgstr "ESP (Encapsulating Security Payload) Attributes" + +#: ../../configuration/vpn/ipsec.rst:112 +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 "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" + +#: ../../configuration/service/conntrack-sync.rst:23 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:53 +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 "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." + +#: ../../configuration/protocols/bgp.rst:29 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:48 +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 "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." + +#: ../../configuration/service/broadcast-relay.rst:43 +msgid "Each broadcast relay instance can be individually disabled without deleting the configured node by using the following command:" +msgstr "Each broadcast relay instance can be individually disabled without deleting the configured node by using the following command:" + +#: ../../configuration/trafficpolicy/index.rst:1027 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:967 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:60 +msgid "Each dynamic NHS will get a peer entry with the configured network address and the discovered NBMA address." +msgstr "Each dynamic NHS will get a peer entry with the configured network address and the discovered NBMA address." + +#: ../../configuration/loadbalancing/wan.rst:158 +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 "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:" + +#: ../../configuration/service/console-server.rst:62 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:173 +msgid "Each node (Hub and Spoke) uses an IP address from the network 172.16.253.128/29." +msgstr "Each node (Hub and Spoke) uses an IP address from the network 172.16.253.128/29." + +#: ../../configuration/vpn/openconnect.rst:141 +msgid "Each of the install command should be applied to the configuration and commited before using under the openconnect configuration:" +msgstr "Each of the install command should be applied to the configuration and commited before using under the openconnect configuration:" + +#: ../../configuration/vpn/site2site_ipsec.rst:16 +msgid "Each site-to-site peer has the next options:" +msgstr "Each site-to-site peer has the next options:" + +#: ../../configuration/interfaces/vxlan.rst:77 +msgid "Eenables the Generic Protocol extension (VXLAN-GPE). Currently, this is only supported together with the external keyword." +msgstr "Eenables the Generic Protocol extension (VXLAN-GPE). Currently, this is only supported together with the external keyword." + +#: ../../configuration/service/https.rst:63 +msgid "Email address to associate with certificate" +msgstr "Email address to associate with certificate" + +#: ../../configuration/trafficpolicy/index.rst:300 +msgid "Embedding one policy into another one" +msgstr "Embedding one policy into another one" + +#: ../../configuration/system/syslog.rst:171 +msgid "Emergency" +msgstr "Emergency" + +#: ../../configuration/protocols/bfd.rst:89 +msgid "Enable BFD for ISIS on an interface" +msgstr "Enable BFD for ISIS on an interface" + +#: ../../configuration/protocols/bfd.rst:77 +msgid "Enable BFD for OSPF on an interface" +msgstr "Enable BFD for OSPF on an interface" + +#: ../../configuration/protocols/bfd.rst:81 +msgid "Enable BFD for OSPFv3 on an interface" +msgstr "Enable BFD for OSPFv3 on an interface" + +#: ../../configuration/protocols/bfd.rst:61 +msgid "Enable BFD in BGP" +msgstr "Enable BFD in BGP" + +#: ../../configuration/protocols/bfd.rst:85 +msgid "Enable BFD in ISIS" +msgstr "Enable BFD in ISIS" + +#: ../../configuration/protocols/bfd.rst:73 +msgid "Enable BFD in OSPF" +msgstr "Enable BFD in OSPF" + +#: ../../configuration/protocols/bfd.rst:69 +msgid "Enable BFD on a BGP peer group" +msgstr "Enable BFD on a BGP peer group" + +#: ../../configuration/protocols/bfd.rst:65 +msgid "Enable BFD on a single BGP neighbor" +msgstr "Enable BFD on a single BGP neighbor" + +#: ../../configuration/service/dhcp-server.rst:168 +msgid "Enable DHCP failover configuration for this address pool." +msgstr "Enable DHCP failover configuration for this address pool." + +#: ../../configuration/interfaces/wireless.rst:178 +msgid "Enable HT-delayed Block Ack ``[DELAYED-BA]``" +msgstr "Enable HT-delayed Block Ack ``[DELAYED-BA]``" + +#: ../../configuration/interfaces/bridge.rst:81 +msgid "Enable IGMP and MLD querier." +msgstr "Enable IGMP and MLD querier." + +#: ../../configuration/interfaces/bridge.rst:85 +msgid "Enable IGMP and MLD snooping." +msgstr "Enable IGMP and MLD snooping." + +#: ../../configuration/service/dhcp-server.rst:304 +msgid "Enable IP forwarding on client" +msgstr "Enable IP forwarding on client" + +#: ../../configuration/protocols/isis.rst:311 +msgid "Enable IS-IS" +msgstr "Enable IS-IS" + +#: ../../configuration/protocols/isis.rst:427 +msgid "Enable IS-IS and IGP-LDP synchronization" +msgstr "Enable IS-IS and IGP-LDP synchronization" + +#: ../../configuration/protocols/isis.rst:386 +msgid "Enable IS-IS and redistribute routes not natively in IS-IS" +msgstr "Enable IS-IS and redistribute routes not natively in IS-IS" + +#: ../../configuration/protocols/isis.rst:465 +#: ../../configuration/protocols/segment-routing.rst:193 +msgid "Enable IS-IS with Segment Routing (Experimental)" +msgstr "Enable IS-IS with Segment Routing (Experimental)" + +#: ../../configuration/interfaces/wireless.rst:194 +msgid "Enable L-SIG TXOP protection capability" +msgstr "Enable L-SIG TXOP protection capability" + +#: ../../configuration/interfaces/wireless.rst:263 +msgid "Enable LDPC (Low Density Parity Check) coding capability" +msgstr "Enable LDPC (Low Density Parity Check) coding capability" + +#: ../../configuration/interfaces/wireless.rst:190 +msgid "Enable LDPC coding capability" +msgstr "Enable LDPC coding capability" + +#: ../../configuration/service/lldp.rst:40 +msgid "Enable LLDP service" +msgstr "Enable LLDP service" + +#: ../../configuration/protocols/ospf.rst:838 +msgid "Enable OSPF" +msgstr "Enable OSPF" + +#: ../../configuration/protocols/ospf.rst:946 +msgid "Enable OSPF and IGP-LDP synchronization:" +msgstr "Enable OSPF and IGP-LDP synchronization:" + +#: ../../configuration/protocols/ospf.rst:983 +#: ../../configuration/protocols/segment-routing.rst:279 +msgid "Enable OSPF with Segment Routing (Experimental):" +msgstr "Enable OSPF with Segment Routing (Experimental):" + +#: ../../configuration/protocols/ospf.rst:911 +msgid "Enable OSPF with route redistribution of the loopback and default originate:" +msgstr "Enable OSPF with route redistribution of the loopback and default originate:" + +#: ../../configuration/system/login.rst:103 +msgid "Enable OTP 2FA for user `username` with default settings, using the BASE32 encoded 2FA/MFA key specified by `<key>`." +msgstr "Enable OTP 2FA for user `username` with default settings, using the BASE32 encoded 2FA/MFA key specified by `<key>`." + +#: ../../configuration/interfaces/openvpn.rst:692 +msgid "Enable OpenVPN Data Channel Offload feature by loading the appropriate kernel module." +msgstr "Enable OpenVPN Data Channel Offload feature by loading the appropriate kernel module." + +#: ../../configuration/service/lldp.rst:59 +msgid "Enable SNMP queries of the LLDP database" +msgstr "Enable SNMP queries of the LLDP database" + +#: ../../configuration/interfaces/bridge.rst:197 +#: ../../configuration/interfaces/bridge.rst:232 +msgid "Enable STP" +msgstr "Enable STP" + +#: ../../configuration/service/tftp-server.rst:18 +msgid "Enable TFTP service by specifying the `<directory>` which will be used to serve files." +msgstr "Enable TFTP service by specifying the `<directory>` which will be used to serve files." + +#: ../../configuration/interfaces/wireless.rst:294 +msgid "Enable VHT TXOP Power Save Mode" +msgstr "Enable VHT TXOP Power Save Mode" + +#: ../../configuration/interfaces/bridge.rst:126 +msgid "Enable VLAN-Aware Bridge" +msgstr "Enable VLAN-Aware Bridge" + +#: ../../configuration/vpn/dmvpn.rst:132 +msgid "Enable creation of shortcut routes." +msgstr "Enable creation of shortcut routes." + +#: ../../configuration/interfaces/ethernet.rst:62 +msgid "Enable different types of hardware offloading on the given NIC." +msgstr "Enable different types of hardware offloading on the given NIC." + +#: ../../configuration/service/lldp.rst:63 +msgid "Enable given legacy protocol on this LLDP instance. Legacy protocols include:" +msgstr "Enable given legacy protocol on this LLDP instance. Legacy protocols include:" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:119 +msgid "Enable layer 7 HTTP health check" +msgstr "Enable layer 7 HTTP health check" + +#: ../../configuration/firewall/general.rst:177 +#: ../../configuration/firewall/general-legacy.rst:126 +msgid "Enable or Disable VyOS to be :rfc:`1337` conform. The following system parameter will be altered:" +msgstr "Enable or Disable VyOS to be :rfc:`1337` conform. The following system parameter will be altered:" + +#: ../../configuration/firewall/general.rst:169 +#: ../../configuration/firewall/general-legacy.rst:119 +msgid "Enable or Disable if VyOS use IPv4 TCP SYN Cookies. The following system parameter will be altered:" +msgstr "Enable or Disable if VyOS use IPv4 TCP SYN Cookies. The following system parameter will be altered:" + +#: ../../configuration/firewall/general.rst:426 +#: ../../configuration/firewall/general-legacy.rst:340 +msgid "Enable or disable logging for the matched packet." +msgstr "Enable or disable logging for the matched packet." + +#: ../../configuration/protocols/ospf.rst:360 +msgid "Enable ospf on an interface and set associated area." +msgstr "Enable ospf on an interface and set associated area." + +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../configuration/interfaces/pppoe.rst:215 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../configuration/interfaces/sstp-client.rst:100 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +#: ../../_include/interface-ip.txt:177 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:213 +#: ../../configuration/interfaces/wireless.rst:286 +msgid "Enable receiving PPDU using STBC (Space Time Block Coding)" +msgstr "Enable receiving PPDU using STBC (Space Time Block Coding)" + +#: ../../configuration/system/flow-accounting.rst:154 +msgid "Enable sampling of packets, which will be transmitted to sFlow collectors." +msgstr "Enable sampling of packets, which will be transmitted to sFlow collectors." + +#: ../../configuration/interfaces/wireless.rst:217 +#: ../../configuration/interfaces/wireless.rst:290 +msgid "Enable sending PPDU using STBC (Space Time Block Coding)" +msgstr "Enable sending PPDU using STBC (Space Time Block Coding)" + +#: ../../configuration/vpn/dmvpn.rst:124 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:100 +msgid "Enable spanning tree protocol. STP is disabled by default." +msgstr "Enable spanning tree protocol. STP is disabled by default." + +#: ../../configuration/protocols/segment-routing.rst:127 +msgid "Enable the Opaque-LSA capability (rfc2370), necessary to transport label on IGP" +msgstr "Enable the Opaque-LSA capability (rfc2370), necessary to transport label on IGP" + +#: ../../configuration/interfaces/openvpn.rst:697 +msgid "Enable this feature causes an interface reset." +msgstr "Enable this feature causes an interface reset." + +#: ../../configuration/service/lldp.rst:49 +msgid "Enable transmission of LLDP information on given `<interface>`. You can also say ``all`` here so LLDP is turned on on every interface." +msgstr "Enable transmission of LLDP information on given `<interface>`. You can also say ``all`` here so LLDP is turned on on every interface." + +#: ../../configuration/interfaces/pppoe.rst:115 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:48 +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 "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." + +#: ../../configuration/vrf/index.rst:459 +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 "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." + +#: ../../configuration/vpn/sstp.rst:266 +msgid "Enables bandwidth shaping via RADIUS." +msgstr "Enables bandwidth shaping via RADIUS." + +#: ../../configuration/vrf/index.rst:481 +msgid "Enables import or export of routes between the current unicast VRF and VPN." +msgstr "Enables import or export of routes between the current unicast VRF and VPN." + +#: ../../configuration/protocols/bfd.rst:30 +msgid "Enables the echo transmission mode" +msgstr "Enables the echo transmission mode" + +#: ../../configuration/service/router-advert.rst:27 +msgid "Enabling Advertisments" +msgstr "Enabling Advertisments" + +#: ../../configuration/interfaces/openvpn.rst:627 +msgid "Enabling OpenVPN DCO" +msgstr "Enabling OpenVPN DCO" + +#: ../../configuration/service/ssh.rst:40 +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 "Enabling SSH only requires you to specify the port ``<port>`` you want SSH to listen on. By default, SSH runs on port 22." + +#: ../../configuration/protocols/igmp.rst:224 +msgid "Enabling this function increases the risk of bandwidth saturation." +msgstr "Enabling this function increases the risk of bandwidth saturation." + +#: ../../configuration/service/https.rst:37 +msgid "Enforce strict path checking" +msgstr "Enforce strict path checking" + +#: ../../configuration/interfaces/bonding.rst:31 +msgid "Enslave `<member>` interface to bond `<interface>`." +msgstr "Enslave `<member>` interface to bond `<interface>`." + +#: ../../configuration/protocols/bgp.rst:764 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:445 +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 "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." + +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +#: ../../_include/interface-ip.txt:172 +msgid "Ericsson call it MAC-Forced Forwarding (RFC Draft)" +msgstr "Ericsson call it MAC-Forced Forwarding (RFC Draft)" + +#: ../../configuration/system/syslog.rst:181 +msgid "Error" +msgstr "Error" + +#: ../../configuration/system/syslog.rst:181 +msgid "Error conditions" +msgstr "Error conditions" + +#: ../../configuration/vpn/l2tp.rst:76 +msgid "Established sessions can be viewed using the **show l2tp-server sessions** operational command" +msgstr "Established sessions can be viewed using the **show l2tp-server sessions** operational command" + +#: ../../configuration/interfaces/ethernet.rst:7 +msgid "Ethernet" +msgstr "Ethernet" + +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +#: ../../_include/interface-disable-flow-control.txt:4 +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 "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." + +#: ../../configuration/interfaces/ethernet.rst:24 +msgid "Ethernet options" +msgstr "Ethernet options" + +#: ../../configuration/service/eventhandler.rst:5 +msgid "Event Handler" +msgstr "Event Handler" + +#: ../../configuration/service/eventhandler.rst:29 +msgid "Event Handler Configuration Steps" +msgstr "Event Handler Configuration Steps" + +#: ../../configuration/service/eventhandler.rst:9 +msgid "Event Handler Technology Overview" +msgstr "Event Handler Technology Overview" + +#: ../../configuration/service/eventhandler.rst:11 +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 "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." + +#: ../../configuration/service/eventhandler.rst:95 +msgid "Event handler script" +msgstr "Event handler script" + +#: ../../configuration/service/eventhandler.rst:85 +msgid "Event handler that monitors the state of interface eth0." +msgstr "Event handler that monitors the state of interface eth0." + +#: ../../configuration/nat/nat44.rst:221 +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 "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." + +#: ../../configuration/nat/nat66.rst:71 +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 "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.、" + +#: ../../configuration/system/login.rst:47 +msgid "Every SSH key comes in three parts:" +msgstr "Every SSH key comes in three parts:" + +#: ../../configuration/system/login.rst:68 +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 "Every SSH public key portion referenced by `<identifier>` requires the configuration of the `<type>` of public-key used. This type can be any of:" + +#: ../../configuration/service/broadcast-relay.rst:14 +msgid "Every UDP port which will be forward requires one unique ID. Currently we support 99 IDs!" +msgstr "Every UDP port which will be forward requires one unique ID. Currently we support 99 IDs!" + +#: ../../configuration/interfaces/pseudo-ethernet.rst:20 +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 "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." + +#: ../../configuration/interfaces/wwan.rst:72 +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 "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." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:98 +msgid "Every connection/remote-access pool we configure also needs a pool where we can draw our client IP addresses from. We provide one IPv4 and IPv6 pool. Authorized clients will receive an IPv4 address from the configured IPv4 prefix and an IPv6 address from the IPv6 prefix. We can also send some DNS nameservers down to our clients used on their connection." +msgstr "Every connection/remote-access pool we configure also needs a pool where we can draw our client IP addresses from. We provide one IPv4 and IPv6 pool. Authorized clients will receive an IPv4 address from the configured IPv4 prefix and an IPv6 address from the IPv6 prefix. We can also send some DNS nameservers down to our clients used on their connection." + +#: ../../configuration/highavailability/index.rst:397 +#: ../../configuration/interfaces/bonding.rst:291 +#: ../../configuration/interfaces/l2tpv3.rst:86 +#: ../../configuration/interfaces/pppoe.rst:310 +#: ../../configuration/interfaces/virtual-ethernet.rst:92 +#: ../../configuration/interfaces/vxlan.rst:166 +#: ../../configuration/interfaces/wwan.rst:294 +#: ../../configuration/protocols/failover.rst:63 +#: ../../configuration/protocols/igmp.rst:35 +#: ../../configuration/protocols/igmp.rst:233 +#: ../../configuration/protocols/rpki.rst:156 +#: ../../configuration/service/broadcast-relay.rst:55 +#: ../../configuration/service/conntrack-sync.rst:186 +#: ../../configuration/service/dhcp-relay.rst:85 +#: ../../configuration/service/dhcp-relay.rst:172 +#: ../../configuration/service/dhcp-server.rst:421 +#: ../../configuration/service/dns.rst:147 +#: ../../configuration/service/dns.rst:263 +#: ../../configuration/service/eventhandler.rst:83 +#: ../../configuration/service/ipoe-server.rst:150 +#: ../../configuration/service/mdns.rst:34 +#: ../../configuration/service/monitoring.rst:134 +#: ../../configuration/service/snmp.rst:94 +#: ../../configuration/service/snmp.rst:145 +#: ../../configuration/service/tftp-server.rst:47 +#: ../../configuration/system/acceleration.rst:58 +#: ../../configuration/system/login.rst:395 +#: ../../configuration/system/name-server.rst:28 +#: ../../configuration/system/name-server.rst:63 +#: ../../configuration/system/sflow.rst:49 +#: ../../configuration/trafficpolicy/index.rst:530 +#: ../../configuration/trafficpolicy/index.rst:1122 +#: ../../configuration/vpn/dmvpn.rst:161 +#: ../../configuration/vpn/openconnect.rst:97 +#: ../../configuration/vpn/sstp.rst:275 +#: ../../configuration/vrf/index.rst:99 +#: ../../configuration/vrf/index.rst:232 +msgid "Example" +msgstr "Example" + +#: ../../configuration/service/pppoe-server.rst:144 +msgid "Example, from radius-server send command for disconnect client with username test" +msgstr "Example, from radius-server send command for disconnect client with username test" + +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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.txt:9 +#: ../../_include/interface-description.txt:7 +#: ../../_include/interface-disable.txt:7 +#: ../../_include/interface-vrf.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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-eapol.txt:18 +#: ../../_include/interface-eapol.txt:33 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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.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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_include/interface-vrf.txt:9 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_include/interface-vrf.txt:9 +#: ../../_include/interface-address.txt:9 +#: ../../_include/interface-description.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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-description.txt:7 +#: ../../_include/interface-disable.txt:7 +#: ../../_include/interface-mtu.txt:7 +#: ../../_include/interface-vrf.txt:9 +#: ../../configuration/interfaces/pppoe.rst:127 +#: ../../configuration/interfaces/pppoe.rst:140 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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-description.txt:7 +#: ../../_include/interface-disable.txt:7 +#: ../../_include/interface-mtu.txt:7 +#: ../../_include/interface-vrf.txt:9 +#: ../../configuration/interfaces/sstp-client.rst:49 +#: ../../configuration/interfaces/sstp-client.rst:62 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_include/interface-vrf.txt:9 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_include/interface-description.txt:7 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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-disable.txt:7 +#: ../../_include/interface-vrf.txt:9 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_include/interface-vrf.txt:9 +#: ../../_include/interface-per-client-thread.txt:10 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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-per-client-thread.txt:10 +#: ../../_include/interface-address-with-dhcp.txt:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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:22 +#: ../../_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-ipv6.txt:83 +#: ../../_include/interface-ipv6.txt:96 +#: ../../_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/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:411 +#: ../../configuration/nat/nat66.rst:78 +#: ../../configuration/nat/nat66.rst:96 +#: ../../configuration/protocols/static.rst:174 +#: ../../configuration/service/dns.rst:350 +#: ../../configuration/service/monitoring.rst:69 +#: ../../configuration/service/monitoring.rst:98 +#: ../../configuration/service/ssh.rst:165 +#: ../../configuration/service/ssh.rst:200 +#: ../../configuration/system/flow-accounting.rst:164 +#: ../../configuration/vpn/l2tp.rst:41 +#: ../../configuration/vpn/site2site_ipsec.rst:158 +#: ../../configuration/vpn/site2site_ipsec.rst:269 +msgid "Example:" +msgstr "Example:" + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:36 +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 "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." + +#: ../../configuration/nat/nat44.rst:357 +msgid "Example: For an ~8,000 host network a source NAT pool of 32 IP addresses is recommended." +msgstr "Example: For an ~8,000 host network a source NAT pool of 32 IP addresses is recommended." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:54 +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 "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." + +#: ../../_include/interface-mirror.txt:19 +msgid "Example: Mirror the inbound traffic of `bond1` port to `eth3`" +msgstr "Example: Mirror the inbound traffic of `bond1` port to `eth3`" + +#: ../../_include/interface-mirror.txt:19 +msgid "Example: Mirror the inbound traffic of `br1` port to `eth3`" +msgstr "Example: Mirror the inbound traffic of `br1` port to `eth3`" + +#: ../../_include/interface-mirror.txt:19 +msgid "Example: Mirror the inbound traffic of `eth1` port to `eth3`" +msgstr "Example: Mirror the inbound traffic of `eth1` port to `eth3`" + +#: ../../_include/interface-mirror.txt:31 +msgid "Example: Mirror the outbound traffic of `bond1` port to `eth3`" +msgstr "Example: Mirror the outbound traffic of `bond1` port to `eth3`" + +#: ../../_include/interface-mirror.txt:31 +msgid "Example: Mirror the outbound traffic of `br1` port to `eth3`" +msgstr "Example: Mirror the outbound traffic of `br1` port to `eth3`" + +#: ../../_include/interface-mirror.txt:31 +msgid "Example: Mirror the outbound traffic of `eth1` port to `eth3`" +msgstr "Example: Mirror the outbound traffic of `eth1` port to `eth3`" + +#: ../../configuration/interfaces/bridge.rst:166 +msgid "Example: Set `eth0` member port to be allowed VLAN 4" +msgstr "Example: Set `eth0` member port to be allowed VLAN 4" + +#: ../../configuration/interfaces/bridge.rst:172 +msgid "Example: Set `eth0` member port to be allowed VLAN 6-8" +msgstr "Example: Set `eth0` member port to be allowed VLAN 6-8" + +#: ../../configuration/interfaces/bridge.rst:153 +msgid "Example: Set `eth0` member port to be native VLAN 2" +msgstr "Example: Set `eth0` member port to be native VLAN 2" + +#: ../../configuration/service/webproxy.rst:28 +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 "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``." + +#: ../../configuration/container/index.rst:177 +#: ../../configuration/service/https.rst:77 +#: ../../configuration/service/router-advert.rst:80 +msgid "Example Configuration" +msgstr "Example Configuration" + +#: ../../configuration/service/dns.rst:365 +msgid "Example IPv6 only:" +msgstr "Example IPv6 only:" + +#: ../../configuration/nat/nat44.rst:666 +msgid "Example Network" +msgstr "Example Network" + +#: ../../configuration/firewall/general.rst:1495 +#: ../../configuration/firewall/general-legacy.rst:979 +msgid "Example Partial Config" +msgstr "Example Partial Config" + +#: ../../configuration/protocols/ospf.rst:1346 +msgid "Example configuration for WireGuard interfaces:" +msgstr "Example configuration for WireGuard interfaces:" + +#: ../../configuration/service/pppoe-server.rst:160 +msgid "Example for changing rate-limit via RADIUS CoA." +msgstr "Example for changing rate-limit via RADIUS CoA." + +#: ../../configuration/vpn/l2tp.rst:12 +msgid "Example for configuring a simple L2TP over IPsec VPN for remote access (works with native Windows and Mac VPN clients):" +msgstr "Example for configuring a simple L2TP over IPsec VPN for remote access (works with native Windows and Mac VPN clients):" + +#: ../../configuration/nat/nat44.rst:280 +msgid "Example of redirection:" +msgstr "Example of redirection:" + +#: ../../configuration/firewall/general.rst:1278 +msgid "Example synproxy" +msgstr "Example synproxy" + +#: ../../configuration/interfaces/bridge.rst:187 +#: ../../configuration/interfaces/macsec.rst:153 +#: ../../configuration/interfaces/wireless.rst:541 +#: ../../configuration/loadbalancing/reverse-proxy.rst:187 +#: ../../configuration/policy/index.rst:46 +#: ../../configuration/protocols/bgp.rst:1095 +#: ../../configuration/protocols/isis.rst:308 +#: ../../configuration/protocols/ospf.rst:834 +#: ../../configuration/service/pppoe-server.rst:356 +#: ../../configuration/service/webproxy.rst:419 +msgid "Examples" +msgstr "Examples" + +#: ../../configuration/vpn/site2site_ipsec.rst:153 +msgid "Examples:" +msgstr "Examples:" + +#: ../../configuration/policy/index.rst:48 +msgid "Examples of policies usage:" +msgstr "Examples of policies usage:" + +#: ../../configuration/highavailability/index.rst:85 +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 "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." + +#: ../../configuration/highavailability/index.rst:83 +msgid "Exclude address" +msgstr "Exclude address" + +#: ../../configuration/loadbalancing/wan.rst:113 +msgid "Exclude traffic" +msgstr "Exclude traffic" + +#: ../../configuration/policy/route-map.rst:192 +msgid "Exit policy on match: go to next sequence number." +msgstr "Exit policy on match: go to next sequence number." + +#: ../../configuration/policy/route-map.rst:188 +msgid "Exit policy on match: go to rule <1-65535>" +msgstr "Exit policy on match: go to rule <1-65535>" + +#: ../../configuration/trafficpolicy/index.rst:265 +msgid "Expedited forwarding (EF)" +msgstr "Expedited forwarding (EF)" + +#: ../../configuration/service/salt-minion.rst:33 +msgid "Explicitly declare ID for this minion to use (default: hostname)" +msgstr "Explicitly declare ID for this minion to use (default: hostname)" + +#: ../../configuration/service/dhcp-relay.rst:176 +msgid "External DHCPv6 server is at 2001:db8::4" +msgstr "External DHCPv6 server is at 2001:db8::4" + +#: ../../configuration/protocols/ospf.rst:474 +msgid "External Route Summarisation" +msgstr "External Route Summarisation" + +#: ../../configuration/trafficpolicy/index.rst:441 +msgid "FQ-CoDel" +msgstr "FQ-CoDel" + +#: ../../configuration/trafficpolicy/index.rst:450 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:460 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:474 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:465 +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 "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." + +#: ../../configuration/protocols/ospf.rst:213 +msgid "FRR offers only partial support for some of the routing protocol extensions that are used with MPLS-TE; it does not support a complete RSVP-TE solution." +msgstr "FRR offers only partial support for some of the routing protocol extensions that are used with MPLS-TE; it does not support a complete RSVP-TE solution." + +#: ../../configuration/interfaces/vxlan.rst:138 +msgid "FRR supports a new way of configuring VLAN-to-VNI mappings for EVPN-VXLAN, when working with the Linux kernel. In this new way, the mapping of a VLAN to a :abbr:`VNI (VXLAN Network Identifier (or VXLAN Segment ID))` is configured against a container VXLAN interface which is referred to as a :abbr:`SVD (Single VXLAN device)`." +msgstr "FRR supports a new way of configuring VLAN-to-VNI mappings for EVPN-VXLAN, when working with the Linux kernel. In this new way, the mapping of a VLAN to a :abbr:`VNI (VXLAN Network Identifier (or VXLAN Segment ID))` is configured against a container VXLAN interface which is referred to as a :abbr:`SVD (Single VXLAN device)`." + +#: ../../configuration/system/syslog.rst:134 +msgid "FTP daemon" +msgstr "FTP daemon" + +#: ../../configuration/system/syslog.rst:96 +msgid "Facilities" +msgstr "Facilities" + +#: ../../configuration/system/syslog.rst:104 +msgid "Facilities can be adjusted to meet the needs of the user:" +msgstr "Facilities can be adjusted to meet the needs of the user:" + +#: ../../configuration/system/syslog.rst:107 +msgid "Facility Code" +msgstr "Facility Code" + +#: ../../configuration/loadbalancing/wan.rst:218 +#: ../../configuration/protocols/failover.rst:3 +#: ../../configuration/service/dhcp-server.rst:171 +#: ../../configuration/service/dhcp-server.rst:428 +msgid "Failover" +msgstr "Failover" + +#: ../../configuration/protocols/failover.rst:12 +msgid "Failover Routes" +msgstr "Failover Routes" + +#: ../../configuration/service/conntrack-sync.rst:61 +msgid "Failover mechanism to use for conntrack-sync." +msgstr "Failover mechanism to use for conntrack-sync." + +#: ../../configuration/protocols/failover.rst:5 +msgid "Failover routes are manually configured routes, but they install to the routing table if the health-check target is alive. If the target is not alive the route is removed from the routing table until the target will be available." +msgstr "Failover routes are manually configured routes, but they install to the routing table if the health-check target is alive. If the target is not alive the route is removed from the routing table until the target will be available." + +#: ../../configuration/trafficpolicy/index.rst:384 +msgid "Fair Queue" +msgstr "Fair Queue" + +#: ../../configuration/trafficpolicy/index.rst:429 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:389 +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 "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." + +#: ../../configuration/protocols/rpki.rst:78 +msgid "Features of the Current Implementation" +msgstr "Features of the Current Implementation" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Field" +msgstr "Field" + +#: ../../configuration/service/dns.rst:228 +msgid "File identified by `<keyfile>` containing the secret RNDC key shared with remote DNS server." +msgstr "File identified by `<keyfile>` containing the secret RNDC key shared with remote DNS server." + +#: ../../configuration/service/pppoe-server.rst:241 +msgid "Filter-Id=2000/3000 (means 2000Kbit down-stream rate and 3000Kbit up-stream rate)" +msgstr "Filter-Id=2000/3000 (means 2000Kbit down-stream rate and 3000Kbit up-stream rate)" + +#: ../../configuration/service/pppoe-server.rst:167 +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 "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." + +#: ../../configuration/protocols/ospf.rst:306 +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 "Filter Type-3 summary-LSAs announced to other areas originated from intra- area paths from specified area. This command makes sense in ABR only." + +#: ../../configuration/policy/index.rst:16 +msgid "Filter traffic based on source/destination address." +msgstr "Filter traffic based on source/destination address." + +#: ../../configuration/service/webproxy.rst:335 +msgid "Filtering" +msgstr "Filtering" + +#: ../../configuration/policy/access-list.rst:5 +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 "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." + +#: ../../configuration/policy/examples.rst:81 +msgid "Finally, to apply the policy route to ingress traffic on our LAN interface, we use:" +msgstr "Finally, to apply the policy route to ingress traffic on our LAN interface, we use:" + +#: ../../configuration/firewall/index.rst:5 +msgid "Firewall" +msgstr "Firewall" + +#: ../../configuration/firewall/general-legacy.rst:7 +msgid "Firewall-Legacy" +msgstr "Firewall-Legacy" + +#: ../../configuration/firewall/general.rst:7 +msgid "Firewall Configuration" +msgstr "Firewall Configuration" + +#: ../../configuration/firewall/general-legacy.rst:7 +msgid "Firewall Configuration (Deprecated)" +msgstr "Firewall Configuration (Deprecated)" + +#: ../../configuration/firewall/general.rst:495 +msgid "Firewall Description" +msgstr "Firewall Description" + +#: ../../configuration/interfaces/openvpn.rst:209 +#: ../../configuration/interfaces/wireguard.rst:207 +msgid "Firewall Exceptions" +msgstr "Firewall Exceptions" + +#: ../../configuration/firewall/general.rst:410 +msgid "Firewall Logs" +msgstr "Firewall Logs" + +#: ../../configuration/firewall/general.rst:318 +msgid "Firewall Rules" +msgstr "Firewall Rules" + +#: ../../configuration/firewall/general.rst:186 +msgid "Firewall groups represent collections of IP addresses, networks, ports, mac addresses, domains or interfaces. Once created, a group can be referenced by firewall, nat and policy route rules as either a source or destination matcher, and as inbpund/outbound in the case of interface group." +msgstr "Firewall groups represent collections of IP addresses, networks, ports, mac addresses, domains or interfaces. Once created, a group can be referenced by firewall, nat and policy route rules as either a source or destination matcher, and as inbpund/outbound in the case of interface group." + +#: ../../configuration/firewall/general-legacy.rst:155 +msgid "Firewall groups represent collections of IP addresses, networks, ports, mac addresses or domains. Once created, a group can be referenced by firewall, nat and policy route rules as either a source or destination matcher. Members can be added or removed from a group without changes to, or the need to reload, individual firewall rules." +msgstr "Firewall groups represent collections of IP addresses, networks, ports, mac addresses or domains. Once created, a group can be referenced by firewall, nat and policy route rules as either a source or destination matcher. Members can be added or removed from a group without changes to, or the need to reload, individual firewall rules." + +#: ../../configuration/highavailability/index.rst:381 +msgid "Firewall mark. It possible to loadbalancing traffic based on ``fwmark`` value" +msgstr "Firewall mark. It possible to loadbalancing traffic based on ``fwmark`` value" + +#: ../../configuration/interfaces/openvpn.rst:311 +msgid "Firewall policy can also be applied to the tunnel interface for `local`, `in`, and `out` directions and functions identically to ethernet interfaces." +msgstr "Firewall policy can also be applied to the tunnel interface for `local`, `in`, and `out` directions and functions identically to ethernet interfaces." + +#: ../../configuration/nat/nat44.rst:620 +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 "Firewall rules are written as normal, using the internal IP address as the source of outbound rules and the destination of inbound rules." + +#: ../../configuration/interfaces/wwan.rst:321 +msgid "Firmware Update" +msgstr "Firmware Update" + +#: ../../configuration/vpn/rsa-keys.rst:9 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:267 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:51 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:176 +msgid "First, you need to generate a key by running ``run generate pki openvpn shared-secret install <name>`` from configuration mode. You can use any name, we will use ``s2s``." +msgstr "First, you need to generate a key by running ``run generate pki openvpn shared-secret install <name>`` from configuration mode. You can use any name, we will use ``s2s``." + +#: ../../configuration/policy/route-map.rst:60 +msgid "First hop interface of a route to match." +msgstr "First hop interface of a route to match." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:20 +msgid "First of all, we need to create a CA root certificate and server certificate on the server side." +msgstr "First of all, we need to create a CA root certificate and server certificate on the server side." + +#: ../../configuration/protocols/bgp.rst:171 +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 "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." + +#: ../../configuration/nat/nat44.rst:635 +msgid "First scenario: apply destination NAT for all HTTP traffic comming through interface eth0, and user 4 backends. First backend should received 30% of the request, second backend should get 20%, third 15% and the fourth 35% We will use source and destination address for hash generation." +msgstr "First scenario: apply destination NAT for all HTTP traffic comming through interface eth0, and user 4 backends. First backend should received 30% of the request, second backend should get 20%, third 15% and the fourth 35% We will use source and destination address for hash generation." + +#: ../../configuration/service/pppoe-server.rst:21 +msgid "First steps" +msgstr "First steps" + +#: ../../configuration/vpn/openconnect.rst:171 +msgid "First the OTP keys must be generated and sent to the user and to the configuration:" +msgstr "First the OTP keys must be generated and sent to the user and to the configuration:" + +#: ../../configuration/interfaces/openvpn.rst:342 +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 "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." + +#: ../../configuration/protocols/rpki.rst:41 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:797 +msgid "Flash" +msgstr "Flash" + +#: ../../configuration/trafficpolicy/index.rst:795 +msgid "Flash Override" +msgstr "Flash Override" + +#: ../../configuration/system/flow-accounting.rst:5 +msgid "Flow Accounting" +msgstr "Flow Accounting" + +#: ../../configuration/system/flow-accounting.rst:86 +msgid "Flow Export" +msgstr "Flow Export" + +#: ../../configuration/loadbalancing/wan.rst:95 +msgid "Flow and packet-based balancing" +msgstr "Flow and packet-based balancing" + +#: ../../configuration/system/flow-accounting.rst:10 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:244 +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 "Flushing the session table will cause other connections to fall back from flow-based to packet-based balancing until each flow is reestablished." + +#: ../../configuration/vpn/openconnect.rst:102 +msgid "Follow the instructions to generate CA cert (in configuration mode):" +msgstr "Follow the instructions to generate CA cert (in configuration mode):" + +#: ../../configuration/vpn/openconnect.rst:120 +msgid "Follow the instructions to generate server cert (in configuration mode):" +msgstr "Follow the instructions to generate server cert (in configuration mode):" + +#: ../../configuration/interfaces/openvpn.rst:258 +msgid "For Encryption:" +msgstr "For Encryption:" + +#: ../../configuration/interfaces/openvpn.rst:295 +msgid "For Hashing:" +msgstr "For Hashing:" + +#: ../../configuration/protocols/isis.rst:33 +msgid "For IS-IS top operate correctly, one must do the equivalent of a Router ID in CLNS. This Router ID is called the :abbr:`NET (Network Entity Title)`. This must be unique for each and every router that is operating in IS-IS. It also must not be duplicated otherwise the same issues that occur within OSPF will occur within IS-IS when it comes to said duplication." +msgstr "For IS-IS top operate correctly, one must do the equivalent of a Router ID in CLNS. This Router ID is called the :abbr:`NET (Network Entity Title)`. This must be unique for each and every router that is operating in IS-IS. It also must not be duplicated otherwise the same issues that occur within OSPF will occur within IS-IS when it comes to said duplication." + +#: ../../configuration/policy/route-map.rst:311 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:201 +msgid "For Local Users" +msgstr "For Local Users" + +#: ../../configuration/service/pppoe-server.rst:236 +msgid "For RADIUS users" +msgstr "For RADIUS users" + +#: ../../configuration/service/console-server.rst:18 +msgid "For USB port information please refor to: :ref:`hardware_usb`." +msgstr "For USB port information please refor to: :ref:`hardware_usb`." + +#: ../../configuration/nat/nat44.rst:137 +msgid "For :ref:`bidirectional-nat` a rule for both :ref:`source-nat` and :ref:`destination-nat` needs to be created." +msgstr "For :ref:`bidirectional-nat` a rule for both :ref:`source-nat` and :ref:`destination-nat` needs to be created." + +#: ../../configuration/nat/nat44.rst:263 +msgid "For :ref:`destination-nat` rules the packets destination address will be replaced by the specified address in the `translation address` command." +msgstr "For :ref:`destination-nat` rules the packets destination address will be replaced by the specified address in the `translation address` command." + +#: ../../configuration/nat/nat44.rst:228 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:383 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:354 +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 "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." + +#: ../../configuration/nat/nat44.rst:248 +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 "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" + +#: ../../configuration/interfaces/pppoe.rst:34 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:35 +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 "For connectionless protocols as like ICMP and UDP, a flow is considered complete once no more packets for this flow appear after configurable timeout." + +#: ../../configuration/system/login.rst:132 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:157 +msgid "For example:" +msgstr "For example:" + +#: ../../configuration/firewall/general.rst:59 +msgid "For firewall filtering, configuration should be done in ``set firewall [ipv4 | ipv6] ...``" +msgstr "For firewall filtering, configuration should be done in ``set firewall [ipv4 | ipv6] ...``" + +#: ../../configuration/firewall/general.rst:320 +msgid "For firewall filtering, firewall rules needs to be created. Each rule is numbered, has an action to apply if the rule is matched, and the ability to specify multiple criteria matchers. Data packets go through the rules from 1 - 999999, so order is crucial. At the first match the action of the rule will be executed." +msgstr "For firewall filtering, firewall rules needs to be created. Each rule is numbered, has an action to apply if the rule is matched, and the ability to specify multiple criteria matchers. Data packets go through the rules from 1 - 999999, so order is crucial. At the first match the action of the rule will be executed." + +#: ../../configuration/interfaces/bonding.rst:219 +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 "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." + +#: ../../configuration/vpn/openconnect.rst:74 +msgid "For generating an OTP key in VyOS, you can use the CLI command (operational mode):" +msgstr "For generating an OTP key in VyOS, you can use the CLI command (operational mode):" + +#: ../../configuration/protocols/bgp.rst:823 +msgid "For inbound updates the order of preference is:" +msgstr "For inbound updates the order of preference is:" + +#: ../../configuration/trafficpolicy/index.rst:254 +msgid "For instance, with :code:`set qos 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 "For instance, with :code:`set qos 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." + +#: ../../configuration/policy/route.rst:67 +msgid "For ipv4:" +msgstr "For ipv4:" + +#: ../../configuration/firewall/zone.rst:9 +msgid "For latest releases, refer the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html#interface-groups>`_ main page to configure zone based rules. New syntax was introduced here :vytask:`T5160`" +msgstr "For latest releases, refer the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html#interface-groups>`_ main page to configure zone based rules. New syntax was introduced here :vytask:`T5160`" + +#: ../../configuration/firewall/zone.rst:19 +msgid "For latest releases, refer the `firewall (interface-groups) <https://docs.vyos.io/en/latest/configuration/firewall/general.html#interface-groups>`_ main page to configure zone based rules. New syntax was introduced here :vytask:`T5160`" +msgstr "For latest releases, refer the `firewall (interface-groups) <https://docs.vyos.io/en/latest/configuration/firewall/general.html#interface-groups>`_ main page to configure zone based rules. New syntax was introduced here :vytask:`T5160`" + +#: ../../configuration/protocols/mpls.rst:27 +msgid "For more information on how MPLS label switching works, please go visit `Wikipedia (MPLS)`_." +msgstr "For more information on how MPLS label switching works, please go visit `Wikipedia (MPLS)`_." + +#: ../../configuration/service/pppoe-server.rst:312 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:131 +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 "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." + +#: ../../configuration/protocols/bgp.rst:829 +msgid "For outbound updates the order of preference is:" +msgstr "For outbound updates the order of preference is:" + +#: ../../configuration/firewall/general.rst:497 +msgid "For reference, a description can be defined for every single rule, and for every defined custom chain." +msgstr "For reference, a description can be defined for every single rule, and for every defined custom chain." + +#: ../../configuration/service/webproxy.rst:84 +msgid "For security, the listen address should only be used on internal/trusted networks!" +msgstr "For security, the listen address should only be used on internal/trusted networks!" + +#: ../../configuration/system/lcd.rst:25 +msgid "For serial via USB port information please refor to: :ref:`hardware_usb`." +msgstr "For serial via USB port information please refor to: :ref:`hardware_usb`." + +#: ../../configuration/vpn/ipsec.rst:24 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:211 +msgid "For the OpenVPN traffic to pass through the WAN interface, you must create a firewall exception." +msgstr "For the OpenVPN traffic to pass through the WAN interface, you must create a firewall exception." + +#: ../../configuration/interfaces/wireguard.rst:209 +msgid "For the WireGuard traffic to pass through the WAN interface, you must create a firewall exception." +msgstr "For the WireGuard traffic to pass through the WAN interface, you must create a firewall exception." + +#: ../../configuration/nat/nat66.rst:92 +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 "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" + +#: ../../configuration/system/console.rst:7 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1183 +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 "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." + +#: ../../configuration/container/index.rst:179 +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 "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." + +#: ../../configuration/firewall/general.rst:66 +msgid "For traffic originated by the router, base chain is **output filter**: ``set firewall [ipv4 | ipv6] output filter ...``" +msgstr "For traffic originated by the router, base chain is **output filter**: ``set firewall [ipv4 | ipv6] output filter ...``" + +#: ../../configuration/firewall/general.rst:69 +msgid "For traffic towards the router itself, base chain is **input filter**: ``set firewall [ipv4 | ipv6] input filter ...``" +msgstr "For traffic towards the router itself, base chain is **input filter**: ``set firewall [ipv4 | ipv6] input filter ...``" + +#: ../../configuration/firewall/general.rst:62 +msgid "For transit traffic, which is received by the router and forwarded, base chain is **forward filter**: ``set firewall [ipv4 | ipv6] forward filter ...``" +msgstr "For transit traffic, which is received by the router and forwarded, base chain is **forward filter**: ``set firewall [ipv4 | ipv6] forward filter ...``" + +#: ../../configuration/protocols/ospf.rst:350 +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 "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." + +#: ../../configuration/service/dns.rst:21 +msgid "Forward incoming DNS queries to the DNS servers configured under the ``system name-server`` nodes." +msgstr "Forward incoming DNS queries to the DNS servers configured under the ``system name-server`` nodes." + +#: ../../configuration/highavailability/index.rst:362 +msgid "Forward method" +msgstr "Forward method" + +#: ../../configuration/service/dns.rst:36 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:69 +msgid "Four policies for reforwarding DHCP packets exist:" +msgstr "Four policies for reforwarding DHCP packets exist:" + +#: ../../configuration/protocols/bgp.rst:24 +msgid "From :rfc:`1930`:" +msgstr "From :rfc:`1930`:" + +#: ../../configuration/interfaces/wireguard.rst:400 +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 "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." + +#: ../../configuration/highavailability/index.rst:380 +msgid "Fwmark" +msgstr "Fwmark" + +#: ../../configuration/interfaces/geneve.rst:7 +msgid "GENEVE" +msgstr "GENEVE" + +#: ../../configuration/interfaces/geneve.rst:16 +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 "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." + +#: ../../configuration/interfaces/geneve.rst:49 +msgid "GENEVE options" +msgstr "GENEVE options" + +#: ../../configuration/vpn/ipsec.rst:21 +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 "GRE/IPIP/SIT and IPsec are widely accepted standards, which make this scheme easy to implement between VyOS and virtually any other router." + +#: ../../configuration/interfaces/tunnel.rst:211 +msgid "GRETAP" +msgstr "GRETAP" + +#: ../../configuration/interfaces/tunnel.rst:229 +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 "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." + +#: ../../configuration/interfaces/tunnel.rst:189 +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 "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." + +#: ../../configuration/interfaces/tunnel.rst:10 +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 "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." + +#: ../../configuration/pki/index.rst:121 +#: ../../configuration/pki/index.rst:126 +msgid "Genearate a new OpenVPN shared secret. The generated secred is the output to the console." +msgstr "Genearate a new OpenVPN shared secret. The generated secred is the output to the console." + +#: ../../configuration/protocols/isis.rst:25 +#: ../../configuration/protocols/ospf.rst:25 +#: ../../configuration/protocols/ospf.rst:1081 +#: ../../configuration/system/option.rst:11 +msgid "General" +msgstr "General" + +#: ../../configuration/protocols/babel.rst:18 +#: ../../configuration/protocols/bgp.rst:582 +#: ../../configuration/protocols/rip.rst:23 +msgid "General Configuration" +msgstr "General Configuration" + +#: ../../configuration/interfaces/wireguard.rst:29 +msgid "Generate Keypair" +msgstr "Generate Keypair" + +#: ../../configuration/interfaces/macsec.rst:119 +msgid "Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key." +msgstr "Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key." + +#: ../../configuration/interfaces/macsec.rst:110 +msgid "Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key 128 or 256 bits." +msgstr "Generate :abbr:`MKA (MACsec Key Agreement protocol)` CAK key 128 or 256 bits." + +#: ../../configuration/pki/index.rst:153 +#: ../../configuration/pki/index.rst:157 +msgid "Generate a WireGuard pre-shared secret used for peers to communicate." +msgstr "Generate a WireGuard pre-shared secret used for peers to communicate." + +#: ../../configuration/pki/index.rst:136 +#: ../../configuration/pki/index.rst:141 +msgid "Generate a new WireGuard public/private key portion and output the result to the console." +msgstr "Generate a new WireGuard public/private key portion and output the result to the console." + +#: ../../configuration/pki/index.rst:104 +#: ../../configuration/pki/index.rst:111 +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 "Generate a new set of :abbr:`DH (Diffie-Hellman)` parameters. The key size is requested by the CLI and defaults to 2048 bit." + +#: ../../configuration/service/ssh.rst:194 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:44 +msgid "Generates a keypair, which includes the public and private parts, and build a configuration command to install this key to ``interface``." +msgstr "Generates a keypair, which includes the public and private parts, and build a configuration command to install this key to ``interface``." + +#: ../../configuration/interfaces/tunnel.rst:106 +msgid "Generic Routing Encapsulation (GRE)" +msgstr "Generic Routing Encapsulation (GRE)" + +#: ../../configuration/interfaces/geneve.rst:25 +msgid "Geneve Header:" +msgstr "Geneve Header:" + +#: ../../configuration/interfaces/wireguard.rst:364 +msgid "Get a list of all wireguard interfaces" +msgstr "Get a list of all wireguard interfaces" + +#: ../../configuration/system/acceleration.rst:50 +msgid "Get an overview over the encryption counters." +msgstr "Get an overview over the encryption counters." + +#: ../../configuration/service/lldp.rst:91 +msgid "Get detailed information about LLDP neighbors." +msgstr "Get detailed information about LLDP neighbors." + +#: ../../configuration/protocols/rpki.rst:39 +msgid "Getting started" +msgstr "Getting started" + +#: ../../configuration/service/dns.rst:54 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:577 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:150 +msgid "Gloabal" +msgstr "Gloabal" + +#: ../../configuration/firewall/general.rst:84 +msgid "Global Options" +msgstr "Global Options" + +#: ../../configuration/highavailability/index.rst:224 +msgid "Global options" +msgstr "Global options" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:152 +msgid "Global parameters" +msgstr "Global parameters" + +#: ../../configuration/firewall/general-legacy.rst:36 +msgid "Global settings" +msgstr "Global settings" + +#: ../../configuration/protocols/ospf.rst:498 +#: ../../configuration/protocols/ospf.rst:1210 +msgid "Graceful Restart" +msgstr "Graceful Restart" + +#: ../../configuration/highavailability/index.rst:236 +msgid "Gratuitous ARP" +msgstr "Gratuitous ARP" + +#: ../../configuration/firewall/general.rst:184 +#: ../../configuration/firewall/general-legacy.rst:153 +msgid "Groups" +msgstr "Groups" + +#: ../../configuration/firewall/general-legacy.rst:161 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:420 +msgid "HQ's router requires the following steps to generate crypto materials for the Branch 1:" +msgstr "HQ's router requires the following steps to generate crypto materials for the Branch 1:" + +#: ../../configuration/service/https.rst:5 +msgid "HTTP-API" +msgstr "HTTP-API" + +#: ../../configuration/service/dns.rst:304 +msgid "HTTP based services" +msgstr "HTTP based services" + +#: ../../configuration/service/monitoring.rst:51 +#: ../../configuration/service/monitoring.rst:55 +msgid "HTTP basic authentication username" +msgstr "HTTP basic authentication username" + +#: ../../configuration/system/option.rst:27 +msgid "HTTP client" +msgstr "HTTP client" + +#: ../../configuration/interfaces/wireless.rst:137 +msgid "HT (High Throughput) capabilities (802.11n)" +msgstr "HT (High Throughput) capabilities (802.11n)" + +#: ../../configuration/nat/nat44.rst:398 +msgid "Hairpin NAT/NAT Reflection" +msgstr "Hairpin NAT/NAT Reflection" + +#: ../../configuration/service/dhcp-server.rst:643 +msgid "Hand out prefixes of size `<length>` to clients in subnet `<prefix>` when they request for prefix delegation." +msgstr "Hand out prefixes of size `<length>` to clients in subnet `<prefix>` when they request for prefix delegation." + +#: ../../configuration/loadbalancing/wan.rst:268 +msgid "Handling and monitoring" +msgstr "Handling and monitoring" + +#: ../../configuration/nat/nat44.rst:389 +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 "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." + +#: ../../configuration/highavailability/index.rst:372 +msgid "Health-check" +msgstr "Health-check" + +#: ../../configuration/highavailability/index.rst:308 +msgid "Health check scripts" +msgstr "Health check scripts" + +#: ../../configuration/loadbalancing/wan.rst:124 +msgid "Health checks" +msgstr "Health checks" + +#: ../../configuration/nat/nat44.rst:602 +msgid "Here's an extract of a simple 1-to-1 NAT configuration with one internal and one external interface:" +msgstr "Here's an extract of a simple 1-to-1 NAT configuration with one internal and one external interface:" + +#: ../../configuration/nat/nat44.rst:668 +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 "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." + +#: ../../configuration/protocols/isis.rst:357 +msgid "Here's the IP routes that are populated. Just the loopback:" +msgstr "Here's the IP routes that are populated. Just the loopback:" + +#: ../../configuration/protocols/ospf.rst:862 +msgid "Here's the neighbors up:" +msgstr "Here's the neighbors up:" + +#: ../../configuration/protocols/ospf.rst:878 +msgid "Here's the routes:" +msgstr "Here's the routes:" + +#: ../../configuration/firewall/general-legacy.rst:759 +msgid "Here are some examples for applying a rule-set to an interface" +msgstr "Here are some examples for applying a rule-set to an interface" + +#: ../../configuration/interfaces/tunnel.rst:146 +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 "Here is a second example of a dual-stack tunnel over IPv6 between a VyOS router and a Linux host using systemd-networkd." + +#: ../../configuration/protocols/isis.rst:44 +msgid "Here is an example :abbr:`NET (Network Entity Title)` value:" +msgstr "Here is an example :abbr:`NET (Network Entity Title)` value:" + +#: ../../configuration/protocols/rpki.rst:167 +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 "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`." + +#: ../../configuration/protocols/isis.rst:523 +#: ../../configuration/protocols/ospf.rst:1036 +#: ../../configuration/protocols/segment-routing.rst:251 +#: ../../configuration/protocols/segment-routing.rst:330 +msgid "Here is the routing tables showing the MPLS segment routing label operations:" +msgstr "Here is the routing tables showing the MPLS segment routing label operations:" + +#: ../../configuration/nat/nat44.rst:633 +msgid "Here we provide two examples on how to apply NAT Load Balance." +msgstr "Here we provide two examples on how to apply NAT Load Balance." + +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +#: ../../_include/interface-ip.txt:170 +msgid "Hewlett-Packard call it Source-Port filtering or port-isolation" +msgstr "Hewlett-Packard call it Source-Port filtering or port-isolation" + +#: ../../configuration/trafficpolicy/index.rst:273 +#: ../../configuration/trafficpolicy/index.rst:279 +#: ../../configuration/trafficpolicy/index.rst:285 +#: ../../configuration/trafficpolicy/index.rst:291 +msgid "High" +msgstr "High" + +#: ../../configuration/highavailability/index.rst:6 +msgid "High availability" +msgstr "High availability" + +#: ../../configuration/interfaces/pppoe.rst:28 +msgid "Home Users" +msgstr "Home Users" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Hop count field of the outgoing RA packets" +msgstr "Hop count field of the outgoing RA packets" + +#: ../../configuration/system/host-name.rst:5 +msgid "Host Information" +msgstr "Host Information" + +#: ../../configuration/system/host-name.rst:10 +msgid "Host name" +msgstr "Host name" + +#: ../../configuration/service/dhcp-server.rst:698 +msgid "Host specific mapping shall be named ``client1``" +msgstr "Host specific mapping shall be named ``client1``" + +#: ../../configuration/system/host-name.rst:16 +msgid "Hostname" +msgstr "Hostname" + +#: ../../configuration/system/host-name.rst:47 +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. This is the VyOS equivalent to `/etc/hosts` file entries." +msgstr "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. This is the VyOS equivalent to `/etc/hosts` file entries." + +#: ../../configuration/service/eventhandler.rst:17 +msgid "How to configure Event Handler" +msgstr "How to configure Event Handler" + +#: ../../configuration/trafficpolicy/index.rst:25 +msgid "How to make it work" +msgstr "How to make it work" + +#: ../../configuration/vpn/ipsec.rst:263 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:80 +msgid "However, since VyOS 1.4, it is possible to verify self-signed certificates using certificate fingerprints." +msgstr "However, since VyOS 1.4, it is possible to verify self-signed certificates using certificate fingerprints." + +#: ../../configuration/interfaces/wireguard.rst:319 +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 "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." + +#: ../../configuration/interfaces/wwan.rst:317 +msgid "Huawei ME909s-120 miniPCIe card (LTE)" +msgstr "Huawei ME909s-120 miniPCIe card (LTE)" + +#: ../../configuration/interfaces/wwan.rst:316 +msgid "Huawei ME909u-521 miniPCIe card (LTE)" +msgstr "Huawei ME909u-521 miniPCIe card (LTE)" + +#: ../../configuration/vpn/dmvpn.rst:185 +msgid "Hub" +msgstr "Hub" + +#: ../../configuration/interfaces/macsec.rst:79 +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 "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." + +#: ../../configuration/interfaces/macsec.rst:97 +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 "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." + +#: ../../_include/interface-vlan-8021ad.txt:3 +#: ../../_include/interface-vlan-8021ad.txt:3 +#: ../../_include/interface-vlan-8021ad.txt:3 +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 "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)." + +#: ../../_include/interface-vlan-8021q.txt:1 +#: ../../_include/interface-vlan-8021q.txt:1 +#: ../../_include/interface-vlan-8021q.txt:1 +#: ../../_include/interface-vlan-8021q.txt:1 +#: ../../_include/interface-vlan-8021q.txt:1 +#: ../../_include/interface-vlan-8021q.txt:1 +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 "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." + +#: ../../configuration/nat/nat44.rst:55 +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 "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." + +#: ../../configuration/protocols/igmp.rst:179 +msgid "IGMP Proxy" +msgstr "IGMP Proxy" + +#: ../../configuration/nat/nat44.rst:726 +msgid "IKE Phase:" +msgstr "IKE Phase:" + +#: ../../configuration/vpn/ipsec.rst:34 +msgid "IKE (Internet Key Exchange) Attributes" +msgstr "IKE (Internet Key Exchange) Attributes" + +#: ../../configuration/vpn/ipsec.rst:35 +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 "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" + +#: ../../configuration/vpn/site2site_ipsec.rst:156 +msgid "IKEv1" +msgstr "IKEv1" + +#: ../../configuration/vpn/site2site_ipsec.rst:267 +msgid "IKEv2" +msgstr "IKEv2" + +#: ../../configuration/system/ip.rst:3 +msgid "IP" +msgstr "IP" + +#: ../../configuration/interfaces/tunnel.rst:46 +msgid "IP6IP6" +msgstr "IP6IP6" + +#: ../../configuration/interfaces/tunnel.rst:30 +msgid "IPIP" +msgstr "IPIP" + +#: ../../configuration/interfaces/tunnel.rst:64 +msgid "IPIP6" +msgstr "IPIP6" + +#: ../../configuration/interfaces/l2tpv3.rst:140 +msgid "IPSec:" +msgstr "IPSec:" + +#: ../../configuration/nat/nat44.rst:722 +msgid "IPSec IKE and ESP" +msgstr "IPSec IKE and ESP" + +#: ../../configuration/nat/nat44.rst:687 +msgid "IPSec IKE and ESP Groups;" +msgstr "IPSec IKE and ESP Groups;" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:4 +msgid "IPSec IKEv2 Remote Access VPN" +msgstr "IPSec IKEv2 Remote Access VPN" + +#: ../../configuration/vpn/site2site_ipsec.rst:281 +msgid "IPSec IKEv2 site2site VPN" +msgstr "IPSec IKEv2 site2site VPN" + +#: ../../configuration/vpn/site2site_ipsec.rst:281 +msgid "IPSec IKEv2 site2site VPN (source ./draw.io/vpn_s2s_ikev2.drawio)" +msgstr "IPSec IKEv2 site2site VPN (source ./draw.io/vpn_s2s_ikev2.drawio)" + +#: ../../configuration/nat/nat44.rst:758 +msgid "IPSec VPN Tunnels" +msgstr "IPSec VPN Tunnels" + +#: ../../configuration/nat/nat44.rst:688 +msgid "IPSec VPN tunnels." +msgstr "IPSec VPN tunnels." + +#: ../../configuration/system/host-name.rst:12 +msgid "IP address" +msgstr "IP address" + +#: ../../configuration/service/dhcp-server.rst:237 +msgid "IP address ``192.168.1.100`` shall be statically mapped to client named ``client1``" +msgstr "IP address ``192.168.1.100`` shall be statically mapped to client named ``client1``" + +#: ../../configuration/interfaces/wireless.rst:349 +#: ../../configuration/interfaces/wireless.rst:549 +msgid "IP address ``192.168.2.1/24``" +msgstr "IP address ``192.168.2.1/24``" + +#: ../../configuration/service/dhcp-server.rst:319 +msgid "IP address for DHCP server identifier" +msgstr "IP address for DHCP server identifier" + +#: ../../configuration/service/dhcp-server.rst:309 +msgid "IP address of NTP server" +msgstr "IP address of NTP server" + +#: ../../configuration/service/dhcp-server.rst:349 +msgid "IP address of POP3 server" +msgstr "IP address of POP3 server" + +#: ../../configuration/service/dhcp-server.rst:344 +msgid "IP address of SMTP server" +msgstr "IP address of SMTP server" + +#: ../../configuration/policy/route-map.rst:65 +msgid "IP address of route to match, based on access-list." +msgstr "IP address of route to match, based on access-list." + +#: ../../configuration/policy/route-map.rst:70 +msgid "IP address of route to match, based on prefix-list." +msgstr "IP address of route to match, based on prefix-list." + +#: ../../configuration/policy/route-map.rst:75 +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 "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.." + +#: ../../configuration/service/dhcp-server.rst:379 +msgid "IP address to exclude from DHCP lease range" +msgstr "IP address to exclude from DHCP lease range" + +#: ../../configuration/service/conntrack-sync.rst:67 +msgid "IP addresses or networks for which local conntrack entries will not be synced" +msgstr "IP addresses or networks for which local conntrack entries will not be synced" + +#: ../../configuration/service/lldp.rst:29 +msgid "IP management address" +msgstr "IP management address" + +#: ../../configuration/nat/nat44.rst:17 +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 "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." + +#: ../../configuration/policy/route-map.rst:83 +msgid "IP next-hop of route to match, based on access-list." +msgstr "IP next-hop of route to match, based on access-list." + +#: ../../configuration/policy/route-map.rst:88 +msgid "IP next-hop of route to match, based on ip address." +msgstr "IP next-hop of route to match, based on ip address." + +#: ../../configuration/policy/route-map.rst:98 +msgid "IP next-hop of route to match, based on prefix-list." +msgstr "IP next-hop of route to match, based on prefix-list." + +#: ../../configuration/policy/route-map.rst:93 +msgid "IP next-hop of route to match, based on prefix length." +msgstr "IP next-hop of route to match, based on prefix length." + +#: ../../configuration/policy/route-map.rst:103 +msgid "IP next-hop of route to match, based on type." +msgstr "IP next-hop of route to match, based on type." + +#: ../../configuration/trafficpolicy/index.rst:784 +msgid "IP precedence as defined in :rfc:`791`:" +msgstr "IP precedence as defined in :rfc:`791`:" + +#: ../../configuration/vpn/l2tp.rst:33 +msgid "IP protocol number 50 (ESP)" +msgstr "IP protocol number 50 (ESP)" + +#: ../../configuration/policy/route-map.rst:108 +msgid "IP route source of route to match, based on access-list." +msgstr "IP route source of route to match, based on access-list." + +#: ../../configuration/policy/route-map.rst:113 +msgid "IP route source of route to match, based on prefix-list." +msgstr "IP route source of route to match, based on prefix-list." + +#: ../../configuration/service/ipoe-server.rst:7 +msgid "IPoE Server" +msgstr "IPoE Server" + +#: ../../configuration/service/ipoe-server.rst:30 +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 "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." + +#: ../../configuration/service/ipoe-server.rst:13 +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 "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." + +#: ../../configuration/service/ipoe-server.rst:152 +msgid "IPoE server will listen on interfaces eth1.50 and eth1.51" +msgstr "IPoE server will listen on interfaces eth1.50 and eth1.51" + +#: ../../configuration/vpn/ipsec.rst:5 +msgid "IPsec" +msgstr "IPsec" + +#: ../../configuration/vpn/ipsec.rst:172 +msgid "IPsec policy matching GRE" +msgstr "IPsec policy matching GRE" + +#: ../../configuration/service/pppoe-server.rst:359 +msgid "IPv4" +msgstr "IPv4" + +#: ../../configuration/interfaces/vxlan.rst:85 +msgid "IPv4/IPv6 remote address of the VXLAN tunnel. Alternative to multicast, the remote IPv4/IPv6 address can set directly." +msgstr "IPv4/IPv6 remote address of the VXLAN tunnel. Alternative to multicast, the remote IPv4/IPv6 address can set directly." + +#: ../../configuration/service/dhcp-server.rst:324 +msgid "IPv4 address of next bootstrap server" +msgstr "IPv4 address of next bootstrap server" + +#: ../../configuration/service/dhcp-server.rst:284 +msgid "IPv4 address of router on the client's subnet" +msgstr "IPv4 address of router on the client's subnet" + +#: ../../configuration/system/flow-accounting.rst:111 +msgid "IPv4 or IPv6 source address of NetFlow packets" +msgstr "IPv4 or IPv6 source address of NetFlow packets" + +#: ../../configuration/protocols/bgp.rst:1098 +msgid "IPv4 peering" +msgstr "IPv4 peering" + +#: ../../configuration/service/dhcp-relay.rst:16 +msgid "IPv4 relay" +msgstr "IPv4 relay" + +#: ../../configuration/policy/route.rst:5 +msgid "IPv4 route and IPv6 route policies are defined in this section. These route policies can then be associated to interfaces." +msgstr "IPv4 route and IPv6 route policies are defined in this section. These route policies can then be associated to interfaces." + +#: ../../configuration/protocols/babel.rst:161 +msgid "IPv4 route source: bgp, connected, eigrp, isis, kernel, nhrp, ospf, rip, static." +msgstr "IPv4 route source: bgp, connected, eigrp, isis, kernel, nhrp, ospf, rip, static." + +#: ../../configuration/service/dhcp-server.rst:11 +msgid "IPv4 server" +msgstr "IPv4 server" + +#: ../../configuration/interfaces/pppoe.rst:231 +#: ../../configuration/service/pppoe-server.rst:280 +#: ../../configuration/system/ipv6.rst:3 +msgid "IPv6" +msgstr "IPv6" + +#: ../../configuration/policy/access-list.rst:44 +msgid "IPv6 Access List" +msgstr "IPv6 Access List" + +#: ../../configuration/interfaces/pppoe.rst:366 +msgid "IPv6 DHCPv6-PD Example" +msgstr "IPv6 DHCPv6-PD Example" + +#: ../../configuration/service/ipoe-server.rst:69 +msgid "IPv6 DNS addresses are optional." +msgstr "IPv6 DNS addresses are optional." + +#: ../../configuration/protocols/pim6.rst:5 +msgid "IPv6 Multicast" +msgstr "IPv6 Multicast" + +#: ../../configuration/service/pppoe-server.rst:295 +msgid "IPv6 Prefix Delegation" +msgstr "IPv6 Prefix Delegation" + +#: ../../configuration/policy/prefix-list.rst:50 +msgid "IPv6 Prefix Lists" +msgstr "IPv6 Prefix Lists" + +#: ../../configuration/service/ipoe-server.rst:63 +msgid "IPv6 SLAAC and IA-PD" +msgstr "IPv6 SLAAC and IA-PD" + +#: ../../configuration/trafficpolicy/index.rst:212 +msgid "IPv6 TCP filters will only match IPv6 packets with no header extension, see https://en.wikipedia.org/wiki/IPv6_packet#Extension_headers" +msgstr "IPv6 TCP filters will only match IPv6 packets with no header extension, see https://en.wikipedia.org/wiki/IPv6_packet#Extension_headers" + +#: ../../configuration/service/dhcp-server.rst:696 +msgid "IPv6 address ``2001:db8::101`` shall be statically mapped" +msgstr "IPv6 address ``2001:db8::101`` shall be statically mapped" + +#: ../../configuration/policy/route-map.rst:118 +msgid "IPv6 address of route to match, based on IPv6 access-list." +msgstr "IPv6 address of route to match, based on IPv6 access-list." + +#: ../../configuration/policy/route-map.rst:123 +msgid "IPv6 address of route to match, based on IPv6 prefix-list." +msgstr "IPv6 address of route to match, based on IPv6 prefix-list." + +#: ../../configuration/policy/route-map.rst:128 +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 "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.." + +#: ../../configuration/service/pppoe-server.rst:283 +msgid "IPv6 client's prefix assignment" +msgstr "IPv6 client's prefix assignment" + +#: ../../configuration/protocols/bgp.rst:1143 +msgid "IPv6 peering" +msgstr "IPv6 peering" + +#: ../../configuration/policy/prefix-list.rst:72 +msgid "IPv6 prefix." +msgstr "IPv6 prefix." + +#: ../../configuration/service/dhcp-server.rst:697 +msgid "IPv6 prefix ``2001:db8:0:101::/64`` shall be statically mapped" +msgstr "IPv6 prefix ``2001:db8:0:101::/64`` shall be statically mapped" + +#: ../../configuration/service/dhcp-relay.rst:132 +msgid "IPv6 relay" +msgstr "IPv6 relay" + +#: ../../configuration/protocols/babel.rst:163 +msgid "IPv6 route source: bgp, connected, eigrp, isis, kernel, nhrp, ospfv3, ripng, static." +msgstr "IPv6 route source: bgp, connected, eigrp, isis, kernel, nhrp, ospfv3, ripng, static." + +#: ../../configuration/service/dhcp-server.rst:578 +msgid "IPv6 server" +msgstr "IPv6 server" + +#: ../../configuration/highavailability/index.rst:51 +msgid "IPv6 support" +msgstr "IPv6 support" + +#: ../../configuration/protocols/isis.rst:7 +msgid "IS-IS" +msgstr "IS-IS" + +#: ../../configuration/protocols/isis.rst:75 +msgid "IS-IS Global Configuration" +msgstr "IS-IS Global Configuration" + +#: ../../configuration/protocols/segment-routing.rst:35 +msgid "IS-IS SR Configuration" +msgstr "IS-IS SR Configuration" + +#: ../../configuration/service/dhcp-server.rst:266 +msgid "ISC-DHCP Option name" +msgstr "ISC-DHCP Option name" + +#: ../../configuration/vpn/openconnect.rst:226 +msgid "Identity Based Configuration" +msgstr "Identity Based Configuration" + +#: ../../configuration/trafficpolicy/index.rst:903 +msgid "If **max-threshold** is set but **min-threshold is not, then **min-threshold** is scaled to 50% of **max-threshold**." +msgstr "If **max-threshold** is set but **min-threshold is not, then **min-threshold** is scaled to 50% of **max-threshold**." + +#: ../../configuration/interfaces/bonding.rst:253 +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 "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." + +#: ../../configuration/pki/index.rst:249 +msgid "If CA is present, this certificate will be included in generated CRLs" +msgstr "If CA is present, this certificate will be included in generated CRLs" + +#: ../../_include/interface-per-client-thread.txt:8 +#: ../../_include/interface-per-client-thread.txt:8 +msgid "If CLI option is not specified, this feature is disabled." +msgstr "If CLI option is not specified, this feature is disabled." + +#: ../../configuration/protocols/bgp.rst:225 +msgid "If :cfgcmd:`strict` is set the BGP session won’t become established until the BGP neighbor sets local Role on its side. This configuration parameter is defined in RFC :rfc:`9234` and is used to enforce the corresponding configuration at your counter-parts side." +msgstr "If :cfgcmd:`strict` is set the BGP session won’t become established until the BGP neighbor sets local Role on its side. This configuration parameter is defined in RFC :rfc:`9234` and is used to enforce the corresponding configuration at your counter-parts side." + +#: ../../configuration/service/console-server.rst:115 +msgid "If ``alias`` is set, it can be used instead of the device when connecting." +msgstr "If ``alias`` is set, it can be used instead of the device when connecting." + +#: ../../configuration/vpn/l2tp.rst:29 +msgid "If a local firewall policy is in place on your external interface you will need to allow the ports below:" +msgstr "If a local firewall policy is in place on your external interface you will need to allow the ports below:" + +#: ../../configuration/container/index.rst:22 +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 "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" + +#: ../../configuration/service/dhcp-server.rst:68 +#: ../../configuration/service/dhcp-server.rst:157 +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 "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)." + +#: ../../configuration/protocols/bgp.rst:771 +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 "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." + +#: ../../configuration/firewall/general.rst:329 +msgid "If a rule is defined, then an action must be defined for it. This tells the firewall what to do if all criteria matchers defined for such rule do match." +msgstr "If a rule is defined, then an action must be defined for it. This tells the firewall what to do if all criteria matchers defined for such rule do match." + +#: ../../configuration/service/dhcp-server.rst:161 +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 "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." + +#: ../../configuration/nat/nat44.rst:43 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:76 +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 "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." + +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +#: ../../_include/interface-ip.txt:72 +msgid "If configured, incoming IP directed broadcast packets on this interface will be forwarded." +msgstr "If configured, incoming IP directed broadcast packets on this interface will be forwarded." + +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +#: ../../_include/interface-ip.txt:124 +msgid "If configured, reply only if the target IP address is local address configured on the incoming interface." +msgstr "If configured, reply only if the target IP address is local address configured on the incoming interface." + +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +#: ../../_include/interface-ip.txt:106 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:30 +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 "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." + +#: ../../configuration/nat/nat44.rst:542 +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 "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`." + +#: ../../configuration/trafficpolicy/index.rst:1031 +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 "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." + +#: ../../configuration/protocols/igmp.rst:221 +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 "If it's vital that the daemon should act exactly like a real multicast client on the upstream interface, this function should be enabled." + +#: ../../configuration/interfaces/openvpn.rst:69 +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 "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." + +#: ../../configuration/system/syslog.rst:87 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:314 +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 "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...)." + +#: ../../configuration/protocols/bgp.rst:100 +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 "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." + +#: ../../configuration/protocols/rpki.rst:86 +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 "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." + +#: ../../configuration/nat/nat44.rst:205 +msgid "If no destination is specified the rule will match on any destination address and port." +msgstr "If no destination is specified the rule will match on any destination address and port." + +#: ../../configuration/policy/prefix-list.rst:9 +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 "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." + +#: ../../configuration/system/syslog.rst:207 +msgid "If no option is specified, this defaults to `all`." +msgstr "If no option is specified, this defaults to `all`." + +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +#: ../../_include/interface-ip.txt:42 +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 "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)." + +#: ../../configuration/system/ip.rst:17 +msgid "If set, IPv4 directed broadcast forwarding will be completely disabled regardless of whether per-interface directed broadcast forwarding is enabled or not." +msgstr "If set, IPv4 directed broadcast forwarding will be completely disabled regardless of whether per-interface directed broadcast forwarding is enabled or not." + +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +#: ../../_include/interface-ip.txt:36 +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 "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." + +#: ../../configuration/system/task-scheduler.rst:24 +msgid "If suffix is omitted, minutes are implied." +msgstr "If suffix is omitted, minutes are implied." + +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +#: ../../_include/interface-ip.txt:91 +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 "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." + +#: ../../configuration/protocols/bgp.rst:380 +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 "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." + +#: ../../configuration/protocols/bgp.rst:377 +msgid "If the AS-Path for the route has only private ASNs, the private ASNs are removed." +msgstr "If the AS-Path for the route has only private ASNs, the private ASNs are removed." + +#: ../../configuration/vpn/dmvpn.rst:86 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:211 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:218 +msgid "If the RADIUS server uses the attribute ``NAS-Port-Id``, ppp tunnels will be renamed." +msgstr "If the RADIUS server uses the attribute ``NAS-Port-Id``, ppp tunnels will be renamed." + +#: ../../configuration/protocols/bgp.rst:444 +msgid "If the :cfgcmd:`no-prepend` attribute is specified, then the supplied local-as is not prepended to the received AS_PATH." +msgstr "If the :cfgcmd:`no-prepend` attribute is specified, then the supplied local-as is not prepended to the received AS_PATH." + +#: ../../configuration/protocols/bgp.rst:447 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:892 +msgid "If the average queue size is lower than the **min-threshold**, an arriving packet will be placed in the queue." +msgstr "If the average queue size is lower than the **min-threshold**, an arriving packet will be placed in the queue." + +#: ../../configuration/trafficpolicy/index.rst:899 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:187 +#: ../../configuration/interfaces/bonding.rst:216 +msgid "If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash." +msgstr "If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash." + +#: ../../configuration/vpn/dmvpn.rst:75 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:24 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:126 +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 "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`" + +#: ../../configuration/service/dhcp-server.rst:72 +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 "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." + +#: ../../configuration/vpn/site2site_ipsec.rst:237 +msgid "If there is SNAT rules on eth1, need to add exclude rule" +msgstr "If there is SNAT rules on eth1, need to add exclude rule" + +#: ../../configuration/interfaces/wireguard.rst:57 +#: ../../configuration/interfaces/wireguard.rst:120 +msgid "If this command is invoked from configure mode with the ``run`` prefix the key is automatically installed to the appropriate interface:" +msgstr "If this command is invoked from configure mode with the ``run`` prefix the key is automatically installed to the appropriate interface:" + +#: ../../configuration/service/dhcp-relay.rst:166 +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 "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." + +#: ../../configuration/protocols/bgp.rst:768 +msgid "If this option is enabled, then the already-selected check, where already selected eBGP routes are preferred, is skipped." +msgstr "If this option is enabled, then the already-selected check, where already selected eBGP routes are preferred, is skipped." + +#: ../../configuration/vpn/sstp.rst:172 +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 "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." + +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +#: ../../_include/interface-ip.txt:75 +msgid "If this option is unset (default), incoming IP directed broadcast packets will not be forwarded." +msgstr "If this option is unset (default), incoming IP directed broadcast packets will not be forwarded." + +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +#: ../../_include/interface-ip.txt:127 +msgid "If this option is unset (default), reply for any local target IP address, configured on any interface." +msgstr "If this option is unset (default), reply for any local target IP address, configured on any interface." + +#: ../../configuration/interfaces/pppoe.rst:163 +msgid "If this parameter is not set, the default holdoff time is 30 seconds." +msgstr "If this parameter is not set, the default holdoff time is 30 seconds." + +#: ../../configuration/interfaces/pppoe.rst:153 +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 "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." + +#: ../../configuration/system/login.rst:270 +msgid "If unset, 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 "If unset, 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." + +#: ../../configuration/system/login.rst:339 +msgid "If unset, incoming connections to the TACACS 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 "If unset, incoming connections to the TACACS 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." + +#: ../../configuration/nat/nat44.rst:788 +msgid "If you've completed all the above steps you no doubt want to see if it's all working." +msgstr "If you've completed all the above steps you no doubt want to see if it's all working." + +#: ../../configuration/protocols/bgp.rst:489 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:637 +msgid "If you are a hacker or want to try on your own we support passing raw OpenVPN options to OpenVPN." +msgstr "If you are a hacker or want to try on your own we support passing raw OpenVPN options to OpenVPN." + +#: ../../configuration/system/name-server.rst:7 +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 "If you are configuring a VRF for management purposes, there is currently no way to force system DNS traffic via a specific VRF." + +#: ../../configuration/protocols/rpki.rst:30 +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 "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?\"" + +#: ../../configuration/protocols/rpki.rst:64 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:483 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:165 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:306 +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 "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." + +#: ../../configuration/system/ip.rst:43 +#: ../../configuration/system/ipv6.rst:39 +#: ../../configuration/vrf/index.rst:57 +#: ../../configuration/vrf/index.rst:67 +msgid "If you choose any as the option that will cause all protocols that are sending routes to zebra." +msgstr "If you choose any as the option that will cause all protocols that are sending routes to zebra." + +#: ../../configuration/trafficpolicy/index.rst:1114 +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 "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." + +#: ../../configuration/protocols/babel.rst:37 +msgid "If you enable this, you will probably want to set diversity-factor and channel below." +msgstr "If you enable this, you will probably want to set diversity-factor and channel below." + +#: ../../configuration/interfaces/bonding.rst:312 +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 "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." + +#: ../../configuration/service/snmp.rst:247 +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 "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." + +#: ../../configuration/service/console-server.rst:15 +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 "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." + +#: ../../configuration/protocols/ospf.rst:362 +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 "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." + +#: ../../configuration/nat/nat44.rst:584 +msgid "If you have configured the `INSIDE-OUT` policy, you will need to add additional rules to permit inbound NAT traffic." +msgstr "If you have configured the `INSIDE-OUT` policy, you will need to add additional rules to permit inbound NAT traffic." + +#: ../../configuration/system/flow-accounting.rst:65 +msgid "If you need to sample also egress traffic, you may want to configure egress flow-accounting:" +msgstr "If you need to sample also egress traffic, you may want to configure egress flow-accounting:" + +#: ../../configuration/interfaces/openvpn.rst:518 +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 "If you only want to check if the user account is enabled and can authenticate (against the primary group) the following snipped is sufficient:" + +#: ../../configuration/vpn/l2tp.rst:196 +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 "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." + +#: ../../configuration/system/console.rst:41 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:140 +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 "If you want to change the maximum number of flows, which are tracking simultaneously, you may do this with this command (default 8192)." + +#: ../../configuration/firewall/general-legacy.rst:375 +msgid "If you want to disable a rule but let it in the configuration." +msgstr "If you want to disable a rule but let it in the configuration." + +#: ../../configuration/system/login.rst:294 +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 "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." + +#: ../../configuration/service/webproxy.rst:340 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:7 +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 "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." + +#: ../../configuration/protocols/bgp.rst:760 +msgid "Ignore AS_PATH length when selecting a route" +msgstr "Ignore AS_PATH length when selecting a route" + +#: ../../configuration/highavailability/index.rst:181 +msgid "Ignore VRRP main interface faults" +msgstr "Ignore VRRP main interface faults" + +#: ../../configuration/service/snmp.rst:63 +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 "Image thankfully borrowed from https://en.wikipedia.org/wiki/File:SNMP_communication_principles_diagram.PNG which is under the GNU Free Documentation License" + +#: ../../configuration/vpn/site2site_ipsec.rst:275 +msgid "Imagine the following topology" +msgstr "Imagine the following topology" + +#: ../../configuration/trafficpolicy/index.rst:799 +msgid "Immediate" +msgstr "Immediate" + +#: ../../configuration/protocols/rpki.rst:46 +msgid "Imported prefixes during the validation may have values:" +msgstr "Imported prefixes during the validation may have values:" + +#: ../../configuration/protocols/static.rst:158 +msgid "In Internet Protocol Version 6 (IPv6) networks, the functionality of ARP is provided by the Neighbor Discovery Protocol (NDP)." +msgstr "In Internet Protocol Version 6 (IPv6) networks, the functionality of ARP is provided by the Neighbor Discovery Protocol (NDP)." + +#: ../../configuration/trafficpolicy/index.rst:713 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:117 +msgid "In VyOS, ESP attributes are specified through ESP groups. Multiple proposals can be specified in a single group." +msgstr "In VyOS, ESP attributes are specified through ESP groups. Multiple proposals can be specified in a single group." + +#: ../../configuration/vpn/ipsec.rst:42 +msgid "In VyOS, IKE attributes are specified through IKE groups. Multiple proposals can be specified in a single group." +msgstr "In VyOS, IKE attributes are specified through IKE groups. Multiple proposals can be specified in a single group." + +#: ../../configuration/trafficpolicy/index.rst:126 +msgid "In VyOS, a class is identified by a number you can choose when configuring it." +msgstr "In VyOS, a class is identified by a number you can choose when configuring it." + +#: ../../_include/interface-vlan-8021ad.txt:22 +#: ../../_include/interface-vlan-8021ad.txt:22 +#: ../../_include/interface-vlan-8021ad.txt:22 +msgid "In VyOS the terms ``vif-s`` and ``vif-c`` stand for the ethertype tags that are used." +msgstr "In VyOS the terms ``vif-s`` and ``vif-c`` stand for the ethertype tags that are used." + +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +#: ../../_include/interface-ip.txt:166 +msgid "In :rfc:`3069` it is called VLAN Aggregation" +msgstr "In :rfc:`3069` it is called VLAN Aggregation" + +#: ../../configuration/firewall/zone.rst:41 +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 "In :vytask:`T2199` the syntax of the zone configuration was changed. The zone configuration moved from ``zone-policy zone <name>`` to ``firewall zone <name>``." + +#: ../../configuration/loadbalancing/wan.rst:14 +msgid "In a minimal configuration, the following must be provided:" +msgstr "In a minimal configuration, the following must be provided:" + +#: ../../_include/interface-vlan-8021ad.txt:16 +#: ../../_include/interface-vlan-8021ad.txt:16 +#: ../../_include/interface-vlan-8021ad.txt:16 +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 "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)." + +#: ../../configuration/protocols/rpki.rst:80 +msgid "In a nutshell, the current implementation provides the following features:" +msgstr "In a nutshell, the current implementation provides the following features:" + +#: ../../configuration/system/ipv6.rst:120 +msgid "In addition, you can specify many other parameters to get BGP information:" +msgstr "In addition, you can specify many other parameters to get BGP information:" + +#: ../../configuration/system/login.rst:301 +msgid "In addition to :abbr:`RADIUS (Remote Authentication Dial-In User Service)`, :abbr:`TACACS (Terminal Access Controller Access Control System)` can also be found in large deployments." +msgstr "In addition to :abbr:`RADIUS (Remote Authentication Dial-In User Service)`, :abbr:`TACACS (Terminal Access Controller Access Control System)` can also be found in large deployments." + +#: ../../configuration/system/flow-accounting.rst:88 +msgid "In addition to displaying flow accounting information locally, one can also exported them to a collection server." +msgstr "In addition to displaying flow accounting information locally, one can also exported them to a collection server." + +#: ../../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 +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 "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." + +#: ../../configuration/service/broadcast-relay.rst:48 +msgid "In addition you can also disable the whole service without the need to remove it from the current configuration." +msgstr "In addition you can also disable the whole service without the need to remove it from the current configuration." + +#: ../../configuration/interfaces/wireguard.rst:416 +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 "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." + +#: ../../configuration/firewall/general.rst:194 +#: ../../configuration/firewall/general-legacy.rst:170 +msgid "In an **address group** a single IP address or IP address ranges are defined." +msgstr "In an **address group** a single IP address or IP address ranges are defined." + +#: ../../configuration/interfaces/openvpn.rst:57 +msgid "In both cases, we will use the following settings:" +msgstr "In both cases, we will use the following settings:" + +#: ../../configuration/system/flow-accounting.rst:78 +msgid "In case, if you need to catch some logs from flow-accounting daemon, you may configure logging facility:" +msgstr "In case, if you need to catch some logs from flow-accounting daemon, you may configure logging facility:" + +#: ../../configuration/protocols/bgp.rst:238 +msgid "In case of peer-peer relationship routes can be received only if OTC value is equal to your neighbor AS number." +msgstr "In case of peer-peer relationship routes can be received only if OTC value is equal to your neighbor AS number." + +#: ../../configuration/trafficpolicy/index.rst:775 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:220 +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 "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:" + +#: ../../configuration/protocols/ospf.rst:339 +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 "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." + +#: ../../configuration/system/login.rst:236 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:45 +msgid "In order for flow accounting information to be collected and displayed for an interface, the interface must be configured for flow accounting." +msgstr "In order for flow accounting information to be collected and displayed for an interface, the interface must be configured for flow accounting." + +#: ../../configuration/service/dhcp-server.rst:196 +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 "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." + +#: ../../configuration/system/name-server.rst:47 +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 "In order for the system to use and complete unqualified host names, a list can be defined which will be used for domain searches." + +#: ../../configuration/protocols/mpls.rst:52 +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 "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." + +#: ../../configuration/protocols/bgp.rst:820 +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 "In order to control and modify routing information that is exchanged between peers you can use route-map, filter-list, prefix-list, distribute-list." + +#: ../../configuration/trafficpolicy/index.rst:121 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:27 +msgid "In order to have VyOS Traffic Control working you need to follow 2 steps:" +msgstr "In order to have VyOS Traffic Control working you need to follow 2 steps:" + +#: ../../configuration/interfaces/pppoe.rst:43 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:691 +msgid "In order to map specific IPv6 addresses to specific hosts static mappings can be created. The following example explains the process." +msgstr "In order to map specific IPv6 addresses to specific hosts static mappings can be created. The following example explains the process." + +#: ../../configuration/trafficpolicy/index.rst:402 +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 "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." + +#: ../../configuration/interfaces/ethernet.rst:95 +msgid "In order to use TSO/LRO with VMXNET3 adaters one must also enable the SG offloading option." +msgstr "In order to use TSO/LRO with VMXNET3 adaters one must also enable the SG offloading option." + +#: ../../configuration/nat/nat44.rst:382 +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 "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." + +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +#: ../../_include/interface-ip.txt:47 +msgid "In other words it allows control of which cards (usually 1) will respond to an arp request." +msgstr "In other words it allows control of which cards (usually 1) will respond to an arp request." + +#: ../../configuration/interfaces/openvpn.rst:55 +msgid "In our example, we used the key name ``openvpn-1`` which we will reference in our configuration." +msgstr "In our example, we used the key name ``openvpn-1`` which we will reference in our configuration." + +#: ../../configuration/nat/nat44.rst:507 +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 "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" + +#: ../../configuration/trafficpolicy/index.rst:906 +msgid "In principle, values must be :code:`min-threshold` < :code:`max-threshold` < :code:`queue-limit`." +msgstr "In principle, values must be :code:`min-threshold` < :code:`max-threshold` < :code:`queue-limit`." + +#: ../../configuration/vpn/dmvpn.rst:22 +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 "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." + +#: ../../configuration/protocols/ospf.rst:46 +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 "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>`" + +#: ../../configuration/interfaces/openvpn.rst:33 +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 "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`." + +#: ../../configuration/trafficpolicy/index.rst:109 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:27 +msgid "In the above example, an external IP of 192.0.2.2 is assumed." +msgstr "In the above example, an external IP of 192.0.2.2 is assumed." + +#: ../../configuration/protocols/bfd.rst:14 +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 "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." + +#: ../../configuration/interfaces/l2tpv3.rst:21 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:895 +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 "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**." + +#: ../../configuration/trafficpolicy/index.rst:564 +msgid "In the case you want to apply some kind of **shaping** to your **inbound** traffic, check the ingress-shaping_ section." +msgstr "In the case you want to apply some kind of **shaping** to your **inbound** traffic, check the ingress-shaping_ section." + +#: ../../configuration/trafficpolicy/index.rst:142 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:272 +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 "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." + +#: ../../configuration/nat/nat44.rst:321 +msgid "In the example used for the Quick Start configuration above, we demonstrate the following configuration:" +msgstr "In the example used for the Quick Start configuration above, we demonstrate the following configuration:" + +#: ../../configuration/system/login.rst:397 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:272 +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 "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." + +#: ../../configuration/highavailability/index.rst:118 +msgid "In the following example, when VLAN9 transitions, VLAN20 will also transition:" +msgstr "In the following example, when VLAN9 transitions, VLAN20 will also transition:" + +#: ../../configuration/protocols/igmp.rst:37 +msgid "In the following example we can see a basic multicast setup:" +msgstr "In the following example we can see a basic multicast setup:" + +#: ../../configuration/interfaces/tunnel.rst:66 +msgid "In the future this is expected to be a very useful protocol (though there are `other proposals`_)." +msgstr "In the future this is expected to be a very useful protocol (though there are `other proposals`_)." + +#: ../../configuration/highavailability/index.rst:400 +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 "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``" + +#: ../../configuration/system/default-route.rst:7 +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 "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." + +#: ../../configuration/system/acceleration.rst:7 +msgid "In this command tree, all hardware acceleration options will be handled. At the moment only `Intel® QAT`_ is supported" +msgstr "In this command tree, all hardware acceleration options will be handled. At the moment only `Intel® QAT`_ is supported" + +#: ../../configuration/system/name-server.rst:30 +msgid "In this example, some *OpenNIC* servers are used, two IPv4 addresses and two IPv6 addresses:" +msgstr "In this example, some *OpenNIC* servers are used, two IPv4 addresses and two IPv6 addresses:" + +#: ../../configuration/nat/nat44.rst:344 +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 "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." + +#: ../../configuration/nat/nat44.rst:498 +msgid "In this example, we will be using the example Quick Start configuration above as a starting point." +msgstr "In this example, we will be using the example Quick Start configuration above as a starting point." + +#: ../../configuration/highavailability/index.rst:430 +msgid "In this example all traffic destined to ports \"80, 2222, 8888\" protocol TCP marks to fwmark \"111\" and balanced between 2 real servers. Port \"0\" is required if multiple ports are used." +msgstr "In this example all traffic destined to ports \"80, 2222, 8888\" protocol TCP marks to fwmark \"111\" and balanced between 2 real servers. Port \"0\" is required if multiple ports are used." + +#: ../../configuration/firewall/index.rst:36 +msgid "In this example image, a simplifed traffic flow is shown to help provide context to the terms of `forward`, `input`, and `output` for the new firewall CLI format." +msgstr "In this example image, a simplifed traffic flow is shown to help provide context to the terms of `forward`, `input`, and `output` for the new firewall CLI format." + +#: ../../configuration/interfaces/openvpn.rst:334 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:30 +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 "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." + +#: ../../configuration/service/dns.rst:152 +msgid "In this scenario:" +msgstr "In this scenario:" + +#: ../../configuration/service/webproxy.rst:95 +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 "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." + +#: ../../configuration/service/snmp.rst:31 +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 "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." + +#: ../../configuration/firewall/zone.rst:13 +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 "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." + +#: ../../configuration/firewall/zone.rst:24 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:201 +msgid "Inbound connections to a WAN interface can be improperly handled when the reply is sent back to the client." +msgstr "Inbound connections to a WAN interface can be improperly handled when the reply is sent back to the client." + +#: ../../configuration/interfaces/bonding.rst:83 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:272 +msgid "Increase Maximum MPDU length to 7991 or 11454 octets (default 3895 octets)" +msgstr "Increase Maximum MPDU length to 7991 or 11454 octets (default 3895 octets)" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:68 +msgid "Indication" +msgstr "Indication" + +#: ../../configuration/service/dhcp-server.rst:84 +msgid "Individual Client Subnet" +msgstr "Individual Client Subnet" + +#: ../../configuration/service/dhcp-server.rst:54 +msgid "Inform client that the DNS server can be found at `<address>`." +msgstr "Inform client that the DNS server can be found at `<address>`." + +#: ../../configuration/service/lldp.rst:20 +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 "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:" + +#: ../../configuration/system/syslog.rst:189 +msgid "Informational" +msgstr "Informational" + +#: ../../configuration/system/syslog.rst:189 +msgid "Informational messages" +msgstr "Informational messages" + +#: ../../configuration/nat/nat66.rst:100 +msgid "Input from `eth0` network interface" +msgstr "Input from `eth0` network interface" + +#: ../../configuration/vpn/pptp.rst:32 +msgid "Install the client software via apt and execute pptpsetup to generate the configuration." +msgstr "Install the client software via apt and execute pptpsetup to generate the configuration." + +#: ../../_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 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:15 +#: ../../_include/interface-ipv6.txt:71 +#: ../../configuration/interfaces/pppoe.rst:205 +#: ../../configuration/interfaces/pppoe.rst:251 +#: ../../_include/interface-ip.txt:15 +#: ../../_include/interface-ipv6.txt:71 +#: ../../_include/interface-ip.txt:15 +#: ../../_include/interface-ipv6.txt:71 +#: ../../configuration/interfaces/sstp-client.rst:90 +#: ../../_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 +#: ../../_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 +#: ../../_include/interface-ip.txt:15 +#: ../../_include/interface-ipv6.txt:71 +#: ../../_include/interface-ip.txt:15 +#: ../../_include/interface-ipv6.txt:71 +msgid "Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to automatically set the proper value." +msgstr "Instead of a numerical MSS value `clamp-mss-to-pmtu` can be used to automatically set the proper value." + +#: ../../configuration/vpn/openconnect.rst:61 +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 "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:" + +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +#: ../../_include/interface-dhcp-options.txt:19 +msgid "Instead of sending the real system hostname to the DHCP server, overwrite the host-name with this given-value." +msgstr "Instead of sending the real system hostname to the DHCP server, overwrite the host-name with this given-value." + +#: ../../configuration/service/snmp.rst:137 +msgid "Integrity – Message integrity to ensure that a packet has not been tampered while in transit including an optional packet replay protection mechanism." +msgstr "Integrity – Message integrity to ensure that a packet has not been tampered while in transit including an optional packet replay protection mechanism." + +#: ../../configuration/interfaces/wireless.rst:600 +msgid "Intel AX200" +msgstr "Intel AX200" + +#: ../../configuration/system/acceleration.rst:12 +msgid "Intel® QAT" +msgstr "Intel® QAT" + +#: ../../configuration/interfaces/virtual-ethernet.rst:94 +msgid "Interconnect the global VRF with vrf \"red\" using the veth10 <-> veth 11 pair" +msgstr "Interconnect the global VRF with vrf \"red\" using the veth10 <-> veth 11 pair" + +#: ../../configuration/protocols/isis.rst:146 +#: ../../configuration/protocols/ospf.rst:356 +#: ../../configuration/protocols/ospf.rst:1139 +msgid "Interface Configuration" +msgstr "Interface Configuration" + +#: ../../configuration/firewall/general.rst:239 +msgid "Interface Groups" +msgstr "Interface Groups" + +#: ../../configuration/protocols/static.rst:64 +msgid "Interface Routes" +msgstr "Interface Routes" + +#: ../../configuration/protocols/igmp.rst:235 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:126 +msgid "Interface configuration" +msgstr "Interface configuration" + +#: ../../configuration/service/dhcp-relay.rst:36 +msgid "Interface for DHCP Relay Agent to forward requests out." +msgstr "Interface for DHCP Relay Agent to forward requests out." + +#: ../../configuration/service/dhcp-relay.rst:32 +msgid "Interface for DHCP Relay Agent to listen for requests." +msgstr "Interface for DHCP Relay Agent to listen for requests." + +#: ../../configuration/service/conntrack-sync.rst:71 +msgid "Interface to use for syncing conntrack entries." +msgstr "Interface to use for syncing conntrack entries." + +#: ../../configuration/interfaces/vxlan.rst:93 +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 "Interface used for VXLAN underlay. This is mandatory when using VXLAN via a multicast network. VXLAN traffic will always enter and exit this interface." + +#: ../../configuration/loadbalancing/wan.rst:62 +msgid "Interface weight" +msgstr "Interface weight" + +#: ../../configuration/interfaces/index.rst:3 +#: ../../configuration/vrf/index.rst:71 +msgid "Interfaces" +msgstr "Interfaces" + +#: ../../configuration/loadbalancing/wan.rst:38 +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 "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." + +#: ../../configuration/protocols/babel.rst:63 +#: ../../configuration/protocols/rip.rst:166 +msgid "Interfaces Configuration" +msgstr "Interfaces Configuration" + +#: ../../configuration/service/dhcp-relay.rst:23 +msgid "Interfaces that participate in the DHCP relay process. If this command is used, at least two entries of it are required: one for the interface that captures the dhcp-requests, and one for the interface to forward such requests. A warning message will be shown if this command is used, since new implementations should use ``listen-interface`` and ``upstream-interface``." +msgstr "Interfaces that participate in the DHCP relay process. If this command is used, at least two entries of it are required: one for the interface that captures the dhcp-requests, and one for the interface to forward such requests. A warning message will be shown if this command is used, since new implementations should use ``listen-interface`` and ``upstream-interface``." + +#: ../../configuration/service/dns.rst:26 +msgid "Interfaces whose DHCP client nameservers to forward requests to." +msgstr "Interfaces whose DHCP client nameservers to forward requests to." + +#: ../../configuration/system/flow-accounting.rst:70 +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 "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:" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:6 +msgid "Internet Key Exchange version 2 (IKEv2) is a tunneling protocol, based on IPsec, that establishes a secure VPN communication between VPN devices, and defines negotiation and authentication processes for IPsec security associations (SAs). It is often known as IKEv2/IPSec or IPSec IKEv2 remote-access — or road-warriors as others call it." +msgstr "Internet Key Exchange version 2 (IKEv2) is a tunneling protocol, based on IPsec, that establishes a secure VPN communication between VPN devices, and defines negotiation and authentication processes for IPsec security associations (SAs). It is often known as IKEv2/IPSec or IPSec IKEv2 remote-access — or road-warriors as others call it." + +#: ../../configuration/trafficpolicy/index.rst:791 +msgid "Internetwork Control" +msgstr "Internetwork Control" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Interval" +msgstr "Interval" + +#: ../../configuration/protocols/bfd.rst:53 +msgid "Interval in milliseconds" +msgstr "Interval in milliseconds" + +#: ../../configuration/service/salt-minion.rst:37 +msgid "Interval in minutes between updates (default: 60)" +msgstr "Interval in minutes between updates (default: 60)" + +#: ../../configuration/protocols/bgp.rst:906 +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 "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`." + +#: ../../configuration/interfaces/openvpn.rst:22 +msgid "It's easy to setup and offers very flexible split tunneling" +msgstr "It's easy to setup and offers very flexible split tunneling" + +#: ../../configuration/interfaces/tunnel.rst:52 +msgid "It's not likely that anyone will need it any time soon, but it does exist." +msgstr "It's not likely that anyone will need it any time soon, but it does exist." + +#: ../../configuration/interfaces/openvpn.rst:28 +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 "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" + +#: ../../configuration/system/option.rst:111 +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 "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." + +#: ../../configuration/system/option.rst:102 +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 "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%." + +#: ../../configuration/interfaces/wireguard.rst:33 +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 "It generates the keypair, which includes the public and private parts. The key is not stored on the system - only a keypair is generated." + +#: ../../configuration/protocols/ospf.rst:532 +#: ../../configuration/protocols/ospf.rst:1244 +msgid "It helps to support as HELPER only for planned restarts." +msgstr "It helps to support as HELPER only for planned restarts." + +#: ../../configuration/firewall/zone.rst:87 +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 "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*" + +#: ../../configuration/vpn/openconnect.rst:93 +msgid "It is compatible with Cisco (R) AnyConnect (R) clients." +msgstr "It is compatible with Cisco (R) AnyConnect (R) clients." + +#: ../../configuration/service/dhcp-server.rst:660 +msgid "It is connected to ``eth1``" +msgstr "It is connected to ``eth1``" + +#: ../../configuration/system/login.rst:42 +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 "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``." + +#: ../../configuration/protocols/mpls.rst:59 +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 "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." + +#: ../../configuration/nat/nat44.rst:549 +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 "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." + +#: ../../configuration/vrf/index.rst:503 +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 "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." + +#: ../../configuration/vrf/index.rst:113 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:136 +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 "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" + +#: ../../configuration/system/login.rst:93 +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 "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." + +#: ../../configuration/vrf/index.rst:494 +msgid "It is possible to permit BGP install VPN prefixes without transport labels. This configuration will install VPN prefixes originated from an e-bgp session, and with the next-hop directly connected." +msgstr "It is possible to permit BGP install VPN prefixes without transport labels. This configuration will install VPN prefixes originated from an e-bgp session, and with the next-hop directly connected." + +#: ../../configuration/service/conntrack-sync.rst:30 +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 "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:" + +#: ../../configuration/vpn/dmvpn.rst:112 +msgid "It is very easy to misconfigure multicast repeating if you have multiple NHSes." +msgstr "It is very easy to misconfigure multicast repeating if you have multiple NHSes." + +#: ../../configuration/interfaces/openvpn.rst:18 +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 "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" + +#: ../../configuration/trafficpolicy/index.rst:454 +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 "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." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:30 +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 "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." + +#: ../../configuration/vrf/index.rst:220 +msgid "Join a given VRF. This will open a new subshell within the specified VRF." +msgstr "Join a given VRF. This will open a new subshell within the specified VRF." + +#: ../../configuration/policy/route-map.rst:33 +msgid "Jump to a different rule in this route-map on a match." +msgstr "Jump to a different rule in this route-map on a match." + +#: ../../configuration/interfaces/bonding.rst:352 +msgid "Juniper EX Switch" +msgstr "Juniper EX Switch" + +#: ../../configuration/system/syslog.rst:112 +msgid "Kernel messages" +msgstr "Kernel messages" + +#: ../../configuration/system/login.rst:40 +msgid "Key Based Authentication" +msgstr "Key Based Authentication" + +#: ../../configuration/pki/index.rst:30 +msgid "Key Generation" +msgstr "Key Generation" + +#: ../../configuration/interfaces/macsec.rst:72 +msgid "Key Management" +msgstr "Key Management" + +#: ../../configuration/vpn/site2site_ipsec.rst:353 +msgid "Key Parameters:" +msgstr "Key Parameters:" + +#: ../../configuration/firewall/zone.rst:31 +msgid "Key Points:" +msgstr "Key Points:" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:12 +msgid "Key exchange and payload encryption is done using IKE and ESP proposals as known from IKEv1 but the connections are faster to establish, more reliable, and also support roaming from IP to IP (called MOBIKE which makes sure your connection does not drop when changing networks from e.g. WIFI to LTE and back). Authentication can be achieved with X.509 certificates." +msgstr "Key exchange and payload encryption is done using IKE and ESP proposals as known from IKEv1 but the connections are faster to establish, more reliable, and also support roaming from IP to IP (called MOBIKE which makes sure your connection does not drop when changing networks from e.g. WIFI to LTE and back). Authentication can be achieved with X.509 certificates." + +#: ../../configuration/pki/index.rst:167 +msgid "Key usage (CLI)" +msgstr "Key usage (CLI)" + +#: ../../configuration/system/option.rst:58 +msgid "Keyboard Layout" +msgstr "Keyboard Layout" + +#: ../../configuration/interfaces/wireguard.rst:23 +msgid "Keypairs" +msgstr "Keypairs" + +#: ../../configuration/system/syslog.rst:107 +#: ../../configuration/system/syslog.rst:167 +msgid "Keyword" +msgstr "Keyword" + +#: ../../configuration/vpn/l2tp.rst:4 +msgid "L2TP" +msgstr "L2TP" + +#: ../../configuration/vpn/l2tp.rst:10 +msgid "L2TP over IPsec" +msgstr "L2TP over IPsec" + +#: ../../configuration/interfaces/l2tpv3.rst:9 +msgid "L2TPv3" +msgstr "L2TPv3" + +#: ../../configuration/interfaces/l2tpv3.rst:176 +msgid "L2TPv3:" +msgstr "L2TPv3:" + +#: ../../configuration/interfaces/l2tpv3.rst:16 +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 "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." + +#: ../../configuration/interfaces/l2tpv3.rst:27 +msgid "L2TPv3 is described in :rfc:`3921`." +msgstr "L2TPv3 is described in :rfc:`3921`." + +#: ../../configuration/interfaces/l2tpv3.rst:27 +msgid "L2TPv3 is described in :rfc:`3931`." +msgstr "L2TPv3 is described in :rfc:`3931`." + +#: ../../configuration/interfaces/l2tpv3.rst:41 +msgid "L2TPv3 options" +msgstr "L2TPv3 options" + +#: ../../configuration/vrf/index.rst:397 +msgid "L3VPN VRFs" +msgstr "L3VPN VRFs" + +#: ../../configuration/interfaces/openvpn.rst:443 +#: ../../configuration/service/webproxy.rst:203 +msgid "LDAP" +msgstr "LDAP" + +#: ../../configuration/service/webproxy.rst:308 +msgid "LDAP protocol version. Defaults to 3 if not specified." +msgstr "LDAP protocol version. Defaults to 3 if not specified." + +#: ../../configuration/service/webproxy.rst:224 +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 "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." + +#: ../../configuration/service/lldp.rst:5 +msgid "LLDP" +msgstr "LLDP" + +#: ../../configuration/service/lldp.rst:14 +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 "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)`." + +#: ../../configuration/vpn/l2tp.rst:89 +msgid "LNS (L2TP Network Server)" +msgstr "LNS (L2TP Network Server)" + +#: ../../configuration/vpn/l2tp.rst:91 +msgid "LNS are often used to connect to a LAC (L2TP Access Concentrator)." +msgstr "LNS are often used to connect to a LAC (L2TP Access Concentrator)." + +#: ../../configuration/protocols/mpls.rst:40 +msgid "Label Distribution Protocol" +msgstr "Label Distribution Protocol" + +#: ../../configuration/interfaces/l2tpv3.rst:11 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:663 +msgid "Lease time will be left at the default value which is 24 hours" +msgstr "Lease time will be left at the default value which is 24 hours" + +#: ../../configuration/service/dhcp-server.rst:369 +msgid "Lease timeout in seconds (default: 86400)" +msgstr "Lease timeout in seconds (default: 86400)" + +#: ../../configuration/firewall/index.rst:47 +msgid "Legacy Firewall" +msgstr "Legacy Firewall" + +#: ../../configuration/interfaces/vxlan.rst:112 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:19 +msgid "Let's assume we have two DHCP WAN interfaces and one LAN (eth2):" +msgstr "Let's assume we have two DHCP WAN interfaces and one LAN (eth2):" + +#: ../../configuration/system/acceleration.rst:60 +msgid "Let's build a simple VPN between 2 Intel® QAT ready devices." +msgstr "Let's build a simple VPN between 2 Intel® QAT ready devices." + +#: ../../configuration/loadbalancing/wan.rst:64 +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 "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." + +#: ../../configuration/service/snmp.rst:147 +msgid "Let SNMP daemon listen only on IP address 192.0.2.1" +msgstr "Let SNMP daemon listen only on IP address 192.0.2.1" + +#: ../../configuration/interfaces/bonding.rst:402 +msgid "Lets assume the following topology:" +msgstr "Lets assume the following topology:" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:190 +msgid "Level 4 balancing" +msgstr "Level 4 balancing" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Lifetime associated with the default router in units of seconds" +msgstr "Lifetime associated with the default router in units of seconds" + +#: ../../configuration/service/https.rst:72 +msgid "Lifetime in days; default is 365" +msgstr "Lifetime in days; default is 365" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Lifetime is decremented by the number of seconds since the last RA - use in conjunction with a DHCPv6-PD prefix" +msgstr "Lifetime is decremented by the number of seconds since the last RA - use in conjunction with a DHCPv6-PD prefix" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:162 +msgid "Limit allowed cipher algorithms used during SSL/TLS handshake" +msgstr "Limit allowed cipher algorithms used during SSL/TLS handshake" + +#: ../../configuration/system/login.rst:112 +msgid "Limit logins to `<limit>` per every ``rate-time`` seconds. Rate limit must be between 1 and 10 attempts." +msgstr "Limit logins to `<limit>` per every ``rate-time`` seconds. Rate limit must be between 1 and 10 attempts." + +#: ../../configuration/system/login.rst:118 +msgid "Limit logins to ``rate-limit`` attemps per every `<seconds>`. Rate time must be between 15 and 600 seconds." +msgstr "Limit logins to ``rate-limit`` attemps per every `<seconds>`. Rate time must be between 15 and 600 seconds." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:157 +msgid "Limit maximum number of connections" +msgstr "Limit maximum number of connections" + +#: ../../configuration/trafficpolicy/index.rst:544 +msgid "Limiter" +msgstr "Limiter" + +#: ../../configuration/trafficpolicy/index.rst:549 +msgid "Limiter is one of those policies that uses classes_ (Ingress qdisc is actually a classless policy but filters do work in it)." +msgstr "Limiter is one of those policies that uses classes_ (Ingress qdisc is actually a classless policy but filters do work in it)." + +#: ../../configuration/system/login.rst:379 +msgid "Limits" +msgstr "Limits" + +#: ../../configuration/system/syslog.rst:124 +msgid "Line printer subsystem" +msgstr "Line printer subsystem" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Link MTU value placed in RAs, exluded in RAs if unset" +msgstr "Link MTU value placed in RAs, exluded in RAs if unset" + +#: ../../configuration/service/lldp.rst:33 +msgid "Link aggregation" +msgstr "Link aggregation" + +#: ../../configuration/nat/nat44.rst:372 +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 "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)." + +#: ../../configuration/interfaces/macsec.rst:128 +msgid "List all MACsec interfaces." +msgstr "List all MACsec interfaces." + +#: ../../configuration/system/syslog.rst:98 +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 "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." + +#: ../../configuration/service/ntp.rst:78 +msgid "List of networks or client addresses permitted to contact this NTP server." +msgstr "List of networks or client addresses permitted to contact this NTP server." + +#: ../../configuration/service/ssh.rst:73 +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 "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``" + +#: ../../configuration/service/ssh.rst:96 +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 "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``." + +#: ../../configuration/service/ssh.rst:53 +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 "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``" + +#: ../../configuration/policy/route-map.rst:360 +msgid "List of well-known communities" +msgstr "List of well-known communities" + +#: ../../configuration/service/dhcp-relay.rst:87 +msgid "Listen for DHCP requests on interface ``eth1``." +msgstr "Listen for DHCP requests on interface ``eth1``." + +#: ../../configuration/vrf/index.rst:118 +msgid "Lists VRFs that have been created" +msgstr "Lists VRFs that have been created" + +#: ../../configuration/loadbalancing/index.rst:5 +msgid "Load-balancing" +msgstr "Load-balancing" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:100 +msgid "Load-balancing algorithms to be used for distributind requests among the vailable servers" +msgstr "Load-balancing algorithms to be used for distributind requests among the vailable servers" + +#: ../../configuration/highavailability/index.rst:347 +msgid "Load-balancing schedule algorithm:" +msgstr "Load-balancing schedule algorithm:" + +#: ../../configuration/nat/nat44.rst:632 +msgid "Load Balance" +msgstr "Load Balance" + +#: ../../configuration/service/pppoe-server.rst:256 +msgid "Load Balancing" +msgstr "Load Balancing" + +#: ../../configuration/system/login.rst:420 +msgid "Load the container image in op-mode." +msgstr "Load the container image in op-mode." + +#: ../../configuration/system/login.rst:17 +msgid "Local" +msgstr "Local" + +#: ../../configuration/interfaces/openvpn.rst:134 +#: ../../configuration/interfaces/openvpn.rst:241 +msgid "Local Configuration:" +msgstr "Local Configuration:" + +#: ../../configuration/interfaces/openvpn.rst:96 +msgid "Local Configuration - Annotated:" +msgstr "Local Configuration - Annotated:" + +#: ../../configuration/service/dhcp-server.rst:178 +msgid "Local IP `<address>` used when communicating to the failover peer." +msgstr "Local IP `<address>` used when communicating to the failover peer." + +#: ../../configuration/service/monitoring.rst:59 +msgid "Local IP addresses to listen on" +msgstr "Local IP addresses to listen on" + +#: ../../configuration/service/conntrack-sync.rst:79 +msgid "Local IPv4 addresses for service to listen on." +msgstr "Local IPv4 addresses for service to listen on." + +#: ../../configuration/policy/local-route.rst:12 +msgid "Local Route IPv4" +msgstr "Local Route IPv4" + +#: ../../configuration/policy/local-route.rst:31 +msgid "Local Route IPv6" +msgstr "Local Route IPv6" + +#: ../../configuration/policy/local-route.rst:3 +msgid "Local Route Policy" +msgstr "Local Route Policy" + +#: ../../configuration/system/syslog.rst:83 +msgid "Local User Account" +msgstr "Local User Account" + +#: ../../configuration/protocols/rpki.rst:141 +msgid "Local path that includes the known hosts file." +msgstr "Local path that includes the known hosts file." + +#: ../../configuration/protocols/rpki.rst:145 +msgid "Local path that includes the private key file of the router." +msgstr "Local path that includes the private key file of the router." + +#: ../../configuration/protocols/rpki.rst:149 +msgid "Local path that includes the public key file of the router." +msgstr "Local path that includes the public key file of the router." + +#: ../../configuration/policy/examples.rst:153 +msgid "Local route" +msgstr "Local route" + +#: ../../configuration/service/console-server.rst:99 +msgid "Locally connect to serial port identified by `<device>`." +msgstr "Locally connect to serial port identified by `<device>`." + +#: ../../configuration/policy/route-map.rst:273 +msgid "Locally significant administrative distance." +msgstr "Locally significant administrative distance." + +#: ../../configuration/system/syslog.rst:140 +msgid "Log alert" +msgstr "Log alert" + +#: ../../configuration/system/syslog.rst:138 +msgid "Log audit" +msgstr "Log audit" + +#: ../../configuration/system/syslog.rst:169 +msgid "Log everything" +msgstr "Log everything" + +#: ../../configuration/system/syslog.rst:212 +msgid "Log messages from a specified image can be displayed on the console. Details of allowed parameters:" +msgstr "Log messages from a specified image can be displayed on the console. Details of allowed parameters:" + +#: ../../configuration/system/syslog.rst:25 +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 "Log syslog messages to ``/dev/console``, for an explanation on :ref:`syslog_facilities` keywords and :ref:`syslog_severity_level` keywords see tables below." + +#: ../../configuration/system/syslog.rst:36 +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 "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." + +#: ../../configuration/system/syslog.rst:64 +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 "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." + +#: ../../configuration/system/conntrack.rst:187 +msgid "Log the connection tracking events per protocol." +msgstr "Log the connection tracking events per protocol." + +#: ../../configuration/system/syslog.rst:14 +msgid "Logging" +msgstr "Logging" + +#: ../../configuration/firewall/general.rst:412 +msgid "Logging can be enable for every single firewall rule. If enabled, other log options can be defined." +msgstr "Logging can be enable for every single firewall rule. If enabled, other log options can be defined." + +#: ../../configuration/system/syslog.rst:56 +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 "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." + +#: ../../configuration/system/login.rst:7 +msgid "Login/User Management" +msgstr "Login/User Management" + +#: ../../configuration/system/login.rst:361 +msgid "Login Banner" +msgstr "Login Banner" + +#: ../../configuration/system/login.rst:381 +msgid "Login limits" +msgstr "Login limits" + +#: ../../configuration/interfaces/loopback.rst:7 +msgid "Loopback" +msgstr "Loopback" + +#: ../../configuration/interfaces/pseudo-ethernet.rst:34 +msgid "Loopbacks occurs at the IP level the same way as for other interfaces, ethernet frames are not forwarded between Pseudo-Ethernet interfaces." +msgstr "Loopbacks occurs at the IP level the same way as for other interfaces, ethernet frames are not forwarded between Pseudo-Ethernet interfaces." + +#: ../../configuration/trafficpolicy/index.rst:269 +#: ../../configuration/trafficpolicy/index.rst:275 +#: ../../configuration/trafficpolicy/index.rst:281 +#: ../../configuration/trafficpolicy/index.rst:287 +msgid "Low" +msgstr "Low" + +#: ../../configuration/service/lldp.rst:31 +msgid "MAC/PHY information" +msgstr "MAC/PHY information" + +#: ../../configuration/interfaces/pseudo-ethernet.rst:7 +msgid "MACVLAN - Pseudo Ethernet" +msgstr "MACVLAN - Pseudo Ethernet" + +#: ../../configuration/firewall/general.rst:282 +#: ../../configuration/firewall/general-legacy.rst:240 +msgid "MAC Groups" +msgstr "MAC Groups" + +#: ../../configuration/interfaces/bridge.rst:70 +msgid "MAC address aging `<time`> in seconds (default: 300)." +msgstr "MAC address aging `<time`> in seconds (default: 300)." + +#: ../../configuration/interfaces/macsec.rst:7 +msgid "MACsec" +msgstr "MACsec" + +#: ../../configuration/interfaces/macsec.rst:9 +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 "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." + +#: ../../configuration/interfaces/macsec.rst:39 +msgid "MACsec only provides authentication by default, encryption is optional. This command will enable encryption for all outgoing packets." +msgstr "MACsec only provides authentication by default, encryption is optional. This command will enable encryption for all outgoing packets." + +#: ../../configuration/interfaces/macsec.rst:30 +msgid "MACsec options" +msgstr "MACsec options" + +#: ../../configuration/service/lldp.rst:32 +msgid "MDI power" +msgstr "MDI power" + +#: ../../configuration/system/login.rst:91 +msgid "MFA/2FA authentication using OTP (one time passwords)" +msgstr "MFA/2FA authentication using OTP (one time passwords)" + +#: ../../configuration/protocols/mpls.rst:5 +msgid "MPLS" +msgstr "MPLS" + +#: ../../configuration/protocols/mpls.rst:30 +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 "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)." + +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../configuration/interfaces/pppoe.rst:202 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../configuration/interfaces/sstp-client.rst:87 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +#: ../../_include/interface-ip.txt:12 +msgid "MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes on a 1492 byte MTU." +msgstr "MSS value = MTU - 20 (IP header) - 20 (TCP header), resulting in 1452 bytes on a 1492 byte MTU." + +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../configuration/interfaces/pppoe.rst:248 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +#: ../../_include/interface-ipv6.txt:68 +msgid "MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 bytes on a 1492 byte MTU." +msgstr "MSS value = MTU - 40 (IPv6 header) - 20 (TCP header), resulting in 1432 bytes on a 1492 byte MTU." + +#: ../../configuration/service/router-advert.rst:1 +msgid "MTU" +msgstr "MTU" + +#: ../../configuration/system/syslog.rst:116 +msgid "Mail system" +msgstr "Mail system" + +#: ../../configuration/firewall/general.rst:20 +msgid "Main structure is shown next:" +msgstr "Main structure is shown next:" + +#: ../../configuration/service/pppoe-server.rst:308 +msgid "Maintenance mode" +msgstr "Maintenance mode" + +#: ../../configuration/service/conntrack-sync.rst:107 +msgid "Make sure conntrack is enabled by running and show connection tracking table." +msgstr "Make sure conntrack is enabled by running and show connection tracking table." + +#: ../../configuration/service/snmp.rst:38 +msgid "Managed devices" +msgstr "Managed devices" + +#: ../../configuration/interfaces/wireless.rst:85 +msgid "Management Frame Protection (MFP) according to IEEE 802.11w" +msgstr "Management Frame Protection (MFP) according to IEEE 802.11w" + +#: ../../configuration/protocols/isis.rst:31 +msgid "Mandatory Settings" +msgstr "Mandatory Settings" + +#: ../../configuration/protocols/ospf.rst:537 +msgid "Manual Neighbor Configuration" +msgstr "Manual Neighbor Configuration" + +#: ../../configuration/interfaces/vxlan.rst:150 +msgid "Maps the VNI to the specified VLAN id. The VLAN can then be consumed by a bridge." +msgstr "Maps the VNI to the specified VLAN id. The VLAN can then be consumed by a bridge." + +#: ../../configuration/vpn/sstp.rst:212 +msgid "Mark RADIUS server as offline for this given `<time>` in seconds." +msgstr "Mark RADIUS server as offline for this given `<time>` in seconds." + +#: ../../configuration/pki/index.rst:206 +msgid "Mark the CAs private key as password protected. User is asked for the password when the key is referenced." +msgstr "Mark the CAs private key as password protected. User is asked for the password when the key is referenced." + +#: ../../configuration/pki/index.rst:244 +msgid "Mark the private key as password protected. User is asked for the password when the key is referenced." +msgstr "Mark the private key as password protected. User is asked for the password when the key is referenced." + +#: ../../configuration/policy/route-map.rst:141 +msgid "Match BGP large communities." +msgstr "Match BGP large communities." + +#: ../../configuration/firewall/general-legacy.rst:474 +msgid "Match IP addresses based on its geolocation. More info: `geoip matching <https://wiki.nftables.org/wiki-nftables/index.php/GeoIP_matching>`_." +msgstr "Match IP addresses based on its geolocation. More info: `geoip matching <https://wiki.nftables.org/wiki-nftables/index.php/GeoIP_matching>`_." + +#: ../../configuration/firewall/general.rst:710 +msgid "Match IP addresses based on its geolocation. More info: `geoip matching <https://wiki.nftables.org/wiki-nftables/index.php/GeoIP_matching>`_. Use inverse-match to match anything except the given country-codes." +msgstr "Match IP addresses based on its geolocation. More info: `geoip matching <https://wiki.nftables.org/wiki-nftables/index.php/GeoIP_matching>`_. Use inverse-match to match anything except the given country-codes." + +#: ../../configuration/policy/route-map.rst:180 +msgid "Match RPKI validation result." +msgstr "Match RPKI validation result." + +#: ../../configuration/policy/route.rst:166 +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 "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." + +#: ../../configuration/firewall/general.rst:1091 +#: ../../configuration/firewall/general-legacy.rst:671 +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 "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." + +#: ../../configuration/firewall/general.rst:1158 +#: ../../configuration/firewall/general-legacy.rst:709 +msgid "Match against the state of a packet." +msgstr "Match against the state of a packet." + +#: ../../configuration/firewall/general.rst:924 +#: ../../configuration/firewall/general-legacy.rst:590 +msgid "Match based on dscp value." +msgstr "Match based on dscp value." + +#: ../../configuration/policy/route.rst:115 +msgid "Match based on dscp value criteria. Multiple values from 0 to 63 and ranges are supported." +msgstr "Match based on dscp value criteria. Multiple values from 0 to 63 and ranges are supported." + +#: ../../configuration/firewall/general.rst:937 +#: ../../configuration/firewall/general-legacy.rst:597 +msgid "Match based on fragment criteria." +msgstr "Match based on fragment criteria." + +#: ../../configuration/firewall/general.rst:956 +#: ../../configuration/firewall/general-legacy.rst:604 +#: ../../configuration/policy/route.rst:131 +msgid "Match based on icmp|icmpv6 code and type." +msgstr "Match based on icmp|icmpv6 code and type." + +#: ../../configuration/firewall/general.rst:975 +#: ../../configuration/firewall/general-legacy.rst:610 +msgid "Match based on icmp|icmpv6 type-name criteria. Use tab for information about what **type-name** criteria are supported." +msgstr "Match based on icmp|icmpv6 type-name criteria. Use tab for information about what **type-name** criteria are supported." + +#: ../../configuration/policy/route.rst:136 +msgid "Match based on icmp|icmpv6 type-name criteria. Use tab for information about what type-name criteria are supported." +msgstr "Match based on icmp|icmpv6 type-name criteria. Use tab for information about what type-name criteria are supported." + +#: ../../configuration/firewall/general-legacy.rst:622 +msgid "Match based on inbound/outbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" +msgstr "Match based on inbound/outbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" + +#: ../../configuration/firewall/general.rst:987 +msgid "Match based on inbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" +msgstr "Match based on inbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" + +#: ../../configuration/firewall/general.rst:1013 +#: ../../configuration/firewall/general-legacy.rst:630 +msgid "Match based on ipsec criteria." +msgstr "Match based on ipsec criteria." + +#: ../../configuration/firewall/general.rst:999 +msgid "Match based on outbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" +msgstr "Match based on outbound interface. Wilcard ``*`` can be used. For example: ``eth2*``" + +#: ../../configuration/firewall/general.rst:1064 +#: ../../configuration/firewall/general-legacy.rst:656 +#: ../../configuration/policy/route.rst:176 +msgid "Match based on packet length criteria. Multiple values from 1 to 65535 and ranges are supported." +msgstr "Match based on packet length criteria. Multiple values from 1 to 65535 and ranges are supported." + +#: ../../configuration/firewall/general.rst:1078 +#: ../../configuration/firewall/general-legacy.rst:664 +#: ../../configuration/policy/route.rst:184 +msgid "Match based on packet type criteria." +msgstr "Match based on packet type criteria." + +#: ../../configuration/firewall/general.rst:1039 +#: ../../configuration/firewall/general-legacy.rst:644 +msgid "Match based on the maximum average rate, specified as **integer/unit**. For example **5/minutes**" +msgstr "Match based on the maximum average rate, specified as **integer/unit**. For example **5/minutes**" + +#: ../../configuration/firewall/general.rst:1026 +#: ../../configuration/firewall/general-legacy.rst:637 +msgid "Match based on the maximum number of packets to allow in excess of rate." +msgstr "Match based on the maximum number of packets to allow in excess of rate." + +#: ../../configuration/firewall/general.rst:1124 +#: ../../configuration/firewall/general-legacy.rst:689 +msgid "Match bases on recently seen sources." +msgstr "Match bases on recently seen sources." + +#: ../../configuration/firewall/general.rst:562 +#: ../../configuration/firewall/general-legacy.rst:394 +msgid "Match criteria based on connection mark." +msgstr "Match criteria based on connection mark." + +#: ../../configuration/firewall/general.rst:549 +#: ../../configuration/firewall/general-legacy.rst:387 +msgid "Match criteria based on nat connection status." +msgstr "Match criteria based on nat connection status." + +#: ../../configuration/firewall/general.rst:586 +msgid "Match criteria based on source and/or destination address. This is similar to the network groups part, but here you are able to negate the matching addresses." +msgstr "Match criteria based on source and/or destination address. This is similar to the network groups part, but here you are able to negate the matching addresses." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:58 +msgid "Match domain name" +msgstr "Match domain name" + +#: ../../configuration/firewall/general.rst:1234 +#: ../../configuration/firewall/general-legacy.rst:732 +#: ../../configuration/policy/route.rst:234 +msgid "Match hop-limit parameter, where 'eq' stands for 'equal'; 'gt' stands for 'greater than', and 'lt' stands for 'less than'." +msgstr "Match hop-limit parameter, where 'eq' stands for 'equal'; 'gt' stands for 'greater than', and 'lt' stands for 'less than'." + +#: ../../configuration/policy/route-map.rst:146 +msgid "Match local preference." +msgstr "Match local preference." + +#: ../../configuration/policy/route-map.rst:150 +msgid "Match route metric." +msgstr "Match route metric." + +#: ../../configuration/firewall/general.rst:1222 +#: ../../configuration/firewall/general-legacy.rst:726 +#: ../../configuration/policy/route.rst:229 +msgid "Match time to live parameter, where 'eq' stands for 'equal'; 'gt' stands for 'greater than', and 'lt' stands for 'less than'." +msgstr "Match time to live parameter, where 'eq' stands for 'equal'; 'gt' stands for 'greater than', and 'lt' stands for 'less than'." + +#: ../../configuration/firewall/general.rst:1259 +#: ../../configuration/firewall/general-legacy.rst:742 +msgid "Match when 'count' amount of connections are seen within 'time'. These matching criteria can be used to block brute-force attempts." +msgstr "Match when 'count' amount of connections are seen within 'time'. These matching criteria can be used to block brute-force attempts." + +#: ../../configuration/firewall/general.rst:534 +#: ../../configuration/firewall/general-legacy.rst:378 +#: ../../configuration/policy/route.rst:38 +msgid "Matching criteria" +msgstr "Matching criteria" + +#: ../../configuration/trafficpolicy/index.rst:119 +msgid "Matching traffic" +msgstr "Matching traffic" + +#: ../../configuration/interfaces/wireless.rst:199 +msgid "Maximum A-MSDU length 3839 (default) or 7935 octets" +msgstr "Maximum A-MSDU length 3839 (default) or 7935 octets" + +#: ../../configuration/service/dns.rst:108 +msgid "Maximum number of DNS cache entries. 1 million per CPU core will generally suffice for most installations." +msgstr "Maximum number of DNS cache entries. 1 million per CPU core will generally suffice for most installations." + +#: ../../configuration/vpn/sstp.rst:148 +msgid "Maximum number of IPv4 nameservers" +msgstr "Maximum number of IPv4 nameservers" + +#: ../../configuration/service/webproxy.rst:160 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:77 +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 "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." + +#: ../../configuration/vpn/sstp.rst:239 +msgid "Maximum number of tries to send Access-Request/Accounting-Request queries" +msgstr "Maximum number of tries to send Access-Request/Accounting-Request queries" + +#: ../../configuration/trafficpolicy/index.rst:271 +#: ../../configuration/trafficpolicy/index.rst:277 +#: ../../configuration/trafficpolicy/index.rst:283 +#: ../../configuration/trafficpolicy/index.rst:289 +msgid "Medium" +msgstr "Medium" + +#: ../../configuration/interfaces/bonding.rst:27 +#: ../../configuration/interfaces/bridge.rst:31 +msgid "Member Interfaces" +msgstr "Member Interfaces" + +#: ../../configuration/interfaces/bridge.rst:196 +msgid "Member interfaces `eth1` and VLAN 10 on interface `eth2`" +msgstr "Member interfaces `eth1` and VLAN 10 on interface `eth2`" + +#: ../../configuration/system/syslog.rst:122 +msgid "Messages generated internally by syslogd" +msgstr "Messages generated internally by syslogd" + +#: ../../configuration/service/monitoring.rst:63 +msgid "Metris version, the default is ``2``" +msgstr "Metris version, the default is ``2``" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Min and max intervals between unsolicited multicast RAs" +msgstr "Min and max intervals between unsolicited multicast RAs" + +#: ../../configuration/interfaces/wireless.rst:22 +msgid "Monitor, the system passively monitors any kind of wireless traffic" +msgstr "Monitor, the system passively monitors any kind of wireless traffic" + +#: ../../configuration/service/monitoring.rst:2 +msgid "Monitoring" +msgstr "Monitoring" + +#: ../../configuration/service/monitoring.rst:108 +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 "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." + +#: ../../configuration/interfaces/vti.rst:32 +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 "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" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:139 +msgid "Most operating systems include native client support for IPsec IKEv2 VPN connections, and others typically have an app or add-on package which adds the capability. This section covers IPsec IKEv2 client configuration for Windows 10." +msgstr "Most operating systems include native client support for IPsec IKEv2 VPN connections, and others typically have an app or add-on package which adds the capability. This section covers IPsec IKEv2 client configuration for Windows 10." + +#: ../../configuration/container/index.rst:85 +msgid "Mount a volume into the container" +msgstr "Mount a volume into the container" + +#: ../../configuration/service/dhcp-server.rst:268 +msgid "Multi" +msgstr "Multi" + +#: ../../configuration/interfaces/openvpn.rst:327 +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 "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." + +#: ../../configuration/nat/nat66.rst:42 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:392 +msgid "Multi: can be specified multiple times." +msgstr "Multi: can be specified multiple times." + +#: ../../configuration/interfaces/vxlan.rst:89 +#: ../../configuration/protocols/igmp.rst:7 +msgid "Multicast" +msgstr "Multicast" + +#: ../../configuration/interfaces/vxlan.rst:209 +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 "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." + +#: ../../configuration/service/mdns.rst:8 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:105 +msgid "Multicast VXLAN" +msgstr "Multicast VXLAN" + +#: ../../configuration/interfaces/vxlan.rst:99 +msgid "Multicast group address for VXLAN interface. VXLAN tunnels can be built either via Multicast or via Unicast." +msgstr "Multicast group address for VXLAN interface. VXLAN tunnels can be built either via Multicast or via Unicast." + +#: ../../configuration/service/conntrack-sync.rst:83 +msgid "Multicast group to use for syncing conntrack entries." +msgstr "Multicast group to use for syncing conntrack entries." + +#: ../../configuration/protocols/igmp.rst:26 +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 "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." + +#: ../../configuration/protocols/pim6.rst:18 +msgid "Multicast receivers will talk MLD to their local router, so, besides having PIMv6 configured in every router, MLD must also be configured in any router where there could be a multicast receiver locally connected." +msgstr "Multicast receivers will talk MLD to their local router, so, besides having PIMv6 configured in every router, MLD must also be configured in any router where there could be a multicast receiver locally connected." + +#: ../../configuration/service/dhcp-server.rst:59 +#: ../../configuration/service/dhcp-server.rst:106 +msgid "Multiple DNS servers can be defined." +msgstr "Multiple DNS servers can be defined." + +#: ../../configuration/protocols/rpki.rst:121 +msgid "Multiple RPKI caching instances can be supplied and they need a preference in which their result sets are used." +msgstr "Multiple RPKI caching instances can be supplied and they need a preference in which their result sets are used." + +#: ../../configuration/policy/examples.rst:90 +msgid "Multiple Uplinks" +msgstr "Multiple Uplinks" + +#: ../../configuration/interfaces/vxlan.rst:144 +msgid "Multiple VLAN to VNI mappings can be configured against the same SVD. This allows for a significant scaling of the number of VNIs since a separate VXLAN interface is no longer required for each VNI." +msgstr "Multiple VLAN to VNI mappings can be configured against the same SVD. This allows for a significant scaling of the number of VNIs since a separate VXLAN interface is no longer required for each VNI." + +#: ../../configuration/system/host-name.rst:68 +msgid "Multiple aliases can pe specified per host-name." +msgstr "Multiple aliases can pe specified per host-name." + +#: ../../configuration/policy/route.rst:101 +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 "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'" + +#: ../../configuration/system/conntrack.rst:122 +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 "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``" + +#: ../../configuration/service/dhcp-relay.rst:143 +msgid "Multiple interfaces may be specified." +msgstr "Multiple interfaces may be specified." + +#: ../../configuration/service/ntp.rst:80 +msgid "Multiple networks/client IP addresses can be configured." +msgstr "Multiple networks/client IP addresses can be configured." + +#: ../../configuration/system/login.rst:248 +#: ../../configuration/system/login.rst:317 +msgid "Multiple servers can be specified." +msgstr "Multiple servers can be specified." + +#: ../../configuration/service/dns.rst:361 +msgid "Multiple services can be used per interface. Just specify as many services per interface as you like!" +msgstr "Multiple services can be used per interface. Just specify as many services per interface as you like!" + +#: ../../configuration/firewall/general.rst:770 +#: ../../configuration/firewall/general-legacy.rst:515 +msgid "Multiple source ports can be specified as a comma-separated list. The whole list can also be \"negated\" using ``!``. For example:" +msgstr "Multiple source ports can be specified as a comma-separated list. The whole list can also be \"negated\" using ``!``. For example:" + +#: ../../configuration/interfaces/bonding.rst:268 +msgid "Multiple target IP addresses can be specified. At least one IP address must be given for ARP monitoring to function." +msgstr "Multiple target IP addresses can be specified. At least one IP address must be given for ARP monitoring to function." + +#: ../../configuration/service/console-server.rst:72 +#: ../../configuration/service/console-server.rst:109 +msgid "Multiple users can connect to the same serial device but only one is allowed to write to the console port." +msgstr "Multiple users can connect to the same serial device but only one is allowed to write to the console port." + +#: ../../configuration/protocols/bgp.rst:50 +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 "Multiprotocol extensions enable BGP to carry routing information for multiple network layer protocols. BGP supports an Address Family Identifier (AFI) for IPv4 and IPv6." + +#: ../../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 +msgid "N" +msgstr "N" + +#: ../../configuration/highavailability/index.rst:363 +#: ../../configuration/nat/index.rst:5 +msgid "NAT" +msgstr "NAT" + +#: ../../configuration/nat/nat44.rst:113 +msgid "NAT, Routing, Firewall Interaction" +msgstr "NAT, Routing, Firewall Interaction" + +#: ../../configuration/nat/nat44.rst:5 +msgid "NAT44" +msgstr "NAT44" + +#: ../../configuration/nat/nat66.rst:5 +msgid "NAT66(NPTv6)" +msgstr "NAT66(NPTv6)" + +#: ../../configuration/nat/nat44.rst:706 +msgid "NAT Configuration" +msgstr "NAT Configuration" + +#: ../../configuration/nat/nat44.rst:287 +msgid "NAT Load Balance" +msgstr "NAT Load Balance" + +#: ../../configuration/nat/nat44.rst:293 +msgid "NAT Load Balance uses an algorithm that generates a hash and based on it, then it applies corresponding translation. This hash can be generated randomly, or can use data from the ip header: source-address, destination-address, source-port and/or destination-port. By default, it will generate the hash randomly." +msgstr "NAT Load Balance uses an algorithm that generates a hash and based on it, then it applies corresponding translation. This hash can be generated randomly, or can use data from the ip header: source-address, destination-address, source-port and/or destination-port. By default, it will generate the hash randomly." + +#: ../../configuration/nat/nat44.rst:119 +msgid "NAT Ruleset" +msgstr "NAT Ruleset" + +#: ../../configuration/nat/nat44.rst:686 +msgid "NAT (specifically, Source NAT);" +msgstr "NAT (specifically, Source NAT);" + +#: ../../configuration/nat/nat44.rst:624 +msgid "NAT before VPN" +msgstr "NAT before VPN" + +#: ../../configuration/nat/nat44.rst:677 +#: ../../configuration/nat/nat44.rst:677 +msgid "NAT before VPN Topology" +msgstr "NAT before VPN Topology" + +#: ../../configuration/vpn/dmvpn.rst:17 +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 "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." + +#: ../../configuration/service/ntp.rst:5 +msgid "NTP" +msgstr "NTP" + +#: ../../configuration/service/ntp.rst:12 +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 "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." + +#: ../../configuration/service/ntp.rst:72 +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 "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." + +#: ../../configuration/system/syslog.rst:136 +msgid "NTP subsystem" +msgstr "NTP subsystem" + +#: ../../configuration/service/ntp.rst:26 +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 "NTP supplies a warning of any impending leap second adjustment, but no information about local time zones or daylight saving time is transmitted." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Name Server" +msgstr "Name Server" + +#: ../../configuration/service/dhcp-server.rst:389 +msgid "Name of static mapping" +msgstr "Name of static mapping" + +#: ../../configuration/service/monitoring.rst:31 +msgid "Name of the single table Only if set group-metrics single-table." +msgstr "Name of the single table Only if set group-metrics single-table." + +#: ../../configuration/service/dhcp-server.rst:329 +msgid "Name or IPv4 address of TFTP server" +msgstr "Name or IPv4 address of TFTP server" + +#: ../../configuration/service/dhcp-server.rst:314 +msgid "NetBIOS over TCP/IP name server" +msgstr "NetBIOS over TCP/IP name server" + +#: ../../configuration/system/flow-accounting.rst:92 +msgid "NetFlow" +msgstr "NetFlow" + +#: ../../configuration/system/flow-accounting.rst:20 +msgid "NetFlow / IPFIX" +msgstr "NetFlow / IPFIX" + +#: ../../configuration/system/flow-accounting.rst:115 +msgid "NetFlow engine-id which will appear in NetFlow data. The range is 0 to 255." +msgstr "NetFlow engine-id which will appear in NetFlow data. The range is 0 to 255." + +#: ../../configuration/system/flow-accounting.rst:21 +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 "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:" + +#: ../../configuration/system/flow-accounting.rst:38 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:166 +msgid "NetFlow v5 example:" +msgstr "NetFlow v5 example:" + +#: ../../configuration/firewall/index.rst:16 +msgid "Netfilter based" +msgstr "Netfilter based" + +#: ../../configuration/policy/prefix-list.rst:43 +#: ../../configuration/policy/prefix-list.rst:76 +msgid "Netmask greater than length." +msgstr "Netmask greater than length." + +#: ../../configuration/policy/prefix-list.rst:47 +#: ../../configuration/policy/prefix-list.rst:80 +msgid "Netmask less than length" +msgstr "Netmask less than length" + +#: ../../configuration/protocols/bgp.rst:500 +msgid "Network Advertisement Configuration" +msgstr "Network Advertisement Configuration" + +#: ../../configuration/trafficpolicy/index.rst:789 +msgid "Network Control" +msgstr "Network Control" + +#: ../../configuration/trafficpolicy/index.rst:619 +msgid "Network Emulator" +msgstr "Network Emulator" + +#: ../../configuration/firewall/general.rst:215 +#: ../../configuration/firewall/general-legacy.rst:191 +msgid "Network Groups" +msgstr "Network Groups" + +#: ../../configuration/interfaces/wireless.rst:350 +msgid "Network ID (SSID) ``Enterprise-TEST``" +msgstr "Network ID (SSID) ``Enterprise-TEST``" + +#: ../../configuration/interfaces/wireless.rst:550 +msgid "Network ID (SSID) ``TEST``" +msgstr "Network ID (SSID) ``TEST``" + +#: ../../configuration/protocols/igmp.rst:None +msgid "Network Topology Diagram" +msgstr "Network Topology Diagram" + +#: ../../configuration/service/snmp.rst:40 +msgid "Network management station (NMS) - software which runs on the manager" +msgstr "Network management station (NMS) - software which runs on the manager" + +#: ../../configuration/system/syslog.rst:126 +msgid "Network news subsystem" +msgstr "Network news subsystem" + +#: ../../configuration/service/monitoring.rst:47 +msgid "Networks allowed to query this server" +msgstr "Networks allowed to query this server" + +#: ../../configuration/service/snmp.rst:149 +msgid "New user will use SHA/AES for authentication and privacy" +msgstr "New user will use SHA/AES for authentication and privacy" + +#: ../../configuration/protocols/failover.rst:51 +msgid "Next-hop interface for the route" +msgstr "Next-hop interface for the route" + +#: ../../configuration/vpn/openconnect.rst:205 +msgid "Next it is necessary to configure 2FA for OpenConnect:" +msgstr "Next it is necessary to configure 2FA for OpenConnect:" + +#: ../../configuration/policy/route-map.rst:279 +msgid "Nexthop IP address." +msgstr "Nexthop IP address." + +#: ../../configuration/policy/route-map.rst:298 +msgid "Nexthop IPv6 address." +msgstr "Nexthop IPv6 address." + +#: ../../configuration/policy/route-map.rst:136 +msgid "Nexthop IPv6 address to match." +msgstr "Nexthop IPv6 address to match." + +#: ../../configuration/protocols/rpki.rst:59 +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 "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" + +#: ../../configuration/interfaces/pppoe.rst:315 +msgid "No VLAN tagging required by your ISP." +msgstr "No VLAN tagging required by your ISP." + +#: ../../configuration/protocols/bgp.rst:707 +msgid "No route is suppressed indefinitely. Maximum-suppress-time defines the maximum time a route can be suppressed before it is re-advertised." +msgstr "No route is suppressed indefinitely. Maximum-suppress-time defines the maximum time a route can be suppressed before it is re-advertised." + +#: ../../configuration/protocols/segment-routing.rst:47 +msgid "No support for SRLB" +msgstr "No support for SRLB" + +#: ../../configuration/protocols/segment-routing.rst:45 +msgid "No support for binding SID" +msgstr "No support for binding SID" + +#: ../../configuration/protocols/segment-routing.rst:43 +msgid "No support for level redistribution (L1 to L2 or L2 to L1)" +msgstr "No support for level redistribution (L1 to L2 or L2 to L1)" + +#: ../../configuration/service/webproxy.rst:99 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:31 +msgid "None of the operating systems have client software installed by default" +msgstr "None of the operating systems have client software installed by default" + +#: ../../configuration/system/syslog.rst:185 +msgid "Normal but significant conditions - conditions that are not error conditions, but that may require special handling." +msgstr "Normal but significant conditions - conditions that are not error conditions, but that may require special handling." + +#: ../../configuration/interfaces/bonding.rst:51 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:127 +msgid "Note: certificate names don't matter, we use 'openvpn-local' and 'openvpn-remote' but they can be arbitrary." +msgstr "Note: certificate names don't matter, we use 'openvpn-local' and 'openvpn-remote' but they can be arbitrary." + +#: ../../configuration/system/syslog.rst:246 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:294 +#: ../../configuration/vpn/rsa-keys.rst:35 +msgid "Note the command with the public key (set pki key-pair ipsec-RIGHT public key 'FAAOCAQ8AMII...')." +msgstr "Note the command with the public key (set pki key-pair ipsec-RIGHT public key 'FAAOCAQ8AMII...')." + +#: ../../configuration/system/syslog.rst:185 +msgid "Notice" +msgstr "Notice" + +#: ../../configuration/service/conntrack-sync.rst:194 +msgid "Now configure conntrack-sync service on ``router1`` **and** ``router2``" +msgstr "Now configure conntrack-sync service on ``router1`` **and** ``router2``" + +#: ../../configuration/vpn/ipsec.rst:297 +msgid "Now the noted public keys should be entered on the opposite routers." +msgstr "Now the noted public keys should be entered on the opposite routers." + +#: ../../configuration/service/dhcp-server.rst:503 +msgid "Now we add the option to the scope, adapt to your setup" +msgstr "Now we add the option to the scope, adapt to your setup" + +#: ../../configuration/interfaces/openvpn.rst:385 +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 "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." + +#: ../../configuration/vpn/openconnect.rst:212 +msgid "Now when connecting the user will first be asked for the password and then the OTP key." +msgstr "Now when connecting the user will first be asked for the password and then the OTP key." + +#: ../../configuration/vpn/rsa-keys.rst:52 +msgid "Now you are ready to setup IPsec. The key points:" +msgstr "Now you are ready to setup IPsec. The key points:" + +#: ../../configuration/vpn/ipsec.rst:311 +msgid "Now you are ready to setup IPsec. You'll need to use an ID instead of address for the peer." +msgstr "Now you are ready to setup IPsec. You'll need to use an ID instead of address for the peer." + +#: ../../configuration/interfaces/wireless.rst:224 +msgid "Number of antennas on this card" +msgstr "Number of antennas on this card" + +#: ../../configuration/system/syslog.rst:231 +msgid "Number of lines to be displayed, default 10" +msgstr "Number of lines to be displayed, default 10" + +#: ../../configuration/protocols/ospf.rst:5 +msgid "OSPF" +msgstr "OSPF" + +#: ../../configuration/protocols/segment-routing.rst:120 +msgid "OSPF SR Configuration" +msgstr "OSPF SR Configuration" + +#: ../../configuration/protocols/ospf.rst:15 +msgid "OSPF is a widely used IGP in large enterprise networks." +msgstr "OSPF is a widely used IGP in large enterprise networks." + +#: ../../configuration/protocols/ospf.rst:539 +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 "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." + +#: ../../configuration/protocols/ospf.rst:19 +msgid "OSPFv2 (IPv4)" +msgstr "OSPFv2 (IPv4)" + +#: ../../configuration/protocols/ospf.rst:1071 +msgid "OSPFv3 (IPv6)" +msgstr "OSPFv3 (IPv6)" + +#: ../../configuration/system/login.rst:141 +msgid "OTP-key generation" +msgstr "OTP-key generation" + +#: ../../configuration/interfaces/ethernet.rst:57 +msgid "Offloading" +msgstr "Offloading" + +#: ../../configuration/service/dhcp-server.rst:278 +msgid "Offset of the client's subnet in seconds from Coordinated Universal Time (UTC)" +msgstr "Offset of the client's subnet in seconds from Coordinated Universal Time (UTC)" + +#: ../../configuration/trafficpolicy/index.rst:302 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:219 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:211 +msgid "On active router run:" +msgstr "On active router run:" + +#: ../../configuration/interfaces/openvpn.rst:83 +msgid "On both sides, you need to generate a self-signed certificate, preferrably using the \"ec\" (elliptic curve) type. You can generate them by executing command ``run generate pki certificate self-signed install <name>`` in the configuration mode. Once the command is complete, it will add the certificate to the configuration session, to the ``pki`` subtree. You can then review the proposed changes and commit them." +msgstr "On both sides, you need to generate a self-signed certificate, preferrably using the \"ec\" (elliptic curve) type. You can generate them by executing command ``run generate pki certificate self-signed install <name>`` in the configuration mode. Once the command is complete, it will add the certificate to the configuration session, to the ``pki`` subtree. You can then review the proposed changes and commit them." + +#: ../../configuration/trafficpolicy/index.rst:487 +msgid "On low rates (below 40Mbit) you may want to tune `quantum` down to something like 300 bytes." +msgstr "On low rates (below 40Mbit) you may want to tune `quantum` down to something like 300 bytes." + +#: ../../configuration/highavailability/index.rst:226 +msgid "On most scenarios, there's no need to change specific parameters, and using default configuration is enough. But there are cases were extra configuration is needed." +msgstr "On most scenarios, there's no need to change specific parameters, and using default configuration is enough. But there are cases were extra configuration is needed." + +#: ../../configuration/service/conntrack-sync.rst:242 +msgid "On standby router run:" +msgstr "On standby router run:" + +#: ../../configuration/interfaces/dummy.rst:16 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:181 +#: ../../configuration/vpn/ipsec.rst:239 +#: ../../configuration/vpn/ipsec.rst:299 +#: ../../configuration/vpn/rsa-keys.rst:40 +msgid "On the LEFT:" +msgstr "On the LEFT:" + +#: ../../configuration/vpn/ipsec.rst:314 +#: ../../configuration/vpn/rsa-keys.rst:59 +msgid "On the LEFT (static address):" +msgstr "On the LEFT (static address):" + +#: ../../configuration/vpn/ipsec.rst:221 +msgid "On the RIGHT, setup by analogy and swap local and remote addresses." +msgstr "On the RIGHT, setup by analogy and swap local and remote addresses." + +#: ../../configuration/vpn/ipsec.rst:250 +#: ../../configuration/vpn/ipsec.rst:305 +#: ../../configuration/vpn/rsa-keys.rst:46 +msgid "On the RIGHT:" +msgstr "On the RIGHT:" + +#: ../../configuration/vpn/ipsec.rst:339 +#: ../../configuration/vpn/rsa-keys.rst:84 +msgid "On the RIGHT (dynamic address):" +msgstr "On the RIGHT (dynamic address):" + +#: ../../configuration/service/conntrack-sync.rst:207 +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 "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" + +#: ../../configuration/vpn/rsa-keys.rst:56 +msgid "On the initiator, we need to set the remote-id option so that it can identify IKE traffic from the responder correctly." +msgstr "On the initiator, we need to set the remote-id option so that it can identify IKE traffic from the responder correctly." + +#: ../../configuration/vpn/rsa-keys.rst:55 +msgid "On the initiator, we set the peer address to its public address, but on the responder we only set the id." +msgstr "On the initiator, we set the peer address to its public address, but on the responder we only set the id." + +#: ../../configuration/vpn/rsa-keys.rst:57 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:229 +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 "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." + +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +#: ../../_include/interface-ip.txt:21 +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 "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." + +#: ../../configuration/protocols/bgp.rst:702 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1152 +msgid "Once a traffic-policy is created, you can apply it to an interface:" +msgstr "Once a traffic-policy is created, you can apply it to an interface:" + +#: ../../configuration/interfaces/pseudo-ethernet.rst:27 +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 "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:" + +#: ../../configuration/system/flow-accounting.rst:177 +msgid "Once flow accounting is configured on an interfaces it provides the ability to display captured network traffic information for all configured interfaces." +msgstr "Once flow accounting is configured on an interfaces it provides the ability to display captured network traffic information for all configured interfaces." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:73 +msgid "Once the command is completed, it will add the certificate to the configuration session, to the pki subtree. You can then review the proposed changes and commit them." +msgstr "Once the command is completed, it will add the certificate to the configuration session, to the pki subtree. You can then review the proposed changes and commit them." + +#: ../../configuration/service/pppoe-server.rst:63 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:576 +msgid "Once the matching rules are set for a class, you can start configuring how you want matching traffic to behave." +msgstr "Once the matching rules are set for a class, you can start configuring how you want matching traffic to behave." + +#: ../../configuration/service/pppoe-server.rst:224 +msgid "Once the user is connected, the user session is using the set limits and can be displayed via 'show pppoe-server sessions'." +msgstr "Once the user is connected, the user session is using the set limits and can be displayed via 'show pppoe-server sessions'." + +#: ../../configuration/vpn/openconnect.rst:250 +msgid "Once you commit the above changes you can create a config file in the /config/auth/ocserv/config-per-user directory that matches a username of a user you have created e.g. \"tst\". Now when logging in with the \"tst\" user the config options you set in this file will be loaded." +msgstr "Once you commit the above changes you can create a config file in the /config/auth/ocserv/config-per-user directory that matches a username of a user you have created e.g. \"tst\". Now when logging in with the \"tst\" user the config options you set in this file will be loaded." + +#: ../../configuration/interfaces/pppoe.rst:52 +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 "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." + +#: ../../configuration/vpn/sstp.rst:295 +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 "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." + +#: ../../configuration/protocols/rpki.rst:183 +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 "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." + +#: ../../configuration/protocols/ospf.rst:319 +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 "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." + +#: ../../configuration/service/eventhandler.rst:70 +msgid "One implicit environment exists." +msgstr "One implicit environment exists." + +#: ../../configuration/service/conntrack-sync.rst:7 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:411 +msgid "One of the uses of Fair Queue might be the mitigation of Denial of Service attacks." +msgstr "One of the uses of Fair Queue might be the mitigation of Denial of Service attacks." + +#: ../../_include/interface-vlan-8021q.txt:32 +#: ../../_include/interface-vlan-8021q.txt:32 +#: ../../_include/interface-vlan-8021q.txt:32 +#: ../../_include/interface-vlan-8021q.txt:32 +#: ../../_include/interface-vlan-8021q.txt:32 +#: ../../_include/interface-vlan-8021q.txt:32 +msgid "Only 802.1Q-tagged packets are accepted on Ethernet vifs." +msgstr "Only 802.1Q-tagged packets are accepted on Ethernet vifs." + +#: ../../configuration/service/conntrack-sync.rst:63 +msgid "Only VRRP is supported. Required option." +msgstr "Only VRRP is supported. Required option." + +#: ../../configuration/firewall/general.rst:731 +#: ../../configuration/firewall/general-legacy.rst:490 +msgid "Only in the source criteria, you can specify a mac-address." +msgstr "Only in the source criteria, you can specify a mac-address." + +#: ../../configuration/protocols/segment-routing.rst:49 +msgid "Only one SRGB and default SPF Algorithm is supported" +msgstr "Only one SRGB and default SPF Algorithm is supported" + +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +#: ../../_include/interface-dhcp-options.txt:43 +msgid "Only request an address from the DHCP server but do not request a default gateway." +msgstr "Only request an address from the DHCP server but do not request a default gateway." + +#: ../../configuration/interfaces/pppoe.rst:124 +msgid "Only request an address from the PPPoE server but do not install any default route." +msgstr "Only request an address from the PPPoE server but do not install any default route." + +#: ../../configuration/interfaces/sstp-client.rst:46 +msgid "Only request an address from the SSTP server but do not install any default route." +msgstr "Only request an address from the SSTP server but do not install any default route." + +#: ../../configuration/system/login.rst:51 +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 "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." + +#: ../../configuration/highavailability/index.rst:457 +msgid "Op-mode check virtual-server status" +msgstr "Op-mode check virtual-server status" + +#: ../../configuration/vpn/openconnect.rst:5 +msgid "OpenConnect" +msgstr "OpenConnect" + +#: ../../configuration/vpn/openconnect.rst:7 +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 "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." + +#: ../../configuration/vpn/openconnect.rst:274 +msgid "OpenConnect can be configured to send accounting information to a RADIUS server to capture user session data such as time of connect/disconnect, data transferred, and so on." +msgstr "OpenConnect can be configured to send accounting information to a RADIUS server to capture user session data such as time of connect/disconnect, data transferred, and so on." + +#: ../../configuration/vpn/openconnect.rst:267 +msgid "OpenConnect server matches the filename in a case sensitive manner, make sure the username/group name you configure matches the filename exactly." +msgstr "OpenConnect server matches the filename in a case sensitive manner, make sure the username/group name you configure matches the filename exactly." + +#: ../../configuration/vpn/openconnect.rst:228 +msgid "OpenConnect supports a subset of it's configuration options to be applied on a per user/group basis, for configuration purposes we refer to this functionality as \"Identity based config\". The following `OpenConnect Server Manual <https://ocserv.gitlab.io/www/manual.html#:~:text=Configuration%20files%20that% 20will%20be%20applied%20per%20user%20connection%20or%0A%23%20per%20group>`_ outlines the set of configuration options that are allowed. This can be leveraged to apply different sets of configs to different users or groups of users." +msgstr "OpenConnect supports a subset of it's configuration options to be applied on a per user/group basis, for configuration purposes we refer to this functionality as \"Identity based config\". The following `OpenConnect Server Manual <https://ocserv.gitlab.io/www/manual.html#:~:text=Configuration%20files%20that% 20will%20be%20applied%20per%20user%20connection%20or%0A%23%20per%20group>`_ outlines the set of configuration options that are allowed. This can be leveraged to apply different sets of configs to different users or groups of users." + +#: ../../configuration/interfaces/openvpn.rst:7 +#: ../../configuration/pki/index.rst:117 +msgid "OpenVPN" +msgstr "OpenVPN" + +#: ../../configuration/interfaces/openvpn.rst:407 +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 "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:" + +#: ../../configuration/interfaces/openvpn.rst:669 +msgid "OpenVPN DCO is not full OpenVPN features supported , is currently considered experimental. Furthermore, there are certain OpenVPN features and use cases that remain incompatible with DCO. To get a comprehensive understanding of the limitations associated with DCO, refer to the list of known limitations in the documentation." +msgstr "OpenVPN DCO is not full OpenVPN features supported , is currently considered experimental. Furthermore, there are certain OpenVPN features and use cases that remain incompatible with DCO. To get a comprehensive understanding of the limitations associated with DCO, refer to the list of known limitations in the documentation." + +#: ../../configuration/interfaces/openvpn.rst:658 +msgid "OpenVPN Data Channel Offload (DCO)" +msgstr "OpenVPN Data Channel Offload (DCO)" + +#: ../../configuration/interfaces/openvpn.rst:660 +msgid "OpenVPN Data Channel Offload (DCO) enables significant performance enhancement in encrypted OpenVPN data processing. By minimizing context switching for each packet, DCO effectively reduces overhead. This optimization is achieved by keeping most data handling tasks within the kernel, avoiding frequent switches between kernel and user space for encryption and packet handling." +msgstr "OpenVPN Data Channel Offload (DCO) enables significant performance enhancement in encrypted OpenVPN data processing. By minimizing context switching for each packet, DCO effectively reduces overhead. This optimization is achieved by keeping most data handling tasks within the kernel, avoiding frequent switches between kernel and user space for encryption and packet handling." + +#: ../../configuration/interfaces/openvpn.rst:64 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:43 +msgid "OpenVPN is popular for client-server setups, but its site-to-site mode remains a relatively obscure feature, and many router appliances still don't support it. However, it's very useful for quickly setting up tunnels between routers." +msgstr "OpenVPN is popular for client-server setups, but its site-to-site mode remains a relatively obscure feature, and many router appliances still don't support it. However, it's very useful for quickly setting up tunnels between routers." + +#: ../../configuration/interfaces/openvpn.rst:320 +msgid "OpenVPN status can be verified using the `show openvpn` operational commands. See the built-in help for a complete list of options." +msgstr "OpenVPN status can be verified using the `show openvpn` operational commands. See the built-in help for a complete list of options." + +#: ../../configuration/vpn/openconnect.rst:154 +msgid "Openconnect Configuration" +msgstr "Openconnect Configuration" + +#: ../../configuration/interfaces/pppoe.rst:21 +msgid "Operating Modes" +msgstr "Operating Modes" + +#: ../../configuration/interfaces/bonding.rst:512 +#: ../../configuration/interfaces/dummy.rst:51 +#: ../../configuration/interfaces/ethernet.rst:132 +#: ../../configuration/interfaces/loopback.rst:41 +#: ../../configuration/interfaces/macsec.rst:106 +#: ../../configuration/interfaces/pppoe.rst:265 +#: ../../configuration/interfaces/sstp-client.rst:117 +#: ../../configuration/interfaces/virtual-ethernet.rst:55 +#: ../../configuration/interfaces/wireless.rst:416 +#: ../../configuration/interfaces/wwan.rst:79 +#: ../../configuration/pki/index.rst:252 +#: ../../configuration/protocols/igmp.rst:245 +#: ../../configuration/protocols/static.rst:183 +#: ../../configuration/service/conntrack-sync.rst:103 +#: ../../configuration/service/console-server.rst:76 +#: ../../configuration/service/dhcp-relay.rst:124 +#: ../../configuration/service/dhcp-relay.rst:199 +#: ../../configuration/service/dns.rst:182 +#: ../../configuration/service/lldp.rst:71 +#: ../../configuration/service/ssh.rst:145 +#: ../../configuration/service/webproxy.rst:330 +#: ../../configuration/system/default-route.rst:25 +#: ../../configuration/system/flow-accounting.rst:175 +#: ../../configuration/vrf/index.rst:111 +#: ../../configuration/vrf/index.rst:321 +#: ../../configuration/vrf/index.rst:501 +msgid "Operation" +msgstr "Operation" + +#: ../../configuration/firewall/general.rst:1307 +#: ../../configuration/firewall/general-legacy.rst:778 +msgid "Operation-mode Firewall" +msgstr "Operation-mode Firewall" + +#: ../../configuration/container/index.rst:143 +msgid "Operation Commands" +msgstr "Operation Commands" + +#: ../../configuration/service/dhcp-server.rst:512 +#: ../../configuration/service/dhcp-server.rst:732 +#: ../../configuration/system/acceleration.rst:42 +msgid "Operation Mode" +msgstr "Operation Mode" + +#: ../../configuration/interfaces/wireless.rst:89 +msgid "Operation mode of wireless radio." +msgstr "Operation mode of wireless radio." + +#: ../../configuration/interfaces/wireguard.rst:338 +#: ../../configuration/protocols/bfd.rst:94 +#: ../../configuration/protocols/bfd.rst:175 +msgid "Operational Commands" +msgstr "Operational Commands" + +#: ../../configuration/protocols/bgp.rst:950 +#: ../../configuration/protocols/mpls.rst:218 +#: ../../configuration/protocols/ospf.rst:609 +#: ../../configuration/protocols/ospf.rst:1266 +#: ../../configuration/protocols/rip.rst:193 +msgid "Operational Mode Commands" +msgstr "Operational Mode Commands" + +#: ../../configuration/system/ip.rst:47 +#: ../../configuration/system/ipv6.rst:43 +msgid "Operational commands" +msgstr "Operational commands" + +#: ../../configuration/system/option.rst:5 +msgid "Option" +msgstr "Option" + +#: ../../configuration/service/dhcp-server.rst:487 +msgid "Option 43 for UniFI" +msgstr "Option 43 for UniFI" + +#: ../../configuration/service/dhcp-server.rst:267 +msgid "Option description" +msgstr "Option description" + +#: ../../configuration/service/dhcp-server.rst:265 +msgid "Option number" +msgstr "Option number" + +#: ../../configuration/interfaces/bonding.rst:148 +msgid "Option specifying the rate in which we'll ask our link partner to transmit LACPDU packets in 802.3ad mode." +msgstr "Option specifying the rate in which we'll ask our link partner to transmit LACPDU packets in 802.3ad mode." + +#: ../../configuration/policy/route.rst:108 +msgid "Option to disable rule." +msgstr "Option to disable rule." + +#: ../../configuration/policy/route.rst:35 +msgid "Option to enable or disable log matching rule." +msgstr "Option to enable or disable log matching rule." + +#: ../../configuration/policy/route.rst:25 +msgid "Option to log packets hitting default-action." +msgstr "Option to log packets hitting default-action." + +#: ../../configuration/interfaces/wireguard.rst:86 +#: ../../configuration/protocols/ospf.rst:68 +#: ../../configuration/protocols/ospf.rst:1105 +msgid "Optional" +msgstr "Optional" + +#: ../../configuration/service/tftp-server.rst:43 +msgid "Optional, if you want to enable uploads, else TFTP server will act as a read-only server." +msgstr "Optional, if you want to enable uploads, else TFTP server will act as a read-only server." + +#: ../../configuration/system/login.rst:107 +msgid "Optional/default settings" +msgstr "Optional/default settings" + +#: ../../configuration/protocols/babel.rst:30 +#: ../../configuration/protocols/rip.rst:58 +msgid "Optional Configuration" +msgstr "Optional Configuration" + +#: ../../configuration/container/index.rst:47 +msgid "Optionally set a specific static IPv4 or IPv6 address for the container. This address must be within the named network prefix." +msgstr "Optionally set a specific static IPv4 or IPv6 address for the container. This address must be within the named network prefix." + +#: ../../configuration/interfaces/openvpn.rst:631 +#: ../../configuration/service/dhcp-relay.rst:53 +#: ../../configuration/service/dhcp-relay.rst:158 +#: ../../configuration/service/dhcp-server.rst:257 +#: ../../configuration/vpn/sstp.rst:219 +msgid "Options" +msgstr "Options" + +#: ../../configuration/vpn/ipsec.rst:159 +msgid "Options (Global IPsec settings) Attributes" +msgstr "Options (Global IPsec settings) Attributes" + +#: ../../configuration/firewall/general-legacy.rst:328 +msgid "Options used for queue target. Action queue must be defined to use this setting" +msgstr "Options used for queue target. Action queue must be defined to use this setting" + +#: ../../configuration/system/conntrack.rst:0 +msgid "Or, for example ftp, `delete system conntrack modules ftp`." +msgstr "Or, for example ftp, `delete system conntrack modules ftp`." + +#: ../../configuration/trafficpolicy/index.rst:66 +msgid "Or **binary** prefixes." +msgstr "Or **binary** prefixes." + +#: ../../configuration/protocols/ospf.rst:73 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:251 +msgid "Other attributes can be used, but they have to be in one of the dictionaries in */usr/share/accel-ppp/radius*." +msgstr "Other attributes can be used, but they have to be in one of the dictionaries in */usr/share/accel-ppp/radius*." + +#: ../../configuration/nat/nat44.rst:512 +msgid "Our configuration commands would be:" +msgstr "Our configuration commands would be:" + +#: ../../configuration/interfaces/wireguard.rst:144 +msgid "Our remote end of the tunnel for peer `to-wg02` is reachable at 192.0.2.1 port 51820" +msgstr "Our remote end of the tunnel for peer `to-wg02` is reachable at 192.0.2.1 port 51820" + +#: ../../configuration/loadbalancing/wan.rst:6 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:97 +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 "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." + +#: ../../configuration/nat/nat66.rst:81 +msgid "Output from `eth0` network interface" +msgstr "Output from `eth0` network interface" + +#: ../../configuration/service/monitoring.rst:43 +msgid "Output plugin Prometheus client" +msgstr "Output plugin Prometheus client" + +#: ../../configuration/interfaces/l2tpv3.rst:89 +msgid "Over IP" +msgstr "Over IP" + +#: ../../configuration/interfaces/l2tpv3.rst:135 +msgid "Over IPSec, L2 VPN (bridge)" +msgstr "Over IPSec, L2 VPN (bridge)" + +#: ../../configuration/interfaces/l2tpv3.rst:108 +msgid "Over UDP" +msgstr "Over UDP" + +#: ../../configuration/service/dhcp-server.rst:473 +msgid "Override static-mapping's name-server with a custom one that will be sent only to this host." +msgstr "Override static-mapping's name-server with a custom one that will be sent only to this host." + +#: ../../configuration/firewall/general.rst:11 +#: ../../configuration/firewall/general-legacy.rst:15 +#: ../../configuration/nat/nat44.rst:68 +#: ../../configuration/nat/nat66.rst:15 +msgid "Overview" +msgstr "Overview" + +#: ../../configuration/service/snmp.rst:29 +msgid "Overview and basic concepts" +msgstr "Overview and basic concepts" + +#: ../../configuration/firewall/general.rst:1461 +#: ../../configuration/firewall/general-legacy.rst:908 +msgid "Overview of defined groups. You see the type, the members, and where the group is used." +msgstr "Overview of defined groups. You see the type, the members, and where the group is used." + +#: ../../configuration/policy/examples.rst:106 +msgid "PBR multiple uplinks" +msgstr "PBR multiple uplinks" + +#: ../../configuration/vrf/index.rst:244 +msgid "PC1 is in the ``default`` VRF and acting as e.g. a \"fileserver\"" +msgstr "PC1 is in the ``default`` VRF and acting as e.g. a \"fileserver\"" + +#: ../../configuration/vrf/index.rst:245 +msgid "PC2 is in VRF ``blue`` which is the development department" +msgstr "PC2 is in VRF ``blue`` which is the development department" + +#: ../../configuration/vrf/index.rst:246 +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 "PC3 and PC4 are connected to a bridge device on router ``R1`` which is in VRF ``red``. Say this is the HR department." + +#: ../../configuration/interfaces/vxlan.rst:109 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:120 +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 "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." + +#: ../../configuration/protocols/igmp.rst:16 +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 "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." + +#: ../../configuration/protocols/igmp.rst:14 +msgid "PIM and IGMP" +msgstr "PIM and IGMP" + +#: ../../configuration/protocols/pim6.rst:9 +msgid "PIMv6 (Protocol Independent Multicast for IPv6) 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 "PIMv6 (Protocol Independent Multicast for IPv6) 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." + +#: ../../configuration/pki/index.rst:7 +msgid "PKI" +msgstr "PKI" + +#: ../../configuration/interfaces/wireless.rst:130 +msgid "PPDU" +msgstr "PPDU" + +#: ../../configuration/vpn/sstp.rst:163 +msgid "PPP Settings" +msgstr "PPP Settings" + +#: ../../configuration/interfaces/pppoe.rst:7 +msgid "PPPoE" +msgstr "PPPoE" + +#: ../../configuration/service/pppoe-server.rst:7 +msgid "PPPoE Server" +msgstr "PPPoE Server" + +#: ../../configuration/interfaces/pppoe.rst:81 +msgid "PPPoE options" +msgstr "PPPoE options" + +#: ../../configuration/vpn/pptp.rst:4 +msgid "PPTP-Server" +msgstr "PPTP-Server" + +#: ../../configuration/loadbalancing/wan.rst:104 +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 "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:" + +#: ../../configuration/protocols/rpki.rst:71 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:60 +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 "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." + +#: ../../configuration/vpn/sstp.rst:155 +msgid "Path to `<file>` pointing to the certificate authority certificate." +msgstr "Path to `<file>` pointing to the certificate authority certificate." + +#: ../../configuration/vpn/sstp.rst:159 +msgid "Path to `<file>` pointing to the servers certificate (public portion)." +msgstr "Path to `<file>` pointing to the servers certificate (public portion)." + +#: ../../configuration/protocols/bgp.rst:221 +msgid "Peer - Peer" +msgstr "Peer - Peer" + +#: ../../configuration/protocols/bgp.rst:475 +msgid "Peer Groups" +msgstr "Peer Groups" + +#: ../../configuration/policy/route-map.rst:159 +msgid "Peer IP address to match." +msgstr "Peer IP address to match." + +#: ../../configuration/protocols/bgp.rst:321 +msgid "Peer Parameters" +msgstr "Peer Parameters" + +#: ../../configuration/protocols/bgp.rst:477 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:89 +msgid "Peer to send unicast UDP conntrack sync entires to, if not using Multicast configuration from above above." +msgstr "Peer to send unicast UDP conntrack sync entires to, if not using Multicast configuration from above above." + +#: ../../configuration/protocols/bgp.rst:183 +msgid "Peers Configuration" +msgstr "Peers Configuration" + +#: ../../configuration/loadbalancing/wan.rst:188 +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 "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:" + +#: ../../configuration/system/syslog.rst:7 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:127 +msgid "Per default every packet is sampled (that is, the sampling rate is 1)." +msgstr "Per default every packet is sampled (that is, the sampling rate is 1)." + +#: ../../configuration/service/pppoe-server.rst:336 +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 "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." + +#: ../../configuration/system/option.rst:78 +msgid "Performance" +msgstr "Performance" + +#: ../../configuration/interfaces/bridge.rst:118 +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 "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." + +#: ../../configuration/vrf/index.rst:197 +msgid "Ping command can be interrupted at any given time using ``<Ctrl>+c``. A brief statistic is shown afterwards." +msgstr "Ping command can be interrupted at any given time using ``<Ctrl>+c``. A brief statistic is shown afterwards." + +#: ../../configuration/vrf/index.rst:183 +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 "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." + +#: ../../configuration/interfaces/macsec.rst:183 +msgid "Pinging (IPv6) the other host and intercepting the traffic in ``eth1`` will show you the content is encrypted." +msgstr "Pinging (IPv6) the other host and intercepting the traffic in ``eth1`` will show you the content is encrypted." + +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +#: ../../_include/interface-vrf.txt:4 +msgid "Place interface in given VRF instance." +msgstr "Place interface in given VRF instance." + +#: ../../configuration/system/option.rst:23 +msgid "Play an audible beep to the system speaker when system is ready." +msgstr "Play an audible beep to the system speaker when system is ready." + +#: ../../configuration/service/ipoe-server.rst:23 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:12 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:43 +msgid "Please refer to the :ref:`ipsec` documentation for the individual IPSec related options." +msgstr "Please refer to the :ref:`ipsec` documentation for the individual IPSec related options." + +#: ../../configuration/vpn/dmvpn.rst:40 +msgid "Please refer to the :ref:`tunnel-interface` documentation for the individual tunnel related options." +msgstr "Please refer to the :ref:`tunnel-interface` documentation for the individual tunnel related options." + +#: ../../configuration/service/dhcp-server.rst:423 +msgid "Please see the :ref:`dhcp-dns-quick-start` configuration." +msgstr "Please see the :ref:`dhcp-dns-quick-start` configuration." + +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +#: ../../_include/need_improvement.txt:13 +msgid "Please take a look at the Contributing Guide for our :ref:`documentation`." +msgstr "Please take a look at the Contributing Guide for our :ref:`documentation`." + +#: ../../configuration/service/https.rst:10 +msgid "Please take a look at the :ref:`vyosapi` page for an detailed how-to." +msgstr "Please take a look at the :ref:`vyosapi` page for an detailed how-to." + +#: ../../configuration/service/salt-minion.rst:48 +msgid "Please take a look in the Automation section to find some usefull Examples." +msgstr "Please take a look in the Automation section to find some usefull Examples." + +#: ../../configuration/policy/index.rst:23 +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 "Policies, in VyOS, are implemented using FRR filtering and route maps. Detailed information of FRR could be found in http://docs.frrouting.org/" + +#: ../../configuration/policy/index.rst:9 +msgid "Policies are used for filtering and traffic management. With policies, network administrators could filter and treat traffic according to their needs." +msgstr "Policies are used for filtering and traffic management. With policies, network administrators could filter and treat traffic according to their needs." + +#: ../../configuration/policy/local-route.rst:5 +msgid "Policies for local traffic are defined in this section." +msgstr "Policies for local traffic are defined in this section." + +#: ../../configuration/policy/index.rst:7 +msgid "Policy" +msgstr "Policy" + +#: ../../configuration/policy/examples.rst:106 +msgid "Policy-Based Routing with multiple ISP uplinks (source ./draw.io/pbr_example_1.drawio)" +msgstr "Policy-Based Routing with multiple ISP uplinks (source ./draw.io/pbr_example_1.drawio)" + +#: ../../configuration/policy/index.rst:28 +msgid "Policy Sections" +msgstr "Policy Sections" + +#: ../../configuration/protocols/failover.rst:38 +msgid "Policy for checking targets" +msgstr "Policy for checking targets" + +#: ../../configuration/system/conntrack.rst:152 +msgid "Policy to track previously established connections." +msgstr "Policy to track previously established connections." + +#: ../../configuration/firewall/general.rst:257 +#: ../../configuration/firewall/general-legacy.rst:215 +msgid "Port Groups" +msgstr "Port Groups" + +#: ../../configuration/interfaces/bonding.rst:282 +#: ../../configuration/interfaces/bridge.rst:179 +#: ../../configuration/interfaces/ethernet.rst:124 +msgid "Port Mirror (SPAN)" +msgstr "Port Mirror (SPAN)" + +#: ../../configuration/vpn/sstp.rst:231 +msgid "Port for Dynamic Authorization Extension server (DM/CoA)" +msgstr "Port for Dynamic Authorization Extension server (DM/CoA)" + +#: ../../configuration/service/lldp.rst:27 +msgid "Port name and description" +msgstr "Port name and description" + +#: ../../configuration/service/monitoring.rst:67 +msgid "Port number used by connection, default is ``9273``" +msgstr "Port number used by connection, default is ``9273``" + +#: ../../configuration/service/conntrack-sync.rst:75 +msgid "Port number used by connection." +msgstr "Port number used by connection." + +#: ../../configuration/service/https.rst:46 +msgid "Port to listen for HTTPS requests; default 443" +msgstr "Port to listen for HTTPS requests; default 443" + +#: ../../_include/interface-vlan-8021q.txt:9 +#: ../../_include/interface-vlan-8021q.txt:9 +#: ../../_include/interface-vlan-8021q.txt:9 +#: ../../_include/interface-vlan-8021q.txt:9 +#: ../../_include/interface-vlan-8021q.txt:9 +#: ../../_include/interface-vlan-8021q.txt:9 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:169 +msgid "Pre-shared keys" +msgstr "Pre-shared keys" + +#: ../../configuration/trafficpolicy/index.rst:787 +#: ../../configuration/trafficpolicy/index.rst:862 +msgid "Precedence" +msgstr "Precedence" + +#: ../../configuration/highavailability/index.rst:148 +msgid "Preemption" +msgstr "Preemption" + +#: ../../configuration/policy/index.rst:20 +msgid "Prefer a specific routing protocol routes over another routing protocol running on the same router." +msgstr "Prefer a specific routing protocol routes over another routing protocol running on the same router." + +#: ../../configuration/protocols/bgp.rst:69 +msgid "Prefer higher local preference routes to lower." +msgstr "Prefer higher local preference routes to lower." + +#: ../../configuration/protocols/bgp.rst:65 +msgid "Prefer higher local weight routes to lower routes." +msgstr "Prefer higher local weight routes to lower routes." + +#: ../../configuration/protocols/bgp.rst:73 +msgid "Prefer local routes (statics, aggregates, redistributed) to received routes." +msgstr "Prefer local routes (statics, aggregates, redistributed) to received routes." + +#: ../../configuration/protocols/bgp.rst:77 +msgid "Prefer shortest hop-count AS_PATHs." +msgstr "Prefer shortest hop-count AS_PATHs." + +#: ../../configuration/protocols/bgp.rst:81 +msgid "Prefer the lowest origin type route. That is, prefer IGP origin routes to EGP, to Incomplete routes." +msgstr "Prefer the lowest origin type route. That is, prefer IGP origin routes to EGP, to Incomplete routes." + +#: ../../configuration/protocols/bgp.rst:91 +msgid "Prefer the route received from an external, eBGP peer over routes received from other types of peers." +msgstr "Prefer the route received from an external, eBGP peer over routes received from other types of peers." + +#: ../../configuration/protocols/bgp.rst:127 +msgid "Prefer the route received from the peer with the higher transport layer address, as a last-resort tie-breaker." +msgstr "Prefer the route received from the peer with the higher transport layer address, as a last-resort tie-breaker." + +#: ../../configuration/protocols/bgp.rst:96 +msgid "Prefer the route with the lower IGP cost." +msgstr "Prefer the route with the lower IGP cost." + +#: ../../configuration/protocols/bgp.rst:115 +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 "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." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Preference associated with the default router" +msgstr "Preference associated with the default router" + +#: ../../configuration/nat/nat66.rst:66 +msgid "Prefix Conversion" +msgstr "Prefix Conversion" + +#: ../../configuration/service/dhcp-server.rst:634 +msgid "Prefix Delegation" +msgstr "Prefix Delegation" + +#: ../../configuration/policy/prefix-list.rst:3 +msgid "Prefix List Policy" +msgstr "Prefix List Policy" + +#: ../../configuration/policy/prefix-list.rst:19 +msgid "Prefix Lists" +msgstr "Prefix Lists" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Prefix can not be used for on-link determination" +msgstr "Prefix can not be used for on-link determination" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Prefix can not be used for stateless address auto-configuration" +msgstr "Prefix can not be used for stateless address auto-configuration" + +#: ../../configuration/policy/prefix-list.rst:12 +msgid "Prefix filtering can be done using prefix-list and prefix-list6." +msgstr "Prefix filtering can be done using prefix-list and prefix-list6." + +#: ../../configuration/protocols/ospf.rst:41 +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 "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." + +#: ../../configuration/policy/prefix-list.rst:5 +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 "Prefix lists provides the most powerful prefix based filtering mechanism. In addition to access-list functionality, ip prefix-list has prefix length range specification." + +#: ../../configuration/policy/prefix-list.rst:39 +msgid "Prefix to match against." +msgstr "Prefix to match against." + +#: ../../configuration/trafficpolicy/index.rst:50 +msgid "Prefixes" +msgstr "Prefixes" + +#: ../../configuration/policy/route-map.rst:212 +msgid "Prepend the existing last AS number (the leftmost ASN) to the AS_PATH." +msgstr "Prepend the existing last AS number (the leftmost ASN) to the AS_PATH." + +#: ../../configuration/policy/route-map.rst:207 +msgid "Prepend the given string of AS numbers to the AS_PATH of the BGP path's NLRI." +msgstr "Prepend the given string of AS numbers to the AS_PATH of the BGP path's NLRI." + +#: ../../configuration/service/snmp.rst:63 +msgid "Principle of SNMP Communication" +msgstr "Principle of SNMP Communication" + +#: ../../configuration/vrf/index.rst:530 +msgid "Print a summary of neighbor connections for the specified AFI/SAFI combination." +msgstr "Print a summary of neighbor connections for the specified AFI/SAFI combination." + +#: ../../configuration/vrf/index.rst:509 +msgid "Print active IPV4 or IPV6 routes advertised via the VPN SAFI." +msgstr "Print active IPV4 or IPV6 routes advertised via the VPN SAFI." + +#: ../../configuration/trafficpolicy/index.rst:787 +#: ../../configuration/trafficpolicy/index.rst:801 +msgid "Priority" +msgstr "Priority" + +#: ../../configuration/trafficpolicy/index.rst:688 +msgid "Priority Queue" +msgstr "Priority Queue" + +#: ../../configuration/trafficpolicy/index.rst:698 +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 "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." + +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +#: ../../_include/interface-ip.txt:153 +msgid "Private VLAN proxy arp. Basically allow proxy arp replies back to the same interface (from which the ARP request/solicitation was received)." +msgstr "Private VLAN proxy arp. Basically allow proxy arp replies back to the same interface (from which the ARP request/solicitation was received)." + +#: ../../configuration/service/monitoring.rst:38 +msgid "Prometheus-client" +msgstr "Prometheus-client" + +#: ../../configuration/service/ssh.rst:114 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:57 +msgid "Protocol for which expect entries need to be synchronized." +msgstr "Protocol for which expect entries need to be synchronized." + +#: ../../configuration/protocols/index.rst:3 +msgid "Protocols" +msgstr "Protocols" + +#: ../../configuration/service/conntrack-sync.rst:45 +msgid "Protocols are: tcp, sctp, dccp, udp, icmp and ipv6-icmp." +msgstr "Protocols are: tcp, sctp, dccp, udp, icmp and ipv6-icmp." + +#: ../../configuration/service/tftp-server.rst:49 +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 "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." + +#: ../../configuration/firewall/general.rst:212 +#: ../../configuration/firewall/general-legacy.rst:188 +msgid "Provide a IPv4 or IPv6 address group description" +msgstr "Provide a IPv4 or IPv6 address group description" + +#: ../../configuration/firewall/general-legacy.rst:212 +msgid "Provide a IPv4 or IPv6 network group description." +msgstr "Provide a IPv4 or IPv6 network group description." + +#: ../../configuration/firewall/general.rst:515 +#: ../../configuration/firewall/general-legacy.rst:334 +#: ../../configuration/policy/route.rst:30 +msgid "Provide a description for each rule." +msgstr "Provide a description for each rule." + +#: ../../configuration/firewall/general.rst:314 +msgid "Provide a domain group description." +msgstr "Provide a domain group description." + +#: ../../configuration/firewall/general.rst:297 +msgid "Provide a mac group description." +msgstr "Provide a mac group description." + +#: ../../configuration/firewall/general.rst:279 +#: ../../configuration/firewall/general-legacy.rst:237 +msgid "Provide a port group description." +msgstr "Provide a port group description." + +#: ../../configuration/firewall/general-legacy.rst:281 +#: ../../configuration/policy/route.rst:20 +msgid "Provide a rule-set description." +msgstr "Provide a rule-set description." + +#: ../../configuration/firewall/general.rst:503 +msgid "Provide a rule-set description to a custom firewall chain." +msgstr "Provide a rule-set description to a custom firewall chain." + +#: ../../configuration/firewall/general.rst:236 +msgid "Provide an IPv4 or IPv6 network group description." +msgstr "Provide an IPv4 or IPv6 network group description." + +#: ../../configuration/firewall/general.rst:254 +msgid "Provide an interface group description" +msgstr "Provide an interface group description" + +#: ../../configuration/protocols/bgp.rst:219 +msgid "Provider - Customer" +msgstr "Provider - Customer" + +#: ../../configuration/protocols/ospf.rst:337 +msgid "Provides a backbone area coherence by virtual link establishment." +msgstr "Provides a backbone area coherence by virtual link establishment." + +#: ../../_include/interface-per-client-thread.txt:4 +#: ../../_include/interface-per-client-thread.txt:4 +msgid "Provides a per-device control to enable/disable the threaded mode for all the NAPI instances of the given network device, without the need for a device up/down." +msgstr "Provides a per-device control to enable/disable the threaded mode for all the NAPI instances of the given network device, without the need for a device up/down." + +#: ../../configuration/service/webproxy.rst:186 +msgid "Proxy authentication method, currently only LDAP is supported." +msgstr "Proxy authentication method, currently only LDAP is supported." + +#: ../../configuration/interfaces/pseudo-ethernet.rst:31 +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 "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." + +#: ../../configuration/interfaces/pseudo-ethernet.rst:36 +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 "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" + +#: ../../configuration/interfaces/pseudo-ethernet.rst:9 +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 "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," + +#: ../../configuration/interfaces/pseudo-ethernet.rst:55 +msgid "Pseudo Ethernet/MACVLAN options" +msgstr "Pseudo Ethernet/MACVLAN options" + +#: ../../configuration/container/index.rst:74 +msgid "Publish a port for the container." +msgstr "Publish a port for the container." + +#: ../../configuration/container/index.rst:147 +msgid "Pull a new image for container" +msgstr "Pull a new image for container" + +#: ../../configuration/interfaces/ethernet.rst:117 +#: ../../configuration/interfaces/virtual-ethernet.rst:39 +#: ../../configuration/interfaces/wireless.rst:408 +msgid "QinQ (802.1ad)" +msgstr "QinQ (802.1ad)" + +#: ../../configuration/trafficpolicy/index.rst:10 +msgid "QoS" +msgstr "QoS" + +#: ../../configuration/service/conntrack-sync.rst:53 +msgid "Queue size for listening to local conntrack events in MB." +msgstr "Queue size for listening to local conntrack events in MB." + +#: ../../configuration/service/conntrack-sync.rst:94 +msgid "Queue size for syncing conntrack entries in MB." +msgstr "Queue size for syncing conntrack entries in MB." + +#: ../../configuration/service/dhcp-server.rst:416 +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 "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." + +#: ../../configuration/nat/nat66.rst:118 +msgid "R1:" +msgstr "R1:" + +#: ../../configuration/interfaces/macsec.rst:156 +msgid "R1 has 192.0.2.1/24 & 2001:db8::1/64" +msgstr "R1 has 192.0.2.1/24 & 2001:db8::1/64" + +#: ../../configuration/vrf/index.rst:248 +msgid "R1 is managed through an out-of-band network that resides in VRF ``mgmt``" +msgstr "R1 is managed through an out-of-band network that resides in VRF ``mgmt``" + +#: ../../configuration/nat/nat66.rst:131 +msgid "R2:" +msgstr "R2:" + +#: ../../configuration/interfaces/macsec.rst:157 +msgid "R2 has 192.0.2.2/24 & 2001:db8::2/64" +msgstr "R2 has 192.0.2.2/24 & 2001:db8::2/64" + +#: ../../configuration/system/login.rst:234 +#: ../../configuration/vpn/sstp.rst:196 +msgid "RADIUS" +msgstr "RADIUS" + +#: ../../configuration/service/ipoe-server.rst:111 +msgid "RADIUS Setup" +msgstr "RADIUS Setup" + +#: ../../configuration/vpn/l2tp.rst:203 +msgid "RADIUS advanced features" +msgstr "RADIUS advanced features" + +#: ../../configuration/vpn/l2tp.rst:139 +msgid "RADIUS authentication" +msgstr "RADIUS authentication" + +#: ../../configuration/vpn/l2tp.rst:180 +msgid "RADIUS bandwidth shaping attribute" +msgstr "RADIUS bandwidth shaping attribute" + +#: ../../configuration/service/pppoe-server.rst:125 +msgid "RADIUS provides the IP addresses in the example above via Framed-IP-Address." +msgstr "RADIUS provides the IP addresses in the example above via Framed-IP-Address." + +#: ../../configuration/interfaces/wireless.rst:354 +msgid "RADIUS server at ``192.168.3.10`` with shared-secret ``VyOSPassword``" +msgstr "RADIUS server at ``192.168.3.10`` with shared-secret ``VyOSPassword``" + +#: ../../configuration/system/login.rst:266 +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." +msgstr "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." + +#: ../../configuration/vpn/l2tp.rst:163 +msgid "RADIUS source address" +msgstr "RADIUS source address" + +#: ../../configuration/highavailability/index.rst:202 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:289 +msgid "RFC 868 time server IPv4 address" +msgstr "RFC 868 time server IPv4 address" + +#: ../../configuration/protocols/rip.rst:7 +msgid "RIP" +msgstr "RIP" + +#: ../../configuration/protocols/rip.rst:19 +msgid "RIPv1 as described in :rfc:`1058`" +msgstr "RIPv1 as described in :rfc:`1058`" + +#: ../../configuration/protocols/rip.rst:20 +msgid "RIPv2 as described in :rfc:`2453`" +msgstr "RIPv2 as described in :rfc:`2453`" + +#: ../../configuration/protocols/rpki.rst:5 +msgid "RPKI" +msgstr "RPKI" + +#: ../../configuration/protocols/bgp.rst:223 +msgid "RS-Server - RS-Client" +msgstr "RS-Server - RS-Client" + +#: ../../configuration/vpn/rsa-keys.rst:4 +msgid "RSA-Keys" +msgstr "RSA-Keys" + +#: ../../configuration/vpn/rsa-keys.rst:5 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:763 +msgid "Random-Detect" +msgstr "Random-Detect" + +#: ../../configuration/trafficpolicy/index.rst:807 +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 "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." + +#: ../../configuration/protocols/static.rst:37 +#: ../../configuration/protocols/static.rst:57 +#: ../../configuration/protocols/static.rst:84 +#: ../../configuration/protocols/static.rst:104 +msgid "Range is 1 to 255, default is 1." +msgstr "Range is 1 to 255, default is 1." + +#: ../../configuration/protocols/failover.rst:26 +msgid "Range is 1 to 300, default is 10." +msgstr "Range is 1 to 300, default is 10." + +#: ../../configuration/trafficpolicy/index.rst:952 +msgid "Rate-Control is a CPU-friendly policy. You might consider using it when you just simply want to slow traffic down." +msgstr "Rate-Control is a CPU-friendly policy. You might consider using it when you just simply want to slow traffic down." + +#: ../../configuration/trafficpolicy/index.rst:918 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:913 +msgid "Rate Control" +msgstr "Rate Control" + +#: ../../configuration/loadbalancing/wan.rst:77 +msgid "Rate limit" +msgstr "Rate limit" + +#: ../../configuration/service/dhcp-server.rst:395 +#: ../../configuration/service/dhcp-server.rst:471 +msgid "Raw Parameters" +msgstr "Raw Parameters" + +#: ../../configuration/service/dhcp-server.rst:397 +msgid "Raw parameters can be passed to shared-network-name, subnet and static-mapping:" +msgstr "Raw parameters can be passed to shared-network-name, subnet and static-mapping:" + +#: ../../configuration/service/ssh.rst:162 +msgid "Re-generated a known pub/private keyfile which can be used to connect to other services (e.g. RPKI cache)." +msgstr "Re-generated a known pub/private keyfile which can be used to connect to other services (e.g. RPKI cache)." + +#: ../../configuration/service/ssh.rst:154 +msgid "Re-generated the public/private keyportion which SSH uses to secure connections." +msgstr "Re-generated the public/private keyportion which SSH uses to secure connections." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Reachable Time" +msgstr "Reachable Time" + +#: ../../configuration/highavailability/index.rst:388 +msgid "Real server" +msgstr "Real server" + +#: ../../configuration/highavailability/index.rst:389 +msgid "Real server IP address and port" +msgstr "Real server IP address and port" + +#: ../../configuration/highavailability/index.rst:404 +msgid "Real server is auto-excluded if port check with this server fail." +msgstr "Real server is auto-excluded if port check with this server fail." + +#: ../../configuration/interfaces/bonding.rst:96 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:205 +msgid "Received RADIUS attributes have a higher priority than parameters defined within the CLI configuration, refer to the explanation below." +msgstr "Received RADIUS attributes have a higher priority than parameters defined within the CLI configuration, refer to the explanation below." + +#: ../../configuration/service/webproxy.rst:255 +msgid "Recommended for larger installations." +msgstr "Recommended for larger installations." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:171 +msgid "Redirect HTTP to HTTPS" +msgstr "Redirect HTTP to HTTPS" + +#: ../../configuration/nat/nat44.rst:417 +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 "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`." + +#: ../../configuration/nat/nat44.rst:413 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:91 +msgid "Redirect URL to a new location" +msgstr "Redirect URL to a new location" + +#: ../../configuration/protocols/babel.rst:154 +#: ../../configuration/protocols/bgp.rst:557 +#: ../../configuration/protocols/ospf.rst:564 +#: ../../configuration/protocols/ospf.rst:1249 +#: ../../configuration/protocols/rip.rst:136 +msgid "Redistribution Configuration" +msgstr "Redistribution Configuration" + +#: ../../configuration/nat/nat66.rst:35 +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 "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." + +#: ../../configuration/service/dns.rst:265 +msgid "Register DNS record ``example.vyos.io`` on DNS server ``ns1.vyos.io``" +msgstr "Register DNS record ``example.vyos.io`` on DNS server ``ns1.vyos.io``" + +#: ../../configuration/interfaces/ethernet.rst:110 +#: ../../configuration/interfaces/virtual-ethernet.rst:33 +#: ../../configuration/interfaces/wireless.rst:401 +msgid "Regular VLANs (802.1q)" +msgstr "Regular VLANs (802.1q)" + +#: ../../configuration/policy/community-list.rst:35 +msgid "Regular expression to match against a community-list." +msgstr "Regular expression to match against a community-list." + +#: ../../configuration/policy/large-community-list.rst:36 +msgid "Regular expression to match against a large community list." +msgstr "Regular expression to match against a large community list." + +#: ../../configuration/policy/as-path-list.rst:33 +msgid "Regular expression to match against an AS path. For example \"64501 64502\"." +msgstr "Regular expression to match against an AS path. For example \"64501 64502\"." + +#: ../../configuration/policy/extcommunity-list.rst:35 +msgid "Regular expression to match against an extended community list, where text could be:" +msgstr "Regular expression to match against an extended community list, where text could be:" + +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +#: ../../_include/interface-dhcp-options.txt:66 +msgid "Reject DHCP leases from a given address or range. This is useful when a modem gives a local IP when first starting." +msgstr "Reject DHCP leases from a given address or range. This is useful when a modem gives a local IP when first starting." + +#: ../../configuration/service/ssh.rst:135 +msgid "Remember source IP in seconds before reset their score. The default is 1800." +msgstr "Remember source IP in seconds before reset their score. The default is 1800." + +#: ../../configuration/service/console-server.rst:60 +msgid "Remote Access" +msgstr "Remote Access" + +#: ../../configuration/interfaces/wireguard.rst:267 +msgid "Remote Access \"RoadWarrior\" Example" +msgstr "Remote Access \"RoadWarrior\" Example" + +#: ../../configuration/interfaces/wireguard.rst:394 +msgid "Remote Access \"RoadWarrior\" clients" +msgstr "Remote Access \"RoadWarrior\" clients" + +#: ../../configuration/interfaces/openvpn.rst:152 +#: ../../configuration/interfaces/openvpn.rst:247 +msgid "Remote Configuration:" +msgstr "Remote Configuration:" + +#: ../../configuration/interfaces/openvpn.rst:137 +msgid "Remote Configuration - Annotated:" +msgstr "Remote Configuration - Annotated:" + +#: ../../configuration/system/syslog.rst:54 +msgid "Remote Host" +msgstr "Remote Host" + +#: ../../configuration/service/monitoring.rst:130 +msgid "Remote URL" +msgstr "Remote URL" + +#: ../../configuration/service/monitoring.rst:35 +msgid "Remote URL." +msgstr "Remote URL." + +#: ../../configuration/service/monitoring.rst:96 +msgid "Remote URL to Splunk collector" +msgstr "Remote URL to Splunk collector" + +#: ../../configuration/service/monitoring.rst:122 +msgid "Remote ``InfluxDB`` bucket name" +msgstr "Remote ``InfluxDB`` bucket name" + +#: ../../configuration/service/monitoring.rst:22 +msgid "Remote database name." +msgstr "Remote database name." + +#: ../../configuration/service/dhcp-server.rst:182 +msgid "Remote peer IP `<address>` of the second DHCP server in this failover cluster." +msgstr "Remote peer IP `<address>` of the second DHCP server in this failover cluster." + +#: ../../configuration/service/monitoring.rst:126 +msgid "Remote port" +msgstr "Remote port" + +#: ../../configuration/protocols/bfd.rst:48 +msgid "Remote transmission interval will be multiplied by this value" +msgstr "Remote transmission interval will be multiplied by this value" + +#: ../../configuration/vpn/l2tp.rst:216 +msgid "Renaming clients interfaces by RADIUS" +msgstr "Renaming clients interfaces by RADIUS" + +#: ../../configuration/interfaces/openvpn.rst:129 +msgid "Repeat the procedure on the other router." +msgstr "Repeat the procedure on the other router." + +#: ../../configuration/interfaces/macsec.rst:93 +msgid "Replay protection" +msgstr "Replay protection" + +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +#: ../../_include/interface-dhcpv6-options.txt:50 +msgid "Request only a temporary address and not form an IA_NA (Identity Association for Non-temporary Addresses) partnership." +msgstr "Request only a temporary address and not form an IA_NA (Identity Association for Non-temporary Addresses) partnership." + +#: ../../configuration/service/dhcp-relay.rst:175 +msgid "Requests are forwarded through ``eth2`` as the `upstream interface`" +msgstr "Requests are forwarded through ``eth2`` as the `upstream interface`" + +#: ../../configuration/vpn/sstp.rst:95 +msgid "Require the peer to authenticate itself using one of the following protocols: pap, chap, mschap, mschap-v2." +msgstr "Require the peer to authenticate itself using one of the following protocols: pap, chap, mschap, mschap-v2." + +#: ../../configuration/service/salt-minion.rst:17 +msgid "Requirements" +msgstr "Requirements" + +#: ../../configuration/interfaces/pppoe.rst:312 +msgid "Requirements:" +msgstr "Requirements:" + +#: ../../configuration/firewall/general.rst:1279 +msgid "Requirements to enable synproxy:" +msgstr "Requirements to enable synproxy:" + +#: ../../configuration/protocols/bgp.rst:1063 +#: ../../configuration/protocols/mpls.rst:248 +msgid "Reset" +msgstr "Reset" + +#: ../../configuration/interfaces/openvpn.rst:725 +msgid "Reset OpenVPN" +msgstr "Reset OpenVPN" + +#: ../../configuration/system/ipv6.rst:176 +msgid "Reset commands" +msgstr "Reset commands" + +#: ../../configuration/service/dns.rst:186 +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 "Resets the local DNS forwarding cache database. You can reset the cache for all entries or only for entries to a specific domain." + +#: ../../configuration/loadbalancing/wan.rst:309 +msgid "Restart" +msgstr "Restart" + +#: ../../configuration/service/dhcp-relay.rst:128 +msgid "Restart DHCP relay service" +msgstr "Restart DHCP relay service" + +#: ../../configuration/service/dhcp-relay.rst:203 +msgid "Restart DHCPv6 relay agent immediately." +msgstr "Restart DHCPv6 relay agent immediately." + +#: ../../configuration/container/index.rst:167 +msgid "Restart a given container" +msgstr "Restart a given container" + +#: ../../configuration/service/dhcp-server.rst:528 +msgid "Restart the DHCP server" +msgstr "Restart the DHCP server" + +#: ../../configuration/protocols/igmp.rst:249 +msgid "Restart the IGMP proxy process." +msgstr "Restart the IGMP proxy process." + +#: ../../configuration/service/ssh.rst:149 +msgid "Restart the SSH daemon process, the current session is not affected, only the background daemon is restarted." +msgstr "Restart the SSH daemon process, the current session is not affected, only the background daemon is restarted." + +#: ../../configuration/service/dns.rst:191 +msgid "Restarts the DNS recursor process. This also invalidates the local DNS forwarding cache." +msgstr "Restarts the DNS recursor process. This also invalidates the local DNS forwarding cache." + +#: ../../configuration/interfaces/wireless.rst:315 +#: ../../configuration/interfaces/wireless.rst:369 +#: ../../configuration/interfaces/wireless.rst:566 +msgid "Resulting in" +msgstr "Resulting in" + +#: ../../configuration/interfaces/vti.rst:14 +msgid "Results in:" +msgstr "Results in:" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Retransmit Timer" +msgstr "Retransmit Timer" + +#: ../../configuration/service/conntrack-sync.rst:140 +msgid "Retrieve current statistics of connection tracking subsystem." +msgstr "Retrieve current statistics of connection tracking subsystem." + +#: ../../configuration/service/conntrack-sync.rst:173 +msgid "Retrieve current status of connection tracking subsystem." +msgstr "Retrieve current status of connection tracking subsystem." + +#: ../../configuration/interfaces/wireguard.rst:77 +msgid "Retrieve public key portion from configured WIreGuard interface." +msgstr "Retrieve public key portion from configured WIreGuard interface." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:4 +msgid "Reverse-proxy" +msgstr "Reverse-proxy" + +#: ../../configuration/trafficpolicy/index.rst:958 +msgid "Round Robin" +msgstr "Round Robin" + +#: ../../configuration/protocols/bgp.rst:527 +msgid "Route Aggregation Configuration" +msgstr "Route Aggregation Configuration" + +#: ../../configuration/protocols/bgp.rst:682 +msgid "Route Dampening" +msgstr "Route Dampening" + +#: ../../configuration/protocols/bgp.rst:1188 +msgid "Route Filtering" +msgstr "Route Filtering" + +#: ../../configuration/protocols/bgp.rst:818 +msgid "Route Filtering Configuration" +msgstr "Route Filtering Configuration" + +#: ../../configuration/policy/route-map.rst:13 +msgid "Route Map" +msgstr "Route Map" + +#: ../../configuration/policy/route-map.rst:3 +msgid "Route Map Policy" +msgstr "Route Map Policy" + +#: ../../configuration/protocols/isis.rst:227 +msgid "Route Redistribution" +msgstr "Route Redistribution" + +#: ../../configuration/protocols/bgp.rst:904 +msgid "Route Reflector Configuration" +msgstr "Route Reflector Configuration" + +#: ../../configuration/protocols/bgp.rst:57 +msgid "Route Selection" +msgstr "Route Selection" + +#: ../../configuration/protocols/bgp.rst:737 +msgid "Route Selection Configuration" +msgstr "Route Selection Configuration" + +#: ../../configuration/policy/route.rst:3 +msgid "Route and Route6 Policy" +msgstr "Route and Route6 Policy" + +#: ../../configuration/protocols/bgp.rst:690 +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 "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." + +#: ../../configuration/protocols/bgp.rst:1190 +msgid "Route filter can be applied using a route-map:" +msgstr "Route filter can be applied using a route-map:" + +#: ../../configuration/policy/route-map.rst:5 +msgid "Route map is a powerfull command, that gives network administrators a very useful and flexible tool for traffic manipulation." +msgstr "Route map is a powerfull command, that gives network administrators a very useful and flexible tool for traffic manipulation." + +#: ../../configuration/protocols/rpki.rst:95 +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 "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." + +#: ../../configuration/protocols/failover.rst:56 +msgid "Route metric" +msgstr "Route metric" + +#: ../../configuration/policy/route-map.rst:184 +msgid "Route tag to match." +msgstr "Route tag to match." + +#: ../../configuration/service/router-advert.rst:5 +msgid "Router Advertisements" +msgstr "Router Advertisements" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Router Lifetime" +msgstr "Router Lifetime" + +#: ../../configuration/service/dhcp-relay.rst:89 +msgid "Router receives DHCP client requests on ``eth1`` and relays them to the server at 10.0.1.4 on ``eth2``." +msgstr "Router receives DHCP client requests on ``eth1`` and relays them to the server at 10.0.1.4 on ``eth2``." + +#: ../../configuration/vrf/index.rst:423 +msgid "Routes exported from a unicast VRF to the VPN RIB must be augmented by two parameters:" +msgstr "Routes exported from a unicast VRF to the VPN RIB must be augmented by two parameters:" + +#: ../../configuration/protocols/isis.rst:413 +msgid "Routes on Node 2:" +msgstr "Routes on Node 2:" + +#: ../../configuration/protocols/bgp.rst:230 +msgid "Routes that are sent from provider, rs-server, or the peer local-role (or if received by customer, rs-client, or the peer local-role) will be marked with a new Only to Customer (OTC) attribute." +msgstr "Routes that are sent from provider, rs-server, or the peer local-role (or if received by customer, rs-client, or the peer local-role) will be marked with a new Only to Customer (OTC) attribute." + +#: ../../configuration/protocols/bgp.rst:662 +#: ../../configuration/protocols/ospf.rst:92 +#: ../../configuration/protocols/rip.rst:64 +#: ../../configuration/protocols/static.rst:39 +#: ../../configuration/protocols/static.rst:59 +msgid "Routes with a distance of 255 are effectively disabled and not installed into the kernel." +msgstr "Routes with a distance of 255 are effectively disabled and not installed into the kernel." + +#: ../../configuration/protocols/bgp.rst:234 +msgid "Routes with this attribute can only be sent to your neighbor if your local-role is provider or rs-server. Routes with this attribute can be received only if your local-role is customer or rs-client." +msgstr "Routes with this attribute can only be sent to your neighbor if your local-role is provider or rs-server. Routes with this attribute can be received only if your local-role is customer or rs-client." + +#: ../../configuration/trafficpolicy/index.rst:803 +msgid "Routine" +msgstr "Routine" + +#: ../../configuration/vrf/index.rst:82 +msgid "Routing" +msgstr "Routing" + +#: ../../configuration/policy/examples.rst:95 +msgid "Routing tables that will be used in this example are:" +msgstr "Routing tables that will be used in this example are:" + +#: ../../configuration/firewall/general-legacy.rst:270 +#: ../../configuration/policy/route.rst:10 +msgid "Rule-Sets" +msgstr "Rule-Sets" + +#: ../../configuration/firewall/general.rst:1310 +#: ../../configuration/firewall/general-legacy.rst:781 +msgid "Rule-set overview" +msgstr "Rule-set overview" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:217 +msgid "Rule 10 matches requests with the domain name ``node1.example.com`` forwards to the backend ``bk-api-01``" +msgstr "Rule 10 matches requests with the domain name ``node1.example.com`` forwards to the backend ``bk-api-01``" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:254 +msgid "Rule 10 matches requests with the exact URL path ``/.well-known/xxx`` and redirects to location ``/certs/``." +msgstr "Rule 10 matches requests with the exact URL path ``/.well-known/xxx`` and redirects to location ``/certs/``." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:257 +msgid "Rule 20 matches requests with URL paths ending in ``/mail`` or exact path ``/email/bar`` redirect to location ``/postfix/``." +msgstr "Rule 20 matches requests with URL paths ending in ``/mail`` or exact path ``/email/bar`` redirect to location ``/postfix/``." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:220 +msgid "Rule 20 matches requests with the domain name ``node2.example.com`` forwards to the backend ``bk-api-02``" +msgstr "Rule 20 matches requests with the domain name ``node2.example.com`` forwards to the backend ``bk-api-02``" + +#: ../../configuration/firewall/general.rst:519 +msgid "Rule Status" +msgstr "Rule Status" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:50 +msgid "Rules" +msgstr "Rules" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:51 +msgid "Rules allow to control and route incoming traffic to specific backend based on predefined conditions. Rules allow to define matching criteria and perform action accordingly." +msgstr "Rules allow to control and route incoming traffic to specific backend based on predefined conditions. Rules allow to define matching criteria and perform action accordingly." + +#: ../../configuration/nat/nat44.rst:134 +msgid "Rules will be created for both :ref:`source-nat` and :ref:`destination-nat`." +msgstr "Rules will be created for both :ref:`source-nat` and :ref:`destination-nat`." + +#: ../../configuration/service/dns.rst:378 +msgid "Running Behind NAT" +msgstr "Running Behind NAT" + +#: ../../configuration/nat/nat44.rst:76 +msgid "SNAT" +msgstr "SNAT" + +#: ../../configuration/nat/nat66.rst:23 +msgid "SNAT66" +msgstr "SNAT66" + +#: ../../configuration/service/snmp.rst:5 +msgid "SNMP" +msgstr "SNMP" + +#: ../../configuration/service/snmp.rst:214 +msgid "SNMP Extensions" +msgstr "SNMP Extensions" + +#: ../../configuration/service/snmp.rst:70 +msgid "SNMP Protocol Versions" +msgstr "SNMP Protocol Versions" + +#: ../../configuration/service/snmp.rst:84 +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 "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)." + +#: ../../configuration/service/snmp.rst:23 +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 "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." + +#: ../../configuration/service/snmp.rst:13 +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 "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." + +#: ../../configuration/service/snmp.rst:77 +msgid "SNMPv2" +msgstr "SNMPv2" + +#: ../../configuration/service/snmp.rst:88 +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 "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." + +#: ../../configuration/service/snmp.rst:79 +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 "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)." + +#: ../../configuration/service/snmp.rst:122 +msgid "SNMPv3" +msgstr "SNMPv3" + +#: ../../configuration/service/snmp.rst:124 +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 "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." + +#: ../../_include/interface-mirror.txt:1 +#: ../../_include/interface-mirror.txt:1 +#: ../../_include/interface-mirror.txt:1 +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. 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 "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. 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." + +#: ../../configuration/protocols/rpki.rst:127 +#: ../../configuration/service/ssh.rst:5 +msgid "SSH" +msgstr "SSH" + +#: ../../configuration/service/ssh.rst:33 +msgid "SSH :ref:`ssh_key_based_authentication`" +msgstr "SSH :ref:`ssh_key_based_authentication`" + +#: ../../configuration/system/login.rst:57 +msgid "SSH :ref:`ssh_operation`" +msgstr "SSH :ref:`ssh_operation`" + +#: ../../configuration/system/option.rst:44 +msgid "SSH client" +msgstr "SSH client" + +#: ../../configuration/service/ssh.rst:12 +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 "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." + +#: ../../configuration/protocols/rpki.rst:137 +msgid "SSH username to establish an SSH connection to the cache server." +msgstr "SSH username to establish an SSH connection to the cache server." + +#: ../../configuration/service/ssh.rst:23 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:114 +msgid "SSID to be used in IEEE 802.11 management frames" +msgstr "SSID to be used in IEEE 802.11 management frames" + +#: ../../configuration/vpn/openconnect.rst:24 +#: ../../configuration/vpn/sstp.rst:151 +msgid "SSL Certificates" +msgstr "SSL Certificates" + +#: ../../configuration/vpn/openconnect.rst:100 +msgid "SSL Certificates generation" +msgstr "SSL Certificates generation" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:67 +msgid "SSL match Server Name Indication (SNI) option:" +msgstr "SSL match Server Name Indication (SNI) option:" + +#: ../../configuration/interfaces/sstp-client.rst:7 +msgid "SSTP Client" +msgstr "SSTP Client" + +#: ../../configuration/interfaces/sstp-client.rst:42 +msgid "SSTP Client Options" +msgstr "SSTP Client Options" + +#: ../../configuration/vpn/sstp.rst:5 +msgid "SSTP Server" +msgstr "SSTP Server" + +#: ../../configuration/vpn/sstp.rst:14 +msgid "SSTP is available for Linux, BSD, and Windows." +msgstr "SSTP is available for Linux, BSD, and Windows." + +#: ../../configuration/interfaces/sstp-client.rst:75 +msgid "SSTP remote server to connect to. Can be either an IP address or FQDN." +msgstr "SSTP remote server to connect to. Can be either an IP address or FQDN." + +#: ../../configuration/interfaces/bridge.rst:90 +msgid "STP Parameter" +msgstr "STP Parameter" + +#: ../../configuration/service/salt-minion.rst:5 +msgid "Salt-Minion" +msgstr "Salt-Minion" + +#: ../../configuration/service/salt-minion.rst:7 +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 "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." + +#: ../../configuration/protocols/ospf.rst:312 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:153 +msgid "Sample configuration of SVD with VLAN to VNI mappings is shown below." +msgstr "Sample configuration of SVD with VLAN to VNI mappings is shown below." + +#: ../../configuration/protocols/mpls.rst:201 +msgid "Sample configuration to setup LDP on VyOS" +msgstr "Sample configuration to setup LDP on VyOS" + +#: ../../configuration/interfaces/wireless.rst:515 +msgid "Scanning is not supported on all wireless drivers and wireless hardware. Refer to your driver and wireless hardware documentation for further details." +msgstr "Scanning is not supported on all wireless drivers and wireless hardware. Refer to your driver and wireless hardware documentation for further details." + +#: ../../configuration/loadbalancing/wan.rst:248 +msgid "Script execution" +msgstr "Script execution" + +#: ../../configuration/highavailability/index.rst:299 +msgid "Scripting" +msgstr "Scripting" + +#: ../../configuration/nat/nat44.rst:652 +msgid "Second scenario: apply source NAT for all outgoing connections from LAN 10.0.0.0/8, using 3 public addresses and equal distribution. We will generate the hash randomly." +msgstr "Second scenario: apply source NAT for all outgoing connections from LAN 10.0.0.0/8, using 3 public addresses and equal distribution. We will generate the hash randomly." + +#: ../../configuration/vpn/sstp.rst:235 +msgid "Secret for Dynamic Authorization Extension server (DM/CoA)" +msgstr "Secret for Dynamic Authorization Extension server (DM/CoA)" + +#: ../../configuration/interfaces/wireless.rst:334 +msgid "Security" +msgstr "Security" + +#: ../../configuration/system/syslog.rst:120 +#: ../../configuration/system/syslog.rst:132 +msgid "Security/authentication messages" +msgstr "Security/authentication messages" + +#: ../../configuration/system/ip.rst:52 +msgid "See below the different parameters available for the IPv4 **show** command:" +msgstr "See below the different parameters available for the IPv4 **show** command:" + +#: ../../configuration/protocols/segment-routing.rst:5 +msgid "Segment Routing" +msgstr "Segment Routing" + +#: ../../configuration/protocols/segment-routing.rst:7 +msgid "Segment Routing (SR) is a network architecture that is similar to source-routing . In this architecture, the ingress router adds a list of segments, known as SIDs, to the packet as it enters the network. These segments represent different portions of the network path that the packet will take." +msgstr "Segment Routing (SR) is a network architecture that is similar to source-routing . In this architecture, the ingress router adds a list of segments, known as SIDs, to the packet as it enters the network. These segments represent different portions of the network path that the packet will take." + +#: ../../configuration/protocols/segment-routing.rst:18 +msgid "Segment Routing can be applied to an existing MPLS-based data plane and defines a control plane network architecture. In MPLS networks, segments are encoded as MPLS labels and are added at the ingress router. These MPLS labels are then exchanged and populated by Interior Gateway Protocols (IGPs) like IS-IS or OSPF which are running on most ISPs." +msgstr "Segment Routing can be applied to an existing MPLS-based data plane and defines a control plane network architecture. In MPLS networks, segments are encoded as MPLS labels and are added at the ingress router. These MPLS labels are then exchanged and populated by Interior Gateway Protocols (IGPs) like IS-IS or OSPF which are running on most ISPs." + +#: ../../configuration/protocols/segment-routing.rst:37 +msgid "Segment routing (SR) is used by the IGP protocols to interconnect network devices, below configuration shows how to enable SR on IS-IS:" +msgstr "Segment routing (SR) is used by the IGP protocols to interconnect network devices, below configuration shows how to enable SR on IS-IS:" + +#: ../../configuration/protocols/segment-routing.rst:122 +msgid "Segment routing (SR) is used by the IGP protocols to interconnect network devices, below configuration shows how to enable SR on OSPF:" +msgstr "Segment routing (SR) is used by the IGP protocols to interconnect network devices, below configuration shows how to enable SR on OSPF:" + +#: ../../configuration/protocols/segment-routing.rst:25 +msgid "Segment routing defines a control plane network architecture and can be applied to an existing MPLS based dataplane. In the MPLS networks, segments are encoded as MPLS labels and are imposed at the ingress router. MPLS labels are exchanged and populated by IGPs like IS-IS.Segment Routing as per RFC8667 for MPLS dataplane. It supports IPv4, IPv6 and ECMP and has been tested against Cisco & Juniper routers.however,this deployment is still EXPERIMENTAL for FRR." +msgstr "Segment routing defines a control plane network architecture and can be applied to an existing MPLS based dataplane. In the MPLS networks, segments are encoded as MPLS labels and are imposed at the ingress router. MPLS labels are exchanged and populated by IGPs like IS-IS.Segment Routing as per RFC8667 for MPLS dataplane. It supports IPv4, IPv6 and ECMP and has been tested against Cisco & Juniper routers.however,this deployment is still EXPERIMENTAL for FRR." + +#: ../../configuration/interfaces/macsec.rst:34 +msgid "Select cipher suite used for cryptographic operations. This setting is mandatory." +msgstr "Select cipher suite used for cryptographic operations. This setting is mandatory." + +#: ../../configuration/vrf/index.rst:466 +msgid "Select how labels are allocated in the given VRF. By default, the per-vrf mode is selected, and one label is used for all prefixes from the VRF. The per-nexthop will use a unique label for all prefixes that are reachable via the same nexthop." +msgstr "Select how labels are allocated in the given VRF. By default, the per-vrf mode is selected, and one label is used for all prefixes from the VRF. The per-nexthop will use a unique label for all prefixes that are reachable via the same nexthop." + +#: ../../configuration/vpn/sstp.rst:30 +msgid "Self Signed CA" +msgstr "Self Signed CA" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:140 +msgid "Send a Proxy Protocol version 1 header (text format)" +msgstr "Send a Proxy Protocol version 1 header (text format)" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:145 +msgid "Send a Proxy Protocol version 2 header (binary format)" +msgstr "Send a Proxy Protocol version 2 header (binary format)" + +#: ../../configuration/service/dns.rst:30 +msgid "Send all DNS queries to the IPv4/IPv6 DNS server specified under `<address>` on optional port specified under `<port>`. The port defaults to 53. You can configure multiple nameservers here." +msgstr "Send all DNS queries to the IPv4/IPv6 DNS server specified under `<address>` on optional port specified under `<port>`. The port defaults to 53. You can configure multiple nameservers here." + +#: ../../configuration/interfaces/wireless.rst:57 +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 "Send empty SSID in beacons and ignore probe request frames that do not specify full SSID, i.e., require stations to know SSID." + +#: ../../configuration/system/console.rst:5 +msgid "Serial Console" +msgstr "Serial Console" + +#: ../../configuration/service/console-server.rst:11 +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 "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)." + +#: ../../configuration/interfaces/openvpn.rst:325 +#: ../../configuration/vpn/sstp.rst:199 +msgid "Server" +msgstr "Server" + +#: ../../configuration/service/tftp-server.rst:74 +msgid "Server:" +msgstr "Server:" + +#: ../../configuration/pki/index.rst:210 +msgid "Server Certificate" +msgstr "Server Certificate" + +#: ../../configuration/vpn/openconnect.rst:45 +msgid "Server Configuration" +msgstr "Server Configuration" + +#: ../../configuration/interfaces/openvpn.rst:588 +msgid "Server Side" +msgstr "Server Side" + +#: ../../configuration/service/ipoe-server.rst:156 +msgid "Server configuration" +msgstr "Server configuration" + +#: ../../configuration/service/https.rst:50 +msgid "Server names for virtual hosts it can be exact, wildcard or regex." +msgstr "Server names for virtual hosts it can be exact, wildcard or regex." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:21 +#: ../../configuration/service/index.rst:3 +msgid "Service" +msgstr "Service" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:16 +msgid "Service configuration is responsible for binding to a specific port, while the backend configuration determines the type of load balancing to be applied and specifies the real servers to be utilized." +msgstr "Service configuration is responsible for binding to a specific port, while the backend configuration determines the type of load balancing to be applied and specifies the real servers to be utilized." + +#: ../../configuration/protocols/bfd.rst:26 +msgid "Set BFD peer IPv4 address or IPv6 address" +msgstr "Set BFD peer IPv4 address or IPv6 address" + +#: ../../configuration/policy/route-map.rst:51 +msgid "Set BGP community-list to exactly match." +msgstr "Set BGP community-list to exactly match." + +#: ../../configuration/policy/route-map.rst:318 +msgid "Set BGP local preference attribute." +msgstr "Set BGP local preference attribute." + +#: ../../configuration/policy/route-map.rst:334 +msgid "Set BGP origin code." +msgstr "Set BGP origin code." + +#: ../../configuration/policy/route-map.rst:339 +msgid "Set BGP originator ID attribute." +msgstr "Set BGP originator ID attribute." + +#: ../../configuration/policy/route-map.rst:357 +msgid "Set BGP weight attribute" +msgstr "Set BGP weight attribute" + +#: ../../configuration/nat/nat44.rst:176 +msgid "Set DNAT rule 20 to only NAT UDP packets" +msgstr "Set DNAT rule 20 to only NAT UDP packets" + +#: ../../configuration/policy/route.rst:144 +msgid "Set IPSec inbound match criterias, where:" +msgstr "Set IPSec inbound match criterias, where:" + +#: ../../configuration/policy/route.rst:123 +msgid "Set IP fragment match, where:" +msgstr "Set IP fragment match, where:" + +#: ../../configuration/policy/route-map.rst:329 +msgid "Set OSPF external metric-type." +msgstr "Set OSPF external metric-type." + +#: ../../configuration/nat/nat44.rst:175 +msgid "Set SNAT rule 20 to only NAT TCP and UDP packets" +msgstr "Set SNAT rule 20 to only NAT TCP and UDP packets" + +#: ../../configuration/nat/nat44.rst:189 +msgid "Set SNAT rule 20 to only NAT packets arriving from the 192.0.2.0/24 network" +msgstr "Set SNAT rule 20 to only NAT packets arriving from the 192.0.2.0/24 network" + +#: ../../configuration/nat/nat44.rst:191 +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 "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" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:46 +msgid "Set SSL certeficate <name> for service <name>" +msgstr "Set SSL certeficate <name> for service <name>" + +#: ../../configuration/firewall/general.rst:1271 +msgid "Set TCP-MSS (maximum segment size) for the connection" +msgstr "Set TCP-MSS (maximum segment size) for the connection" + +#: ../../configuration/service/dns.rst:267 +msgid "Set TTL to 300 seconds" +msgstr "Set TTL to 300 seconds" + +#: ../../configuration/interfaces/vti.rst:7 +msgid "Set Virtual Tunnel Interface" +msgstr "Set Virtual Tunnel Interface" + +#: ../../configuration/container/index.rst:54 +msgid "Set a container description" +msgstr "Set a container description" + +#: ../../configuration/system/conntrack.rst:114 +msgid "Set a destination and/or source port. Accepted input:" +msgstr "Set a destination and/or source port. Accepted input:" + +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +#: ../../_include/interface-description.txt:4 +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 "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." + +#: ../../configuration/system/login.rst:385 +msgid "Set a limit on the maximum number of concurrent logged-in users on the system." +msgstr "Set a limit on the maximum number of concurrent logged-in users on the system." + +#: ../../configuration/firewall/zone.rst:79 +msgid "Set a meaningful description." +msgstr "Set a meaningful description." + +#: ../../configuration/service/https.rst:18 +msgid "Set a named api key. Every key has the same, full permissions on the system." +msgstr "Set a named api key. Every key has the same, full permissions on the system." + +#: ../../configuration/system/conntrack.rst:92 +msgid "Set a rule description." +msgstr "Set a rule description." + +#: ../../configuration/policy/route.rst:254 +msgid "Set a specific connection mark." +msgstr "Set a specific connection mark." + +#: ../../configuration/policy/route.rst:264 +msgid "Set a specific packet mark." +msgstr "Set a specific packet mark." + +#: ../../configuration/policy/route-map.rst:25 +msgid "Set action for the route-map policy." +msgstr "Set action for the route-map policy." + +#: ../../configuration/policy/as-path-list.rst:25 +#: ../../configuration/policy/community-list.rst:26 +#: ../../configuration/policy/extcommunity-list.rst:26 +#: ../../configuration/policy/large-community-list.rst:26 +msgid "Set action to take on entries matching this rule." +msgstr "Set action to take on entries matching this rule." + +#: ../../configuration/service/https.rst:79 +msgid "Set an API-KEY is the minimal configuration to get a working API Endpoint." +msgstr "Set an API-KEY is the minimal configuration to get a working API Endpoint." + +#: ../../configuration/vpn/sstp.rst:100 +msgid "Set authentication backend. The configured authentication backend is used for all queries." +msgstr "Set authentication backend. The configured authentication backend is used for all queries." + +#: ../../configuration/container/index.rst:117 +msgid "Set container capabilities or permissions." +msgstr "Set container capabilities or permissions." + +#: ../../configuration/highavailability/index.rst:247 +msgid "Set delay between gratuitous ARP messages sent on an interface." +msgstr "Set delay between gratuitous ARP messages sent on an interface." + +#: ../../configuration/highavailability/index.rst:255 +msgid "Set delay for second set of gratuitous ARPs after transition to MASTER." +msgstr "Set delay for second set of gratuitous ARPs after transition to MASTER." + +#: ../../configuration/policy/as-path-list.rst:21 +msgid "Set description for as-path-list policy." +msgstr "Set description for as-path-list policy." + +#: ../../configuration/policy/community-list.rst:21 +msgid "Set description for community-list policy." +msgstr "Set description for community-list policy." + +#: ../../configuration/policy/extcommunity-list.rst:21 +msgid "Set description for extcommunity-list policy." +msgstr "Set description for extcommunity-list policy." + +#: ../../configuration/policy/large-community-list.rst:21 +msgid "Set description for large-community-list policy." +msgstr "Set description for large-community-list policy." + +#: ../../configuration/policy/as-path-list.rst:29 +#: ../../configuration/policy/community-list.rst:30 +#: ../../configuration/policy/extcommunity-list.rst:31 +#: ../../configuration/policy/large-community-list.rst:31 +msgid "Set description for rule." +msgstr "Set description for rule." + +#: ../../configuration/policy/prefix-list.rst:67 +msgid "Set description for rule in IPv6 prefix-list." +msgstr "Set description for rule in IPv6 prefix-list." + +#: ../../configuration/policy/prefix-list.rst:35 +msgid "Set description for rule in the prefix-list." +msgstr "Set description for rule in the prefix-list." + +#: ../../configuration/policy/access-list.rst:54 +msgid "Set description for the IPv6 access list." +msgstr "Set description for the IPv6 access list." + +#: ../../configuration/policy/prefix-list.rst:58 +msgid "Set description for the IPv6 prefix-list policy." +msgstr "Set description for the IPv6 prefix-list policy." + +#: ../../configuration/policy/access-list.rst:25 +msgid "Set description for the access list." +msgstr "Set description for the access list." + +#: ../../configuration/policy/prefix-list.rst:27 +msgid "Set description for the prefix-list policy." +msgstr "Set description for the prefix-list policy." + +#: ../../configuration/policy/route-map.rst:21 +msgid "Set description for the route-map policy." +msgstr "Set description for the route-map policy." + +#: ../../configuration/policy/route-map.rst:37 +msgid "Set description for the rule in the route-map policy." +msgstr "Set description for the rule in the route-map policy." + +#: ../../configuration/protocols/bgp.rst:252 +msgid "Set description of the peer or peer group." +msgstr "Set description of the peer or peer group." + +#: ../../configuration/policy/local-route.rst:24 +#: ../../configuration/policy/local-route.rst:43 +msgid "Set destination address or prefix to match." +msgstr "Set destination address or prefix to match." + +#: ../../configuration/policy/route-map.rst:323 +msgid "Set destination routing protocol metric. Add or subtract metric, or set metric value." +msgstr "Set destination routing protocol metric. Add or subtract metric, or set metric value." + +#: ../../configuration/service/dhcp-relay.rst:141 +msgid "Set eth1 to be the listening interface for the DHCPv6 relay." +msgstr "Set eth1 to be the listening interface for the DHCPv6 relay." + +#: ../../configuration/system/task-scheduler.rst:28 +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 "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." + +#: ../../configuration/policy/route-map.rst:251 +msgid "Set extcommunity bandwidth" +msgstr "Set extcommunity bandwidth" + +#: ../../configuration/interfaces/wireless.rst:229 +msgid "Set if antenna pattern does not change during the lifetime of an association" +msgstr "Set if antenna pattern does not change during the lifetime of an association" + +#: ../../configuration/policy/local-route.rst:28 +#: ../../configuration/policy/local-route.rst:47 +msgid "Set inbound interface to match." +msgstr "Set inbound interface to match." + +#: ../../configuration/firewall/zone.rst:65 +msgid "Set interfaces to a zone. A zone can have multiple interfaces. But an interface can only be a member in one zone." +msgstr "Set interfaces to a zone. A zone can have multiple interfaces. But an interface can only be a member in one zone." + +#: ../../configuration/protocols/bgp.rst:42 +msgid "Set local :abbr:`ASN (Autonomous System Number)` that this router represents. This is a a mandatory option!" +msgstr "Set local :abbr:`ASN (Autonomous System Number)` that this router represents. This is a a mandatory option!" + +#: ../../configuration/protocols/bgp.rst:179 +msgid "Set local autonomous system number that this router represents. This is a mandatory option!" +msgstr "Set local autonomous system number that this router represents. This is a mandatory option!" + +#: ../../configuration/policy/route.rst:47 +msgid "Set match criteria based on connection mark." +msgstr "Set match criteria based on connection mark." + +#: ../../configuration/policy/route.rst:94 +msgid "Set match criteria based on destination port, where <match_criteria> could be:" +msgstr "Set match criteria based on destination port, where <match_criteria> could be:" + +#: ../../configuration/policy/route.rst:200 +msgid "Set match criteria based on session state." +msgstr "Set match criteria based on session state." + +#: ../../configuration/policy/route.rst:87 +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 "Set match criteria based on source or destination groups, where <text> would be the group name/identifier. Prepend character '!' for inverted matching criteria." + +#: ../../configuration/policy/route.rst:58 +msgid "Set match criteria based on source or destination ipv4|ipv6 address, where <match_criteria> could be:" +msgstr "Set match criteria based on source or destination ipv4|ipv6 address, where <match_criteria> could be:" + +#: ../../configuration/policy/route.rst:205 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:62 +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 "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." + +#: ../../configuration/policy/route.rst:157 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:162 +msgid "Set maximum hop count before packets are discarded, default: 10" +msgstr "Set maximum hop count before packets are discarded, default: 10" + +#: ../../configuration/policy/route.rst:152 +msgid "Set maximum number of packets to alow in excess of rate." +msgstr "Set maximum number of packets to alow in excess of rate." + +#: ../../configuration/highavailability/index.rst:265 +msgid "Set minimum time interval for refreshing gratuitous ARPs while MASTER." +msgstr "Set minimum time interval for refreshing gratuitous ARPs while MASTER." + +#: ../../configuration/highavailability/index.rst:285 +msgid "Set number of gratuitous ARP messages to send at a time after transition to MASTER." +msgstr "Set number of gratuitous ARP messages to send at a time after transition to MASTER." + +#: ../../configuration/highavailability/index.rst:275 +msgid "Set number of gratuitous ARP messages to send at a time while MASTER." +msgstr "Set number of gratuitous ARP messages to send at a time while MASTER." + +#: ../../configuration/protocols/ospf.rst:413 +#: ../../configuration/protocols/ospf.rst:1157 +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 "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." + +#: ../../configuration/protocols/ospf.rst:397 +#: ../../configuration/protocols/ospf.rst:1149 +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 "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." + +#: ../../configuration/policy/route.rst:274 +msgid "Set packet modifications: Explicitly set TCP Maximum segment size value." +msgstr "Set packet modifications: Explicitly set TCP Maximum segment size value." + +#: ../../configuration/policy/route.rst:259 +msgid "Set packet modifications: Packet Differentiated Services Codepoint (DSCP)" +msgstr "Set packet modifications: Packet Differentiated Services Codepoint (DSCP)" + +#: ../../configuration/policy/route.rst:191 +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 "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)." + +#: ../../configuration/policy/route-map.rst:348 +msgid "Set prefixes to table." +msgstr "Set prefixes to table." + +#: ../../configuration/system/proxy.rst:13 +msgid "Set proxy for all connections initiated by VyOS, including HTTP, HTTPS, and FTP (anonymous ftp)." +msgstr "Set proxy for all connections initiated by VyOS, including HTTP, HTTPS, and FTP (anonymous ftp)." + +#: ../../configuration/policy/route-map.rst:260 +msgid "Set route target value in format ``<0-65535:0-4294967295>`` or ``<IP:0-65535>``." +msgstr "Set route target value in format ``<0-65535:0-4294967295>`` or ``<IP:0-65535>``." + +#: ../../configuration/policy/local-route.rst:16 +#: ../../configuration/policy/local-route.rst:35 +msgid "Set routing table to forward packet to." +msgstr "Set routing table to forward packet to." + +#: ../../configuration/policy/route.rst:247 +msgid "Set rule action to drop." +msgstr "Set rule action to drop." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:26 +msgid "Set service to bind on IP address, by default listen on any IPv4 and IPv6" +msgstr "Set service to bind on IP address, by default listen on any IPv4 and IPv6" + +#: ../../configuration/policy/route-map.rst:265 +msgid "Set site of origin value in format ``<0-65535:0-4294967295>`` or ``<IP:0-65535>``." +msgstr "Set site of origin value in format ``<0-65535:0-4294967295>`` or ``<IP:0-65535>``." + +#: ../../configuration/policy/index.rst:18 +msgid "Set some attributes (like AS PATH or Community value) to advertised routes to neighbors." +msgstr "Set some attributes (like AS PATH or Community value) to advertised routes to neighbors." + +#: ../../configuration/policy/index.rst:17 +msgid "Set some metric to routes learned from a particular neighbor." +msgstr "Set some metric to routes learned from a particular neighbor." + +#: ../../configuration/interfaces/l2tpv3.rst:112 +msgid "Set source-address to your local IP (LAN)." +msgstr "Set source-address to your local IP (LAN)." + +#: ../../configuration/policy/route-map.rst:344 +msgid "Set source IP/IPv6 address for route." +msgstr "Set source IP/IPv6 address for route." + +#: ../../configuration/policy/local-route.rst:20 +#: ../../configuration/policy/local-route.rst:39 +msgid "Set source address or prefix to match." +msgstr "Set source address or prefix to match." + +#: ../../configuration/policy/route-map.rst:352 +msgid "Set tag value for routing protocol." +msgstr "Set tag value for routing protocol." + +#: ../../configuration/service/dns.rst:50 +msgid "Set the \"recursion desired\" bit in requests to the upstream nameserver." +msgstr "Set the \"recursion desired\" bit in requests to the upstream nameserver." + +#: ../../configuration/policy/route-map.rst:290 +#: ../../configuration/policy/route-map.rst:303 +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 "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." + +#: ../../configuration/interfaces/l2tpv3.rst:52 +msgid "Set the IP address of the local interface to be used for the tunnel." +msgstr "Set the IP address of the local interface to be used for the tunnel." + +#: ../../configuration/interfaces/l2tpv3.rst:59 +msgid "Set the IP address of the remote peer. It may be specified as an IPv4 address or an IPv6 address." +msgstr "Set the IP address of the remote peer. It may be specified as an IPv4 address or an IPv6 address." + +#: ../../configuration/firewall/general.rst:162 +#: ../../configuration/firewall/general-legacy.rst:112 +msgid "Set the IPv4 source validation mode. The following system parameter will be altered:" +msgstr "Set the IPv4 source validation mode. The following system parameter will be altered:" + +#: ../../configuration/protocols/pim6.rst:62 +msgid "Set the MLD last member query count. The default value is 2." +msgstr "Set the MLD last member query count. The default value is 2." + +#: ../../configuration/protocols/pim6.rst:66 +msgid "Set the MLD last member query interval in milliseconds (100-6553500). The default value is 1000 milliseconds." +msgstr "Set the MLD last member query interval in milliseconds (100-6553500). The default value is 1000 milliseconds." + +#: ../../configuration/protocols/pim6.rst:70 +msgid "Set the MLD query response timeout in milliseconds (100-6553500). The default value is 10000 milliseconds." +msgstr "Set the MLD query response timeout in milliseconds (100-6553500). The default value is 10000 milliseconds." + +#: ../../configuration/protocols/pim6.rst:74 +msgid "Set the MLD version used on this interface. The default value is 2." +msgstr "Set the MLD version used on this interface. The default value is 2." + +#: ../../configuration/protocols/segment-routing.rst:85 +#: ../../configuration/protocols/segment-routing.rst:163 +msgid "Set the Maximum Stack Depth supported by the router. The value depend of the MPLS dataplane." +msgstr "Set the Maximum Stack Depth supported by the router. The value depend of the MPLS dataplane." + +#: ../../configuration/protocols/segment-routing.rst:56 +#: ../../configuration/protocols/segment-routing.rst:134 +msgid "Set the Segment Routing Global Block i.e. the label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535." +msgstr "Set the Segment Routing Global Block i.e. the label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535." + +#: ../../configuration/protocols/segment-routing.rst:63 +#: ../../configuration/protocols/segment-routing.rst:141 +msgid "Set the Segment Routing Global Block i.e. the low label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535." +msgstr "Set the Segment Routing Global Block i.e. the low label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535." + +#: ../../configuration/protocols/segment-routing.rst:70 +#: ../../configuration/protocols/segment-routing.rst:148 +msgid "Set the Segment Routing Local Block i.e. the label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535.Segment Routing Local Block, The negative command always unsets both." +msgstr "Set the Segment Routing Local Block i.e. the label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535.Segment Routing Local Block, The negative command always unsets both." + +#: ../../configuration/protocols/segment-routing.rst:78 +#: ../../configuration/protocols/segment-routing.rst:156 +msgid "Set the Segment Routing Local Block i.e. the low label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535.Segment Routing Local Block, The negative command always unsets both." +msgstr "Set the Segment Routing Local Block i.e. the low label range used by MPLS to store label in the MPLS FIB for Prefix SID. Note that the block size may not exceed 65535.Segment Routing Local Block, The negative command always unsets both." + +#: ../../configuration/service/ssh.rst:106 +msgid "Set the ``sshd`` log level. The default is ``info``." +msgstr "Set the ``sshd`` log level. The default is ``info``." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:130 +msgid "Set the address of the backend port" +msgstr "Set the address of the backend port" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:124 +msgid "Set the address of the backend server to which the incoming traffic will be forwarded" +msgstr "Set the address of the backend server to which the incoming traffic will be forwarded" + +#: ../../configuration/highavailability/index.rst:295 +msgid "Set the default VRRP version to use. This defaults to 2, but IPv6 instances will always use version 3." +msgstr "Set the default VRRP version to use. This defaults to 2, but IPv6 instances will always use version 3." + +#: ../../configuration/interfaces/macsec.rst:56 +msgid "Set the device's transmit (TX) key. This key must be a hex string that is 16-bytes (GCM-AES-128) or 32-bytes (GCM-AES-256)." +msgstr "Set the device's transmit (TX) key. This key must be a hex string that is 16-bytes (GCM-AES-128) or 32-bytes (GCM-AES-256)." + +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +#: ../../_include/interface-dhcp-options.txt:55 +msgid "Set the distance for the default gateway sent by the DHCP server." +msgstr "Set the distance for the default gateway sent by the DHCP server." + +#: ../../configuration/interfaces/pppoe.rst:138 +msgid "Set the distance for the default gateway sent by the PPPoE server." +msgstr "Set the distance for the default gateway sent by the PPPoE server." + +#: ../../configuration/interfaces/sstp-client.rst:60 +msgid "Set the distance for the default gateway sent by the SSTP server." +msgstr "Set the distance for the default gateway sent by the SSTP server." + +#: ../../configuration/interfaces/l2tpv3.rst:45 +msgid "Set the encapsulation type of the tunnel. Valid values for encapsulation are: udp, ip." +msgstr "Set the encapsulation type of the tunnel. Valid values for encapsulation are: udp, ip." + +#: ../../configuration/firewall/general-legacy.rst:136 +msgid "Set the global setting for an established connection." +msgstr "Set the global setting for an established connection." + +#: ../../configuration/firewall/general-legacy.rst:142 +msgid "Set the global setting for invalid packets." +msgstr "Set the global setting for invalid packets." + +#: ../../configuration/firewall/general-legacy.rst:148 +msgid "Set the global setting for related connections." +msgstr "Set the global setting for related connections." + +#: ../../configuration/service/https.rst:28 +msgid "Set the listen port of the local API, this has no effect on the webserver. The default is port 8080" +msgstr "Set the listen port of the local API, this has no effect on the webserver. The default is port 8080" + +#: ../../configuration/service/dhcp-relay.rst:57 +msgid "Set the maximum hop `<count>` before packets are discarded. Range 0...255, default 10." +msgstr "Set the maximum hop `<count>` before packets are discarded. Range 0...255, default 10." + +#: ../../configuration/interfaces/wireless.rst:277 +msgid "Set the maximum length of A-MPDU pre-EOF padding that the station can receive" +msgstr "Set the maximum length of A-MPDU pre-EOF padding that the station can receive" + +#: ../../configuration/system/conntrack.rst:147 +msgid "Set the maximum number of TCP half-open connections." +msgstr "Set the maximum number of TCP half-open connections." + +#: ../../_include/interface-eapol.txt:12 +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 "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." + +#: ../../_include/interface-eapol.txt:29 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:148 +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 "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" + +#: ../../configuration/policy/route-map.rst:284 +msgid "Set the next-hop as unchanged. Pass through the route-map without changing its value" +msgstr "Set the next-hop as unchanged. Pass through the route-map without changing its value" + +#: ../../configuration/system/conntrack.rst:157 +msgid "Set the number of TCP maximum retransmit attempts." +msgstr "Set the number of TCP maximum retransmit attempts." + +#: ../../configuration/loadbalancing/wan.rst:148 +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 "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." + +#: ../../configuration/system/login.rst:84 +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 "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." + +#: ../../configuration/service/console-server.rst:45 +msgid "Set the parity option for the console. If unset this will default to none." +msgstr "Set the parity option for the console. If unset this will default to none." + +#: ../../configuration/interfaces/macsec.rst:61 +msgid "Set the peer's MAC address" +msgstr "Set the peer's MAC address" + +#: ../../configuration/interfaces/macsec.rst:65 +msgid "Set the peer's key used to receive (RX) traffic" +msgstr "Set the peer's key used to receive (RX) traffic" + +#: ../../configuration/interfaces/l2tpv3.rst:70 +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 "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." + +#: ../../configuration/container/index.rst:98 +msgid "Set the restart behavior of the container." +msgstr "Set the restart behavior of the container." + +#: ../../configuration/policy/route.rst:269 +msgid "Set the routing table to forward packet with." +msgstr "Set the routing table to forward packet with." + +#: ../../configuration/interfaces/l2tpv3.rst:64 +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 "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." + +#: ../../configuration/system/conntrack.rst:31 +msgid "Set the size of the hash table. The connection tracking hash table makes searching the connection tracking table faster. The hash table uses “buckets” to record entries in the connection tracking table." +msgstr "Set the size of the hash table. The connection tracking hash table makes searching the connection tracking table faster. The hash table uses “buckets” to record entries in the connection tracking table." + +#: ../../configuration/service/broadcast-relay.rst:33 +msgid "Set the source IP of forwarded packets, otherwise original senders address is used." +msgstr "Set the source IP of forwarded packets, otherwise original senders address is used." + +#: ../../configuration/system/conntrack.rst:83 +msgid "Set the timeout in secounds for a protocol or state." +msgstr "Set the timeout in secounds for a protocol or state." + +#: ../../configuration/system/conntrack.rst:141 +msgid "Set the timeout in secounds for a protocol or state in a custom rule." +msgstr "Set the timeout in secounds for a protocol or state in a custom rule." + +#: ../../configuration/interfaces/l2tpv3.rst:76 +#: ../../configuration/interfaces/l2tpv3.rst:81 +msgid "Set the tunnel id, which is a 32-bit integer value. Uniquely identifies the tunnel into which the session will be created." +msgstr "Set the tunnel id, which is a 32-bit integer value. Uniquely identifies the tunnel into which the session will be created." + +#: ../../configuration/firewall/general.rst:1275 +msgid "Set the window scale factor for TCP window scaling" +msgstr "Set the window scale factor for TCP window scaling" + +#: ../../configuration/system/login.rst:124 +msgid "Set window of concurrently valid codes." +msgstr "Set window of concurrently valid codes." + +#: ../../configuration/container/index.rst:16 +msgid "Sets the image name in the hub registry" +msgstr "Sets the image name in the hub registry" + +#: ../../configuration/interfaces/vxlan.rst:299 +msgid "Sets the interface to listen for multicast packets on. Could be a loopback, not yet tested." +msgstr "Sets the interface to listen for multicast packets on. Could be a loopback, not yet tested." + +#: ../../configuration/service/webproxy.rst:111 +msgid "Sets the listening port for a listening address. This overrides the default port of 3128 on the specific listen address." +msgstr "Sets the listening port for a listening address. This overrides the default port of 3128 on the specific listen address." + +#: ../../configuration/interfaces/vxlan.rst:306 +msgid "Sets the unique id for this vxlan-interface. Not sure how it correlates with multicast-address." +msgstr "Sets the unique id for this vxlan-interface. Not sure how it correlates with multicast-address." + +#: ../../configuration/highavailability/index.rst:96 +msgid "Setting VRRP group priority" +msgstr "Setting VRRP group priority" + +#: ../../configuration/service/dhcp-server.rst:264 +msgid "Setting name" +msgstr "Setting name" + +#: ../../configuration/vpn/dmvpn.rst:227 +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 "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)." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:78 +msgid "Setting up IPSec:" +msgstr "Setting up IPSec:" + +#: ../../configuration/interfaces/openvpn.rst:132 +msgid "Setting up OpenVPN" +msgstr "Setting up OpenVPN" + +#: ../../configuration/interfaces/openvpn.rst:76 +msgid "Setting up a full-blown PKI with a CA certificate would arguably defeat the purpose of site-to-site OpenVPN, since its main goal is supposed to be configuration simplicity, compared to server setups that need to support multiple clients." +msgstr "Setting up a full-blown PKI with a CA certificate would arguably defeat the purpose of site-to-site OpenVPN, since its main goal is supposed to be configuration simplicity, compared to server setups that need to support multiple clients." + +#: ../../configuration/interfaces/openvpn.rst:74 +msgid "Setting up certificates" +msgstr "Setting up certificates" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:19 +msgid "Setting up certificates:" +msgstr "Setting up certificates:" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:113 +msgid "Setting up tunnel:" +msgstr "Setting up tunnel:" + +#: ../../configuration/service/dhcp-server.rst:432 +msgid "Setup DHCP failover for network 192.0.2.0/24" +msgstr "Setup DHCP failover for network 192.0.2.0/24" + +#: ../../configuration/system/login.rst:34 +msgid "Setup encrypted password for given username. This is useful for transferring a hashed password from system to system." +msgstr "Setup encrypted password for given username. This is useful for transferring a hashed password from system to system." + +#: ../../configuration/system/login.rst:262 +msgid "Setup the `<timeout>` in seconds when querying the RADIUS server." +msgstr "Setup the `<timeout>` in seconds when querying the RADIUS server." + +#: ../../configuration/system/login.rst:331 +msgid "Setup the `<timeout>` in seconds when querying the TACACS server." +msgstr "Setup the `<timeout>` in seconds when querying the TACACS server." + +#: ../../configuration/service/dns.rst:314 +msgid "Setup the dynamic DNS hostname `<hostname>` associated with the DynDNS provider identified by `<service>` when the IP address on interface `<interface>` changes." +msgstr "Setup the dynamic DNS hostname `<hostname>` associated with the DynDNS provider identified by `<service>` when the IP address on interface `<interface>` changes." + +#: ../../configuration/system/option.rst:31 +msgid "Several commands utilize cURL to initiate transfers. Configure the local source IPv4/IPv6 address used for all cURL operations." +msgstr "Several commands utilize cURL to initiate transfers. Configure the local source IPv4/IPv6 address used for all cURL operations." + +#: ../../configuration/system/option.rst:36 +msgid "Several commands utilize curl to initiate transfers. Configure the local source interface used for all CURL operations." +msgstr "Several commands utilize curl to initiate transfers. Configure the local source interface used for all CURL operations." + +#: ../../configuration/system/syslog.rst:167 +msgid "Severity" +msgstr "Severity" + +#: ../../configuration/system/syslog.rst:164 +msgid "Severity Level" +msgstr "Severity Level" + +#: ../../configuration/trafficpolicy/index.rst:1017 +msgid "Shaper" +msgstr "Shaper" + +#: ../../configuration/interfaces/wireless.rst:282 +msgid "Short GI capabilities" +msgstr "Short GI capabilities" + +#: ../../configuration/interfaces/wireless.rst:204 +msgid "Short GI capabilities for 20 and 40 MHz" +msgstr "Short GI capabilities for 20 and 40 MHz" + +#: ../../configuration/trafficpolicy/index.rst:923 +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 "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." + +#: ../../configuration/vrf/index.rst:486 +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 "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." + +#: ../../configuration/protocols/bgp.rst:953 +#: ../../configuration/protocols/mpls.rst:225 +msgid "Show" +msgstr "Show" + +#: ../../configuration/service/dhcp-server.rst:516 +msgid "Show DHCP server daemon log file" +msgstr "Show DHCP server daemon log file" + +#: ../../configuration/service/dhcp-server.rst:736 +msgid "Show DHCPv6 server daemon log file" +msgstr "Show DHCPv6 server daemon log file" + +#: ../../configuration/firewall/general.rst:1482 +#: ../../configuration/firewall/general-legacy.rst:965 +msgid "Show Firewall log" +msgstr "Show Firewall log" + +#: ../../configuration/service/lldp.rst:138 +msgid "Show LLDP neighbors connected via interface `<interface>`." +msgstr "Show LLDP neighbors connected via interface `<interface>`." + +#: ../../configuration/loadbalancing/wan.rst:271 +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 "Show WAN load balancer information including test types and targets. A character at the start of each line depicts the state of the test" + +#: ../../configuration/interfaces/wwan.rst:200 +msgid "Show WWAN module IMEI." +msgstr "Show WWAN module IMEI." + +#: ../../configuration/interfaces/wwan.rst:211 +msgid "Show WWAN module IMSI." +msgstr "Show WWAN module IMSI." + +#: ../../configuration/interfaces/wwan.rst:229 +msgid "Show WWAN module MSISDN." +msgstr "Show WWAN module MSISDN." + +#: ../../configuration/interfaces/wwan.rst:263 +msgid "Show WWAN module SIM card information." +msgstr "Show WWAN module SIM card information." + +#: ../../configuration/interfaces/wwan.rst:184 +msgid "Show WWAN module firmware." +msgstr "Show WWAN module firmware." + +#: ../../configuration/interfaces/wwan.rst:169 +msgid "Show WWAN module hardware capabilities." +msgstr "Show WWAN module hardware capabilities." + +#: ../../configuration/interfaces/wwan.rst:238 +msgid "Show WWAN module hardware revision." +msgstr "Show WWAN module hardware revision." + +#: ../../configuration/interfaces/wwan.rst:220 +msgid "Show WWAN module model." +msgstr "Show WWAN module model." + +#: ../../configuration/interfaces/wwan.rst:247 +msgid "Show WWAN module signal strength." +msgstr "Show WWAN module signal strength." + +#: ../../configuration/container/index.rst:163 +msgid "Show a list available container networks" +msgstr "Show a list available container networks" + +#: ../../configuration/pki/index.rst:259 +msgid "Show a list of installed :abbr:`CA (Certificate Authority)` certificates." +msgstr "Show a list of installed :abbr:`CA (Certificate Authority)` certificates." + +#: ../../configuration/pki/index.rst:294 +msgid "Show a list of installed :abbr:`CRLs (Certificate Revocation List)`." +msgstr "Show a list of installed :abbr:`CRLs (Certificate Revocation List)`." + +#: ../../configuration/pki/index.rst:277 +msgid "Show a list of installed certificates" +msgstr "Show a list of installed certificates" + +#: ../../configuration/protocols/bfd.rst:98 +msgid "Show all BFD peers" +msgstr "Show all BFD peers" + +#: ../../configuration/interfaces/ethernet.rst:210 +msgid "Show available offloading functions on given `<interface>`" +msgstr "Show available offloading functions on given `<interface>`" + +#: ../../configuration/system/acceleration.rst:54 +msgid "Show binded qat device interrupts to certain core." +msgstr "Show binded qat device interrupts to certain core." + +#: ../../configuration/interfaces/bridge.rst:283 +msgid "Show bridge `<name>` fdb displays the current forwarding table:" +msgstr "Show bridge `<name>` fdb displays the current forwarding table:" + +#: ../../configuration/interfaces/bridge.rst:310 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:516 +#: ../../configuration/interfaces/dummy.rst:55 +#: ../../configuration/interfaces/ethernet.rst:136 +#: ../../configuration/interfaces/loopback.rst:45 +#: ../../configuration/interfaces/virtual-ethernet.rst:59 +msgid "Show brief interface information." +msgstr "Show brief interface information." + +#: ../../configuration/system/ipv6.rst:46 +msgid "Show commands" +msgstr "Show commands" + +#: ../../configuration/service/console-server.rst:80 +msgid "Show configured serial ports and their respective interface configuration." +msgstr "Show configured serial ports and their respective interface configuration." + +#: ../../configuration/loadbalancing/wan.rst:297 +msgid "Show connection data of load balanced traffic:" +msgstr "Show connection data of load balanced traffic:" + +#: ../../configuration/service/conntrack-sync.rst:132 +msgid "Show connection syncing external cache entries" +msgstr "Show connection syncing external cache entries" + +#: ../../configuration/service/conntrack-sync.rst:136 +msgid "Show connection syncing internal cache entries" +msgstr "Show connection syncing internal cache entries" + +#: ../../configuration/service/console-server.rst:89 +msgid "Show currently connected users." +msgstr "Show currently connected users." + +#: ../../configuration/protocols/segment-routing.rst:109 +msgid "Show detailed information about all learned Segment Routing Nodes" +msgstr "Show detailed information about all learned Segment Routing Nodes" + +#: ../../configuration/protocols/segment-routing.rst:113 +msgid "Show detailed information about prefix-sid and label learned" +msgstr "Show detailed information about prefix-sid and label learned" + +#: ../../configuration/interfaces/bonding.rst:548 +msgid "Show detailed information about the underlaying physical links on given bond `<interface>`." +msgstr "Show detailed information about the underlaying physical links on given bond `<interface>`." + +#: ../../configuration/interfaces/bonding.rst:531 +#: ../../configuration/interfaces/dummy.rst:67 +#: ../../configuration/interfaces/ethernet.rst:150 +#: ../../configuration/interfaces/pppoe.rst:269 +#: ../../configuration/interfaces/sstp-client.rst:121 +#: ../../configuration/interfaces/virtual-ethernet.rst:72 +#: ../../configuration/interfaces/wwan.rst:83 +msgid "Show detailed information on given `<interface>`" +msgstr "Show detailed information on given `<interface>`" + +#: ../../configuration/interfaces/loopback.rst:58 +msgid "Show detailed information on the given loopback interface `lo`." +msgstr "Show detailed information on the given loopback interface `lo`." + +#: ../../configuration/interfaces/wwan.rst:102 +msgid "Show detailed information summary on given `<interface>`" +msgstr "Show detailed information summary on given `<interface>`" + +#: ../../configuration/system/flow-accounting.rst:182 +msgid "Show flow accounting information for given `<interface>`." +msgstr "Show flow accounting information for given `<interface>`." + +#: ../../configuration/system/flow-accounting.rst:199 +msgid "Show flow accounting information for given `<interface>` for a specific host only." +msgstr "Show flow accounting information for given `<interface>` for a specific host only." + +#: ../../configuration/interfaces/wireguard.rst:376 +msgid "Show general information about specific WireGuard interface" +msgstr "Show general information about specific WireGuard interface" + +#: ../../configuration/interfaces/wireguard.rst:345 +msgid "Show info about the Wireguard service. It also shows the latest handshake." +msgstr "Show info about the Wireguard service. It also shows the latest handshake." + +#: ../../configuration/interfaces/ethernet.rst:169 +msgid "Show information about physical `<interface>`" +msgstr "Show information about physical `<interface>`" + +#: ../../configuration/container/index.rst:159 +msgid "Show logs from a given container" +msgstr "Show logs from a given container" + +#: ../../configuration/service/dhcp-server.rst:520 +msgid "Show logs from all DHCP client processes." +msgstr "Show logs from all DHCP client processes." + +#: ../../configuration/service/dhcp-server.rst:740 +msgid "Show logs from all DHCPv6 client processes." +msgstr "Show logs from all DHCPv6 client processes." + +#: ../../configuration/service/dhcp-server.rst:524 +msgid "Show logs from specific `interface` DHCP client process." +msgstr "Show logs from specific `interface` DHCP client process." + +#: ../../configuration/service/dhcp-server.rst:744 +msgid "Show logs from specific `interface` DHCPv6 client process." +msgstr "Show logs from specific `interface` DHCPv6 client process." + +#: ../../configuration/pki/index.rst:273 +msgid "Show only information for specified Certificate Authority." +msgstr "Show only information for specified Certificate Authority." + +#: ../../configuration/pki/index.rst:290 +msgid "Show only information for specified certificate." +msgstr "Show only information for specified certificate." + +#: ../../configuration/service/dhcp-server.rst:562 +#: ../../configuration/service/dhcp-server.rst:767 +msgid "Show only leases in the specified pool." +msgstr "Show only leases in the specified pool." + +#: ../../configuration/service/dhcp-server.rst:776 +msgid "Show only leases with the specified state. Possible states: abandoned, active, all, backup, expired, free, released, reset (default = active)" +msgstr "Show only leases with the specified state. Possible states: abandoned, active, all, backup, expired, free, released, reset (default = active)" + +#: ../../configuration/service/dhcp-server.rst:571 +msgid "Show only leases with the specified state. Possible states: all, active, free, expired, released, abandoned, reset, backup (default = active)" +msgstr "Show only leases with the specified state. Possible states: all, active, free, expired, released, abandoned, reset, backup (default = active)" + +#: ../../configuration/system/default-route.rst:29 +msgid "Show routing table entry for the default route." +msgstr "Show routing table entry for the default route." + +#: ../../configuration/interfaces/macsec.rst:142 +msgid "Show specific MACsec interface information" +msgstr "Show specific MACsec interface information" + +#: ../../configuration/vpn/site2site_ipsec.rst:217 +msgid "Show status of new setup:" +msgstr "Show status of new setup:" + +#: ../../configuration/service/dhcp-server.rst:547 +msgid "Show statuses of all active leases:" +msgstr "Show statuses of all active leases:" + +#: ../../configuration/service/dhcp-server.rst:532 +msgid "Show the DHCP server statistics:" +msgstr "Show the DHCP server statistics:" + +#: ../../configuration/service/dhcp-server.rst:543 +msgid "Show the DHCP server statistics for the specified pool." +msgstr "Show the DHCP server statistics for the specified pool." + +#: ../../configuration/service/console-server.rst:120 +msgid "Show the console server log." +msgstr "Show the console server log." + +#: ../../configuration/system/acceleration.rst:46 +msgid "Show the full config uploaded to the QAT device." +msgstr "Show the full config uploaded to the QAT device." + +#: ../../configuration/container/index.rst:151 +msgid "Show the list of all active containers." +msgstr "Show the list of all active containers." + +#: ../../configuration/container/index.rst:155 +msgid "Show the local container images." +msgstr "Show the local container images." + +#: ../../configuration/firewall/general.rst:1486 +#: ../../configuration/firewall/general-legacy.rst:969 +msgid "Show the logs of a specific Rule-Set." +msgstr "Show the logs of a specific Rule-Set." + +#: ../../configuration/protocols/failover.rst:75 +#: ../../configuration/protocols/failover.rst:101 +msgid "Show the route" +msgstr "Show the route" + +#: ../../configuration/interfaces/ethernet.rst:242 +msgid "Show transceiver information from plugin modules, e.g SFP+, QSFP" +msgstr "Show transceiver information from plugin modules, e.g SFP+, QSFP" + +#: ../../configuration/protocols/bfd.rst:179 +msgid "Showing BFD monitored static routes" +msgstr "Showing BFD monitored static routes" + +#: ../../configuration/service/dhcp-server.rst:752 +msgid "Shows status of all assigned leases:" +msgstr "Shows status of all assigned leases:" + +#: ../../configuration/system/acceleration.rst:62 +msgid "Side A:" +msgstr "Side A:" + +#: ../../configuration/system/acceleration.rst:87 +msgid "Side B:" +msgstr "Side B:" + +#: ../../configuration/interfaces/wwan.rst:312 +msgid "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" + +#: ../../configuration/interfaces/wwan.rst:313 +msgid "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" + +#: ../../configuration/interfaces/wwan.rst:314 +msgid "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" + +#: ../../configuration/interfaces/wwan.rst:315 +msgid "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" + +#: ../../configuration/vpn/site2site_ipsec.rst:397 +msgid "Similar combinations are applicable for the dead-peer-detection." +msgstr "Similar combinations are applicable for the dead-peer-detection." + +#: ../../configuration/protocols/babel.rst:190 +msgid "Simple Babel configuration using 2 nodes and redistributing connected interfaces." +msgstr "Simple Babel configuration using 2 nodes and redistributing connected interfaces." + +#: ../../configuration/protocols/rip.rst:241 +msgid "Simple RIP configuration using 2 nodes and redistributing connected interfaces." +msgstr "Simple RIP configuration using 2 nodes and redistributing connected interfaces." + +#: ../../configuration/vpn/openconnect.rst:156 +msgid "Simple setup with one user added and password authentication:" +msgstr "Simple setup with one user added and password authentication:" + +#: ../../configuration/protocols/ospf.rst:371 +msgid "Simple text password authentication is insecure and deprecated in favour of MD5 HMAC authentication." +msgstr "Simple text password authentication is insecure and deprecated in favour of MD5 HMAC authentication." + +#: ../../configuration/vpn/rsa-keys.rst:54 +msgid "Since both routers do not know their effective public addresses, we set the local-address of the peer to \"any\"." +msgstr "Since both routers do not know their effective public addresses, we set the local-address of the peer to \"any\"." + +#: ../../configuration/interfaces/openvpn.rst:395 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:151 +msgid "Since the RADIUS server would be a single point of failure, multiple RADIUS servers can be setup and will be used subsequentially." +msgstr "Since the RADIUS server would be a single point of failure, multiple RADIUS servers can be setup and will be used subsequentially." + +#: ../../configuration/service/mdns.rst:13 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:136 +msgid "Single VXLAN device (SVD)" +msgstr "Single VXLAN device (SVD)" + +#: ../../configuration/interfaces/openvpn.rst:39 +#: ../../configuration/vpn/site2site_ipsec.rst:4 +msgid "Site-to-Site" +msgstr "Site-to-Site" + +#: ../../configuration/vpn/site2site_ipsec.rst:6 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:47 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:15 +msgid "Site to Site VPN" +msgstr "Site to Site VPN" + +#: ../../configuration/interfaces/bonding.rst:47 +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 "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." + +#: ../../configuration/nat/nat44.rst:554 +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 "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." + +#: ../../configuration/service/snmp.rst:245 +msgid "SolarWinds" +msgstr "SolarWinds" + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:10 +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 "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." + +#: ../../configuration/system/proxy.rst:7 +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 "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`)." + +#: ../../configuration/vpn/l2tp.rst:159 +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 "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." + +#: ../../configuration/nat/nat44.rst:626 +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 "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." + +#: ../../configuration/firewall/general.rst:86 +#: ../../configuration/firewall/general-legacy.rst:38 +msgid "Some firewall settings are global and have an affect on the whole system." +msgstr "Some firewall settings are global and have an affect on the whole system." + +#: ../../configuration/trafficpolicy/index.rst:327 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:342 +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 "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." + +#: ../../configuration/system/proxy.rst:27 +msgid "Some proxys require/support the \"basic\" HTTP authentication scheme as per :rfc:`7617`, thus a password can be configured." +msgstr "Some proxys require/support the \"basic\" HTTP authentication scheme as per :rfc:`7617`, thus a password can be configured." + +#: ../../configuration/system/proxy.rst:22 +msgid "Some proxys require/support the \"basic\" HTTP authentication scheme as per :rfc:`7617`, thus a username can be configured." +msgstr "Some proxys require/support the \"basic\" HTTP authentication scheme as per :rfc:`7617`, thus a username can be configured." + +#: ../../configuration/interfaces/pppoe.rst:352 +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 "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:" + +#: ../../configuration/service/webproxy.rst:397 +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 "Some services don't work correctly when being handled via a web proxy. So sometimes it is useful to bypass a transparent proxy:" + +#: ../../configuration/interfaces/wireguard.rst:396 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:651 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:771 +msgid "Sort the output by the specified key. Possible keys: expires, iaid_duid, ip, last_comm, pool, remaining, state, type (default = ip)" +msgstr "Sort the output by the specified key. Possible keys: expires, iaid_duid, ip, last_comm, pool, remaining, state, type (default = ip)" + +#: ../../configuration/service/dhcp-server.rst:566 +msgid "Sort the output by the specified key. Possible keys: ip, hardware_address, state, start, end, remaining, pool, hostname (default = ip)" +msgstr "Sort the output by the specified key. Possible keys: ip, hardware_address, state, start, end, remaining, pool, hostname (default = ip)" + +#: ../../configuration/nat/nat44.rst:226 +msgid "Source Address" +msgstr "Source Address" + +#: ../../configuration/interfaces/vxlan.rst:67 +msgid "Source IP address used for VXLAN underlay. This is mandatory when using VXLAN via L2VPN/EVPN." +msgstr "Source IP address used for VXLAN underlay. This is mandatory when using VXLAN via L2VPN/EVPN." + +#: ../../configuration/vpn/sstp.rst:257 +msgid "Source IPv4 address used in all RADIUS server queires." +msgstr "Source IPv4 address used in all RADIUS server queires." + +#: ../../configuration/loadbalancing/wan.rst:186 +msgid "Source NAT rules" +msgstr "Source NAT rules" + +#: ../../configuration/nat/nat66.rst:69 +msgid "Source Prefix" +msgstr "Source Prefix" + +#: ../../configuration/system/login.rst:276 +msgid "Source all connections to the RADIUS servers from given VRF `<name>`." +msgstr "Source all connections to the RADIUS servers from given VRF `<name>`." + +#: ../../configuration/system/login.rst:345 +msgid "Source all connections to the TACACS servers from given VRF `<name>`." +msgstr "Source all connections to the TACACS servers from given VRF `<name>`." + +#: ../../configuration/policy/route-map.rst:174 +msgid "Source protocol to match." +msgstr "Source protocol to match." + +#: ../../configuration/vpn/ipsec.rst:225 +msgid "Source tunnel from loopbacks" +msgstr "Source tunnel from loopbacks" + +#: ../../configuration/interfaces/bridge.rst:105 +msgid "Spanning Tree Protocol forwarding `<delay>` in seconds (default: 15)." +msgstr "Spanning Tree Protocol forwarding `<delay>` in seconds (default: 15)." + +#: ../../configuration/interfaces/bridge.rst:115 +msgid "Spanning Tree Protocol hello advertisement `<interval>` in seconds (default: 2)." +msgstr "Spanning Tree Protocol hello advertisement `<interval>` in seconds (default: 2)." + +#: ../../configuration/interfaces/bridge.rst:16 +msgid "Spanning Tree Protocol is not enabled by default in VyOS. :ref:`stp` can be easily enabled if needed." +msgstr "Spanning Tree Protocol is not enabled by default in VyOS. :ref:`stp` can be easily enabled if needed." + +#: ../../configuration/interfaces/wireless.rst:209 +msgid "Spatial Multiplexing Power Save (SMPS) settings" +msgstr "Spatial Multiplexing Power Save (SMPS) settings" + +#: ../../configuration/vpn/dmvpn.rst:105 +msgid "Specfying nhs makes all multicast packets to be repeated to each statically configured next hop." +msgstr "Specfying nhs makes all multicast packets to be repeated to each statically configured next hop." + +#: ../../configuration/vpn/sstp.rst:227 +msgid "Specifies IP address for Dynamic Authorization Extension server (DM/CoA)" +msgstr "Specifies IP address for Dynamic Authorization Extension server (DM/CoA)" + +#: ../../configuration/vpn/sstp.rst:183 +msgid "Specifies :abbr:`MPPE (Microsoft Point-to-Point Encryption)` negotioation preference." +msgstr "Specifies :abbr:`MPPE (Microsoft Point-to-Point Encryption)` negotioation preference." + +#: ../../configuration/vrf/index.rst:475 +msgid "Specifies an optional route-map to be applied to routes imported or exported between the current unicast VRF and VPN." +msgstr "Specifies an optional route-map to be applied to routes imported or exported between the current unicast VRF and VPN." + +#: ../../configuration/service/dhcp-relay.rst:148 +msgid "Specifies an upstream network `<interface>` from which replies from `<server>` and other relay agents will be accepted." +msgstr "Specifies an upstream network `<interface>` from which replies from `<server>` and other relay agents will be accepted." + +#: ../../configuration/service/webproxy.rst:173 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:40 +msgid "Specifies one of the bonding policies. The default is 802.3ad. Possible values are:" +msgstr "Specifies one of the bonding policies. The default is 802.3ad. Possible values are:" + +#: ../../configuration/service/webproxy.rst:81 +msgid "Specifies proxy service listening address. The listen address is the IP address on which the web proxy service listens for client requests." +msgstr "Specifies proxy service listening address. The listen address is the IP address on which the web proxy service listens for client requests." + +#: ../../configuration/vpn/sstp.rst:110 +msgid "Specifies single `<gateway>` IP address to be used as local address of PPP interfaces." +msgstr "Specifies single `<gateway>` IP address to be used as local address of PPP interfaces." + +#: ../../configuration/vpn/dmvpn.rst:56 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:245 +msgid "Specifies the ARP link monitoring `<time>` in seconds." +msgstr "Specifies the ARP link monitoring `<time>` in seconds." + +#: ../../configuration/interfaces/bonding.rst:264 +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 "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." + +#: ../../configuration/service/ssh.rst:69 +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 "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." + +#: ../../configuration/service/webproxy.rst:207 +msgid "Specifies the base DN under which the users are located." +msgstr "Specifies the base DN under which the users are located." + +#: ../../configuration/service/dhcp-server.rst:272 +msgid "Specifies the clients subnet mask as per RFC 950. If unset, subnet declaration is used." +msgstr "Specifies the clients subnet mask as per RFC 950. If unset, subnet declaration is used." + +#: ../../configuration/vpn/dmvpn.rst:69 +#: ../../configuration/vpn/dmvpn.rst:155 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:132 +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 "Specifies the interval at which Netflow data will be sent to a collector. As per default, Netflow data will be sent every 60 seconds." + +#: ../../configuration/service/webproxy.rst:131 +msgid "Specifies the maximum size of a reply body in KB, used to limit the reply size." +msgstr "Specifies the maximum size of a reply body in KB, used to limit the reply size." + +#: ../../configuration/interfaces/bonding.rst:129 +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 "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." + +#: ../../configuration/service/webproxy.rst:290 +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 "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`)." + +#: ../../configuration/interfaces/pseudo-ethernet.rst:59 +msgid "Specifies the physical `<ethX>` Ethernet interface associated with a Pseudo Ethernet `<interface>`." +msgstr "Specifies the physical `<ethX>` Ethernet interface associated with a Pseudo Ethernet `<interface>`." + +#: ../../configuration/vpn/sstp.rst:116 +msgid "Specifies the port `<port>` that the SSTP port will listen on (default 443)." +msgstr "Specifies the port `<port>` that the SSTP port will listen on (default 443)." + +#: ../../configuration/service/webproxy.rst:194 +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 "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." + +#: ../../configuration/vrf/index.rst:450 +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 "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." + +#: ../../configuration/vrf/index.rst:443 +msgid "Specifies the route distinguisher to be added to a route exported from the current unicast VRF to VPN." +msgstr "Specifies the route distinguisher to be added to a route exported from the current unicast VRF to VPN." + +#: ../../configuration/vpn/sstp.rst:270 +msgid "Specifies the vendor dictionary, dictionary needs to be in /usr/share/accel-ppp/radius." +msgstr "Specifies the vendor dictionary, dictionary needs to be in /usr/share/accel-ppp/radius." + +#: ../../configuration/vpn/sstp.rst:177 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:72 +msgid "Specifies whether an external control plane (e.g. BGP L2VPN/EVPN) or the internal FDB should be used." +msgstr "Specifies whether an external control plane (e.g. BGP L2VPN/EVPN) or the internal FDB should be used." + +#: ../../configuration/protocols/ospf.rst:268 +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 "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." + +#: ../../configuration/vpn/sstp.rst:261 +msgid "Specifies which RADIUS server attribute contains the rate limit information. The default attribute is `Filter-Id`." +msgstr "Specifies which RADIUS server attribute contains the rate limit information. The default attribute is `Filter-Id`." + +#: ../../configuration/service/ssh.rst:45 +msgid "Specify IPv4/IPv6 listen address of SSH server. Multiple addresses can be defined." +msgstr "Specify IPv4/IPv6 listen address of SSH server. Multiple addresses can be defined." + +#: ../../configuration/firewall/general.rst:663 +#: ../../configuration/firewall/general-legacy.rst:455 +msgid "Specify a Fully Qualified Domain Name as source/destination matcher. Ensure router is able to resolve such dns query." +msgstr "Specify a Fully Qualified Domain Name as source/destination matcher. Ensure router is able to resolve such dns query." + +#: ../../configuration/service/dhcp-server.rst:620 +msgid "Specify a NIS+ server address for DHCPv6 clients." +msgstr "Specify a NIS+ server address for DHCPv6 clients." + +#: ../../configuration/service/dhcp-server.rst:615 +msgid "Specify a NIS server address for DHCPv6 clients." +msgstr "Specify a NIS server address for DHCPv6 clients." + +#: ../../configuration/service/dhcp-server.rst:625 +msgid "Specify a :abbr:`SIP (Session Initiation Protocol)` server by IPv6 address of Fully Qualified Domain Name for all DHCPv6 clients." +msgstr "Specify a :abbr:`SIP (Session Initiation Protocol)` server by IPv6 address of Fully Qualified Domain Name for all DHCPv6 clients." + +#: ../../configuration/system/task-scheduler.rst:33 +msgid "Specify absolute `<path>` to script which will be run when `<task>` is executed." +msgstr "Specify absolute `<path>` to script which will be run when `<task>` is executed." + +#: ../../configuration/service/ssh.rst:94 +msgid "Specify allowed :abbr:`KEX (Key Exchange)` algorithms." +msgstr "Specify allowed :abbr:`KEX (Key Exchange)` algorithms." + +#: ../../configuration/protocols/bgp.rst:438 +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 "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." + +#: ../../configuration/service/webproxy.rst:263 +msgid "Specify an alternate TCP port where the ldap server is listening if other than the default LDAP port 389." +msgstr "Specify an alternate TCP port where the ldap server is listening if other than the default LDAP port 389." + +#: ../../configuration/service/ntp.rst:84 +#: ../../configuration/service/ssh.rst:110 +#: ../../configuration/system/syslog.rst:79 +msgid "Specify name of the :abbr:`VRF (Virtual Routing and Forwarding)` instance." +msgstr "Specify name of the :abbr:`VRF (Virtual Routing and Forwarding)` instance." + +#: ../../configuration/loadbalancing/wan.rst:141 +msgid "Specify nexthop on the path to the destination, ``ipv4-address`` can be set to ``dhcp``" +msgstr "Specify nexthop on the path to the destination, ``ipv4-address`` can be set to ``dhcp``" + +#: ../../configuration/system/default-route.rst:16 +msgid "Specify static route into the routing table sending all non local traffic to the nexthop address `<address>`." +msgstr "Specify static route into the routing table sending all non local traffic to the nexthop address `<address>`." + +#: ../../configuration/system/login.rst:245 +msgid "Specify the IP `<address>` of the RADIUS server user with the pre-shared-secret given in `<secret>`." +msgstr "Specify the IP `<address>` of the RADIUS server user with the pre-shared-secret given in `<secret>`." + +#: ../../configuration/system/login.rst:314 +msgid "Specify the IP `<address>` of the TACACS server user with the pre-shared-secret given in `<secret>`." +msgstr "Specify the IP `<address>` of the TACACS server user with the pre-shared-secret given in `<secret>`." + +#: ../../configuration/protocols/bgp.rst:257 +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 "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." + +#: ../../configuration/service/webproxy.rst:272 +msgid "Specify the LDAP server to connect to." +msgstr "Specify the LDAP server to connect to." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:50 +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 "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)." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:27 +msgid "Specify the interface address used locally on the interface where the prefix has been delegated to. ID must be a decimal integer." +msgstr "Specify the interface address used locally on the interface where the prefix has been delegated to. ID must be a decimal integer." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:167 +msgid "Specify the minimum required TLS version 1.2 or 1.3" +msgstr "Specify the minimum required TLS version 1.2 or 1.3" + +#: ../../configuration/system/login.rst:27 +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 "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." + +#: ../../configuration/service/webproxy.rst:49 +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 "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." + +#: ../../configuration/system/time-zone.rst:13 +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 "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." + +#: ../../configuration/system/task-scheduler.rst:16 +msgid "Specify the time interval when `<task>` should be executed. The interval is specified as number with one of the following suffixes:" +msgstr "Specify the time interval when `<task>` should be executed. The interval is specified as number with one of the following suffixes:" + +#: ../../configuration/service/dns.rst:256 +msgid "Specify timeout / update interval to check if IP address changed." +msgstr "Specify timeout / update interval to check if IP address changed." + +#: ../../configuration/service/ssh.rst:90 +msgid "Specify timeout interval for keepalive message in seconds." +msgstr "Specify timeout interval for keepalive message in seconds." + +#: ../../configuration/interfaces/vxlan.rst:170 +msgid "Spine1 is a Cisco IOS router running version 15.4, Leaf2 and Leaf3 is each a VyOS router running 1.2." +msgstr "Spine1 is a Cisco IOS router running version 15.4, Leaf2 and Leaf3 is each a VyOS router running 1.2." + +#: ../../configuration/service/monitoring.rst:83 +msgid "Splunk" +msgstr "Splunk" + +#: ../../configuration/vpn/dmvpn.rst:235 +msgid "Spoke" +msgstr "Spoke" + +#: ../../configuration/service/webproxy.rst:9 +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 "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." + +#: ../../configuration/nat/nat44.rst:791 +msgid "Start by checking for IPSec SAs (Security Associations) with:" +msgstr "Start by checking for IPSec SAs (Security Associations) with:" + +#: ../../configuration/firewall/zone.rst:9 +msgid "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos instalations, and zone based firewall is no longer supported. Documentation for most of the new firewall CLI can be found in the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html>`_ chapter. The legacy firewall is still available for versions before 1.4-rolling-202308040557 and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the legacy firewall configuration commands, since this feature has been removed in earlier releases." +msgstr "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos instalations, and zone based firewall is no longer supported. Documentation for most of the new firewall CLI can be found in the `firewall <https://docs.vyos.io/en/latest/configuration/firewall/general.html>`_ chapter. The legacy firewall is still available for versions before 1.4-rolling-202308040557 and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the legacy firewall configuration commands, since this feature has been removed in earlier releases." + +#: ../../configuration/firewall/index.rst:8 +msgid "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos installations." +msgstr "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos installations." + +#: ../../configuration/firewall/index.rst:5 +msgid "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos installations. Documentation for most new firewall cli can be found here:" +msgstr "Starting from VyOS 1.4-rolling-202308040557, a new firewall structure can be found on all vyos installations. Documentation for most new firewall cli can be found here:" + +#: ../../configuration/service/console-server.rst:7 +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 "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." + +#: ../../configuration/service/mdns.rst:4 +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 "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." + +#: ../../configuration/protocols/static.rst:5 +msgid "Static" +msgstr "Static" + +#: ../../configuration/service/dhcp-server.rst:224 +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 "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." + +#: ../../configuration/system/host-name.rst:45 +msgid "Static Hostname Mapping" +msgstr "Static Hostname Mapping" + +#: ../../configuration/interfaces/macsec.rst:48 +msgid "Static Keys" +msgstr "Static Keys" + +#: ../../configuration/protocols/static.rst:20 +msgid "Static Routes" +msgstr "Static Routes" + +#: ../../configuration/interfaces/openvpn.rst:235 +msgid "Static Routing:" +msgstr "Static Routing:" + +#: ../../configuration/interfaces/openvpn.rst:63 +msgid "Static Routing or other dynamic routing protocols can be used over the vtun interface" +msgstr "Static Routing or other dynamic routing protocols can be used over the vtun interface" + +#: ../../configuration/interfaces/macsec.rst:49 +msgid "Static :abbr:`SAK (Secure Authentication Key)` mode can be configured manually on each device wishing to use MACsec. Keys must be set statically on all devices for traffic to flow properly. Key rotation is dependent on the administrator updating all keys manually across connected devices. Static SAK mode can not be used with MKA." +msgstr "Static :abbr:`SAK (Secure Authentication Key)` mode can be configured manually on each device wishing to use MACsec. Keys must be set statically on all devices for traffic to flow properly. Key rotation is dependent on the administrator updating all keys manually across connected devices. Static SAK mode can not be used with MKA." + +#: ../../configuration/service/dhcp-server.rst:209 +#: ../../configuration/service/dhcp-server.rst:689 +msgid "Static mappings" +msgstr "Static mappings" + +#: ../../configuration/service/dhcp-server.rst:557 +#: ../../configuration/service/dhcp-server.rst:762 +msgid "Static mappings aren't shown. To show all states, use ``show dhcp server leases state all``." +msgstr "Static mappings aren't shown. To show all states, use ``show dhcp server leases state all``." + +#: ../../configuration/protocols/static.rst:7 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:237 +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 "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:" + +#: ../../configuration/interfaces/wireless.rst:298 +msgid "Station supports receiving VHT variant HT Control field" +msgstr "Station supports receiving VHT variant HT Control field" + +#: ../../configuration/interfaces/wireguard.rst:341 +msgid "Status" +msgstr "Status" + +#: ../../configuration/loadbalancing/wan.rst:200 +msgid "Sticky Connections" +msgstr "Sticky Connections" + +#: ../../configuration/protocols/bgp.rst:397 +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 "Storage of route updates uses memory. If you enable soft reconfiguration inbound for multiple neighbors, the amount of memory used can become significant." + +#: ../../configuration/trafficpolicy/index.rst:82 +msgid "Suffixes" +msgstr "Suffixes" + +#: ../../configuration/protocols/ospf.rst:483 +msgid "Summarisation starts only after this delay timer expiry." +msgstr "Summarisation starts only after this delay timer expiry." + +#: ../../configuration/interfaces/wwan.rst:307 +msgid "Supported Modules" +msgstr "Supported Modules" + +#: ../../configuration/interfaces/wireless.rst:150 +msgid "Supported channel width set." +msgstr "Supported channel width set." + +#: ../../configuration/service/router-advert.rst:11 +msgid "Supported interface types:" +msgstr "Supported interface types:" + +#: ../../configuration/service/ssh.rst:198 +msgid "Supported remote protocols are FTP, FTPS, HTTP, HTTPS, SCP/SFTP and TFTP." +msgstr "Supported remote protocols are FTP, FTPS, HTTP, HTTPS, SCP/SFTP and TFTP." + +#: ../../configuration/protocols/rip.rst:17 +msgid "Supported versions of RIP are:" +msgstr "Supported versions of RIP are:" + +#: ../../configuration/protocols/ospf.rst:528 +#: ../../configuration/protocols/ospf.rst:1240 +msgid "Supports as HELPER for configured grace period." +msgstr "Supports as HELPER for configured grace period." + +#: ../../configuration/vpn/ipsec.rst:178 +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 "Suppose the LEFT router has external address 192.0.2.10 on its eth0 interface, and the RIGHT router is 203.0.113.45" + +#: ../../configuration/interfaces/openvpn.rst:338 +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 "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." + +#: ../../configuration/protocols/bgp.rst:283 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:108 +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 "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." + +#: ../../configuration/highavailability/index.rst:108 +msgid "Sync groups" +msgstr "Sync groups" + +#: ../../configuration/firewall/general.rst:1264 +msgid "Synproxy" +msgstr "Synproxy" + +#: ../../configuration/firewall/general.rst:1265 +msgid "Synproxy connections" +msgstr "Synproxy connections" + +#: ../../configuration/firewall/general.rst:1282 +msgid "Synproxy relies on syncookies and TCP timestamps, ensure these are enabled" +msgstr "Synproxy relies on syncookies and TCP timestamps, ensure these are enabled" + +#: ../../configuration/interfaces/pppoe.rst:327 +msgid "Syntax has changed from VyOS 1.2 (crux) and it will be automatically migrated during an upgrade." +msgstr "Syntax has changed from VyOS 1.2 (crux) and it will be automatically migrated during an upgrade." + +#: ../../configuration/system/sysctl.rst:5 +msgid "Sysctl" +msgstr "Sysctl" + +#: ../../configuration/system/syslog.rst:5 +msgid "Syslog" +msgstr "Syslog" + +#: ../../configuration/system/syslog.rst:16 +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 "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." + +#: ../../configuration/system/syslog.rst:48 +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 "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." + +#: ../../configuration/system/syslog.rst:42 +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 "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." + +#: ../../configuration/system/index.rst:3 +msgid "System" +msgstr "System" + +#: ../../configuration/system/name-server.rst:5 +msgid "System DNS" +msgstr "System DNS" + +#: ../../configuration/system/lcd.rst:5 +msgid "System Display (LCD)" +msgstr "System Display (LCD)" + +#: ../../configuration/service/lldp.rst:26 +msgid "System Name and Description" +msgstr "System Name and Description" + +#: ../../configuration/system/proxy.rst:5 +msgid "System Proxy" +msgstr "System Proxy" + +#: ../../configuration/service/lldp.rst:30 +msgid "System capabilities (switching, routing, etc.)" +msgstr "System capabilities (switching, routing, etc.)" + +#: ../../configuration/system/ip.rst:6 +#: ../../configuration/system/ipv6.rst:6 +msgid "System configuration commands" +msgstr "System configuration commands" + +#: ../../configuration/system/syslog.rst:118 +msgid "System daemons" +msgstr "System daemons" + +#: ../../configuration/protocols/isis.rst:57 +msgid "System identifier: ``1921.6800.1002`` - for system idetifiers we recommend to use IP address or MAC address of the router itself. The way to construct this is to keep all of the zeroes of the router IP address, and then change the periods from being every three numbers to every four numbers. The address that is listed here is ``192.168.1.2``, which if expanded will turn into ``192.168.001.002``. Then all one has to do is move the dots to have four numbers instead of three. This gives us ``1921.6800.1002``." +msgstr "System identifier: ``1921.6800.1002`` - for system idetifiers we recommend to use IP address or MAC address of the router itself. The way to construct this is to keep all of the zeroes of the router IP address, and then change the periods from being every three numbers to every four numbers. The address that is listed here is ``192.168.1.2``, which if expanded will turn into ``192.168.001.002``. Then all one has to do is move the dots to have four numbers instead of three. This gives us ``1921.6800.1002``." + +#: ../../configuration/system/syslog.rst:171 +msgid "System is unusable - a panic condition" +msgstr "System is unusable - a panic condition" + +#: ../../configuration/system/login.rst:299 +msgid "TACACS+" +msgstr "TACACS+" + +#: ../../configuration/system/login.rst:416 +msgid "TACACS Example" +msgstr "TACACS Example" + +#: ../../configuration/system/login.rst:305 +msgid "TACACS is defined in :rfc:`8907`." +msgstr "TACACS is defined in :rfc:`8907`." + +#: ../../configuration/system/login.rst:335 +msgid "TACACS servers could be hardened by only allowing certain IP addresses to connect. As of this the source address of each TACACS query can be configured." +msgstr "TACACS servers could be hardened by only allowing certain IP addresses to connect. As of this the source address of each TACACS query can be configured." + +#: ../../configuration/protocols/static.rst:140 +#: ../../configuration/system/flow-accounting.rst:83 +msgid "TBD" +msgstr "TBD" + +#: ../../configuration/vrf/index.rst:40 +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 "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." + +#: ../../configuration/service/tftp-server.rst:5 +msgid "TFTP Server" +msgstr "TFTP Server" + +#: ../../configuration/protocols/ospf.rst:489 +msgid "Tag is the optional parameter. If tag configured Summary route will be originated with the configured tag." +msgstr "Tag is the optional parameter. If tag configured Summary route will be originated with the configured tag." + +#: ../../configuration/system/task-scheduler.rst:5 +msgid "Task Scheduler" +msgstr "Task Scheduler" + +#: ../../configuration/service/monitoring.rst:107 +msgid "Telegraf" +msgstr "Telegraf" + +#: ../../configuration/service/monitoring.rst:6 +msgid "Telegraf output plugin azure-data-explorer_" +msgstr "Telegraf output plugin azure-data-explorer_" + +#: ../../configuration/service/monitoring.rst:39 +msgid "Telegraf output plugin prometheus-client_" +msgstr "Telegraf output plugin prometheus-client_" + +#: ../../configuration/service/monitoring.rst:84 +msgid "Telegraf output plugin splunk_. HTTP Event Collector." +msgstr "Telegraf output plugin splunk_. HTTP Event Collector." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Tell hosts to use the administered (stateful) protocol (i.e. DHCP) for autoconfiguration of other (non-address) information" +msgstr "Tell hosts to use the administered (stateful) protocol (i.e. DHCP) for autoconfiguration of other (non-address) information" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Tell hosts to use the administered stateful protocol (i.e. DHCP) for autoconfiguration" +msgstr "Tell hosts to use the administered stateful protocol (i.e. DHCP) for autoconfiguration" + +#: ../../configuration/vpn/sstp.rst:216 +msgid "Temporary disable this RADIUS server." +msgstr "Temporary disable this RADIUS server." + +#: ../../configuration/system/login.rst:258 +msgid "Temporary disable this RADIUS server. It won't be queried." +msgstr "Temporary disable this RADIUS server. It won't be queried." + +#: ../../configuration/system/login.rst:327 +msgid "Temporary disable this TACACS server. It won't be queried." +msgstr "Temporary disable this TACACS server. It won't be queried." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:245 +msgid "Terminate SSL" +msgstr "Terminate SSL" + +#: ../../configuration/interfaces/pppoe.rst:305 +msgid "Test connecting given connection-oriented interface. `<interface>` can be ``pppoe0`` as the example." +msgstr "Test connecting given connection-oriented interface. `<interface>` can be ``pppoe0`` as the example." + +#: ../../configuration/interfaces/sstp-client.rst:149 +msgid "Test connecting given connection-oriented interface. `<interface>` can be ``sstpc0`` as the example." +msgstr "Test connecting given connection-oriented interface. `<interface>` can be ``sstpc0`` as the example." + +#: ../../configuration/interfaces/pppoe.rst:300 +msgid "Test disconnecting given connection-oriented interface. `<interface>` can be ``pppoe0`` as the example." +msgstr "Test disconnecting given connection-oriented interface. `<interface>` can be ``pppoe0`` as the example." + +#: ../../configuration/interfaces/sstp-client.rst:144 +msgid "Test disconnecting given connection-oriented interface. `<interface>` can be ``sstpc0`` as the example." +msgstr "Test disconnecting given connection-oriented interface. `<interface>` can be ``sstpc0`` as the example." + +#: ../../configuration/vpn/sstp.rst:293 +msgid "Testing SSTP" +msgstr "Testing SSTP" + +#: ../../configuration/nat/nat44.rst:786 +msgid "Testing and Validation" +msgstr "Testing and Validation" + +#: ../../configuration/interfaces/vxlan.rst:125 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1194 +msgid "That is how it is possible to do the so-called \"ingress shaping\"." +msgstr "That is how it is possible to do the so-called \"ingress shaping\"." + +#: ../../configuration/nat/nat44.rst:806 +msgid "That looks good - we defined 2 tunnels and they're both up and running." +msgstr "That looks good - we defined 2 tunnels and they're both up and running." + +#: ../../configuration/interfaces/bonding.rst:247 +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 "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." + +#: ../../configuration/nat/nat44.rst:724 +msgid "The ASP has documented their IPSec requirements:" +msgstr "The ASP has documented their IPSec requirements:" + +#: ../../configuration/protocols/rpki.rst:82 +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 "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." + +#: ../../configuration/vrf/index.rst:94 +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 "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." + +#: ../../configuration/protocols/isis.rst:50 +msgid "The CLNS address consists of the following parts:" +msgstr "The CLNS address consists of the following parts:" + +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +#: ../../_include/interface-dhcpv6-options.txt:4 +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 "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." + +#: ../../configuration/service/webproxy.rst:216 +msgid "The DN and password to bind as while performing searches." +msgstr "The DN and password to bind as while performing searches." + +#: ../../configuration/service/webproxy.rst:238 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:446 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:215 +msgid "The HTTP service listen on TCP port 80." +msgstr "The HTTP service listen on TCP port 80." + +#: ../../configuration/nat/nat44.rst:505 +msgid "The IP address of the internal system we wish to forward traffic to." +msgstr "The IP address of the internal system we wish to forward traffic to." + +#: ../../configuration/interfaces/wireless.rst:602 +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 "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:" + +#: ../../configuration/service/snmp.rst:231 +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 "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." + +#: ../../configuration/vpn/pptp.rst:6 +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 "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." + +#: ../../configuration/service/dns.rst:62 +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 "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:" + +#: ../../configuration/trafficpolicy/index.rst:694 +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 "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." + +#: ../../configuration/vpn/openconnect.rst:287 +msgid "The RADIUS accounting feature must be used with the OpenConnect authentication mode RADIUS. It cannot be used with local authentication. You must configure the OpenConnect authentication mode to \"radius\"." +msgstr "The RADIUS accounting feature must be used with the OpenConnect authentication mode RADIUS. It cannot be used with local authentication. You must configure the OpenConnect authentication mode to \"radius\"." + +#: ../../configuration/vpn/l2tp.rst:200 +msgid "The RADIUS dictionaries in VyOS are located at ``/usr/share/accel-ppp/radius/``" +msgstr "The RADIUS dictionaries in VyOS are located at ``/usr/share/accel-ppp/radius/``" + +#: ../../configuration/protocols/segment-routing.rst:12 +msgid "The SR segments are portions of the network path taken by the packet, and are called SIDs. At each node, the first SID of the list is read, executed as a forwarding function, and may be popped to let the next node read the next SID of the list. The SID list completely determines the path where the packet is forwarded." +msgstr "The SR segments are portions of the network path taken by the packet, and are called SIDs. At each node, the first SID of the list is read, executed as a forwarding function, and may be popped to let the next node read the next SID of the list. The SID list completely determines the path where the packet is forwarded." + +#: ../../configuration/trafficpolicy/index.rst:1023 +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 "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." + +#: ../../configuration/service/broadcast-relay.rst:38 +msgid "The UDP port number used by your apllication. It is mandatory for this kind of operation." +msgstr "The UDP port number used by your apllication. It is mandatory for this kind of operation." + +#: ../../configuration/interfaces/vxlan.rst:23 +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 "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." + +#: ../../configuration/service/dns.rst:14 +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 "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." + +#: ../../configuration/service/dns.rst:160 +msgid "The VyOS DNS forwarder will only accept lookup requests from the LAN subnets - 192.168.1.0/24 and 2001:db8::/64" +msgstr "The VyOS DNS forwarder will only accept lookup requests from the LAN subnets - 192.168.1.0/24 and 2001:db8::/64" + +#: ../../configuration/service/dns.rst:158 +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 "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" + +#: ../../configuration/service/dns.rst:162 +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 "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." + +#: ../../configuration/container/index.rst:7 +msgid "The VyOS container implementation is based on `Podman<https://podman.io/>` as a deamonless container engine." +msgstr "The VyOS container implementation is based on `Podman<https://podman.io/>` as a deamonless container engine." + +#: ../../configuration/interfaces/wireless.rst:347 +#: ../../configuration/interfaces/wireless.rst:547 +msgid "The WAP in this example has the following characteristics:" +msgstr "The WAP in this example has the following characteristics:" + +#: ../../configuration/interfaces/wwan.rst:9 +msgid "The Wireless Wide-Area-Network interface provides access (through a wireless modem/wwan) to wireless networks provided by various cellular providers." +msgstr "The Wireless Wide-Area-Network interface provides access (through a wireless modem/wwan) to wireless networks provided by various cellular providers." + +#: ../../configuration/protocols/bgp.rst:36 +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 "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." + +#: ../../configuration/nat/nat66.rst:55 +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 "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." + +#: ../../configuration/protocols/mpls.rst:42 +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 "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`." + +#: ../../configuration/nat/nat66.rst:75 +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 "The :ref:`source-nat66` rule replaces the source address of the packet and calculates the converted address using the prefix specified in the rule." + +#: ../../configuration/service/dns.rst:98 +msgid "The ``CD``-bit is honored correctly for process and validate. For log-fail, failures will be logged too." +msgstr "The ``CD``-bit is honored correctly for process and validate. For log-fail, failures will be logged too." + +#: ../../configuration/highavailability/index.rst:60 +msgid "The ``address`` can be configured either on the VRRP interface or on not VRRP interface." +msgstr "The ``address`` can be configured either on the VRRP interface or on not VRRP interface." + +#: ../../configuration/highavailability/index.rst:53 +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 "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``" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:248 +msgid "The ``http`` service is lestens on port 80 and force redirects from HTTP to HTTPS." +msgstr "The ``http`` service is lestens on port 80 and force redirects from HTTP to HTTPS." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:251 +msgid "The ``https`` service listens on port 443 with backend `bk-default` to handle HTTPS traffic. It uses certificate named ``cert`` for SSL termination." +msgstr "The ``https`` service listens on port 443 with backend `bk-default` to handle HTTPS traffic. It uses certificate named ``cert`` for SSL termination." + +#: ../../configuration/interfaces/openvpn.rst:66 +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 "The ``persistent-tunnel`` directive will allow us to configure tunnel-related attributes, such as firewall policy as we would on any normal network interface." + +#: ../../configuration/vpn/l2tp.rst:176 +msgid "The ``source-address`` must be configured on one of VyOS interface. Best practice would be a loopback or dummy interface." +msgstr "The ``source-address`` must be configured on one of VyOS interface. Best practice would be a loopback or dummy interface." + +#: ../../configuration/interfaces/bridge.rst:270 +msgid "The `show bridge` operational command can be used to display configured bridges:" +msgstr "The `show bridge` operational command can be used to display configured bridges:" + +#: ../../configuration/vpn/openconnect.rst:246 +msgid "The above directory and default-config must be a child directory of /config/auth, since files outside this directory are not persisted after an image upgrade." +msgstr "The above directory and default-config must be a child directory of /config/auth, since files outside this directory are not persisted after an image upgrade." + +#: ../../configuration/firewall/general.rst:332 +msgid "The action can be :" +msgstr "The action can be :" + +#: ../../configuration/protocols/bgp.rst:775 +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 "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." + +#: ../../configuration/nat/nat44.rst:61 +msgid "The allocated address block is 100.64.0.0/10." +msgstr "The allocated address block is 100.64.0.0/10." + +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +#: ../../_include/interface-ipv6.txt:92 +msgid "The amount of Duplicate Address Detection probes to send." +msgstr "The amount of Duplicate Address Detection probes to send." + +#: ../../configuration/protocols/bgp.rst:835 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:80 +msgid "The available options for <match> are:" +msgstr "The available options for <match> are:" + +#: ../../configuration/vpn/dmvpn.rst:175 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:9 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1179 +msgid "The case of ingress shaping" +msgstr "The case of ingress shaping" + +#: ../../configuration/service/pppoe-server.rst:398 +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 "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." + +#: ../../configuration/service/ipoe-server.rst:90 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:183 +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 "The command :opcmd:`show interfaces wireguard wg01 public-key` will then show the public key, which needs to be shared with the peer." + +#: ../../configuration/interfaces/wireguard.rst:412 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:244 +msgid "The command below enables it, assuming the RADIUS connection has been setup and is working." +msgstr "The command below enables it, assuming the RADIUS connection has been setup and is working." + +#: ../../configuration/protocols/rip.rst:213 +msgid "The command displays current RIP status. It includes RIP timer, filtering, version, RIP enabled interface and RIP peer information." +msgstr "The command displays current RIP status. It includes RIP timer, filtering, version, RIP enabled interface and RIP peer information." + +#: ../../configuration/vpn/pptp.rst:42 +msgid "The command pon TESTUNNEL establishes the PPTP tunnel to the remote system." +msgstr "The command pon TESTUNNEL establishes the PPTP tunnel to the remote system." + +#: ../../configuration/nat/nat44.rst:32 +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 "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:" + +#: ../../configuration/service/dhcp-server.rst:244 +#: ../../configuration/service/dhcp-server.rst:670 +#: ../../configuration/service/dhcp-server.rst:712 +msgid "The configuration will look as follows:" +msgstr "The configuration will look as follows:" + +#: ../../configuration/interfaces/openvpn.rst:253 +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 "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:" + +#: ../../configuration/service/conntrack-sync.rst:14 +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 "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." + +#: ../../configuration/system/conntrack.rst:23 +msgid "The connection tracking expect table contains one entry for each expected connection related to an existing connection. These are generally used by “connection tracking helper” modules such as FTP. The default size of the expect table is 2048 entries." +msgstr "The connection tracking expect table contains one entry for each expected connection related to an existing connection. These are generally used by “connection tracking helper” modules such as FTP. The default size of the expect table is 2048 entries." + +#: ../../configuration/system/conntrack.rst:17 +msgid "The connection tracking table contains one entry for each connection being tracked by the system." +msgstr "The connection tracking table contains one entry for each connection being tracked by the system." + +#: ../../configuration/service/pppoe-server.rst:238 +msgid "The current attribute 'Filter-Id' is being used as default and can be setup within RADIUS:" +msgstr "The current attribute 'Filter-Id' is being used as default and can be setup within RADIUS:" + +#: ../../configuration/service/ntp.rst:29 +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 "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`." + +#: ../../configuration/service/conntrack-sync.rst:49 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:189 +msgid "The default RADIUS attribute for rate limiting is ``Filter-Id``, but you may also redefine it." +msgstr "The default RADIUS attribute for rate limiting is ``Filter-Id``, but you may also redefine it." + +#: ../../configuration/system/login.rst:9 +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 "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." + +#: ../../configuration/system/host-name.rst:29 +msgid "The default hostname used is `vyos`." +msgstr "The default hostname used is `vyos`." + +#: ../../configuration/service/dhcp-server.rst:596 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:336 +msgid "The default port udp is set to 8472. It can be changed with ``set interface vxlan <vxlanN> port <port>``" +msgstr "The default port udp is set to 8472. It can be changed with ``set interface vxlan <vxlanN> port <port>``" + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:15 +msgid "The default value corresponds to 64." +msgstr "The default value corresponds to 64." + +#: ../../configuration/interfaces/bonding.rst:138 +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 "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." + +#: ../../configuration/protocols/rpki.rst:110 +msgid "The default value is 300 seconds." +msgstr "The default value is 300 seconds." + +#: ../../configuration/service/dhcp-server.rst:113 +msgid "The default value is 86400 seconds which corresponds to one day." +msgstr "The default value is 86400 seconds which corresponds to one day." + +#: ../../configuration/interfaces/bonding.rst:157 +msgid "The default value is slow." +msgstr "The default value is slow." + +#: ../../configuration/trafficpolicy/index.rst:859 +msgid "The default values for the minimum-threshold depend on IP precedence:" +msgstr "The default values for the minimum-threshold depend on IP precedence:" + +#: ../../configuration/interfaces/vxlan.rst:313 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:200 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:36 +#: ../../configuration/service/dhcp-server.rst:138 +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 "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)." + +#: ../../configuration/service/dhcp-server.rst:45 +#: ../../configuration/service/dhcp-server.rst:145 +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 "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)." + +#: ../../configuration/nat/nat44.rst:694 +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 "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." + +#: ../../configuration/interfaces/dummy.rst:9 +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 "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." + +#: ../../configuration/service/webproxy.rst:154 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:105 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:382 +msgid "The example below covers a dual-stack configuration via pppoe-server." +msgstr "The example below covers a dual-stack configuration via pppoe-server." + +#: ../../configuration/service/pppoe-server.rst:361 +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 "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." + +#: ../../configuration/service/ipoe-server.rst:35 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:303 +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 "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." + +#: ../../configuration/nat/nat44.rst:319 +msgid "The external IP address to translate to" +msgstr "The external IP address to translate to" + +#: ../../configuration/firewall/general.rst:16 +msgid "The firewall supports the creation of groups for addresses, domains, interfaces, mac-addresses, networks and port groups. This groups can be used later in firewall ruleset as desired." +msgstr "The firewall supports the creation of groups for addresses, domains, interfaces, mac-addresses, networks and port groups. This groups can be used later in firewall ruleset as desired." + +#: ../../configuration/firewall/general-legacy.rst:20 +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 "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." + +#: ../../configuration/container/index.rst:50 +msgid "The first IP in the container network is reserved by the engine and cannot be used" +msgstr "The first IP in the container network is reserved by the engine and cannot be used" + +#: ../../configuration/service/ipoe-server.rst:49 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:174 +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 "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." + +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +#: ../../_include/interface-disable-flow-control.txt:8 +msgid "The first flow control mechanism, the pause frame, was defined by the IEEE 802.3x standard." +msgstr "The first flow control mechanism, the pause frame, was defined by the IEEE 802.3x standard." + +#: ../../configuration/vpn/dmvpn.rst:63 +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 "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." + +#: ../../configuration/vpn/sstp.rst:299 +msgid "The following PPP configuration tests MSCHAP-v2:" +msgstr "The following PPP configuration tests MSCHAP-v2:" + +#: ../../configuration/system/login.rst:143 +msgid "The following command can be used to generate the OTP key as well as the CLI commands to configure them:" +msgstr "The following command can be used to generate the OTP key as well as the CLI commands to configure them:" + +#: ../../configuration/interfaces/openvpn.rst:708 +msgid "The following commands let you check tunnel status." +msgstr "The following commands let you check tunnel status." + +#: ../../configuration/interfaces/openvpn.rst:727 +msgid "The following commands let you reset OpenVPN." +msgstr "The following commands let you reset OpenVPN." + +#: ../../configuration/container/index.rst:35 +msgid "The following commands translate to \"--net host\" when the container is created" +msgstr "The following commands translate to \"--net host\" when the container is created" + +#: ../../configuration/vrf/index.rst:101 +msgid "The following commands would be required to set options for a given dynamic routing protocol inside a given vrf:" +msgstr "The following commands would be required to set options for a given dynamic routing protocol inside a given vrf:" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:212 +msgid "The following configuration demonstrates how to use VyOS to achieve load balancing based on the domain name." +msgstr "The following configuration demonstrates how to use VyOS to achieve load balancing based on the domain name." + +#: ../../configuration/protocols/pim6.rst:87 +msgid "The following configuration explicitly joins multicast group `ff15::1234` on interface `eth1` and source-specific multicast group `ff15::5678` with source address `2001:db8::1` on interface `eth1`:" +msgstr "The following configuration explicitly joins multicast group `ff15::1234` on interface `eth1` and source-specific multicast group `ff15::5678` with source address `2001:db8::1` on interface `eth1`:" + +#: ../../configuration/interfaces/bonding.rst:293 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:246 +msgid "The following configuration reverse-proxy terminate SSL." +msgstr "The following configuration reverse-proxy terminate SSL." + +#: ../../configuration/interfaces/pppoe.rst:370 +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 "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." + +#: ../../configuration/policy/examples.rst:155 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:543 +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 "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." + +#: ../../configuration/interfaces/wwan.rst:296 +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 "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`." + +#: ../../configuration/vrf/index.rst:237 +msgid "The following example topology was built using EVE-NG." +msgstr "The following example topology was built using EVE-NG." + +#: ../../configuration/policy/examples.rst:58 +msgid "The following example will show how VyOS can be used to redirect web traffic to an external transparent proxy:" +msgstr "The following example will show how VyOS can be used to redirect web traffic to an external transparent proxy:" + +#: ../../configuration/interfaces/wwan.rst:309 +msgid "The following hardware modules have been tested successfully in an :ref:`pc-engines-apu4` board:" +msgstr "The following hardware modules have been tested successfully in an :ref:`pc-engines-apu4` board:" + +#: ../../configuration/interfaces/wireguard.rst:302 +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 "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." + +#: ../../configuration/vrf/index.rst:54 +msgid "The following protocols can be used: any, babel, bgp, connected, eigrp, isis, kernel, ospf, rip, static, table" +msgstr "The following protocols can be used: any, babel, bgp, connected, eigrp, isis, kernel, ospf, rip, static, table" + +#: ../../configuration/vrf/index.rst:64 +msgid "The following protocols can be used: any, babel, bgp, connected, isis, kernel, ospfv3, ripng, static, table" +msgstr "The following protocols can be used: any, babel, bgp, connected, isis, kernel, ospfv3, ripng, static, table" + +#: ../../configuration/index.rst:5 +msgid "The following structure respresent the cli structure." +msgstr "The following structure respresent the cli structure." + +#: ../../configuration/interfaces/bonding.rst:205 +msgid "The formula for unfragmented TCP and UDP packets is" +msgstr "The formula for unfragmented TCP and UDP packets is" + +#: ../../configuration/interfaces/bridge.rst:107 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:98 +#: ../../configuration/service/dhcp-relay.rst:184 +msgid "The generated configuration will look like:" +msgstr "The generated configuration will look like:" + +#: ../../configuration/pki/index.rst:107 +msgid "The generated parameters are then output to the console." +msgstr "The generated parameters are then output to the console." + +#: ../../configuration/trafficpolicy/index.rst:12 +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 "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." + +#: ../../configuration/service/salt-minion.rst:29 +msgid "The hash type used when discovering file on master server (default: sha256)" +msgstr "The hash type used when discovering file on master server (default: sha256)" + +#: ../../configuration/loadbalancing/wan.rst:126 +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 "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:" + +#: ../../configuration/protocols/ospf.rst:404 +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 "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." + +#: ../../configuration/system/host-name.rst:25 +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 "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." + +#: ../../configuration/service/salt-minion.rst:41 +msgid "The hostname or IP address of the master" +msgstr "The hostname or IP address of the master" + +#: ../../configuration/service/dhcp-server.rst:700 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:237 +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 "The individual spoke configurations only differ in the local IP address on the ``tun10`` interface. See the above diagram for the individual IP addresses." + +#: ../../_include/interface-vlan-8021ad.txt:25 +#: ../../_include/interface-vlan-8021ad.txt:25 +#: ../../_include/interface-vlan-8021ad.txt:25 +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 "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)." + +#: ../../configuration/nat/nat44.rst:503 +msgid "The interface traffic will be coming in on;" +msgstr "The interface traffic will be coming in on;" + +#: ../../configuration/service/broadcast-relay.rst:27 +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 "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." + +#: ../../configuration/nat/nat44.rst:317 +msgid "The internal IP addresses we want to translate" +msgstr "The internal IP addresses we want to translate" + +#: ../../configuration/interfaces/l2tpv3.rst:105 +msgid "The inverse configuration has to be applied to the remote side." +msgstr "The inverse configuration has to be applied to the remote side." + +#: ../../configuration/interfaces/pppoe.rst:319 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:163 +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 "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." + +#: ../../configuration/firewall/index.rst:12 +msgid "The legacy and zone-based firewall configuration options is not longer supported. They are here for reference purposes only." +msgstr "The legacy and zone-based firewall configuration options is not longer supported. They are here for reference purposes only." + +#: ../../configuration/trafficpolicy/index.rst:552 +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 "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." + +#: ../../configuration/policy/route-map.rst:255 +msgid "The link bandwidth extended community is encoded as non-transitive" +msgstr "The link bandwidth extended community is encoded as non-transitive" + +#: ../../configuration/service/dns.rst:132 +msgid "The local IPv4 or IPv6 addresses to bind the DNS forwarder to. The forwarder will listen on this address for incoming connections." +msgstr "The local IPv4 or IPv6 addresses to bind the DNS forwarder to. The forwarder will listen on this address for incoming connections." + +#: ../../configuration/service/dns.rst:137 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:62 +msgid "The local site will have a subnet of 10.0.0.0/16." +msgstr "The local site will have a subnet of 10.0.0.0/16." + +#: ../../configuration/interfaces/loopback.rst:9 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:271 +msgid "The maximum number of targets that can be specified is 16. The default value is no IP address." +msgstr "The maximum number of targets that can be specified is 16. The default value is no IP address." + +#: ../../configuration/trafficpolicy/index.rst:130 +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 number of a class in a Priority Queue it does not only identify it, it also defines its priority." +msgstr "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 number of a class in a Priority Queue it does not only identify it, it also defines its priority." + +#: ../../configuration/interfaces/bridge.rst:230 +msgid "The member interface `eth1` is a trunk that allows VLAN 10 to pass" +msgstr "The member interface `eth1` is a trunk that allows VLAN 10 to pass" + +#: ../../configuration/protocols/isis.rst:180 +msgid "The metric range is 1 to 16777215 (Max value depend if metric support narrow or wide value)." +msgstr "The metric range is 1 to 16777215 (Max value depend if metric support narrow or wide value)." + +#: ../../configuration/protocols/bfd.rst:43 +msgid "The minimal echo receive transmission interval that this system is capable of handling" +msgstr "The minimal echo receive transmission interval that this system is capable of handling" + +#: ../../configuration/service/ssh.rst:18 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:292 +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 "The multicast-group used by all leaves for this vlan extension. Has to be the same on all leaves that has this interface." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:182 +msgid "The name of the service can be different, in this example it is only for convenience." +msgstr "The name of the service can be different, in this example it is only for convenience." + +#: ../../configuration/service/dhcp-server.rst:13 +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 "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." + +#: ../../configuration/service/conntrack-sync.rst:188 +msgid "The next example is a simple configuration of conntrack-sync." +msgstr "The next example is a simple configuration of conntrack-sync." + +#: ../../configuration/interfaces/wireguard.rst:128 +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 "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." + +#: ../../configuration/vpn/rsa-keys.rst:38 +msgid "The noted public keys should be entered on the opposite routers." +msgstr "The noted public keys should be entered on the opposite routers." + +#: ../../configuration/service/dns.rst:125 +msgid "The number of milliseconds to wait for a remote authoritative server to respond before timing out and responding with SERVFAIL." +msgstr "The number of milliseconds to wait for a remote authoritative server to respond before timing out and responding with SERVFAIL." + +#: ../../configuration/protocols/bgp.rst:331 +msgid "The number parameter (1-10) configures the amount of accepted occurences of the system AS number in AS path." +msgstr "The number parameter (1-10) configures the amount of accepted occurences of the system AS number in AS path." + +#: ../../configuration/interfaces/openvpn.rst:64 +msgid "The official port for OpenVPN is 1194, which we reserve for client VPN; we will use 1195 for site-to-site VPN." +msgstr "The official port for OpenVPN is 1194, which we reserve for client VPN; we will use 1195 for site-to-site VPN." + +#: ../../configuration/firewall/index.rst:32 +msgid "The only stages VyOS will process as part of the firewall configuration is the `forward` (F4 stage), `input` (L4 stage), and `output` (L5 stage). All the other stages and steps are for reference and cant be manipulated through VyOS." +msgstr "The only stages VyOS will process as part of the firewall configuration is the `forward` (F4 stage), `input` (L4 stage), and `output` (L5 stage). All the other stages and steps are for reference and cant be manipulated through VyOS." + +#: ../../configuration/protocols/ospf.rst:155 +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 "The optional `disable` option allows to exclude interface from passive state. This command is used if the command :cfgcmd:`passive-interface default` was configured." + +#: ../../configuration/vpn/dmvpn.rst:93 +msgid "The optional parameter register specifies that Registration Request should be sent to this peer on startup." +msgstr "The optional parameter register specifies that Registration Request should be sent to this peer on startup." + +#: ../../_include/interface-vlan-8021ad.txt:10 +#: ../../_include/interface-vlan-8021ad.txt:10 +#: ../../_include/interface-vlan-8021ad.txt:10 +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 "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." + +#: ../../configuration/nat/nat44.rst:318 +msgid "The outgoing interface to perform the translation on" +msgstr "The outgoing interface to perform the translation on" + +#: ../../configuration/vpn/site2site_ipsec.rst:13 +msgid "The peer name must be an alphanumeric and can have hypen or underscore as special characters. It is purely informational." +msgstr "The peer name must be an alphanumeric and can have hypen or underscore as special characters. It is purely informational." + +#: ../../configuration/vpn/ipsec.rst:235 +msgid "The peer names RIGHT and LEFT are used as informational text." +msgstr "The peer names RIGHT and LEFT are used as informational text." + +#: ../../configuration/interfaces/macsec.rst:89 +msgid "The peer with lower priority will become the key server and start distributing SAKs." +msgstr "The peer with lower priority will become the key server and start distributing SAKs." + +#: ../../configuration/vrf/index.rst:181 +msgid "The ping command is used to test whether a network host is reachable or not." +msgstr "The ping command is used to test whether a network host is reachable or not." + +#: ../../configuration/service/dns.rst:94 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:50 +msgid "The pre-shared key mode is deprecated and will be removed from future OpenVPN versions, so VyOS will have to remove support for that option as well. The reason is that using pre-shared keys is significantly less secure than using TLS." +msgstr "The pre-shared key mode is deprecated and will be removed from future OpenVPN versions, so VyOS will have to remove support for that option as well. The reason is that using pre-shared keys is significantly less secure than using TLS." + +#: ../../configuration/protocols/rpki.rst:49 +msgid "The prefix and ASN that originated it match a signed ROA. These are probably trustworthy route announcements." +msgstr "The prefix and ASN that originated it match a signed ROA. These are probably trustworthy route announcements." + +#: ../../configuration/protocols/rpki.rst:53 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:434 +msgid "The primary DHCP server uses address `192.168.189.252`" +msgstr "The primary DHCP server uses address `192.168.189.252`" + +#: ../../configuration/service/dhcp-server.rst:193 +msgid "The primary and secondary statements determines whether the server is primary or secondary." +msgstr "The primary and secondary statements determines whether the server is primary or secondary." + +#: ../../configuration/interfaces/bonding.rst:240 +msgid "The primary option is only valid for active-backup, transmit-load-balance, and adaptive-load-balance mode." +msgstr "The primary option is only valid for active-backup, transmit-load-balance, and adaptive-load-balance mode." + +#: ../../configuration/highavailability/index.rst:104 +msgid "The priority must be an integer number from 1 to 255. Higher priority value increases router's precedence in the master elections." +msgstr "The priority must be an integer number from 1 to 255. Higher priority value increases router's precedence in the master elections." + +#: ../../configuration/service/dhcp-server.rst:609 +msgid "The procedure to specify a :abbr:`NIS+ (Network Information Service Plus)` domain is similar to the NIS domain one:" +msgstr "The procedure to specify a :abbr:`NIS+ (Network Information Service Plus)` domain is similar to the NIS domain one:" + +#: ../../configuration/vrf/index.rst:222 +msgid "The prompt is adjusted to reflect this change in both config and op-mode." +msgstr "The prompt is adjusted to reflect this change in both config and op-mode." + +#: ../../configuration/nat/nat44.rst:504 +msgid "The protocol and port we wish to forward;" +msgstr "The protocol and port we wish to forward;" + +#: ../../configuration/service/ntp.rst:21 +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 "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." + +#: ../../configuration/interfaces/l2tpv3.rst:25 +msgid "The protocol overhead of L2TPv3 is also significantly bigger than MPLS." +msgstr "The protocol overhead of L2TPv3 is also significantly bigger than MPLS." + +#: ../../configuration/service/webproxy.rst:7 +msgid "The proxy service in VyOS is based on Squid_ and some related modules." +msgstr "The proxy service in VyOS is based on Squid_ and some related modules." + +#: ../../configuration/interfaces/openvpn.rst:59 +msgid "The public IP address of the local side of the VPN will be 198.51.100.10." +msgstr "The public IP address of the local side of the VPN will be 198.51.100.10." + +#: ../../configuration/interfaces/openvpn.rst:60 +msgid "The public IP address of the remote side of the VPN will be 203.0.113.11." +msgstr "The public IP address of the remote side of the VPN will be 203.0.113.11." + +#: ../../configuration/service/ipoe-server.rst:130 +#: ../../configuration/vpn/l2tp.rst:120 +msgid "The rate-limit is set in kbit/sec." +msgstr "The rate-limit is set in kbit/sec." + +#: ../../configuration/service/eventhandler.rst:46 +msgid "The regular expression matches if and only if the entire string matches the pattern." +msgstr "The regular expression matches if and only if the entire string matches the pattern." + +#: ../../configuration/interfaces/wireguard.rst:146 +msgid "The remote peer `to-wg02` uses XMrlPykaxhdAAiSjhtPlvi30NVkvLQliQuKP7AI7CyI= as its public key portion" +msgstr "The remote peer `to-wg02` uses XMrlPykaxhdAAiSjhtPlvi30NVkvLQliQuKP7AI7CyI= as its public key portion" + +#: ../../configuration/interfaces/openvpn.rst:63 +msgid "The remote site will have a subnet of 10.1.0.0/16." +msgstr "The remote site will have a subnet of 10.1.0.0/16." + +#: ../../configuration/vpn/openconnect.rst:15 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:458 +msgid "The required config file may look like this:" +msgstr "The required config file may look like this:" + +#: ../../configuration/nat/nat44.rst:683 +msgid "The required configuration can be broken down into 4 major pieces:" +msgstr "The required configuration can be broken down into 4 major pieces:" + +#: ../../configuration/service/tftp-server.rst:53 +msgid "The resulting configuration will look like:" +msgstr "The resulting configuration will look like:" + +#: ../../configuration/interfaces/vti.rst:35 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:963 +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 "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)." + +#: ../../configuration/protocols/bgp.rst:59 +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 "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." + +#: ../../configuration/protocols/bgp.rst:122 +msgid "The route with the shortest cluster-list length is used. The cluster-list reflects the iBGP reflection path the route has taken." +msgstr "The route with the shortest cluster-list length is used. The cluster-list reflects the iBGP reflection path the route has taken." + +#: ../../configuration/protocols/ospf.rst:174 +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 "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." + +#: ../../configuration/service/dhcp-relay.rst:45 +msgid "The router should discard DHCP packages already containing relay agent information to ensure that only requests from DHCP clients are forwarded." +msgstr "The router should discard DHCP packages already containing relay agent information to ensure that only requests from DHCP clients are forwarded." + +#: ../../configuration/system/sflow.rst:9 +msgid "The sFlow accounting based on hsflowd https://sflow.net/" +msgstr "The sFlow accounting based on hsflowd https://sflow.net/" + +#: ../../configuration/vpn/openconnect.rst:263 +msgid "The same configuration options apply when Identity based config is configured in group mode except that group mode can only be used with RADIUS authentication." +msgstr "The same configuration options apply when Identity based config is configured in group mode except that group mode can only be used with RADIUS authentication." + +#: ../../configuration/vpn/ipsec.rst:227 +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 "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." + +#: ../../configuration/service/webproxy.rst:228 +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 "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`." + +#: ../../configuration/service/dhcp-server.rst:435 +msgid "The secondary DHCP server uses address `192.168.189.253`" +msgstr "The secondary DHCP server uses address `192.168.189.253`" + +#: ../../configuration/service/snmp.rst:132 +msgid "The security approach in SNMPv3 targets:" +msgstr "The security approach in SNMPv3 targets:" + +#: ../../configuration/service/console-server.rst:112 +msgid "The sequence ``^Ec?`` translates to: ``Ctrl+E c ?``. To quit the session use: ``Ctrl+E c .``" +msgstr "The sequence ``^Ec?`` translates to: ``Ctrl+E c ?``. To quit the session use: ``Ctrl+E c .``" + +#: ../../configuration/interfaces/vxlan.rst:168 +msgid "The setup is this: Leaf2 - Spine1 - Leaf3" +msgstr "The setup is this: Leaf2 - Spine1 - Leaf3" + +#: ../../configuration/service/webproxy.rst:38 +msgid "The size of the on-disk Proxy cache is user configurable. The Proxies default cache-size is configured to 100 MB." +msgstr "The size of the on-disk Proxy cache is user configurable. The Proxies default cache-size is configured to 100 MB." + +#: ../../configuration/system/console.rst:30 +msgid "The speed (baudrate) of the console device. Supported values are:" +msgstr "The speed (baudrate) of the console device. Supported values are:" + +#: ../../_include/interface-vlan-8021q.txt:16 +#: ../../_include/interface-vlan-8021q.txt:16 +#: ../../_include/interface-vlan-8021q.txt:16 +#: ../../_include/interface-vlan-8021q.txt:16 +#: ../../_include/interface-vlan-8021q.txt:16 +#: ../../_include/interface-vlan-8021q.txt:16 +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 "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." + +#: ../../configuration/system/lcd.rst:7 +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 "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." + +#: ../../configuration/system/name-server.rst:65 +msgid "The system is configured to attempt domain completion in the following order: vyos.io (first), vyos.net (second) and vyos.network (last):" +msgstr "The system is configured to attempt domain completion in the following order: vyos.io (first), vyos.net (second) and vyos.network (last):" + +#: ../../configuration/protocols/ospf.rst:729 +msgid "The table consists of following data:" +msgstr "The table consists of following data:" + +#: ../../configuration/system/task-scheduler.rst:7 +msgid "The task scheduler allows you to execute tasks on a given schedule. It makes use of UNIX cron_." +msgstr "The task scheduler allows you to execute tasks on a given schedule. It makes use of UNIX cron_." + +#: ../../configuration/nat/nat44.rst:233 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:61 +msgid "The tunnel will use 10.255.1.1 for the local IP and 10.255.1.2 for the remote." +msgstr "The tunnel will use 10.255.1.1 for the local IP and 10.255.1.2 for the remote." + +#: ../../configuration/protocols/ospf.rst:788 +msgid "The type can be the following: asbr-summary, external, network, nssa-external, opaque-area, opaque-as, opaque-link, router, summary." +msgstr "The type can be the following: asbr-summary, external, network, nssa-external, opaque-area, opaque-as, opaque-link, router, summary." + +#: ../../configuration/trafficpolicy/index.rst:114 +msgid "The ultimate goal of classifying traffic is to give each class a different treatment." +msgstr "The ultimate goal of classifying traffic is to give each class a different treatment." + +#: ../../configuration/service/ipoe-server.rst:18 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:221 +msgid "The value of the attribute ``NAS-Port-Id`` must be less than 16 characters, otherwise the interface won't be renamed." +msgstr "The value of the attribute ``NAS-Port-Id`` must be less than 16 characters, otherwise the interface won't be renamed." + +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +#: ../../_include/interface-dhcp-options.txt:31 +msgid "The vendor-class-id option can be used to request a specific class of vendor options from the server." +msgstr "The vendor-class-id option can be used to request a specific class of vendor options from the server." + +#: ../../configuration/interfaces/virtual-ethernet.rst:9 +msgid "The veth devices are virtual Ethernet devices. They can act as tunnels between network namespaces to create a bridge to a physical network device in another namespace or VRF, but can also be used as standalone network devices." +msgstr "The veth devices are virtual Ethernet devices. They can act as tunnels between network namespaces to create a bridge to a physical network device in another namespace or VRF, but can also be used as standalone network devices." + +#: ../../configuration/system/login.rst:138 +msgid "The window size must be between 1 and 21." +msgstr "The window size must be between 1 and 21." + +#: ../../configuration/interfaces/wireless.rst:340 +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 "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." + +#: ../../configuration/nat/nat44.rst:597 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:359 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:196 +msgid "Then you need to install the key on the remote router:" +msgstr "Then you need to install the key on the remote router:" + +#: ../../configuration/interfaces/openvpn.rst:202 +msgid "Then you need to set the key in your OpenVPN interface settings:" +msgstr "Then you need to set the key in your OpenVPN interface settings:" + +#: ../../configuration/interfaces/openvpn.rst:24 +msgid "There's a variety of client GUI frontends for any platform" +msgstr "There's a variety of client GUI frontends for any platform" + +#: ../../configuration/service/ntp.rst:47 +msgid "There are 3 default NTP server set. You are able to change them." +msgstr "There are 3 default NTP server set. You are able to change them." + +#: ../../configuration/firewall/general.rst:536 +#: ../../configuration/firewall/general-legacy.rst:380 +msgid "There are a lot of matching criteria against which the package can be tested." +msgstr "There are a lot of matching criteria against which the package can be tested." + +#: ../../configuration/policy/route.rst:40 +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 "There are a lot of matching criteria options available, both for ``policy route`` and ``policy route6``. These options are listed in this section." + +#: ../../configuration/system/ipv6.rst:91 +msgid "There are different parameters for getting prefix-list information:" +msgstr "There are different parameters for getting prefix-list information:" + +#: ../../configuration/interfaces/wireless.rst:157 +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 "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:" + +#: ../../configuration/trafficpolicy/index.rst:166 +msgid "There are many parameters you will be able to use in order to match the traffic you want for a class:" +msgstr "There are many parameters you will be able to use in order to match the traffic you want for a class:" + +#: ../../configuration/system/flow-accounting.rst:96 +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 "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:" + +#: ../../configuration/service/ipoe-server.rst:153 +msgid "There are rate-limited and non rate-limited users (MACs)" +msgstr "There are rate-limited and non rate-limited users (MACs)" + +#: ../../configuration/system/console.rst:13 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:14 +msgid "There are three modes of operation for a wireless interface:" +msgstr "There are three modes of operation for a wireless interface:" + +#: ../../configuration/protocols/rpki.rst:9 +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 "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" + +#: ../../configuration/protocols/bgp.rst:896 +msgid "There are two ways that help us to mitigate the BGPs full-mesh requirement in a network:" +msgstr "There are two ways that help us to mitigate the BGPs full-mesh requirement in a network:" + +#: ../../configuration/interfaces/loopback.rst:13 +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 "There can only be one loopback ``lo`` interface on the system. If you need multiple interfaces, please use the :ref:`dummy-interface` interface type." + +#: ../../configuration/policy/index.rst:13 +msgid "There could be a wide range of routing policies. Some examples are listed below:" +msgstr "There could be a wide range of routing policies. Some examples are listed below:" + +#: ../../configuration/nat/nat44.rst:115 +msgid "There is a very nice picture/explanation in the Vyatta documentation which should be rewritten here." +msgstr "There is a very nice picture/explanation in the Vyatta documentation which should be rewritten here." + +#: ../../configuration/interfaces/tunnel.rst:282 +msgid "There is also a GRE over IPv6 encapsulation available, it is called: ``ip6gre``." +msgstr "There is also a GRE over IPv6 encapsulation available, it is called: ``ip6gre``." + +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +#: ../../_include/interface-vrf.txt:6 +msgid "There is an entire chapter about how to configure a :ref:`vrf`, please check this for additional information." +msgstr "There is an entire chapter about how to configure a :ref:`vrf`, please check this for additional information." + +#: ../../configuration/protocols/igmp.rst:93 +#: ../../configuration/protocols/pim6.rst:27 +msgid "These are the commands for a basic setup." +msgstr "These are the commands for a basic setup." + +#: ../../configuration/policy/examples.rst:149 +msgid "These commands allow the VLAN10 and VLAN11 hosts to communicate with each other using the main routing table." +msgstr "These commands allow the VLAN10 and VLAN11 hosts to communicate with each other using the main routing table." + +#: ../../configuration/highavailability/index.rst:238 +msgid "These configuration is not mandatory and in most cases there's no need to configure it. But if necessary, Gratuitous ARP can be configured in ``global-parameters`` and/or in ``group`` section." +msgstr "These configuration is not mandatory and in most cases there's no need to configure it. But if necessary, Gratuitous ARP can be configured in ``global-parameters`` and/or in ``group`` section." + +#: ../../configuration/service/dhcp-server.rst:409 +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 "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" + +#: ../../configuration/service/dhcp-server.rst:489 +msgid "These parameters need to be part of the DHCP global options. They stay unchanged." +msgstr "These parameters need to be part of the DHCP global options. They stay unchanged." + +#: ../../configuration/trafficpolicy/index.rst:52 +msgid "They can be **decimal** prefixes." +msgstr "They can be **decimal** prefixes." + +#: ../../configuration/interfaces/l2tpv3.rst:54 +msgid "This address must be the address of a local interface. It may be specified as an IPv4 address or an IPv6 address." +msgstr "This address must be the address of a local interface. It may be specified as an IPv4 address or an IPv6 address." + +#: ../../configuration/interfaces/bonding.rst:172 +#: ../../configuration/interfaces/bonding.rst:198 +msgid "This algorithm is 802.3ad compliant." +msgstr "This algorithm is 802.3ad compliant." + +#: ../../configuration/interfaces/bonding.rst:224 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:169 +msgid "This algorithm will place all traffic to a particular network peer on the same slave." +msgstr "This algorithm will place all traffic to a particular network peer on the same slave." + +#: ../../configuration/interfaces/bonding.rst:190 +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 "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." + +#: ../../configuration/protocols/bfd.rst:19 +msgid "This allows avoiding the timers defined in BGP and OSPF protocol to expires." +msgstr "This allows avoiding the timers defined in BGP and OSPF protocol to expires." + +#: ../../configuration/service/dns.rst:41 +msgid "This also works for reverse-lookup zones (``18.172.in-addr.arpa``)." +msgstr "This also works for reverse-lookup zones (``18.172.in-addr.arpa``)." + +#: ../../configuration/interfaces/tunnel.rst:8 +msgid "This article touches on 'classic' IP tunneling protocols." +msgstr "This article touches on 'classic' IP tunneling protocols." + +#: ../../configuration/vpn/dmvpn.rst:164 +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 "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)`." + +#: ../../configuration/policy/examples.rst:78 +msgid "This can be confirmed using the ``show ip route table 100`` operational command." +msgstr "This can be confirmed using the ``show ip route table 100`` operational command." + +#: ../../configuration/service/webproxy.rst:296 +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 "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`)." + +#: ../../configuration/system/sysctl.rst:7 +msgid "This chapeter describes how to configure kernel parameters at runtime." +msgstr "This chapeter describes how to configure kernel parameters at runtime." + +#: ../../configuration/system/option.rst:7 +msgid "This chapter describe the possibilities of advanced system behavior." +msgstr "This chapter describe the possibilities of advanced system behavior." + +#: ../../configuration/protocols/isis.rst:42 +msgid "This commad sets network entity title (NET) provided in ISO format." +msgstr "This commad sets network entity title (NET) provided in ISO format." + +#: ../../configuration/protocols/bgp.rst:326 +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 "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." + +#: ../../configuration/protocols/bgp.rst:304 +msgid "This command allow override the result of Capability Negotiation with local configuration. Ignore remote peer’s capability value." +msgstr "This command allow override the result of Capability Negotiation with local configuration. Ignore remote peer’s capability value." + +#: ../../configuration/protocols/bgp.rst:417 +msgid "This command allows peerings between directly connected eBGP peers using loopback addresses without adjusting the default TTL of 1." +msgstr "This command allows peerings between directly connected eBGP peers using loopback addresses without adjusting the default TTL of 1." + +#: ../../configuration/protocols/bgp.rst:429 +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 "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`." + +#: ../../configuration/protocols/bgp.rst:812 +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 "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." + +#: ../../configuration/protocols/ospf.rst:97 +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 "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." + +#: ../../configuration/protocols/ospf.rst:432 +#: ../../configuration/protocols/ospf.rst:1172 +msgid "This command allows to specify the distribution type for the network connected to this interface:" +msgstr "This command allows to specify the distribution type for the network connected to this interface:" + +#: ../../configuration/protocols/bgp.rst:576 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1259 +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 "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." + +#: ../../configuration/protocols/rip.rst:152 +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 "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." + +#: ../../configuration/protocols/ospf.rst:603 +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 "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." + +#: ../../configuration/protocols/isis.rst:251 +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 "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." + +#: ../../configuration/protocols/babel.rst:173 +msgid "This command allows you apply access lists to a chosen interface to filter the Babel routes." +msgstr "This command allows you apply access lists to a chosen interface to filter the Babel routes." + +#: ../../configuration/protocols/rip.rst:90 +msgid "This command allows you apply access lists to a chosen interface to filter the RIP path." +msgstr "This command allows you apply access lists to a chosen interface to filter the RIP path." + +#: ../../configuration/protocols/babel.rst:184 +msgid "This command allows you apply prefix lists to a chosen interface to filter the Babel routes." +msgstr "This command allows you apply prefix lists to a chosen interface to filter the Babel routes." + +#: ../../configuration/protocols/rip.rst:101 +msgid "This command allows you apply prefix lists to a chosen interface to filter the RIP path." +msgstr "This command allows you apply prefix lists to a chosen interface to filter the RIP path." + +#: ../../configuration/interfaces/pppoe.rst:91 +msgid "This command allows you to select a specific access concentrator when you know the access concentrators `<name>`." +msgstr "This command allows you to select a specific access concentrator when you know the access concentrators `<name>`." + +#: ../../configuration/protocols/bgp.rst:552 +msgid "This command applies route-map to selectively unsuppress prefixes suppressed by summarisation." +msgstr "This command applies route-map to selectively unsuppress prefixes suppressed by summarisation." + +#: ../../configuration/protocols/bgp.rst:867 +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 "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." + +#: ../../configuration/protocols/bgp.rst:843 +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 "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." + +#: ../../configuration/protocols/bgp.rst:851 +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 "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." + +#: ../../configuration/protocols/bgp.rst:859 +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 "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." + +#: ../../configuration/protocols/bgp.rst:496 +msgid "This command bind specific peer to peer group with a given name." +msgstr "This command bind specific peer to peer group with a given name." + +#: ../../configuration/protocols/babel.rst:167 +msgid "This command can be used to filter the Babel routes using access lists. :cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the access lists are applied." +msgstr "This command can be used to filter the Babel routes using access lists. :cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the access lists are applied." + +#: ../../configuration/protocols/babel.rst:178 +msgid "This command can be used to filter the Babel routes using prefix lists. :cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the prefix lists are applied." +msgstr "This command can be used to filter the Babel routes using prefix lists. :cfgcmd:`in` and :cfgcmd:`out` this is the direction in which the prefix lists are applied." + +#: ../../configuration/protocols/rip.rst:84 +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 "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." + +#: ../../configuration/protocols/rip.rst:95 +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 "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." + +#: ../../configuration/protocols/rip.rst:74 +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 "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." + +#: ../../configuration/protocols/bgp.rst:652 +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 "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." + +#: ../../configuration/protocols/ospf.rst:88 +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 "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." + +#: ../../configuration/protocols/ospf.rst:82 +msgid "This command change distance value of OSPF globally. The distance range is 1 to 255." +msgstr "This command change distance value of OSPF globally. The distance range is 1 to 255." + +#: ../../configuration/protocols/ospf.rst:1115 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1109 +msgid "This command change distance value of OSPFv3 globally. The distance range is 1 to 255." +msgstr "This command change distance value of OSPFv3 globally. The distance range is 1 to 255." + +#: ../../configuration/protocols/rip.rst:62 +msgid "This command change the distance value of RIP. The distance range is 1 to 255." +msgstr "This command change the distance value of RIP. The distance range is 1 to 255." + +#: ../../configuration/protocols/bgp.rst:638 +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 "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." + +#: ../../configuration/protocols/isis.rst:171 +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 "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." + +#: ../../configuration/protocols/isis.rst:196 +msgid "This command configures the authentication password for the interface." +msgstr "This command configures the authentication password for the interface." + +#: ../../configuration/protocols/isis.rst:93 +msgid "This command configures the maximum size of generated :abbr:`LSPs (Link State PDUs)`, in bytes. The size range is 128 to 4352." +msgstr "This command configures the maximum size of generated :abbr:`LSPs (Link State PDUs)`, in bytes. The size range is 128 to 4352." + +#: ../../configuration/protocols/isis.rst:191 +msgid "This command configures the passive mode for this interface." +msgstr "This command configures the passive mode for this interface." + +#: ../../configuration/protocols/bgp.rst:191 +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 "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." + +#: ../../configuration/policy/route-map.rst:17 +msgid "This command creates a new route-map policy, identified by <text>." +msgstr "This command creates a new route-map policy, identified by <text>." + +#: ../../configuration/policy/access-list.rst:58 +msgid "This command creates a new rule in the IPv6 access list and defines an action." +msgstr "This command creates a new rule in the IPv6 access list and defines an action." + +#: ../../configuration/policy/prefix-list.rst:62 +msgid "This command creates a new rule in the IPv6 prefix-list and defines an action." +msgstr "This command creates a new rule in the IPv6 prefix-list and defines an action." + +#: ../../configuration/policy/access-list.rst:30 +msgid "This command creates a new rule in the access list and defines an action." +msgstr "This command creates a new rule in the access list and defines an action." + +#: ../../configuration/policy/prefix-list.rst:31 +msgid "This command creates a new rule in the prefix-list and defines an action." +msgstr "This command creates a new rule in the prefix-list and defines an action." + +#: ../../configuration/policy/access-list.rst:50 +msgid "This command creates the new IPv6 access list, identified by <text>" +msgstr "This command creates the new IPv6 access list, identified by <text>" + +#: ../../configuration/policy/prefix-list.rst:54 +msgid "This command creates the new IPv6 prefix-list policy, identified by <text>." +msgstr "This command creates the new IPv6 prefix-list policy, identified by <text>." + +#: ../../configuration/policy/access-list.rst:20 +msgid "This command creates the new access list policy, where <acl_number> must be a number from 1 to 2699." +msgstr "This command creates the new access list policy, where <acl_number> must be a number from 1 to 2699." + +#: ../../configuration/policy/prefix-list.rst:23 +msgid "This command creates the new prefix-list policy, identified by <text>." +msgstr "This command creates the new prefix-list policy, identified by <text>." + +#: ../../configuration/protocols/bgp.rst:486 +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 "This command defines a new peer group. You can specify to the group the same parameters that you can specify for specific neighbors." + +#: ../../configuration/policy/access-list.rst:64 +msgid "This command defines matching parameters for IPv6 access list rule. Matching criteria could be applied to source parameters:" +msgstr "This command defines matching parameters for IPv6 access list rule. Matching criteria could be applied to source parameters:" + +#: ../../configuration/policy/access-list.rst:35 +msgid "This command defines matching parameters for access list rule. Matching criteria could be applied to destination or source parameters:" +msgstr "This command defines matching parameters for access list rule. Matching criteria could be applied to destination or source parameters:" + +#: ../../configuration/protocols/isis.rst:85 +msgid "This command defines the IS-IS router behavior:" +msgstr "This command defines the IS-IS router behavior:" + +#: ../../configuration/protocols/bgp.rst:720 +msgid "This command defines the accumulated penalty amount at which the route is re-advertised. The penalty range is 1 to 20000." +msgstr "This command defines the accumulated penalty amount at which the route is re-advertised. The penalty range is 1 to 20000." + +#: ../../configuration/protocols/bgp.rst:726 +msgid "This command defines the accumulated penalty amount at which the route is suppressed. The penalty range is 1 to 20000." +msgstr "This command defines the accumulated penalty amount at which the route is suppressed. The penalty range is 1 to 20000." + +#: ../../configuration/protocols/bgp.rst:713 +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 "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." + +#: ../../configuration/protocols/bgp.rst:595 +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 "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." + +#: ../../configuration/protocols/bgp.rst:732 +msgid "This command defines the maximum time in minutes that a route is suppressed. The timer range is 1 to 255 minutes." +msgstr "This command defines the maximum time in minutes that a route is suppressed. The timer range is 1 to 255 minutes." + +#: ../../configuration/protocols/bgp.rst:246 +msgid "This command disable the peer or peer group. To reenable the peer use the delete form of this command." +msgstr "This command disable the peer or peer group. To reenable the peer use the delete form of this command." + +#: ../../configuration/protocols/isis.rst:218 +#: ../../configuration/protocols/ospf.rst:465 +msgid "This command disables IGP-LDP sync for this specific interface." +msgstr "This command disables IGP-LDP sync for this specific interface." + +#: ../../configuration/protocols/isis.rst:213 +msgid "This command disables Three-Way Handshake for P2P adjacencies which described in :rfc:`5303`. Three-Way Handshake is enabled by default." +msgstr "This command disables Three-Way Handshake for P2P adjacencies which described in :rfc:`5303`. Three-Way Handshake is enabled by default." + +#: ../../configuration/protocols/ospf.rst:426 +#: ../../configuration/protocols/ospf.rst:1165 +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 "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." + +#: ../../configuration/protocols/ospf.rst:524 +#: ../../configuration/protocols/ospf.rst:1236 +msgid "This command disables it." +msgstr "This command disables it." + +#: ../../configuration/protocols/bgp.rst:607 +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 "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." + +#: ../../configuration/protocols/rip.rst:181 +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 "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" + +#: ../../configuration/protocols/bgp.rst:1008 +msgid "This command displays BGP dampened routes." +msgstr "This command displays BGP dampened routes." + +#: ../../configuration/protocols/bgp.rst:1031 +msgid "This command displays BGP received-routes that are accepted after filtering." +msgstr "This command displays BGP received-routes that are accepted after filtering." + +#: ../../configuration/protocols/bgp.rst:1021 +msgid "This command displays BGP routes advertised to a neighbor." +msgstr "This command displays BGP routes advertised to a neighbor." + +#: ../../configuration/protocols/bgp.rst:1016 +msgid "This command displays BGP routes allowed by the specified AS Path access list." +msgstr "This command displays BGP routes allowed by the specified AS Path access list." + +#: ../../configuration/protocols/bgp.rst:1025 +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 "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." + +#: ../../configuration/protocols/ospf.rst:830 +msgid "This command displays LSAs in MaxAge list." +msgstr "This command displays LSAs in MaxAge list." + +#: ../../configuration/protocols/rip.rst:197 +msgid "This command displays RIP routes." +msgstr "This command displays RIP routes." + +#: ../../configuration/protocols/ospf.rst:785 +#: ../../configuration/protocols/ospf.rst:1304 +msgid "This command displays a database contents for a specific link advertisement type." +msgstr "This command displays a database contents for a specific link advertisement type." + +#: ../../configuration/protocols/ospf.rst:752 +#: ../../configuration/protocols/ospf.rst:1299 +msgid "This command displays a summary table with a database contents (LSA)." +msgstr "This command displays a summary table with a database contents (LSA)." + +#: ../../configuration/protocols/ospf.rst:747 +#: ../../configuration/protocols/ospf.rst:1294 +msgid "This command displays a table of paths to area boundary and autonomous system boundary routers." +msgstr "This command displays a table of paths to area boundary and autonomous system boundary routers." + +#: ../../configuration/protocols/bgp.rst:957 +msgid "This command displays all entries in BGP routing table." +msgstr "This command displays all entries in BGP routing table." + +#: ../../configuration/protocols/bgp.rst:1035 +msgid "This command displays dampened routes received from BGP neighbor." +msgstr "This command displays dampened routes received from BGP neighbor." + +#: ../../configuration/protocols/ospf.rst:1309 +msgid "This command displays external information redistributed into OSPFv3" +msgstr "This command displays external information redistributed into OSPFv3" + +#: ../../configuration/protocols/bgp.rst:1039 +msgid "This command displays information about BGP routes whose AS path matches the specified regular expression." +msgstr "This command displays information about BGP routes whose AS path matches the specified regular expression." + +#: ../../configuration/protocols/bgp.rst:1012 +msgid "This command displays information about flapping BGP routes." +msgstr "This command displays information about flapping BGP routes." + +#: ../../configuration/protocols/bgp.rst:976 +msgid "This command displays information about the particular entry in the BGP routing table." +msgstr "This command displays information about the particular entry in the BGP routing table." + +#: ../../configuration/protocols/bgp.rst:1003 +msgid "This command displays routes that are permitted by the BGP community list." +msgstr "This command displays routes that are permitted by the BGP community list." + +#: ../../configuration/protocols/bgp.rst:996 +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 "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." + +#: ../../configuration/protocols/bgp.rst:992 +msgid "This command displays routes with classless interdomain routing (CIDR)." +msgstr "This command displays routes with classless interdomain routing (CIDR)." + +#: ../../configuration/protocols/ospf.rst:672 +msgid "This command displays state and configuration of OSPF the specified interface, or all interfaces if no interface is given." +msgstr "This command displays state and configuration of OSPF the specified interface, or all interfaces if no interface is given." + +#: ../../configuration/protocols/ospf.rst:1283 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1289 +msgid "This command displays the OSPF routing table, as determined by the most recent SPF calculation." +msgstr "This command displays the OSPF routing table, as determined by the most recent SPF calculation." + +#: ../../configuration/protocols/ospf.rst:703 +msgid "This command displays the OSPF routing table, as determined by the most recent SPF calculation. With the optional :cfgcmd:`detail` argument, each route item's advertiser router and network attribute will be shown." +msgstr "This command displays the OSPF routing table, as determined by the most recent SPF calculation. With the optional :cfgcmd:`detail` argument, each route item's advertiser router and network attribute will be shown." + +#: ../../configuration/protocols/ospf.rst:1279 +msgid "This command displays the neighbor DR choice information." +msgstr "This command displays the neighbor DR choice information." + +#: ../../configuration/protocols/ospf.rst:623 +#: ../../configuration/protocols/ospf.rst:1274 +msgid "This command displays the neighbors information in a detailed form, not just a summary table." +msgstr "This command displays the neighbors information in a detailed form, not just a summary table." + +#: ../../configuration/protocols/ospf.rst:662 +msgid "This command displays the neighbors information in a detailed form for a neighbor whose IP address is specified." +msgstr "This command displays the neighbors information in a detailed form for a neighbor whose IP address is specified." + +#: ../../configuration/protocols/ospf.rst:613 +#: ../../configuration/protocols/ospf.rst:1270 +msgid "This command displays the neighbors status." +msgstr "This command displays the neighbors status." + +#: ../../configuration/protocols/ospf.rst:667 +msgid "This command displays the neighbors status for a neighbor on the specified interface." +msgstr "This command displays the neighbors status for a neighbor on the specified interface." + +#: ../../configuration/protocols/bgp.rst:1044 +msgid "This command displays the status of all BGP connections." +msgstr "This command displays the status of all BGP connections." + +#: ../../configuration/protocols/ospf.rst:487 +msgid "This command enable/disables summarisation for the configured address range." +msgstr "This command enable/disables summarisation for the configured address range." + +#: ../../configuration/protocols/bgp.rst:603 +msgid "This command enable logging neighbor up/down changes and reset reason." +msgstr "This command enable logging neighbor up/down changes and reset reason." + +#: ../../configuration/protocols/isis.rst:70 +msgid "This command enables IS-IS on this interface, and allows for adjacency to occur. Note that the name of IS-IS instance must be the same as the one used to configure the IS-IS process." +msgstr "This command enables IS-IS on this interface, and allows for adjacency to occur. Note that the name of IS-IS instance must be the same as the one used to configure the IS-IS process." + +#: ../../configuration/protocols/rip.rst:27 +msgid "This command enables RIP and sets the RIP enable interface by NETWORK. The interfaces which have addresses matching with NETWORK are enabled." +msgstr "This command enables RIP and sets the RIP enable interface by NETWORK. The interfaces which have addresses matching with NETWORK are enabled." + +#: ../../configuration/protocols/ospf.rst:421 +msgid "This command enables :abbr:`BFD (Bidirectional Forwarding Detection)` on this OSPF link interface." +msgstr "This command enables :abbr:`BFD (Bidirectional Forwarding Detection)` on this OSPF link interface." + +#: ../../configuration/protocols/isis.rst:106 +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 "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." + +#: ../../configuration/protocols/rip.rst:187 +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 "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." + +#: ../../configuration/protocols/babel.rst:34 +msgid "This command enables routing using radio frequency diversity. This is highly recommended in networks with many wireless nodes." +msgstr "This command enables routing using radio frequency diversity. This is highly recommended in networks with many wireless nodes." + +#: ../../configuration/protocols/babel.rst:137 +msgid "This command enables sending timestamps with each Hello and IHU message in order to compute RTT values. It is recommended to enable timestamps on tunnel interfaces." +msgstr "This command enables sending timestamps with each Hello and IHU message in order to compute RTT values. It is recommended to enable timestamps on tunnel interfaces." + +#: ../../configuration/protocols/isis.rst:79 +msgid "This command enables support for dynamic hostname TLV. Dynamic hostname mapping determined as described in :rfc:`2763`, Dynamic Hostname Exchange Mechanism for IS-IS." +msgstr "This command enables support for dynamic hostname TLV. Dynamic hostname mapping determined as described in :rfc:`2763`, Dynamic Hostname Exchange Mechanism for IS-IS." + +#: ../../configuration/protocols/bgp.rst:875 +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 "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." + +#: ../../configuration/protocols/bgp.rst:467 +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 "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`." + +#: ../../configuration/protocols/bgp.rst:310 +msgid "This command forces strictly compare remote capabilities and local capabilities. If capabilities are different, send Unsupported Capability error then reset connection." +msgstr "This command forces strictly compare remote capabilities and local capabilities. If capabilities are different, send Unsupported Capability error then reset connection." + +#: ../../configuration/protocols/bgp.rst:367 +msgid "This command forces the BGP speaker to report itself as the next hop for an advertised route it advertised to a neighbor." +msgstr "This command forces the BGP speaker to report itself as the next hop for an advertised route it advertised to a neighbor." + +#: ../../configuration/protocols/rip.rst:80 +msgid "This command generate a default route into the RIP." +msgstr "This command generate a default route into the RIP." + +#: ../../configuration/interfaces/wireless.rst:484 +msgid "This command gives a brief status overview of a specified wireless interface. The wireless interface identifier can range from wlan0 to wlan999." +msgstr "This command gives a brief status overview of a specified wireless interface. The wireless interface identifier can range from wlan0 to wlan999." + +#: ../../configuration/protocols/bgp.rst:632 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:133 +#: ../../configuration/interfaces/sstp-client.rst:55 +msgid "This command got added in VyOS 1.4 and inverts the logic from the old ``default-route`` CLI option." +msgstr "This command got added in VyOS 1.4 and inverts the logic from the old ``default-route`` CLI option." + +#: ../../configuration/protocols/ospf.rst:300 +#: ../../configuration/protocols/ospf.rst:1132 +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 "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." + +#: ../../configuration/protocols/ospf.rst:37 +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 "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." + +#: ../../configuration/protocols/bgp.rst:349 +#: ../../configuration/protocols/bgp.rst:451 +msgid "This command is only allowed for eBGP peers." +msgstr "This command is only allowed for eBGP peers." + +#: ../../configuration/protocols/bgp.rst:334 +msgid "This command is only allowed for eBGP peers. It is not applicable for peer groups." +msgstr "This command is only allowed for eBGP peers. It is not applicable for peer groups." + +#: ../../configuration/protocols/rip.rst:106 +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 "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`." + +#: ../../configuration/protocols/bgp.rst:505 +msgid "This command is used for advertising IPv4 or IPv6 networks." +msgstr "This command is used for advertising IPv4 or IPv6 networks." + +#: ../../configuration/interfaces/wireless.rst:511 +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 "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." + +#: ../../configuration/protocols/bgp.rst:620 +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 "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." + +#: ../../configuration/protocols/rip.rst:158 +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 "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`." + +#: ../../configuration/protocols/bgp.rst:340 +msgid "This command override AS number of the originating router with the local AS number." +msgstr "This command override AS number of the originating router with the local AS number." + +#: ../../configuration/protocols/bgp.rst:885 +msgid "This command prevents from sending back prefixes learned from the neighbor." +msgstr "This command prevents from sending back prefixes learned from the neighbor." + +#: ../../configuration/protocols/bgp.rst:804 +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 "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." + +#: ../../configuration/protocols/bgp.rst:741 +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 "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." + +#: ../../configuration/protocols/isis.rst:231 +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 "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." + +#: ../../configuration/protocols/isis.rst:237 +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 "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." + +#: ../../configuration/protocols/rip.rst:140 +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 "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." + +#: ../../configuration/protocols/bgp.rst:562 +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 "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." + +#: ../../configuration/protocols/babel.rst:158 +msgid "This command redistributes routing information from the given route source to the Babel process." +msgstr "This command redistributes routing information from the given route source to the Babel process." + +#: ../../configuration/protocols/ospf.rst:568 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1253 +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 "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." + +#: ../../configuration/protocols/bgp.rst:373 +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 "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." + +#: ../../configuration/protocols/bgp.rst:1067 +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 "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." + +#: ../../configuration/protocols/bgp.rst:1087 +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 "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." + +#: ../../configuration/protocols/bgp.rst:1074 +msgid "This command resets all BGP connections of given router." +msgstr "This command resets all BGP connections of given router." + +#: ../../configuration/protocols/bgp.rst:1083 +msgid "This command resets all external BGP peers of given router." +msgstr "This command resets all external BGP peers of given router." + +#: ../../configuration/protocols/ospf.rst:119 +msgid "This command selects ABR model. OSPF router supports four ABR models:" +msgstr "This command selects ABR model. OSPF router supports four ABR models:" + +#: ../../configuration/protocols/isis.rst:178 +msgid "This command set default metric for circuit." +msgstr "This command set default metric for circuit." + +#: ../../configuration/protocols/babel.rst:143 +msgid "This command set the channel number that diversity routing uses for this interface (see diversity option above)." +msgstr "This command set the channel number that diversity routing uses for this interface (see diversity option above)." + +#: ../../configuration/protocols/isis.rst:114 +msgid "This command sets ATT bit to 1 in Level1 LSPs. It is described in :rfc:`3787`." +msgstr "This command sets ATT bit to 1 in Level1 LSPs. It is described in :rfc:`3787`." + +#: ../../configuration/protocols/isis.rst:275 +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 "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." + +#: ../../configuration/protocols/isis.rst:266 +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 "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." + +#: ../../configuration/protocols/ospf.rst:368 +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 "This command sets OSPF authentication key to a simple password. After setting, all OSPF packets are authenticated. Key has length up to 8 chars." + +#: ../../configuration/protocols/isis.rst:207 +msgid "This command sets PSNP interval in seconds. The interval range is 0 to 127." +msgstr "This command sets PSNP interval in seconds. The interval range is 0 to 127." + +#: ../../configuration/protocols/ospf.rst:443 +#: ../../configuration/protocols/ospf.rst:1180 +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 "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." + +#: ../../configuration/protocols/rip.rst:69 +msgid "This command sets default RIP distance to a specified value when the routes source IP address matches the specified prefix." +msgstr "This command sets default RIP distance to a specified value when the routes source IP address matches the specified prefix." + +#: ../../configuration/protocols/isis.rst:160 +msgid "This command sets hello interval in seconds on a given interface. The range is 1 to 600." +msgstr "This command sets hello interval in seconds on a given interface. The range is 1 to 600." + +#: ../../configuration/protocols/ospf.rst:391 +#: ../../configuration/protocols/ospf.rst:1143 +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 "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." + +#: ../../configuration/protocols/isis.rst:284 +msgid "This command sets minimum interval between consecutive SPF calculations in seconds.The interval range is 1 to 120." +msgstr "This command sets minimum interval between consecutive SPF calculations in seconds.The interval range is 1 to 120." + +#: ../../configuration/protocols/isis.rst:261 +msgid "This command sets minimum interval in seconds between regenerating same LSP. The interval range is 1 to 120." +msgstr "This command sets minimum interval in seconds between regenerating same LSP. The interval range is 1 to 120." + +#: ../../configuration/protocols/isis.rst:166 +msgid "This command sets multiplier for hello holding time on a given interface. The range is 2 to 100." +msgstr "This command sets multiplier for hello holding time on a given interface. The range is 2 to 100." + +#: ../../configuration/protocols/ospf.rst:458 +#: ../../configuration/protocols/ospf.rst:1202 +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 "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." + +#: ../../configuration/protocols/ospf.rst:451 +#: ../../configuration/protocols/ospf.rst:1194 +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 "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." + +#: ../../configuration/protocols/isis.rst:98 +msgid "This command sets old-style (ISO 10589) or new style packet formats:" +msgstr "This command sets old-style (ISO 10589) or new style packet formats:" + +#: ../../configuration/protocols/bgp.rst:944 +msgid "This command sets other confederations <nsubasn> as members of autonomous system specified by :cfgcmd:`confederation identifier <asn>`." +msgstr "This command sets other confederations <nsubasn> as members of autonomous system specified by :cfgcmd:`confederation identifier <asn>`." + +#: ../../configuration/protocols/isis.rst:118 +msgid "This command sets overload bit to avoid any transit traffic through this router. It is described in :rfc:`3787`." +msgstr "This command sets overload bit to avoid any transit traffic through this router. It is described in :rfc:`3787`." + +#: ../../configuration/protocols/isis.rst:200 +msgid "This command sets priority for the interface for :abbr:`DIS (Designated Intermediate System)` election. The priority range is 0 to 127." +msgstr "This command sets priority for the interface for :abbr:`DIS (Designated Intermediate System)` election. The priority range is 0 to 127." + +#: ../../configuration/protocols/bgp.rst:659 +msgid "This command sets the administrative distance for a particular route. The distance range is 1 to 255." +msgstr "This command sets the administrative distance for a particular route. The distance range is 1 to 255." + +#: ../../configuration/protocols/ospf.rst:239 +msgid "This command sets the cost of default-summary LSAs announced to stubby areas. The cost range is 0 to 16777215." +msgstr "This command sets the cost of default-summary LSAs announced to stubby areas. The cost range is 0 to 16777215." + +#: ../../configuration/protocols/ospf.rst:262 +msgid "This command sets the default cost of LSAs announced to NSSA areas. The cost range is 0 to 16777215." +msgstr "This command sets the default cost of LSAs announced to NSSA areas. The cost range is 0 to 16777215." + +#: ../../configuration/protocols/ospf.rst:183 +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 "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." + +#: ../../configuration/protocols/ospf.rst:386 +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 "This command sets the interface bandwidth for cost calculations, where bandwidth can be in range from 1 to 100000, specified in Mbits/s." + +#: ../../configuration/protocols/babel.rst:67 +msgid "This command sets the interface type:" +msgstr "This command sets the interface type:" + +#: ../../configuration/protocols/rip.rst:176 +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 "This command sets the interface with RIP MD5 authentication. This command also sets MD5 Key. The key must be shorter than 16 characters." + +#: ../../configuration/protocols/rip.rst:170 +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 "This command sets the interface with RIP simple password authentication. This command also sets authentication string. The string must be shorter than 16 characters." + +#: ../../configuration/protocols/babel.rst:42 +msgid "This command sets the multiplicative factor used for diversity routing, in units of 1/256; lower values cause diversity to play a more important role in route selection. The default it 256, which means that diversity plays no role in route selection; you will probably want to set that to 128 or less on nodes with multiple independent radios." +msgstr "This command sets the multiplicative factor used for diversity routing, in units of 1/256; lower values cause diversity to play a more important role in route selection. The default it 256, which means that diversity plays no role in route selection; you will probably want to set that to 128 or less on nodes with multiple independent radios." + +#: ../../configuration/protocols/ospf.rst:52 +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 "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)." + +#: ../../configuration/protocols/ospf.rst:60 +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 "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!" + +#: ../../configuration/protocols/ospf.rst:1095 +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 "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!" + +#: ../../configuration/protocols/rip.rst:47 +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 "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." + +#: ../../configuration/protocols/ospf.rst:147 +msgid "This command should NOT be set normally." +msgstr "This command should NOT be set normally." + +#: ../../configuration/interfaces/wireless.rst:463 +msgid "This command shows both status and statistics on the specified wireless interface. The wireless interface identifier can range from wlan0 to wlan999." +msgstr "This command shows both status and statistics on the specified wireless interface. The wireless interface identifier can range from wlan0 to wlan999." + +#: ../../configuration/protocols/bgp.rst:938 +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 "This command specifies a BGP confederation identifier. <asn> is the number of the autonomous system that internally includes multiple sub-autonomous systems (a confederation)." + +#: ../../configuration/protocols/babel.rst:25 +msgid "This command specifies a Babel enabled interface by interface name. Both the sending and receiving of Babel packets will be enabled on the interface specified in this command." +msgstr "This command specifies a Babel enabled interface by interface name. Both the sending and receiving of Babel packets will be enabled on the interface specified in this command." + +#: ../../configuration/protocols/bgp.rst:461 +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 "This command specifies a MD5 password to be used with the tcp socket that is being used to connect to the remote peer." + +#: ../../configuration/protocols/rip.rst:32 +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 "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." + +#: ../../configuration/protocols/rip.rst:38 +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 "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." + +#: ../../configuration/protocols/bgp.rst:404 +msgid "This command specifies a default weight value for the neighbor’s routes. The number range is 1 to 65535." +msgstr "This command specifies a default weight value for the neighbor’s routes. The number range is 1 to 65535." + +#: ../../configuration/protocols/bgp.rst:360 +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 "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." + +#: ../../configuration/protocols/ospf.rst:161 +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 "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." + +#: ../../configuration/protocols/rip.rst:54 +msgid "This command specifies all interfaces to passive mode." +msgstr "This command specifies all interfaces to passive mode." + +#: ../../configuration/protocols/bgp.rst:532 +msgid "This command specifies an aggregate address. The router will also announce longer-prefixes inside of the aggregate address." +msgstr "This command specifies an aggregate address. The router will also announce longer-prefixes inside of the aggregate address." + +#: ../../configuration/protocols/bgp.rst:545 +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 "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." + +#: ../../configuration/protocols/bgp.rst:538 +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 "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." + +#: ../../configuration/protocols/bgp.rst:354 +msgid "This command specifies attributes to be left unchanged for advertisements sent to a peer or peer group." +msgstr "This command specifies attributes to be left unchanged for advertisements sent to a peer or peer group." + +#: ../../configuration/protocols/isis.rst:151 +msgid "This command specifies circuit type for interface:" +msgstr "This command specifies circuit type for interface:" + +#: ../../configuration/protocols/bgp.rst:920 +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 "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." + +#: ../../configuration/protocols/bgp.rst:671 +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 "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." + +#: ../../configuration/protocols/ospf.rst:151 +#: ../../configuration/protocols/ospf.rst:1187 +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 "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)." + +#: ../../configuration/protocols/bgp.rst:677 +msgid "This command specifies keep-alive time in seconds. The timer can range from 4 to 65535. The default value is 60 second." +msgstr "This command specifies keep-alive time in seconds. The timer can range from 4 to 65535. The default value is 60 second." + +#: ../../configuration/protocols/bgp.rst:569 +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 "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." + +#: ../../configuration/protocols/rip.rst:146 +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 "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." + +#: ../../configuration/protocols/ospf.rst:579 +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 "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." + +#: ../../configuration/protocols/isis.rst:244 +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 "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." + +#: ../../configuration/protocols/ospf.rst:585 +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 "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." + +#: ../../configuration/protocols/isis.rst:186 +msgid "This command specifies network type to Point-to-Point. The default network type is broadcast." +msgstr "This command specifies network type to Point-to-Point. The default network type is broadcast." + +#: ../../configuration/protocols/bgp.rst:784 +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 "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." + +#: ../../configuration/protocols/bgp.rst:754 +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 "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." + +#: ../../configuration/protocols/bgp.rst:791 +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 "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." + +#: ../../configuration/protocols/bgp.rst:392 +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 "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." + +#: ../../configuration/protocols/ospf.rst:278 +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 "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." + +#: ../../configuration/protocols/bgp.rst:423 +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 "This command specifies that the community attribute should not be sent in route updates to a peer. By default community attribute is sent." + +#: ../../configuration/protocols/bgp.rst:748 +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 "This command specifies that the length of confederation path sets and sequences should be taken into account during the BGP best path decision process." + +#: ../../configuration/protocols/ospf.rst:547 +msgid "This command specifies the IP address of the neighboring device." +msgstr "This command specifies the IP address of the neighboring device." + +#: ../../configuration/protocols/ospf.rst:32 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1088 +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 "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." + +#: ../../configuration/protocols/ospf.rst:253 +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 "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." + +#: ../../configuration/protocols/ospf.rst:244 +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 "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." + +#: ../../configuration/protocols/ospf.rst:222 +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 "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." + +#: ../../configuration/protocols/ospf.rst:231 +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 "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." + +#: ../../configuration/protocols/babel.rst:104 +msgid "This command specifies the base receive cost for this interface. For wireless interfaces, it specifies the multiplier used for computing the ETX reception cost (default 256); for wired interfaces, it specifies the cost that will be advertised to neighbours." +msgstr "This command specifies the base receive cost for this interface. For wireless interfaces, it specifies the multiplier used for computing the ETX reception cost (default 256); for wired interfaces, it specifies the cost that will be advertised to neighbours." + +#: ../../configuration/protocols/babel.rst:112 +msgid "This command specifies the decay factor for the exponential moving average of RTT samples, in units of 1/256. Higher values discard old samples faster. The default is 42." +msgstr "This command specifies the decay factor for the exponential moving average of RTT samples, in units of 1/256. Higher values discard old samples faster. The default is 42." + +#: ../../configuration/protocols/bgp.rst:799 +msgid "This command specifies the default local preference value. The local preference range is 0 to 4294967295." +msgstr "This command specifies the default local preference value. The local preference range is 0 to 4294967295." + +#: ../../configuration/protocols/ospf.rst:574 +msgid "This command specifies the default metric value of redistributed routes. The metric range is 0 to 16777214." +msgstr "This command specifies the default metric value of redistributed routes. The metric range is 0 to 16777214." + +#: ../../configuration/protocols/rip.rst:129 +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 "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." + +#: ../../configuration/protocols/bgp.rst:916 +msgid "This command specifies the given neighbor as route reflector client." +msgstr "This command specifies the given neighbor as route reflector client." + +#: ../../configuration/protocols/ospf.rst:551 +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 "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." + +#: ../../configuration/protocols/babel.rst:124 +msgid "This command specifies the maximum RTT, in milliseconds, above which we don't increase the cost to a neighbour. The default is 120 ms." +msgstr "This command specifies the maximum RTT, in milliseconds, above which we don't increase the cost to a neighbour. The default is 120 ms." + +#: ../../configuration/protocols/babel.rst:130 +msgid "This command specifies the maximum cost added to a neighbour because of RTT, i.e. when the RTT is higher or equal than rtt-max. The default is 150. Setting it to 0 effectively disables the use of a RTT-based cost." +msgstr "This command specifies the maximum cost added to a neighbour because of RTT, i.e. when the RTT is higher or equal than rtt-max. The default is 150. Setting it to 0 effectively disables the use of a RTT-based cost." + +#: ../../configuration/protocols/babel.rst:118 +msgid "This command specifies the minimum RTT, in milliseconds, starting from which we increase the cost to a neighbour. The additional cost is linear in (rtt - rtt-min). The default is 10 ms." +msgstr "This command specifies the minimum RTT, in milliseconds, starting from which we increase the cost to a neighbour. The additional cost is linear in (rtt - rtt-min). The default is 10 ms." + +#: ../../configuration/protocols/bgp.rst:410 +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 "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." + +#: ../../configuration/protocols/bgp.rst:589 +msgid "This command specifies the router-ID. If router ID is not specified it will use the highest interface IP address." +msgstr "This command specifies the router-ID. If router ID is not specified it will use the highest interface IP address." + +#: ../../configuration/protocols/ospf.rst:558 +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 "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." + +#: ../../configuration/protocols/babel.rst:56 +msgid "This command specifies the time constant, in seconds, of the smoothing algorithm used for implementing hysteresis. Larger values reduce route oscillation at the cost of very slightly increasing convergence time. The value 0 disables hysteresis, and is suitable for wired networks. The default is 4 s." +msgstr "This command specifies the time constant, in seconds, of the smoothing algorithm used for implementing hysteresis. Larger values reduce route oscillation at the cost of very slightly increasing convergence time. The value 0 disables hysteresis, and is suitable for wired networks. The default is 4 s." + +#: ../../configuration/protocols/babel.rst:51 +msgid "This command specifies the time in milliseconds after which an 'important' request or update will be resent. The default is 2000 ms." +msgstr "This command specifies the time in milliseconds after which an 'important' request or update will be resent. The default is 2000 ms." + +#: ../../configuration/protocols/babel.rst:89 +msgid "This command specifies the time in milliseconds between two scheduled hellos. On wired links, Babel notices a link failure within two hello intervals; on wireless links, the link quality value is reestimated at every hello interval. The default is 4000 ms." +msgstr "This command specifies the time in milliseconds between two scheduled hellos. On wired links, Babel notices a link failure within two hello intervals; on wireless links, the link quality value is reestimated at every hello interval. The default is 4000 ms." + +#: ../../configuration/protocols/babel.rst:97 +msgid "This command specifies the time in milliseconds between two scheduled updates. Since Babel makes extensive use of triggered updates, this can be set to fairly high values on links with little packet loss. The default is 20000 ms." +msgstr "This command specifies the time in milliseconds between two scheduled updates. Since Babel makes extensive use of triggered updates, this can be set to fairly high values on links with little packet loss. The default is 20000 ms." + +#: ../../configuration/protocols/rip.rst:121 +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 "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." + +#: ../../configuration/protocols/rip.rst:114 +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 "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." + +#: ../../configuration/protocols/babel.rst:77 +msgid "This command specifies whether to perform split-horizon on the interface. Specifying no babel split-horizon is always correct, while babel split-horizon is an optimisation that should only be used on symmetric and transitive (wired) networks." +msgstr "This command specifies whether to perform split-horizon on the interface. Specifying no babel split-horizon is always correct, while babel split-horizon is an optimisation that should only be used on symmetric and transitive (wired) networks." + +#: ../../configuration/protocols/ospf.rst:284 +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 "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." + +#: ../../configuration/protocols/ospf.rst:377 +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 "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." + +#: ../../configuration/protocols/ospf.rst:1126 +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 "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." + +#: ../../configuration/protocols/ospf.rst:290 +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 "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." + +#: ../../configuration/protocols/ospf.rst:494 +msgid "This command to ensure not advertise the summary lsa for the matched external LSAs." +msgstr "This command to ensure not advertise the summary lsa for the matched external LSAs." + +#: ../../configuration/protocols/bgp.rst:1078 +msgid "This command uses to clear BGP route dampening information and to unsuppress suppressed routes." +msgstr "This command uses to clear BGP route dampening information and to unsuppress suppressed routes." + +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +#: ../../_include/interface-ipv6.txt:65 +msgid "This command was introduced in VyOS 1.4 - it was previously called: ``set firewall options interface <name> adjust-mss6 <value>``" +msgstr "This command was introduced in VyOS 1.4 - it was previously called: ``set firewall options interface <name> adjust-mss6 <value>``" + +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../configuration/interfaces/pppoe.rst:199 +#: ../../configuration/interfaces/pppoe.rst:245 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../configuration/interfaces/sstp-client.rst:84 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +#: ../../_include/interface-ip.txt:9 +msgid "This command was introduced in VyOS 1.4 - it was previously called: ``set firewall options interface <name> adjust-mss <value>``" +msgstr "This command was introduced in VyOS 1.4 - it was previously called: ``set firewall options interface <name> adjust-mss <value>``" + +#: ../../configuration/protocols/isis.rst:223 +#: ../../configuration/protocols/ospf.rst:470 +msgid "This command will change the hold down value for IGP-LDP synchronization during convergence/interface flap events, but for this interface only." +msgstr "This command will change the hold down value for IGP-LDP synchronization during convergence/interface flap events, but for this interface only." + +#: ../../configuration/protocols/isis.rst:141 +#: ../../configuration/protocols/ospf.rst:202 +msgid "This command will change the hold down value globally for IGP-LDP synchronization during convergence/interface flap events." +msgstr "This command will change the hold down value globally for IGP-LDP synchronization during convergence/interface flap events." + +#: ../../configuration/protocols/isis.rst:134 +msgid "This command will enable IGP-LDP synchronization globally for ISIS. This requires for LDP to be functional. This is described in :rfc:`5443`. By default all interfaces operational in IS-IS are enabled for synchronization. Loopbacks are exempt." +msgstr "This command will enable IGP-LDP synchronization globally for ISIS. This requires for LDP to be functional. This is described in :rfc:`5443`. By default all interfaces operational in IS-IS are enabled for synchronization. Loopbacks are exempt." + +#: ../../configuration/protocols/ospf.rst:195 +msgid "This command will enable IGP-LDP synchronization globally for OSPF. This requires for LDP to be functional. This is described in :rfc:`5443`. By default all interfaces operational in OSPF are enabled for synchronization. Loopbacks are exempt." +msgstr "This command will enable IGP-LDP synchronization globally for OSPF. This requires for LDP to be functional. This is described in :rfc:`5443`. By default all interfaces operational in OSPF are enabled for synchronization. Loopbacks are exempt." + +#: ../../configuration/protocols/isis.rst:124 +msgid "This command will generate a default-route in L1 database." +msgstr "This command will generate a default-route in L1 database." + +#: ../../configuration/protocols/isis.rst:129 +msgid "This command will generate a default-route in L2 database." +msgstr "This command will generate a default-route in L2 database." + +#: ../../configuration/firewall/general.rst:1457 +#: ../../configuration/firewall/general-legacy.rst:904 +msgid "This command will give an overview of a rule in a single rule-set" +msgstr "This command will give an overview of a rule in a single rule-set" + +#: ../../configuration/firewall/general-legacy.rst:940 +msgid "This command will give an overview of a rule in a single rule-set." +msgstr "This command will give an overview of a rule in a single rule-set." + +#: ../../configuration/firewall/general.rst:1435 +#: ../../configuration/firewall/general-legacy.rst:932 +msgid "This command will give an overview of a single rule-set." +msgstr "This command will give an overview of a single rule-set." + +#: ../../configuration/protocols/bgp.rst:268 +msgid "This command would allow the dynamic update of capabilities over an established BGP session." +msgstr "This command would allow the dynamic update of capabilities over an established BGP session." + +#: ../../configuration/interfaces/vxlan.rst:272 +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 "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." + +#: ../../configuration/protocols/isis.rst:301 +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 "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`." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:192 +msgid "This configuration enables the TCP reverse proxy for the \"my-tcp-api\" service. Incoming TCP connections on port 8888 will be load balanced across the backend servers (srv01 and srv02) using the round-robin load-balancing algorithm." +msgstr "This configuration enables the TCP reverse proxy for the \"my-tcp-api\" service. Incoming TCP connections on port 8888 will be load balanced across the backend servers (srv01 and srv02) using the round-robin load-balancing algorithm." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:174 +msgid "This configuration listen on port 80 and redirect incoming requests to HTTPS:" +msgstr "This configuration listen on port 80 and redirect incoming requests to HTTPS:" + +#: ../../configuration/protocols/bgp.rst:513 +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 "This configuration modifies the behavior of the network statement. If you have this configured the underlying network must exist in the routing table." + +#: ../../configuration/service/dhcp-server.rst:78 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:628 +msgid "This could be helpful if you want to test how an application behaves under certain network conditions." +msgstr "This could be helpful if you want to test how an application behaves under certain network conditions." + +#: ../../configuration/policy/examples.rst:67 +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 "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." + +#: ../../configuration/service/dns.rst:111 +msgid "This defaults to 10000." +msgstr "This defaults to 10000." + +#: ../../configuration/system/login.rst:254 +msgid "This defaults to 1812." +msgstr "This defaults to 1812." + +#: ../../configuration/interfaces/wireless.rst:81 +msgid "This defaults to 2007." +msgstr "This defaults to 2007." + +#: ../../configuration/service/dns.rst:258 +msgid "This defaults to 300 seconds." +msgstr "This defaults to 300 seconds." + +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +#: ../../_include/interface-ip.txt:25 +msgid "This defaults to 30 seconds." +msgstr "This defaults to 30 seconds." + +#: ../../configuration/system/login.rst:323 +msgid "This defaults to 49." +msgstr "This defaults to 49." + +#: ../../configuration/service/webproxy.rst:165 +msgid "This defaults to 5." +msgstr "This defaults to 5." + +#: ../../configuration/interfaces/l2tpv3.rst:48 +msgid "This defaults to UDP" +msgstr "This defaults to UDP" + +#: ../../configuration/interfaces/wireless.rst:101 +msgid "This defaults to phy0." +msgstr "This defaults to phy0." + +#: ../../configuration/interfaces/wireless.rst:65 +msgid "This depends on the driver capabilities and may not be available with all drivers." +msgstr "This depends on the driver capabilities and may not be available with all drivers." + +#: ../../configuration/service/conntrack-sync.rst:98 +msgid "This diable the external cache and directly injects the flow-states into the in-kernel Connection Tracking System of the backup firewall." +msgstr "This diable the external cache and directly injects the flow-states into the in-kernel Connection Tracking System of the backup firewall." + +#: ../../configuration/interfaces/wireguard.rst:17 +msgid "This diagram corresponds with the example site to site configuration below." +msgstr "This diagram corresponds with the example site to site configuration below." + +#: ../../configuration/protocols/ospf.rst:104 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:186 +msgid "This enables the greenfield option which sets the ``[GF]`` option" +msgstr "This enables the greenfield option which sets the ``[GF]`` option" + +#: ../../configuration/nat/nat44.rst:546 +msgid "This establishes our Port Forward rule, but if we created a firewall policy it will likely block the traffic." +msgstr "This establishes our Port Forward rule, but if we created a firewall policy it will likely block the traffic." + +#: ../../configuration/policy/examples.rst:189 +msgid "This example shows how to target an MSS clamp (in our example to 1360 bytes) to a specific destination IP." +msgstr "This example shows how to target an MSS clamp (in our example to 1360 bytes) to a specific destination IP." + +#: ../../configuration/protocols/ospf.rst:476 +msgid "This feature summarises originated external LSAs (Type-5 and Type-7). Summary Route will be originated on-behalf of all matched external LSAs." +msgstr "This feature summarises originated external LSAs (Type-5 and Type-7). Summary Route will be originated on-behalf of all matched external LSAs." + +#: ../../configuration/firewall/general.rst:626 +#: ../../configuration/firewall/general-legacy.rst:431 +msgid "This functions for both individual addresses and address groups." +msgstr "This functions for both individual addresses and address groups." + +#: ../../configuration/protocols/isis.rst:449 +#: ../../configuration/protocols/ospf.rst:968 +msgid "This gives us IGP-LDP synchronization for all non-loopback interfaces with a holddown timer of zero seconds:" +msgstr "This gives us IGP-LDP synchronization for all non-loopback interfaces with a holddown timer of zero seconds:" + +#: ../../configuration/protocols/isis.rst:501 +#: ../../configuration/protocols/ospf.rst:1018 +#: ../../configuration/protocols/segment-routing.rst:229 +#: ../../configuration/protocols/segment-routing.rst:312 +msgid "This gives us MPLS segment routing enabled and labels for far end loopbacks:" +msgstr "This gives us MPLS segment routing enabled and labels for far end loopbacks:" + +#: ../../configuration/protocols/isis.rst:339 +msgid "This gives us the following neighborships, Level 1 and Level 2:" +msgstr "This gives us the following neighborships, Level 1 and Level 2:" + +#: ../../configuration/vpn/dmvpn.rst:139 +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 "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." + +#: ../../configuration/nat/nat44.rst:106 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:96 +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 "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>`." + +#: ../../configuration/service/dhcp-server.rst:103 +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 "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>`." + +#: ../../configuration/service/eventhandler.rst:44 +msgid "This is a mandatory command. Sets regular expression to match against log string message." +msgstr "This is a mandatory command. Sets regular expression to match against log string message." + +#: ../../configuration/service/eventhandler.rst:55 +msgid "This is a mandatory command. Sets the full path to the script. The script file must be executable." +msgstr "This is a mandatory command. Sets the full path to the script. The script file must be executable." + +#: ../../configuration/protocols/rpki.rst:117 +#: ../../configuration/protocols/rpki.rst:124 +msgid "This is a mandatory setting." +msgstr "This is a mandatory setting." + +#: ../../configuration/trafficpolicy/index.rst:780 +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 "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." + +#: ../../configuration/vpn/dmvpn.rst:89 +msgid "This is also known as the HUBs IP address or FQDN." +msgstr "This is also known as the HUBs IP address or FQDN." + +#: ../../configuration/service/eventhandler.rst:76 +msgid "This is an optional command. Adds arguments to the script. Arguments must be separated by spaces." +msgstr "This is an optional command. Adds arguments to the script. Arguments must be separated by spaces." + +#: ../../configuration/service/eventhandler.rst:68 +msgid "This is an optional command. Adds environment and its value to the script. Use separate commands for each environment." +msgstr "This is an optional command. Adds environment and its value to the script. Use separate commands for each environment." + +#: ../../configuration/service/eventhandler.rst:64 +msgid "This is an optional command. Filters log messages by syslog-identifier." +msgstr "This is an optional command. Filters log messages by syslog-identifier." + +#: ../../configuration/service/eventhandler.rst:36 +msgid "This is an optional command because the event handler will be automatically created after any of the next commands." +msgstr "This is an optional command because the event handler will be automatically created after any of the next commands." + +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +#: ../../_include/interface-ip.txt:156 +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 "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." + +#: ../../configuration/protocols/igmp.rst:208 +msgid "This is especially useful for the upstream interface, since the source for multicast traffic is often from a remote location." +msgstr "This is especially useful for the upstream interface, since the source for multicast traffic is often from a remote location." + +#: ../../configuration/interfaces/tunnel.rst:32 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:93 +#: ../../configuration/interfaces/wireguard.rst:107 +msgid "This is optional." +msgstr "This is optional." + +#: ../../configuration/firewall/general-legacy.rst:405 +msgid "This is similar to the network groups part, but here you are able to negate the matching addresses." +msgstr "This is similar to the network groups part, but here you are able to negate the matching addresses." + +#: ../../configuration/interfaces/tunnel.rst:48 +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 "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`." + +#: ../../configuration/interfaces/l2tpv3.rst:137 +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 "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." + +#: ../../configuration/system/lcd.rst:29 +msgid "This is the LCD model used in your system." +msgstr "This is the LCD model used in your system." + +#: ../../configuration/service/dhcp-server.rst:40 +#: ../../configuration/service/dhcp-server.rst:49 +#: ../../configuration/service/dhcp-server.rst:56 +msgid "This is the configuration parameter for the entire shared network definition. All subnets will inherit this configuration item if not specified locally." +msgstr "This is the configuration parameter for the entire shared network definition. All subnets will inherit this configuration item if not specified locally." + +#: ../../configuration/service/dhcp-server.rst:232 +msgid "This is the equivalent of the host block in dhcpd.conf of isc-dhcpd." +msgstr "This is the equivalent of the host block in dhcpd.conf of isc-dhcpd." + +#: ../../configuration/system/lcd.rst:21 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:371 +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 "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.**" + +#: ../../configuration/service/dhcp-server.rst:230 +msgid "This is useful, for example, in combination with hostfile update." +msgstr "This is useful, for example, in combination with hostfile update." + +#: ../../configuration/service/broadcast-relay.rst:11 +msgid "This is where \"UDP broadcast relay\" comes into play! It will forward received broadcasts to other configured networks." +msgstr "This is where \"UDP broadcast relay\" comes into play! It will forward received broadcasts to other configured networks." + +#: ../../configuration/service/dns.rst:142 +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 "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." + +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +#: ../../_include/interface-ipv6.txt:12 +msgid "This method automatically disables IPv6 traffic forwarding on the interface in question." +msgstr "This method automatically disables IPv6 traffic forwarding on the interface in question." + +#: ../../configuration/interfaces/bonding.rst:73 +msgid "This mode provides fault tolerance." +msgstr "This mode provides fault tolerance." + +#: ../../configuration/interfaces/bonding.rst:67 +msgid "This mode provides fault tolerance. The :cfgcmd:`primary` option, documented below, affects the behavior of this mode." +msgstr "This mode provides fault tolerance. The :cfgcmd:`primary` option, documented below, affects the behavior of this mode." + +#: ../../configuration/interfaces/bonding.rst:78 +#: ../../configuration/interfaces/bonding.rst:125 +msgid "This mode provides load balancing and fault tolerance." +msgstr "This mode provides load balancing and fault tolerance." + +#: ../../configuration/interfaces/wireless.rst:107 +msgid "This option adds Power Constraint element when applicable and Country element is added. Power Constraint element is required by Transmit Power Control." +msgstr "This option adds Power Constraint element when applicable and Country element is added. Power Constraint element is required by Transmit Power Control." + +#: ../../configuration/service/dhcp-server.rst:133 +msgid "This option can be specified multiple times." +msgstr "This option can be specified multiple times." + +#: ../../configuration/protocols/igmp.rst:211 +msgid "This option can be supplied multiple times." +msgstr "This option can be supplied multiple times." + +#: ../../configuration/interfaces/wireless.rst:53 +msgid "This option is mandatory in Access-Point mode." +msgstr "This option is mandatory in Access-Point mode." + +#: ../../configuration/vpn/dmvpn.rst:96 +msgid "This option is required when running a DMVPN spoke." +msgstr "This option is required when running a DMVPN spoke." + +#: ../../configuration/system/login.rst:388 +msgid "This option must be used with ``timeout`` option." +msgstr "This option must be used with ``timeout`` option." + +#: ../../configuration/interfaces/bonding.rst:136 +#: ../../configuration/interfaces/bonding.rst:151 +msgid "This option only affects 802.3ad mode." +msgstr "This option only affects 802.3ad mode." + +#: ../../configuration/highavailability/index.rst:232 +msgid "This option specifies a delay in seconds before vrrp instances start up after keepalived starts." +msgstr "This option specifies a delay in seconds before vrrp instances start up after keepalived starts." + +#: ../../configuration/protocols/ospf.rst:326 +msgid "This parameter allows to \"shortcut\" routes (non-backbone) for inter-area routes. There are three modes available for routes shortcutting:" +msgstr "This parameter allows to \"shortcut\" routes (non-backbone) for inter-area routes. There are three modes available for routes shortcutting:" + +#: ../../configuration/interfaces/bonding.rst:194 +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 "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." + +#: ../../configuration/nat/nat44.rst:48 +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 "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`)." + +#: ../../configuration/firewall/general-legacy.rst:308 +msgid "This required setting defines the action of the current rule. If action is set to ``jump``, then ``jump-target`` is also needed." +msgstr "This required setting defines the action of the current rule. If action is set to ``jump``, then ``jump-target`` is also needed." + +#: ../../configuration/firewall/general.rst:360 +msgid "This required setting defines the action of the current rule. If action is set to jump, then jump-target is also needed." +msgstr "This required setting defines the action of the current rule. If action is set to jump, then jump-target is also needed." + +#: ../../configuration/interfaces/tunnel.rst:161 +msgid "This requires two files, one to create the device (XXX.netdev) and one to configure the network on the device (XXX.network)" +msgstr "This requires two files, one to create the device (XXX.netdev) and one to configure the network on the device (XXX.network)" + +#: ../../configuration/interfaces/bridge.rst:208 +#: ../../configuration/interfaces/bridge.rst:244 +msgid "This results in the active configuration:" +msgstr "This results in the active configuration:" + +#: ../../configuration/service/dhcp-server.rst:88 +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 "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." + +#: ../../configuration/system/name-server.rst:10 +msgid "This section describes configuring DNS on the system, namely:" +msgstr "This section describes configuring DNS on the system, namely:" + +#: ../../configuration/system/host-name.rst:7 +msgid "This section describes the system's host information and how to configure them, it covers the following topics:" +msgstr "This section describes the system's host information and how to configure them, it covers the following topics:" + +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +#: ../../_include/need_improvement.txt:11 +msgid "This section needs improvements, examples and explanations." +msgstr "This section needs improvements, examples and explanations." + +#: ../../configuration/firewall/general-legacy.rst:288 +msgid "This set the default action of the rule-set if no rule matched a packet criteria. If defacult-action is set to ``jump``, then ``default-jump-target`` is also needed." +msgstr "This set the default action of the rule-set if no rule matched a packet criteria. If defacult-action is set to ``jump``, then ``default-jump-target`` is also needed." + +#: ../../configuration/firewall/general.rst:392 +msgid "This set the default action of the rule-set if no rule matched a packet criteria. If defacult-action is set to ``jump``, then ``default-jump-target`` is also needed. Note that for base chains, default action can only be set to ``accept`` or ``drop``, while on custom chain, more actions are available." +msgstr "This set the default action of the rule-set if no rule matched a packet criteria. If defacult-action is set to ``jump``, then ``default-jump-target`` is also needed. Note that for base chains, default action can only be set to ``accept`` or ``drop``, while on custom chain, more actions are available." + +#: ../../configuration/interfaces/openvpn.rst:278 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:260 +msgid "This sets the cipher when NCP (Negotiable Crypto Parameters) is disabled or OpenVPN version < 2.4.0." +msgstr "This sets the cipher when NCP (Negotiable Crypto Parameters) is disabled or OpenVPN version < 2.4.0." + +#: ../../configuration/service/dns.rst:120 +msgid "This setting, which defaults to 3600 seconds, puts a maximum on the amount of time negative entries are cached." +msgstr "This setting, which defaults to 3600 seconds, puts a maximum on the amount of time negative entries are cached." + +#: ../../configuration/service/dns.rst:128 +msgid "This setting defaults to 1500 and is valid between 10 and 60000." +msgstr "This setting defaults to 1500 and is valid between 10 and 60000." + +#: ../../configuration/firewall/general.rst:121 +#: ../../configuration/firewall/general-legacy.rst:73 +msgid "This setting enable or disable the response of icmp broadcast messages. The following system parameter will be altered:" +msgstr "This setting enable or disable the response of icmp broadcast messages. The following system parameter will be altered:" + +#: ../../configuration/firewall/general.rst:129 +#: ../../configuration/firewall/general-legacy.rst:81 +msgid "This setting handle if VyOS accept packets with a source route option. The following system parameter will be altered:" +msgstr "This setting handle if VyOS accept packets with a source route option. The following system parameter will be altered:" + +#: ../../configuration/highavailability/index.rst:310 +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 "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:" + +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +#: ../../_include/interface-dhcpv6-options.txt:28 +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 "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." + +#: ../../configuration/protocols/ospf.rst:109 +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 "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." + +#: ../../configuration/nat/nat44.rst:409 +msgid "This technique is commonly referred to as NAT Reflection or Hairpin NAT." +msgstr "This technique is commonly referred to as NAT Reflection or Hairpin NAT." + +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +#: ../../_include/interface-ip.txt:164 +msgid "This technology is known by different names:" +msgstr "This technology is known by different names:" + +#: ../../configuration/trafficpolicy/index.rst:357 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:173 +msgid "This topology was built using GNS3." +msgstr "This topology was built using GNS3." + +#: ../../configuration/interfaces/ethernet.rst:9 +msgid "This will be the most widely used interface on a router carrying traffic to the real world." +msgstr "This will be the most widely used interface on a router carrying traffic to the real world." + +#: ../../configuration/protocols/static.rst:171 +msgid "This will configure a static ARP entry always resolving `<address>` to `<mac>` for interface `<interface>`." +msgstr "This will configure a static ARP entry always resolving `<address>` to `<mac>` for interface `<interface>`." + +#: ../../configuration/trafficpolicy/index.rst:164 +msgid "This will match TCP traffic with source port 80." +msgstr "This will match TCP traffic with source port 80." + +#: ../../configuration/service/dns.rst:282 +msgid "This will render the following ddclient_ configuration entry:" +msgstr "This will render the following ddclient_ configuration entry:" + +#: ../../configuration/firewall/general.rst:1314 +#: ../../configuration/firewall/general-legacy.rst:785 +msgid "This will show you a basic firewall overview" +msgstr "This will show you a basic firewall overview" + +#: ../../configuration/firewall/general-legacy.rst:936 +msgid "This will show you a rule-set statistic since the last boot." +msgstr "This will show you a rule-set statistic since the last boot." + +#: ../../configuration/firewall/general.rst:1479 +#: ../../configuration/firewall/general-legacy.rst:900 +msgid "This will show you a statistic of all rule-sets since the last boot." +msgstr "This will show you a statistic of all rule-sets since the last boot." + +#: ../../configuration/firewall/general.rst:1377 +#: ../../configuration/firewall/general-legacy.rst:851 +msgid "This will show you a summary of rule-sets and groups" +msgstr "This will show you a summary of rule-sets and groups" + +#: ../../configuration/trafficpolicy/index.rst:1188 +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 "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." + +#: ../../configuration/nat/nat44.rst:566 +msgid "This would generate the following configuration:" +msgstr "This would generate the following configuration:" + +#: ../../configuration/service/snmp.rst:19 +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 "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." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Time, in milliseconds, that a node assumes a neighbor is reachable after having received a reachability confirmation" +msgstr "Time, in milliseconds, that a node assumes a neighbor is reachable after having received a reachability confirmation" + +#: ../../configuration/system/time-zone.rst:5 +msgid "Time Zone" +msgstr "Time Zone" + +#: ../../configuration/system/time-zone.rst:7 +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 "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." + +#: ../../configuration/service/router-advert.rst:1 +msgid "Time in milliseconds between retransmitted Neighbor Solicitation messages" +msgstr "Time in milliseconds between retransmitted Neighbor Solicitation messages" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Time in seconds that the prefix will remain preferred (default 4 hours)" +msgstr "Time in seconds that the prefix will remain preferred (default 4 hours)" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Time in seconds that the prefix will remain valid (default: 30 days)" +msgstr "Time in seconds that the prefix will remain valid (default: 30 days)" + +#: ../../configuration/service/webproxy.rst:177 +msgid "Time is in minutes and defaults to 60." +msgstr "Time is in minutes and defaults to 60." + +#: ../../configuration/firewall/general.rst:1211 +#: ../../configuration/firewall/general-legacy.rst:722 +#: ../../configuration/policy/route.rst:225 +msgid "Time to match the defined rule." +msgstr "Time to match the defined rule." + +#: ../../configuration/protocols/failover.rst:24 +msgid "Timeout in seconds between health target checks." +msgstr "Timeout in seconds between health target checks." + +#: ../../configuration/vpn/sstp.rst:223 +msgid "Timeout to wait reply for Interim-Update packets. (default 3 seconds)" +msgstr "Timeout to wait reply for Interim-Update packets. (default 3 seconds)" + +#: ../../configuration/vpn/sstp.rst:243 +msgid "Timeout to wait response from server (seconds)" +msgstr "Timeout to wait response from server (seconds)" + +#: ../../configuration/protocols/bgp.rst:667 +#: ../../configuration/protocols/isis.rst:257 +msgid "Timers" +msgstr "Timers" + +#: ../../configuration/interfaces/bridge.rst:130 +msgid "To activate the VLAN aware bridge, you must activate this setting to use VLAN settings for the bridge" +msgstr "To activate the VLAN aware bridge, you must activate this setting to use VLAN settings for the bridge" + +#: ../../configuration/vpn/l2tp.rst:58 +msgid "To allow VPN-clients access via your external address, a NAT rule is required:" +msgstr "To allow VPN-clients access via your external address, a NAT rule is required:" + +#: ../../configuration/vpn/site2site_ipsec.rst:253 +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 "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)" + +#: ../../configuration/policy/examples.rst:200 +msgid "To apply this policy to the correct interface, configure it on the interface the inbound local host will send through to reach our destined target host (in our example eth1)." +msgstr "To apply this policy to the correct interface, configure it on the interface the inbound local host will send through to reach our destined target host (in our example eth1)." + +#: ../../configuration/service/webproxy.rst:381 +msgid "To auto update the blacklist files" +msgstr "To auto update the blacklist files" + +#: ../../configuration/service/pppoe-server.rst:59 +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 "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." + +#: ../../configuration/firewall/general-legacy.rst:314 +msgid "To be used only when ``action`` is set to ``jump``. Use this command to specify jump target." +msgstr "To be used only when ``action`` is set to ``jump``. Use this command to specify jump target." + +#: ../../configuration/firewall/general.rst:401 +#: ../../configuration/firewall/general-legacy.rst:295 +msgid "To be used only when ``defult-action`` is set to ``jump``. Use this command to specify jump target for default rule." +msgstr "To be used only when ``defult-action`` is set to ``jump``. Use this command to specify jump target for default rule." + +#: ../../configuration/firewall/general.rst:374 +msgid "To be used only when action is set to jump. Use this command to specify jump target." +msgstr "To be used only when action is set to jump. Use this command to specify jump target." + +#: ../../configuration/service/webproxy.rst:408 +msgid "To bypass the proxy for every request that is coming from a specific source:" +msgstr "To bypass the proxy for every request that is coming from a specific source:" + +#: ../../configuration/service/webproxy.rst:400 +msgid "To bypass the proxy for every request that is directed to a specific destination:" +msgstr "To bypass the proxy for every request that is directed to a specific destination:" + +#: ../../configuration/service/ipoe-server.rst:65 +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 "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." + +#: ../../configuration/firewall/index.rst:58 +msgid "To configure VyOS with the :doc:`legacy firewall configuration </configuration/firewall/general-legacy>`" +msgstr "To configure VyOS with the :doc:`legacy firewall configuration </configuration/firewall/general-legacy>`" + +#: ../../configuration/firewall/index.rst:79 +msgid "To configure VyOS with the :doc:`zone-based firewall configuration </configuration/firewall/zone>`" +msgstr "To configure VyOS with the :doc:`zone-based firewall configuration </configuration/firewall/zone>`" + +#: ../../configuration/firewall/index.rst:30 +msgid "To configure VyOS with the new :doc:`firewall configuration </configuration/firewall/general>`" +msgstr "To configure VyOS with the new :doc:`firewall configuration </configuration/firewall/general>`" + +#: ../../configuration/service/webproxy.rst:386 +msgid "To configure blocking add the following to the configuration" +msgstr "To configure blocking add the following to the configuration" + +#: ../../configuration/vpn/site2site_ipsec.rst:10 +msgid "To configure site-to-site connection you need to add peers with the ``set vpn ipsec site-to-site peer <name>`` command." +msgstr "To configure site-to-site connection you need to add peers with the ``set vpn ipsec site-to-site peer <name>`` command." + +#: ../../configuration/system/syslog.rst:11 +msgid "To configure syslog, you need to switch into configuration mode." +msgstr "To configure syslog, you need to switch into configuration mode." + +#: ../../configuration/system/lcd.rst:12 +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 "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." + +#: ../../configuration/service/ipoe-server.rst:98 +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 "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." + +#: ../../configuration/system/login.rst:375 +msgid "To create a new line in your login message you need to escape the new line character by using ``\\\\n``." +msgstr "To create a new line in your login message you need to escape the new line character by using ``\\\\n``." + +#: ../../configuration/interfaces/l2tpv3.rst:131 +msgid "To create more than one tunnel, use distinct UDP ports." +msgstr "To create more than one tunnel, use distinct UDP ports." + +#: ../../configuration/policy/examples.rst:71 +msgid "To create routing table 100 and add a new default gateway to be used by traffic matching our route policy:" +msgstr "To create routing table 100 and add a new default gateway to be used by traffic matching our route policy:" + +#: ../../configuration/firewall/zone.rst:61 +msgid "To define a zone setup either one with interfaces or a local zone." +msgstr "To define a zone setup either one with interfaces or a local zone." + +#: ../../configuration/service/router-advert.rst:75 +msgid "To disable advertisements without deleting the configuration:" +msgstr "To disable advertisements without deleting the configuration:" + +#: ../../configuration/system/login.rst:190 +msgid "To display the configured OTP user key, use the command:" +msgstr "To display the configured OTP user key, use the command:" + +#: ../../configuration/vpn/openconnect.rst:219 +msgid "To display the configured OTP user settings, use the command:" +msgstr "To display the configured OTP user settings, use the command:" + +#: ../../configuration/protocols/ospf.rst:515 +#: ../../configuration/protocols/ospf.rst:1227 +msgid "To enable/disable helper support for a specific neighbour, the router-id (A.B.C.D) has to be specified." +msgstr "To enable/disable helper support for a specific neighbour, the router-id (A.B.C.D) has to be specified." + +#: ../../configuration/protocols/pim6.rst:80 +msgid "To enable MLD reports and query on interfaces `eth0` and `eth1`:" +msgstr "To enable MLD reports and query on interfaces `eth0` and `eth1`:" + +#: ../../configuration/vpn/l2tp.rst:141 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:182 +msgid "To enable bandwidth shaping via RADIUS, the option rate-limit needs to be enabled." +msgstr "To enable bandwidth shaping via RADIUS, the option rate-limit needs to be enabled." + +#: ../../configuration/service/https.rst:23 +msgid "To enable debug messages. Available via :opcmd:`show log` or :opcmd:`monitor log`" +msgstr "To enable debug messages. Available via :opcmd:`show log` or :opcmd:`monitor log`" + +#: ../../configuration/service/mdns.rst:22 +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 "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." + +#: ../../configuration/loadbalancing/wan.rst:115 +msgid "To exclude traffic from load balancing, traffic matching an exclude rule is not balanced but routed through the system routing table instead:" +msgstr "To exclude traffic from load balancing, traffic matching an exclude rule is not balanced but routed through the system routing table instead:" + +#: ../../configuration/service/snmp.rst:216 +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 "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." + +#: ../../configuration/service/broadcast-relay.rst:57 +msgid "To forward all broadcast packets received on `UDP port 1900` on `eth3`, `eth4` or `eth5` to all other interfaces in this configuration." +msgstr "To forward all broadcast packets received on `UDP port 1900` on `eth3`, `eth4` or `eth5` to all other interfaces in this configuration." + +#: ../../configuration/vpn/sstp.rst:32 +msgid "To generate the CA, the server private key and certificates the following commands can be used." +msgstr "To generate the CA, the server private key and certificates the following commands can be used." + +#: ../../configuration/interfaces/wireless.rst:592 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:636 +msgid "To hand out individual prefixes to your clients the following configuration is used:" +msgstr "To hand out individual prefixes to your clients the following configuration is used:" + +#: ../../configuration/highavailability/index.rst:336 +msgid "To know more about scripting, check the :ref:`command-scripting` section." +msgstr "To know more about scripting, check the :ref:`command-scripting` section." + +#: ../../configuration/service/mdns.rst:36 +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 "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:" + +#: ../../configuration/protocols/static.rst:161 +msgid "To manipulate or display ARP_ table entries, the following commands are implemented." +msgstr "To manipulate or display ARP_ table entries, the following commands are implemented." + +#: ../../configuration/protocols/ospf.rst:505 +#: ../../configuration/protocols/ospf.rst:1217 +msgid "To perform a graceful shutdown, the FRR ``graceful-restart prepare ip ospf`` EXEC-level command needs to be issued before restarting the ospfd daemon." +msgstr "To perform a graceful shutdown, the FRR ``graceful-restart prepare ip ospf`` EXEC-level command needs to be issued before restarting the ospfd daemon." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:17 +msgid "To request a /56 prefix from your ISP use:" +msgstr "To request a /56 prefix from your ISP use:" + +#: ../../configuration/service/dhcp-server.rst:748 +msgid "To restart the DHCPv6 server" +msgstr "To restart the DHCPv6 server" + +#: ../../configuration/nat/nat44.rst:315 +msgid "To setup SNAT, we need to know:" +msgstr "To setup SNAT, we need to know:" + +#: ../../configuration/nat/nat44.rst:501 +msgid "To setup a destination NAT rule we need to gather:" +msgstr "To setup a destination NAT rule we need to gather:" + +#: ../../configuration/interfaces/wwan.rst:329 +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 "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:" + +#: ../../configuration/service/ipoe-server.rst:113 +msgid "To use a RADIUS server for authentication and bandwidth-shaping, the following example configuration can be used." +msgstr "To use a RADIUS server for authentication and bandwidth-shaping, the following example configuration can be used." + +#: ../../configuration/service/pppoe-server.rst:106 +msgid "To use a radius server, you need to switch to authentication mode RADIUS and then configure it." +msgstr "To use a radius server, you need to switch to authentication mode RADIUS and then configure it." + +#: ../../configuration/service/dns.rst:308 +msgid "To use such a service, one must define a login, password, one or multiple hostnames, protocol and server." +msgstr "To use such a service, one must define a login, password, one or multiple hostnames, protocol and server." + +#: ../../configuration/service/salt-minion.rst:19 +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 "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>`_" + +#: ../../configuration/service/https.rst:86 +msgid "To use this full configuration we asume a public accessible hostname." +msgstr "To use this full configuration we asume a public accessible hostname." + +#: ../../configuration/interfaces/vxlan.rst:175 +msgid "Topology:" +msgstr "Topology:" + +#: ../../configuration/interfaces/vxlan.rst:107 +msgid "Topology: PC4 - Leaf2 - Spine1 - Leaf3 - PC5" +msgstr "Topology: PC4 - Leaf2 - Spine1 - Leaf3 - PC5" + +#: ../../configuration/highavailability/index.rst:171 +msgid "Track" +msgstr "Track" + +#: ../../configuration/highavailability/index.rst:173 +msgid "Track option to track non VRRP interface states. VRRP changes status to ``FAULT`` if one of the track interfaces in state ``down``." +msgstr "Track option to track non VRRP interface states. VRRP changes status to ``FAULT`` if one of the track interfaces in state ``down``." + +#: ../../configuration/protocols/bgp.rst:146 +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 "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)." + +#: ../../configuration/firewall/index.rst:54 +msgid "Traditionally firewalls weere configured with the concept of data going in and out of an interface. The router just listened to the data flowing through and responding as required if it was directed at the router itself." +msgstr "Traditionally firewalls weere configured with the concept of data going in and out of an interface. The router just listened to the data flowing through and responding as required if it was directed at the router itself." + +#: ../../configuration/interfaces/openvpn.rst:9 +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 "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." + +#: ../../configuration/nat/nat44.rst:143 +msgid "Traffic Filters" +msgstr "Traffic Filters" + +#: ../../configuration/nat/nat44.rst:145 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:5 +msgid "Traffic Policy" +msgstr "Traffic Policy" + +#: ../../configuration/firewall/zone.rst:37 +msgid "Traffic cannot flow between zone member interface and any interface that is not a zone member." +msgstr "Traffic cannot flow between zone member interface and any interface that is not a zone member." + +#: ../../configuration/protocols/igmp.rst:22 +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 "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)." + +#: ../../configuration/protocols/pim6.rst:15 +msgid "Traffic from multicast sources will go to the Rendezvous Point, and receivers will pull it from a shared tree using MLD (Multicast Listener Discovery)." +msgstr "Traffic from multicast sources will go to the Rendezvous Point, and receivers will pull it from a shared tree using MLD (Multicast Listener Discovery)." + +#: ../../configuration/firewall/general.rst:1281 +msgid "Traffic must be symmetric" +msgstr "Traffic must be symmetric" + +#: ../../configuration/highavailability/index.rst:322 +msgid "Transition scripts" +msgstr "Transition scripts" + +#: ../../configuration/highavailability/index.rst:324 +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 "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:" + +#: ../../configuration/policy/examples.rst:56 +msgid "Transparent Proxy" +msgstr "Transparent Proxy" + +#: ../../configuration/interfaces/tunnel.rst:227 +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#: ../../configuration/protocols/igmp.rst:119 +#: ../../configuration/protocols/pim6.rst:41 +msgid "Tuning commands" +msgstr "Tuning commands" + +#: ../../configuration/interfaces/tunnel.rst:6 +msgid "Tunnel" +msgstr "Tunnel" + +#: ../../configuration/interfaces/tunnel.rst:187 +msgid "Tunnel keys" +msgstr "Tunnel keys" + +#: ../../configuration/loadbalancing/wan.rst:257 +msgid "Two environment variables are available:" +msgstr "Two environment variables are available:" + +#: ../../configuration/service/ssh.rst:188 +msgid "Two new files ``/config/auth/id_rsa_rpki`` and ``/config/auth/id_rsa_rpki.pub`` will be created." +msgstr "Two new files ``/config/auth/id_rsa_rpki`` and ``/config/auth/id_rsa_rpki.pub`` will be created." + +#: ../../configuration/interfaces/macsec.rst:155 +msgid "Two routers connected both via eth1 through an untrusted switch" +msgstr "Two routers connected both via eth1 through an untrusted switch" + +#: ../../configuration/service/monitoring.rst:26 +msgid "Type of metrics grouping when push to Azure Data Explorer. The default is ``table-per-metric``." +msgstr "Type of metrics grouping when push to Azure Data Explorer. The default is ``table-per-metric``." + +#: ../../configuration/nat/nat44.rst:594 +msgid "Typically, a 1-to-1 NAT rule omits the destination port (all ports) and replaces the protocol with either **all** or **ip**." +msgstr "Typically, a 1-to-1 NAT rule omits the destination port (all ports) and replaces the protocol with either **all** or **ip**." + +#: ../../configuration/service/broadcast-relay.rst:5 +msgid "UDP Broadcast Relay" +msgstr "UDP Broadcast Relay" + +#: ../../configuration/interfaces/l2tpv3.rst:110 +msgid "UDP mode works better with NAT:" +msgstr "UDP mode works better with NAT:" + +#: ../../configuration/vpn/l2tp.rst:34 +msgid "UDP port 1701 for IPsec" +msgstr "UDP port 1701 for IPsec" + +#: ../../configuration/vpn/l2tp.rst:39 +msgid "UDP port 4500 (NAT-T)" +msgstr "UDP port 4500 (NAT-T)" + +#: ../../configuration/vpn/l2tp.rst:32 +msgid "UDP port 500 (IKE)" +msgstr "UDP port 500 (IKE)" + +#: ../../configuration/service/webproxy.rst:17 +msgid "URL Filtering is provided by SquidGuard_." +msgstr "URL Filtering is provided by SquidGuard_." + +#: ../../configuration/service/webproxy.rst:315 +msgid "URL filtering" +msgstr "URL filtering" + +#: ../../configuration/service/salt-minion.rst:45 +msgid "URL with signature of master for auth reply verification" +msgstr "URL with signature of master for auth reply verification" + +#: ../../configuration/service/console-server.rst:55 +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 "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." + +#: ../../configuration/system/syslog.rst:128 +msgid "UUCP subsystem" +msgstr "UUCP subsystem" + +#: ../../configuration/interfaces/vxlan.rst:81 +msgid "Unicast" +msgstr "Unicast" + +#: ../../configuration/highavailability/index.rst:188 +msgid "Unicast VRRP" +msgstr "Unicast VRRP" + +#: ../../configuration/interfaces/vxlan.rst:319 +msgid "Unicast VXLAN" +msgstr "Unicast VXLAN" + +#: ../../configuration/service/webproxy.rst:41 +msgid "Unit of this command is MB." +msgstr "Unit of this command is MB." + +#: ../../configuration/trafficpolicy/index.rst:42 +msgid "Units" +msgstr "Units" + +#: ../../configuration/interfaces/openvpn.rst:171 +msgid "Until VyOS 1.4, the only option for site-to-site OpenVPN without PKI was to use pre-shared keys. That option is still available but it is deprecated and will be removed in the future. However, if you need to set up a tunnel to an older VyOS version or a system with older OpenVPN, you need to still need to know how to use it." +msgstr "Until VyOS 1.4, the only option for site-to-site OpenVPN without PKI was to use pre-shared keys. That option is still available but it is deprecated and will be removed in the future. However, if you need to set up a tunnel to an older VyOS version or a system with older OpenVPN, you need to still need to know how to use it." + +#: ../../configuration/trafficpolicy/index.rst:705 +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 "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." + +#: ../../configuration/service/webproxy.rst:338 +msgid "Update" +msgstr "Update" + +#: ../../configuration/container/index.rst:171 +msgid "Update container image" +msgstr "Update container image" + +#: ../../configuration/firewall/general.rst:1540 +#: ../../configuration/firewall/general-legacy.rst:1050 +msgid "Update geoip database" +msgstr "Update geoip database" + +#: ../../configuration/protocols/rpki.rst:99 +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 "Updates from the RPKI cache servers are directly applied and path selection is updated accordingly. (Soft reconfiguration must be enabled for this to work)." + +#: ../../configuration/vpn/sstp.rst:90 +msgid "Upload bandwidth limit in kbit/s for `<user>`." +msgstr "Upload bandwidth limit in kbit/s for `<user>`." + +#: ../../configuration/loadbalancing/wan.rst:209 +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 "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:" + +#: ../../configuration/service/router-advert.rst:1 +msgid "Upon shutdown, this option will deprecate the prefix by announcing it in the shutdown RA" +msgstr "Upon shutdown, this option will deprecate the prefix by announcing it in the shutdown RA" + +#: ../../configuration/interfaces/wireless.rst:352 +#: ../../configuration/interfaces/wireless.rst:552 +msgid "Use 802.11n protocol" +msgstr "Use 802.11n protocol" + +#: ../../configuration/service/dns.rst:352 +msgid "Use DynDNS as your preferred provider:" +msgstr "Use DynDNS as your preferred provider:" + +#: ../../configuration/service/monitoring.rst:88 +msgid "Use TLS but skip host validation" +msgstr "Use TLS but skip host validation" + +#: ../../configuration/service/webproxy.rst:281 +msgid "Use TLS encryption." +msgstr "Use TLS encryption." + +#: ../../configuration/vpn/sstp.rst:121 +msgid "Use `<subnet>` as the IP pool for all connecting clients." +msgstr "Use `<subnet>` as the IP pool for all connecting clients." + +#: ../../configuration/system/syslog.rst:236 +msgid "Use ``show log | strip-private`` if you want to hide private data when sharing your logs." +msgstr "Use ``show log | strip-private`` if you want to hide private data when sharing your logs." + +#: ../../configuration/system/conntrack.rst:0 +msgid "Use `delete system conntrack modules` to deactive all modules." +msgstr "Use `delete system conntrack modules` to deactive all modules." + +#: ../../configuration/service/webproxy.rst:250 +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 "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." + +#: ../../configuration/firewall/general.rst:799 +#: ../../configuration/firewall/general-legacy.rst:531 +msgid "Use a specific address-group. Prepend character ``!`` for inverted matching criteria." +msgstr "Use a specific address-group. Prepend character ``!`` for inverted matching criteria." + +#: ../../configuration/firewall/general.rst:874 +#: ../../configuration/firewall/general-legacy.rst:567 +msgid "Use a specific domain-group. Prepend character ``!`` for inverted matching criteria." +msgstr "Use a specific domain-group. Prepend character ``!`` for inverted matching criteria." + +#: ../../configuration/firewall/general.rst:899 +#: ../../configuration/firewall/general-legacy.rst:579 +msgid "Use a specific mac-group. Prepend character ``!`` for inverted matching criteria." +msgstr "Use a specific mac-group. Prepend character ``!`` for inverted matching criteria." + +#: ../../configuration/firewall/general.rst:824 +#: ../../configuration/firewall/general-legacy.rst:543 +msgid "Use a specific network-group. Prepend character ``!`` for inverted matching criteria." +msgstr "Use a specific network-group. Prepend character ``!`` for inverted matching criteria." + +#: ../../configuration/firewall/general.rst:849 +#: ../../configuration/firewall/general-legacy.rst:555 +msgid "Use a specific port-group. Prepend character ``!`` for inverted matching criteria." +msgstr "Use a specific port-group. Prepend character ``!`` for inverted matching criteria." + +#: ../../configuration/nat/nat44.rst:247 +msgid "Use address `masquerade` (the interfaces primary address) on rule 30" +msgstr "Use address `masquerade` (the interfaces primary address) on rule 30" + +#: ../../configuration/service/https.rst:67 +msgid "Use an automatically generated self-signed certificate" +msgstr "Use an automatically generated self-signed certificate" + +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +#: ../../_include/interface-ip.txt:104 +msgid "Use any local address, configured on any interface if this is not set." +msgstr "Use any local address, configured on any interface if this is not set." + +#: ../../configuration/service/dns.rst:266 +msgid "Use auth key file at ``/config/auth/my.key``" +msgstr "Use auth key file at ``/config/auth/my.key``" + +#: ../../configuration/service/dns.rst:389 +msgid "Use configured `<url>` to determine your IP address. ddclient_ will load `<url>` and tries to extract your IP address from the response." +msgstr "Use configured `<url>` to determine your IP address. ddclient_ will load `<url>` and tries to extract your IP address from the response." + +#: ../../configuration/firewall/general-legacy.rst:478 +msgid "Use inverse-match to match anything except the given country-codes." +msgstr "Use inverse-match to match anything except the given country-codes." + +#: ../../configuration/service/https.rst:33 +msgid "Use local socket for API" +msgstr "Use local socket for API" + +#: ../../configuration/vpn/sstp.rst:277 +msgid "Use local user `foo` with password `bar`" +msgstr "Use local user `foo` with password `bar`" + +#: ../../configuration/service/webproxy.rst:379 +msgid "Use tab completion to get a list of categories." +msgstr "Use tab completion to get a list of categories." + +#: ../../configuration/system/option.rst:53 +msgid "Use the address of the specified interface on the local machine as the source address of the connection." +msgstr "Use the address of the specified interface on the local machine as the source address of the connection." + +#: ../../configuration/nat/nat66.rst:111 +msgid "Use the following topology to build a nat66 based isolated network between internal and external networks (dynamic prefix is not supported):" +msgstr "Use the following topology to build a nat66 based isolated network between internal and external networks (dynamic prefix is not supported):" + +#: ../../configuration/system/option.rst:48 +msgid "Use the specified address on the local machine as the source address of the connection. Only useful on systems with more than one address." +msgstr "Use the specified address on the local machine as the source address of the connection. Only useful on systems with more than one address." + +#: ../../configuration/protocols/mpls.rst:113 +msgid "Use these commands if you would like to set the discovery hello and hold time parameters." +msgstr "Use these commands if you would like to set the discovery hello and hold time parameters." + +#: ../../configuration/protocols/mpls.rst:196 +msgid "Use these commands if you would like to set the discovery hello and hold time parameters for the targeted LDP neighbors." +msgstr "Use these commands if you would like to set the discovery hello and hold time parameters for the targeted LDP neighbors." + +#: ../../configuration/protocols/mpls.rst:136 +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 "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." + +#: ../../configuration/protocols/mpls.rst:126 +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 "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." + +#: ../../configuration/protocols/igmp.rst:125 +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 "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." + +#: ../../configuration/protocols/igmp.rst:140 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:288 +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 "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." + +#: ../../configuration/vpn/sstp.rst:126 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:93 +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." +msgstr "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." + +#: ../../configuration/service/pppoe-server.rst:93 +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 "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." + +#: ../../configuration/protocols/mpls.rst:144 +msgid "Use this command if you would like for the router to advertise FECs with a label of 0 for explicit null operations." +msgstr "Use this command if you would like for the router to advertise FECs with a label of 0 for explicit null operations." + +#: ../../configuration/protocols/mpls.rst:152 +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 "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." + +#: ../../configuration/protocols/mpls.rst:119 +msgid "Use this command if you would like to set the TCP session hold time intervals." +msgstr "Use this command if you would like to set the TCP session hold time intervals." + +#: ../../configuration/protocols/pim6.rst:53 +msgid "Use this command to allow the selected interface to join a multicast group." +msgstr "Use this command to allow the selected interface to join a multicast group." + +#: ../../configuration/protocols/igmp.rst:149 +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 "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." + +#: ../../configuration/protocols/pim6.rst:57 +msgid "Use this command to allow the selected interface to join a source-specific multicast group." +msgstr "Use this command to allow the selected interface to join a source-specific multicast group." + +#: ../../configuration/interfaces/openvpn.rst:712 +msgid "Use this command to check the tunnel status for OpenVPN client interfaces." +msgstr "Use this command to check the tunnel status for OpenVPN client interfaces." + +#: ../../configuration/interfaces/openvpn.rst:716 +msgid "Use this command to check the tunnel status for OpenVPN server interfaces." +msgstr "Use this command to check the tunnel status for OpenVPN server interfaces." + +#: ../../configuration/interfaces/openvpn.rst:720 +msgid "Use this command to check the tunnel status for OpenVPN site-to-site interfaces." +msgstr "Use this command to check the tunnel status for OpenVPN site-to-site interfaces." + +#: ../../configuration/system/ipv6.rst:180 +msgid "Use this command to clear Border Gateway Protocol statistics or status." +msgstr "Use this command to clear Border Gateway Protocol statistics or status." + +#: ../../configuration/service/pppoe-server.rst:300 +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 "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." + +#: ../../configuration/vpn/sstp.rst:135 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:133 +msgid "Use this command to configure Dynamic Authorization Extensions to RADIUS so that you can remotely disconnect sessions and change some authentication parameters." +msgstr "Use this command to configure Dynamic Authorization Extensions to RADIUS so that you can remotely disconnect sessions and change some authentication parameters." + +#: ../../configuration/protocols/static.rst:112 +#: ../../configuration/protocols/static.rst:125 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:649 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:753 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:814 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:885 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:834 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:843 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:852 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:823 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:947 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:930 +msgid "Use this command to configure a Rate-Control policy, set its name and the rate limit you want to have." +msgstr "Use this command to configure a Rate-Control policy, set its name and the rate limit you want to have." + +#: ../../configuration/trafficpolicy/index.rst:935 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:987 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:994 +msgid "Use this command to configure a Round-Robin policy, set its name, set a class ID, and the queue size in packets." +msgstr "Use this command to configure a Round-Robin policy, set its name, set a class ID, and the queue size in packets." + +#: ../../configuration/trafficpolicy/index.rst:1049 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1063 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1070 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:1056 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:1042 +msgid "Use this command to configure a Shaper policy, set its name and the maximum bandwidth for all combined traffic." +msgstr "Use this command to configure a Shaper policy, set its name and the maximum bandwidth for all combined traffic." + +#: ../../configuration/service/pppoe-server.rst:206 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:378 +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 "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)." + +#: ../../configuration/protocols/mpls.rst:98 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:571 +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 "Use this command to configure an Ingress Policer, defining its name, a class identifier (1-4090), a class matching rule name and its description." + +#: ../../configuration/trafficpolicy/index.rst:611 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:591 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:583 +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 "Use this command to configure an Ingress Policer, defining its name, a class identifier (1-4090) and the maximum allowed bandwidth for this class." + +#: ../../configuration/trafficpolicy/index.rst:604 +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 "Use this command to configure an Ingress Policer, defining its name and the burst size in bytes (default: 15) for its default policy." + +#: ../../configuration/trafficpolicy/index.rst:598 +msgid "Use this command to configure an Ingress Policer, defining its name and the maximum allowed bandwidth for its default policy." +msgstr "Use this command to configure an Ingress Policer, defining its name and the maximum allowed bandwidth for its default policy." + +#: ../../configuration/trafficpolicy/index.rst:517 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:523 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:497 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:503 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:509 +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 "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)." + +#: ../../configuration/protocols/igmp.rst:112 +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 "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." + +#: ../../configuration/protocols/mpls.rst:92 +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 "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." + +#: ../../configuration/protocols/igmp.rst:156 +msgid "Use this command to configure in the selected interface the IGMP host query interval (1-1800) in seconds that PIM will use." +msgstr "Use this command to configure in the selected interface the IGMP host query interval (1-1800) in seconds that PIM will use." + +#: ../../configuration/protocols/igmp.rst:163 +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 "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." + +#: ../../configuration/protocols/pim6.rst:47 +msgid "Use this command to configure in the selected interface the MLD host query interval (1-65535) in seconds that PIM will use. The default value is 125 seconds." +msgstr "Use this command to configure in the selected interface the MLD host query interval (1-65535) in seconds that PIM will use. The default value is 125 seconds." + +#: ../../configuration/service/pppoe-server.rst:112 +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 "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." + +#: ../../configuration/protocols/mpls.rst:82 +msgid "Use this command to configure the IP address used as the LDP router-id of the local device." +msgstr "Use this command to configure the IP address used as the LDP router-id of the local device." + +#: ../../configuration/protocols/igmp.rst:134 +msgid "Use this command to configure the PIM hello interval in seconds (1-180) for the selected interface." +msgstr "Use this command to configure the PIM hello interval in seconds (1-180) for the selected interface." + +#: ../../configuration/system/flow-accounting.rst:119 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:640 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:47 +msgid "Use this command to configure the local gateway IP address." +msgstr "Use this command to configure the local gateway IP address." + +#: ../../configuration/trafficpolicy/index.rst:634 +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 "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." + +#: ../../configuration/system/sflow.rst:41 +msgid "Use this command to configure the sampling rate for sFlow accounting (default: 1000)" +msgstr "Use this command to configure the sampling rate for sFlow accounting (default: 1000)" + +#: ../../configuration/service/pppoe-server.rst:37 +msgid "Use this command to configure the username and the password of a locally configured user." +msgstr "Use this command to configure the username and the password of a locally configured user." + +#: ../../configuration/protocols/ospf.rst:168 +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 "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)." + +#: ../../configuration/trafficpolicy/index.rst:398 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:425 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:416 +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 "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)." + +#: ../../configuration/system/name-server.rst:53 +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 "Use this command to define domains, one at a time, so that the system uses them to complete unqualified host names. Maximum: 6 entries." + +#: ../../configuration/protocols/igmp.rst:172 +msgid "Use this command to define in the selected interface whether you choose IGMP version 2 or 3. The default value is 3." +msgstr "Use this command to define in the selected interface whether you choose IGMP version 2 or 3. The default value is 3." + +#: ../../configuration/service/pppoe-server.rst:73 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:42 +msgid "Use this command to define the interface the PPPoE server will use to listen for PPPoE clients." +msgstr "Use this command to define the interface the PPPoE server will use to listen for PPPoE clients." + +#: ../../configuration/service/pppoe-server.rst:79 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:681 +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 "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." + +#: ../../configuration/system/ip.rst:23 +msgid "Use this command to define the maximum number of entries to keep in the ARP cache (1024, 2048, 4096, 8192, 16384, 32768)." +msgstr "Use this command to define the maximum number of entries to keep in the ARP cache (1024, 2048, 4096, 8192, 16384, 32768)." + +#: ../../configuration/system/ipv6.rst:14 +msgid "Use this command to define the maximum number of entries to keep in the Neighbor cache (1024, 2048, 4096, 8192, 16384, 32768)." +msgstr "Use this command to define the maximum number of entries to keep in the Neighbor cache (1024, 2048, 4096, 8192, 16384, 32768)." + +#: ../../configuration/service/pppoe-server.rst:31 +msgid "Use this command to define whether your PPPoE clients will locally authenticate in your VyOS system or in RADIUS server." +msgstr "Use this command to define whether your PPPoE clients will locally authenticate in your VyOS system or in RADIUS server." + +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +#: ../../_include/interface-disable-link-detect.txt:4 +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 "Use this command to direct an interface to not detect any physical state changes on a link, for example, when the cable is unplugged." + +#: ../../configuration/system/ip.rst:14 +msgid "Use this command to disable IPv4 directed broadcast forwarding on all interfaces." +msgstr "Use this command to disable IPv4 directed broadcast forwarding on all interfaces." + +#: ../../configuration/system/ip.rst:10 +msgid "Use this command to disable IPv4 forwarding on all interfaces." +msgstr "Use this command to disable IPv4 forwarding on all interfaces." + +#: ../../configuration/system/ipv6.rst:10 +msgid "Use this command to disable IPv6 forwarding on all interfaces." +msgstr "Use this command to disable IPv6 forwarding on all interfaces." + +#: ../../configuration/system/ipv6.rst:19 +msgid "Use this command to disable IPv6 operation on interface when Duplicate Address Detection fails on Link-Local address." +msgstr "Use this command to disable IPv6 operation on interface when Duplicate Address Detection fails on Link-Local address." + +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +#: ../../_include/interface-disable-flow-control.txt:16 +msgid "Use this command to disable the generation of Ethernet flow control (pause frames)." +msgstr "Use this command to disable the generation of Ethernet flow control (pause frames)." + +#: ../../configuration/trafficpolicy/index.rst:659 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:667 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:674 +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 "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." + +#: ../../configuration/protocols/mpls.rst:105 +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 "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)." + +#: ../../configuration/protocols/mpls.rst:78 +msgid "Use this command to enable LDP on the interface you define." +msgstr "Use this command to enable LDP on the interface you define." + +#: ../../configuration/protocols/mpls.rst:74 +msgid "Use this command to enable MPLS processing on the interface you define." +msgstr "Use this command to enable MPLS processing on the interface you define." + +#: ../../configuration/protocols/igmp.rst:97 +msgid "Use this command to enable PIM in the selected interface so that it can communicate with PIM neighbors." +msgstr "Use this command to enable PIM in the selected interface so that it can communicate with PIM neighbors." + +#: ../../configuration/protocols/pim6.rst:31 +msgid "Use this command to enable PIMv6 in the selected interface so that it can communicate with PIMv6 neighbors. This command also enables MLD reports and query on the interface unless :cfgcmd:`mld disable` is configured." +msgstr "Use this command to enable PIMv6 in the selected interface so that it can communicate with PIMv6 neighbors. This command also enables MLD reports and query on the interface unless :cfgcmd:`mld disable` is configured." + +#: ../../configuration/interfaces/pppoe.rst:235 +msgid "Use this command to enable acquisition of IPv6 address using stateless autoconfig (SLAAC)." +msgstr "Use this command to enable acquisition of IPv6 address using stateless autoconfig (SLAAC)." + +#: ../../configuration/service/pppoe-server.rst:249 +msgid "Use this command to enable bandwidth shaping via RADIUS." +msgstr "Use this command to enable bandwidth shaping via RADIUS." + +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +#: ../../_include/interface-ip.txt:137 +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 "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." + +#: ../../configuration/protocols/mpls.rst:177 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:262 +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 "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." + +#: ../../configuration/protocols/mpls.rst:184 +msgid "Use this command to enable the local router to try and connect with a targeted LDP session to another router." +msgstr "Use this command to enable the local router to try and connect with a targeted LDP session to another router." + +#: ../../configuration/firewall/general-legacy.rst:301 +msgid "Use this command to enable the logging of the default action." +msgstr "Use this command to enable the logging of the default action." + +#: ../../configuration/firewall/general.rst:431 +msgid "Use this command to enable the logging of the default action on custom chains." +msgstr "Use this command to enable the logging of the default action on custom chains." + +#: ../../configuration/system/ipv6.rst:191 +msgid "Use this command to flush the kernel IPv6 route cache. An address can be added to flush it only for that route." +msgstr "Use this command to flush the kernel IPv6 route cache. An address can be added to flush it only for that route." + +#: ../../configuration/firewall/general-legacy.rst:948 +msgid "Use this command to get an overview of a zone." +msgstr "Use this command to get an overview of a zone." + +#: ../../configuration/system/ipv6.rst:146 +msgid "Use this command to get information about OSPFv3." +msgstr "Use this command to get information about OSPFv3." + +#: ../../configuration/system/ipv6.rst:168 +msgid "Use this command to get information about the RIPNG protocol" +msgstr "Use this command to get information about the RIPNG protocol" + +#: ../../configuration/interfaces/pppoe.rst:110 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:188 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:324 +msgid "Use this command to locally check the active sessions in the PPPoE server." +msgstr "Use this command to locally check the active sessions in the PPPoE server." + +#: ../../configuration/protocols/igmp.rst:104 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:172 +#: ../../configuration/interfaces/sstp-client.rst:70 +msgid "Use this command to not install advertised DNS nameservers into the local system." +msgstr "Use this command to not install advertised DNS nameservers into the local system." + +#: ../../configuration/protocols/mpls.rst:171 +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 "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." + +#: ../../configuration/system/ipv6.rst:186 +msgid "Use this command to reset IPv6 Neighbor Discovery Protocol cache for an address or interface." +msgstr "Use this command to reset IPv6 Neighbor Discovery Protocol cache for an address or interface." + +#: ../../configuration/protocols/mpls.rst:252 +msgid "Use this command to reset an LDP neighbor/TCP session that is established" +msgstr "Use this command to reset an LDP neighbor/TCP session that is established" + +#: ../../configuration/interfaces/openvpn.rst:735 +msgid "Use this command to reset the OpenVPN process on a specific interface." +msgstr "Use this command to reset the OpenVPN process on a specific interface." + +#: ../../configuration/interfaces/openvpn.rst:731 +msgid "Use this command to reset the specified OpenVPN client." +msgstr "Use this command to reset the specified OpenVPN client." + +#: ../../configuration/interfaces/pppoe.rst:85 +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 "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." + +#: ../../configuration/protocols/mpls.rst:237 +msgid "Use this command to see LDP interface information" +msgstr "Use this command to see LDP interface information" + +#: ../../configuration/protocols/mpls.rst:241 +msgid "Use this command to see LDP neighbor information" +msgstr "Use this command to see LDP neighbor information" + +#: ../../configuration/protocols/mpls.rst:245 +msgid "Use this command to see detailed LDP neighbor information" +msgstr "Use this command to see detailed LDP neighbor information" + +#: ../../configuration/protocols/mpls.rst:233 +msgid "Use this command to see discovery hello information" +msgstr "Use this command to see discovery hello information" + +#: ../../configuration/protocols/mpls.rst:229 +msgid "Use this command to see the Label Information Base." +msgstr "Use this command to see the Label Information Base." + +#: ../../configuration/service/pppoe-server.rst:26 +msgid "Use this command to set a name for this PPPoE-server access concentrator." +msgstr "Use this command to set a name for this PPPoE-server access concentrator." + +#: ../../configuration/interfaces/pppoe.rst:159 +msgid "Use this command to set re-dial delay time to be used with persist PPPoE sessions. When the PPPoE session is terminated by peer, and on-demand option is not set, the router will attempt to re-establish the PPPoE link." +msgstr "Use this command to set re-dial delay time to be used with persist PPPoE sessions. When the PPPoE session is terminated by peer, and on-demand option is not set, the router will attempt to re-establish the PPPoE link." + +#: ../../configuration/interfaces/pppoe.rst:167 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:177 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:51 +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 "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." + +#: ../../configuration/protocols/mpls.rst:88 +msgid "Use this command to set the IPv4 or IPv6 transport-address used by LDP." +msgstr "Use this command to set the IPv4 or IPv6 transport-address used by LDP." + +#: ../../configuration/interfaces/pppoe.rst:148 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:102 +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 "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." + +#: ../../configuration/firewall/general-legacy.rst:320 +msgid "Use this command to set the target to use. Action queue must be defined to use this setting" +msgstr "Use this command to set the target to use. Action queue must be defined to use this setting" + +#: ../../configuration/interfaces/pppoe.rst:96 +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 "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." + +#: ../../configuration/system/ipv6.rst:117 +msgid "Use this command to show IPv6 Border Gateway Protocol information." +msgstr "Use this command to show IPv6 Border Gateway Protocol information." + +#: ../../configuration/system/ipv6.rst:50 +msgid "Use this command to show IPv6 Neighbor Discovery Protocol information." +msgstr "Use this command to show IPv6 Neighbor Discovery Protocol information." + +#: ../../configuration/system/ipv6.rst:58 +msgid "Use this command to show IPv6 forwarding status." +msgstr "Use this command to show IPv6 forwarding status." + +#: ../../configuration/system/ipv6.rst:54 +msgid "Use this command to show IPv6 multicast group membership." +msgstr "Use this command to show IPv6 multicast group membership." + +#: ../../configuration/system/ipv6.rst:62 +msgid "Use this command to show IPv6 routes." +msgstr "Use this command to show IPv6 routes." + +#: ../../configuration/system/ipv6.rst:104 +msgid "Use this command to show all IPv6 access lists" +msgstr "Use this command to show all IPv6 access lists" + +#: ../../configuration/system/ipv6.rst:89 +msgid "Use this command to show all IPv6 prefix lists" +msgstr "Use this command to show all IPv6 prefix lists" + +#: ../../configuration/system/ipv6.rst:172 +msgid "Use this command to show the status of the RIPNG protocol" +msgstr "Use this command to show the status of the RIPNG protocol" + +#: ../../configuration/system/name-server.rst:21 +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 "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." + +#: ../../configuration/service/webproxy.rst:25 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:182 +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 "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." + +#: ../../configuration/system/ip.rst:28 +msgid "Use this command to use Layer 4 information for IPv4 ECMP hashing." +msgstr "Use this command to use Layer 4 information for IPv4 ECMP hashing." + +#: ../../configuration/protocols/mpls.rst:159 +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 "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`." + +#: ../../configuration/protocols/mpls.rst:165 +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 "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`." + +#: ../../configuration/system/ipv6.rst:24 +msgid "Use this command to user Layer 4 information for ECMP hashing." +msgstr "Use this command to user Layer 4 information for ECMP hashing." + +#: ../../configuration/interfaces/wireless.rst:431 +msgid "Use this command to view operational status and details wireless-specific information about all wireless interfaces." +msgstr "Use this command to view operational status and details wireless-specific information about all wireless interfaces." + +#: ../../configuration/interfaces/wireless.rst:420 +msgid "Use this command to view operational status and wireless-specific information about all wireless interfaces." +msgstr "Use this command to view operational status and wireless-specific information about all wireless interfaces." + +#: ../../configuration/interfaces/wireless.rst:498 +msgid "Use this command to view wireless interface queue information. The wireless interface identifier can range from wlan0 to wlan999." +msgstr "Use this command to view wireless interface queue information. The wireless interface identifier can range from wlan0 to wlan999." + +#: ../../configuration/service/lldp.rst:142 +msgid "Used for troubleshooting." +msgstr "Used for troubleshooting." + +#: ../../configuration/service/webproxy.rst:121 +msgid "Used to block a specific mime-type." +msgstr "Used to block a specific mime-type." + +#: ../../configuration/service/webproxy.rst:60 +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 "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." + +#: ../../configuration/system/syslog.rst:114 +msgid "User-level messages" +msgstr "User-level messages" + +#: ../../configuration/policy/examples.rst:18 +msgid "Using 'soft-reconfiguration' we get the policy update without bouncing the neighbor." +msgstr "Using 'soft-reconfiguration' we get the policy update without bouncing the neighbor." + +#: ../../configuration/interfaces/openvpn.rst:346 +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 "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." + +#: ../../configuration/protocols/bgp.rst:900 +msgid "Using BGP confederation" +msgstr "Using BGP confederation" + +#: ../../configuration/protocols/bgp.rst:899 +msgid "Using BGP route-reflectors" +msgstr "Using BGP route-reflectors" + +#: ../../configuration/interfaces/bridge.rst:225 +msgid "Using VLAN aware Bridge" +msgstr "Using VLAN aware Bridge" + +#: ../../configuration/interfaces/bridge.rst:266 +msgid "Using the operation mode command to view Bridge Information" +msgstr "Using the operation mode command to view Bridge Information" + +#: ../../configuration/interfaces/wireguard.rst:408 +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 "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." + +#: ../../configuration/protocols/bgp.rst:343 +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 "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." + +#: ../../configuration/interfaces/wireless.rst:220 +msgid "VHT (Very High Throughput) capabilities (802.11ac)" +msgstr "VHT (Very High Throughput) capabilities (802.11ac)" + +#: ../../configuration/interfaces/wireless.rst:267 +msgid "VHT link adaptation capabilities" +msgstr "VHT link adaptation capabilities" + +#: ../../configuration/interfaces/wireless.rst:245 +msgid "VHT operating channel center frequency - center freq 1 (for use with 80, 80+80 and 160 modes)" +msgstr "VHT operating channel center frequency - center freq 1 (for use with 80, 80+80 and 160 modes)" + +#: ../../configuration/interfaces/wireless.rst:248 +msgid "VHT operating channel center frequency - center freq 2 (for use with the 80+80 mode)" +msgstr "VHT operating channel center frequency - center freq 2 (for use with the 80+80 mode)" + +#: ../../configuration/interfaces/bonding.rst:275 +#: ../../configuration/interfaces/bridge.rst:123 +#: ../../configuration/interfaces/ethernet.rst:107 +#: ../../configuration/interfaces/pseudo-ethernet.rst:63 +#: ../../configuration/interfaces/virtual-ethernet.rst:30 +#: ../../configuration/interfaces/wireless.rst:398 +msgid "VLAN" +msgstr "VLAN" + +#: ../../configuration/service/pppoe-server.rst:176 +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 "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." + +#: ../../configuration/interfaces/bridge.rst:231 +msgid "VLAN 10 on member interface `eth2` (ACCESS mode)" +msgstr "VLAN 10 on member interface `eth2` (ACCESS mode)" + +#: ../../configuration/interfaces/pppoe.rst:350 +msgid "VLAN Example" +msgstr "VLAN Example" + +#: ../../configuration/interfaces/bridge.rst:134 +msgid "VLAN Options" +msgstr "VLAN Options" + +#: ../../configuration/service/lldp.rst:28 +msgid "VLAN name" +msgstr "VLAN name" + +#: ../../configuration/vpn/ipsec.rst:29 +msgid "VMware users should ensure that a VMXNET3 adapter is used. E1000 adapters have known issues with GRE processing." +msgstr "VMware users should ensure that a VMXNET3 adapter is used. E1000 adapters have known issues with GRE processing." + +#: ../../configuration/vpn/index.rst:3 +msgid "VPN" +msgstr "VPN" + +#: ../../configuration/vpn/l2tp.rst:68 +msgid "VPN-clients will request configuration parameters, optionally you can DNS parameter to the client." +msgstr "VPN-clients will request configuration parameters, optionally you can DNS parameter to the client." + +#: ../../configuration/vrf/index.rst:7 +msgid "VRF" +msgstr "VRF" + +#: ../../configuration/vrf/index.rst:409 +msgid "VRF Route Leaking" +msgstr "VRF Route Leaking" + +#: ../../configuration/vrf/index.rst:283 +msgid "VRF and NAT" +msgstr "VRF and NAT" + +#: ../../configuration/vrf/index.rst:378 +msgid "VRF blue routing table" +msgstr "VRF blue routing table" + +#: ../../configuration/vrf/index.rst:345 +msgid "VRF default routing table" +msgstr "VRF default routing table" + +#: ../../configuration/vrf/index.rst:361 +msgid "VRF red routing table" +msgstr "VRF red routing table" + +#: ../../configuration/vrf/index.rst:235 +#: ../../configuration/vrf/index.rst:242 +msgid "VRF route leaking" +msgstr "VRF route leaking" + +#: ../../configuration/vrf/index.rst:242 +msgid "VRF topology example" +msgstr "VRF topology example" + +#: ../../configuration/highavailability/index.rst:8 +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 "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." + +#: ../../configuration/highavailability/index.rst:150 +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 "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." + +#: ../../configuration/highavailability/index.rst:301 +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 "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." + +#: ../../configuration/highavailability/index.rst:28 +msgid "VRRP groups are created with the ``set high-availability vrrp group $GROUP_NAME`` commands. The required parameters are interface, vrid, and address." +msgstr "VRRP groups are created with the ``set high-availability vrrp group $GROUP_NAME`` commands. The required parameters are interface, vrid, and address." + +#: ../../configuration/highavailability/index.rst:17 +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 "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." + +#: ../../configuration/highavailability/index.rst:98 +msgid "VRRP priority can be set with ``priority`` option:" +msgstr "VRRP priority can be set with ``priority`` option:" + +#: ../../configuration/interfaces/vti.rst:5 +msgid "VTI - Virtual Tunnel Interface" +msgstr "VTI - Virtual Tunnel Interface" + +#: ../../configuration/interfaces/vxlan.rst:7 +msgid "VXLAN" +msgstr "VXLAN" + +#: ../../configuration/interfaces/vxlan.rst:17 +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 "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." + +#: ../../configuration/interfaces/vxlan.rst:49 +msgid "VXLAN specific options" +msgstr "VXLAN specific options" + +#: ../../configuration/interfaces/vxlan.rst:28 +msgid "VXLAN was officially documented by the IETF in :rfc:`7348`." +msgstr "VXLAN was officially documented by the IETF in :rfc:`7348`." + +#: ../../configuration/interfaces/wireless.rst:110 +msgid "Valid values are 0..255." +msgstr "Valid values are 0..255." + +#: ../../configuration/system/syslog.rst:167 +msgid "Value" +msgstr "Value" + +#: ../../configuration/vpn/sstp.rst:252 +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 "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." + +#: ../../configuration/vpn/sstp.rst:247 +msgid "Value to send to RADIUS server in NAS-Identifier attribute and to be matched in DM/CoA requests." +msgstr "Value to send to RADIUS server in NAS-Identifier attribute and to be matched in DM/CoA requests." + +#: ../../configuration/highavailability/index.rst:212 +#: ../../configuration/service/tftp-server.rst:65 +#: ../../configuration/vpn/openconnect.rst:83 +msgid "Verification" +msgstr "Verification" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:168 +msgid "Verification:" +msgstr "Verification:" + +#: ../../configuration/highavailability/index.rst:291 +msgid "Version" +msgstr "Version" + +#: ../../configuration/highavailability/index.rst:339 +msgid "Virtual-server" +msgstr "Virtual-server" + +#: ../../configuration/highavailability/index.rst:398 +msgid "Virtual-server can be configured with VRRP virtual address or without VRRP." +msgstr "Virtual-server can be configured with VRRP virtual address or without VRRP." + +#: ../../configuration/interfaces/virtual-ethernet.rst:7 +msgid "Virtual Ethernet" +msgstr "Virtual Ethernet" + +#: ../../configuration/highavailability/index.rst:342 +msgid "Virtual Server allows to Load-balance traffic destination virtual-address:port between several real servers." +msgstr "Virtual Server allows to Load-balance traffic destination virtual-address:port between several real servers." + +#: ../../configuration/container/index.rst:94 +msgid "Volume is either mounted as rw (read-write - default) or ro (read-only)" +msgstr "Volume is either mounted as rw (read-write - default) or ro (read-only)" + +#: ../../configuration/service/ssh.rst:30 +msgid "VyOS 1.1 supported login as user ``root``. This has been removed due to tighter security in VyOS 1.2." +msgstr "VyOS 1.1 supported login as user ``root``. This has been removed due to tighter security in VyOS 1.2." + +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +#: ../../_include/interface-dhcpv6-prefix-delegation.txt:3 +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 "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." + +#: ../../configuration/vrf/index.rst:84 +msgid "VyOS 1.4 (sagitta) introduced dynamic routing support for VRFs." +msgstr "VyOS 1.4 (sagitta) introduced dynamic routing support for VRFs." + +#: ../../configuration/pki/index.rst:9 +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 "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." + +#: ../../configuration/service/ntp.rst:33 +msgid "VyOS 1.4 uses chrony instead of ntpd (see :vytask:`T3008`) which will no longer accept anonymous NTP requests as in VyOS 1.3. All configurations will be migrated to keep the anonymous functionality. For new setups if you have clients using your VyOS installation as NTP server, you must specify the `allow-client` directive." +msgstr "VyOS 1.4 uses chrony instead of ntpd (see :vytask:`T3008`) which will no longer accept anonymous NTP requests as in VyOS 1.3. All configurations will be migrated to keep the anonymous functionality. For new setups if you have clients using your VyOS installation as NTP server, you must specify the `allow-client` directive." + +#: ../../configuration/interfaces/bonding.rst:None +msgid "VyOS Arista EOS setup" +msgstr "VyOS Arista EOS setup" + +#: ../../configuration/vpn/ipsec.rst:120 +msgid "VyOS ESP group has the next options:" +msgstr "VyOS ESP group has the next options:" + +#: ../../configuration/service/router-advert.rst:1 +msgid "VyOS Field" +msgstr "VyOS Field" + +#: ../../configuration/vpn/ipsec.rst:45 +msgid "VyOS IKE group has the next options:" +msgstr "VyOS IKE group has the next options:" + +#: ../../configuration/service/snmp.rst:202 +msgid "VyOS MIBs" +msgstr "VyOS MIBs" + +#: ../../configuration/nat/nat66.rst:None +msgid "VyOS NAT66 Simple Configure" +msgstr "VyOS NAT66 Simple Configure" + +#: ../../configuration/trafficpolicy/index.rst:624 +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 "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." + +#: ../../configuration/service/router-advert.rst:1 +msgid "VyOS Option" +msgstr "VyOS Option" + +#: ../../configuration/policy/examples.rst:92 +msgid "VyOS Policy-Based Routing (PBR) works by matching source IP address ranges and forwarding the traffic using different routing tables." +msgstr "VyOS Policy-Based Routing (PBR) works by matching source IP address ranges and forwarding the traffic using different routing tables." + +#: ../../configuration/service/snmp.rst:67 +msgid "VyOS SNMP supports both IPv4 and IPv6." +msgstr "VyOS SNMP supports both IPv4 and IPv6." + +#: ../../configuration/interfaces/sstp-client.rst:16 +msgid "VyOS also comes with a build in SSTP server, see :ref:`sstp`." +msgstr "VyOS also comes with a build in SSTP server, see :ref:`sstp`." + +#: ../../configuration/service/dhcp-server.rst:580 +msgid "VyOS also provides DHCPv6 server functionality which is described in this section." +msgstr "VyOS also provides DHCPv6 server functionality which is described in this section." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:127 +msgid "VyOS also supports two different modes of authentication, local and RADIUS. To create a new local user named \"vyos\" with a password of \"vyos\" use the following commands." +msgstr "VyOS also supports two different modes of authentication, local and RADIUS. To create a new local user named \"vyos\" with a password of \"vyos\" use the following commands." + +#: ../../configuration/vpn/dmvpn.rst:290 +msgid "VyOS can also run in DMVPN spoke mode." +msgstr "VyOS can also run in DMVPN spoke mode." + +#: ../../configuration/system/conntrack.rst:6 +msgid "VyOS can be configured to track connections using the connection tracking subsystem. Connection tracking becomes operational once either stateful firewall or NAT is configured." +msgstr "VyOS can be configured to track connections using the connection tracking subsystem. Connection tracking becomes operational once either stateful firewall or NAT is configured." + +#: ../../configuration/interfaces/openvpn.rst:573 +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 "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." + +#: ../../configuration/interfaces/ethernet.rst:34 +#: ../../configuration/interfaces/ethernet.rst:53 +msgid "VyOS default will be `auto`." +msgstr "VyOS default will be `auto`." + +#: ../../configuration/protocols/babel.rst:20 +msgid "VyOS does not have a special command to start the Babel process. The Babel process starts when the first Babel enabled interface is configured." +msgstr "VyOS does not have a special command to start the Babel process. The Babel process starts when the first Babel enabled interface is configured." + +#: ../../configuration/protocols/ospf.rst:27 +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 "VyOS does not have a special command to start the OSPF process. The OSPF process starts when the first ospf enabled interface is configured." + +#: ../../configuration/protocols/ospf.rst:1083 +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 "VyOS does not have a special command to start the OSPFv3 process. The OSPFv3 process starts when the first ospf enabled interface is configured." + +#: ../../configuration/protocols/igmp.rst:9 +msgid "VyOS facilitates IP Multicast by supporting **PIM Sparse Mode**, **IGMP** and **IGMP-Proxy**." +msgstr "VyOS facilitates IP Multicast by supporting **PIM Sparse Mode**, **IGMP** and **IGMP-Proxy**." + +#: ../../configuration/protocols/pim6.rst:7 +msgid "VyOS facilitates IPv6 Multicast by supporting **PIMv6** and **MLD**." +msgstr "VyOS facilitates IPv6 Multicast by supporting **PIMv6** and **MLD**." + +#: ../../configuration/service/dns.rst:201 +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 "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." + +#: ../../configuration/service/dns.rst:306 +msgid "VyOS is also able to use any service relying on protocols supported by ddclient." +msgstr "VyOS is also able to use any service relying on protocols supported by ddclient." + +#: ../../configuration/service/snmp.rst:72 +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 "VyOS itself supports SNMPv2_ (version 2) and SNMPv3_ (version 3) where the later is recommended because of improved security (optional authentication and encryption)." + +#: ../../configuration/trafficpolicy/index.rst:337 +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 "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)." + +#: ../../configuration/firewall/general.rst:13 +#: ../../configuration/firewall/general-legacy.rst:17 +msgid "VyOS makes use of Linux `netfilter <https://netfilter.org/>`_ for packet filtering." +msgstr "VyOS makes use of Linux `netfilter <https://netfilter.org/>`_ for packet filtering." + +#: ../../configuration/protocols/bgp.rst:12 +msgid "VyOS makes use of :abbr:`FRR (Free Range Routing)` and we would like to thank them for their effort!" +msgstr "VyOS makes use of :abbr:`FRR (Free Range Routing)` and we would like to thank them for their effort!" + +#: ../../configuration/pki/index.rst:21 +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 "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." + +#: ../../configuration/pki/index.rst:35 +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 "VyOS now also has the ability to create CAs, keys, Diffie-Hellman and other keypairs from an easy to access operational level command." + +#: ../../configuration/pki/index.rst:254 +msgid "VyOS operational mode commands are not only available for generating keys but also to display them." +msgstr "VyOS operational mode commands are not only available for generating keys but also to display them." + +#: ../../configuration/service/https.rst:7 +msgid "VyOS provide an HTTP API. You can use it to execute op-mode commands, update VyOS, set or delete config." +msgstr "VyOS provide an HTTP API. You can use it to execute op-mode commands, update VyOS, set or delete config." + +#: ../../configuration/service/dns.rst:10 +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 "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." + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:144 +msgid "VyOS provides a command to generate a connection profile used by Windows clients that will connect to the \"rw\" connection on our VyOS server." +msgstr "VyOS provides a command to generate a connection profile used by Windows clients that will connect to the \"rw\" connection on our VyOS server." + +#: ../../configuration/policy/as-path-list.rst:5 +msgid "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **as-path-list** is one of them." +msgstr "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **as-path-list** is one of them." + +#: ../../configuration/policy/community-list.rst:5 +msgid "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **community-list** is one of them." +msgstr "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **community-list** is one of them." + +#: ../../configuration/policy/extcommunity-list.rst:5 +msgid "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **extcommunity-list** is one of them." +msgstr "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **extcommunity-list** is one of them." + +#: ../../configuration/policy/large-community-list.rst:5 +msgid "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **large-community-list** is one of them." +msgstr "VyOS provides policies commands exclusively for BGP traffic filtering and manipulation: **large-community-list** is one of them." + +#: ../../configuration/interfaces/openvpn.rst:703 +msgid "VyOS provides some operational commands on OpenVPN." +msgstr "VyOS provides some operational commands on OpenVPN." + +#: ../../configuration/service/dhcp-server.rst:173 +msgid "VyOS provides support for DHCP failover. DHCP failover must be configured explicitly by the following statements." +msgstr "VyOS provides support for DHCP failover. DHCP failover must be configured explicitly by the following statements." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:8 +msgid "VyOS reverse-proxy is balancer and proxy server that provides high-availability, load balancing and proxying for TCP (level 4) and HTTP-based (level 7) applications." +msgstr "VyOS reverse-proxy is balancer and proxy server that provides high-availability, load balancing and proxying for TCP (level 4) and HTTP-based (level 7) applications." + +#: ../../configuration/protocols/igmp.rst:30 +msgid "VyOS supports both IGMP version 2 and version 3 (which allows source-specific multicast)." +msgstr "VyOS supports both IGMP version 2 and version 3 (which allows source-specific multicast)." + +#: ../../configuration/protocols/pim6.rst:22 +msgid "VyOS supports both MLD version 1 and version 2 (which allows source-specific multicast)." +msgstr "VyOS supports both MLD version 1 and version 2 (which allows source-specific multicast)." + +#: ../../configuration/system/flow-accounting.rst:7 +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 "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." + +#: ../../configuration/system/sflow.rst:5 +msgid "VyOS supports sFlow 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 "VyOS supports sFlow 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." + +#: ../../configuration/system/conntrack.rst:53 +msgid "VyOS supports setting timeouts for connections according to the connection type. You can set timeout values for generic connections, for ICMP connections, UDP connections, or for TCP connections in a number of different states." +msgstr "VyOS supports setting timeouts for connections according to the connection type. You can set timeout values for generic connections, for ICMP connections, UDP connections, or for TCP connections in a number of different states." + +#: ../../configuration/interfaces/pppoe.rst:23 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:7 +msgid "VyOS uses ISC DHCP server for both IPv4 and IPv6 address assignment." +msgstr "VyOS uses ISC DHCP server for both IPv4 and IPv6 address assignment." + +#: ../../configuration/interfaces/wwan.rst:12 +msgid "VyOS uses the `interfaces wwan` subsystem for configuration." +msgstr "VyOS uses the `interfaces wwan` subsystem for configuration." + +#: ../../_include/interface-mirror.txt:9 +#: ../../_include/interface-mirror.txt:9 +#: ../../_include/interface-mirror.txt:9 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:9 +msgid "VyOS utilizes `accel-ppp`_ to provide PPPoE server functionality. It can be used with local authentication or a connected RADIUS server." +msgstr "VyOS utilizes `accel-ppp`_ to provide PPPoE server functionality. It can be used with local authentication or a connected RADIUS server." + +#: ../../configuration/service/ipoe-server.rst:9 +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 "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." + +#: ../../configuration/vpn/l2tp.rst:6 +msgid "VyOS utilizes accel-ppp_ to provide L2TP server functionality. It can be used with local authentication or a connected RADIUS server." +msgstr "VyOS utilizes accel-ppp_ to provide L2TP server functionality. It can be used with local authentication or a connected RADIUS server." + +#: ../../configuration/vpn/sstp.rst:16 +msgid "VyOS utilizes accel-ppp_ to provide SSTP server functionality. We support both local and RADIUS authentication." +msgstr "VyOS utilizes accel-ppp_ to provide SSTP server functionality. We support both local and RADIUS authentication." + +#: ../../configuration/loadbalancing/wan.rst:31 +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 "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." + +#: ../../configuration/vpn/site2site_ipsec.rst:160 +msgid "WAN interface on `eth1`" +msgstr "WAN interface on `eth1`" + +#: ../../configuration/loadbalancing/wan.rst:4 +msgid "WAN load balancing" +msgstr "WAN load balancing" + +#: ../../configuration/interfaces/wireless.rst:7 +msgid "WLAN/WIFI - Wireless LAN" +msgstr "WLAN/WIFI - Wireless LAN" + +#: ../../configuration/interfaces/wireless.rst:145 +msgid "WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]" +msgstr "WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]" + +#: ../../configuration/interfaces/wireless.rst:351 +#: ../../configuration/interfaces/wireless.rst:551 +msgid "WPA passphrase ``12345678``" +msgstr "WPA passphrase ``12345678``" + +#: ../../configuration/interfaces/wwan.rst:7 +msgid "WWAN - Wireless Wide-Area-Network" +msgstr "WWAN - Wireless Wide-Area-Network" + +#: ../../configuration/system/syslog.rst:183 +msgid "Warning" +msgstr "Warning" + +#: ../../configuration/system/syslog.rst:183 +msgid "Warning conditions" +msgstr "Warning conditions" + +#: ../../configuration/interfaces/openvpn.rst:54 +msgid "We'll configure OpenVPN using self-signed certificates, and then discuss the legacy pre-shared key mode." +msgstr "We'll configure OpenVPN using self-signed certificates, and then discuss the legacy pre-shared key mode." + +#: ../../configuration/nat/nat44.rst:760 +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 "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." + +#: ../../configuration/vpn/ipsec.rst:232 +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 "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." + +#: ../../configuration/system/lcd.rst:41 +msgid "We can't support all displays from the beginning. If your display type is missing, please create a feature request via Phabricator_." +msgstr "We can't support all displays from the beginning. If your display type is missing, please create a feature request via Phabricator_." + +#: ../../configuration/vpn/openconnect.rst:35 +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 "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." + +#: ../../configuration/protocols/rpki.rst:158 +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 "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`:" + +#: ../../configuration/protocols/bgp.rst:1248 +msgid "We could expand on this and also deny link local and multicast in the rule 20 action deny." +msgstr "We could expand on this and also deny link local and multicast in the rule 20 action deny." + +#: ../../configuration/interfaces/openvpn.rst:633 +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 "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`)." + +#: ../../configuration/service/eventhandler.rst:78 +msgid "We don't recomend to use arguments. Using environments is more preffereble." +msgstr "We don't recomend to use arguments. Using environments is more preffereble." + +#: ../../configuration/interfaces/wireguard.rst:148 +msgid "We listen on port 51820" +msgstr "We listen on port 51820" + +#: ../../configuration/vpn/openconnect.rst:26 +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 "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:" + +#: ../../configuration/system/option.rst:85 +msgid "We now utilize `tuned` for dynamic resource balancing based on profiles." +msgstr "We now utilize `tuned` for dynamic resource balancing based on profiles." + +#: ../../configuration/interfaces/wireguard.rst:143 +msgid "We only allow the 192.168.2.0/24 subnet to travel over the tunnel" +msgstr "We only allow the 192.168.2.0/24 subnet to travel over the tunnel" + +#: ../../configuration/nat/nat44.rst:699 +msgid "We only need a single step for this interface:" +msgstr "We only need a single step for this interface:" + +#: ../../configuration/interfaces/wireguard.rst:149 +msgid "We route all traffic for the 192.168.2.0/24 network to interface `wg01`" +msgstr "We route all traffic for the 192.168.2.0/24 network to interface `wg01`" + +#: ../../configuration/system/login.rst:418 +msgid "We use a vontainer providing the TACACS serve rin this example." +msgstr "We use a vontainer providing the TACACS serve rin this example." + +#: ../../configuration/service/dhcp-server.rst:364 +msgid "Web Proxy Autodiscovery (WPAD) URL" +msgstr "Web Proxy Autodiscovery (WPAD) URL" + +#: ../../configuration/service/webproxy.rst:5 +msgid "Webproxy" +msgstr "Webproxy" + +#: ../../configuration/protocols/mpls.rst:220 +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 "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:" + +#: ../../configuration/vrf/index.rst:73 +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 "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." + +#: ../../configuration/service/dns.rst:341 +msgid "When a ``custom`` DynDNS provider is used the `<server>` where update requests are being sent to must be specified." +msgstr "When a ``custom`` DynDNS provider is used the `<server>` where update requests are being sent to must be specified." + +#: ../../configuration/service/dns.rst:334 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:60 +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 "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." + +#: ../../configuration/interfaces/bonding.rst:112 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:361 +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 "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." + +#: ../../configuration/protocols/bgp.rst:684 +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 "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." + +#: ../../configuration/protocols/bgp.rst:135 +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 "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." + +#: ../../configuration/service/pppoe-server.rst:182 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:828 +msgid "When configuring a Random-Detect policy: **the higher the precedence number, the higher the priority**." +msgstr "When configuring a Random-Detect policy: **the higher the precedence number, the higher the priority**." + +#: ../../configuration/trafficpolicy/index.rst:178 +msgid "When configuring your filter, you can use the ``Tab`` key to see the many different parameters you can configure." +msgstr "When configuring your filter, you can use the ``Tab`` key to see the many different parameters you can configure." + +#: ../../configuration/trafficpolicy/index.rst:44 +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 "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." + +#: ../../configuration/firewall/general.rst:521 +msgid "When defining a rule, it is enable by default. In some cases, it is useful to just disable the rule, rather than removing it." +msgstr "When defining a rule, it is enable by default. In some cases, it is useful to just disable the rule, rather than removing it." + +#: ../../configuration/nat/nat44.rst:299 +msgid "When defining the translated address, called ``backends``, a ``weight`` must be configured. This lets the user define load balance distribution according to their needs. Them sum of all the weights defined for the backends should be equal to 100. In oder words, the weight defined for the backend is the percentage of the connections that will receive such backend." +msgstr "When defining the translated address, called ``backends``, a ``weight`` must be configured. This lets the user define load balance distribution according to their needs. Them sum of all the weights defined for the backends should be equal to 100. In oder words, the weight defined for the backend is the percentage of the connections that will receive such backend." + +#: ../../configuration/trafficpolicy/index.rst:420 +msgid "When dequeuing, each hash-bucket with data is queried in a round robin fashion. You can configure the length of the queue." +msgstr "When dequeuing, each hash-bucket with data is queried in a round robin fashion. You can configure the length of the queue." + +#: ../../configuration/nat/nat44.rst:129 +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 "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." + +#: ../../configuration/vrf/index.rst:188 +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 "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." + +#: ../../configuration/pki/index.rst:176 +#: ../../configuration/pki/index.rst:219 +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 "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:" + +#: ../../configuration/pki/index.rst:197 +#: ../../configuration/pki/index.rst:235 +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 "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:" + +#: ../../configuration/policy/route.rst:240 +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 "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." + +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +#: ../../_include/interface-dhcpv6-options.txt:17 +msgid "When no-release is specified, dhcp6c will send a release message on client exit to prevent losing an assigned address or prefix." +msgstr "When no-release is specified, dhcp6c will send a release message on client exit to prevent losing an assigned address or prefix." + +#: ../../configuration/system/syslog.rst:233 +msgid "When no options/parameters are used, the contents of the main syslog file are displayed." +msgstr "When no options/parameters are used, the contents of the main syslog file are displayed." + +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +#: ../../_include/interface-dhcpv6-options.txt:40 +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 "When rapid-commit is specified, dhcp6c will include a rapid-commit option in solicit messages and wait for an immediate reply instead of advertisements." + +#: ../../configuration/protocols/bgp.rst:287 +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 "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." + +#: ../../configuration/trafficpolicy/index.rst:479 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:108 +msgid "When set the interface is enabled for \"dial-on-demand\"." +msgstr "When set the interface is enabled for \"dial-on-demand\"." + +#: ../../configuration/vpn/dmvpn.rst:144 +msgid "When specified, this should be the only keyword for the interface." +msgstr "When specified, this should be the only keyword for the interface." + +#: ../../configuration/system/option.rst:60 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:63 +#: ../../configuration/service/dhcp-server.rst:152 +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 "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." + +#: ../../configuration/vpn/site2site_ipsec.rst:386 +msgid "When the close-action option is set on the peers, the connection-type of each peer has to considered carefully. For example, if the option is set on both peers, then both would attempt to initiate and hold open multiple copies of each child SA. This might lead to instability of the device or cpu/memory utilization." +msgstr "When the close-action option is set on the peers, the connection-type of each peer has to considered carefully. For example, if the option is set on both peers, then both would attempt to initiate and hold open multiple copies of each child SA. This might lead to instability of the device or cpu/memory utilization." + +#: ../../configuration/firewall/general.rst:106 +#: ../../configuration/firewall/general-legacy.rst:58 +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 "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." + +#: ../../configuration/firewall/general.rst:115 +#: ../../configuration/firewall/general-legacy.rst:67 +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 "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." + +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +#: ../../_include/interface-address-with-dhcp.txt:14 +msgid "When using DHCP to retrieve IPv4 address and if local customizations are needed, they should be possible using the enter and exit hooks provided. The hook dirs are:" +msgstr "When using DHCP to retrieve IPv4 address and if local customizations are needed, they should be possible using the enter and exit hooks provided. The hook dirs are:" + +#: ../../configuration/interfaces/bonding.rst:505 +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 "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!" + +#: ../../configuration/nat/nat44.rst:351 +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 "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." + +#: ../../configuration/nat/nat44.rst:238 +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 "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." + +#: ../../configuration/protocols/rpki.rst:151 +msgid "When using SSH, known-hosts-file, private-key-file and public-key-file are mandatory options." +msgstr "When using SSH, known-hosts-file, private-key-file and public-key-file are mandatory options." + +#: ../../configuration/vpn/openconnect.rst:215 +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 "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" + +#: ../../configuration/interfaces/vti.rst:25 +msgid "When using site-to-site IPsec with VTI interfaces, be sure to disable route autoinstall" +msgstr "When using site-to-site IPsec with VTI interfaces, be sure to disable route autoinstall" + +#: ../../configuration/interfaces/bonding.rst:398 +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 "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." + +#: ../../configuration/firewall/general.rst:57 +msgid "Where, main key words and configuration paths that needs to be understood:" +msgstr "Where, main key words and configuration paths that needs to be understood:" + +#: ../../configuration/protocols/bgp.rst:108 +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 "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." + +#: ../../configuration/protocols/bgp.rst:86 +msgid "Where routes with a MED were received from the same AS, prefer the route with the lowest MED." +msgstr "Where routes with a MED were received from the same AS, prefer the route with the lowest MED." + +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +#: ../../_include/interface-ipv6.txt:77 +msgid "Whether to accept DAD (Duplicate Address Detection)." +msgstr "Whether to accept DAD (Duplicate Address Detection)." + +#: ../../configuration/nat/nat44.rst:330 +msgid "Which generates the following configuration:" +msgstr "Which generates the following configuration:" + +#: ../../configuration/nat/nat44.rst:444 +msgid "Which results in a configuration of:" +msgstr "Which results in a configuration of:" + +#: ../../configuration/nat/nat44.rst:522 +msgid "Which would generate the following NAT destination configuration:" +msgstr "Which would generate the following NAT destination configuration:" + +#: ../../configuration/firewall/general.rst:217 +#: ../../configuration/firewall/general-legacy.rst:193 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:43 +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 "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." + +#: ../../configuration/interfaces/tunnel.rst:213 +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 "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." + +#: ../../configuration/service/ssh.rst:125 +msgid "Whitelist of addresses and networks. Always allow inbound connections from these systems." +msgstr "Whitelist of addresses and networks. Always allow inbound connections from these systems." + +#: ../../configuration/interfaces/openvpn.rst:642 +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 "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." + +#: ../../configuration/interfaces/openvpn.rst:649 +msgid "Will add ``push \"keepalive 1 10\"`` to the generated OpenVPN config file." +msgstr "Will add ``push \"keepalive 1 10\"`` to the generated OpenVPN config file." + +#: ../../configuration/system/flow-accounting.rst:56 +msgid "Will be recorded only packets/flows on **incoming** direction in configured interfaces by default." +msgstr "Will be recorded only packets/flows on **incoming** direction in configured interfaces by default." + +#: ../../configuration/service/dhcp-server.rst:31 +msgid "Will drop `<shared-network-name>_` from client DNS record, using only the host declaration name and domain: `<hostname>.<domain-name>`" +msgstr "Will drop `<shared-network-name>_` from client DNS record, using only the host declaration name and domain: `<hostname>.<domain-name>`" + +#: ../../configuration/vpn/remoteaccess_ipsec.rst:147 +msgid "Windows expects the server name to be also used in the server's certificate common name, so it's best to use this DNS name for your VPN connection." +msgstr "Windows expects the server name to be also used in the server's certificate common name, so it's best to use this DNS name for your VPN connection." + +#: ../../configuration/interfaces/wireguard.rst:7 +#: ../../configuration/pki/index.rst:132 +msgid "WireGuard" +msgstr "WireGuard" + +#: ../../configuration/interfaces/wireguard.rst:0 +msgid "WireGuard Client QR code" +msgstr "WireGuard Client QR code" + +#: ../../configuration/interfaces/wireguard.rst:142 +msgid "WireGuard interface itself uses address 10.1.0.1/30" +msgstr "WireGuard interface itself uses address 10.1.0.1/30" + +#: ../../configuration/interfaces/wireguard.rst:9 +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 "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." + +#: ../../configuration/interfaces/wireguard.rst:25 +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 "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." + +#: ../../configuration/interfaces/wwan.rst:68 +msgid "WirelessModem (WWAN) options" +msgstr "WirelessModem (WWAN) options" + +#: ../../configuration/interfaces/wireless.rst:353 +#: ../../configuration/interfaces/wireless.rst:553 +msgid "Wireless channel ``1``" +msgstr "Wireless channel ``1``" + +#: ../../configuration/interfaces/wireless.rst:119 +msgid "Wireless device type for this interface" +msgstr "Wireless device type for this interface" + +#: ../../configuration/interfaces/wireless.rst:99 +msgid "Wireless hardware device used as underlay radio." +msgstr "Wireless hardware device used as underlay radio." + +#: ../../configuration/interfaces/wireless.rst:40 +msgid "Wireless options" +msgstr "Wireless options" + +#: ../../configuration/interfaces/wireless.rst:301 +msgid "Wireless options (Station/Client)" +msgstr "Wireless options (Station/Client)" + +#: ../../configuration/firewall/index.rst:23 +msgid "With VyOS being based on top of Linux and its kernel, the Netfilter project created the iptables and now the successor nftables for the Linux kernel to work directly on the data flows. This now extends the concept of zone-based security to allow for manipulating the data at multiple stages once accepted by the network interface and the driver before being handed off to the destination (e.g. a web server OR another device)." +msgstr "With VyOS being based on top of Linux and its kernel, the Netfilter project created the iptables and now the successor nftables for the Linux kernel to work directly on the data flows. This now extends the concept of zone-based security to allow for manipulating the data at multiple stages once accepted by the network interface and the driver before being handed off to the destination (e.g. a web server OR another device)." + +#: ../../configuration/interfaces/wireguard.rst:269 +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 "With WireGuard, a Road Warrior VPN config is similar to a site-to-site VPN. It just lacks the ``address`` and ``port`` statements." + +#: ../../configuration/interfaces/pppoe.rst:323 +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 "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." + +#: ../../configuration/firewall/general.rst:94 +#: ../../configuration/firewall/general-legacy.rst:46 +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 "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." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:75 +msgid "With this command, you can specify how the URL path should be matched against incoming requests." +msgstr "With this command, you can specify how the URL path should be matched against incoming requests." + +#: ../../configuration/firewall/index.rst:73 +msgid "With zone-based firewalls a new concept was implemented, in addtion to the standard in and out traffic flows, a local flow was added. This local was for traffic originating and destined to the router itself. Which means additional rules were required to secure the firewall itself from the network, in addition to the existing inbound and outbound rules from the traditional concept above." +msgstr "With zone-based firewalls a new concept was implemented, in addtion to the standard in and out traffic flows, a local flow was added. This local was for traffic originating and destined to the router itself. Which means additional rules were required to secure the firewall itself from the network, in addition to the existing inbound and outbound rules from the traditional concept above." + +#: ../../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 +msgid "Y" +msgstr "Y" + +#: ../../configuration/firewall/zone.rst:99 +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 "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." + +#: ../../configuration/system/login.rst:363 +msgid "You are able to set post-login or pre-login banner messages to display certain information for this system." +msgstr "You are able to set post-login or pre-login banner messages to display certain information for this system." + +#: ../../configuration/service/snmp.rst:206 +msgid "You are be able to download the files using SCP, once the SSH service has been activated like so" +msgstr "You are be able to download the files using SCP, once the SSH service has been activated like so" + +#: ../../configuration/highavailability/index.rst:162 +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 "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:" + +#: ../../configuration/system/conntrack.rst:86 +msgid "You can also define custom timeout values to apply to a specific subset of connections, based on a packet and flow selector. To do this, you need to create a rule defining the packet and flow selector." +msgstr "You can also define custom timeout values to apply to a specific subset of connections, based on a packet and flow selector. To do this, you need to create a rule defining the packet and flow selector." + +#: ../../configuration/service/dns.rst:299 +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 "You can also keep different DNS zone updated. Just create a new config node: ``set service dns dynamic interface <interface> rfc2136 <other-service-name>``" + +#: ../../configuration/system/ipv6.rst:106 +msgid "You can also specify which IPv6 access-list should be shown:" +msgstr "You can also specify which IPv6 access-list should be shown:" + +#: ../../configuration/protocols/igmp.rst:121 +#: ../../configuration/protocols/pim6.rst:42 +msgid "You can also tune multicast with the following commands." +msgstr "You can also tune multicast with the following commands." + +#: ../../configuration/service/pppoe-server.rst:152 +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 "You can also use another attributes for identify client for disconnect, like Framed-IP-Address, Acct-Session-Id, etc. Result commands appears in log." + +#: ../../configuration/trafficpolicy/index.rst:200 +msgid "You can also write a description for a filter:" +msgstr "You can also write a description for a filter:" + +#: ../../configuration/system/login.rst:78 +msgid "You can assign multiple keys to the same user by using a unique identifier per SSH key." +msgstr "You can assign multiple keys to the same user by using a unique identifier per SSH key." + +#: ../../configuration/nat/nat44.rst:386 +msgid "You can avoid the \"leaky\" behavior by using a firewall policy that drops \"invalid\" state packets." +msgstr "You can avoid the \"leaky\" behavior by using a firewall policy that drops \"invalid\" state packets." + +#: ../../configuration/interfaces/bonding.rst:318 +msgid "You can check your NIC driver by issuing :opcmd:`show interfaces ethernet eth0 physical | grep -i driver`" +msgstr "You can check your NIC driver by issuing :opcmd:`show interfaces ethernet eth0 physical | grep -i driver`" + +#: ../../configuration/trafficpolicy/index.rst:314 +msgid "You can configure a policy into a class through the ``queue-type`` setting." +msgstr "You can configure a policy into a class through the ``queue-type`` setting." + +#: ../../configuration/trafficpolicy/index.rst:559 +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 "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." + +#: ../../configuration/system/flow-accounting.rst:53 +msgid "You can configure multiple interfaces which whould participate in flow accounting." +msgstr "You can configure multiple interfaces which whould participate in flow accounting." + +#: ../../configuration/system/sflow.rst:32 +msgid "You can configure multiple interfaces which whould participate in sflow accounting." +msgstr "You can configure multiple interfaces which whould participate in sflow accounting." + +#: ../../_include/interface-vlan-8021q.txt:29 +#: ../../_include/interface-vlan-8021q.txt:29 +#: ../../_include/interface-vlan-8021q.txt:29 +#: ../../_include/interface-vlan-8021q.txt:29 +#: ../../_include/interface-vlan-8021q.txt:29 +#: ../../_include/interface-vlan-8021q.txt:29 +msgid "You can create multiple VLAN interfaces on a physical interface. The VLAN ID range is from 0 to 4094." +msgstr "You can create multiple VLAN interfaces on a physical interface. The VLAN ID range is from 0 to 4094." + +#: ../../configuration/highavailability/index.rst:72 +msgid "You can disable a VRRP group with ``disable`` option:" +msgstr "You can disable a VRRP group with ``disable`` option:" + +#: ../../configuration/system/ipv6.rst:148 +msgid "You can get more specific OSPFv3 information by using the parameters shown below:" +msgstr "You can get more specific OSPFv3 information by using the parameters shown below:" + +#: ../../configuration/interfaces/wireguard.rst:168 +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 "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`_." + +#: ../../configuration/service/mdns.rst:30 +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 "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!" + +#: ../../configuration/vpn/sstp.rst:320 +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 "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``." + +#: ../../configuration/system/login.rst:441 +msgid "You can now SSH into your system using admin/admin as a default user supplied from the ``lfkeitel/tacacs_plus:latest`` container." +msgstr "You can now SSH into your system using admin/admin as a default user supplied from the ``lfkeitel/tacacs_plus:latest`` container." + +#: ../../configuration/trafficpolicy/index.rst:1158 +msgid "You can only apply one policy per interface and direction, but you could reuse a policy on different interfaces and directions:" +msgstr "You can only apply one policy per interface and direction, but you could reuse a policy on different interfaces and directions:" + +#: ../../configuration/service/broadcast-relay.rst:51 +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 "You can run the UDP broadcast relay service on multiple routers connected to a subnet. There is **NO** UDP broadcast relay packet storm!" + +#: ../../configuration/service/dhcp-server.rst:211 +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 "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." + +#: ../../configuration/service/snmp.rst:197 +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 "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``" + +#: ../../configuration/firewall/general-legacy.rst:774 +msgid "You can use wildcard ``*`` to match a group of interfaces." +msgstr "You can use wildcard ``*`` to match a group of interfaces." + +#: ../../configuration/highavailability/index.rst:40 +msgid "You can verify your VRRP group status with the operational mode ``run show vrrp`` command:" +msgstr "You can verify your VRRP group status with the operational mode ``run show vrrp`` command:" + +#: ../../configuration/policy/examples.rst:208 +msgid "You can view that the policy is being correctly (or incorrectly) utilised with the following command:" +msgstr "You can view that the policy is being correctly (or incorrectly) utilised with the following command:" + +#: ../../configuration/protocols/ospf.rst:1342 +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 "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`." + +#: ../../configuration/interfaces/openvpn.rst:119 +msgid "You do **not** need to copy the certificate to the other router. Instead, you need to retrieve its SHA-256 fingerprint. OpenVPN only supports SHA-256 fingerprints at the moment, so you need to use the following command:" +msgstr "You do **not** need to copy the certificate to the other router. Instead, you need to retrieve its SHA-256 fingerprint. OpenVPN only supports SHA-256 fingerprints at the moment, so you need to use the following command:" + +#: ../../configuration/system/flow-accounting.rst:135 +msgid "You may also additionally configure timeouts for different types of connections." +msgstr "You may also additionally configure timeouts for different types of connections." + +#: ../../configuration/protocols/bgp.rst:291 +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 "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." + +#: ../../configuration/protocols/bgp.rst:314 +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 "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." + +#: ../../configuration/firewall/zone.rst:39 +msgid "You need 2 separate firewalls to define traffic: one for each direction." +msgstr "You need 2 separate firewalls to define traffic: one for each direction." + +#: ../../configuration/system/flow-accounting.rst:14 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:316 +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 "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." + +#: ../../configuration/policy/examples.rst:52 +msgid "You now see the longer AS path." +msgstr "You now see the longer AS path." + +#: ../../configuration/interfaces/pppoe.rst:340 +msgid "You should add a firewall to your configuration above as well by assigning it to the pppoe0 itself as shown here:" +msgstr "You should add a firewall to your configuration above as well by assigning it to the pppoe0 itself as shown here:" + +#: ../../configuration/interfaces/openvpn.rst:227 +#: ../../configuration/interfaces/wireguard.rst:225 +msgid "You should also ensure that the OUTISDE_LOCAL firewall group is applied to the WAN interface and a direction (local)." +msgstr "You should also ensure that the OUTISDE_LOCAL firewall group is applied to the WAN interface and a direction (local)." + +#: ../../configuration/interfaces/wireguard.rst:136 +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 "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." + +#: ../../configuration/interfaces/pppoe.rst:314 +msgid "Your ISPs modem is connected to port ``eth0`` of your VyOS box." +msgstr "Your ISPs modem is connected to port ``eth0`` of your VyOS box." + +#: ../../configuration/system/ip.rst:31 +#: ../../configuration/system/ipv6.rst:27 +#: ../../configuration/vrf/index.rst:44 +msgid "Zebra/Kernel route filtering" +msgstr "Zebra/Kernel route filtering" + +#: ../../configuration/system/ip.rst:33 +#: ../../configuration/system/ipv6.rst:29 +#: ../../configuration/vrf/index.rst:46 +msgid "Zebra supports prefix-lists and Route Mapss to match routes received from other FRR components. The permit/deny facilities provided by these commands can be used to filter which routes zebra will install in the kernel." +msgstr "Zebra supports prefix-lists and Route Mapss to match routes received from other FRR components. The permit/deny facilities provided by these commands can be used to filter which routes zebra will install in the kernel." + +#: ../../configuration/firewall/general-legacy.rst:944 +msgid "Zone-Policy Overview" +msgstr "Zone-Policy Overview" + +#: ../../configuration/firewall/index.rst:66 +msgid "Zone-based firewall" +msgstr "Zone-based firewall" + +#: ../../configuration/firewall/zone.rst:7 +msgid "Zone Based Firewall" +msgstr "Zone Based Firewall" + +#: ../../configuration/firewall/zone.rst:7 +msgid "Zone Based Firewall (Deprecated)" +msgstr "Zone Based Firewall (Deprecated)" + +#: ../../configuration/protocols/ospf.rst:792 +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 "[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." + +#: ../../configuration/service/webproxy.rst:414 +msgid "(This can be useful when a called service has many and/or often changing destination addresses - e.g. Netflix.)" +msgstr "(This can be useful when a called service has many and/or often changing destination addresses - e.g. Netflix.)" + +#: ../../configuration/protocols/isis.rst:52 +msgid ":abbr:`AFI (Address family authority identifier)` - ``49`` The AFI value 49 is what IS-IS uses for private addressing." +msgstr ":abbr:`AFI (Address family authority identifier)` - ``49`` The AFI value 49 is what IS-IS uses for private addressing." + +#: ../../configuration/protocols/static.rst:152 +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 ":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." + +#: ../../configuration/protocols/bfd.rst:11 +msgid ":abbr:`BFD (Bidirectional Forwarding Detection)` is described and extended by the following RFCs: :rfc:`5880`, :rfc:`5881` and :rfc:`5883`." +msgstr ":abbr:`BFD (Bidirectional Forwarding Detection)` is described and extended by the following RFCs: :rfc:`5880`, :rfc:`5881` and :rfc:`5883`." + +#: ../../configuration/protocols/bgp.rst:7 +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 ":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." + +#: ../../configuration/interfaces/macsec.rst:85 +msgid ":abbr:`CKN (MACsec connectivity association name)` key" +msgstr ":abbr:`CKN (MACsec connectivity association name)` key" + +#: ../../configuration/vpn/dmvpn.rst:7 +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 ":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:" + +#: ../../configuration/nat/nat44.rst:91 +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 ":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." + +#: ../../_include/interface-eapol.txt:1 +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 ":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." + +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +#: ../../_include/interface-ipv6.txt:25 +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 ":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." + +#: ../../configuration/interfaces/geneve.rst:9 +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 ":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." + +#: ../../configuration/vpn/ipsec.rst:7 +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 ":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." + +#: ../../configuration/interfaces/ethernet.rst:74 +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 ":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." + +#: ../../configuration/interfaces/ethernet.rst:64 +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 ":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." + +#: ../../configuration/protocols/igmp.rst:181 +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 ":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." + +#: ../../configuration/vpn/dmvpn.rst:14 +msgid ":abbr:`IPSec (IP Security)` - too many RFCs to list, but start with :rfc:`4301`" +msgstr ":abbr:`IPSec (IP Security)` - too many RFCs to list, but start with :rfc:`4301`" + +#: ../../configuration/protocols/isis.rst:9 +msgid ":abbr:`IS-IS (Intermediate System to Intermediate System)` is a link-state interior gateway protocol (IGP) which is described in ISO10589, :rfc:`1195`, :rfc:`5308`. 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, lowest cost) path to a destination. The intermediate systems (the name for routers) exchange topology information with their directly conencted 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. The tree database that is created with IS-IS is similar to the one that is created with OSPF in that the paths chosen should be similar. Comparisons to OSPF are inevitable and often are reasonable ones to make in regards to the way a network will respond with either IGP." +msgstr ":abbr:`IS-IS (Intermediate System to Intermediate System)` is a link-state interior gateway protocol (IGP) which is described in ISO10589, :rfc:`1195`, :rfc:`5308`. 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, lowest cost) path to a destination. The intermediate systems (the name for routers) exchange topology information with their directly conencted 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. The tree database that is created with IS-IS is similar to the one that is created with OSPF in that the paths chosen should be similar. Comparisons to OSPF are inevitable and often are reasonable ones to make in regards to the way a network will respond with either IGP." + +#: ../../configuration/vrf/index.rst:399 +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 ":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." + +#: ../../configuration/protocols/mpls.rst:46 +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 ":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." + +#: ../../configuration/service/lldp.rst:7 +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 ":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." + +#: ../../configuration/interfaces/macsec.rst:74 +msgid ":abbr:`MKA (MACsec Key Agreement protocol)` is used to synchronize keys between individual peers." +msgstr ":abbr:`MKA (MACsec Key Agreement protocol)` is used to synchronize keys between individual peers." + +#: ../../configuration/protocols/mpls.rst:7 +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 ":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." + +#: ../../configuration/nat/nat44.rst:7 +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 ":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." + +#: ../../configuration/nat/nat44.rst:121 +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 ":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." + +#: ../../configuration/protocols/isis.rst:65 +msgid ":abbr:`NET (Network Entity Title)` selector: ``00`` Must always be 00. This setting indicates \"this system\" or \"local system.\"" +msgstr ":abbr:`NET (Network Entity Title)` selector: ``00`` Must always be 00. This setting indicates \"this system\" or \"local system.\"" + +#: ../../configuration/vpn/dmvpn.rst:12 +msgid ":abbr:`NHRP (Next Hop Resolution Protocol)` :rfc:`2332`" +msgstr ":abbr:`NHRP (Next Hop Resolution Protocol)` :rfc:`2332`" + +#: ../../configuration/nat/nat66.rst:7 +msgid ":abbr:`NPTv6 (IPv6-to-IPv6 Network Prefix Translation)` is an address translation technology based on IPv6 networks, used to convert an IPv6 address prefix in an IPv6 message into another IPv6 address 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 ":abbr:`NPTv6 (IPv6-to-IPv6 Network Prefix Translation)` is an address translation technology based on IPv6 networks, used to convert an IPv6 address prefix in an IPv6 message into another IPv6 address 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." + +#: ../../configuration/service/ntp.rst:7 +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 ":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." + +#: ../../configuration/protocols/ospf.rst:7 +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 ":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." + +#: ../../configuration/interfaces/pppoe.rst:9 +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 ":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." + +#: ../../configuration/service/router-advert.rst:7 +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 ":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)`." + +#: ../../configuration/protocols/rip.rst:9 +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 ":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." + +#: ../../configuration/protocols/rpki.rst:14 +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 ":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`." + +#: ../../configuration/interfaces/ethernet.rst:82 +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 ":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:" + +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +#: ../../_include/interface-ipv6.txt:4 +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 ":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." + +#: ../../configuration/nat/nat44.rst:78 +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 ":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." + +#: ../../configuration/service/snmp.rst:7 +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 ":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." + +#: ../../configuration/nat/nat66.rst:25 +msgid ":abbr:`SNPTv6 (Source IPv6-to-IPv6 Network Prefix Translation)` The conversion function is mainly used in the following scenarios:" +msgstr ":abbr:`SNPTv6 (Source IPv6-to-IPv6 Network Prefix Translation)` The conversion function is mainly used in the following scenarios:" + +#: ../../configuration/service/ssh.rst:7 +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 ":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." + +#: ../../configuration/vpn/sstp.rst:7 +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 ":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." + +#: ../../configuration/interfaces/sstp-client.rst:9 +msgid ":abbr:`SSTP (Secure Socket Tunneling Protocol)` is a form of :abbr:`VTP (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 (by default, port can be changed) allows SSTP to pass through virtually all firewalls and proxy servers except for authenticated web proxies." +msgstr ":abbr:`SSTP (Secure Socket Tunneling Protocol)` is a form of :abbr:`VTP (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 (by default, port can be changed) allows SSTP to pass through virtually all firewalls and proxy servers except for authenticated web proxies." + +#: ../../configuration/interfaces/bridge.rst:92 +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 ":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." + +#: ../../configuration/service/tftp-server.rst:7 +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 ":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." + +#: ../../configuration/interfaces/geneve.rst:57 +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 ":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." + +#: ../../configuration/vrf/index.rst:9 +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 ":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." + +#: ../../configuration/interfaces/vxlan.rst:9 +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 ":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)`." + +#: ../../configuration/interfaces/wireless.rst:16 +msgid ":abbr:`WAP (Wireless Access-Point)` provides network access to connecting stations if the physical hardware supports acting as a WAP" +msgstr ":abbr:`WAP (Wireless Access-Point)` provides network access to connecting stations if the physical hardware supports acting as a WAP" + +#: ../../configuration/interfaces/wireless.rst:9 +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 ":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." + +#: ../../configuration/interfaces/wireless.rst:336 +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 ":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." + +#: ../../configuration/vpn/dmvpn.rst:13 +msgid ":abbr:`mGRE (Multipoint Generic Routing Encapsulation)` :rfc:`1702`" +msgstr ":abbr:`mGRE (Multipoint Generic Routing Encapsulation)` :rfc:`1702`" + +#: ../../configuration/protocols/ospf.rst:797 +msgid ":cfgcmd:`adv-router <A.B.C.D>` – router id, which link advertisements need to be reviewed." +msgstr ":cfgcmd:`adv-router <A.B.C.D>` – router id, which link advertisements need to be reviewed." + +#: ../../configuration/protocols/ospf.rst:800 +msgid ":cfgcmd:`self-originate` displays only self-originated LSAs from the local router." +msgstr ":cfgcmd:`self-originate` displays only self-originated LSAs from the local router." + +#: ../../configuration/service/conntrack-sync.rst:34 +msgid ":cfgcmd:`set service conntrack-sync interface eth0 peer 192.168.0.250`" +msgstr ":cfgcmd:`set service conntrack-sync interface eth0 peer 192.168.0.250`" + +#: ../../configuration/service/webproxy.rst:383 +msgid ":code:`set service webproxy url-filtering squidguard auto-update update-hour 23`" +msgstr ":code:`set service webproxy url-filtering squidguard auto-update update-hour 23`" + +#: ../../configuration/service/webproxy.rst:388 +msgid ":code:`set service webproxy url-filtering squidguard block-category ads`" +msgstr ":code:`set service webproxy url-filtering squidguard block-category ads`" + +#: ../../configuration/service/webproxy.rst:390 +msgid ":code:`set service webproxy url-filtering squidguard block-category malware`" +msgstr ":code:`set service webproxy url-filtering squidguard block-category malware`" + +#: ../../configuration/service/webproxy.rst:405 +msgid ":code:`set service webproxy whitelist destination-address 192.0.2.0/24`" +msgstr ":code:`set service webproxy whitelist destination-address 192.0.2.0/24`" + +#: ../../configuration/service/webproxy.rst:403 +msgid ":code:`set service webproxy whitelist destination-address 198.51.100.33`" +msgstr ":code:`set service webproxy whitelist destination-address 198.51.100.33`" + +#: ../../configuration/service/webproxy.rst:410 +msgid ":code:`set service webproxy whitelist source-address 192.168.1.2`" +msgstr ":code:`set service webproxy whitelist source-address 192.168.1.2`" + +#: ../../configuration/service/webproxy.rst:412 +msgid ":code:`set service webproxy whitelist source-address 192.168.2.0/24`" +msgstr ":code:`set service webproxy whitelist source-address 192.168.2.0/24`" + +#: ../../configuration/policy/index.rst:1 +msgid ":lastproofread:2021-07-12" +msgstr ":lastproofread:2021-07-12" + +#: ../../configuration/interfaces/wireguard.rst:177 +msgid ":opcmd:`generate pki wireguard key-pair`." +msgstr ":opcmd:`generate pki wireguard key-pair`." + +#: ../../configuration/vrf/index.rst:88 +msgid ":ref:`routing-bgp`" +msgstr ":ref:`routing-bgp`" + +#: ../../configuration/vrf/index.rst:104 +msgid ":ref:`routing-bgp`: ``set vrf name <name> protocols bgp ...``" +msgstr ":ref:`routing-bgp`: ``set vrf name <name> protocols bgp ...``" + +#: ../../configuration/vrf/index.rst:89 +msgid ":ref:`routing-isis`" +msgstr ":ref:`routing-isis`" + +#: ../../configuration/vrf/index.rst:105 +msgid ":ref:`routing-isis`: ``set vrf name <name> protocols isis ...``" +msgstr ":ref:`routing-isis`: ``set vrf name <name> protocols isis ...``" + +#: ../../configuration/vrf/index.rst:90 +msgid ":ref:`routing-ospf`" +msgstr ":ref:`routing-ospf`" + +#: ../../configuration/vrf/index.rst:106 +msgid ":ref:`routing-ospf`: ``set vrf name <name> protocols ospf ...``" +msgstr ":ref:`routing-ospf`: ``set vrf name <name> protocols ospf ...``" + +#: ../../configuration/vrf/index.rst:91 +msgid ":ref:`routing-ospfv3`" +msgstr ":ref:`routing-ospfv3`" + +#: ../../configuration/vrf/index.rst:107 +msgid ":ref:`routing-ospfv3`: ``set vrf name <name> protocols ospfv3 ...``" +msgstr ":ref:`routing-ospfv3`: ``set vrf name <name> protocols ospfv3 ...``" + +#: ../../configuration/vrf/index.rst:92 +msgid ":ref:`routing-static`" +msgstr ":ref:`routing-static`" + +#: ../../configuration/vrf/index.rst:108 +msgid ":ref:`routing-static`: ``set vrf name <name> protocols static ...``" +msgstr ":ref:`routing-static`: ``set vrf name <name> protocols static ...``" + +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +#: ../../_include/interface-dhcp-options.txt:4 +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 ":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." + +#: ../../configuration/service/dns.rst:217 +msgid ":rfc:`2136` Based" +msgstr ":rfc:`2136` Based" + +#: ../../configuration/protocols/ospf.rst:140 +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 ":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." + +#: ../../configuration/pki/index.rst:15 +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 ":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." + +#: ../../configuration/service/eventhandler.rst:19 +msgid "`1. Create an event handler`_" +msgstr "`1. Create an event handler`_" + +#: ../../configuration/service/eventhandler.rst:21 +msgid "`2. Add regex to the script`_" +msgstr "`2. Add regex to the script`_" + +#: ../../configuration/service/eventhandler.rst:23 +msgid "`3. Add a full path to the script`_" +msgstr "`3. Add a full path to the script`_" + +#: ../../configuration/service/eventhandler.rst:25 +msgid "`4. Add optional parameters`_" +msgstr "`4. Add optional parameters`_" + +#: ../../configuration/service/dhcp-server.rst:189 +msgid "`<name>` must be identical on both sides!" +msgstr "`<name>` must be identical on both sides!" + +#: ../../configuration/pki/index.rst:202 +msgid "``$ tail -n +2 ca.key | head -n -1 | tr -d '\\n'``" +msgstr "``$ tail -n +2 ca.key | head -n -1 | tr -d '\\n'``" + +#: ../../configuration/pki/index.rst:181 +msgid "``$ tail -n +2 ca.pem | head -n -1 | tr -d '\\n'``" +msgstr "``$ tail -n +2 ca.pem | head -n -1 | tr -d '\\n'``" + +#: ../../configuration/pki/index.rst:240 +msgid "``$ tail -n +2 cert.key | head -n -1 | tr -d '\\n'``" +msgstr "``$ tail -n +2 cert.key | head -n -1 | tr -d '\\n'``" + +#: ../../configuration/pki/index.rst:224 +msgid "``$ tail -n +2 cert.pem | head -n -1 | tr -d '\\n'``" +msgstr "``$ tail -n +2 cert.pem | head -n -1 | tr -d '\\n'``" + +#: ../../configuration/loadbalancing/wan.rst:274 +msgid "``+`` successful" +msgstr "``+`` successful" + +#: ../../configuration/loadbalancing/wan.rst:275 +msgid "``-`` failed" +msgstr "``-`` failed" + +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +#: ../../_include/interface-address-with-dhcp.txt:19 +msgid "``/config/scripts/dhcp-client/post-hooks.d/``" +msgstr "``/config/scripts/dhcp-client/post-hooks.d/``" + +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +#: ../../_include/interface-address-with-dhcp.txt:18 +msgid "``/config/scripts/dhcp-client/pre-hooks.d/``" +msgstr "``/config/scripts/dhcp-client/pre-hooks.d/``" + +#: ../../configuration/service/ntp.rst:49 +msgid "``0.pool.ntp.org``" +msgstr "``0.pool.ntp.org``" + +#: ../../configuration/interfaces/macsec.rst:101 +msgid "``0``: No replay window, strict check" +msgstr "``0``: No replay window, strict check" + +#: ../../configuration/interfaces/wireless.rst:256 +msgid "``0`` - 20 or 40 MHz channel width (default)" +msgstr "``0`` - 20 or 40 MHz channel width (default)" + +#: ../../configuration/interfaces/macsec.rst:102 +msgid "``1-4294967295``: Number of packets that could be misordered" +msgstr "``1-4294967295``: Number of packets that could be misordered" + +#: ../../configuration/system/console.rst:39 +msgid "``115200`` - 115,200 bps (default for serial console)" +msgstr "``115200`` - 115,200 bps (default for serial console)" + +#: ../../configuration/system/console.rst:32 +msgid "``1200`` - 1200 bps" +msgstr "``1200`` - 1200 bps" + +#: ../../configuration/system/console.rst:36 +msgid "``19200`` - 19,200 bps" +msgstr "``19200`` - 19,200 bps" + +#: ../../configuration/policy/examples.rst:162 +msgid "``192.168.2.254`` IP addreess on VyOS eth2 from ISP2" +msgstr "``192.168.2.254`` IP addreess on VyOS eth2 from ISP2" + +#: ../../configuration/service/ntp.rst:50 +msgid "``1.pool.ntp.org``" +msgstr "``1.pool.ntp.org``" + +#: ../../configuration/interfaces/wireless.rst:257 +msgid "``1`` - 80 MHz channel width" +msgstr "``1`` - 80 MHz channel width" + +#: ../../configuration/policy/examples.rst:161 +msgid "``203.0.113.254`` IP addreess on VyOS eth1 from ISP1" +msgstr "``203.0.113.254`` IP addreess on VyOS eth1 from ISP1" + +#: ../../configuration/system/console.rst:33 +msgid "``2400`` - 2400 bps" +msgstr "``2400`` - 2400 bps" + +#: ../../configuration/service/ntp.rst:51 +msgid "``2.pool.ntp.org``" +msgstr "``2.pool.ntp.org``" + +#: ../../configuration/interfaces/wireless.rst:258 +msgid "``2`` - 160 MHz channel width" +msgstr "``2`` - 160 MHz channel width" + +#: ../../configuration/system/console.rst:37 +msgid "``38400`` - 38,400 bps (default for Xen console)" +msgstr "``38400`` - 38,400 bps (default for Xen console)" + +#: ../../configuration/interfaces/wireless.rst:259 +msgid "``3`` - 80+80 MHz channel width" +msgstr "``3`` - 80+80 MHz channel width" + +#: ../../configuration/system/console.rst:34 +msgid "``4800`` - 4800 bps" +msgstr "``4800`` - 4800 bps" + +#: ../../configuration/system/console.rst:38 +msgid "``57600`` - 57,600 bps" +msgstr "``57600`` - 57,600 bps" + +#: ../../configuration/interfaces/bonding.rst:43 +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 "``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." + +#: ../../configuration/system/console.rst:35 +msgid "``9600`` - 9600 bps" +msgstr "``9600`` - 9600 bps" + +#: ../../configuration/vpn/ipsec.rst:149 +msgid "``< dh-group >`` defines a Diffie-Hellman group for PFS;" +msgstr "``< dh-group >`` defines a Diffie-Hellman group for PFS;" + +#: ../../configuration/protocols/segment-routing.rst:41 +msgid "``Known limitations:``" +msgstr "``Known limitations:``" + +#: ../../configuration/loadbalancing/wan.rst:259 +msgid "``WLB_INTERFACE_NAME=[interfacename]``: Interface to be monitored" +msgstr "``WLB_INTERFACE_NAME=[interfacename]``: Interface to be monitored" + +#: ../../configuration/loadbalancing/wan.rst:260 +msgid "``WLB_INTERFACE_STATE=[ACTIVE|FAILED]``: Interface state" +msgstr "``WLB_INTERFACE_STATE=[ACTIVE|FAILED]``: Interface state" + +#: ../../configuration/interfaces/wireless.rst:91 +msgid "``a`` - 802.11a - 54 Mbits/sec" +msgstr "``a`` - 802.11a - 54 Mbits/sec" + +#: ../../configuration/interfaces/wireless.rst:95 +msgid "``ac`` - 802.11ac - 1300 Mbits/sec" +msgstr "``ac`` - 802.11ac - 1300 Mbits/sec" + +#: ../../configuration/policy/route-map.rst:373 +msgid "``accept-own-nexthop`` - Well-known communities value accept-own-nexthop 0xFFFF0008" +msgstr "``accept-own-nexthop`` - Well-known communities value accept-own-nexthop 0xFFFF0008" + +#: ../../configuration/policy/route-map.rst:366 +msgid "``accept-own`` - Well-known communities value ACCEPT_OWN 0xFFFF0001" +msgstr "``accept-own`` - Well-known communities value ACCEPT_OWN 0xFFFF0001" + +#: ../../configuration/firewall/general.rst:334 +msgid "``accept``: accept the packet." +msgstr "``accept``: accept the packet." + +#: ../../configuration/interfaces/wireless.rst:121 +msgid "``access-point`` - Access-point forwards packets between other nodes" +msgstr "``access-point`` - Access-point forwards packets between other nodes" + +#: ../../configuration/vpn/ipsec.rst:61 +msgid "``action`` keep-alive failure action:" +msgstr "``action`` keep-alive failure action:" + +#: ../../configuration/interfaces/bonding.rst:55 +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 "``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." + +#: ../../configuration/interfaces/bonding.rst:87 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:96 +msgid "``aggressive`` use Aggressive mode for Key Exchanges in the IKEv1 protocol aggressive mode is much more insecure compared to Main mode;" +msgstr "``aggressive`` use Aggressive mode for Key Exchanges in the IKEv1 protocol aggressive mode is much more insecure compared to Main mode;" + +#: ../../configuration/protocols/failover.rst:40 +msgid "``all-available`` all checking target addresses must be available to pass this check" +msgstr "``all-available`` all checking target addresses must be available to pass this check" + +#: ../../configuration/protocols/failover.rst:43 +msgid "``any-available`` any of the checking target addresses must be available to pass this check" +msgstr "``any-available`` any of the checking target addresses must be available to pass this check" + +#: ../../configuration/vpn/site2site_ipsec.rst:355 +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 "``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." + +#: ../../configuration/vpn/site2site_ipsec.rst:18 +msgid "``authentication`` - configure authentication between VyOS and a remote peer. Suboptions:" +msgstr "``authentication`` - configure authentication between VyOS and a remote peer. Suboptions:" + +#: ../../configuration/interfaces/wireless.rst:92 +msgid "``b`` - 802.11b - 11 Mbits/sec" +msgstr "``b`` - 802.11b - 11 Mbits/sec" + +#: ../../configuration/policy/route-map.rst:164 +msgid "``babel`` - Babel routing protocol (Babel)" +msgstr "``babel`` - Babel routing protocol (Babel)" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:79 +msgid "``begin`` Matches the beginning of the URL path" +msgstr "``begin`` Matches the beginning of the URL path" + +#: ../../configuration/policy/route-map.rst:165 +msgid "``bgp`` - Border Gateway Protocol (BGP)" +msgstr "``bgp`` - Border Gateway Protocol (BGP)" + +#: ../../configuration/vpn/site2site_ipsec.rst:147 +msgid "``bind`` - select a VTI interface to bind to this peer;" +msgstr "``bind`` - select a VTI interface to bind to this peer;" + +#: ../../configuration/policy/route-map.rst:374 +msgid "``blackhole`` - Well-known communities value BLACKHOLE 0xFFFF029A" +msgstr "``blackhole`` - Well-known communities value BLACKHOLE 0xFFFF029A" + +#: ../../configuration/interfaces/bonding.rst:70 +msgid "``broadcast`` - Broadcast policy: transmits everything on all slave interfaces." +msgstr "``broadcast`` - Broadcast policy: transmits everything on all slave interfaces." + +#: ../../configuration/loadbalancing/wan.rst:86 +msgid "``burst``: Number of packets allowed to overshoot the limit within ``period``. Default 5." +msgstr "``burst``: Number of packets allowed to overshoot the limit within ``period``. Default 5." + +#: ../../configuration/vpn/site2site_ipsec.rst:56 +msgid "``ca-cert-file`` - CA certificate file. Using for authenticating remote peer;" +msgstr "``ca-cert-file`` - CA certificate file. Using for authenticating remote peer;" + +#: ../../configuration/service/lldp.rst:65 +msgid "``cdp`` - Listen for CDP for Cisco routers/switches" +msgstr "``cdp`` - Listen for CDP for Cisco routers/switches" + +#: ../../configuration/vpn/site2site_ipsec.rst:59 +msgid "``cert-file`` - certificate file, which will be used for authenticating local router on remote peer;" +msgstr "``cert-file`` - certificate file, which will be used for authenticating local router on remote peer;" + +#: ../../configuration/vpn/ipsec.rst:65 +msgid "``clear`` set action to clear;" +msgstr "``clear`` set action to clear;" + +#: ../../configuration/vpn/site2site_ipsec.rst:381 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:47 +msgid "``close-action`` defines the action to take if the remote peer unexpectedly closes a CHILD_SA:" +msgstr "``close-action`` defines the action to take if the remote peer unexpectedly closes a CHILD_SA:" + +#: ../../configuration/vpn/ipsec.rst:122 +msgid "``compression`` Enables the IPComp(IP Payload Compression) protocol which allows compressing the content of IP packets." +msgstr "``compression`` Enables the IPComp(IP Payload Compression) protocol which allows compressing the content of IP packets." + +#: ../../configuration/vpn/ipsec.rst:129 +msgid "``compression`` whether IPComp compression of content is proposed on the connection:" +msgstr "``compression`` whether IPComp compression of content is proposed on the connection:" + +#: ../../configuration/policy/route-map.rst:166 +msgid "``connected`` - Connected routes (directly attached subnet or host)" +msgstr "``connected`` - Connected routes (directly attached subnet or host)" + +#: ../../configuration/vpn/site2site_ipsec.rst:72 +msgid "``connection-type`` - how to handle this connection process. Possible variants:" +msgstr "``connection-type`` - how to handle this connection process. Possible variants:" + +#: ../../configuration/vpn/site2site_ipsec.rst:62 +msgid "``crl-file`` - file with the Certificate Revocation List. Using to check if a certificate for the remote peer is valid or revoked;" +msgstr "``crl-file`` - file with the Certificate Revocation List. Using to check if a certificate for the remote peer is valid or revoked;" + +#: ../../configuration/system/task-scheduler.rst:22 +msgid "``d`` - Execution interval in days" +msgstr "``d`` - Execution interval in days" + +#: ../../configuration/vpn/site2site_ipsec.rst:370 +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 the IPsec 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 "``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 the IPsec 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." + +#: ../../configuration/vpn/ipsec.rst:56 +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 "``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:" + +#: ../../configuration/vpn/site2site_ipsec.rst:88 +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 "``default-esp-group`` - ESP group to use by default for traffic encryption. Might be overwritten by individual settings for tunnel or VTI interface binding;" + +#: ../../configuration/vpn/site2site_ipsec.rst:92 +msgid "``description`` - description for this peer;" +msgstr "``description`` - description for this peer;" + +#: ../../configuration/vpn/ipsec.rst:101 +msgid "``dh-group`` dh-group;" +msgstr "``dh-group`` dh-group;" + +#: ../../configuration/vpn/site2site_ipsec.rst:23 +msgid "``dhcp-interface`` - ID for authentication generated from DHCP address dynamically;" +msgstr "``dhcp-interface`` - ID for authentication generated from DHCP address dynamically;" + +#: ../../configuration/vpn/site2site_ipsec.rst:94 +msgid "``dhcp-interface`` - use an IP address, received from DHCP for IPSec connection with this peer, instead of ``local-address``;" +msgstr "``dhcp-interface`` - use an IP address, received from DHCP for IPSec connection with this peer, instead of ``local-address``;" + +#: ../../configuration/vpn/ipsec.rst:88 +msgid "``disable-mobike`` disables MOBIKE Support. MOBIKE is only available for IKEv2 and enabled by default." +msgstr "``disable-mobike`` disables MOBIKE Support. MOBIKE is only available for IKEv2 and enabled by default." + +#: ../../configuration/vpn/site2site_ipsec.rst:366 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:162 +msgid "``disable-route-autoinstall`` Do not automatically install routes to remote networks;" +msgstr "``disable-route-autoinstall`` Do not automatically install routes to remote networks;" + +#: ../../configuration/vpn/site2site_ipsec.rst:119 +msgid "``disable`` - disable this tunnel;" +msgstr "``disable`` - disable this tunnel;" + +#: ../../configuration/vpn/ipsec.rst:147 +msgid "``disable`` Disable PFS;" +msgstr "``disable`` Disable PFS;" + +#: ../../configuration/vpn/ipsec.rst:132 +msgid "``disable`` disable IPComp compression (default);" +msgstr "``disable`` disable IPComp compression (default);" + +#: ../../configuration/vpn/ipsec.rst:96 +msgid "``disable`` disable MOBIKE;" +msgstr "``disable`` disable MOBIKE;" + +#: ../../configuration/firewall/general.rst:336 +msgid "``drop``: drop the packet." +msgstr "``drop``: drop the packet." + +#: ../../configuration/system/login.rst:71 +msgid "``ecdsa-sha2-nistp256``" +msgstr "``ecdsa-sha2-nistp256``" + +#: ../../configuration/system/login.rst:72 +msgid "``ecdsa-sha2-nistp384``" +msgstr "``ecdsa-sha2-nistp384``" + +#: ../../configuration/system/login.rst:73 +msgid "``ecdsa-sha2-nistp521``" +msgstr "``ecdsa-sha2-nistp521``" + +#: ../../configuration/service/lldp.rst:66 +msgid "``edp`` - Listen for EDP for Extreme routers/switches" +msgstr "``edp`` - Listen for EDP for Extreme routers/switches" + +#: ../../configuration/vpn/ipsec.rst:145 +msgid "``enable`` Inherit Diffie-Hellman group from IKE group (default);" +msgstr "``enable`` Inherit Diffie-Hellman group from IKE group (default);" + +#: ../../configuration/vpn/ipsec.rst:134 +msgid "``enable`` enable IPComp compression;" +msgstr "``enable`` enable IPComp compression;" + +#: ../../configuration/vpn/ipsec.rst:94 +msgid "``enable`` enable MOBIKE (default for IKEv2);" +msgstr "``enable`` enable MOBIKE (default for IKEv2);" + +#: ../../configuration/vpn/ipsec.rst:103 +msgid "``encryption`` encryption algorithm;" +msgstr "``encryption`` encryption algorithm;" + +#: ../../configuration/vpn/ipsec.rst:153 +msgid "``encryption`` encryption algorithm (default 128 bit AES-CBC);" +msgstr "``encryption`` encryption algorithm (default 128 bit AES-CBC);" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:80 +msgid "``end`` Matches the end of the URL path." +msgstr "``end`` Matches the end of the URL path." + +#: ../../configuration/vpn/site2site_ipsec.rst:121 +msgid "``esp-group`` - define ESP group for encrypt traffic, defined by this tunnel;" +msgstr "``esp-group`` - define ESP group for encrypt traffic, defined by this tunnel;" + +#: ../../configuration/vpn/site2site_ipsec.rst:149 +msgid "``esp-group`` - define ESP group for encrypt traffic, passed this VTI interface." +msgstr "``esp-group`` - define ESP group for encrypt traffic, passed this VTI interface." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:81 +msgid "``exact`` Requires an exactly match of the URL path" +msgstr "``exact`` Requires an exactly match of the URL path" + +#: ../../configuration/service/lldp.rst:67 +msgid "``fdp`` - Listen for FDP for Foundry routers/switches" +msgstr "``fdp`` - Listen for FDP for Foundry routers/switches" + +#: ../../configuration/vpn/site2site_ipsec.rst:68 +msgid "``file`` - path to the key file;" +msgstr "``file`` - path to the key file;" + +#: ../../configuration/vpn/ipsec.rst:164 +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 "``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;" + +#: ../../configuration/vpn/site2site_ipsec.rst:97 +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 "``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;" + +#: ../../configuration/interfaces/wireless.rst:93 +msgid "``g`` - 802.11g - 54 Mbits/sec (default)" +msgstr "``g`` - 802.11g - 54 Mbits/sec (default)" + +#: ../../configuration/policy/route-map.rst:365 +msgid "``graceful-shutdown`` - Well-known communities value GRACEFUL_SHUTDOWN 0xFFFF0000" +msgstr "``graceful-shutdown`` - Well-known communities value GRACEFUL_SHUTDOWN 0xFFFF0000" + +#: ../../configuration/system/task-scheduler.rst:21 +msgid "``h`` - Execution interval in hours" +msgstr "``h`` - Execution interval in hours" + +#: ../../configuration/vpn/ipsec.rst:105 +msgid "``hash`` hash algorithm." +msgstr "``hash`` hash algorithm." + +#: ../../configuration/vpn/ipsec.rst:155 +msgid "``hash`` hash algorithm (default sha1)." +msgstr "``hash`` hash algorithm (default sha1)." + +#: ../../configuration/vpn/ipsec.rst:52 +msgid "``hold`` set action to hold;" +msgstr "``hold`` set action to hold;" + +#: ../../configuration/vpn/ipsec.rst:63 +msgid "``hold`` set action to hold (default)" +msgstr "``hold`` set action to hold (default)" + +#: ../../configuration/interfaces/wireless.rst:154 +msgid "``ht40+`` - Both 20 MHz and 40 MHz with secondary channel above the primary channel" +msgstr "``ht40+`` - Both 20 MHz and 40 MHz with secondary channel above the primary channel" + +#: ../../configuration/interfaces/wireless.rst:152 +msgid "``ht40-`` - Both 20 MHz and 40 MHz with secondary channel below the primary channel" +msgstr "``ht40-`` - Both 20 MHz and 40 MHz with secondary channel below the primary channel" + +#: ../../configuration/system/console.rst:26 +msgid "``hvc0`` - Xen console" +msgstr "``hvc0`` - Xen console" + +#: ../../configuration/vpn/site2site_ipsec.rst:25 +msgid "``id`` - static ID's for authentication. In general local and remote address ``<x.x.x.x>``, ``<h:h:h:h:h:h:h:h>`` or ``%any``;" +msgstr "``id`` - static ID's for authentication. In general local and remote address ``<x.x.x.x>``, ``<h:h:h:h:h:h:h:h>`` or ``%any``;" + +#: ../../configuration/vpn/site2site_ipsec.rst:101 +msgid "``ike-group`` - IKE group to use for key exchanges;" +msgstr "``ike-group`` - IKE group to use for key exchanges;" + +#: ../../configuration/vpn/ipsec.rst:82 +msgid "``ikev1`` use IKEv1 for Key Exchange;" +msgstr "``ikev1`` use IKEv1 for Key Exchange;" + +#: ../../configuration/vpn/site2site_ipsec.rst:103 +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 "``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;" + +#: ../../configuration/vpn/ipsec.rst:73 +msgid "``ikev2-reauth`` whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, reauthentication is always done. Setting this parameter enables remote host re-authentication during an IKE rekey." +msgstr "``ikev2-reauth`` whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, reauthentication is always done. Setting this parameter enables remote host re-authentication during an IKE rekey." + +#: ../../configuration/vpn/ipsec.rst:75 +msgid "``ikev2-reauth`` whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, reauthentication is always done:" +msgstr "``ikev2-reauth`` whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1, reauthentication is always done:" + +#: ../../configuration/vpn/ipsec.rst:84 +msgid "``ikev2`` use IKEv2 for Key Exchange;" +msgstr "``ikev2`` use IKEv2 for Key Exchange;" + +#: ../../configuration/firewall/general-legacy.rst:751 +msgid "``in``: Ruleset for forwarded packets on an inbound interface" +msgstr "``in``: Ruleset for forwarded packets on an inbound interface" + +#: ../../configuration/vpn/site2site_ipsec.rst:75 +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 "``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;" + +#: ../../configuration/vpn/ipsec.rst:166 +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 "``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;" + +#: ../../configuration/pki/index.rst:148 +msgid "``interface`` is used for the VyOS CLI command to identify the WireGuard interface where this private key is to be used." +msgstr "``interface`` is used for the VyOS CLI command to identify the WireGuard interface where this private key is to be used." + +#: ../../configuration/policy/route-map.rst:364 +msgid "``internet`` - Well-known communities value 0" +msgstr "``internet`` - Well-known communities value 0" + +#: ../../configuration/vpn/ipsec.rst:69 +msgid "``interval`` keep-alive interval in seconds <2-86400> (default 30);" +msgstr "``interval`` keep-alive interval in seconds <2-86400> (default 30);" + +#: ../../configuration/policy/route-map.rst:167 +msgid "``isis`` - Intermediate System to Intermediate System (IS-IS)" +msgstr "``isis`` - Intermediate System to Intermediate System (IS-IS)" + +#: ../../configuration/firewall/general.rst:340 +msgid "``jump``: jump to another custom chain." +msgstr "``jump``: jump to another custom chain." + +#: ../../configuration/policy/route-map.rst:168 +msgid "``kernel`` - Kernel routes" +msgstr "``kernel`` - Kernel routes" + +#: ../../configuration/vpn/ipsec.rst:78 +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 "``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:" + +#: ../../configuration/vpn/site2site_ipsec.rst:65 +msgid "``key`` - a private key, which will be used for authenticating local router on remote peer:" +msgstr "``key`` - a private key, which will be used for authenticating local router on remote peer:" + +#: ../../configuration/system/option.rst:107 +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 "``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``." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:108 +msgid "``least-connection`` Distributes requests tp tje server wotj the fewest active connections" +msgstr "``least-connection`` Distributes requests tp tje server wotj the fewest active connections" + +#: ../../configuration/vpn/ipsec.rst:125 +msgid "``life-bytes`` ESP life in bytes <1024-26843545600000>. Number of bytes transmitted over an IPsec SA before it expires;" +msgstr "``life-bytes`` ESP life in bytes <1024-26843545600000>. Number of bytes transmitted over an IPsec SA before it expires;" + +#: ../../configuration/vpn/ipsec.rst:128 +msgid "``life-packets`` ESP life in packets <1000-26843545600000>. Number of packets transmitted over an IPsec SA before it expires;" +msgstr "``life-packets`` ESP life in packets <1000-26843545600000>. Number of packets transmitted over an IPsec SA before it expires;" + +#: ../../configuration/vpn/ipsec.rst:131 +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 "``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;" + +#: ../../configuration/vpn/ipsec.rst:86 +msgid "``lifetime`` IKE lifetime in seconds <0-86400> (default 28800);" +msgstr "``lifetime`` IKE lifetime in seconds <0-86400> (default 28800);" + +#: ../../configuration/vpn/ipsec.rst:90 +msgid "``lifetime`` IKE lifetime in seconds <30-86400> (default 28800);" +msgstr "``lifetime`` IKE lifetime in seconds <30-86400> (default 28800);" + +#: ../../configuration/policy/route-map.rst:371 +msgid "``llgr-stale`` - Well-known communities value LLGR_STALE 0xFFFF0006" +msgstr "``llgr-stale`` - Well-known communities value LLGR_STALE 0xFFFF0006" + +#: ../../configuration/vpn/site2site_ipsec.rst:107 +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 "``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;" + +#: ../../configuration/policy/route-map.rst:361 +msgid "``local-as`` - Well-known communities value NO_EXPORT_SUBCONFED 0xFFFFFF03" +msgstr "``local-as`` - Well-known communities value NO_EXPORT_SUBCONFED 0xFFFFFF03" + +#: ../../configuration/vpn/site2site_ipsec.rst:31 +msgid "``local-id`` - ID for the local VyOS router. If defined, during the authentication it will be send to remote peer;" +msgstr "``local-id`` - ID for the local VyOS router. If defined, during the authentication it will be send to remote peer;" + +#: ../../configuration/firewall/general-legacy.rst:753 +msgid "``local``: Ruleset for packets destined for this router" +msgstr "``local``: Ruleset for packets destined for this router" + +#: ../../configuration/vpn/site2site_ipsec.rst:123 +msgid "``local`` - define a local source for match traffic, which should be encrypted and send to this peer:" +msgstr "``local`` - define a local source for match traffic, which should be encrypted and send to this peer:" + +#: ../../configuration/system/task-scheduler.rst:20 +msgid "``m`` - Execution interval in minutes" +msgstr "``m`` - Execution interval in minutes" + +#: ../../configuration/policy/examples.rst:99 +msgid "``main`` Routing table used by VyOS and other interfaces not participating in PBR" +msgstr "``main`` Routing table used by VyOS and other interfaces not participating in PBR" + +#: ../../configuration/vpn/ipsec.rst:93 +msgid "``main`` use Main mode for Key Exchanges in the IKEv1 Protocol (Recommended Default);" +msgstr "``main`` use Main mode for Key Exchanges in the IKEv1 Protocol (Recommended Default);" + +#: ../../configuration/service/eventhandler.rst:72 +msgid "``message``: Full message that has triggered the script." +msgstr "``message``: Full message that has triggered the script." + +#: ../../configuration/vpn/ipsec.rst:92 +msgid "``mobike`` enable MOBIKE Support. MOBIKE is only available for IKEv2:" +msgstr "``mobike`` enable MOBIKE Support. MOBIKE is only available for IKEv2:" + +#: ../../configuration/vpn/site2site_ipsec.rst:35 +msgid "``mode`` - mode for authentication between VyOS and remote peer:" +msgstr "``mode`` - mode for authentication between VyOS and remote peer:" + +#: ../../configuration/vpn/ipsec.rst:91 +msgid "``mode`` IKEv1 Phase 1 Mode Selection:" +msgstr "``mode`` IKEv1 Phase 1 Mode Selection:" + +#: ../../configuration/vpn/ipsec.rst:136 +msgid "``mode`` the type of the connection:" +msgstr "``mode`` the type of the connection:" + +#: ../../configuration/interfaces/wireless.rst:123 +msgid "``monitor`` - Passively monitor all packets on the frequency/channel" +msgstr "``monitor`` - Passively monitor all packets on the frequency/channel" + +#: ../../configuration/interfaces/wireless.rst:240 +msgid "``multi-user-beamformee`` - Support for operation as single user beamformer" +msgstr "``multi-user-beamformee`` - Support for operation as single user beamformer" + +#: ../../configuration/interfaces/wireless.rst:239 +msgid "``multi-user-beamformer`` - Support for operation as single user beamformer" +msgstr "``multi-user-beamformer`` - Support for operation as single user beamformer" + +#: ../../configuration/interfaces/wireless.rst:94 +msgid "``n`` - 802.11n - 600 Mbits/sec" +msgstr "``n`` - 802.11n - 600 Mbits/sec" + +#: ../../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 +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 "``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." + +#: ../../configuration/firewall/general.rst:142 +#: ../../configuration/firewall/general-legacy.rst:93 +msgid "``net.ipv4.conf.all.accept_redirects``" +msgstr "``net.ipv4.conf.all.accept_redirects``" + +#: ../../configuration/firewall/general.rst:132 +#: ../../configuration/firewall/general-legacy.rst:84 +msgid "``net.ipv4.conf.all.accept_source_route``" +msgstr "``net.ipv4.conf.all.accept_source_route``" + +#: ../../configuration/firewall/general.rst:157 +#: ../../configuration/firewall/general-legacy.rst:108 +msgid "``net.ipv4.conf.all.log_martians``" +msgstr "``net.ipv4.conf.all.log_martians``" + +#: ../../configuration/firewall/general.rst:165 +#: ../../configuration/firewall/general-legacy.rst:115 +msgid "``net.ipv4.conf.all.rp_filter``" +msgstr "``net.ipv4.conf.all.rp_filter``" + +#: ../../configuration/firewall/general.rst:150 +#: ../../configuration/firewall/general-legacy.rst:101 +msgid "``net.ipv4.conf.all.send_redirects``" +msgstr "``net.ipv4.conf.all.send_redirects``" + +#: ../../configuration/firewall/general.rst:124 +#: ../../configuration/firewall/general-legacy.rst:76 +msgid "``net.ipv4.icmp_echo_ignore_broadcasts``" +msgstr "``net.ipv4.icmp_echo_ignore_broadcasts``" + +#: ../../configuration/firewall/general.rst:180 +#: ../../configuration/firewall/general-legacy.rst:129 +msgid "``net.ipv4.tcp_rfc1337``" +msgstr "``net.ipv4.tcp_rfc1337``" + +#: ../../configuration/firewall/general.rst:172 +#: ../../configuration/firewall/general-legacy.rst:122 +msgid "``net.ipv4.tcp_syncookies``" +msgstr "``net.ipv4.tcp_syncookies``" + +#: ../../configuration/firewall/general.rst:143 +#: ../../configuration/firewall/general-legacy.rst:94 +msgid "``net.ipv6.conf.all.accept_redirects``" +msgstr "``net.ipv6.conf.all.accept_redirects``" + +#: ../../configuration/firewall/general.rst:133 +#: ../../configuration/firewall/general-legacy.rst:85 +msgid "``net.ipv6.conf.all.accept_source_route``" +msgstr "``net.ipv6.conf.all.accept_source_route``" + +#: ../../configuration/policy/route-map.rst:362 +msgid "``no-advertise`` - Well-known communities value NO_ADVERTISE 0xFFFFFF02" +msgstr "``no-advertise`` - Well-known communities value NO_ADVERTISE 0xFFFFFF02" + +#: ../../configuration/policy/route-map.rst:363 +msgid "``no-export`` - Well-known communities value NO_EXPORT 0xFFFFFF01" +msgstr "``no-export`` - Well-known communities value NO_EXPORT 0xFFFFFF01" + +#: ../../configuration/policy/route-map.rst:372 +msgid "``no-llgr`` - Well-known communities value NO_LLGR 0xFFFF0007" +msgstr "``no-llgr`` - Well-known communities value NO_LLGR 0xFFFF0007" + +#: ../../configuration/policy/route-map.rst:375 +msgid "``no-peer`` - Well-known communities value NOPEER 0xFFFFFF04" +msgstr "``no-peer`` - Well-known communities value NOPEER 0xFFFFFF04" + +#: ../../configuration/vpn/ipsec.rst:80 +msgid "``no`` disable remote host re-authenticaton during an IKE rekey;" +msgstr "``no`` disable remote host re-authenticaton during an IKE rekey;" + +#: ../../configuration/system/task-scheduler.rst:19 +msgid "``none`` - Execution interval in minutes" +msgstr "``none`` - Execution interval in minutes" + +#: ../../configuration/vpn/site2site_ipsec.rst:85 +msgid "``none`` - loads the connection only, which then can be manually initiated or used as a responder configuration." +msgstr "``none`` - loads the connection only, which then can be manually initiated or used as a responder configuration." + +#: ../../configuration/vpn/ipsec.rst:50 +msgid "``none`` set action to none (default);" +msgstr "``none`` set action to none (default);" + +#: ../../configuration/service/ntp.rst:57 +msgid "``noselect`` marks the server as unused, except for display purposes. The server is discarded by the selection algorithm." +msgstr "``noselect`` marks the server as unused, except for display purposes. The server is discarded by the selection algorithm." + +#: ../../configuration/service/ntp.rst:60 +msgid "``nts`` enables Network Time Security (NTS) for the server as specified in :rfc:`8915`" +msgstr "``nts`` enables Network Time Security (NTS) for the server as specified in :rfc:`8915`" + +#: ../../configuration/vpn/ipsec.rst:160 +msgid "``options``" +msgstr "``options``" + +#: ../../configuration/policy/route-map.rst:169 +msgid "``ospf`` - Open Shortest Path First (OSPFv2)" +msgstr "``ospf`` - Open Shortest Path First (OSPFv2)" + +#: ../../configuration/policy/route-map.rst:170 +msgid "``ospfv3`` - Open Shortest Path First (IPv6) (OSPFv3)" +msgstr "``ospfv3`` - Open Shortest Path First (IPv6) (OSPFv3)" + +#: ../../configuration/firewall/general-legacy.rst:752 +msgid "``out``: Ruleset for forwarded packets on an outbound interface" +msgstr "``out``: Ruleset for forwarded packets on an outbound interface" + +#: ../../configuration/vpn/site2site_ipsec.rst:70 +msgid "``password`` - passphrase private key, if needed." +msgstr "``password`` - passphrase private key, if needed." + +#: ../../configuration/pki/index.rst:163 +msgid "``peer`` is used for the VyOS CLI command to identify the WireGuard peer where this secred is to be used." +msgstr "``peer`` is used for the VyOS CLI command to identify the WireGuard peer where this secred is to be used." + +#: ../../configuration/loadbalancing/wan.rst:88 +msgid "``period``: Time window for rate calculation. Possible values: ``second`` (one second), ``minute`` (one minute), ``hour`` (one hour). Default is ``second``." +msgstr "``period``: Time window for rate calculation. Possible values: ``second`` (one second), ``minute`` (one minute), ``hour`` (one hour). Default is ``second``." + +#: ../../configuration/vpn/ipsec.rst:142 +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 "``pfs`` whether Perfect Forward Secrecy of keys is desired on the connection's keying channel and defines a Diffie-Hellman group for PFS:" + +#: ../../configuration/service/ntp.rst:63 +msgid "``pool`` mobilizes persistent client mode association with a number of remote servers." +msgstr "``pool`` mobilizes persistent client mode association with a number of remote servers." + +#: ../../configuration/vpn/site2site_ipsec.rst:126 +#: ../../configuration/vpn/site2site_ipsec.rst:136 +msgid "``port`` - define port. Have effect only when used together with ``prefix``;" +msgstr "``port`` - define port. Have effect only when used together with ``prefix``;" + +#: ../../configuration/vpn/site2site_ipsec.rst:37 +msgid "``pre-shared-secret`` - use predefined shared secret phrase;" +msgstr "``pre-shared-secret`` - use predefined shared secret phrase;" + +#: ../../configuration/service/ntp.rst:66 +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 "``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." + +#: ../../configuration/vpn/site2site_ipsec.rst:128 +msgid "``prefix`` - IP network at local side." +msgstr "``prefix`` - IP network at local side." + +#: ../../configuration/vpn/site2site_ipsec.rst:138 +msgid "``prefix`` - IP network at remote side." +msgstr "``prefix`` - IP network at remote side." + +#: ../../configuration/vpn/ipsec.rst:107 +msgid "``prf`` pseudo-random function." +msgstr "``prf`` pseudo-random function." + +#: ../../configuration/vpn/ipsec.rst:151 +msgid "``proposal`` ESP-group proposal with number <1-65535>:" +msgstr "``proposal`` ESP-group proposal with number <1-65535>:" + +#: ../../configuration/vpn/ipsec.rst:99 +msgid "``proposal`` the list of proposals and their parameters:" +msgstr "``proposal`` the list of proposals and their parameters:" + +#: ../../configuration/vpn/site2site_ipsec.rst:130 +msgid "``protocol`` - define the protocol for match traffic, which should be encrypted and send to this peer;" +msgstr "``protocol`` - define the protocol for match traffic, which should be encrypted and send to this peer;" + +#: ../../configuration/vpn/site2site_ipsec.rst:21 +msgid "``psk`` - Preshared secret key name:" +msgstr "``psk`` - Preshared secret key name:" + +#: ../../configuration/firewall/general.rst:345 +msgid "``queue``: Enqueue packet to userspace." +msgstr "``queue``: Enqueue packet to userspace." + +#: ../../configuration/loadbalancing/wan.rst:91 +msgid "``rate``: Number of packets. Default 5." +msgstr "``rate``: Number of packets. Default 5." + +#: ../../configuration/firewall/general.rst:338 +msgid "``reject``: reject the packet." +msgstr "``reject``: reject the packet." + +#: ../../configuration/vpn/site2site_ipsec.rst:111 +msgid "``remote-address`` - remote IP address or hostname for IPSec connection. IPv4 or IPv6 address is used when a peer has a public static IP address. Hostname is a DNS name which 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 "``remote-address`` - remote IP address or hostname for IPSec connection. IPv4 or IPv6 address is used when a peer has a public static IP address. Hostname is a DNS name which 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." + +#: ../../configuration/vpn/site2site_ipsec.rst:44 +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 "``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;" + +#: ../../configuration/vpn/site2site_ipsec.rst:133 +msgid "``remote`` - define the remote destination for match traffic, which should be encrypted and send to this peer:" +msgstr "``remote`` - define the remote destination for match traffic, which should be encrypted and send to this peer:" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:64 +msgid "``req-ssl-sni`` SSL Server Name Indication (SNI) request match" +msgstr "``req-ssl-sni`` SSL Server Name Indication (SNI) request match" + +#: ../../configuration/loadbalancing/wan.rst:172 +msgid "``resp-time``: the maximum response time for ping in seconds. Range 1...30, default 5" +msgstr "``resp-time``: the maximum response time for ping in seconds. Range 1...30, default 5" + +#: ../../configuration/vpn/site2site_ipsec.rst:80 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:54 +#: ../../configuration/vpn/ipsec.rst:67 +msgid "``restart`` set action to restart;" +msgstr "``restart`` set action to restart;" + +#: ../../configuration/firewall/general.rst:342 +msgid "``return``: Return from the current chain and continue at the next rule of the last chain." +msgstr "``return``: Return from the current chain and continue at the next rule of the last chain." + +#: ../../configuration/policy/route-map.rst:171 +msgid "``rip`` - Routing Information Protocol (RIP)" +msgstr "``rip`` - Routing Information Protocol (RIP)" + +#: ../../configuration/policy/route-map.rst:172 +msgid "``ripng`` - Routing Information Protocol next-generation (IPv6) (RIPng)" +msgstr "``ripng`` - Routing Information Protocol next-generation (IPv6) (RIPng)" + +#: ../../configuration/interfaces/bonding.rst:75 +msgid "``round-robin`` - Round-robin policy: Transmit packets in sequential order from the first available slave through the last." +msgstr "``round-robin`` - Round-robin policy: Transmit packets in sequential order from the first available slave through the last." + +#: ../../configuration/loadbalancing/reverse-proxy.rst:106 +msgid "``round-robin`` Distributes requests in a circular manner, sequentially sending each request to the next server in line" +msgstr "``round-robin`` Distributes requests in a circular manner, sequentially sending each request to the next server in line" + +#: ../../configuration/policy/route-map.rst:367 +msgid "``route-filter-translated-v4`` - Well-known communities value ROUTE_FILTER_TRANSLATED_v4 0xFFFF0002" +msgstr "``route-filter-translated-v4`` - Well-known communities value ROUTE_FILTER_TRANSLATED_v4 0xFFFF0002" + +#: ../../configuration/policy/route-map.rst:369 +msgid "``route-filter-translated-v6`` - Well-known communities value ROUTE_FILTER_TRANSLATED_v6 0xFFFF0004" +msgstr "``route-filter-translated-v6`` - Well-known communities value ROUTE_FILTER_TRANSLATED_v6 0xFFFF0004" + +#: ../../configuration/policy/route-map.rst:368 +msgid "``route-filter-v4`` - Well-known communities value ROUTE_FILTER_v4 0xFFFF0003" +msgstr "``route-filter-v4`` - Well-known communities value ROUTE_FILTER_v4 0xFFFF0003" + +#: ../../configuration/policy/route-map.rst:370 +msgid "``route-filter-v6`` - Well-known communities value ROUTE_FILTER_v6 0xFFFF0005" +msgstr "``route-filter-v6`` - Well-known communities value ROUTE_FILTER_v6 0xFFFF0005" + +#: ../../configuration/vpn/site2site_ipsec.rst:48 +msgid "``rsa-key-name`` - shared RSA key for authentication. The key must be defined in the ``set vpn rsa-keys`` section;" +msgstr "``rsa-key-name`` - shared RSA key for authentication. The key must be defined in the ``set vpn rsa-keys`` section;" + +#: ../../configuration/vpn/site2site_ipsec.rst:39 +msgid "``rsa`` - use simple shared RSA key. The key must be defined in the ``set vpn rsa-keys`` section;" +msgstr "``rsa`` - use simple shared RSA key. The key must be defined in the ``set vpn rsa-keys`` section;" + +#: ../../configuration/vpn/site2site_ipsec.rst:27 +msgid "``secret`` - predefined shared secret. Used if configured mode ``pre-shared-secret``;" +msgstr "``secret`` - predefined shared secret. Used if configured mode ``pre-shared-secret``;" + +#: ../../configuration/interfaces/wireless.rst:238 +msgid "``single-user-beamformee`` - Support for operation as single user beamformee" +msgstr "``single-user-beamformee`` - Support for operation as single user beamformee" + +#: ../../configuration/interfaces/wireless.rst:237 +msgid "``single-user-beamformer`` - Support for operation as single user beamformer" +msgstr "``single-user-beamformer`` - Support for operation as single user beamformer" + +#: ../../configuration/service/lldp.rst:68 +msgid "``sonmp`` - Listen for SONMP for Nortel routers/switches" +msgstr "``sonmp`` - Listen for SONMP for Nortel routers/switches" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:104 +msgid "``source-address`` Distributes requests based on the source IP address of the client" +msgstr "``source-address`` Distributes requests based on the source IP address of the client" + +#: ../../configuration/system/login.rst:74 +msgid "``ssh-dss``" +msgstr "``ssh-dss``" + +#: ../../configuration/system/login.rst:75 +msgid "``ssh-ed25519``" +msgstr "``ssh-ed25519``" + +#: ../../configuration/system/login.rst:49 +msgid "``ssh-rsa AAAAB3NzaC1yc2EAAAABAA...VBD5lKwEWB username@host.example.com``" +msgstr "``ssh-rsa AAAAB3NzaC1yc2EAAAABAA...VBD5lKwEWB username@host.example.com``" + +#: ../../configuration/system/login.rst:76 +msgid "``ssh-rsa``" +msgstr "``ssh-rsa``" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:66 +msgid "``ssl-fc-sni-end`` SSL frontend match end of connection Server Name" +msgstr "``ssl-fc-sni-end`` SSL frontend match end of connection Server Name" + +#: ../../configuration/loadbalancing/reverse-proxy.rst:65 +msgid "``ssl-fc-sni`` SSL frontend connection Server Name Indication match" +msgstr "``ssl-fc-sni`` SSL frontend connection Server Name Indication match" + +#: ../../configuration/policy/route-map.rst:173 +msgid "``static`` - Statically configured routes" +msgstr "``static`` - Statically configured routes" + +#: ../../configuration/interfaces/wireless.rst:122 +msgid "``station`` - Connects to another access point" +msgstr "``station`` - Connects to another access point" + +#: ../../configuration/firewall/general.rst:347 +msgid "``synproxy``: synproxy the packet." +msgstr "``synproxy``: synproxy the packet." + +#: ../../configuration/system/sysctl.rst:9 +msgid "``sysctl`` is used to modify kernel parameters at runtime. The parameters available are those listed under /proc/sys/." +msgstr "``sysctl`` is used to modify kernel parameters at runtime. The parameters available are those listed under /proc/sys/." + +#: ../../configuration/policy/examples.rst:163 +msgid "``table 10`` Routing table used for ISP1" +msgstr "``table 10`` Routing table used for ISP1" + +#: ../../configuration/policy/examples.rst:97 +msgid "``table 10`` Routing table used for VLAN 10 (192.168.188.0/24)" +msgstr "``table 10`` Routing table used for VLAN 10 (192.168.188.0/24)" + +#: ../../configuration/policy/examples.rst:164 +msgid "``table 11`` Routing table used for ISP2" +msgstr "``table 11`` Routing table used for ISP2" + +#: ../../configuration/policy/examples.rst:98 +msgid "``table 11`` Routing table used for VLAN 11 (192.168.189.0/24)" +msgstr "``table 11`` Routing table used for VLAN 11 (192.168.189.0/24)" + +#: ../../configuration/policy/route-map.rst:174 +msgid "``table`` - Non-main Kernel Routing Table" +msgstr "``table`` - Non-main Kernel Routing Table" + +#: ../../configuration/loadbalancing/wan.rst:174 +msgid "``target``: the target to be sent ICMP packets to, address can be an IPv4 address or hostname" +msgstr "``target``: the target to be sent ICMP packets to, address can be an IPv4 address or hostname" + +#: ../../configuration/loadbalancing/wan.rst:176 +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 "``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" + +#: ../../configuration/loadbalancing/wan.rst:92 +msgid "``threshold``: ``below`` or ``above`` the specified rate limit." +msgstr "``threshold``: ``below`` or ``above`` the specified rate limit." + +#: ../../configuration/system/option.rst:97 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:71 +msgid "``timeout`` keep-alive timeout in seconds <2-86400> (default 120) IKEv1 only" +msgstr "``timeout`` keep-alive timeout in seconds <2-86400> (default 120) IKEv1 only" + +#: ../../configuration/interfaces/bonding.rst:80 +msgid "``transmit-load-balance`` - Adaptive transmit load balancing: channel bonding that does not require any special switch support." +msgstr "``transmit-load-balance`` - Adaptive transmit load balancing: channel bonding that does not require any special switch support." + +#: ../../configuration/vpn/ipsec.rst:140 +msgid "``transport`` transport mode;" +msgstr "``transport`` transport mode;" + +#: ../../configuration/loadbalancing/wan.rst:179 +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 "``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" + +#: ../../configuration/system/console.rst:24 +msgid "``ttySN`` - Serial device name" +msgstr "``ttySN`` - Serial device name" + +#: ../../configuration/system/console.rst:25 +msgid "``ttyUSBX`` - USB Serial device name" +msgstr "``ttyUSBX`` - USB Serial device name" + +#: ../../configuration/vpn/site2site_ipsec.rst:116 +msgid "``tunnel`` - define criteria for traffic to be matched for encrypting and send it to a peer:" +msgstr "``tunnel`` - define criteria for traffic to be matched for encrypting and send it to a peer:" + +#: ../../configuration/vpn/ipsec.rst:138 +msgid "``tunnel`` tunnel mode (default);" +msgstr "``tunnel`` tunnel mode (default);" + +#: ../../configuration/loadbalancing/wan.rst:182 +msgid "``type``: Specify the type of test. type can be ping, ttl or a user defined script" +msgstr "``type``: Specify the type of test. type can be ping, ttl or a user defined script" + +#: ../../configuration/vpn/site2site_ipsec.rst:51 +msgid "``use-x509-id`` - use local ID from x509 certificate. Cannot be used when ``id`` is defined;" +msgstr "``use-x509-id`` - use local ID from x509 certificate. Cannot be used when ``id`` is defined;" + +#: ../../configuration/vpn/ipsec.rst:168 +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 "``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." + +#: ../../configuration/policy/route-map.rst:175 +msgid "``vnc`` - Virtual Network Control (VNC)" +msgstr "``vnc`` - Virtual Network Control (VNC)" + +#: ../../configuration/vpn/site2site_ipsec.rst:140 +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 "``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:" + +#: ../../configuration/vpn/site2site_ipsec.rst:54 +msgid "``x509`` - options for x509 authentication mode:" +msgstr "``x509`` - options for x509 authentication mode:" + +#: ../../configuration/vpn/site2site_ipsec.rst:42 +msgid "``x509`` - use certificates infrastructure for authentication." +msgstr "``x509`` - use certificates infrastructure for authentication." + +#: ../../configuration/interfaces/bonding.rst:119 +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 "``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." + +#: ../../configuration/vpn/ipsec.rst:78 +msgid "``yes`` enable remote host re-authentication during an IKE rekey;" +msgstr "``yes`` enable remote host re-authentication during an IKE rekey;" + +#: ../../configuration/system/option.rst:39 +msgid "`source-address` and `source-interface` can not be used at the same time." +msgstr "`source-address` and `source-interface` can not be used at the same time." + +#: ../../configuration/protocols/rpki.rst:16 +msgid "`tweet by EvilMog`_, 2020-02-21" +msgstr "`tweet by EvilMog`_, 2020-02-21" + +#: ../../configuration/system/acceleration.rst:111 +msgid "a bandwidth test over the VPN got these results:" +msgstr "a bandwidth test over the VPN got these results:" + +#: ../../configuration/loadbalancing/wan.rst:276 +msgid "a blank indicates that no test has been carried out" +msgstr "a blank indicates that no test has been carried out" + +#: ../../configuration/nat/nat44.rst:728 +#: ../../configuration/nat/nat44.rst:733 +msgid "aes256 Encryption" +msgstr "aes256 Encryption" + +#: ../../configuration/system/syslog.rst:173 +msgid "alert" +msgstr "alert" + +#: ../../configuration/system/syslog.rst:110 +#: ../../configuration/system/syslog.rst:169 +#: ../../configuration/system/syslog.rst:219 +msgid "all" +msgstr "all" + +#: ../../configuration/vrf/index.rst:426 +msgid "an RD / RTLIST" +msgstr "an RD / RTLIST" + +#: ../../configuration/loadbalancing/wan.rst:16 +msgid "an interface with a nexthop" +msgstr "an interface with a nexthop" + +#: ../../configuration/policy/access-list.rst:38 +msgid "any: any IP address to match." +msgstr "any: any IP address to match." + +#: ../../configuration/policy/access-list.rst:67 +msgid "any: any IPv6 address to match." +msgstr "any: any IPv6 address to match." + +#: ../../configuration/system/syslog.rst:120 +msgid "auth" +msgstr "auth" + +#: ../../configuration/system/syslog.rst:221 +msgid "authorization" +msgstr "authorization" + +#: ../../configuration/interfaces/ethernet.rst:30 +msgid "auto - interface duplex setting is auto-negotiated" +msgstr "auto - interface duplex setting is auto-negotiated" + +#: ../../configuration/interfaces/ethernet.rst:41 +msgid "auto - interface speed is auto-negotiated" +msgstr "auto - interface speed is auto-negotiated" + +#: ../../configuration/service/router-advert.rst:13 +msgid "bonding" +msgstr "bonding" + +#: ../../configuration/service/dhcp-server.rst:338 +msgid "boot-size" +msgstr "boot-size" + +#: ../../configuration/service/dhcp-server.rst:331 +msgid "bootfile-name" +msgstr "bootfile-name" + +#: ../../configuration/service/dhcp-server.rst:333 +msgid "bootfile-name, filename" +msgstr "bootfile-name, filename" + +#: ../../configuration/service/dhcp-server.rst:321 +msgid "bootfile-server" +msgstr "bootfile-server" + +#: ../../configuration/service/dhcp-server.rst:336 +msgid "bootfile-size" +msgstr "bootfile-size" + +#: ../../configuration/service/router-advert.rst:14 +msgid "bridge" +msgstr "bridge" + +#: ../../configuration/service/dhcp-server.rst:269 +msgid "client-prefix-length" +msgstr "client-prefix-length" + +#: ../../configuration/vpn/pptp.rst:30 +msgid "client example (debian 9)" +msgstr "client example (debian 9)" + +#: ../../configuration/system/syslog.rst:142 +msgid "clock" +msgstr "clock" + +#: ../../configuration/system/syslog.rst:142 +msgid "clock daemon (note 2)" +msgstr "clock daemon (note 2)" + +#: ../../configuration/system/syslog.rst:178 +msgid "crit" +msgstr "crit" + +#: ../../configuration/system/syslog.rst:130 +msgid "cron" +msgstr "cron" + +#: ../../configuration/system/syslog.rst:118 +msgid "daemon" +msgstr "daemon" + +#: ../../configuration/service/dns.rst:384 +msgid "ddclient_ has another way to determine the WAN IP address. This is controlled by:" +msgstr "ddclient_ has another way to determine the WAN IP address. This is controlled by:" + +#: ../../configuration/service/dns.rst:205 +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 "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." + +#: ../../configuration/service/dns.rst:394 +msgid "ddclient_ will skip any address located before the string set in `<pattern>`." +msgstr "ddclient_ will skip any address located before the string set in `<pattern>`." + +#: ../../configuration/system/syslog.rst:191 +msgid "debug" +msgstr "debug" + +#: ../../configuration/service/router-advert.rst:1 +msgid "decrement-lifetime" +msgstr "decrement-lifetime" + +#: ../../configuration/service/dhcp-server.rst:368 +msgid "default-lease-time, max-lease-time" +msgstr "default-lease-time, max-lease-time" + +#: ../../configuration/service/router-advert.rst:1 +msgid "default-lifetime" +msgstr "default-lifetime" + +#: ../../configuration/service/router-advert.rst:1 +msgid "default-preference" +msgstr "default-preference" + +#: ../../configuration/service/dhcp-server.rst:281 +msgid "default-router" +msgstr "default-router" + +#: ../../configuration/trafficpolicy/index.rst:862 +msgid "default min-threshold" +msgstr "default min-threshold" + +#: ../../configuration/service/router-advert.rst:1 +msgid "deprecate-prefix" +msgstr "deprecate-prefix" + +#: ../../configuration/highavailability/index.rst:354 +msgid "destination-hashing" +msgstr "destination-hashing" + +#: ../../configuration/service/dhcp-server.rst:318 +msgid "dhcp-server-identifier" +msgstr "dhcp-server-identifier" + +#: ../../configuration/highavailability/index.rst:364 +msgid "direct" +msgstr "direct" + +#: ../../configuration/system/syslog.rst:223 +msgid "directory" +msgstr "directory" + +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../configuration/interfaces/pppoe.rst:228 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../configuration/interfaces/sstp-client.rst:113 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +#: ../../_include/interface-ip.txt:190 +msgid "disable: No source validation" +msgstr "disable: No source validation" + +#: ../../configuration/service/router-advert.rst:1 +msgid "dnssl" +msgstr "dnssl" + +#: ../../configuration/service/dhcp-server.rst:296 +#: ../../configuration/service/dhcp-server.rst:298 +msgid "domain-name" +msgstr "domain-name" + +#: ../../configuration/service/dhcp-server.rst:293 +msgid "domain-name-servers" +msgstr "domain-name-servers" + +#: ../../configuration/service/dhcp-server.rst:351 +#: ../../configuration/service/dhcp-server.rst:353 +msgid "domain-search" +msgstr "domain-search" + +#: ../../configuration/system/syslog.rst:171 +msgid "emerg" +msgstr "emerg" + +#: ../../configuration/firewall/general.rst:147 +msgid "enable or disable ICMPv4 redirect messages send by VyOS The following system parameter will be altered:" +msgstr "enable or disable ICMPv4 redirect messages send by VyOS The following system parameter will be altered:" + +#: ../../configuration/firewall/general-legacy.rst:98 +msgid "enable or disable ICMPv4 redirect messages send by VyOS The following system parameter will be altered:" +msgstr "enable or disable ICMPv4 redirect messages send by VyOS The following system parameter will be altered:" + +#: ../../configuration/firewall/general.rst:139 +#: ../../configuration/firewall/general-legacy.rst:90 +msgid "enable or disable of ICMPv4 or ICMPv6 redirect messages accepted by VyOS. The following system parameter will be altered:" +msgstr "enable or disable of ICMPv4 or ICMPv6 redirect messages accepted by VyOS. The following system parameter will be altered:" + +#: ../../configuration/firewall/general.rst:154 +#: ../../configuration/firewall/general-legacy.rst:105 +msgid "enable or disable the logging of martian IPv4 packets. The following system parameter will be altered:" +msgstr "enable or disable the logging of martian IPv4 packets. The following system parameter will be altered:" + +#: ../../configuration/system/syslog.rst:181 +msgid "err" +msgstr "err" + +#: ../../configuration/service/router-advert.rst:15 +msgid "ethernet" +msgstr "ethernet" + +#: ../../configuration/policy/access-list.rst:68 +msgid "exact-match: exact match of the network prefixes." +msgstr "exact-match: exact match of the network prefixes." + +#: ../../configuration/service/dhcp-server.rst:376 +msgid "exclude" +msgstr "exclude" + +#: ../../configuration/service/dhcp-server.rst:381 +msgid "failover" +msgstr "failover" + +#: ../../configuration/interfaces/bonding.rst:155 +msgid "fast: Request partner to transmit LACPDUs every 1 second" +msgstr "fast: Request partner to transmit LACPDUs every 1 second" + +#: ../../configuration/system/syslog.rst:225 +msgid "file <file name>" +msgstr "file <file name>" + +#: ../../configuration/protocols/bgp.rst:826 +#: ../../configuration/protocols/bgp.rst:832 +msgid "filter-list" +msgstr "filter-list" + +#: ../../configuration/system/syslog.rst:134 +msgid "ftp" +msgstr "ftp" + +#: ../../configuration/interfaces/ethernet.rst:31 +msgid "full - always use full-duplex" +msgstr "full - always use full-duplex" + +#: ../../configuration/interfaces/ethernet.rst:32 +msgid "half - always use half-duplex" +msgstr "half - always use half-duplex" + +#: ../../configuration/service/router-advert.rst:1 +msgid "hop-limit" +msgstr "hop-limit" + +#: ../../configuration/policy/access-list.rst:39 +msgid "host: single host IP address to match." +msgstr "host: single host IP address to match." + +#: ../../configuration/system/option.rst:89 +msgid "https://access.redhat.com/sites/default/files/attachments/201501-perf-brief-low-latency-tuning-rhel7-v2.1.pdf" +msgstr "https://access.redhat.com/sites/default/files/attachments/201501-perf-brief-low-latency-tuning-rhel7-v2.1.pdf" + +#: ../../configuration/interfaces/openvpn.rst:675 +msgid "https://community.openvpn.net/openvpn/wiki/DataChannelOffload/Features" +msgstr "https://community.openvpn.net/openvpn/wiki/DataChannelOffload/Features" + +#: ../../configuration/system/acceleration.rst:28 +msgid "if there is a supported device, enable Intel® QAT" +msgstr "if there is a supported device, enable Intel® QAT" + +#: ../../configuration/system/acceleration.rst:24 +msgid "if there is non device the command will show ```No QAT device found```" +msgstr "if there is non device the command will show ```No QAT device found```" + +#: ../../configuration/system/syslog.rst:189 +msgid "info" +msgstr "info" + +#: ../../configuration/service/router-advert.rst:1 +msgid "interval" +msgstr "interval" + +#: ../../configuration/protocols/rpki.rst:56 +msgid "invalid" +msgstr "invalid" + +#: ../../configuration/policy/access-list.rst:40 +msgid "inverse-match: network/netmask to match (requires network be defined)." +msgstr "inverse-match: network/netmask to match (requires network be defined)." + +#: ../../configuration/service/dhcp-server.rst:301 +#: ../../configuration/service/dhcp-server.rst:303 +msgid "ip-forwarding" +msgstr "ip-forwarding" + +#: ../../configuration/interfaces/ethernet.rst:90 +msgid "it can be used with any NIC," +msgstr "it can be used with any NIC," + +#: ../../configuration/interfaces/ethernet.rst:92 +msgid "it does not increase hardware device interrupt rate (although it does introduce inter-processor interrupts (IPIs))." +msgstr "it does not increase hardware device interrupt rate (although it does introduce inter-processor interrupts (IPIs))." + +#: ../../configuration/system/syslog.rst:112 +msgid "kern" +msgstr "kern" + +#: ../../configuration/service/router-advert.rst:16 +msgid "l2tpv3" +msgstr "l2tpv3" + +#: ../../configuration/service/dhcp-server.rst:366 +msgid "lease" +msgstr "lease" + +#: ../../configuration/highavailability/index.rst:351 +msgid "least-connection" +msgstr "least-connection" + +#: ../../configuration/vpn/site2site_ipsec.rst:271 +msgid "left local_ip: 192.168.0.10 # VPN Gateway, behind NAT device" +msgstr "left local_ip: 192.168.0.10 # VPN Gateway, behind NAT device" + +#: ../../configuration/vpn/site2site_ipsec.rst:163 +msgid "left local_ip: `198.51.100.3` # server side WAN IP" +msgstr "left local_ip: `198.51.100.3` # server side WAN IP" + +#: ../../configuration/vpn/site2site_ipsec.rst:272 +msgid "left public_ip:172.18.201.10" +msgstr "left public_ip:172.18.201.10" + +#: ../../configuration/vpn/site2site_ipsec.rst:161 +msgid "left subnet: `192.168.0.0/24` site1, server side (i.e. locality, actually there is no client or server roles)" +msgstr "left subnet: `192.168.0.0/24` site1, server side (i.e. locality, actually there is no client or server roles)" + +#: ../../configuration/service/router-advert.rst:1 +msgid "link-mtu" +msgstr "link-mtu" + +#: ../../configuration/system/syslog.rst:144 +msgid "local0" +msgstr "local0" + +#: ../../configuration/system/syslog.rst:146 +msgid "local1" +msgstr "local1" + +#: ../../configuration/system/syslog.rst:148 +msgid "local2" +msgstr "local2" + +#: ../../configuration/system/syslog.rst:150 +msgid "local3" +msgstr "local3" + +#: ../../configuration/system/syslog.rst:152 +msgid "local4" +msgstr "local4" + +#: ../../configuration/system/syslog.rst:154 +msgid "local5" +msgstr "local5" + +#: ../../configuration/system/syslog.rst:156 +msgid "local6" +msgstr "local6" + +#: ../../configuration/system/syslog.rst:158 +msgid "local7" +msgstr "local7" + +#: ../../configuration/system/syslog.rst:144 +msgid "local use 0 (local0)" +msgstr "local use 0 (local0)" + +#: ../../configuration/system/syslog.rst:146 +msgid "local use 1 (local1)" +msgstr "local use 1 (local1)" + +#: ../../configuration/system/syslog.rst:148 +msgid "local use 2 (local2)" +msgstr "local use 2 (local2)" + +#: ../../configuration/system/syslog.rst:150 +msgid "local use 3 (local3)" +msgstr "local use 3 (local3)" + +#: ../../configuration/system/syslog.rst:152 +msgid "local use 4 (local4)" +msgstr "local use 4 (local4)" + +#: ../../configuration/system/syslog.rst:154 +msgid "local use 5 (local5)" +msgstr "local use 5 (local5)" + +#: ../../configuration/system/syslog.rst:158 +msgid "local use 7 (local7)" +msgstr "local use 7 (local7)" + +#: ../../configuration/highavailability/index.rst:355 +msgid "locality-based-least-connection" +msgstr "locality-based-least-connection" + +#: ../../configuration/system/syslog.rst:140 +msgid "logalert" +msgstr "logalert" + +#: ../../configuration/system/syslog.rst:138 +msgid "logaudit" +msgstr "logaudit" + +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../configuration/interfaces/pppoe.rst:224 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../configuration/interfaces/sstp-client.rst:109 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +#: ../../_include/interface-ip.txt:186 +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 "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." + +#: ../../configuration/system/syslog.rst:124 +msgid "lpr" +msgstr "lpr" + +#: ../../configuration/service/mdns.rst:2 +msgid "mDNS Repeater" +msgstr "mDNS Repeater" + +#: ../../configuration/service/mdns.rst:28 +msgid "mDNS repeater can be temporarily disabled without deleting the service using" +msgstr "mDNS repeater can be temporarily disabled without deleting the service using" + +#: ../../configuration/system/syslog.rst:116 +msgid "mail" +msgstr "mail" + +#: ../../configuration/service/router-advert.rst:1 +msgid "managed-flag" +msgstr "managed-flag" + +#: ../../configuration/policy/route.rst:125 +msgid "match-frag: Second and further fragments of fragmented packets." +msgstr "match-frag: Second and further fragments of fragmented packets." + +#: ../../configuration/policy/route.rst:146 +msgid "match-ipsec: match inbound IPsec packets." +msgstr "match-ipsec: match inbound IPsec packets." + +#: ../../configuration/policy/route.rst:126 +msgid "match-non-frag: Head fragments or unfragmented packets." +msgstr "match-non-frag: Head fragments or unfragmented packets." + +#: ../../configuration/policy/route.rst:147 +msgid "match-none: match inbound non-IPsec packets." +msgstr "match-none: match inbound non-IPsec packets." + +#: ../../configuration/highavailability/index.rst:32 +msgid "minimal config" +msgstr "minimal config" + +#: ../../configuration/protocols/segment-routing.rst:115 +msgid "more information related IGP - :ref:`routing-isis`" +msgstr "more information related IGP - :ref:`routing-isis`" + +#: ../../configuration/protocols/segment-routing.rst:184 +msgid "more information related IGP - :ref:`routing-ospf`" +msgstr "more information related IGP - :ref:`routing-ospf`" + +#: ../../configuration/service/dhcp-server.rst:291 +#: ../../configuration/service/router-advert.rst:1 +msgid "name-server" +msgstr "name-server" + +#: ../../configuration/service/dhcp-server.rst:313 +msgid "netbios-name-servers" +msgstr "netbios-name-servers" + +#: ../../configuration/policy/access-list.rst:41 +msgid "network: network/netmask to match (requires inverse-match be defined)." +msgstr "network: network/netmask to match (requires inverse-match be defined)." + +#: ../../configuration/policy/access-list.rst:69 +msgid "network: network/netmask to match (requires inverse-match be defined) BUG, NO invert-match option in access-list6" +msgstr "network: network/netmask to match (requires inverse-match be defined) BUG, NO invert-match option in access-list6" + +#: ../../configuration/system/syslog.rst:126 +msgid "news" +msgstr "news" + +#: ../../configuration/service/dhcp-server.rst:323 +msgid "next-server" +msgstr "next-server" + +#: ../../configuration/service/router-advert.rst:1 +msgid "no-autonomous-flag" +msgstr "no-autonomous-flag" + +#: ../../configuration/service/router-advert.rst:1 +msgid "no-on-link-flag" +msgstr "no-on-link-flag" + +#: ../../configuration/protocols/rpki.rst:61 +msgid "notfound" +msgstr "notfound" + +#: ../../configuration/system/syslog.rst:185 +msgid "notice" +msgstr "notice" + +#: ../../configuration/system/syslog.rst:136 +msgid "ntp" +msgstr "ntp" + +#: ../../configuration/service/dhcp-server.rst:306 +msgid "ntp-server" +msgstr "ntp-server" + +#: ../../configuration/service/dhcp-server.rst:308 +msgid "ntp-servers" +msgstr "ntp-servers" + +#: ../../configuration/loadbalancing/wan.rst:17 +msgid "one rule with a LAN (inbound-interface) and the WAN (interface)." +msgstr "one rule with a LAN (inbound-interface) and the WAN (interface)." + +#: ../../configuration/service/router-advert.rst:17 +msgid "openvpn" +msgstr "openvpn" + +#: ../../configuration/protocols/ospf.rst:207 +msgid "ospfd supports Opaque LSA :rfc:`2370` as partial support for MPLS Traffic Engineering LSAs. The opaque-lsa capability must be enabled in the configuration." +msgstr "ospfd supports Opaque LSA :rfc:`2370` as partial support for MPLS Traffic Engineering LSAs. The opaque-lsa capability must be enabled in the configuration." + +#: ../../configuration/service/router-advert.rst:1 +msgid "other-config-flag" +msgstr "other-config-flag" + +#: ../../configuration/vpn/index.rst:18 +msgid "pages to sort" +msgstr "pages to sort" + +#: ../../configuration/policy/as-path-list.rst:13 +msgid "policy as-path-list" +msgstr "policy as-path-list" + +#: ../../configuration/policy/community-list.rst:13 +msgid "policy community-list" +msgstr "policy community-list" + +#: ../../configuration/policy/extcommunity-list.rst:13 +msgid "policy extcommunity-list" +msgstr "policy extcommunity-list" + +#: ../../configuration/policy/large-community-list.rst:13 +msgid "policy large-community-list" +msgstr "policy large-community-list" + +#: ../../configuration/service/dhcp-server.rst:346 +#: ../../configuration/service/dhcp-server.rst:348 +msgid "pop-server" +msgstr "pop-server" + +#: ../../configuration/service/router-advert.rst:1 +msgid "preferred-lifetime" +msgstr "preferred-lifetime" + +#: ../../configuration/protocols/bgp.rst:827 +#: ../../configuration/protocols/bgp.rst:831 +msgid "prefix-list, distribute-list" +msgstr "prefix-list, distribute-list" + +#: ../../configuration/service/router-advert.rst:18 +msgid "pseudo-ethernet" +msgstr "pseudo-ethernet" + +#: ../../configuration/service/dhcp-server.rst:371 +#: ../../configuration/service/dhcp-server.rst:373 +msgid "range" +msgstr "range" + +#: ../../configuration/service/router-advert.rst:1 +msgid "reachable-time" +msgstr "reachable-time" + +#: ../../configuration/system/ip.rst:82 +msgid "reset commands" +msgstr "reset commands" + +#: ../../configuration/service/router-advert.rst:1 +msgid "retrans-timer" +msgstr "retrans-timer" + +#: ../../configuration/service/dhcp-server.rst:358 +msgid "rfc3442-static-route, windows-static-route" +msgstr "rfc3442-static-route, windows-static-route" + +#: ../../configuration/highavailability/index.rst:200 +msgid "rfc3768-compatibility" +msgstr "rfc3768-compatibility" + +#: ../../configuration/vpn/site2site_ipsec.rst:273 +msgid "right local_ip: 172.18.202.10 # right side WAN IP" +msgstr "right local_ip: 172.18.202.10 # right side WAN IP" + +#: ../../configuration/vpn/site2site_ipsec.rst:165 +msgid "right local_ip: `203.0.113.2` # remote office side WAN IP" +msgstr "right local_ip: `203.0.113.2` # remote office side WAN IP" + +#: ../../configuration/vpn/site2site_ipsec.rst:164 +msgid "right subnet: `10.0.0.0/24` site2,remote office side" +msgstr "right subnet: `10.0.0.0/24` site2,remote office side" + +#: ../../configuration/highavailability/index.rst:349 +msgid "round-robin" +msgstr "round-robin" + +#: ../../configuration/protocols/bgp.rst:825 +#: ../../configuration/protocols/bgp.rst:833 +msgid "route-map" +msgstr "route-map" + +#: ../../configuration/service/dhcp-server.rst:283 +msgid "routers" +msgstr "routers" + +#: ../../configuration/system/flow-accounting.rst:144 +#: ../../configuration/system/sflow.rst:3 +msgid "sFlow" +msgstr "sFlow" + +#: ../../configuration/system/sflow.rst:7 +msgid "sFlow is a technology that enables monitoring of network traffic by sending sampled packets to a collector device." +msgstr "sFlow is a technology that enables monitoring of network traffic by sending sampled packets to a collector device." + +#: ../../configuration/system/syslog.rst:132 +msgid "security" +msgstr "security" + +#: ../../configuration/service/dhcp-server.rst:316 +msgid "server-identifier" +msgstr "server-identifier" + +#: ../../configuration/vpn/pptp.rst:17 +msgid "server example" +msgstr "server example" + +#: ../../configuration/system/conntrack.rst:98 +msgid "set a destination and/or source address. Accepted input:" +msgstr "set a destination and/or source address. Accepted input:" + +#: ../../configuration/nat/nat44.rst:729 +#: ../../configuration/nat/nat44.rst:734 +msgid "sha256 Hashes" +msgstr "sha256 Hashes" + +#: ../../configuration/system/ip.rst:50 +msgid "show commands" +msgstr "show commands" + +#: ../../configuration/service/dhcp-server.rst:322 +msgid "siaddr" +msgstr "siaddr" + +#: ../../configuration/interfaces/bonding.rst:153 +msgid "slow: Request partner to transmit LACPDUs every 30 seconds" +msgstr "slow: Request partner to transmit LACPDUs every 30 seconds" + +#: ../../configuration/service/dhcp-server.rst:341 +#: ../../configuration/service/dhcp-server.rst:343 +msgid "smtp-server" +msgstr "smtp-server" + +#: ../../configuration/interfaces/ethernet.rst:91 +msgid "software filters can easily be added to hash over new protocols," +msgstr "software filters can easily be added to hash over new protocols," + +#: ../../configuration/highavailability/index.rst:353 +msgid "source-hashing" +msgstr "source-hashing" + +#: ../../configuration/vpn/dmvpn.rst:241 +msgid "spoke01-spoke04" +msgstr "spoke01-spoke04" + +#: ../../configuration/vpn/dmvpn.rst:288 +msgid "spoke05" +msgstr "spoke05" + +#: ../../configuration/service/dhcp-server.rst:386 +msgid "static-mapping" +msgstr "static-mapping" + +#: ../../configuration/service/dhcp-server.rst:356 +msgid "static-route" +msgstr "static-route" + +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../configuration/interfaces/pppoe.rst:220 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../configuration/interfaces/sstp-client.rst:105 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +#: ../../_include/interface-ip.txt:182 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:271 +msgid "subnet-mask" +msgstr "subnet-mask" + +#: ../../configuration/system/syslog.rst:122 +msgid "syslog" +msgstr "syslog" + +#: ../../configuration/system/syslog.rst:228 +msgid "tail" +msgstr "tail" + +#: ../../configuration/trafficpolicy/index.rst:18 +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 "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." + +#: ../../configuration/service/dhcp-server.rst:326 +#: ../../configuration/service/dhcp-server.rst:328 +msgid "tftp-server-name" +msgstr "tftp-server-name" + +#: ../../configuration/protocols/segment-routing.rst:98 +#: ../../configuration/protocols/segment-routing.rst:176 +msgid "this option allows to configure prefix-sid on SR. The ‘no-php-flag’ means NO Penultimate Hop Popping that allows SR node to request to its neighbor to not pop the label. The ‘explicit-null’ flag allows SR node to request to its neighbor to send IP packet with the EXPLICIT-NULL label. The ‘n-flag-clear’ option can be used to explicitly clear the Node flag that is set by default for Prefix-SIDs associated to loopback addresses. This option is necessary to configure Anycast-SIDs." +msgstr "this option allows to configure prefix-sid on SR. The ‘no-php-flag’ means NO Penultimate Hop Popping that allows SR node to request to its neighbor to not pop the label. The ‘explicit-null’ flag allows SR node to request to its neighbor to send IP packet with the EXPLICIT-NULL label. The ‘n-flag-clear’ option can be used to explicitly clear the Node flag that is set by default for Prefix-SIDs associated to loopback addresses. This option is necessary to configure Anycast-SIDs." + +#: ../../configuration/service/dhcp-server.rst:275 +#: ../../configuration/service/dhcp-server.rst:277 +msgid "time-offset" +msgstr "time-offset" + +#: ../../configuration/service/dhcp-server.rst:286 +msgid "time-server" +msgstr "time-server" + +#: ../../configuration/service/dhcp-server.rst:288 +msgid "time-servers" +msgstr "time-servers" + +#: ../../configuration/highavailability/index.rst:365 +#: ../../configuration/service/router-advert.rst:19 +msgid "tunnel" +msgstr "tunnel" + +#: ../../configuration/system/syslog.rst:156 +msgid "use 6 (local6)" +msgstr "use 6 (local6)" + +#: ../../configuration/system/acceleration.rst:16 +msgid "use this command to check if there is an Intel® QAT supported Processor in your system." +msgstr "use this command to check if there is an Intel® QAT supported Processor in your system." + +#: ../../configuration/system/syslog.rst:114 +msgid "user" +msgstr "user" + +#: ../../configuration/system/syslog.rst:128 +msgid "uucp" +msgstr "uucp" + +#: ../../configuration/protocols/rpki.rst:50 +msgid "valid" +msgstr "valid" + +#: ../../configuration/service/router-advert.rst:1 +msgid "valid-lifetime" +msgstr "valid-lifetime" + +#: ../../configuration/interfaces/virtual-ethernet.rst:13 +msgid "veth interfaces need to be created in pairs - it's called the peer name" +msgstr "veth interfaces need to be created in pairs - it's called the peer name" + +#: ../../configuration/service/router-advert.rst:20 +msgid "vxlan" +msgstr "vxlan" + +#: ../../configuration/system/syslog.rst:183 +msgid "warning" +msgstr "warning" + +#: ../../configuration/protocols/segment-routing.rst:189 +msgid "we described the configuration SR ISIS / SR OSPF using 2 connected with them to share label information." +msgstr "we described the configuration SR ISIS / SR OSPF using 2 connected with them to share label information." + +#: ../../configuration/highavailability/index.rst:352 +msgid "weighted-least-connection" +msgstr "weighted-least-connection" + +#: ../../configuration/highavailability/index.rst:350 +msgid "weighted-round-robin" +msgstr "weighted-round-robin" + +#: ../../configuration/trafficpolicy/index.rst:93 +msgid "while a *byte* is written as a single **b**." +msgstr "while a *byte* is written as a single **b**." + +#: ../../configuration/service/dhcp-server.rst:311 +msgid "wins-server" +msgstr "wins-server" + +#: ../../configuration/service/router-advert.rst:21 +msgid "wireguard" +msgstr "wireguard" + +#: ../../configuration/service/router-advert.rst:22 +msgid "wireless" +msgstr "wireless" + +#: ../../configuration/system/acceleration.rst:133 +msgid "with :cfgcmd:`set system acceleration qat` on both systems the bandwidth increases." +msgstr "with :cfgcmd:`set system acceleration qat` on both systems the bandwidth increases." + +#: ../../configuration/service/dhcp-server.rst:361 +msgid "wpad-url" +msgstr "wpad-url" + +#: ../../configuration/service/dhcp-server.rst:363 +msgid "wpad-url, wpad-url code 252 = text" +msgstr "wpad-url, wpad-url code 252 = text" + +#: ../../configuration/service/router-advert.rst:23 +msgid "wwan" +msgstr "wwan" diff --git a/docs/_locale/ja/contributing.pot b/docs/_locale/ja/contributing.pot new file mode 100644 index 00000000..0b6bc28f --- /dev/null +++ b/docs/_locale/ja/contributing.pot @@ -0,0 +1,1727 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../contributing/development.rst:653 +msgid "\"${vyos_libexecdir}/validators/foo bar $VAR(@)\" will be executed, <constraintErrorMessage> will be displayed on failure" +msgstr "\"${vyos_libexecdir}/validators/foo bar $VAR(@)\" will be executed, <constraintErrorMessage> will be displayed on failure" + +#: ../../contributing/development.rst:647 +msgid "<constraintErrorMessage> will be displayed on failure" +msgstr "<constraintErrorMessage> will be displayed on failure" + +#: ../../contributing/development.rst:632 +msgid "<node name=\"mynode\"> </node>" +msgstr "<node name=\"mynode\"> </node>" + +#: ../../contributing/development.rst:667 +msgid "<properties> <completionHelp> <list> foo bar </list>" +msgstr "<properties> <completionHelp> <list> foo bar </list>" + +#: ../../contributing/development.rst:670 +msgid "<properties> <completionHelp> <path> vpn ipsec esp-group </path> ..." +msgstr "<properties> <completionHelp> <path> vpn ipsec esp-group </path> ..." + +#: ../../contributing/development.rst:673 +msgid "<properties> <completionHelp> <script> /path/to/script </script> ..." +msgstr "<properties> <completionHelp> <script> /path/to/script </script> ..." + +#: ../../contributing/development.rst:646 +msgid "<properties> <constraint> <regex> ..." +msgstr "<properties> <constraint> <regex> ..." + +#: ../../contributing/development.rst:652 +msgid "<properties> <constraint> <validator> <name =\"foo\" argument=\"bar\">" +msgstr "<properties> <constraint> <validator> <name =\"foo\" argument=\"bar\">" + +#: ../../contributing/development.rst:638 +msgid "<properties> <help>My node</help>" +msgstr "<properties> <help>My node</help>" + +#: ../../contributing/development.rst:664 +msgid "<properties> <multi/>" +msgstr "<properties> <multi/>" + +#: ../../contributing/development.rst:660 +msgid "<properties> <priority>999</priority>" +msgstr "<properties> <priority>999</priority>" + +#: ../../contributing/development.rst:641 +msgid "<properties> <valueHelp> <format> format </format> <description> some string </description>" +msgstr "<properties> <valueHelp> <format> format </format> <description> some string </description>" + +#: ../../contributing/development.rst:635 +msgid "<tagNode name=\"mynode> </node>" +msgstr "<tagNode name=\"mynode> </node>" + +#: ../../contributing/upstream-packages.rst:81 +msgid "A fork with packaging changes for VyOS is kept at https://github.com/vyos/hvinfo" +msgstr "A fork with packaging changes for VyOS is kept at https://github.com/vyos/hvinfo" + +#: ../../contributing/development.rst:31 +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 "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``." + +#: ../../contributing/debugging.rst:44 +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 "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." + +#: ../../contributing/development.rst:74 +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 "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``" + +#: ../../contributing/development.rst:569 +msgid "Abbreviations and acronyms **must** be capitalized." +msgstr "Abbreviations and acronyms **must** be capitalized." + +#: ../../contributing/build-vyos.rst:403 +#: ../../contributing/build-vyos.rst:591 +msgid "Accel-PPP" +msgstr "Accel-PPP" + +#: ../../contributing/development.rst:577 +msgid "Acronyms also **must** be capitalized to visually distinguish them from normal words:" +msgstr "Acronyms also **must** be capitalized to visually distinguish them from normal words:" + +#: ../../contributing/development.rst:165 +msgid "Add file to Git index using ``git add myfile``, or for a whole directory: ``git add somedir/*``" +msgstr "Add file to Git index using ``git add myfile``, or for a whole directory: ``git add somedir/*``" + +#: ../../contributing/testing.rst:99 +msgid "Add one or more IP addresses" +msgstr "Add one or more IP addresses" + +#: ../../contributing/development.rst:502 +msgid "Address" +msgstr "Address" + +#: ../../contributing/build-vyos.rst:800 +msgid "After a minute or two you will find the generated DEB packages next to the vyos-1x source directory:" +msgstr "After a minute or two you will find the generated DEB packages next to the vyos-1x source directory:" + +#: ../../contributing/build-vyos.rst:627 +#: ../../contributing/build-vyos.rst:656 +#: ../../contributing/build-vyos.rst:691 +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 "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." + +#: ../../contributing/testing.rst:50 +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 "After its first boot into the newly installed system the main Smoketest script is executed, it can be found here: `/usr/bin/vyos-smoketest`" + +#: ../../contributing/development.rst:7 +msgid "All VyOS source code is hosted on GitHub under the VyOS organization which can be found here: https://github.com/vyos" +msgstr "All VyOS source code is hosted on GitHub under the VyOS organization which can be found here: https://github.com/vyos" + +#: ../../contributing/development.rst:680 +msgid "All commit time checks should be in the verify() function of the script" +msgstr "All commit time checks should be in the verify() function of the script" + +#: ../../contributing/development.rst:514 +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 "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." + +#: ../../contributing/issues-features.rst:14 +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 "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." + +#: ../../contributing/development.rst:683 +msgid "All logic should be in the scripts" +msgstr "All logic should be in the scripts" + +#: ../../contributing/development.rst:90 +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 "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)" + +#: ../../contributing/development.rst:99 +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 "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." + +#: ../../contributing/development.rst:336 +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 "Another advantage is testability of the code. Mocking the entire config subsystem is hard, while constructing an internal representation by hand is way simpler." + +#: ../../contributing/build-vyos.rst:702 +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 "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." + +#: ../../contributing/build-vyos.rst:831 +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 "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." + +#: ../../contributing/testing.rst:56 +msgid "As Smoketests will alter the system configuration and you are logged in remote you may loose your connection to the system." +msgstr "As Smoketests will alter the system configuration and you are logged in remote you may loose your connection to the system." + +#: ../../contributing/testing.rst:12 +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 "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." + +#: ../../contributing/build-vyos.rst:777 +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 "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." + +#: ../../contributing/development.rst:175 +msgid "Attach patch to Phabricator task" +msgstr "Attach patch to Phabricator task" + +#: ../../contributing/development.rst:619 +msgid "Bad: \"Disables IPv6 forwarding\"" +msgstr "Bad: \"Disables IPv6 forwarding\"" + +#: ../../contributing/development.rst:563 +msgid "Bad: \"Frobnication algorithm.\"" +msgstr "Bad: \"Frobnication algorithm.\"" + +#: ../../contributing/development.rst:605 +msgid "Bad: \"Set TCP connection timeout\"" +msgstr "Bad: \"Set TCP connection timeout\"" + +#: ../../contributing/development.rst:562 +msgid "Bad: \"frobnication algorithm\"" +msgstr "Bad: \"frobnication algorithm\"" + +#: ../../contributing/development.rst:574 +msgid "Bad: \"tcp connection timeout\"" +msgstr "Bad: \"tcp connection timeout\"" + +#: ../../contributing/development.rst:594 +msgid "Bad: PPPOE, IPSEC" +msgstr "Bad: PPPOE, IPSEC" + +#: ../../contributing/development.rst:595 +msgid "Bad: pppoe, ipsec" +msgstr "Bad: pppoe, ipsec" + +#: ../../contributing/development.rst:583 +msgid "Bad: radius (unless it's about the distance between a center of a circle and any of its points)" +msgstr "Bad: radius (unless it's about the distance between a center of a circle and any of its points)" + +#: ../../contributing/debugging.rst:160 +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 "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." + +#: ../../contributing/debugging.rst:170 +msgid "Boot Timing" +msgstr "Boot Timing" + +#: ../../contributing/issues-features.rst:10 +msgid "Bug Report/Issue" +msgstr "Bug Report/Issue" + +#: ../../contributing/build-vyos.rst:785 +msgid "Build" +msgstr "Build" + +#: ../../contributing/build-vyos.rst:60 +msgid "Build Container" +msgstr "Build Container" + +#: ../../contributing/build-vyos.rst:182 +msgid "Build ISO" +msgstr "Build ISO" + +#: ../../contributing/build-vyos.rst:5 +msgid "Build VyOS" +msgstr "Build VyOS" + +#: ../../contributing/build-vyos.rst:85 +msgid "Build from source" +msgstr "Build from source" + +#: ../../contributing/build-vyos.rst:582 +msgid "Building Out-Of-Tree Modules" +msgstr "Building Out-Of-Tree Modules" + +#: ../../contributing/build-vyos.rst:435 +msgid "Building The Kernel" +msgstr "Building The Kernel" + +#: ../../contributing/build-vyos.rst:246 +msgid "Building VyOS on Windows WSL2 with Docker integrated into WSL2 will work like a charm. No problems are known so far!" +msgstr "Building VyOS on Windows WSL2 with Docker integrated into WSL2 will work like a charm. No problems are known so far!" + +#: ../../contributing/build-vyos.rst:705 +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 "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." + +#: ../../contributing/build-vyos.rst:584 +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 "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." + +#: ../../contributing/build-vyos.rst:475 +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 "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." + +#: ../../contributing/build-vyos.rst:13 +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 "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`." + +#: ../../contributing/development.rst:247 +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 "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." + +#: ../../contributing/development.rst:686 +msgid "C++ Backend Code" +msgstr "C++ Backend Code" + +#: ../../contributing/development.rst:551 +msgid "Capitalization and punctuation" +msgstr "Capitalization and punctuation" + +#: ../../contributing/build-vyos.rst:448 +msgid "Check out the required kernel version - see ``vyos-build/data/defaults.json`` file (example uses kernel 4.19.146):" +msgstr "Check out the required kernel version - see ``vyos-build/data/defaults.json`` file (example uses kernel 4.19.146):" + +#: ../../contributing/development.rst:149 +msgid "Clone: ``git clone https://github.com/<user>/vyos-1x.git``" +msgstr "Clone: ``git clone https://github.com/<user>/vyos-1x.git``" + +#: ../../contributing/build-vyos.rst:441 +msgid "Clone the kernel source to `vyos-build/packages/linux-kernel/`:" +msgstr "Clone the kernel source to `vyos-build/packages/linux-kernel/`:" + +#: ../../contributing/development.rst:187 +msgid "Coding Guidelines" +msgstr "Coding Guidelines" + +#: ../../contributing/development.rst:490 +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 "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." + +#: ../../contributing/development.rst:168 +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 "Commit the changes by calling ``git commit``. Please use a meaningful commit headline (read above) and don't forget to reference the Phabricator_ ID." + +#: ../../contributing/testing.rst:151 +msgid "Config Load Tests" +msgstr "Config Load Tests" + +#: ../../contributing/debugging.rst:132 +msgid "Config Migration Scripts" +msgstr "Config Migration Scripts" + +#: ../../contributing/debugging.rst:158 +msgid "Configuration Error on System Boot" +msgstr "Configuration Error on System Boot" + +#: ../../contributing/development.rst:260 +msgid "Configuration Script Structure and Behaviour" +msgstr "Configuration Script Structure and Behaviour" + +#: ../../contributing/issues-features.rst:24 +msgid "Consult the documentation_ to ensure that you have configured your system correctly" +msgstr "Consult the documentation_ to ensure that you have configured your system correctly" + +#: ../../contributing/development.rst:705 +msgid "Continuous Integration" +msgstr "Continuous Integration" + +#: ../../contributing/build-vyos.rst:255 +msgid "Customize" +msgstr "Customize" + +#: ../../contributing/testing.rst:100 +msgid "DHCP client and DHCPv6 prefix delegation" +msgstr "DHCP client and DHCPv6 prefix delegation" + +#: ../../contributing/upstream-packages.rst:46 +msgid "DMVPN patches are added by this commit: https://github.com/vyos/vyos-strongswan/commit/1cf12b0f2f921bfc51affa3b81226" +msgstr "DMVPN patches are added by this commit: https://github.com/vyos/vyos-strongswan/commit/1cf12b0f2f921bfc51affa3b81226" + +#: ../../contributing/build-vyos.rst:713 +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 "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." + +#: ../../contributing/build-vyos.rst:154 +msgid "Debian Bullseye for VyOS 1.4 (sagitta, current) - aka the rolling release" +msgstr "Debian Bullseye for VyOS 1.4 (sagitta, current) - aka the rolling release" + +#: ../../contributing/build-vyos.rst:153 +msgid "Debian Buster for VyOS 1.3 (equuleus)" +msgstr "Debian Buster for VyOS 1.3 (equuleus)" + +#: ../../contributing/build-vyos.rst:152 +msgid "Debian Jessie for VyOS 1.2 (crux)" +msgstr "Debian Jessie for VyOS 1.2 (crux)" + +#: ../../contributing/upstream-packages.rst:31 +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 "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" + +#: ../../contributing/debugging.rst:5 +msgid "Debugging" +msgstr "Debugging" + +#: ../../contributing/debugging.rst:96 +msgid "Debugging Python Code with PDB" +msgstr "Debugging Python Code with PDB" + +#: ../../contributing/development.rst:503 +msgid "Description" +msgstr "Description" + +#: ../../contributing/development.rst:120 +msgid "Determinine source package" +msgstr "Determinine source package" + +#: ../../contributing/development.rst:5 +msgid "Development" +msgstr "Development" + +#: ../../contributing/development.rst:643 +msgid "Do not add angle brackets around the format, they will be inserted automatically" +msgstr "Do not add angle brackets around the format, they will be inserted automatically" + +#: ../../contributing/build-vyos.rst:33 +msgid "Docker" +msgstr "Docker" + +#: ../../contributing/build-vyos.rst:73 +msgid "Dockerhub" +msgstr "Dockerhub" + +#: ../../contributing/build-vyos.rst:50 +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 "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`_." + +#: ../../contributing/upstream-packages.rst:17 +msgid "Due to issues in the upstream version that sometimes set interfaces down, a modified version is used." +msgstr "Due to issues in the upstream version that sometimes set interfaces down, a modified version is used." + +#: ../../contributing/debugging.rst:172 +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 "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." + +#: ../../contributing/development.rst:717 +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 "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/." + +#: ../../contributing/build-vyos.rst:407 +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 "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:" + +#: ../../contributing/development.rst:504 +msgid "Enabled/Disabled" +msgstr "Enabled/Disabled" + +#: ../../contributing/issues-features.rst:29 +msgid "Ensure the problem is reproducible" +msgstr "Ensure the problem is reproducible" + +#: ../../contributing/development.rst:104 +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 "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." + +#: ../../contributing/development.rst:412 +#: ../../contributing/testing.rst:65 +msgid "Example:" +msgstr "Example:" + +#: ../../contributing/development.rst:559 +#: ../../contributing/development.rst:571 +#: ../../contributing/development.rst:580 +#: ../../contributing/development.rst:591 +#: ../../contributing/development.rst:602 +#: ../../contributing/development.rst:616 +msgid "Examples:" +msgstr "Examples:" + +#: ../../contributing/development.rst:377 +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 "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." + +#: ../../contributing/development.rst:182 +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 "Export last commit to patch file: ``git format-patch`` or export the last two commits into its appropriate patch files: ``git format-patch -2``" + +#: ../../contributing/development.rst:657 +msgid "External arithmetic validator may be added if there's demand, complex validation is better left to commit-time scripts" +msgstr "External arithmetic validator may be added if there's demand, complex validation is better left to commit-time scripts" + +#: ../../contributing/debugging.rst:87 +msgid "FRR" +msgstr "FRR" + +#: ../../contributing/issues-features.rst:68 +msgid "Feature Request" +msgstr "Feature Request" + +#: ../../contributing/build-vyos.rst:560 +msgid "Firmware" +msgstr "Firmware" + +#: ../../contributing/build-vyos.rst:593 +msgid "First, clone the source code and check out the appropriate version by running:" +msgstr "First, clone the source code and check out the appropriate version by running:" + +#: ../../contributing/development.rst:177 +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 "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)" + +#: ../../contributing/development.rst:85 +msgid "Followed by a message which describes all the details like:" +msgstr "Followed by a message which describes all the details like:" + +#: ../../contributing/debugging.rst:48 +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 "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." + +#: ../../contributing/development.rst:384 +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 "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." + +#: ../../contributing/debugging.rst:55 +msgid "For example, ``/tmp/vyos.ifconfig.debug`` can be created to enable interface debugging." +msgstr "For example, ``/tmp/vyos.ifconfig.debug`` can be created to enable interface debugging." + +#: ../../contributing/debugging.rst:61 +msgid "For example running, ``export VYOS_IFCONFIG_DEBUG=\"\"`` on your vbash, will have the same effect as ``touch /tmp/vyos.ifconfig.debug``." +msgstr "For example running, ``export VYOS_IFCONFIG_DEBUG=\"\"`` on your vbash, will have the same effect as ``touch /tmp/vyos.ifconfig.debug``." + +#: ../../contributing/build-vyos.rst:170 +msgid "For the packages required, you can refer to the ``docker/Dockerfile`` file in the repository_. The ``./build-vyos-image`` script will also warn you if any dependencies are missing." +msgstr "For the packages required, you can refer to the ``docker/Dockerfile`` file in the repository_. The ``./build-vyos-image`` script will also warn you if any dependencies are missing." + +#: ../../contributing/development.rst:151 +msgid "Fork: ``git remote add myfork https://github.com/<user>/vyos-1x.git``" +msgstr "Fork: ``git remote add myfork https://github.com/<user>/vyos-1x.git``" + +#: ../../contributing/development.rst:138 +msgid "Fork Repository and submit Patch" +msgstr "Fork Repository and submit Patch" + +#: ../../contributing/development.rst:140 +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 "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" + +#: ../../contributing/development.rst:200 +msgid "Formatting" +msgstr "Formatting" + +#: ../../contributing/development.rst:495 +msgid "GNU Preprocessor" +msgstr "GNU Preprocessor" + +#: ../../contributing/issues-features.rst:26 +msgid "Get community support via Slack_ or our Forum_" +msgstr "Get community support via Slack_ or our Forum_" + +#: ../../contributing/development.rst:618 +msgid "Good: \"Disable IPv6 forwarding\"" +msgstr "Good: \"Disable IPv6 forwarding\"" + +#: ../../contributing/development.rst:561 +msgid "Good: \"Frobnication algorithm\"" +msgstr "Good: \"Frobnication algorithm\"" + +#: ../../contributing/development.rst:573 +#: ../../contributing/development.rst:604 +msgid "Good: \"TCP connection timeout\"" +msgstr "Good: \"TCP connection timeout\"" + +#: ../../contributing/development.rst:593 +msgid "Good: PPPoE, IPsec" +msgstr "Good: PPPoE, IPsec" + +#: ../../contributing/development.rst:582 +msgid "Good: RADIUS (as in remote authentication for dial-in user services)" +msgstr "Good: RADIUS (as in remote authentication for dial-in user services)" + +#: ../../contributing/build-vyos.rst:244 +msgid "Good luck!" +msgstr "Good luck!" + +#: ../../contributing/development.rst:535 +msgid "Guidelines" +msgstr "Guidelines" + +#: ../../contributing/development.rst:545 +msgid "Help String" +msgstr "Help String" + +#: ../../contributing/development.rst:51 +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 "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" + +#: ../../contributing/development.rst:575 +msgid "Horrible: \"Tcp connection timeout\"" +msgstr "Horrible: \"Tcp connection timeout\"" + +#: ../../contributing/development.rst:564 +msgid "Horrible: \"frobnication algorithm.\"" +msgstr "Horrible: \"frobnication algorithm.\"" + +#: ../../contributing/issues-features.rst:63 +msgid "How can we reproduce this Bug?" +msgstr "How can we reproduce this Bug?" + +#: ../../contributing/testing.rst:102 +msgid "IP and IPv6 options" +msgstr "IP and IPv6 options" + +#: ../../contributing/build-vyos.rst:308 +msgid "ISO Build Issues" +msgstr "ISO Build Issues" + +#: ../../contributing/debugging.rst:12 +msgid "ISO image build" +msgstr "ISO image build" + +#: ../../contributing/issues-features.rst:19 +msgid "I have found a bug, what should I do?" +msgstr "I have found a bug, what should I do?" + +#: ../../contributing/development.rst:607 +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 "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." + +#: ../../contributing/development.rst:94 +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 "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``" + +#: ../../contributing/development.rst:64 +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 "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." + +#: ../../contributing/build-vyos.rst:699 +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 "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." + +#: ../../contributing/build-vyos.rst:562 +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 "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." + +#: ../../contributing/development.rst:39 +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 "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)." + +#: ../../contributing/development.rst:267 +msgid "In addition this also helps when browsing the GitHub codebase on a mobile device if you happen to be a crazy scientist." +msgstr "In addition this also helps when browsing the GitHub codebase on a mobile device if you happen to be a crazy scientist." + +#: ../../contributing/issues-features.rst:56 +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 "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." + +#: ../../contributing/development.rst:153 +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 "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``." + +#: ../../contributing/debugging.rst:81 +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 "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``." + +#: ../../contributing/development.rst:80 +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 "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." + +#: ../../contributing/build-vyos.rst:554 +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 "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." + +#: ../../contributing/upstream-packages.rst:22 +msgid "In the future, we may switch to using systemd infrastructure instead. Building it doesn't require a special procedure." +msgstr "In the future, we may switch to using systemd infrastructure instead. Building it doesn't require a special procedure." + +#: ../../contributing/issues-features.rst:45 +msgid "Include output" +msgstr "Include output" + +#: ../../contributing/debugging.rst:106 +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 "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." + +#: ../../contributing/build-vyos.rst:810 +msgid "Install" +msgstr "Install" + +#: ../../contributing/upstream-packages.rst:53 +msgid "Install https://pypi.org/project/stdeb/" +msgstr "Install https://pypi.org/project/stdeb/" + +#: ../../contributing/build-vyos.rst:35 +msgid "Installing Docker_ and prerequisites:" +msgstr "Installing Docker_ and prerequisites:" + +#: ../../contributing/development.rst:506 +msgid "Instead of supplying all those XML nodes multiple times there are now include files with predefined features. Brief overview:" +msgstr "Instead of supplying all those XML nodes multiple times there are now include files with predefined features. Brief overview:" + +#: ../../contributing/build-vyos.rst:632 +msgid "Intel NIC" +msgstr "Intel NIC" + +#: ../../contributing/build-vyos.rst:404 +msgid "Intel NIC drivers" +msgstr "Intel NIC drivers" + +#: ../../contributing/build-vyos.rst:661 +msgid "Intel QAT" +msgstr "Intel QAT" + +#: ../../contributing/build-vyos.rst:405 +msgid "Inter QAT" +msgstr "Inter QAT" + +#: ../../contributing/testing.rst:90 +msgid "Interface based tests" +msgstr "Interface based tests" + +#: ../../contributing/issues-features.rst:5 +msgid "Issues/Feature requests" +msgstr "Issues/Feature requests" + +#: ../../contributing/issues-features.rst:12 +msgid "Issues or bugs are found in any software project. VyOS is not an exception." +msgstr "Issues or bugs are found in any software project. VyOS is not an exception." + +#: ../../contributing/upstream-packages.rst:85 +msgid "It's an Ada program and requires GNAT and gprbuild for building, dependencies are properly specified so just follow debuild's suggestions." +msgstr "It's an Ada program and requires GNAT and gprbuild for building, dependencies are properly specified so just follow debuild's suggestions." + +#: ../../contributing/debugging.rst:58 +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 "It is also possible to set up the debugging using environment variables. In that case, the name will be (in uppercase) VYOS_FEATURE_DEBUG." + +#: ../../contributing/testing.rst:17 +msgid "Jenkins CI" +msgstr "Jenkins CI" + +#: ../../contributing/build-vyos.rst:816 +msgid "Just install using the following commands:" +msgstr "Just install using the following commands:" + +#: ../../contributing/development.rst:46 +msgid "Keep track of the progress (what we've already done in this branch and what we still need to do)." +msgstr "Keep track of the progress (what we've already done in this branch and what we still need to do)." + +#: ../../contributing/upstream-packages.rst:28 +msgid "Keepalived normally isn't updated to newer feature releases between Debian versions, so we are building it from source." +msgstr "Keepalived normally isn't updated to newer feature releases between Debian versions, so we are building it from source." + +#: ../../contributing/debugging.rst:25 +msgid "Kernel" +msgstr "Kernel" + +#: ../../contributing/build-vyos.rst:787 +msgid "Launch Docker container and build package" +msgstr "Launch Docker container and build package" + +#: ../../contributing/development.rst:633 +msgid "Leaf nodes (nodes with values) use <leafNode> tag instead" +msgstr "Leaf nodes (nodes with values) use <leafNode> tag instead" + +#: ../../contributing/development.rst:240 +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 "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." + +#: ../../contributing/debugging.rst:101 +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 "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``" + +#: ../../contributing/development.rst:189 +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 "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.." + +#: ../../contributing/development.rst:109 +msgid "Limits:" +msgstr "Limits:" + +#: ../../contributing/build-vyos.rst:390 +msgid "Linux Kernel" +msgstr "Linux Kernel" + +#: ../../contributing/debugging.rst:42 +msgid "Live System" +msgstr "Live System" + +#: ../../contributing/testing.rst:101 +msgid "MTU size" +msgstr "MTU size" + +#: ../../contributing/development.rst:162 +msgid "Make your changes and save them. Do the following for all changes files to record them in your created Git commit:" +msgstr "Make your changes and save them. Do the following for all changes files to record them in your created Git commit:" + +#: ../../contributing/testing.rst:60 +msgid "Manual Smoketest Run" +msgstr "Manual Smoketest Run" + +#: ../../contributing/testing.rst:168 +msgid "Manual config load test" +msgstr "Manual config load test" + +#: ../../contributing/upstream-packages.rst:6 +msgid "Many base system packages are pulled straight from Debian's main and contrib repositories, but there are exceptions." +msgstr "Many base system packages are pulled straight from Debian's main and contrib repositories, but there are exceptions." + +#: ../../contributing/development.rst:622 +msgid "Migrating old CLI" +msgstr "Migrating old CLI" + +#: ../../contributing/development.rst:677 +msgid "Move default values to scripts" +msgstr "Move default values to scripts" + +#: ../../contributing/build-vyos.rst:147 +msgid "Native Build" +msgstr "Native Build" + +#: ../../contributing/development.rst:629 +msgid "New syntax" +msgstr "New syntax" + +#: ../../contributing/development.rst:230 +msgid "No code incompatible with Python3" +msgstr "No code incompatible with Python3" + +#: ../../contributing/development.rst:228 +msgid "No new features in Perl" +msgstr "No new features in Perl" + +#: ../../contributing/development.rst:229 +msgid "No old style command definitions" +msgstr "No old style command definitions" + +#: ../../contributing/upstream-packages.rst:68 +#: ../../contributing/upstream-packages.rst:76 +msgid "No special build procedure is required." +msgstr "No special build procedure is required." + +#: ../../contributing/development.rst:649 +#: ../../contributing/development.rst:656 +#: ../../contributing/development.rst:676 +#: ../../contributing/development.rst:679 +#: ../../contributing/development.rst:682 +msgid "None" +msgstr "None" + +#: ../../contributing/development.rst:630 +msgid "Notes" +msgstr "Notes" + +#: ../../contributing/build-vyos.rst:199 +msgid "Now a fresh build of the VyOS ISO can begin. Change directory to the ``vyos-build`` directory and run:" +msgstr "Now a fresh build of the VyOS ISO can begin. Change directory to the ``vyos-build`` directory and run:" + +#: ../../contributing/build-vyos.rst:184 +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 "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`." + +#: ../../contributing/build-vyos.rst:384 +msgid "Now it's time to fix the package mirror and rerun the last step until the package installation succeeds again!" +msgstr "Now it's time to fix the package mirror and rerun the last step until the package installation succeeds again!" + +#: ../../contributing/build-vyos.rst:469 +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 "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." + +#: ../../contributing/build-vyos.rst:133 +msgid "Now you are prepared with two new aliases ``vybld`` and ``vybld_crux`` to spawn your development containers in your current working directory." +msgstr "Now you are prepared with two new aliases ``vybld`` and ``vybld_crux`` to spawn your development containers in your current working directory." + +#: ../../contributing/development.rst:628 +msgid "Old concept/syntax" +msgstr "Old concept/syntax" + +#: ../../contributing/testing.rst:62 +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 "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." + +#: ../../contributing/build-vyos.rst:174 +msgid "Once you have the required dependencies installed, you may proceed with the steps described in :ref:`build_iso`." +msgstr "Once you have the required dependencies installed, you may proceed with the steps described in :ref:`build_iso`." + +#: ../../contributing/debugging.rst:112 +msgid "Once you run ``show xyz`` and your condition is triggered you should be dropped into the python debugger:" +msgstr "Once you run ``show xyz`` and your condition is triggered you should be dropped into the python debugger:" + +#: ../../contributing/testing.rst:170 +msgid "One is not bound to load all configurations one after another but can also load individual test configurations on his own." +msgstr "One is not bound to load all configurations one after another but can also load individual test configurations on his own." + +#: ../../contributing/testing.rst:7 +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 "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." + +#: ../../contributing/development.rst:665 +msgid "Only applicable to leaf nodes" +msgstr "Only applicable to leaf nodes" + +#: ../../contributing/build-vyos.rst:401 +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 "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." + +#: ../../contributing/upstream-packages.rst:39 +msgid "Our StrongSWAN build differs from the upstream:" +msgstr "Our StrongSWAN build differs from the upstream:" + +#: ../../contributing/testing.rst:19 +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 "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." + +#: ../../contributing/development.rst:10 +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 "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." + +#: ../../contributing/upstream-packages.rst:49 +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 "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:" + +#: ../../contributing/testing.rst:92 +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 "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." + +#: ../../contributing/build-vyos.rst:697 +#: ../../contributing/build-vyos.rst:766 +msgid "Packages" +msgstr "Packages" + +#: ../../contributing/development.rst:27 +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 "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." + +#: ../../contributing/upstream-packages.rst:42 +msgid "Patches for DMVPN are merged in" +msgstr "Patches for DMVPN are merged in" + +#: ../../contributing/development.rst:661 +msgid "Please leave a comment explaining why the priority was chosen (e.g. \"after interfaces are configured\")" +msgstr "Please leave a comment explaining why the priority was chosen (e.g. \"after interfaces are configured\")" + +#: ../../contributing/development.rst:115 +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 "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" + +#: ../../contributing/development.rst:254 +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 "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." + +#: ../../contributing/testing.rst:103 +msgid "Port description" +msgstr "Port description" + +#: ../../contributing/testing.rst:104 +msgid "Port disable" +msgstr "Port disable" + +#: ../../contributing/development.rst:612 +msgid "Prefer infinitives" +msgstr "Prefer infinitives" + +#: ../../contributing/development.rst:37 +msgid "Prepare patch/commit" +msgstr "Prepare patch/commit" + +#: ../../contributing/development.rst:49 +msgid "Prepare release notes for upcoming releases" +msgstr "Prepare release notes for upcoming releases" + +#: ../../contributing/build-vyos.rst:9 +msgid "Prerequisites" +msgstr "Prerequisites" + +#: ../../contributing/debugging.rst:188 +msgid "Priorities" +msgstr "Priorities" + +#: ../../contributing/issues-features.rst:61 +msgid "Provide as much information as you can" +msgstr "Provide as much information as you can" + +#: ../../contributing/development.rst:234 +msgid "Python" +msgstr "Python" + +#: ../../contributing/development.rst:202 +msgid "Python: Tabs **shall not** be used. Every indentation level should be 4 spaces" +msgstr "Python: Tabs **shall not** be used. Every indentation level should be 4 spaces" + +#: ../../contributing/development.rst:195 +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 "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." + +#: ../../contributing/development.rst:243 +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 "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." + +#: ../../contributing/build-vyos.rst:745 +msgid "QEMU" +msgstr "QEMU" + +#: ../../contributing/development.rst:556 +msgid "Rationale: this seems to be the unwritten standard in network device CLIs, and a good aesthetic compromise." +msgstr "Rationale: this seems to be the unwritten standard in network device CLIs, and a good aesthetic compromise." + +#: ../../contributing/debugging.rst:89 +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 "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." + +#: ../../contributing/issues-features.rst:54 +msgid "Report a Bug" +msgstr "Report a Bug" + +#: ../../contributing/build-vyos.rst:747 +msgid "Run the following command after building the ISO image." +msgstr "Run the following command after building the ISO image." + +#: ../../contributing/build-vyos.rst:756 +msgid "Run the following command after building the QEMU image." +msgstr "Run the following command after building the QEMU image." + +#: ../../contributing/build-vyos.rst:637 +#: ../../contributing/build-vyos.rst:666 +msgid "Simply use our wrapper script to build all of the driver modules." +msgstr "Simply use our wrapper script to build all of the driver modules." + +#: ../../contributing/build-vyos.rst:102 +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 "Since VyOS has switched to Debian (11) Bullseye in its ``current`` branch, you will require individual container for `current`, `equuleus` and `crux` builds." + +#: ../../contributing/testing.rst:29 +msgid "Smoketests" +msgstr "Smoketests" + +#: ../../contributing/testing.rst:31 +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 "Smoketests executes predefined VyOS CLI commands and checks if the desired daemon/service configuration is rendert - that is how to put it \"short\"." + +#: ../../contributing/testing.rst:44 +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 "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." + +#: ../../contributing/build-vyos.rst:136 +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 "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." + +#: ../../contributing/development.rst:586 +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 "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." + +#: ../../contributing/testing.rst:201 +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 "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." + +#: ../../contributing/debugging.rst:98 +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 "Sometimes it might be useful to debug Python code interactively on the live system rather than a IDE. This can be achieved using pdb." + +#: ../../contributing/build-vyos.rst:229 +msgid "Start the build:" +msgstr "Start the build:" + +#: ../../contributing/build-vyos.rst:17 +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 "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." + +#: ../../contributing/development.rst:25 +msgid "Submit a Patch" +msgstr "Submit a Patch" + +#: ../../contributing/development.rst:171 +msgid "Submit the patch ``git push`` and create the GitHub pull-request." +msgstr "Submit the patch ``git push`` and create the GitHub pull-request." + +#: ../../contributing/development.rst:223 +msgid "Summary" +msgstr "Summary" + +#: ../../contributing/development.rst:122 +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 "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." + +#: ../../contributing/debugging.rst:18 +msgid "System Startup" +msgstr "System Startup" + +#: ../../contributing/development.rst:214 +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 "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." + +#: ../../contributing/testing.rst:5 +msgid "Testing" +msgstr "Testing" + +#: ../../contributing/development.rst:212 +msgid "Text generation" +msgstr "Text generation" + +#: ../../contributing/development.rst:688 +msgid "The CLI parser used in VyOS is a mix of bash, bash-completion helper and the C++ backend library [vyatta-cfg](https://github.com/vyos/vyatta-cfg). This section is a reference of common CLI commands and the respective entry point in the C/C++ code." +msgstr "The CLI parser used in VyOS is a mix of bash, bash-completion helper and the C++ backend library [vyatta-cfg](https://github.com/vyos/vyatta-cfg). This section is a reference of common CLI commands and the respective entry point in the C/C++ code." + +#: ../../contributing/build-vyos.rst:634 +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 "The Intel NIC drivers do not come from a Git repository, instead we just fetch the tarballs from our mirror and compile them." + +#: ../../contributing/build-vyos.rst:662 +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 "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." + +#: ../../contributing/build-vyos.rst:392 +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 "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:" + +#: ../../contributing/development.rst:22 +msgid "The README.md file will guide you to use the this top level repository." +msgstr "The README.md file will guide you to use the this top level repository." + +#: ../../contributing/development.rst:370 +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 "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." + +#: ../../contributing/development.rst:351 +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 "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." + +#: ../../contributing/development.rst:349 +msgid "The ``generate()`` function generates config files for system components." +msgstr "The ``generate()`` function generates config files for system components." + +#: ../../contributing/development.rst:328 +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 "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." + +#: ../../contributing/testing.rst:47 +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 "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." + +#: ../../contributing/development.rst:340 +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 "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." + +#: ../../contributing/development.rst:392 +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 "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." + +#: ../../contributing/build-vyos.rst:54 +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 "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\"" + +#: ../../contributing/testing.rst:158 +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 "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" + +#: ../../contributing/build-vyos.rst:87 +msgid "The container can also be built directly from source:" +msgstr "The container can also be built directly from source:" + +#: ../../contributing/build-vyos.rst:62 +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 "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)." + +#: ../../contributing/development.rst:219 +msgid "The default template processor for VyOS code is Jinja2_." +msgstr "The default template processor for VyOS code is Jinja2_." + +#: ../../contributing/build-vyos.rst:773 +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 "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." + +#: ../../contributing/testing.rst:163 +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 "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." + +#: ../../contributing/debugging.rst:52 +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 "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." + +#: ../../contributing/development.rst:553 +msgid "The first word of every help string **must** be capitalized. There **must not** be a period at the end of help strings." +msgstr "The first word of every help string **must** be capitalized. There **must not** be a period at the end of help strings." + +#: ../../contributing/development.rst:71 +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 "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/" + +#: ../../contributing/development.rst:404 +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 "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." + +#: ../../contributing/development.rst:44 +msgid "The information is used in three ways:" +msgstr "The information is used in three ways:" + +#: ../../contributing/build-vyos.rst:437 +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 "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." + +#: ../../contributing/build-vyos.rst:425 +msgid "The most obvious reasons could be:" +msgstr "The most obvious reasons could be:" + +#: ../../contributing/upstream-packages.rst:83 +msgid "The original repo is at https://github.com/dmbaturin/hvinfo" +msgstr "The original repo is at https://github.com/dmbaturin/hvinfo" + +#: ../../contributing/testing.rst:153 +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 "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." + +#: ../../contributing/issues-features.rst:47 +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 "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." + +#: ../../contributing/upstream-packages.rst:60 +msgid "The package ends up in deb_dist dir." +msgstr "The package ends up in deb_dist dir." + +#: ../../contributing/debugging.rst:148 +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 "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:" + +#: ../../contributing/development.rst:19 +msgid "The repository that contains all the ISO build scripts is: https://github.com/vyos/vyos-build" +msgstr "The repository that contains all the ISO build scripts is: https://github.com/vyos/vyos-build" + +#: ../../contributing/testing.rst:53 +msgid "The script only searches for executable \"test-cases\" under ``/usr/libexec/vyos/tests/smoke/cli/`` and executes them one by one." +msgstr "The script only searches for executable \"test-cases\" under ``/usr/libexec/vyos/tests/smoke/cli/`` and executes them one by one." + +#: ../../contributing/build-vyos.rst:23 +msgid "The source code remains public and an ISO can be built using the process outlined in this chapter." +msgstr "The source code remains public and an ISO can be built using the process outlined in this chapter." + +#: ../../contributing/upstream-packages.rst:44 +msgid "The source is at https://github.com/vyos/vyos-strongswan" +msgstr "The source is at https://github.com/vyos/vyos-strongswan" + +#: ../../contributing/upstream-packages.rst:20 +msgid "The source is located at https://github.com/vyos/vyos-netplug" +msgstr "The source is located at https://github.com/vyos/vyos-netplug" + +#: ../../contributing/development.rst:236 +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 "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." + +#: ../../contributing/debugging.rst:20 +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 "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." + +#: ../../contributing/build-vyos.rst:310 +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 "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:" + +#: ../../contributing/build-vyos.rst:11 +msgid "There are different ways you can build VyOS." +msgstr "There are different ways you can build VyOS." + +#: ../../contributing/development.rst:205 +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 "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." + +#: ../../contributing/debugging.rst:7 +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 "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." + +#: ../../contributing/build-vyos.rst:257 +msgid "This ISO can be customized with the following list of configure options. The full and current list can be generated with ``./build-vyos-image --help``:" +msgstr "This ISO can be customized with the following list of configure options. The full and current list can be generated with ``./build-vyos-image --help``:" + +#: ../../contributing/debugging.rst:185 +msgid "This can also be done permanently by changing ``/boot/grub/grub.cfg``." +msgstr "This can also be done permanently by changing ``/boot/grub/grub.cfg``." + +#: ../../contributing/upstream-packages.rst:9 +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 "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." + +#: ../../contributing/debugging.rst:177 +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 "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_" + +#: ../../contributing/development.rst:132 +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 "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" + +#: ../../contributing/upstream-packages.rst:65 +msgid "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/mdns-repeater" +msgstr "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/mdns-repeater" + +#: ../../contributing/upstream-packages.rst:73 +msgid "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/udp-broadcast-relay" +msgstr "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/udp-broadcast-relay" + +#: ../../contributing/build-vyos.rst:572 +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 "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``:" + +#: ../../contributing/build-vyos.rst:26 +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 "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." + +#: ../../contributing/testing.rst:147 +msgid "This will limit the `bond` interface test to only make use of `eth1` and `eth2` as member ports." +msgstr "This will limit the `bond` interface test to only make use of `eth1` and `eth2` as member ports." + +#: ../../contributing/testing.rst:97 +msgid "Those common tests consists out of:" +msgstr "Those common tests consists out of:" + +#: ../../contributing/build-vyos.rst:107 +msgid "Tips and Tricks" +msgstr "Tips and Tricks" + +#: ../../contributing/build-vyos.rst:46 +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 "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``." + +#: ../../contributing/build-vyos.rst:149 +msgid "To build VyOS natively you require a properly configured build host with the following Debian versions installed:" +msgstr "To build VyOS natively you require a properly configured build host with the following Debian versions installed:" + +#: ../../contributing/development.rst:711 +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 "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_." + +#: ../../contributing/debugging.rst:196 +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 "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." + +#: ../../contributing/build-vyos.rst:333 +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 "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:" + +#: ../../contributing/debugging.rst:182 +msgid "To enable boot time graphing change the Kernel commandline and add the folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" +msgstr "To enable boot time graphing change the Kernel commandline and add the folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" + +#: ../../contributing/debugging.rst:93 +msgid "To enable debugging just run: ``$ touch /tmp/vyos.frr.debug``" +msgstr "To enable debugging just run: ``$ touch /tmp/vyos.frr.debug``" + +#: ../../contributing/development.rst:547 +msgid "To ensure uniform look and feel, and improve readability, we should follow a set of guidelines consistently." +msgstr "To ensure uniform look and feel, and improve readability, we should follow a set of guidelines consistently." + +#: ../../contributing/development.rst:55 +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 "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:" + +#: ../../contributing/build-vyos.rst:75 +msgid "To manually download the container from DockerHub, run:" +msgstr "To manually download the container from DockerHub, run:" + +#: ../../contributing/build-vyos.rst:156 +msgid "To start, clone the repository to your local machine:" +msgstr "To start, clone the repository to your local machine:" + +#: ../../contributing/build-vyos.rst:812 +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 "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." + +#: ../../contributing/build-vyos.rst:711 +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#: ../../contributing/development.rst:362 +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 "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." + +#: ../../contributing/upstream-packages.rst:4 +msgid "Upstream packages" +msgstr "Upstream packages" + +#: ../../contributing/development.rst:567 +msgid "Use of abbreviations and acronyms" +msgstr "Use of abbreviations and acronyms" + +#: ../../contributing/development.rst:538 +msgid "Use of numbers" +msgstr "Use of numbers" + +#: ../../contributing/development.rst:540 +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 "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." + +#: ../../contributing/development.rst:598 +msgid "Use of verbs" +msgstr "Use of verbs" + +#: ../../contributing/development.rst:650 +msgid "Use regex" +msgstr "Use regex" + +#: ../../contributing/debugging.rst:125 +msgid "Useful commands are:" +msgstr "Useful commands are:" + +#: ../../contributing/development.rst:501 +msgid "VIF (incl. VIF-S/VIF-C)" +msgstr "VIF (incl. VIF-S/VIF-C)" + +#: ../../contributing/testing.rst:105 +msgid "VLANs (QinQ and regular 802.1q)" +msgstr "VLANs (QinQ and regular 802.1q)" + +#: ../../contributing/build-vyos.rst:754 +msgid "VMware" +msgstr "VMware" + +#: ../../contributing/development.rst:614 +msgid "Verbs, when they are necessary, **should** be in their infinitive form." +msgstr "Verbs, when they are necessary, **should** be in their infinitive form." + +#: ../../contributing/development.rst:600 +msgid "Verbs **should** be avoided. If a verb can be omitted, omit it." +msgstr "Verbs **should** be avoided. If a verb can be omitted, omit it." + +#: ../../contributing/build-vyos.rst:742 +msgid "Virtualization Platforms" +msgstr "Virtualization Platforms" + +#: ../../contributing/debugging.rst:190 +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 "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." + +#: ../../contributing/build-vyos.rst:768 +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 "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." + +#: ../../contributing/development.rst:707 +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 "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." + +#: ../../contributing/build-vyos.rst:600 +msgid "We again make use of a helper script and some patches to make the build work. Just run the following command:" +msgstr "We again make use of a helper script and some patches to make the build work. Just run the following command:" + +#: ../../contributing/testing.rst:24 +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 "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." + +#: ../../contributing/build-vyos.rst:349 +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 "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." + +#: ../../contributing/build-vyos.rst:341 +msgid "We now need to mount some required, volatile filesystems" +msgstr "We now need to mount some required, volatile filesystems" + +#: ../../contributing/development.rst:111 +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 "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." + +#: ../../contributing/development.rst:87 +msgid "What/why/how something has been changed, makes everyone's life easier when working with `git bisect`" +msgstr "What/why/how something has been changed, makes everyone's life easier when working with `git bisect`" + +#: ../../contributing/issues-features.rst:42 +msgid "What commands did you use? Use e.g. ``run show configuration commands``" +msgstr "What commands did you use? Use e.g. ``run show configuration commands``" + +#: ../../contributing/issues-features.rst:41 +msgid "What was the configuration prior to the change?" +msgstr "What was the configuration prior to the change?" + +#: ../../contributing/issues-features.rst:40 +msgid "What were you attempting to achieve?" +msgstr "What were you attempting to achieve?" + +#: ../../contributing/testing.rst:34 +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 "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:" + +#: ../../contributing/debugging.rst:14 +msgid "When having trouble compiling your own ISO image or debugging Jenkins issues you can follow the steps at :ref:`iso_build_issues`." +msgstr "When having trouble compiling your own ISO image or debugging Jenkins issues you can follow the steps at :ref:`iso_build_issues`." + +#: ../../contributing/development.rst:225 +msgid "When modifying the source code, remember these rules of the legacy elimination campaign:" +msgstr "When modifying the source code, remember these rules of the legacy elimination campaign:" + +#: ../../contributing/build-vyos.rst:241 +msgid "When the build is successful, the resulting iso can be found inside the ``build`` directory as ``live-image-[architecture].hybrid.iso``." +msgstr "When the build is successful, the resulting iso can be found inside the ``build`` directory as ``live-image-[architecture].hybrid.iso``." + +#: ../../contributing/debugging.rst:134 +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 "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:" + +#: ../../contributing/issues-features.rst:31 +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 "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." + +#: ../../contributing/testing.rst:108 +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 "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." + +#: ../../contributing/issues-features.rst:21 +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 "When you believe you have found a bug, it is always a good idea to verify the issue prior to opening a bug request." + +#: ../../contributing/issues-features.rst:34 +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 "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." + +#: ../../contributing/issues-features.rst:62 +msgid "Which version of VyOS are you using? ``run show version``" +msgstr "Which version of VyOS are you using? ``run show version``" + +#: ../../contributing/build-vyos.rst:406 +#: ../../contributing/build-vyos.rst:595 +msgid "WireGuard" +msgstr "WireGuard" + +#: ../../contributing/development.rst:69 +msgid "Writing good commit messages" +msgstr "Writing good commit messages" + +#: ../../contributing/development.rst:203 +msgid "XML: Tabs **shall not** be used. Every indentation level should be 2 spaces" +msgstr "XML: Tabs **shall not** be used. Every indentation level should be 2 spaces" + +#: ../../contributing/development.rst:390 +msgid "XML (used for CLI definitions)" +msgstr "XML (used for CLI definitions)" + +#: ../../contributing/development.rst:497 +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 "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:" + +#: ../../contributing/development.rst:399 +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 "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." + +#: ../../contributing/build-vyos.rst:827 +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 "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." + +#: ../../contributing/build-vyos.rst:109 +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 "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:" + +#: ../../contributing/debugging.rst:122 +msgid "You can type ``help`` to get an overview of the available commands, and ``help command`` to get more information on each command." +msgstr "You can type ``help`` to get an overview of the available commands, and ``help command`` to get more information on each command." + +#: ../../contributing/issues-features.rst:70 +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 "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." + +#: ../../contributing/build-vyos.rst:430 +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, Intel QAT or Intel NIC drivers" +msgstr "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, Intel QAT or Intel NIC drivers" + +#: ../../contributing/build-vyos.rst:434 +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 "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" + +#: ../../contributing/debugging.rst:166 +msgid "You shoudl now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." +msgstr "You shoudl now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." + +#: ../../contributing/development.rst:146 +msgid "You then can proceed with cloning your fork or add a new remote to your local repository:" +msgstr "You then can proceed with cloning your fork or add a new remote to your local repository:" + +#: ../../contributing/development.rst:262 +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 "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." + +#: ../../contributing/testing.rst:106 +msgid "..." +msgstr "..." + +#: ../../contributing/development.rst:509 +msgid "`IPv4, IPv6 and DHCP(v6)`_ address assignment" +msgstr "`IPv4, IPv6 and DHCP(v6)`_ address assignment" + +#: ../../contributing/development.rst:510 +msgid "`IPv4, IPv6`_ address assignment" +msgstr "`IPv4, IPv6`_ address assignment" + +#: ../../contributing/development.rst:512 +msgid "`MAC address`_ assignment" +msgstr "`MAC address`_ assignment" + +#: ../../contributing/development.rst:511 +msgid "`VLAN (VIF)`_ definition" +msgstr "`VLAN (VIF)`_ definition" + +#: ../../contributing/upstream-packages.rst:55 +msgid "`./configure --enable-python-eggs`" +msgstr "`./configure --enable-python-eggs`" + +#: ../../contributing/development.rst:62 +msgid "``Jenkins: add current Git commit ID to build description``" +msgstr "``Jenkins: add current Git commit ID to build description``" + +#: ../../contributing/debugging.rst:67 +msgid "``command`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." +msgstr "``command`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." + +#: ../../contributing/development.rst:699 +msgid "``commit``" +msgstr "``commit``" + +#: ../../contributing/development.rst:61 +msgid "``ddclient: T1030: auto create runtime directories``" +msgstr "``ddclient: T1030: auto create runtime directories``" + +#: ../../contributing/debugging.rst:70 +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 "``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." + +#: ../../contributing/debugging.rst:64 +msgid "``ifconfig`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." +msgstr "``ifconfig`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." + +#: ../../contributing/debugging.rst:77 +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 "``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." + +#: ../../contributing/development.rst:693 +msgid "``set``" +msgstr "``set``" + +#: ../../contributing/build-vyos.rst:427 +msgid "``vyos-build`` repo is outdated, please ``git pull`` to update to the latest release kernel version from us." +msgstr "``vyos-build`` repo is outdated, please ``git pull`` to update to the latest release kernel version from us." + +#: ../../contributing/debugging.rst:33 +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 "``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." + +#: ../../contributing/debugging.rst:27 +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 "``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``." + +#: ../../contributing/upstream-packages.rst:56 +msgid "`cd src/libcharon/plugins/vici/python`" +msgstr "`cd src/libcharon/plugins/vici/python`" + +#: ../../contributing/upstream-packages.rst:54 +msgid "`cd vyos-strongswan`" +msgstr "`cd vyos-strongswan`" + +#: ../../contributing/upstream-packages.rst:57 +msgid "`make`" +msgstr "`make`" + +#: ../../contributing/upstream-packages.rst:58 +msgid "`python3 setup.py --command-packages=stdeb.command bdist_deb`" +msgstr "`python3 setup.py --command-packages=stdeb.command bdist_deb`" + +#: ../../contributing/development.rst:672 +msgid "allowed: /path/to/script" +msgstr "allowed: /path/to/script" + +#: ../../contributing/development.rst:669 +msgid "allowed: cli-shell-api listNodes vpn ipsec esp-group" +msgstr "allowed: cli-shell-api listNodes vpn ipsec esp-group" + +#: ../../contributing/development.rst:666 +msgid "allowed: echo foo bar" +msgstr "allowed: echo foo bar" + +#: ../../contributing/development.rst:681 +msgid "begin:/create:/delete:" +msgstr "begin:/create:/delete:" + +#: ../../contributing/development.rst:678 +msgid "commit:expression:" +msgstr "commit:expression:" + +#: ../../contributing/debugging.rst:128 +msgid "contine execution using ``cont``" +msgstr "contine execution using ``cont``" + +#: ../../contributing/development.rst:675 +msgid "default:" +msgstr "default:" + +#: ../../contributing/debugging.rst:127 +msgid "examine variables using ``pp(var)``" +msgstr "examine variables using ``pp(var)``" + +#: ../../contributing/debugging.rst:129 +msgid "get a backtrace using ``bt``" +msgstr "get a backtrace using ``bt``" + +#: ../../contributing/development.rst:637 +msgid "help: My node" +msgstr "help: My node" + +#: ../../contributing/development.rst:701 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/commit/commit-algorithm.cpp#L1252" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/commit/commit-algorithm.cpp#L1252" + +#: ../../contributing/development.rst:696 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L2549" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L2549" + +#: ../../contributing/development.rst:695 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L352" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L352" + +#: ../../contributing/upstream-packages.rst:79 +msgid "hvinfo" +msgstr "hvinfo" + +#: ../../contributing/upstream-packages.rst:26 +msgid "keepalived" +msgstr "keepalived" + +#: ../../contributing/upstream-packages.rst:63 +msgid "mdns-repeater" +msgstr "mdns-repeater" + +#: ../../contributing/development.rst:663 +msgid "multi:" +msgstr "multi:" + +#: ../../contributing/development.rst:631 +msgid "mynode/node.def" +msgstr "mynode/node.def" + +#: ../../contributing/development.rst:634 +msgid "mynode/node.tag , tag:" +msgstr "mynode/node.tag , tag:" + +#: ../../contributing/development.rst:659 +msgid "priority: 999" +msgstr "priority: 999" + +#: ../../contributing/upstream-packages.rst:37 +msgid "strongswan" +msgstr "strongswan" + +#: ../../contributing/upstream-packages.rst:41 +msgid "strongswan-nm package build is disabled since we don't use NetworkManager" +msgstr "strongswan-nm package build is disabled since we don't use NetworkManager" + +#: ../../contributing/development.rst:648 +msgid "syntax:expression: $VAR(@) in \"foo\", \"bar\", \"baz\"" +msgstr "syntax:expression: $VAR(@) in \"foo\", \"bar\", \"baz\"" + +#: ../../contributing/development.rst:655 +msgid "syntax:expression: (arithmetic expression)" +msgstr "syntax:expression: (arithmetic expression)" + +#: ../../contributing/development.rst:651 +msgid "syntax:expression: exec ..." +msgstr "syntax:expression: exec ..." + +#: ../../contributing/development.rst:645 +msgid "syntax:expression: pattern" +msgstr "syntax:expression: pattern" + +#: ../../contributing/upstream-packages.rst:71 +msgid "udp-broadcast-relay" +msgstr "udp-broadcast-relay" + +#: ../../contributing/development.rst:640 +msgid "val_help: <format>; some string" +msgstr "val_help: <format>; some string" + +#: ../../contributing/upstream-packages.rst:15 +msgid "vyos-netplug" +msgstr "vyos-netplug" diff --git a/docs/_locale/ja/copyright.pot b/docs/_locale/ja/copyright.pot new file mode 100644 index 00000000..53078f45 --- /dev/null +++ b/docs/_locale/ja/copyright.pot @@ -0,0 +1,29 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../copyright.md:1 +msgid "Copyright Notice" +msgstr "Copyright Notice" + +#: ../../copyright.md:3 +msgid "Copyright (C) 2018-2023 VyOS maintainers and contributors" +msgstr "Copyright (C) 2018-2023 VyOS maintainers and contributors" + +#: ../../copyright.md:9 +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 "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." + +#: ../../copyright.md:14 +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 "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." + +#: ../../copyright.md:5 +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 "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." diff --git a/docs/_locale/ja/documentation.pot b/docs/_locale/ja/documentation.pot new file mode 100644 index 00000000..6b2b8401 --- /dev/null +++ b/docs/_locale/ja/documentation.pot @@ -0,0 +1,417 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../documentation.rst:239 +msgid "16bit ASN: ``64496 - 64511``" +msgstr "16bit ASN: ``64496 - 64511``" + +#: ../../documentation.rst:240 +msgid "32bit ASN: ``65536 - 65551``" +msgstr "32bit ASN: ``65536 - 65551``" + +#: ../../documentation.rst:182 +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 "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." + +#: ../../documentation.rst:103 +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 "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." + +#: ../../documentation.rst:229 +msgid "Address space" +msgstr "Address space" + +#: ../../documentation.rst:390 +msgid "All RST files must follow the same TOC Level syntax and have to start with" +msgstr "All RST files must follow the same TOC Level syntax and have to start with" + +#: ../../documentation.rst:413 +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 "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." + +#: ../../documentation.rst:53 +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 "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." + +#: ../../documentation.rst:436 +msgid "Anything else" +msgstr "Anything else" + +#: ../../documentation.rst:438 +msgid "Anything else that is not a configuration or an operation command has no predefined structure." +msgstr "Anything else that is not a configuration or an operation command has no predefined structure." + +#: ../../documentation.rst:257 +msgid "Autolinter" +msgstr "Autolinter" + +#: ../../documentation.rst:94 +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 "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." + +#: ../../documentation.rst:123 +msgid "Check your configured remote repositories:" +msgstr "Check your configured remote repositories:" + +#: ../../documentation.rst:78 +msgid "Clone fork to local machine, then change to that directory ``$ cd vyos-documentation``" +msgstr "Clone fork to local machine, then change to that directory ``$ cd vyos-documentation``" + +#: ../../documentation.rst:107 +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 "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`)." + +#: ../../documentation.rst:399 +msgid "Configuration mode pages" +msgstr "Configuration mode pages" + +#: ../../documentation.rst:84 +msgid "Create a new branch for your work, use a descriptive name of your work: ``$ git checkout -b <branch-name>``" +msgstr "Create a new branch for your work, use a descriptive name of your work: ``$ git checkout -b <branch-name>``" + +#: ../../documentation.rst:180 +msgid "Cross-References" +msgstr "Cross-References" + +#: ../../documentation.rst:268 +msgid "Custom Sphinx-doc Markup" +msgstr "Custom Sphinx-doc Markup" + +#: ../../documentation.rst:270 +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 "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." + +#: ../../documentation.rst:45 +msgid "Don't forget to update ``index.rst`` when adding a new node." +msgstr "Don't forget to update ``index.rst`` when adding a new node." + +#: ../../documentation.rst:259 +msgid "Each GitHub pull request is automatically linted to check the address space and line length." +msgstr "Each GitHub pull request is automatically linted to check the address space and line length." + +#: ../../documentation.rst:252 +msgid "Except in ``.. code-block::`` because it uses the html tag ``<pre>`` and renders the same line format from the source rst file." +msgstr "Except in ``.. code-block::`` because it uses the html tag ``<pre>`` and renders the same line format from the source rst file." + +#: ../../documentation.rst:292 +msgid "For an inline configuration level command, use ``:cfgcmd:``" +msgstr "For an inline configuration level command, use ``:cfgcmd:``" + +#: ../../documentation.rst:328 +msgid "For an inline operational level command, use ``:opcmd:``" +msgstr "For an inline operational level command, use ``:opcmd:``" + +#: ../../documentation.rst:186 +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 "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." + +#: ../../documentation.rst:405 +msgid "For example:" +msgstr "For example:" + +#: ../../documentation.rst:76 +msgid "Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork" +msgstr "Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork" + +#: ../../documentation.rst:58 +msgid "Forking Workflow" +msgstr "Forking Workflow" + +#: ../../documentation.rst:150 +msgid "Formating and Sphinxmarkup" +msgstr "Formating and Sphinxmarkup" + +#: ../../documentation.rst:432 +msgid "General concepts for troubleshooting and detailed process descriptions belong here." +msgstr "General concepts for troubleshooting and detailed process descriptions belong here." + +#: ../../documentation.rst:33 +msgid "Guidelines" +msgstr "Guidelines" + +#: ../../documentation.rst:423 +msgid "If there some troubleshooting guides related to the commands. Explain it in the next optional part." +msgstr "If there some troubleshooting guides related to the commands. Explain it in the next optional part." + +#: ../../documentation.rst:143 +msgid "If you also want to update your fork on GitHub, use the following: ``$ git push origin master``" +msgstr "If you also want to update your fork on GitHub, use the following: ``$ git push origin master``" + +#: ../../documentation.rst:13 +msgid "If you are willing to contribute to our documentation this is the definite guide how to do so." +msgstr "If you are willing to contribute to our documentation this is the definite guide how to do so." + +#: ../../documentation.rst:16 +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 "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." + +#: ../../documentation.rst:417 +msgid "In the configuration part of the page, all possible configuration options should be documented. Use ``.. cfgcmd::`` described above." +msgstr "In the configuration part of the page, all possible configuration options should be documented. Use ``.. cfgcmd::`` described above." + +#: ../../documentation.rst:50 +msgid "Indent with two spaces." +msgstr "Indent with two spaces." + +#: ../../documentation.rst:81 +msgid "Install the requirements ``$ pip install -r requirements.txt`` (or something similar)" +msgstr "Install the requirements ``$ pip install -r requirements.txt`` (or something similar)" + +#: ../../documentation.rst:49 +msgid "Leave a newline before and after a header." +msgstr "Leave a newline before and after a header." + +#: ../../documentation.rst:250 +msgid "Limit all lines to a maximum of 80 characters." +msgstr "Limit all lines to a maximum of 80 characters." + +#: ../../documentation.rst:248 +msgid "Line length" +msgstr "Line length" + +#: ../../documentation.rst:87 +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 "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_." + +#: ../../documentation.rst:242 +msgid "Multicast MAC-Addresses: ``90-10-00`` to ``90-10-FF``" +msgstr "Multicast MAC-Addresses: ``90-10-00`` to ``90-10-FF``" + +#: ../../documentation.rst:231 +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 "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:" + +#: ../../documentation.rst:118 +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 "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``" + +#: ../../documentation.rst:429 +msgid "Operation mode commands that do not fit in a related configuration mode command must be documented in this part of the documentation." +msgstr "Operation mode commands that do not fit in a related configuration mode command must be documented in this part of the documentation." + +#: ../../documentation.rst:427 +msgid "Operation mode pages" +msgstr "Operation mode pages" + +#: ../../documentation.rst:385 +msgid "Page content" +msgstr "Page content" + +#: ../../documentation.rst:244 +msgid "Please do not use other public address space." +msgstr "Please do not use other public address space." + +#: ../../documentation.rst:47 +msgid "Properly quote commands, filenames and brief code snippets with double backticks." +msgstr "Properly quote commands, filenames and brief code snippets with double backticks." + +#: ../../documentation.rst:112 +msgid "Push commits to your GitHub project: ``$ git push -u origin <branch-name>``" +msgstr "Push commits to your GitHub project: ``$ git push -u origin <branch-name>``" + +#: ../../documentation.rst:420 +msgid "Related operation command must be documented in the next part of the article. Use ``::opcmd..`` for these commands." +msgstr "Related operation command must be documented in the next part of the article. Use ``::opcmd..`` for these commands." + +#: ../../documentation.rst:262 +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 "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." + +#: ../../documentation.rst:147 +msgid "Style Guide" +msgstr "Style Guide" + +#: ../../documentation.rst:114 +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 "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." + +#: ../../documentation.rst:153 +msgid "TOC Level" +msgstr "TOC Level" + +#: ../../documentation.rst:38 +msgid "Take a look at the :doc:`/documentation` page for an intricate explanation of the documentation process." +msgstr "Take a look at the :doc:`/documentation` page for an intricate explanation of the documentation process." + +#: ../../documentation.rst:60 +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 "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." + +#: ../../documentation.rst:410 +msgid "The article starts with a short introduction about the command or the technology. Please include some helpful links or background information." +msgstr "The article starts with a short introduction about the command or the technology. Please include some helpful links or background information." + +#: ../../documentation.rst:401 +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 "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." + +#: ../../documentation.rst:387 +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 "The documentation has 3 different types of pages. The same kind of pages must have the same structure to achieve a recognition factor." + +#: ../../documentation.rst:25 +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 "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." + +#: ../../documentation.rst:41 +msgid "The following is a quick summary of the rules:" +msgstr "The following is a quick summary of the rules:" + +#: ../../documentation.rst:66 +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 "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." + +#: ../../documentation.rst:199 +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 "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." + +#: ../../documentation.rst:35 +msgid "There are a few things to keep in mind when contributing to the documentation, for the sake of consistency and readability." +msgstr "There are a few things to keep in mind when contributing to the documentation, for the sake of consistency and readability." + +#: ../../documentation.rst:299 +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 "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." + +#: ../../documentation.rst:337 +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 "To minimize redundancy, there is a special include directive. It includes a txt file and replace the ``{{ var0 }}`` - ``{{ var9 }}`` with the correct value." + +#: ../../documentation.rst:46 +msgid "Try not to exceed 80 characters per line, but don't break URLs over this." +msgstr "Try not to exceed 80 characters per line, but don't break URLs over this." + +#: ../../documentation.rst:241 +msgid "Unicast MAC Addresses: ``00-53-00`` to ``00-53-FF``" +msgstr "Unicast MAC Addresses: ``00-53-00`` to ``00-53-FF``" + +#: ../../documentation.rst:73 +msgid "Updates to our documentation should be delivered by a GitHub pull-request. This requires you already have a GitHub account." +msgstr "Updates to our documentation should be delivered by a GitHub pull-request. This requires you already have a GitHub account." + +#: ../../documentation.rst:43 +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 "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`_." + +#: ../../documentation.rst:48 +msgid "Use literal blocks for longer snippets." +msgstr "Use literal blocks for longer snippets." + +#: ../../documentation.rst:99 +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 "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." + +#: ../../documentation.rst:20 +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 "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." + +#: ../../documentation.rst:9 +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 "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." + +#: ../../documentation.rst:155 +msgid "We use the following syntax for Headlines." +msgstr "We use the following syntax for Headlines." + +#: ../../documentation.rst:277 +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 "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." + +#: ../../documentation.rst:316 +msgid "When documenting operational level commands, use the ``.. opcmd::`` directive. An explanation of the described command should be added below this statement." +msgstr "When documenting operational level commands, use the ``.. opcmd::`` directive. An explanation of the described command should be added below this statement." + +#: ../../documentation.rst:51 +msgid "When in doubt, follow the style of existing documentation." +msgstr "When in doubt, follow the style of existing documentation." + +#: ../../documentation.rst:375 +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 "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." + +#: ../../documentation.rst:319 +msgid "With those custom commands, it is possible to render them in a more descriptive way in the resulting HTML/PDF manual." +msgstr "With those custom commands, it is possible to render them in a more descriptive way in the resulting HTML/PDF manual." + +#: ../../documentation.rst:282 +msgid "With those custom commands, it will be possible to render them in a more descriptive way in the resulting HTML/PDF manual." +msgstr "With those custom commands, it will be possible to render them in a more descriptive way in the resulting HTML/PDF manual." + +#: ../../documentation.rst:7 +msgid "Write Documentation" +msgstr "Write Documentation" + +#: ../../documentation.rst:29 +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 "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." + +#: ../../documentation.rst:133 +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 "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." + +#: ../../documentation.rst:235 +msgid "``192.0.2.0/24``" +msgstr "``192.0.2.0/24``" + +#: ../../documentation.rst:236 +msgid "``198.51.100.0/24``" +msgstr "``198.51.100.0/24``" + +#: ../../documentation.rst:238 +msgid "``2001:db8::/32``" +msgstr "``2001:db8::/32``" + +#: ../../documentation.rst:237 +msgid "``203.0.113.0/24``" +msgstr "``203.0.113.0/24``" + +#: ../../documentation.rst:194 +msgid "``:ref:`Check out VLAN<configuration/interfaces/ethernet:vlan>``" +msgstr "``:ref:`Check out VLAN<configuration/interfaces/ethernet:vlan>``" + +#: ../../documentation.rst:190 +msgid "``:ref:`configuration/interfaces/ethernet:vlan``" +msgstr "``:ref:`configuration/interfaces/ethernet:vlan``" + +#: ../../documentation.rst:407 +msgid "``set firewall zone`` is written in ``firewall/zone.rst``" +msgstr "``set firewall zone`` is written in ``firewall/zone.rst``" + +#: ../../documentation.rst:408 +msgid "``set interfaces ethernet`` is written in ``interfaces/ethernet.rst``" +msgstr "``set interfaces ethernet`` is written in ``interfaces/ethernet.rst``" + +#: ../../documentation.rst:275 +msgid "cfgcmd" +msgstr "cfgcmd" + +#: ../../documentation.rst:335 +msgid "cmdinclude" +msgstr "cmdinclude" + +#: ../../documentation.rst:197 +msgid "handle build errors" +msgstr "handle build errors" + +#: ../../documentation.rst:314 +msgid "opcmd" +msgstr "opcmd" + +#: ../../documentation.rst:346 +msgid "the content of interface-address.txt looks like this" +msgstr "the content of interface-address.txt looks like this" + +#: ../../documentation.rst:192 +msgid "to use an alternative hyperlink use it this way:" +msgstr "to use an alternative hyperlink use it this way:" + +#: ../../documentation.rst:373 +msgid "vytask" +msgstr "vytask" diff --git a/docs/_locale/ja/index.pot b/docs/_locale/ja/index.pot new file mode 100644 index 00000000..c3b65128 --- /dev/null +++ b/docs/_locale/ja/index.pot @@ -0,0 +1,89 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../index.rst:0 +msgid "Add missing parts or improve the :ref:`Documentation<documentation:Write Documentation>`." +msgstr "Add missing parts or improve the :ref:`Documentation<documentation:Write Documentation>`." + +#: ../../index.rst:70 +msgid "Adminguide" +msgstr "Adminguide" + +#: ../../index.rst:31 +msgid "Automate" +msgstr "Automate" + +#: ../../index.rst:23 +msgid "Configuration and Operation" +msgstr "Configuration and Operation" + +#: ../../index.rst:44 +msgid "Contribute and Community" +msgstr "Contribute and Community" + +#: ../../index.rst:83 +msgid "Development" +msgstr "Development" + +#: ../../index.rst:0 +msgid "Discuss in `Slack <https://slack.vyos.io/>`_ or the `Forum <https://forum.vyos.io>`_." +msgstr "Discuss in `Slack <https://slack.vyos.io/>`_ or the `Forum <https://forum.vyos.io>`_." + +#: ../../index.rst:38 +msgid "Examples" +msgstr "Examples" + +#: ../../index.rst:61 +msgid "First Steps" +msgstr "First Steps" + +#: ../../index.rst:11 +msgid "Get / Build VyOS" +msgstr "Get / Build VyOS" + +#: ../../index.rst:40 +msgid "Get some inspiration from the :ref:`Configuration Blueprints<configexamples/index:Configuration Blueprints>` to build your infrastructure." +msgstr "Get some inspiration from the :ref:`Configuration Blueprints<configexamples/index:Configuration Blueprints>` to build your infrastructure." + +#: ../../index.rst:16 +msgid "Install VyOS" +msgstr "Install VyOS" + +#: ../../index.rst:33 +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 "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>`." + +#: ../../index.rst:96 +msgid "Misc" +msgstr "Misc" + +#: ../../index.rst:0 +msgid "Or you can pick up a `Task <https://vyos.dev/>`_ and fix the :ref:`code<contributing/development:development>`." +msgstr "Or you can pick up a `Task <https://vyos.dev/>`_ and fix the :ref:`code<contributing/development:development>`." + +#: ../../index.rst:13 +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 "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." + +#: ../../index.rst:18 +msgid "Read about how to install VyOS on :ref:`Bare Metal<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 "Read about how to install VyOS on :ref:`Bare Metal<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" + +#: ../../index.rst:0 +msgid "There are many ways to contribute to the project." +msgstr "There are many ways to contribute to the project." + +#: ../../index.rst:25 +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 "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." + +#: ../../index.rst:5 +msgid "VyOS User Guide" +msgstr "VyOS User Guide" diff --git a/docs/_locale/ja/installation.pot b/docs/_locale/ja/installation.pot new file mode 100644 index 00000000..dd3e9019 --- /dev/null +++ b/docs/_locale/ja/installation.pot @@ -0,0 +1,1976 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../installation/virtual/docker.rst:62 +msgid "$ mkdir rootfs $ sudo mount -o loop vyos-1.4-rolling-202308240020-amd64.iso rootfs $ sudo apt-get install -y squashfs-tools $ mkdir unsquashfs $ sudo unsquashfs -f -d unsquashfs/ rootfs/live/filesystem.squashfs $ sudo tar -C unsquashfs -c . | docker import - vyos:1.4-rolling-202111281249 $ sudo umount rootfs $ cd .. $ sudo rm -rf vyos $ docker run -d --rm --name vyos --privileged -v /lib/modules:/lib/modules \\ > vyos:1.4-rolling-202111281249 /sbin/init $ docker exec -ti vyos su - vyos" +msgstr "$ mkdir rootfs $ sudo mount -o loop vyos-1.4-rolling-202308240020-amd64.iso rootfs $ sudo apt-get install -y squashfs-tools $ mkdir unsquashfs $ sudo unsquashfs -f -d unsquashfs/ rootfs/live/filesystem.squashfs $ sudo tar -C unsquashfs -c . | docker import - vyos:1.4-rolling-202111281249 $ sudo umount rootfs $ cd .. $ sudo rm -rf vyos $ docker run -d --rm --name vyos --privileged -v /lib/modules:/lib/modules \\ > vyos:1.4-rolling-202111281249 /sbin/init $ docker exec -ti vyos su - vyos" + +#: ../../installation/virtual/gns3.rst:169 +msgid "**Advanced** settings tab: Mark the checkbox **Use as a linked base VM** and click ``OK`` to save the changes." +msgstr "**Advanced** settings tab: Mark the checkbox **Use as a linked base VM** and click ``OK`` to save the changes." + +#: ../../installation/virtual/gns3.rst:160 +msgid "**CD/DVD** tab: Unmount the installation image file by clearing the **Image** entry field." +msgstr "**CD/DVD** tab: Unmount the installation image file by clearing the **Image** entry field." + +#: ../../installation/virtual/gns3.rst:142 +msgid "**Delete the VM** from the GNS3 project." +msgstr "**Delete the VM** from the GNS3 project." + +#: ../../installation/install.rst:33 +msgid "**Early Production Access**" +msgstr "**Early Production Access**" + +#: ../../installation/install.rst:538 +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 "**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." + +#: ../../installation/virtual/gns3.rst:156 +msgid "**General settings** tab: Set the boot priority to **HDD**" +msgstr "**General settings** tab: Set the boot priority to **HDD**" + +#: ../../installation/install.rst:37 +msgid "**Long-Term Support**" +msgstr "**Long-Term Support**" + +#: ../../installation/install.rst:21 +msgid "**Nightly (Beta)**" +msgstr "**Nightly (Beta)**" + +#: ../../installation/install.rst:17 +msgid "**Nightly (Current)**" +msgstr "**Nightly (Current)**" + +#: ../../installation/install.rst:29 +msgid "**Release Candidate**" +msgstr "**Release Candidate**" + +#: ../../installation/install.rst:432 +msgid "**Requirements**" +msgstr "**Requirements**" + +#: ../../installation/install.rst:543 +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 "**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``." + +#: ../../installation/install.rst:25 +msgid "**Snapshot**" +msgstr "**Snapshot**" + +#: ../../installation/install.rst:300 +msgid "**Warning**: This will destroy all data on the USB drive!" +msgstr "**Warning**: This will destroy all data on the USB drive!" + +#: ../../installation/vyos-on-baremetal.rst:20 +msgid "1x Crucial CT4G4DFS824A (4GB DDR4 RAM 2400 MT/s, PC4-19200)" +msgstr "1x Crucial CT4G4DFS824A (4GB DDR4 RAM 2400 MT/s, PC4-19200)" + +#: ../../installation/vyos-on-baremetal.rst:102 +msgid "1x Kingston SUV500MS/120G" +msgstr "1x Kingston SUV500MS/120G" + +#: ../../installation/vyos-on-baremetal.rst:21 +msgid "1x SanDisk Ultra Fit 32GB (USB-A 3.0 SDCZ43-032G-G46 mass storage for OS)" +msgstr "1x SanDisk Ultra Fit 32GB (USB-A 3.0 SDCZ43-032G-G46 mass storage for OS)" + +#: ../../installation/vyos-on-baremetal.rst:18 +msgid "1x Supermicro A2SDi-2C-HLN4F (Intel Atom C3338, 2C/2T, 4MB cache, Quad LAN with Intel C3000 SoC 1GbE)" +msgstr "1x Supermicro A2SDi-2C-HLN4F (Intel Atom C3338, 2C/2T, 4MB cache, Quad LAN with Intel C3000 SoC 1GbE)" + +#: ../../installation/vyos-on-baremetal.rst:16 +msgid "1x Supermicro CSE-505-203B (19\" 1U chassis, inkl. 200W PSU)" +msgstr "1x Supermicro CSE-505-203B (19\" 1U chassis, inkl. 200W PSU)" + +#: ../../installation/vyos-on-baremetal.rst:30 +msgid "1x Supermicro MCP-120-00063-0N (Riser Card Bracket)" +msgstr "1x Supermicro MCP-120-00063-0N (Riser Card Bracket)" + +#: ../../installation/vyos-on-baremetal.rst:17 +msgid "1x Supermicro MCP-260-00085-0B (I/O Shield for A2SDi-2C-HLN4F)" +msgstr "1x Supermicro MCP-260-00085-0B (I/O Shield for A2SDi-2C-HLN4F)" + +#: ../../installation/vyos-on-baremetal.rst:22 +msgid "1x Supermicro MCP-320-81302-0B (optional FAN tray)" +msgstr "1x Supermicro MCP-320-81302-0B (optional FAN tray)" + +#: ../../installation/vyos-on-baremetal.rst:29 +msgid "1x Supermicro RSC-RR1U-E8 (Riser Card)" +msgstr "1x Supermicro RSC-RR1U-E8 (Riser Card)" + +#: ../../installation/vyos-on-baremetal.rst:103 +msgid "1x VARIA Group Item 326745 19\" dual rack for APU4" +msgstr "1x VARIA Group Item 326745 19\" dual rack for APU4" + +#: ../../installation/vyos-on-baremetal.rst:101 +msgid "1x apu4c4 = 4 i211AT LAN / AMD GX-412TC CPU / 4 GB DRAM / dual SIM" +msgstr "1x apu4c4 = 4 i211AT LAN / AMD GX-412TC CPU / 4 GB DRAM / dual SIM" + +#: ../../installation/vyos-on-baremetal.rst:91 +msgid "2 miniPCI express (one with SIM socket for 3G modem)." +msgstr "2 miniPCI express (one with SIM socket for 3G modem)." + +#: ../../installation/vyos-on-baremetal.rst:89 +msgid "4 GB DDR3-1333 DRAM, with optional ECC support" +msgstr "4 GB DDR3-1333 DRAM, with optional ECC support" + +#: ../../installation/vyos-on-baremetal.rst:92 +msgid "4 Gigabit Ethernet channels using Intel i211AT NICs" +msgstr "4 Gigabit Ethernet channels using Intel i211AT NICs" + +#: ../../installation/vyos-on-baremetal.rst:87 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 custom VyOS powder coat" +msgstr "APU4 custom VyOS powder coat" + +#: ../../installation/vyos-on-baremetal.rst:None +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 desktop back" +msgstr "APU4 desktop back" + +#: ../../installation/vyos-on-baremetal.rst:None +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 desktop closed" +msgstr "APU4 desktop closed" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 rack closed" +msgstr "APU4 rack closed" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 rack front" +msgstr "APU4 rack front" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 rack module #1" +msgstr "APU4 rack module #1" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 rack module #2" +msgstr "APU4 rack module #2" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "APU4 rack module #3 with PSU" +msgstr "APU4 rack module #3 with PSU" + +#: ../../installation/virtual/gns3.rst:19 +msgid "A VyOS installation image (.iso file). You can find how to get it on the :ref:`installation` page" +msgstr "A VyOS installation image (.iso file). You can find how to get it on the :ref:`installation` page" + +#: ../../installation/install.rst:487 +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 "A directory named pxelinux.cfg which must contain the configuration file. We will use the configuration_ file shown below, which we named default_." + +#: ../../installation/install.rst:25 +msgid "A particularly stable release frozen from nightly each month after manual testing. Still contains experimental code." +msgstr "A particularly stable release frozen from nightly each month after manual testing. Still contains experimental code." + +#: ../../installation/install.rst:269 +msgid "A permanent VyOS installation always requires to go first through a live installation." +msgstr "A permanent VyOS installation always requires to go first through a live installation." + +#: ../../installation/virtual/gns3.rst:22 +msgid "A working GNS3 installation. For further information see the `GNS3 documentation <https://docs.gns3.com/>`__." +msgstr "A working GNS3 installation. For further information see the `GNS3 documentation <https://docs.gns3.com/>`__." + +#: ../../installation/vyos-on-baremetal.rst:90 +msgid "About 6 to 10W of 12V DC power depending on CPU load" +msgstr "About 6 to 10W of 12V DC power depending on CPU load" + +#: ../../installation/cloud/azure.rst:55 +msgid "Absorbing Routes" +msgstr "Absorbing Routes" + +#: ../../installation/install.rst:15 +msgid "Access to Images" +msgstr "Access to Images" + +#: ../../installation/install.rst:15 +msgid "Access to Source" +msgstr "Access to Source" + +#: ../../installation/vyos-on-baremetal.rst:368 +msgid "Acrosser AND-J190N1" +msgstr "Acrosser AND-J190N1" + +#: ../../installation/cloud/azure.rst:45 +msgid "Add interface" +msgstr "Add interface" + +#: ../../installation/cloud/azure.rst:61 +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 "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." + +#: ../../installation/cloud/aws.rst:27 +msgid "Additional storage. You can remove additional storage ``/dev/sdb``. First root device will be ``/dev/xvda``. You can skeep this step." +msgstr "Additional storage. You can remove additional storage ``/dev/sdb``. First root device will be ``/dev/xvda``. You can skeep this step." + +#: ../../installation/vyos-on-baremetal.rst:394 +msgid "Advanced > Serial Port Console Redirection > Console Redirection Settings:" +msgstr "Advanced > Serial Port Console Redirection > Console Redirection Settings:" + +#: ../../installation/virtual/gns3.rst:139 +msgid "After a successful installation, shutdown the VM with the ``poweroff`` command." +msgstr "After a successful installation, shutdown the VM with the ``poweroff`` command." + +#: ../../installation/cloud/gcp.rst:41 +msgid "After few seconds click to ``instance``" +msgstr "After few seconds click to ``instance``" + +#: ../../installation/virtual/libvirt.rst:50 +msgid "After installation - exit from the console using the key combination ``Ctrl + ]`` and reboot the system." +msgstr "After installation - exit from the console using the key combination ``Ctrl + ]`` and reboot the system." + +#: ../../installation/virtual/proxmox.rst:47 +msgid "After installation has completed, remove the installation iso using the GUI or ``qm set 200 --ide2 none``." +msgstr "After installation has completed, remove the installation iso using the GUI or ``qm set 200 --ide2 none``." + +#: ../../installation/update.rst:81 +msgid "After reboot you might want to verify the version you are running with the :opcmd:`show version` command." +msgstr "After reboot you might want to verify the version you are running with the :opcmd:`show version` command." + +#: ../../installation/install.rst:413 +msgid "After the installation is completed, remove the live USB stick or CD." +msgstr "After the installation is completed, remove the live USB stick or CD." + +#: ../../installation/migrate-from-vyatta.rst:20 +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 "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." + +#: ../../installation/cloud/aws.rst:3 +msgid "Amazon AWS" +msgstr "Amazon AWS" + +#: ../../installation/cloud/aws.rst:53 +msgid "Amazon CloudWatch Agent Usage" +msgstr "Amazon CloudWatch Agent Usage" + +#: ../../installation/install.rst:450 +msgid "An IP address" +msgstr "An IP address" + +#: ../../installation/vyos-on-baremetal.rst:334 +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 "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." + +#: ../../installation/install.rst:551 +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 "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``." + +#: ../../installation/install.rst:240 +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 "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:" + +#: ../../installation/install.rst:228 +msgid "Another point is that we are using RSA now, which requires absurdly large keys to be secure." +msgstr "Another point is that we are using RSA now, which requires absurdly large keys to be secure." + +#: ../../installation/vyos-on-baremetal.rst:201 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:82 +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 "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." + +#: ../../installation/virtual/gns3.rst:100 +msgid "At the **CD/DVD** tab click on ``Browse...`` and locate the VyOS image you want to install." +msgstr "At the **CD/DVD** tab click on ``Browse...`` and locate the VyOS image you want to install." + +#: ../../installation/virtual/gns3.rst:95 +msgid "At the **HDD** tab, change the Disk interface to **sata** to speed up the boot process." +msgstr "At the **HDD** tab, change the Disk interface to **sata** to speed up the boot process." + +#: ../../installation/virtual/gns3.rst:120 +msgid "At the general **Preferences** window, click ``OK`` to save and close." +msgstr "At the general **Preferences** window, click ``OK`` to save and close." + +#: ../../installation/cloud/aws.rst:59 +msgid "Attach the created role to your VyOS :abbr:`EC2 (Elastic Compute Cloud)` instance." +msgstr "Attach the created role to your VyOS :abbr:`EC2 (Elastic Compute Cloud)` instance." + +#: ../../installation/install.rst:17 +msgid "Automatically built from the current branch. Always up to date with cutting edge development but guaranteed to contain bugs." +msgstr "Automatically built from the current branch. Always up to date with cutting edge development but guaranteed to contain bugs." + +#: ../../installation/install.rst:21 +msgid "Automatically built from the development branch and released alongside snapshots. Most likely contains bugs." +msgstr "Automatically built from the development branch and released alongside snapshots. Most likely contains bugs." + +#: ../../installation/cloud/azure.rst:3 +msgid "Azure" +msgstr "Azure" + +#: ../../installation/cloud/azure.rst:51 +msgid "Azure does not allow you attach interface when the instance in the **Running** state." +msgstr "Azure does not allow you attach interface when the instance in the **Running** state." + +#: ../../installation/cloud/azure.rst:68 +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 "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'``" + +#: ../../installation/vyos-on-baremetal.rst:382 +msgid "BIOS Settings:" +msgstr "BIOS Settings:" + +#: ../../installation/install.rst:334 +msgid "Before a permanent installation, VyOS requires a :ref:`live_installation`." +msgstr "Before a permanent installation, VyOS requires a :ref:`live_installation`." + +#: ../../installation/vyos-on-baremetal.rst:358 +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 "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." + +#: ../../installation/virtual/gns3.rst:80 +msgid "Being again at the **Preferences** window, having **Qemu VMs** selected and having our new VM selected, click the ``Edit`` button." +msgstr "Being again at the **Preferences** window, having **Qemu VMs** selected and having our new VM selected, click the ``Edit`` button." + +#: ../../installation/vyos-on-baremetal.rst:397 +msgid "Bits per second : 9600" +msgstr "Bits per second : 9600" + +#: ../../installation/install.rst:580 +msgid "Black screen on install" +msgstr "Black screen on install" + +#: ../../installation/vyos-on-baremetal.rst:362 +msgid "Boot to the VyOS installer and install as usual." +msgstr "Boot to the VyOS installer and install as usual." + +#: ../../installation/vyos-on-baremetal.rst:236 +msgid "Both device types operate without any moving parts and emit zero noise." +msgstr "Both device types operate without any moving parts and emit zero noise." + +#: ../../installation/install.rst:66 +msgid "Building from source" +msgstr "Building from source" + +#: ../../installation/virtual/libvirt.rst:13 +msgid "CLI" +msgstr "CLI" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B Back" +msgstr "CSE-505-203B Back" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B Front" +msgstr "CSE-505-203B Front" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B Open 1" +msgstr "CSE-505-203B Open 1" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B Open 2" +msgstr "CSE-505-203B Open 2" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B Open 3" +msgstr "CSE-505-203B Open 3" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B w/ 10GE Open" +msgstr "CSE-505-203B w/ 10GE Open" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B w/ 10GE Open 1" +msgstr "CSE-505-203B w/ 10GE Open 1" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B w/ 10GE Open 2" +msgstr "CSE-505-203B w/ 10GE Open 2" + +#: ../../installation/vyos-on-baremetal.rst:None +msgid "CSE-505-203B w/ 10GE Open 3" +msgstr "CSE-505-203B w/ 10GE Open 3" + +#: ../../installation/cloud/gcp.rst:37 +msgid "Change Deployment name/Zone/Machine type and click ``Deploy``" +msgstr "Change Deployment name/Zone/Machine type and click ``Deploy``" + +#: ../../installation/vyos-on-baremetal.rst:360 +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 "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." + +#: ../../installation/virtual/libvirt.rst:140 +#: ../../installation/virtual/libvirt.rst:180 +msgid "Choose Memory and CPU" +msgstr "Choose Memory and CPU" + +#: ../../installation/virtual/libvirt.rst:171 +msgid "Choose ``Import existing disk`` image" +msgstr "Choose ``Import existing disk`` image" + +#: ../../installation/virtual/libvirt.rst:132 +msgid "Choose ``Local install media`` (ISO)" +msgstr "Choose ``Local install media`` (ISO)" + +#: ../../installation/virtual/libvirt.rst:136 +msgid "Choose path to iso vyos.iso. Operating System can be any Debian based." +msgstr "Choose path to iso vyos.iso. Operating System can be any Debian based." + +#: ../../installation/cloud/aws.rst:18 +msgid "Choose the instance type. Minimum recommendation start from ``m3.medium``" +msgstr "Choose the instance type. Minimum recommendation start from ``m3.medium``" + +#: ../../installation/virtual/libvirt.rst:175 +msgid "Choose the path to the image ``vyos_kvm.qcow2`` that was previously downloaded . Operation System can be any Debian based." +msgstr "Choose the path to the image ``vyos_kvm.qcow2`` that was previously downloaded . Operation System can be any Debian based." + +#: ../../installation/cloud/azure.rst:12 +msgid "Choose vm name, resource group, region and click **Browse all public and private images**" +msgstr "Choose vm name, resource group, region and click **Browse all public and private images**" + +#: ../../installation/cloud/gcp.rst:30 +msgid "Click **Add item** and paste your public ssh key. Click ``Save``." +msgstr "Click **Add item** and paste your public ssh key. Click ``Save``." + +#: ../../installation/virtual/gns3.rst:74 +msgid "Click ``Finish`` to end the **New QEMU VM template** wizard." +msgstr "Click ``Finish`` to end the **New QEMU VM template** wizard." + +#: ../../installation/cloud/azure.rst:29 +msgid "Click ``Review + create``. After a few seconds your deployment will be complete" +msgstr "Click ``Review + create``. After a few seconds your deployment will be complete" + +#: ../../installation/virtual/gns3.rst:88 +msgid "Click on the ``Browse...`` button to choose the **Symbol** you want to have representing your VM." +msgstr "Click on the ``Browse...`` button to choose the **Symbol** you want to have representing your VM." + +#: ../../installation/cloud/aws.rst:10 +msgid "Click to ``Instances`` and ``Launch Instance``" +msgstr "Click to ``Instances`` and ``Launch Instance``" + +#: ../../installation/cloud/azure.rst:33 +msgid "Click to your new vm and find out your Public IP address." +msgstr "Click to your new vm and find out your Public IP address." + +#: ../../installation/install.rst:562 +msgid "Client Boot" +msgstr "Client Boot" + +#: ../../installation/install.rst:434 +msgid "Clients (where VyOS is to be installed) with a PXE-enabled NIC" +msgstr "Clients (where VyOS is to be installed) with a PXE-enabled NIC" + +#: ../../installation/cloud/aws.rst:88 +msgid "CloudWatchAgentServerRole is too permisive and should be used for single configuration creation and deployment. That's why after completion of step #3 higly recommended to replace instance CloudWatchAgentAdminRole role with CloudWatchAgentServerRole." +msgstr "CloudWatchAgentServerRole is too permisive and should be used for single configuration creation and deployment. That's why after completion of step #3 higly recommended to replace instance CloudWatchAgentAdminRole role with CloudWatchAgentServerRole." + +#: ../../installation/cloud/aws.rst:82 +msgid "CloudWatch SSM Configuration creation" +msgstr "CloudWatch SSM Configuration creation" + +#: ../../installation/install.rst:12 +msgid "Comparison of VyOS image releases" +msgstr "Comparison of VyOS image releases" + +#: ../../installation/vyos-on-baremetal.rst:117 +msgid "Compex WLE900VX mini-PCIe WiFi module, only supported in mPCIe slot 1." +msgstr "Compex WLE900VX mini-PCIe WiFi module, only supported in mPCIe slot 1." + +#: ../../installation/install.rst:443 +msgid "Configuration" +msgstr "Configuration" + +#: ../../installation/cloud/aws.rst:32 +msgid "Configure Security Group. It's recommended that you configure ssh access only from certain address sources. Or permit any (by default)." +msgstr "Configure Security Group. It's recommended that you configure ssh access only from certain address sources. Or permit any (by default)." + +#: ../../installation/install.rst:448 +msgid "Configure a DHCP server to provide the client with:" +msgstr "Configure a DHCP server to provide the client with:" + +#: ../../installation/install.rst:476 +msgid "Configure a TFTP server so that it serves the following:" +msgstr "Configure a TFTP server so that it serves the following:" + +#: ../../installation/cloud/aws.rst:22 +msgid "Configure instance for your requirements. Select number of instances / network / subnet" +msgstr "Configure instance for your requirements. Select number of instances / network / subnet" + +#: ../../installation/vyos-on-baremetal.rst:142 +msgid "Connect serial port to a PC through null modem cable (RXD / TXD crossed over). Set terminal emulator to 115200 8N1." +msgstr "Connect serial port to a PC through null modem cable (RXD / TXD crossed over). Set terminal emulator to 115200 8N1." + +#: ../../installation/virtual/libvirt.rst:36 +msgid "Connect to VM with command ``virsh console vyos_r1``" +msgstr "Connect to VM with command ``virsh console vyos_r1``" + +#: ../../installation/virtual/libvirt.rst:79 +msgid "Connect to VM with command ``virsh console vyos_r2``" +msgstr "Connect to VM with command ``virsh console vyos_r2``" + +#: ../../installation/vyos-on-baremetal.rst:391 +msgid "Connect to serial (115200bps). Power on the appliance and press Del in the console when requested to enter BIOS settings." +msgstr "Connect to serial (115200bps). Power on the appliance and press Del in the console when requested to enter BIOS settings." + +#: ../../installation/cloud/gcp.rst:49 +msgid "Connect to the instance. SSH key was generated in the first step." +msgstr "Connect to the instance. SSH key was generated in the first step." + +#: ../../installation/cloud/aws.rst:45 +#: ../../installation/cloud/azure.rst:37 +msgid "Connect to the instance by SSH key." +msgstr "Connect to the instance by SSH key." + +#: ../../installation/cloud/index.rst:7 +#: ../../installation/cloud/index.rst:7 +#: ../../installation/index.rst:7 +#: ../../installation/index.rst:7 +#: ../../installation/virtual/index.rst:5 +#: ../../installation/virtual/index.rst:5 +msgid "Content" +msgstr "Content" + +#: ../../installation/virtual/proxmox.rst:14 +msgid "Copy the qcow2 image to a temporary directory on the Proxmox server." +msgstr "Copy the qcow2 image to a temporary directory on the Proxmox server." + +#: ../../installation/virtual/libvirt.rst:18 +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 "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." + +#: ../../installation/virtual/libvirt.rst:63 +msgid "Create VM with ``import`` qcow2 disk option." +msgstr "Create VM with ``import`` qcow2 disk option." + +#: ../../installation/vyos-on-baremetal.rst:412 +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 "Create a VyOS bootable USB key. I used the 64-bit ISO (VyOS 1.1.7) and `LinuxLive USB Creator <http://www.linuxliveusb.com/>`_." + +#: ../../installation/vyos-on-baremetal.rst:140 +msgid "Create a bootable USB pendrive using e.g. Rufus_ on a Windows machine." +msgstr "Create a bootable USB pendrive using e.g. Rufus_ on a Windows machine." + +#: ../../installation/virtual/gns3.rst:130 +msgid "Create a new project." +msgstr "Create a new project." + +#: ../../installation/cloud/azure.rst:59 +msgid "Create a route table and browse to **Configuration**" +msgstr "Create a route table and browse to **Configuration**" + +#: ../../installation/cloud/aws.rst:57 +msgid "Create an :abbr:`IAM (Identity and Access Management)` role for the :abbr:`EC2 (Elastic Compute Cloud)` instance to access CloudWatch service, and name it CloudWatchAgentServerRole. The role should contain two default policies: CloudWatchAgentServerPolicy and AmazonSSMManagedInstanceCore." +msgstr "Create an :abbr:`IAM (Identity and Access Management)` role for the :abbr:`EC2 (Elastic Compute Cloud)` instance to access CloudWatch service, and name it CloudWatchAgentServerRole. The role should contain two default policies: CloudWatchAgentServerPolicy and AmazonSSMManagedInstanceCore." + +#: ../../installation/cloud/aws.rst:86 +msgid "Create an :abbr:`IAM (Identity and Access Management)` role for your :abbr:`EC2 (Elastic Compute Cloud)` instance to access the CloudWatch service. Name it CloudWatchAgentAdminRole. The role should contain at two default policies: CloudWatchAgentAdminPolicy and AmazonSSMManagedInstanceCore." +msgstr "Create an :abbr:`IAM (Identity and Access Management)` role for your :abbr:`EC2 (Elastic Compute Cloud)` instance to access the CloudWatch service. Name it CloudWatchAgentAdminRole. The role should contain at two default policies: CloudWatchAgentAdminPolicy and AmazonSSMManagedInstanceCore." + +#: ../../installation/cloud/aws.rst:84 +msgid "Creating the Amazon Cloudwatch Agent Configuration in Amazon :abbr:`SSM (Systems Manager)` Parameter Store." +msgstr "Creating the Amazon Cloudwatch Agent Configuration in Amazon :abbr:`SSM (Systems Manager)` Parameter Store." + +#: ../../installation/install.rst:216 +msgid "Currently we are using GPG for release signing (pretty much like everyone else)." +msgstr "Currently we are using GPG for release signing (pretty much like everyone else)." + +#: ../../installation/cloud/azure.rst:25 +msgid "Define network, subnet, Public IP. Or it will be created by default." +msgstr "Define network, subnet, Public IP. Or it will be created by default." + +#: ../../installation/image.rst:47 +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 "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`." + +#: ../../installation/vyos-on-baremetal.rst:137 +msgid "Depending on the VyOS versions you intend to install there is a difference in the serial port settings (:vytask:`T1327`)." +msgstr "Depending on the VyOS versions you intend to install there is a difference in the serial port settings (:vytask:`T1327`)." + +#: ../../installation/cloud/aws.rst:6 +#: ../../installation/cloud/azure.rst:6 +#: ../../installation/cloud/gcp.rst:6 +msgid "Deploy VM" +msgstr "Deploy VM" + +#: ../../installation/virtual/proxmox.rst:12 +msgid "Deploy VyOS from CLI with qcow2 image" +msgstr "Deploy VyOS from CLI with qcow2 image" + +#: ../../installation/virtual/proxmox.rst:35 +msgid "Deploy VyOS from CLI with rolling release ISO" +msgstr "Deploy VyOS from CLI with rolling release ISO" + +#: ../../installation/cloud/aws.rst:8 +msgid "Deploy VyOS on Amazon :abbr:`AWS (Amazon Web Services)`" +msgstr "Deploy VyOS on Amazon :abbr:`AWS (Amazon Web Services)`" + +#: ../../installation/cloud/azure.rst:8 +msgid "Deploy VyOS on Azure." +msgstr "Deploy VyOS on Azure." + +#: ../../installation/virtual/docker.rst:49 +msgid "Deploy container from ISO" +msgstr "Deploy container from ISO" + +#: ../../installation/virtual/libvirt.rst:16 +#: ../../installation/virtual/libvirt.rst:127 +msgid "Deploy from ISO" +msgstr "Deploy from ISO" + +#: ../../installation/virtual/libvirt.rst:54 +#: ../../installation/virtual/libvirt.rst:159 +msgid "Deploy from qcow2" +msgstr "Deploy from qcow2" + +#: ../../installation/install.rst:15 +msgid "Description" +msgstr "Description" + +#: ../../installation/vyos-on-baremetal.rst:270 +msgid "Desktop / Bench Top" +msgstr "Desktop / Bench Top" + +#: ../../installation/install.rst:17 +msgid "Developing VyOS, testing new features, experimenting." +msgstr "Developing VyOS, testing new features, experimenting." + +#: ../../installation/install.rst:21 +msgid "Developing and testing the latest major version under development." +msgstr "Developing and testing the latest major version under development." + +#: ../../installation/vyos-on-baremetal.rst:406 +msgid "Disable XHCI" +msgstr "Disable XHCI" + +#: ../../installation/virtual/libvirt.rst:144 +msgid "Disk size" +msgstr "Disk size" + +#: ../../installation/install.rst:547 +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 "Do not change the name of the *filesystem.squashfs* file. If you are working with different versions, you can create different directories instead." + +#: ../../installation/virtual/docker.rst:7 +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 "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." + +#: ../../installation/install.rst:52 +msgid "Download" +msgstr "Download" + +#: ../../installation/install.rst:90 +msgid "Download Verification" +msgstr "Download Verification" + +#: ../../installation/virtual/libvirt.rst:161 +msgid "Download predefined VyOS.qcow2 image for ``KVM``" +msgstr "Download predefined VyOS.qcow2 image for ``KVM``" + +#: ../../installation/virtual/docker.rst:51 +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 "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``." + +#: ../../installation/virtual/docker.rst:51 +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-202308240020-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 "Download the ISO on which you want to base the container. In this example, the name of the ISO is ``vyos-1.4-rolling-202308240020-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``." + +#: ../../installation/virtual/proxmox.rst:37 +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 "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." + +#: ../../installation/virtual/gns3.rst:131 +msgid "Drag the newly created VyOS VM into it." +msgstr "Drag the newly created VyOS VM into it." + +#: ../../installation/install.rst:256 +msgid "During an image upgrade VyOS performas the following command:" +msgstr "During an image upgrade VyOS performas the following command:" + +#: ../../installation/virtual/vmware.rst:7 +msgid "ESXi 5.5 or later" +msgstr "ESXi 5.5 or later" + +#: ../../installation/virtual/eve-ng.rst:3 +msgid "EVE-NG" +msgstr "EVE-NG" + +#: ../../installation/virtual/docker.rst:31 +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 "Edit /etc/docker/daemon.json to set the ``ipv6`` key to ``true`` and to specify the ``fixed-cidr-v6`` to your desired IPv6 subnet." + +#: ../../installation/vyos-on-baremetal.rst:407 +msgid "Enable USB 2.0 (EHCI) Support" +msgstr "Enable USB 2.0 (EHCI) Support" + +#: ../../installation/cloud/aws.rst:61 +msgid "Ensure that amazon-cloudwatch-agent package is installed." +msgstr "Ensure that amazon-cloudwatch-agent package is installed." + +#: ../../installation/install.rst:37 +msgid "Every major version" +msgstr "Every major version" + +#: ../../installation/install.rst:25 +msgid "Every month until RC comes out" +msgstr "Every month until RC comes out" + +#: ../../installation/install.rst:17 +#: ../../installation/install.rst:21 +msgid "Every night" +msgstr "Every night" + +#: ../../installation/install.rst:343 +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 "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." + +#: ../../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 +msgid "Everyone" +msgstr "Everyone" + +#: ../../installation/install.rst:76 +msgid "Everyone can download bleeding-edge VyOS rolling images from: https://downloads.vyos.io/" +msgstr "Everyone can download bleeding-edge VyOS rolling images from: https://downloads.vyos.io/" + +#: ../../installation/update.rst:50 +msgid "Example" +msgstr "Example" + +#: ../../installation/cloud/gcp.rst:13 +msgid "Example:" +msgstr "Example:" + +#: ../../installation/install.rst:519 +msgid "Example of simple (no menu) configuration file:" +msgstr "Example of simple (no menu) configuration file:" + +#: ../../installation/install.rst:499 +msgid "Example of the contents of the TFTP server:" +msgstr "Example of the contents of the TFTP server:" + +#: ../../installation/vyos-on-baremetal.rst:109 +msgid "Extension Modules" +msgstr "Extension Modules" + +#: ../../installation/install.rst:439 +msgid "Files *pxelinux.0* and *ldlinux.c32* `from the Syslinux distribution <https://kernel.org/pub/linux/utils/boot/syslinux/>`_" +msgstr "Files *pxelinux.0* and *ldlinux.c32* `from the Syslinux distribution <https://kernel.org/pub/linux/utils/boot/syslinux/>`_" + +#: ../../installation/install.rst:564 +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 "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." + +#: ../../installation/install.rst:201 +msgid "Finally, verify the authenticity of the downloaded image:" +msgstr "Finally, verify the authenticity of the downloaded image:" + +#: ../../installation/install.rst:285 +msgid "Find out the device name of your USB drive (you can use the ``lsblk`` command)" +msgstr "Find out the device name of your USB drive (you can use the ``lsblk`` command)" + +#: ../../installation/cloud/gcp.rst:45 +msgid "Find out your external IP address" +msgstr "Find out your external IP address" + +#: ../../installation/cloud/aws.rst:41 +msgid "Find out your public IP address." +msgstr "Find out your public IP address." + +#: ../../installation/virtual/gns3.rst:30 +msgid "First, a virtual machine (VM) for the VyOS installation must be created in GNS3." +msgstr "First, a virtual machine (VM) for the VyOS installation must be created in GNS3." + +#: ../../installation/install.rst:102 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:384 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:42 +msgid "For completion the key below corresponds to the key listed in the URL above." +msgstr "For completion the key below corresponds to the key listed in the URL above." + +#: ../../installation/vyos-on-baremetal.rst:387 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:161 +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 "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." + +#: ../../installation/install.rst:192 +msgid "GPG verification" +msgstr "GPG verification" + +#: ../../installation/install.rst:582 +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 "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." + +#: ../../installation/cloud/gcp.rst:10 +msgid "Generate SSH key pair type **ssh-rsa** from the host that will connect to VyOS." +msgstr "Generate SSH key pair type **ssh-rsa** from the host that will connect to VyOS." + +#: ../../installation/cloud/azure.rst:21 +msgid "Generate new SSH key pair or use existing." +msgstr "Generate new SSH key pair or use existing." + +#: ../../installation/cloud/azure.rst:10 +msgid "Go to the Azure services and Click to **Add new Virtual machine**" +msgstr "Go to the Azure services and Click to **Add new Virtual machine**" + +#: ../../installation/virtual/gns3.rst:33 +msgid "Go to the GNS3 **File** menu, click **New template** and choose select **Manually create a new Template**." +msgstr "Go to the GNS3 **File** menu, click **New template** and choose select **Manually create a new Template**." + +#: ../../installation/cloud/gcp.rst:3 +msgid "Google Cloud Platform" +msgstr "Google Cloud Platform" + +#: ../../installation/install.rst:37 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:304 +msgid "Hardware" +msgstr "Hardware" + +#: ../../installation/install.rst:45 +msgid "Hardware requirements" +msgstr "Hardware requirements" + +#: ../../installation/virtual/docker.rst:22 +msgid "Here is a example using the macvlan driver." +msgstr "Here is a example using the macvlan driver." + +#: ../../installation/install.rst:33 +msgid "Highly stable with no known bugs. Needs to be tested repeatedly under different conditions before it can become the final release." +msgstr "Highly stable with no known bugs. Needs to be tested repeatedly under different conditions before it can become the final release." + +#: ../../installation/install.rst:25 +msgid "Home labs and simple networks that call for new features." +msgstr "Home labs and simple networks that call for new features." + +#: ../../installation/vyos-on-baremetal.rst:132 +msgid "Huawei ME909u-521 miniPCIe card (LTE)" +msgstr "Huawei ME909u-521 miniPCIe card (LTE)" + +#: ../../installation/vyos-on-baremetal.rst:415 +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 "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." + +#: ../../installation/virtual/docker.rst:13 +msgid "IPv6 Support for docker" +msgstr "IPv6 Support for docker" + +#: ../../installation/vyos-on-baremetal.rst:346 +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 "I believe this is actually the same hardware as the Protectli. I purchased it in June 2018. It came pre-loaded with pfSense." + +#: ../../installation/vyos-on-baremetal.rst:418 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:10 +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 "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." + +#: ../../installation/cloud/azure.rst:47 +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 "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." + +#: ../../installation/update.rst:25 +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 "If there is not enough **free disk space available**, the installation will be canceled. To delete images use the :opcmd:`delete system image` command." + +#: ../../installation/cloud/azure.rst:57 +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 "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." + +#: ../../installation/virtual/libvirt.rst:93 +msgid "If you can not go to this screen" +msgstr "If you can not go to this screen" + +#: ../../installation/install.rst:319 +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 "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." + +#: ../../installation/install.rst:280 +msgid "If you have a GNU+Linux system, you can create your VyOS bootable USB stick with with the ``dd`` command:" +msgstr "If you have a GNU+Linux system, you can create your VyOS bootable USB stick with with the ``dd`` command:" + +#: ../../installation/image.rst:114 +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 "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." + +#: ../../installation/update.rst:33 +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 "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." + +#: ../../installation/image.rst:99 +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 "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:" + +#: ../../installation/cloud/azure.rst:63 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:26 +msgid "If you want to get additional ethernet ports or even 10GE connectivity the following optional parts will be required:" +msgstr "If you want to get additional ethernet ports or even 10GE connectivity the following optional parts will be required:" + +#: ../../installation/image.rst:5 +msgid "Image Management" +msgstr "Image Management" + +#: ../../installation/virtual/gns3.rst:90 +msgid "In **Category** select in which group you want to find your VM." +msgstr "In **Category** select in which group you want to find your VM." + +#: ../../installation/install.rst:231 +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 "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." + +#: ../../installation/cloud/gcp.rst:20 +msgid "In name \"vyos@mypc\" The first value must be \"**vyos**\". Because default user is vyos and google api uses this option." +msgstr "In name \"vyos@mypc\" The first value must be \"**vyos**\". Because default user is vyos and google api uses this option." + +#: ../../installation/install.rst:354 +msgid "In order to proceed with a permanent installation:" +msgstr "In order to proceed with a permanent installation:" + +#: ../../installation/virtual/gns3.rst:114 +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 "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." + +#: ../../installation/virtual/gns3.rst:85 +msgid "In the **General settings** tab of your **QEMU VM template configuration**, do the following:" +msgstr "In the **General settings** tab of your **QEMU VM template configuration**, do the following:" + +#: ../../installation/virtual/gns3.rst:108 +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 "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)**." + +#: ../../installation/install.rst:491 +msgid "In the example we configured our existent VyOS as the TFTP server too:" +msgstr "In the example we configured our existent VyOS as the TFTP server too:" + +#: ../../installation/install.rst:454 +msgid "In this example we configured an existent VyOS as the DHCP server:" +msgstr "In this example we configured an existent VyOS as the DHCP server:" + +#: ../../installation/vyos-on-baremetal.rst:410 +msgid "Install VyOS:" +msgstr "Install VyOS:" + +#: ../../installation/install.rst:5 +#: ../../installation/vyos-on-baremetal.rst:352 +msgid "Installation" +msgstr "Installation" + +#: ../../installation/index.rst:3 +msgid "Installation and Image Management" +msgstr "Installation and Image Management" + +#: ../../installation/install.rst:594 +msgid "Installation can then continue as outlined above." +msgstr "Installation can then continue as outlined above." + +#: ../../installation/vyos-on-baremetal.rst:224 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:118 +msgid "Intel Corporation AX200 mini-PCIe WiFi module, only supported in mPCIe slot 1. (see :ref:`wireless-interface-intel-ax200`)" +msgstr "Intel Corporation AX200 mini-PCIe WiFi module, only supported in mPCIe slot 1. (see :ref:`wireless-interface-intel-ax200`)" + +#: ../../installation/install.rst:15 +msgid "Intended Use" +msgstr "Intended Use" + +#: ../../installation/install.rst:29 +msgid "Irregularly until EPA comes out" +msgstr "Irregularly until EPA comes out" + +#: ../../installation/install.rst:33 +msgid "Irregularly until LTS comes out" +msgstr "Irregularly until LTS comes out" + +#: ../../installation/install.rst:110 +msgid "It can be retrieved directly from a key server:" +msgstr "It can be retrieved directly from a key server:" + +#: ../../installation/virtual/vmware.rst:31 +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 "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." + +#: ../../installation/install.rst:235 +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 "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." + +#: ../../installation/install.rst:575 +msgid "Known Issues" +msgstr "Known Issues" + +#: ../../installation/install.rst:92 +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 "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." + +#: ../../installation/install.rst:29 +msgid "Labs, small offices and non-critical production systems backed by a high-availability setup." +msgstr "Labs, small offices and non-critical production systems backed by a high-availability setup." + +#: ../../installation/install.rst:37 +msgid "Large-scale enterprise networks, internet service providers, critical production environments that call for minimum downtime." +msgstr "Large-scale enterprise networks, internet service providers, critical production environments that call for minimum downtime." + +#: ../../installation/vyos-on-baremetal.rst:32 +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 "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)." + +#: ../../installation/virtual/libvirt.rst:7 +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 "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." + +#: ../../installation/image.rst:33 +msgid "List all available system images which can be booted on the current system." +msgstr "List all available system images which can be booted on the current system." + +#: ../../installation/install.rst:267 +msgid "Live installation" +msgstr "Live installation" + +#: ../../installation/install.rst:356 +msgid "Log into the VyOS live system (use the default credentials: vyos, vyos)" +msgstr "Log into the VyOS live system (use the default credentials: vyos, vyos)" + +#: ../../installation/install.rst:555 +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 "Make sure the available directories and files in both TFTP and HTTP server have the right permissions to be accessed from the booting clients." + +#: ../../installation/virtual/vmware.rst:18 +msgid "Memory Contention Considerations" +msgstr "Memory Contention Considerations" + +#: ../../installation/virtual/docker.rst:20 +msgid "Method 1: Create a docker network with IPv6 support" +msgstr "Method 1: Create a docker network with IPv6 support" + +#: ../../installation/virtual/docker.rst:29 +msgid "Method 2: Add IPv6 support to the docker daemon" +msgstr "Method 2: Add IPv6 support to the docker daemon" + +#: ../../installation/migrate-from-vyatta.rst:4 +msgid "Migrate from Vyatta Core" +msgstr "Migrate from Vyatta Core" + +#: ../../installation/install.rst:214 +msgid "Minisign verification" +msgstr "Minisign verification" + +#: ../../installation/virtual/libvirt.rst:148 +#: ../../installation/virtual/libvirt.rst:184 +msgid "Name of VM and network selection" +msgstr "Name of VM and network selection" + +#: ../../installation/update.rst:6 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:99 +msgid "Next add the VyOS image." +msgstr "Next add the VyOS image." + +#: ../../installation/install.rst:33 +msgid "Non-critical production environments, preparing for the LTS release." +msgstr "Non-critical production environments, preparing for the LTS release." + +#: ../../installation/install.rst:68 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:166 +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 "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." + +#: ../../installation/virtual/gns3.rst:78 +msgid "Now the VM settings have to be edited." +msgstr "Now the VM settings have to be edited." + +#: ../../installation/install.rst:347 +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 "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)." + +#: ../../installation/cloud/gcp.rst:35 +msgid "On marketplace search \"VyOS\"" +msgstr "On marketplace search \"VyOS\"" + +#: ../../installation/cloud/aws.rst:14 +msgid "On the marketplace search \"VyOS\"" +msgstr "On the marketplace search \"VyOS\"" + +#: ../../installation/cloud/azure.rst:17 +msgid "On the marketplace search ``VyOS`` and choose the appropriate subscription" +msgstr "On the marketplace search ``VyOS`` and choose the appropriate subscription" + +#: ../../installation/install.rst:315 +msgid "Once VyOS is completely loaded, enter the default credentials (login: vyos, password: vyos)." +msgstr "Once VyOS is completely loaded, enter the default credentials (login: vyos, password: vyos)." + +#: ../../installation/install.rst:309 +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 "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." + +#: ../../installation/virtual/proxmox.rst:46 +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 "Once booted into the live system, type ``install image`` into the command line and follow the prompts to install VyOS to the virtual drive." + +#: ../../installation/install.rst:569 +msgid "Once finished you will be able to proceed with the ``install image`` command as in a regular VyOS installation." +msgstr "Once finished you will be able to proceed with the ``install image`` command as in a regular VyOS installation." + +#: ../../installation/vyos-on-baremetal.rst:211 +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 "Once you ``commit`` the above changes access to the serial interface is lost until you set your terminal emulator to 115200 8N1 again." + +#: ../../installation/update.rst:11 +msgid "Only LTS releases are PGP-signed." +msgstr "Only LTS releases are PGP-signed." + +#: ../../installation/cloud/gcp.rst:24 +msgid "Open GCP console and navigate to the menu **Metadata**. Choose **SSH Keys** and click ``edit``." +msgstr "Open GCP console and navigate to the menu **Metadata**. Choose **SSH Keys** and click ``edit``." + +#: ../../installation/virtual/libvirt.rst:129 +#: ../../installation/virtual/libvirt.rst:168 +msgid "Open :abbr:`VMM (Virtual Machine Manager)` and Create a new :abbr:`VM (Virtual Machine)`" +msgstr "Open :abbr:`VMM (Virtual Machine Manager)` and Create a new :abbr:`VM (Virtual Machine)`" + +#: ../../installation/virtual/gns3.rst:133 +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 "Open a console. The console should show the system booting. It will ask for the login credentials, you are at the VyOS live system." + +#: ../../installation/virtual/libvirt.rst:107 +msgid "Open a secondary/parallel session and use this command to reboot the VM:" +msgstr "Open a secondary/parallel session and use this command to reboot the VM:" + +#: ../../installation/install.rst:283 +msgid "Open your terminal emulator." +msgstr "Open your terminal emulator." + +#: ../../installation/vyos-on-baremetal.rst:25 +msgid "Optional (10GE)" +msgstr "Optional (10GE)" + +#: ../../installation/virtual/proxmox.rst:24 +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 "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`." + +#: ../../installation/install.rst:118 +msgid "Or from the following block:" +msgstr "Or from the following block:" + +#: ../../installation/install.rst:114 +msgid "Or it can be accessed via a web browser:" +msgstr "Or it can be accessed via a web browser:" + +#: ../../installation/cloud/oracel.rst:3 +msgid "Oracle" +msgstr "Oracle" + +#: ../../installation/vyos-on-baremetal.rst:80 +msgid "PC Engines APU4" +msgstr "PC Engines APU4" + +#: ../../installation/install.rst:427 +msgid "PXE Boot" +msgstr "PXE Boot" + +#: ../../installation/vyos-on-baremetal.rst:342 +msgid "Partaker i5" +msgstr "Partaker i5" + +#: ../../installation/install.rst:332 +msgid "Permanent installation" +msgstr "Permanent installation" + +#: ../../installation/vyos-on-baremetal.rst:38 +#: ../../installation/vyos-on-baremetal.rst:234 +msgid "Pictures" +msgstr "Pictures" + +#: ../../installation/vyos-on-baremetal.rst:355 +msgid "Plug in VGA, power, USB keyboard, and USB drive" +msgstr "Plug in VGA, power, USB keyboard, and USB drive" + +#: ../../installation/install.rst:218 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:324 +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 "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." + +#: ../../installation/install.rst:312 +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 "Power the computer on, making sure it boots from the USB drive (you might need to select booting device or change booting settings)." + +#: ../../installation/virtual/proxmox.rst:38 +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 "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." + +#: ../../installation/install.rst:100 +msgid "Preparing for the verification" +msgstr "Preparing for the verification" + +#: ../../installation/vyos-on-baremetal.rst:356 +msgid "Press \"SW\" button on the front (this is the power button; I don't know what \"SW\" is supposed to mean)." +msgstr "Press \"SW\" button on the front (this is the power button; I don't know what \"SW\" is supposed to mean)." + +#: ../../installation/virtual/proxmox.rst:7 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:291 +msgid "Qotom Q355G4" +msgstr "Qotom Q355G4" + +#: ../../installation/vyos-on-baremetal.rst:240 +msgid "Rack Mount" +msgstr "Rack Mount" + +#: ../../installation/install.rst:29 +msgid "Rather stable. All development focuses on testing and hunting down remaining bugs following the feature freeze." +msgstr "Rather stable. All development focuses on testing and hunting down remaining bugs following the feature freeze." + +#: ../../installation/vyos-on-baremetal.rst:404 +msgid "Reboot into BIOS, Chipset > South Bridge > USB Configuration:" +msgstr "Reboot into BIOS, Chipset > South Bridge > USB Configuration:" + +#: ../../installation/install.rst:416 +msgid "Reboot the system." +msgstr "Reboot the system." + +#: ../../installation/virtual/proxmox.rst:48 +msgid "Reboot the virtual machine using the GUI or ``qm reboot 200``." +msgstr "Reboot the virtual machine using the GUI or ``qm reboot 200``." + +#: ../../installation/vyos-on-baremetal.rst:114 +msgid "Refer to :ref:`wireless-interface` for additional information, below listed modules have been tested successfully on this Hardware platform:" +msgstr "Refer to :ref:`wireless-interface` for additional information, below listed modules have been tested successfully on this Hardware platform:" + +#: ../../installation/vyos-on-baremetal.rst:124 +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 "Refer to :ref:`wwan-interface` for additional information, below listed modules have been tested successfully on this Hardware platform using VyOS 1.3 (equuleus):" + +#: ../../installation/cloud/aws.rst:99 +#: ../../installation/cloud/azure.rst:71 +#: ../../installation/cloud/gcp.rst:57 +#: ../../installation/cloud/oracel.rst:7 +#: ../../installation/virtual/eve-ng.rst:6 +#: ../../installation/virtual/vmware.rst:40 +msgid "References" +msgstr "References" + +#: ../../installation/install.rst:55 +msgid "Registered Subscribers" +msgstr "Registered Subscribers" + +#: ../../installation/install.rst:57 +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 "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." + +#: ../../installation/install.rst:15 +msgid "Release Cycle" +msgstr "Release Cycle" + +#: ../../installation/install.rst:15 +msgid "Release Type" +msgstr "Release Type" + +#: ../../installation/virtual/docker.rst:41 +msgid "Reload the docker configuration." +msgstr "Reload the docker configuration." + +#: ../../installation/virtual/gns3.rst:15 +msgid "Requirements" +msgstr "Requirements" + +#: ../../installation/cloud/aws.rst:69 +msgid "Retreive an existing CloudWatch Agent configuration from the :abbr:`SSM (Systems Manager)` Parameter Store." +msgstr "Retreive an existing CloudWatch Agent configuration from the :abbr:`SSM (Systems Manager)` Parameter Store." + +#: ../../installation/install.rst:74 +msgid "Rolling Release" +msgstr "Rolling Release" + +#: ../../installation/install.rst:79 +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 "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!" + +#: ../../installation/cloud/aws.rst:90 +msgid "Run Cloudwatch configuration wizard." +msgstr "Run Cloudwatch configuration wizard." + +#: ../../installation/install.rst:359 +msgid "Run the ``install image`` command and follow the wizard:" +msgstr "Run the ``install image`` command and follow the wizard:" + +#: ../../installation/cloud/index.rst:3 +msgid "Running VyOS in Cloud Environments" +msgstr "Running VyOS in Cloud Environments" + +#: ../../installation/virtual/index.rst:3 +msgid "Running VyOS in Virtual Environments" +msgstr "Running VyOS in Virtual Environments" + +#: ../../installation/virtual/docker.rst:5 +msgid "Running in Docker Container" +msgstr "Running in Docker Container" + +#: ../../installation/vyos-on-baremetal.rst:5 +msgid "Running on Bare Metal" +msgstr "Running on Bare Metal" + +#: ../../installation/virtual/gns3.rst:5 +msgid "Running on GNS3" +msgstr "Running on GNS3" + +#: ../../installation/virtual/libvirt.rst:5 +msgid "Running on Libvirt Qemu/KVM" +msgstr "Running on Libvirt Qemu/KVM" + +#: ../../installation/virtual/proxmox.rst:5 +msgid "Running on Proxmox" +msgstr "Running on Proxmox" + +#: ../../installation/virtual/vmware.rst:4 +msgid "Running on VMware ESXi" +msgstr "Running on VMware ESXi" + +#: ../../installation/vyos-on-baremetal.rst:399 +msgid "Save, reboot and change serial speed to 9600 on your client." +msgstr "Save, reboot and change serial speed to 9600 on your client." + +#: ../../installation/virtual/gns3.rst:55 +msgid "Select **New image** for the base disk image of your VM and click ``Create``." +msgstr "Select **New image** for the base disk image of your VM and click ``Create``." + +#: ../../installation/virtual/gns3.rst:38 +msgid "Select **Quemu VMs** and then click on the ``New`` button." +msgstr "Select **Quemu VMs** and then click on the ``New`` button." + +#: ../../installation/virtual/gns3.rst:46 +msgid "Select **qemu-system-x86_64** as Quemu binary, then **512MB** of RAM and click ``Next``." +msgstr "Select **qemu-system-x86_64** as Quemu binary, then **512MB** of RAM and click ``Next``." + +#: ../../installation/virtual/gns3.rst:51 +msgid "Select **telnet** as your console type and click ``Next``." +msgstr "Select **telnet** as your console type and click ``Next``." + +#: ../../installation/cloud/aws.rst:37 +msgid "Select SSH key pair and click ``Launch Instances``" +msgstr "Select SSH key pair and click ``Launch Instances``" + +#: ../../installation/image.rst:105 +msgid "Select the default boot image which will be started on the next boot of the system." +msgstr "Select the default boot image which will be started on the next boot of the system." + +#: ../../installation/cloud/azure.rst:66 +msgid "Serial Console" +msgstr "Serial Console" + +#: ../../installation/virtual/gns3.rst:91 +msgid "Set the **Boot priority** to **CD/DVD-ROM**." +msgstr "Set the **Boot priority** to **CD/DVD-ROM**." + +#: ../../installation/virtual/gns3.rst:69 +msgid "Set the disk size to 2000 MiB, and click ``Finish`` to end the **Quemu image creator**." +msgstr "Set the disk size to 2000 MiB, and click ``Finish`` to end the **Quemu image creator**." + +#: ../../installation/virtual/gns3.rst:165 +msgid "Set the number of required network adapters, for example **4**." +msgstr "Set the number of required network adapters, for example **4**." + +#: ../../installation/vyos-on-baremetal.rst:14 +#: ../../installation/vyos-on-baremetal.rst:99 +msgid "Shopping Cart" +msgstr "Shopping Cart" + +#: ../../installation/image.rst:70 +msgid "Show current system image version." +msgstr "Show current system image version." + +#: ../../installation/vyos-on-baremetal.rst:128 +msgid "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7304 miniPCIe card (LTE)" + +#: ../../installation/vyos-on-baremetal.rst:129 +msgid "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7430 miniPCIe card (LTE)" + +#: ../../installation/vyos-on-baremetal.rst:130 +msgid "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7455 miniPCIe card (LTE)" + +#: ../../installation/vyos-on-baremetal.rst:131 +msgid "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" +msgstr "Sierra Wireless AirPrime MC7710 miniPCIe card (LTE)" + +#: ../../installation/vyos-on-baremetal.rst:228 +msgid "Simply proceed with a regular image installation as described in :ref:`installation`." +msgstr "Simply proceed with a regular image installation as described in :ref:`installation`." + +#: ../../installation/vyos-on-baremetal.rst:401 +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 "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." + +#: ../../installation/virtual/gns3.rst:7 +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 "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." + +#: ../../installation/virtual/gns3.rst:132 +msgid "Start the VM." +msgstr "Start the VM." + +#: ../../installation/virtual/proxmox.rst:44 +msgid "Start the VM using the command ``qm start 200`` or using the start button located in the proxmox GUI." +msgstr "Start the VM using the command ``qm start 200`` or using the start button located in the proxmox GUI." + +#: ../../installation/virtual/proxmox.rst:30 +msgid "Start the virtual machine in the proxmox GUI or CLI using ``qm start 200``." +msgstr "Start the virtual machine in the proxmox GUI or CLI using ``qm start 200``." + +#: ../../installation/virtual/libvirt.rst:100 +msgid "Stayed in this stage. This is because the KVM console is chosen as the default boot option." +msgstr "Stayed in this stage. This is because the KVM console is chosen as the default boot option." + +#: ../../installation/install.rst:446 +msgid "Step 1: DHCP" +msgstr "Step 1: DHCP" + +#: ../../installation/install.rst:474 +msgid "Step 2: TFTP" +msgstr "Step 2: TFTP" + +#: ../../installation/install.rst:531 +msgid "Step 3: HTTP" +msgstr "Step 3: HTTP" + +#: ../../installation/install.rst:175 +msgid "Store the key in a new text file and import it into GPG via: ``gpg --import file_with_the_public_key``" +msgstr "Store the key in a new text file and import it into GPG via: ``gpg --import file_with_the_public_key``" + +#: ../../installation/install.rst:37 +msgid "Subscribers, contributors, non-profits, emergency services, academic institutions" +msgstr "Subscribers, contributors, non-profits, emergency services, academic institutions" + +#: ../../installation/vyos-on-baremetal.rst:8 +msgid "Supermicro A2SDi (Atom C3000)" +msgstr "Supermicro A2SDi (Atom C3000)" + +#: ../../installation/image.rst:97 +msgid "System rollback" +msgstr "System rollback" + +#: ../../installation/vyos-on-baremetal.rst:396 +msgid "Terminal Type : VT100+" +msgstr "Terminal Type : VT100+" + +#: ../../installation/virtual/gns3.rst:144 +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 "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." + +#: ../../installation/install.rst:452 +msgid "The *bootfile name* (DHCP option 67), which is *pxelinux.0*" +msgstr "The *bootfile name* (DHCP option 67), which is *pxelinux.0*" + +#: ../../installation/install.rst:479 +msgid "The *ldlinux.c32* file from the Syslinux distribution" +msgstr "The *ldlinux.c32* file from the Syslinux distribution" + +#: ../../installation/install.rst:478 +msgid "The *pxelinux.0* file from the Syslinux distribution" +msgstr "The *pxelinux.0* file from the Syslinux distribution" + +#: ../../installation/vyos-on-baremetal.rst:105 +msgid "The 19\" enclosure can accommodate up to two APU4 boards - there is a single and dual front cover." +msgstr "The 19\" enclosure can accommodate up to two APU4 boards - there is a single and dual front cover." + +#: ../../installation/vyos-on-baremetal.rst:187 +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 "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:" + +#: ../../installation/install.rst:451 +msgid "The TFTP server address (DHCP option 66). Sometimes referred as *boot server*" +msgstr "The TFTP server address (DHCP option 66). Sometimes referred as *boot server*" + +#: ../../installation/virtual/gns3.rst:174 +msgid "The VyOS VM is now ready to be deployed." +msgstr "The VyOS VM is now ready to be deployed." + +#: ../../installation/image.rst:7 +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 "The VyOS image-based installation is implemented by creating a directory for each image on the storage device selected during the install process." + +#: ../../installation/cloud/aws.rst:77 +msgid "The VyOS platform-specific scripts feature is under development. Thus, this step should be repeated manually after changing system image (:doc:`/installation/update`)" +msgstr "The VyOS platform-specific scripts feature is under development. Thus, this step should be repeated manually after changing system image (:doc:`/installation/update`)" + +#: ../../installation/update.rst:20 +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 "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." + +#: ../../installation/cloud/aws.rst:67 +msgid "The amazon-cloudwatch-agent package is normally included in VyOS 1.3.3+ and 1.4+" +msgstr "The amazon-cloudwatch-agent package is normally included in VyOS 1.3.3+ and 1.4+" + +#: ../../installation/vyos-on-baremetal.rst:94 +msgid "The board can be powered via 12V from the front or via a 5V onboard connector." +msgstr "The board can be powered via 12V from the front or via a 5V onboard connector." + +#: ../../installation/vyos-on-baremetal.rst:314 +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 "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." + +#: ../../installation/virtual/proxmox.rst:15 +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 "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`." + +#: ../../installation/virtual/libvirt.rst:55 +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 "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``" + +#: ../../installation/install.rst:326 +msgid "The default username and password for the live system is *vyos*." +msgstr "The default username and password for the live system is *vyos*." + +#: ../../installation/image.rst:10 +msgid "The directory structure of the boot device:" +msgstr "The directory structure of the boot device:" + +#: ../../installation/virtual/gns3.rst:17 +msgid "The following items are required:" +msgstr "The following items are required:" + +#: ../../installation/install.rst:84 +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 "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" + +#: ../../installation/image.rst:19 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:180 +msgid "The image will be loaded and the last lines you will get will be:" +msgstr "The image will be loaded and the last lines you will get will be:" + +#: ../../installation/install.rst:178 +msgid "The import can be verified with:" +msgstr "The import can be verified with:" + +#: ../../installation/install.rst:483 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:293 +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 "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." + +#: ../../installation/install.rst:480 +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 "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." + +#: ../../installation/install.rst:47 +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 "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." + +#: ../../installation/update.rst:76 +msgid "The most up-do-date Rolling Release for AMD64 can be accessed using the following URL:" +msgstr "The most up-do-date Rolling Release for AMD64 can be accessed using the following URL:" + +#: ../../installation/install.rst:107 +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 "The official VyOS public key can be retrieved in a number of ways. Skip to :ref:`gpg-verification` if the key is already present." + +#: ../../installation/install.rst:197 +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 "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." + +#: ../../installation/virtual/libvirt.rst:116 +msgid "The system is fully operational." +msgstr "The system is fully operational." + +#: ../../installation/virtual/libvirt.rst:120 +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 "The virt-manager application is a desktop user interface for managing virtual machines through libvirt. On the linux open :abbr:`VMM (Virtual Machine Manager)`." + +#: ../../installation/install.rst:587 +msgid "The workaround is to type `e` when the boot menu appears and edit the GRUB boot options. Specifically, remove the:" +msgstr "The workaround is to type `e` when the boot menu appears and edit the GRUB boot options. Specifically, remove the:" + +#: ../../installation/vyos-on-baremetal.rst:421 +msgid "Then VyOS should boot and you can perform the ``install image``" +msgstr "Then VyOS should boot and you can perform the ``install image``" + +#: ../../installation/virtual/libvirt.rst:113 +msgid "Then go to the first session where you opened the console. Select ``VyOS 1.4.x for QEMU (Serial console)`` and press ``Enter``" +msgstr "Then go to the first session where you opened the console. Select ``VyOS 1.4.x for QEMU (Serial console)`` and press ``Enter``" + +#: ../../installation/image.rst:108 +msgid "Then reboot the system." +msgstr "Then reboot the system." + +#: ../../installation/virtual/libvirt.rst:152 +#: ../../installation/virtual/libvirt.rst:188 +msgid "Then you will be taken to the console." +msgstr "Then you will be taken to the console." + +#: ../../installation/vyos-on-baremetal.rst:328 +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 "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)." + +#: ../../installation/vyos-on-baremetal.rst:306 +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 "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)." + +#: ../../installation/virtual/vmware.rst:13 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:101 +msgid "This example uses VyOS 1.0.0, however, it's better to install the latest release." +msgstr "This example uses VyOS 1.0.0, however, it's better to install the latest release." + +#: ../../installation/vyos-on-baremetal.rst:85 +msgid "This guide was developed using an APU4C4 board with the following specs:" +msgstr "This guide was developed using an APU4C4 board with the following specs:" + +#: ../../installation/virtual/gns3.rst:11 +msgid "This guide will provide the necessary steps for installing and setting up VyOS on GNS3." +msgstr "This guide will provide the necessary steps for installing and setting up VyOS on GNS3." + +#: ../../installation/install.rst:577 +msgid "This is a list of known issues that can arise during installation." +msgstr "This is a list of known issues that can arise during installation." + +#: ../../installation/vyos-on-baremetal.rst:374 +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 "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" + +#: ../../installation/image.rst:25 +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 "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." + +#: ../../installation/cloud/aws.rst:75 +msgid "This step also enables systemd service and runs it." +msgstr "This step also enables systemd service and runs it." + +#: ../../installation/install.rst:96 +msgid "This subsection only applies to LTS images, for Rolling images please jump to :ref:`live_installation`." +msgstr "This subsection only applies to LTS images, for Rolling images please jump to :ref:`live_installation`." + +#: ../../installation/cloud/gcp.rst:8 +msgid "To deploy VyOS on GCP (Google Cloud Platform)" +msgstr "To deploy VyOS on GCP (Google Cloud Platform)" + +#: ../../installation/virtual/gns3.rst:153 +msgid "To turn the template into a working VyOS machine, further steps are necessary as outlined below:" +msgstr "To turn the template into a working VyOS machine, further steps are necessary as outlined below:" + +#: ../../installation/cloud/aws.rst:55 +msgid "To use Amazon CloudWatch Agent, configure it within the Amazon SSM Parameter Store. If you don't have a configuration yet, do :ref:`configuration_creation`." +msgstr "To use Amazon CloudWatch Agent, configure it within the Amazon SSM Parameter Store. If you don't have a configuration yet, do :ref:`configuration_creation`." + +#: ../../installation/install.rst:248 +msgid "To verify a VyOS image starting off with VyOS 1.3.0-rc6 you can run:" +msgstr "To verify a VyOS image starting off with VyOS 1.3.0-rc6 you can run:" + +#: ../../installation/install.rst:337 +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 "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." + +#: ../../installation/install.rst:288 +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 "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." + +#: ../../installation/update.rst:4 +msgid "Update VyOS" +msgstr "Update VyOS" + +#: ../../installation/migrate-from-vyatta.rst:26 +msgid "Upgrade procedure" +msgstr "Upgrade procedure" + +#: ../../installation/migrate-from-vyatta.rst:156 +msgid "Upon reboot, you should have a working installation of VyOS." +msgstr "Upon reboot, you should have a working installation of VyOS." + +#: ../../installation/virtual/gns3.rst:60 +msgid "Use the defaults in the **Binary and format** window and click ``Next``." +msgstr "Use the defaults in the **Binary and format** window and click ``Next``." + +#: ../../installation/virtual/gns3.rst:65 +msgid "Use the defaults in the **Qcow2 options** window and click ``Next``." +msgstr "Use the defaults in the **Qcow2 options** window and click ``Next``." + +#: ../../installation/vyos-on-baremetal.rst:205 +msgid "Use the following command to adjust the :ref:`serial-console` settings:" +msgstr "Use the following command to adjust the :ref:`serial-console` settings:" + +#: ../../installation/update.rst:16 +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 "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." + +#: ../../installation/virtual/proxmox.rst:45 +msgid "Using the proxmox webGUI, open the virtual console for your newly created vm. Login username/password is ``vyos/vyos``." +msgstr "Using the proxmox webGUI, open the virtual console for your newly created vm. Login username/password is ``vyos/vyos``." + +#: ../../installation/virtual/gns3.rst:28 +msgid "VM setup" +msgstr "VM setup" + +#: ../../installation/virtual/libvirt.rst:119 +msgid "Virt-manager" +msgstr "Virt-manager" + +#: ../../installation/virtual/proxmox.rst:54 +msgid "Visit https://www.proxmox.com/en/ for more information about the download and installation of this hypervisor." +msgstr "Visit https://www.proxmox.com/en/ for more information about the download and installation of this hypervisor." + +#: ../../installation/install.rst:272 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:135 +msgid "VyOS 1.2 (crux)" +msgstr "VyOS 1.2 (crux)" + +#: ../../installation/vyos-on-baremetal.rst:222 +msgid "VyOS 1.2 (rolling)" +msgstr "VyOS 1.2 (rolling)" + +#: ../../installation/migrate-from-vyatta.rst:6 +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 "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." + +#: ../../installation/install.rst:438 +msgid "VyOS ISO image to be installed (do not use images prior to VyOS 1.2.3)" +msgstr "VyOS ISO image to be installed (do not use images prior to VyOS 1.2.3)" + +#: ../../installation/virtual/gns3.rst:151 +msgid "VyOS VM configuration" +msgstr "VyOS VM configuration" + +#: ../../installation/image.rst:110 +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 "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." + +#: ../../installation/install.rst:429 +msgid "VyOS can also be installed through PXE. This is a more complex installation method that allows deploying VyOS through the network." +msgstr "VyOS can also be installed through PXE. This is a more complex installation method that allows deploying VyOS through the network." + +#: ../../installation/update.rst:29 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:263 +msgid "VyOS custom print" +msgstr "VyOS custom print" + +#: ../../installation/virtual/gns3.rst:128 +msgid "VyOS installation" +msgstr "VyOS installation" + +#: ../../installation/install.rst:7 +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 "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." + +#: ../../installation/virtual/docker.rst:15 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:15 +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 "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." + +#: ../../installation/migrate-from-vyatta.rst:13 +msgid "Vyatta Core releases from 6.5 to 6.6 should be 100% compatible." +msgstr "Vyatta Core releases from 6.5 to 6.6 should be 100% compatible." + +#: ../../installation/migrate-from-vyatta.rst:11 +msgid "Vyatta release compatibility" +msgstr "Vyatta release compatibility" + +#: ../../installation/vyos-on-baremetal.rst:122 +msgid "WWAN" +msgstr "WWAN" + +#: ../../installation/install.rst:306 +msgid "Wait until you get the outcome (bytes copied). Be patient, in some computers it might take more than one minute." +msgstr "Wait until you get the outcome (bytes copied). Be patient, in some computers it might take more than one minute." + +#: ../../installation/vyos-on-baremetal.rst:364 +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 "Warning the interface labels on my device are backwards; the left-most \"LAN4\" port is eth0 and the right-most \"LAN1\" port is eth3." + +#: ../../installation/install.rst:533 +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 "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." + +#: ../../installation/install.rst:437 +msgid "Webserver (HTTP) - optional, but we will use it to speed up installation" +msgstr "Webserver (HTTP) - optional, but we will use it to speed up installation" + +#: ../../installation/cloud/aws.rst:96 +msgid "When prompted, answer \"yes\" to the question \"Do you want to store the config in the SSM parameter store?\"." +msgstr "When prompted, answer \"yes\" to the question \"Do you want to store the config in the SSM parameter store?\"." + +#: ../../installation/virtual/vmware.rst:19 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:112 +msgid "WiFi" +msgstr "WiFi" + +#: ../../installation/install.rst:194 +msgid "With the public key imported, the signature for the desired image needs to be downloaded." +msgstr "With the public key imported, the signature for the desired image needs to be downloaded." + +#: ../../installation/vyos-on-baremetal.rst:354 +msgid "Write VyOS ISO to USB drive of some sort" +msgstr "Write VyOS ISO to USB drive of some sort" + +#: ../../installation/virtual/gns3.rst:42 +msgid "Write a name for your VM, for instance \"VyOS\", and click ``Next``." +msgstr "Write a name for your VM, for instance \"VyOS\", and click ``Next``." + +#: ../../installation/install.rst:296 +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 "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)." + +#: ../../installation/update.rst:38 +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 "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:" + +#: ../../installation/virtual/docker.rst:74 +msgid "You can execute ``docker stop vyos`` when you are finished with the container." +msgstr "You can execute ``docker stop vyos`` when you are finished with the container." + +#: ../../installation/migrate-from-vyatta.rst:158 +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 "You can go back to your Vyatta install using the ``set system image default-boot`` command and selecting the your previous Vyatta Core image." + +#: ../../installation/vyos-on-baremetal.rst:198 +msgid "You can now proceed with a regular image installation as described in :ref:`installation`." +msgstr "You can now proceed with a regular image installation as described in :ref:`installation`." + +#: ../../installation/migrate-from-vyatta.rst:28 +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 "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." + +#: ../../installation/vyos-on-baremetal.rst:377 +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 "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)." + +#: ../../installation/virtual/gns3.rst:105 +msgid "You probably will want to accept to copy the .iso file to your default image directory when you are asked." +msgstr "You probably will want to accept to copy the .iso file to your default image directory when you are asked." + +#: ../../installation/install.rst:423 +msgid "You will boot now into a permanent VyOS system." +msgstr "You will boot now into a permanent VyOS system." + +#: ../../installation/virtual/vmware.rst:9 +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 ".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`." + +#: ../../installation/virtual/gns3.rst:136 +msgid ":ref:`Install VyOS <installation>` as normal (that is, using the ``install image`` command)." +msgstr ":ref:`Install VyOS <installation>` as normal (that is, using the ``install image`` command)." + +#: ../../installation/install.rst:435 +msgid ":ref:`dhcp-server`" +msgstr ":ref:`dhcp-server`" + +#: ../../installation/install.rst:436 +msgid ":ref:`tftp-server`" +msgstr ":ref:`tftp-server`" + +#: ../../installation/install.rst:246 +msgid ":vytask:`T2108` switched the validation system to prefer minisign over GPG keys." +msgstr ":vytask:`T2108` switched the validation system to prefer minisign over GPG keys." + +#: ../../installation/vyos-on-baremetal.rst:349 +msgid "`Manufacturer product page <http://www.inctel.com.cn/product/detail/338.html>`_." +msgstr "`Manufacturer product page <http://www.inctel.com.cn/product/detail/338.html>`_." + +#: ../../installation/install.rst:112 +msgid "``gpg --recv-keys FD220285A0FE6D7E``" +msgstr "``gpg --recv-keys FD220285A0FE6D7E``" + +#: ../../installation/install.rst:590 +msgid "`console=ttyS0,115200`" +msgstr "`console=ttyS0,115200`" + +#: ../../installation/cloud/azure.rst:72 +msgid "https://azure.microsoft.com" +msgstr "https://azure.microsoft.com" + +#: ../../installation/cloud/aws.rst:100 +msgid "https://console.aws.amazon.com/" +msgstr "https://console.aws.amazon.com/" + +#: ../../installation/cloud/gcp.rst:58 +msgid "https://console.cloud.google.com/" +msgstr "https://console.cloud.google.com/" + +#: ../../installation/cloud/aws.rst:101 +msgid "https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/create-iam-roles-for-cloudwatch-agent.html" +msgstr "https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/create-iam-roles-for-cloudwatch-agent.html" + +#: ../../installation/cloud/aws.rst:102 +msgid "https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Agent-on-EC2-Instance-fleet.html" +msgstr "https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Agent-on-EC2-Instance-fleet.html" + +#: ../../installation/virtual/vmware.rst:44 +msgid "https://muralidba.blogspot.com/2018/03/how-does-linux-out-of-memory-oom-killer.html" +msgstr "https://muralidba.blogspot.com/2018/03/how-does-linux-out-of-memory-oom-killer.html" + +#: ../../installation/install.rst:116 +msgid "https://pgp.mit.edu/pks/lookup?op=get&search=0xFD220285A0FE6D7E" +msgstr "https://pgp.mit.edu/pks/lookup?op=get&search=0xFD220285A0FE6D7E" + +#: ../../installation/update.rst:79 +msgid "https://vyos.net/get/nightly-builds/" +msgstr "https://vyos.net/get/nightly-builds/" + +#: ../../installation/virtual/eve-ng.rst:8 +msgid "https://www.eve-ng.net/" +msgstr "https://www.eve-ng.net/" + +#: ../../installation/cloud/oracel.rst:8 +msgid "https://www.oracle.com/cloud/" +msgstr "https://www.oracle.com/cloud/" + +#: ../../installation/virtual/docker.rst:73 +msgid "ly-builds/releases/download/1.4-rolling-202308240020/vyos-1.4-rolling-202308240020-amd64.iso" +msgstr "ly-builds/releases/download/1.4-rolling-202308240020/vyos-1.4-rolling-202308240020-amd64.iso" + +#: ../../installation/install.rst:592 +msgid "option, and type CTRL-X to boot." +msgstr "option, and type CTRL-X to boot." diff --git a/docs/_locale/ja/introducing.pot b/docs/_locale/ja/introducing.pot new file mode 100644 index 00000000..cebfdaf6 --- /dev/null +++ b/docs/_locale/ja/introducing.pot @@ -0,0 +1,161 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../introducing/history.rst:134 +msgid "A business model comparable to that of Redis, rather than that of VyOS today." +msgstr "A business model comparable to that of Redis, rather than that of VyOS today." + +#: ../../introducing/history.rst:119 +msgid "A note on copyright" +msgstr "A note on copyright" + +#: ../../introducing/about.rst:5 +msgid "About" +msgstr "About" + +#: ../../introducing/history.rst:74 +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 "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." + +#: ../../introducing/history.rst:88 +msgid "As of 2022, Crux is still supported and maintained." +msgstr "As of 2022, Crux is still supported and maintained." + +#: ../../introducing/history.rst:104 +msgid "As of 2022, Equuleus is in the stable." +msgstr "As of 2022, Equuleus is in the stable." + +#: ../../introducing/history.rst:35 +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 "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." + +#: ../../introducing/history.rst:113 +msgid "Circinus (1.5)" +msgstr "Circinus (1.5)" + +#: ../../introducing/history.rst:115 +msgid "Circinus (the Compass) is the codename of the upcoming development branch, so there's no VyOS 1.5 yet." +msgstr "Circinus (the Compass) is the codename of the upcoming development branch, so there's no VyOS 1.5 yet." + +#: ../../introducing/history.rst:68 +msgid "Crux (1.2)" +msgstr "Crux (1.2)" + +#: ../../introducing/history.rst:70 +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 "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)." + +#: ../../introducing/history.rst:81 +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 "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." + +#: ../../introducing/history.rst:91 +msgid "Equuleus (1.3)" +msgstr "Equuleus (1.3)" + +#: ../../introducing/history.rst:97 +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 "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." + +#: ../../introducing/history.rst:133 +msgid "From the Sanskrit adjective \"Vyātta\" (व्यात्त), meaning opened." +msgstr "From the Sanskrit adjective \"Vyātta\" (व्यात्त), meaning opened." + +#: ../../introducing/history.rst:58 +msgid "Helium (1.1)" +msgstr "Helium (1.1)" + +#: ../../introducing/history.rst:60 +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 "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)." + +#: ../../introducing/history.rst:5 +msgid "History" +msgstr "History" + +#: ../../introducing/history.rst:49 +msgid "Hydrogen (1.0)" +msgstr "Hydrogen (1.0)" + +#: ../../introducing/history.rst:28 +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 "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." + +#: ../../introducing/history.rst:8 +msgid "In the beginning..." +msgstr "In the beginning..." + +#: ../../introducing/history.rst:22 +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 "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." + +#: ../../introducing/history.rst:40 +msgid "Major releases" +msgstr "Major releases" + +#: ../../introducing/history.rst:51 +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 "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." + +#: ../../introducing/history.rst:107 +msgid "Sagitta (1.4)" +msgstr "Sagitta (1.4)" + +#: ../../introducing/history.rst:109 +msgid "Sagitta (the Arrow) is the codename of the current development branch, so there's no VyOS 1.4 yet." +msgstr "Sagitta (the Arrow) is the codename of the current development branch, so there's no VyOS 1.4 yet." + +#: ../../introducing/history.rst:93 +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 "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." + +#: ../../introducing/about.rst:19 +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 "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." + +#: ../../introducing/history.rst:10 +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 "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. [*]_" + +#: ../../introducing/history.rst:136 +msgid "This is not unlike how Linus Torvalds owns the trademark \"Linux\"." +msgstr "This is not unlike how Linus Torvalds owns the trademark \"Linux\"." + +#: ../../introducing/history.rst:121 +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 "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." + +#: ../../introducing/about.rst:23 +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 "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." + +#: ../../introducing/about.rst:7 +msgid "VyOS is an open source network operating system based on Debian GNU/Linux." +msgstr "VyOS is an open source network operating system based on Debian GNU/Linux." + +#: ../../introducing/history.rst:42 +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 "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." + +#: ../../introducing/history.rst:42 +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 <https://en.wikipedia.org/wiki/IAU_designated_constellations_by_area>`_ designated constellations by solid angle area, starting from the smallest." +msgstr "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 <https://en.wikipedia.org/wiki/IAU_designated_constellations_by_area>`_ designated constellations by solid angle area, starting from the smallest." + +#: ../../introducing/about.rst:9 +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 "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." + +#: ../../introducing/history.rst:17 +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 "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." + +#: ../../introducing/about.rst:14 +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 "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)." diff --git a/docs/_locale/ja/operation.pot b/docs/_locale/ja/operation.pot new file mode 100644 index 00000000..0a11547c --- /dev/null +++ b/docs/_locale/ja/operation.pot @@ -0,0 +1,326 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../operation/raid.rst:154 +msgid "1 - Remove the failed disk from the RAID 1 set by issuing the following command:" +msgstr "1 - Remove the failed disk from the RAID 1 set by issuing the following command:" + +#: ../../operation/raid.rst:113 +msgid "1 - To break apart the current RAID 1 set, enter “No” at the prompt. The" +msgstr "1 - To break apart the current RAID 1 set, enter “No” at the prompt. The" + +#: ../../operation/raid.rst:71 +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 "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." + +#: ../../operation/raid.rst:162 +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 "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." + +#: ../../operation/raid.rst:123 +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 "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." + +#: ../../operation/raid.rst:79 +msgid "2 - To overwrite the old filesystem, enter “Yes”." +msgstr "2 - To overwrite the old filesystem, enter “Yes”." + +#: ../../operation/raid.rst:131 +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 "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." + +#: ../../operation/raid.rst:165 +msgid "3 - Replace the failed drive with a drive of the same size or larger." +msgstr "3 - Replace the failed drive with a drive of the same size or larger." + +#: ../../operation/raid.rst:81 +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 "3 - The system informs you that all data on both drives will be erased. You are prompted to confirm that you want to continue" + +#: ../../operation/raid.rst:88 +#: ../../operation/raid.rst:139 +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 "4 - Enter “Yes” at the prompt to retain the current VyOS configuration once installation is complete. Enter “No” to delete the current VyOS configuration." + +#: ../../operation/raid.rst:167 +msgid "4 - Format the new disk for RAID 1 by issuing the following command:" +msgstr "4 - Format the new disk for RAID 1 by issuing the following command:" + +#: ../../operation/raid.rst:174 +msgid "5-Add the replacement disk to the RAID 1 set by issuing the following command:" +msgstr "5-Add the replacement disk to the RAID 1 set by issuing the following command:" + +#: ../../operation/raid.rst:142 +msgid "5 - Continue with installation in the normal way." +msgstr "5 - Continue with installation in the normal way." + +#: ../../operation/raid.rst:96 +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 "5 - Enter “Yes” at the prompt to retain the current VyOS configuration once installation is complete. Enter “No” to delete the current VyOS configuration." + +#: ../../operation/raid.rst:99 +msgid "6 - Continue with installation in the normal way." +msgstr "6 - Continue with installation in the normal way." + +#: ../../operation/raid.rst:7 +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 "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:" + +#: ../../operation/raid.rst:40 +msgid "Before a permanent installation, VyOS runs a live installation" +msgstr "Before a permanent installation, VyOS runs a live installation" + +#: ../../operation/boot-options.rst:6 +msgid "Boot Options" +msgstr "Boot Options" + +#: ../../operation/raid.rst:43 +msgid "Configuration" +msgstr "Configuration" + +#: ../../operation/raid.rst:146 +msgid "Detecting and Replacing a Failed RAID 1 Disk" +msgstr "Detecting and Replacing a Failed RAID 1 Disk" + +#: ../../operation/raid.rst:21 +msgid "Detection and reporting of disk failure" +msgstr "Detection and reporting of disk failure" + +#: ../../operation/boot-options.rst:45 +msgid "Disable specific boot process steps" +msgstr "Disable specific boot process steps" + +#: ../../operation/boot-options.rst:56 +msgid "Do not initialize default firewall chains, renders any firewall configuration unusable." +msgstr "Do not initialize default firewall chains, renders any firewall configuration unusable." + +#: ../../operation/boot-options.rst:53 +msgid "Do not perform config migration." +msgstr "Do not perform config migration." + +#: ../../operation/raid.rst:61 +msgid "Empty 2+ Disk" +msgstr "Empty 2+ Disk" + +#: ../../operation/information.rst:34 +msgid "For additional details you can refer to https://vyos.dev/T2490." +msgstr "For additional details you can refer to https://vyos.dev/T2490." + +#: ../../operation/information.rst:14 +msgid "Hardware" +msgstr "Hardware" + +#: ../../operation/raid.rst:63 +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 "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." + +#: ../../operation/information.rst:40 +msgid "If a device is unplugged and re-plugged it will receive a new Port, Dev, If identification." +msgstr "If a device is unplugged and re-plugged it will receive a new Port, Dev, If identification." + +#: ../../operation/raid.rst:57 +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 "If you do not want to configure RAID 1 mirroring, enter “No” at the prompt and continue with installation in the normal way." + +#: ../../operation/information.rst:21 +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 "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`." + +#: ../../operation/information.rst:7 +msgid "Information" +msgstr "Information" + +#: ../../operation/raid.rst:30 +msgid "Installation Implications" +msgstr "Installation Implications" + +#: ../../operation/raid.rst:183 +msgid "Operation" +msgstr "Operation" + +#: ../../operation/index.rst:3 +msgid "Operation Mode" +msgstr "Operation Mode" + +#: ../../operation/password-recovery.rst:5 +msgid "Password Recovery" +msgstr "Password Recovery" + +#: ../../operation/raid.rst:103 +msgid "Present RAID-1" +msgstr "Present RAID-1" + +#: ../../operation/raid.rst:5 +msgid "RAID-1" +msgstr "RAID-1" + +#: ../../operation/information.rst:74 +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 "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." + +#: ../../operation/information.rst:38 +msgid "Retrieve a tree like representation of all connected USB devices." +msgstr "Retrieve a tree like representation of all connected USB devices." + +#: ../../operation/information.rst:108 +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 "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." + +#: ../../operation/information.rst:146 +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 "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." + +#: ../../operation/information.rst:137 +msgid "Return version number of the Linux Kernel used in this release." +msgstr "Return version number of the Linux Kernel used in this release." + +#: ../../operation/raid.rst:46 +msgid "Single disk, install as normal" +msgstr "Single disk, install as normal" + +#: ../../operation/boot-options.rst:26 +msgid "Specify custom config file" +msgstr "Specify custom config file" + +#: ../../operation/boot-options.rst:28 +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 "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." + +#: ../../operation/raid.rst:148 +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 "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." + +#: ../../operation/raid.rst:32 +msgid "The VyOS systems installation utility provides several options for installing to a RAID 1 set. You can:" +msgstr "The VyOS systems installation utility provides several options for installing to a RAID 1 set. You can:" + +#: ../../operation/raid.rst:23 +msgid "The ability to boot the system with one failed disk" +msgstr "The ability to boot the system with one failed disk" + +#: ../../operation/raid.rst:22 +msgid "The ability to maintain system operation with one failed disk" +msgstr "The ability to maintain system operation with one failed disk" + +#: ../../operation/raid.rst:25 +msgid "The ability to monitor the status of remirroring" +msgstr "The ability to monitor the status of remirroring" + +#: ../../operation/raid.rst:24 +msgid "The ability to replace a failed disk and initiate re-mirroring" +msgstr "The ability to replace a failed disk and initiate re-mirroring" + +#: ../../operation/password-recovery.rst:14 +msgid "The stand-alone user-password recovery tool starts running and prompts you to reset the local system user password." +msgstr "The stand-alone user-password recovery tool starts running and prompts you to reset the local system user password." + +#: ../../operation/boot-options.rst:47 +msgid "These options disable some boot steps. Make sure you understand the :ref:`boot process <boot-steps>` well before using them!" +msgstr "These options disable some boot steps. Make sure you understand the :ref:`boot process <boot-steps>` well before using them!" + +#: ../../operation/raid.rst:196 +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 "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)." + +#: ../../operation/boot-options.rst:8 +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 "This function may be highly disruptive. It may cause major service interruption, so make sure you really need it and verify your input carefully." + +#: ../../operation/raid.rst:185 +msgid "This part introduces how to add a disk partition to a RAID-1 set initiates mirror synchronization, check and display information." +msgstr "This part introduces how to add a disk partition to a RAID-1 set initiates mirror synchronization, check and display information." + +#: ../../operation/boot-options.rst:37 +msgid "To load the *factory default* config, use:" +msgstr "To load the *factory default* config, use:" + +#: ../../operation/information.rst:28 +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 "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." + +#: ../../operation/raid.rst:152 +msgid "To replace a bad disk within a RAID 1 set, perform the following steps:" +msgstr "To replace a bad disk within a RAID 1 set, perform the following steps:" + +#: ../../operation/information.rst:19 +msgid "USB" +msgstr "USB" + +#: ../../operation/raid.rst:38 +msgid "Use a previously-created RAID 1 set." +msgstr "Use a previously-created RAID 1 set." + +#: ../../operation/raid.rst:35 +msgid "Use the install system to create the RAID 1 set" +msgstr "Use the install system to create the RAID 1 set" + +#: ../../operation/raid.rst:36 +msgid "Use the underlying Linux commands to create a RAID 1 set before running the install system command." +msgstr "Use the underlying Linux commands to create a RAID 1 set before running the install system command." + +#: ../../operation/raid.rst:190 +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 "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." + +#: ../../operation/raid.rst:232 +msgid "Use this command to display the formatting of a hard disk." +msgstr "Use this command to display the formatting of a hard disk." + +#: ../../operation/password-recovery.rst:7 +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 "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.”" + +#: ../../operation/information.rst:104 +msgid "Version" +msgstr "Version" + +#: ../../operation/information.rst:9 +msgid "VyOS features a rich set of operational level commands to retrieve arbitrary information about your running system." +msgstr "VyOS features a rich set of operational level commands to retrieve arbitrary information about your running system." + +#: ../../operation/boot-options.rst:14 +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 "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." + +#: ../../operation/raid.rst:105 +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 "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:" + +#: ../../operation/raid.rst:48 +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 "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." + +#: ../../operation/raid.rst:115 +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 "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:" + +#: ../../operation/boot-options.rst:54 +msgid "no-vyos-firewall" +msgstr "no-vyos-firewall" + +#: ../../operation/boot-options.rst:51 +msgid "no-vyos-migrate" +msgstr "no-vyos-migrate" + +#: ../../operation/raid.rst:201 +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 "shows output for show raid md0 as sdb1 is being added to the RAID 1 set and is in the process of being resynchronized." + +#: ../../operation/raid.rst:159 +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 "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)." + +#: ../../operation/raid.rst:178 +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 "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)." + +#: ../../operation/raid.rst:171 +msgid "where disk-device1 is the replacement disk (for example, sdb) and disk-device2 is the existing healthy disk (for example, sda)." +msgstr "where disk-device1 is the replacement disk (for example, sdb) and disk-device2 is the existing healthy disk (for example, sda)." diff --git a/docs/_locale/ja/quick-start.pot b/docs/_locale/ja/quick-start.pot new file mode 100644 index 00000000..b4c7bf79 --- /dev/null +++ b/docs/_locale/ja/quick-start.pot @@ -0,0 +1,305 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../quick-start.rst:178 +msgid "A default action of ``return``, which returns the packet back to the original chain if no action is taken." +msgstr "A default action of ``return``, which returns the packet back to the original chain if no action is taken." + +#: ../../quick-start.rst:124 +msgid "A new firewall structure—which uses the ``nftables`` backend, rather than ``iptables``—is available on all installations starting from VyOS ``1.4-rolling-202308040557``. The firewall supports creation of distinct, interlinked chains for each `Netfilter hook <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_ and allows for more granular control over the packet filtering process." +msgstr "A new firewall structure—which uses the ``nftables`` backend, rather than ``iptables``—is available on all installations starting from VyOS ``1.4-rolling-202308040557``. The firewall supports creation of distinct, interlinked chains for each `Netfilter hook <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_ and allows for more granular control over the packet filtering process." + +#: ../../quick-start.rst:180 +msgid "A rule to ``accept`` packets from established and related connections." +msgstr "A rule to ``accept`` packets from established and related connections." + +#: ../../quick-start.rst:181 +msgid "A rule to ``drop`` packets from invalid connections." +msgstr "A rule to ``drop`` packets from invalid connections." + +#: ../../quick-start.rst:125 +msgid "Add a set of firewall policies for our outside/WAN interface." +msgstr "Add a set of firewall policies for our outside/WAN interface." + +#: ../../quick-start.rst:29 +msgid "After every configuration change, you need to apply the changes by using the following command:" +msgstr "After every configuration change, you need to apply the changes by using the following command:" + +#: ../../quick-start.rst:65 +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 "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." + +#: ../../quick-start.rst:51 +msgid "After switching to :ref:`quick-start-configuration-mode` issue the following commands:" +msgstr "After switching to :ref:`quick-start-configuration-mode` issue the following commands:" + +#: ../../quick-start.rst:301 +msgid "Allow Access to Services" +msgstr "Allow Access to Services" + +#: ../../quick-start.rst:257 +msgid "Allow Management Access" +msgstr "Allow Management Access" + +#: ../../quick-start.rst:208 +msgid "Alternatively, instead of configuring the ``CONN_FILTER`` chain described above, you can take the more traditional stateful connection filtering approach by creating rules on each hook's chain:" +msgstr "Alternatively, instead of configuring the ``CONN_FILTER`` chain described above, you can take the more traditional stateful connection filtering approach by creating rules on each hook's chain:" + +#: ../../quick-start.rst:167 +msgid "Apply the firewall policies:" +msgstr "Apply the firewall policies:" + +#: ../../quick-start.rst:367 +msgid "As above, commit your changes, save the configuration, and exit configuration mode:" +msgstr "As above, commit your changes, save the configuration, and exit configuration mode:" + +#: ../../quick-start.rst:227 +msgid "Block Incoming Traffic" +msgstr "Block Incoming Traffic" + +#: ../../quick-start.rst:17 +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 "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:" + +#: ../../quick-start.rst:17 +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 "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:" + +#: ../../quick-start.rst:27 +msgid "Commit and Save" +msgstr "Commit and Save" + +#: ../../quick-start.rst:327 +msgid "Commit changes, save the configuration, and exit configuration mode:" +msgstr "Commit changes, save the configuration, and exit configuration mode:" + +#: ../../quick-start.rst:15 +msgid "Configuration Mode" +msgstr "Configuration Mode" + +#: ../../quick-start.rst:143 +msgid "Configure Firewall Groups" +msgstr "Configure Firewall Groups" + +#: ../../quick-start.rst:162 +msgid "Configure Stateful Packet Filtering" +msgstr "Configure Stateful Packet Filtering" + +#: ../../quick-start.rst:271 +msgid "Configure a rule on the ``input`` hook filter to jump to the ``VyOS_MANAGEMENT`` chain when new connections are addressed to port 22 (SSH) on the router itself:" +msgstr "Configure a rule on the ``input`` hook filter to jump to the ``VyOS_MANAGEMENT`` chain when new connections are addressed to port 22 (SSH) on the router itself:" + +#: ../../quick-start.rst:233 +msgid "Create a new chain (``OUTSIDE-IN``) which will drop all traffic that is not explicity allowed at some point in the chain. Then, we can jump to that chain from the ``forward`` hook when traffic is coming from the ``WAN`` interface group and is addressed to our local network." +msgstr "Create a new chain (``OUTSIDE-IN``) which will drop all traffic that is not explicity allowed at some point in the chain. Then, we can jump to that chain from the ``forward`` hook when traffic is coming from the ``WAN`` interface group and is addressed to our local network." + +#: ../../quick-start.rst:78 +msgid "DHCP/DNS quick-start" +msgstr "DHCP/DNS quick-start" + +#: ../../quick-start.rst:87 +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 "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`" + +#: ../../quick-start.rst:87 +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 "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``" + +#: ../../quick-start.rst:89 +msgid "DHCP leases will hold for one day (86400 seconds)" +msgstr "DHCP leases will hold for one day (86400 seconds)" + +#: ../../quick-start.rst:131 +msgid "Documentation for most of the new firewall CLI can be found in the :ref:`firewall` chapter.The legacy firewall is still available for versions before ``1.4-rolling-202308040557`` and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the new configuration." +msgstr "Documentation for most of the new firewall CLI can be found in the :ref:`firewall` chapter.The legacy firewall is still available for versions before ``1.4-rolling-202308040557`` and can be found in the :ref:`firewall-legacy` chapter. The examples in this section use the new configuration." + +#: ../../quick-start.rst:341 +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 "Especially if you are allowing SSH remote access from the outside/WAN interface, there are a few additional configuration steps that should be taken." + +#: ../../quick-start.rst:281 +msgid "Finally, configure the ``VyOS_MANAGEMENT`` chain to accept connection from the ``LAN`` interface group while limiting requests coming from the ``WAN`` interface group to 4 per minute:" +msgstr "Finally, configure the ``VyOS_MANAGEMENT`` chain to accept connection from the ``LAN`` interface group while limiting requests coming from the ``WAN`` interface group to 4 per minute:" + +#: ../../quick-start.rst:357 +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 "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`:" + +#: ../../quick-start.rst:319 +msgid "Finally, we can now configure access to the services running on this router, allowing all connections coming from localhost:" +msgstr "Finally, we can now configure access to the services running on this router, allowing all connections coming from localhost:" + +#: ../../quick-start.rst:122 +msgid "Firewall" +msgstr "Firewall" + +#: ../../quick-start.rst:263 +msgid "First, create a new dedicated chain (``VyOS_MANAGEMENT``) for management access, which returns to the parent chain if no action is taken. Add a rule to accept traffic from the ``LAN`` interface group:" +msgstr "First, create a new dedicated chain (``VyOS_MANAGEMENT``) for management access, which returns to the parent chain if no action is taken. Add a rule to accept traffic from the ``LAN`` interface group:" + +#: ../../quick-start.rst:339 +msgid "Hardening" +msgstr "Hardening" + +#: ../../quick-start.rst:303 +msgid "Here we're allowing the router to respond to pings. Then, we can allow access to the DNS recursor we configured earlier, accepting traffic bound for port 53 from all hosts on the ``NET-INSIDE-v4`` network:" +msgstr "Here we're allowing the router to respond to pings. Then, we can allow access to the DNS recursor we configured earlier, accepting traffic bound for port 53 from all hosts on the ``NET-INSIDE-v4`` network:" + +#: ../../quick-start.rst:146 +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 "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." + +#: ../../quick-start.rst:150 +msgid "In this case, we will create two interface groups—a ``WAN`` group for our interfaces connected to the public internet and a ``LAN`` group for the interfaces connected to our internal network. Additionally, we will create a network group, ``NET-INSIDE-v4``, that contains our internal subnet." +msgstr "In this case, we will create two interface groups—a ``WAN`` group for our interfaces connected to the public internet and a ``LAN`` group for the interfaces connected to our internal network. Additionally, we will create a network group, ``NET-INSIDE-v4``, that contains our internal subnet." + +#: ../../quick-start.rst:44 +msgid "Interface Configuration" +msgstr "Interface Configuration" + +#: ../../quick-start.rst:109 +msgid "NAT" +msgstr "NAT" + +#: ../../quick-start.rst:229 +msgid "Now that we have configured stateful connection filtering to allow traffic from established and related connections, we can block all other incoming traffic addressed to our local network." +msgstr "Now that we have configured stateful connection filtering to allow traffic from established and related connections, we can block all other incoming traffic addressed to our local network." + +#: ../../quick-start.rst:36 +msgid "Once your configuration works as expected, you can save it permanently by using the following command:" +msgstr "Once your configuration works as expected, you can save it permanently by using the following command:" + +#: ../../quick-start.rst:92 +msgid "Only hosts from your internal/LAN network can use the DNS recursor" +msgstr "Only hosts from your internal/LAN network can use the DNS recursor" + +#: ../../quick-start.rst:168 +msgid "Option 1: Common Chain" +msgstr "Option 1: Common Chain" + +#: ../../quick-start.rst:206 +msgid "Option 2: Per-Hook Chain" +msgstr "Option 2: Per-Hook Chain" + +#: ../../quick-start.rst:5 +msgid "Quick Start" +msgstr "Quick Start" + +#: ../../quick-start.rst:344 +msgid "Replace the default ``vyos`` system user:" +msgstr "Replace the default ``vyos`` system user:" + +#: ../../quick-start.rst:192 +msgid "Replace the default `vyos` system user:" +msgstr "Replace the default `vyos` system user:" + +#: ../../quick-start.rst:63 +msgid "SSH Management" +msgstr "SSH Management" + +#: ../../quick-start.rst:350 +msgid "Set up :ref:`ssh_key_based_authentication`:" +msgstr "Set up :ref:`ssh_key_based_authentication`:" + +#: ../../quick-start.rst:85 +msgid "The address range `192.168.0.2/24 - 192.168.0.8/24` will be reserved for static assignments" +msgstr "The address range `192.168.0.2/24 - 192.168.0.8/24` will be reserved for static assignments" + +#: ../../quick-start.rst:85 +msgid "The address range ``192.168.0.2/24 - 192.168.0.8/24`` will be reserved for static assignments" +msgstr "The address range ``192.168.0.2/24 - 192.168.0.8/24`` will be reserved for static assignments" + +#: ../../quick-start.rst:176 +msgid "The chain we will create is called ``CONN_FILTER`` and has three rules:" +msgstr "The chain we will create is called ``CONN_FILTER`` and has three rules:" + +#: ../../quick-start.rst:84 +msgid "The default gateway and DNS recursor address will be `192.168.0.1/24`" +msgstr "The default gateway and DNS recursor address will be `192.168.0.1/24`" + +#: ../../quick-start.rst:84 +msgid "The default gateway and DNS recursor address will be ``192.168.0.1/24``" +msgstr "The default gateway and DNS recursor address will be ``192.168.0.1/24``" + +#: ../../quick-start.rst:137 +msgid "The firewall begins with the base ``filter`` tables you define for each of the ``forward``, ``input``, and ``output`` Netfiter hooks. Each of these tables is populated with rules that are processed in order and can jump to other chains for more granular filtering." +msgstr "The firewall begins with the base ``filter`` tables you define for each of the ``forward``, ``input``, and ``output`` Netfiter hooks. Each of these tables is populated with rules that are processed in order and can jump to other chains for more granular filtering." + +#: ../../quick-start.rst:80 +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 "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." + +#: ../../quick-start.rst:111 +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 "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." + +#: ../../quick-start.rst:194 +msgid "Then, we can jump to the common chain from both the ``forward`` and ``input`` hooks as the first filtering rule in the respective chains:" +msgstr "Then, we can jump to the common chain from both the ``forward`` and ``input`` hooks as the first filtering rule in the respective chains:" + +#: ../../quick-start.rst:150 +msgid "These rules allow SSH traffic and rate limit it to 4 requests per minute. This blocks brute-forcing attempts:" +msgstr "These rules allow SSH traffic and rate limit it to 4 requests per minute. This blocks brute-forcing attempts:" + +#: ../../quick-start.rst:7 +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 "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``)." + +#: ../../quick-start.rst:7 +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 "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`)." + +#: ../../quick-start.rst:127 +msgid "This configuration creates a proper stateful firewall that blocks all traffic which was not initiated from the internal/LAN side first." +msgstr "This configuration creates a proper stateful firewall that blocks all traffic which was not initiated from the internal/LAN side first." + +#: ../../quick-start.rst:145 +msgid "To make firewall configuration easier, we can create groups of interfaces, networks, addresses, ports, and domains that describe different parts of our network. We can then use them for filtering within our firewall rulesets, allowing for more concise and readable configuration." +msgstr "To make firewall configuration easier, we can create groups of interfaces, networks, addresses, ports, and domains that describe different parts of our network. We can then use them for filtering within our firewall rulesets, allowing for more concise and readable configuration." + +#: ../../quick-start.rst:90 +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 "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)" + +#: ../../quick-start.rst:170 +msgid "We can create a common chain for stateful connection filtering of multiple interfaces (or multiple netfilter hooks on one interface). Those individual chains can then jump to the common chain for stateful connection filtering, returning to the original chain for further rule processing if no action is taken on the packet." +msgstr "We can create a common chain for stateful connection filtering of multiple interfaces (or multiple netfilter hooks on one interface). Those individual chains can then jump to the common chain for stateful connection filtering, returning to the original chain for further rule processing if no action is taken on the packet." + +#: ../../quick-start.rst:259 +msgid "We can now configure access to the router itself, allowing SSH access from the inside/LAN network and rate limiting SSH access from the outside/WAN network." +msgstr "We can now configure access to the router itself, allowing SSH access from the inside/LAN network and rate limiting SSH access from the outside/WAN network." + +#: ../../quick-start.rst:247 +msgid "We should also block all traffic destinated to the router itself that isn't explicitly allowed at some point in the chain for the ``input`` hook. As we've already configured stateful packet filtering above, we only need to set the default action to ``drop``:" +msgstr "We should also block all traffic destinated to the router itself that isn't explicitly allowed at some point in the chain for the ``input`` hook. As we've already configured stateful packet filtering above, we only need to set the default action to ``drop``:" + +#: ../../quick-start.rst:164 +msgid "With the new firewall structure, we have have a lot of flexibility in how we group and order our rules, as shown by the two alternative approaches below." +msgstr "With the new firewall structure, we have have a lot of flexibility in how we group and order our rules, as shown by the two alternative approaches below." + +#: ../../quick-start.rst:379 +msgid "You now should have a simple yet secure and functioning router to experiment with further. Enjoy!" +msgstr "You now should have a simple yet secure and functioning router to experiment with further. Enjoy!" + +#: ../../quick-start.rst:48 +msgid "Your internal/LAN interface will be ``eth1``. It will use a static IP address of ``192.168.0.1/24``." +msgstr "Your internal/LAN interface will be ``eth1``. It will use a static IP address of ``192.168.0.1/24``." + +#: ../../quick-start.rst:48 +msgid "Your internal/LAN interface will be `eth1`. It will use a static IP address of `192.168.0.1/24`." +msgstr "Your internal/LAN interface will be `eth1`. It will use a static IP address of `192.168.0.1/24`." + +#: ../../quick-start.rst:46 +msgid "Your outside/WAN interface will be ``eth0``. It will receive its interface address via DHCP." +msgstr "Your outside/WAN interface will be ``eth0``. It will receive its interface address via DHCP." + +#: ../../quick-start.rst:46 +msgid "Your outside/WAN interface will be `eth0`. It will receive its interface address via DHCP." +msgstr "Your outside/WAN interface will be `eth0`. It will receive its interface address via DHCP." diff --git a/docs/_locale/ja/troubleshooting.pot b/docs/_locale/ja/troubleshooting.pot new file mode 100644 index 00000000..78b6b06f --- /dev/null +++ b/docs/_locale/ja/troubleshooting.pot @@ -0,0 +1,290 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: ja\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../troubleshooting/index.rst:73 +msgid "Advanced Connectivity Tests" +msgstr "Advanced Connectivity Tests" + +#: ../../troubleshooting/index.rst:196 +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 "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." + +#: ../../troubleshooting/index.rst:193 +msgid "Another example could be when cloning VyOS VMs in GNS3 and you get into the same issue: interface names have changed." +msgstr "Another example could be when cloning VyOS VMs in GNS3 and you get into the same issue: interface names have changed." + +#: ../../troubleshooting/index.rst:16 +msgid "Basic Connectivity Tests" +msgstr "Basic Connectivity Tests" + +#: ../../troubleshooting/index.rst:411 +msgid "Boot Steps" +msgstr "Boot Steps" + +#: ../../troubleshooting/index.rst:13 +msgid "Connectivity Tests" +msgstr "Connectivity Tests" + +#: ../../troubleshooting/index.rst:111 +msgid "Discover routers via eth0." +msgstr "Discover routers via eth0." + +#: ../../troubleshooting/index.rst:113 +#: ../../troubleshooting/index.rst:150 +msgid "Example:" +msgstr "Example:" + +#: ../../troubleshooting/index.rst:446 +msgid "Finally it runs the post-config script ``/config/scripts/vyos-postconfig-bootup.script``" +msgstr "Finally it runs the post-config script ``/config/scripts/vyos-postconfig-bootup.script``" + +#: ../../troubleshooting/index.rst:167 +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 "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." + +#: ../../troubleshooting/index.rst:419 +msgid "Grub then starts the Linux boot and loads the Linux Kernel ``/boot/vmlinuz``" +msgstr "Grub then starts the Linux boot and loads the Linux Kernel ``/boot/vmlinuz``" + +#: ../../troubleshooting/index.rst:77 +msgid "However, another helper is available which combines ping and traceroute into a single tool. An example of its output is shown:" +msgstr "However, another helper is available which combines ping and traceroute into a single tool. An example of its output is shown:" + +#: ../../troubleshooting/index.rst:102 +msgid "IPv6 Topology Discovery" +msgstr "IPv6 Topology Discovery" + +#: ../../troubleshooting/index.rst:104 +msgid "IPv6 uses different techniques to discover its Neighbors/topology." +msgstr "IPv6 uses different techniques to discover its Neighbors/topology." + +#: ../../troubleshooting/index.rst:188 +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 "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." + +#: ../../troubleshooting/index.rst:435 +msgid "If the config file was upgraded, runs any post upgrade scripts ``/config/scripts/post-upgrade.d``" +msgstr "If the config file was upgraded, runs any post upgrade scripts ``/config/scripts/post-upgrade.d``" + +#: ../../troubleshooting/index.rst:164 +msgid "If you find the names of your interfaces have changed, this could be because your MAC addresses have changed." +msgstr "If you find the names of your interfaces have changed, this could be because your MAC addresses have changed." + +#: ../../troubleshooting/index.rst:429 +msgid "Initialises the boot configuration file - copies over ``config.boot.default`` if there is no configuration" +msgstr "Initialises the boot configuration file - copies over ``config.boot.default`` if there is no configuration" + +#: ../../troubleshooting/index.rst:275 +msgid "Interface Bandwidth Usage" +msgstr "Interface Bandwidth Usage" + +#: ../../troubleshooting/index.rst:307 +msgid "Interface Performance" +msgstr "Interface Performance" + +#: ../../troubleshooting/index.rst:162 +msgid "Interface names" +msgstr "Interface names" + +#: ../../troubleshooting/index.rst:420 +msgid "Kernel Launches Systemd ``/lib/systemd/systemd``" +msgstr "Kernel Launches Systemd ``/lib/systemd/systemd``" + +#: ../../troubleshooting/index.rst:173 +msgid "Log into VyOS and run this command to display your interface settings." +msgstr "Log into VyOS and run this command to display your interface settings." + +#: ../../troubleshooting/index.rst:332 +msgid "Monitor command" +msgstr "Monitor command" + +#: ../../troubleshooting/index.rst:203 +msgid "Monitoring" +msgstr "Monitoring" + +#: ../../troubleshooting/index.rst:438 +msgid "Mounts the ``/boot`` partition" +msgstr "Mounts the ``/boot`` partition" + +#: ../../troubleshooting/index.rst:145 +msgid "Neighbor Discovery" +msgstr "Neighbor Discovery" + +#: ../../troubleshooting/index.rst:181 +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 "Now, in order to update a MAC address in the configuration, run this command specifying the interface name and MAC address you want." + +#: ../../troubleshooting/index.rst:171 +msgid "One way to fix this issue **taking control of the MAC addresses** is:" +msgstr "One way to fix this issue **taking control of the MAC addresses** is:" + +#: ../../troubleshooting/index.rst:107 +msgid "Router Discovery" +msgstr "Router Discovery" + +#: ../../troubleshooting/index.rst:433 +msgid "Runs The pre-config script, if there is one ``/config/scripts/vyos-preconfig-bootup.script``" +msgstr "Runs The pre-config script, if there is one ``/config/scripts/vyos-preconfig-bootup.script``" + +#: ../../troubleshooting/index.rst:445 +msgid "Runs ``telinit q`` to tell the init system to reload ``/etc/inittab``" +msgstr "Runs ``telinit q`` to tell the init system to reload ``/etc/inittab``" + +#: ../../troubleshooting/index.rst:431 +msgid "Runs the configuration migration, if the configuration is for an older version of VyOS" +msgstr "Runs the configuration migration, if the configuration is for an older version of VyOS" + +#: ../../troubleshooting/index.rst:25 +msgid "Send ICMP echo requests to destination host. There are multiple options to ping, inkl. VRF support." +msgstr "Send ICMP echo requests to destination host. There are multiple options to ping, inkl. VRF support." + +#: ../../troubleshooting/index.rst:97 +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 "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." + +#: ../../troubleshooting/index.rst:7 +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 "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." + +#: ../../troubleshooting/index.rst:364 +msgid "Sometimes you need to clear counters or statistics to troubleshoot better." +msgstr "Sometimes you need to clear counters or statistics to troubleshoot better." + +#: ../../troubleshooting/index.rst:427 +msgid "Starts FRR_ - successor to `GNU Zebra`_ and Quagga_" +msgstr "Starts FRR_ - successor to `GNU Zebra`_ and Quagga_" + +#: ../../troubleshooting/index.rst:437 +msgid "Starts ``rl-system`` and ``firewall``" +msgstr "Starts ``rl-system`` and ``firewall``" + +#: ../../troubleshooting/index.rst:406 +msgid "System Information" +msgstr "System Information" + +#: ../../troubleshooting/index.rst:421 +msgid "Systemd loads the VyOS service file ``/lib/systemd/system/vyos-router.service``" +msgstr "Systemd loads the VyOS service file ``/lib/systemd/system/vyos-router.service``" + +#: ../../troubleshooting/index.rst:179 +msgid "Take note of MAC addresses." +msgstr "Take note of MAC addresses." + +#: ../../troubleshooting/index.rst:362 +msgid "Terminal/Console" +msgstr "Terminal/Console" + +#: ../../troubleshooting/index.rst:418 +msgid "The BIOS loads Grub (or isolinux for the Live CD)" +msgstr "The BIOS loads Grub (or isolinux for the Live CD)" + +#: ../../troubleshooting/index.rst:319 +msgid "The ``accept`` command opens a listening iperf server on TCP Port 5001" +msgstr "The ``accept`` command opens a listening iperf server on TCP Port 5001" + +#: ../../troubleshooting/index.rst:320 +msgid "The ``initiate`` command connects to that server to perform the test." +msgstr "The ``initiate`` command connects to that server to perform the test." + +#: ../../troubleshooting/index.rst:334 +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 "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." + +#: ../../troubleshooting/index.rst:439 +msgid "The boot configuration file is then applied by ``/opt/vyatta/sbin/ vyatta-boot-config-loader/opt/vyatta/etc/config/config.boot``" +msgstr "The boot configuration file is then applied by ``/opt/vyatta/sbin/ vyatta-boot-config-loader/opt/vyatta/etc/config/config.boot``" + +#: ../../troubleshooting/index.rst:383 +msgid "The command follow the same logic as the ``set`` command in configuration mode." +msgstr "The command follow the same logic as the ``set`` command in configuration mode." + +#: ../../troubleshooting/index.rst:442 +msgid "The config loader script writes log entries to ``/var/log/vyatta-config-loader.log``" +msgstr "The config loader script writes log entries to ``/var/log/vyatta-config-loader.log``" + +#: ../../troubleshooting/index.rst:94 +msgid "The output consumes the screen and will replace your command prompt." +msgstr "The output consumes the screen and will replace your command prompt." + +#: ../../troubleshooting/index.rst:423 +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 "The service file launches the VyOS router init script ``/usr/libexec/vyos/init/vyos-router`` - this is part of the vyatta-cfg_ Debian package" + +#: ../../troubleshooting/index.rst:416 +msgid "These are the boot steps for VyOS 1.2" +msgstr "These are the boot steps for VyOS 1.2" + +#: ../../troubleshooting/index.rst:366 +msgid "To do this use the ``clear`` command in Operational mode." +msgstr "To do this use the ``clear`` command in Operational mode." + +#: ../../troubleshooting/index.rst:242 +msgid "To monitor interface traffic, issue the :code:`monitor traffic interface <name>` command, replacing `<name>` with your chosen interface." +msgstr "To monitor interface traffic, issue the :code:`monitor traffic interface <name>` command, replacing `<name>` with your chosen interface." + +#: ../../troubleshooting/index.rst:260 +msgid "To quit monitoring, press `Ctrl-c` and you'll be returned to the VyOS command prompt." +msgstr "To quit monitoring, press `Ctrl-c` and you'll be returned to the VyOS command prompt." + +#: ../../troubleshooting/index.rst:309 +msgid "To take a look on the network bandwidth between two nodes, the ``monitor bandwidth-test`` command is used to run iperf." +msgstr "To take a look on the network bandwidth between two nodes, the ``monitor bandwidth-test`` command is used to run iperf." + +#: ../../troubleshooting/index.rst:59 +msgid "Trace path to target." +msgstr "Trace path to target." + +#: ../../troubleshooting/index.rst:240 +msgid "Traffic Dumps" +msgstr "Traffic Dumps" + +#: ../../troubleshooting/index.rst:263 +msgid "Traffic can be filtered and saved." +msgstr "Traffic can be filtered and saved." + +#: ../../troubleshooting/index.rst:5 +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#: ../../troubleshooting/index.rst:18 +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 "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):" + +#: ../../troubleshooting/index.rst:413 +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 "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." + +#: ../../troubleshooting/index.rst:205 +msgid "VyOS features several monitoring tools." +msgstr "VyOS features several monitoring tools." + +#: ../../troubleshooting/index.rst:343 +msgid "Will clear the screen and show you the output of ``show interfaces`` every 2 seconds." +msgstr "Will clear the screen and show you the output of ``show interfaces`` every 2 seconds." + +#: ../../troubleshooting/index.rst:284 +msgid "show the following:" +msgstr "show the following:" + +#: ../../troubleshooting/index.rst:393 +msgid "to clear counters on firewall rulesets or single rules" +msgstr "to clear counters on firewall rulesets or single rules" + +#: ../../troubleshooting/index.rst:374 +msgid "to clear interface counters" +msgstr "to clear interface counters" + +#: ../../troubleshooting/index.rst:368 +msgid "to clear the console output" +msgstr "to clear the console output" + +#: ../../troubleshooting/index.rst:277 +msgid "to take a quick view on the used bandwidth of an interface use the ``monitor bandwidth`` command" +msgstr "to take a quick view on the used bandwidth of an interface use the ``monitor bandwidth`` command" |