From b90010c3cf2d5d011c8ff181a1a47136135d164b Mon Sep 17 00:00:00 2001 From: rebortg Date: Wed, 6 Sep 2023 19:02:18 +0000 Subject: Github: update translations --- docs/_locale/de/404.pot | 4 +- docs/_locale/de/LC_MESSAGES/404.mo | Bin 936 -> 984 bytes docs/_locale/de/LC_MESSAGES/configexamples.mo | Bin 0 -> 119351 bytes docs/_locale/de/LC_MESSAGES/configuration.mo | Bin 0 -> 1034491 bytes docs/_locale/de/LC_MESSAGES/contributing.mo | Bin 0 -> 109085 bytes docs/_locale/de/configexamples.pot | 2676 ++++ docs/_locale/de/configuration.pot | 20444 ++++++++++++++++++++++++ docs/_locale/de/contributing.pot | 1726 ++ docs/_locale/en/LC_MESSAGES/configexamples.mo | Bin 119198 -> 119340 bytes docs/_locale/en/LC_MESSAGES/introducing.mo | Bin 13212 -> 14136 bytes 10 files changed, 24848 insertions(+), 2 deletions(-) create mode 100644 docs/_locale/de/LC_MESSAGES/configexamples.mo create mode 100644 docs/_locale/de/LC_MESSAGES/configuration.mo create mode 100644 docs/_locale/de/LC_MESSAGES/contributing.mo create mode 100644 docs/_locale/de/configexamples.pot create mode 100644 docs/_locale/de/configuration.pot create mode 100644 docs/_locale/de/contributing.pot (limited to 'docs') diff --git a/docs/_locale/de/404.pot b/docs/_locale/de/404.pot index 1f1db527..0ecb1908 100644 --- a/docs/_locale/de/404.pot +++ b/docs/_locale/de/404.pot @@ -14,7 +14,7 @@ msgstr "Seite nicht gefunden" #: ../../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:" +msgstr "Entschuldigung, wir konnten keine Seite finden. Versuchen Sie es mit dem Suchfeld oder gehen Sie auf die Homepage der Veröffentlichung:" #: ../../404.rst:9 msgid "`1.2.x (crux) `_" @@ -26,4 +26,4 @@ msgstr "`1.3.x (equuleus) `_" #: ../../404.rst:11 msgid "`rolling release (sagitta) `_" -msgstr "`rolling release (sagitta) `_" +msgstr "`Rolling Release (Sagitta) `_" diff --git a/docs/_locale/de/LC_MESSAGES/404.mo b/docs/_locale/de/LC_MESSAGES/404.mo index b413a497..5cfb6e0c 100644 Binary files a/docs/_locale/de/LC_MESSAGES/404.mo and b/docs/_locale/de/LC_MESSAGES/404.mo differ diff --git a/docs/_locale/de/LC_MESSAGES/configexamples.mo b/docs/_locale/de/LC_MESSAGES/configexamples.mo new file mode 100644 index 00000000..b576ae18 Binary files /dev/null and b/docs/_locale/de/LC_MESSAGES/configexamples.mo differ diff --git a/docs/_locale/de/LC_MESSAGES/configuration.mo b/docs/_locale/de/LC_MESSAGES/configuration.mo new file mode 100644 index 00000000..d64511e6 Binary files /dev/null and b/docs/_locale/de/LC_MESSAGES/configuration.mo differ diff --git a/docs/_locale/de/LC_MESSAGES/contributing.mo b/docs/_locale/de/LC_MESSAGES/contributing.mo new file mode 100644 index 00000000..da94bd77 Binary files /dev/null and b/docs/_locale/de/LC_MESSAGES/contributing.mo differ diff --git a/docs/_locale/de/configexamples.pot b/docs/_locale/de/configexamples.pot new file mode 100644 index 00000000..acf53765 --- /dev/null +++ b/docs/_locale/de/configexamples.pot @@ -0,0 +1,2676 @@ +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: de\n" +"Plural-Forms: nplurals=2; plural=(n==1) ? 0 : 1;\n" + +#: ../../configexamples/zone-policy.rst:152 +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:118 +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:135 +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:157 +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:134 +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:24 +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:35 +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:33 +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/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:34 +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/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/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/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/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:141 +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 `_" +msgstr "Check all possible settings `here `_" + +#: ../../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/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:93 +#: ../../configexamples/azure-vpn-dual-bgp.rst:95 +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/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/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:27 +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/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:86 +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:99 +msgid "Configure the VPN tunnel" +msgstr "Configure the VPN tunnel" + +#: ../../configexamples/azure-vpn-dual-bgp.rst:102 +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:85 +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:124 +#: ../../configexamples/azure-vpn-dual-bgp.rst:142 +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:364 +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:39 +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:81 +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:31 +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:80 +#: ../../configexamples/azure-vpn-dual-bgp.rst:79 +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:243 +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/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 ` 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 ` 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/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:272 +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 ``::64``, where ``64`` is hexadecimal of address 100." +msgstr "Here we use the prefix to configure the address of eth1 (LAN) to form ``::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/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:373 +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:161 +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:90 +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:375 +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:100 +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:93 +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:157 +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:8 +msgid "In :vytask:`T2199` the syntax of the zone configuration was changed. The zone configuration moved from ``zone-policy zone `` to ``firewall zone ``." +msgstr "In :vytask:`T2199` the syntax of the zone configuration was changed. The zone configuration moved from ``zone-policy zone `` to ``firewall zone ``." + +#: ../../configexamples/zone-policy.rst:105 +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:367 +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 `_ 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 `_ first." + +#: ../../configexamples/zone-policy.rst:355 +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:97 +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:40 +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/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:30 +msgid "Internet - 192.168.200.100 - TCP/25" +msgstr "Internet - 192.168.200.100 - TCP/25" + +#: ../../configexamples/zone-policy.rst:29 +msgid "Internet - 192.168.200.100 - TCP/443" +msgstr "Internet - 192.168.200.100 - TCP/443" + +#: ../../configexamples/zone-policy.rst:31 +msgid "Internet - 192.168.200.100 - TCP/53" +msgstr "Internet - 192.168.200.100 - TCP/53" + +#: ../../configexamples/zone-policy.rst:28 +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:130 +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:50 +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:382 +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:37 +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:38 +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/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:13 +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/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:401 +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:345 +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/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/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:88 +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:226 +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:406 +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:348 +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/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:47 +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:123 +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:172 +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:29 +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:37 +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/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/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:248 +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:134 +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:85 +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/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:32 +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:15 +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:378 +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:403 +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:79 +msgid "Zones Basics" +msgstr "Zones Basics" + +#: ../../configexamples/zone-policy.rst:126 +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:165 +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:40 +msgid "configure each host in the lab" +msgstr "configure each host in the lab" + +#: ../../configexamples/index.rst:39 +msgid "create the lab on a eve-ng server" +msgstr "create the lab on a eve-ng server" + +#: ../../configexamples/index.rst:41 +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:43 +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:42 +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:44 +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:384 +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\", um die RIB in unserem Spoke PE anzuzeigen." + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:579 +msgid "“show mpls ldp binding” for checking mpls label assignment" +msgstr "\"show mpls ldp binding\" zur Überprüfung der mpls-Label-Zuweisung" + +#: ../../configexamples/l3vpn-hub-and-spoke.rst:567 +msgid "“show mpls ldp neighbor “ for checking ldp neighbors" +msgstr "\"show mpls ldp neighbor \" zur Überprüfung von ldp-Nachbarn" diff --git a/docs/_locale/de/configuration.pot b/docs/_locale/de/configuration.pot new file mode 100644 index 00000000..55ce60ff --- /dev/null +++ b/docs/_locale/de/configuration.pot @@ -0,0 +1,20444 @@ +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: de\n" +"Plural-Forms: nplurals=2; plural=(n==1) ? 0 : 1;\n" + +#: ../../configuration/policy/route.rst:74 +msgid "!: Match everything except the specified prefix." +msgstr "!: Match everything except the specified prefix." + +#: ../../configuration/policy/route.rst:75 +msgid "!-: Match everything except the specified range." +msgstr "!-: Match everything except the specified range." + +#: ../../configuration/policy/route.rst:73 +msgid "!: Match everything except the specified address." +msgstr "!: Match everything except the specified address." + +#: ../../configuration/policy/route.rst:66 +msgid "!: Match everything except the specified subnet." +msgstr "!: Match everything except the specified subnet." + +#: ../../configuration/policy/route.rst:67 +msgid "!-: Match everything except the specified range." +msgstr "!-: Match everything except the specified range." + +#: ../../configuration/policy/route.rst:65 +msgid "!: Match everything except the specified address." +msgstr "!: 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/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 ` **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 ` **as FQ-CoDel**." + +#: ../../configuration/firewall/general-legacy.rst:9 +#: ../../configuration/firewall/zone.rst:9 +msgid "**Important note:** This documentation is valid only for VyOS Sagitta prior to 1.4-rolling-YYYYMMDDHHmm" +msgstr "**Wichtiger Hinweis: ** Diese Dokumentation ist nur für VyOS Sagitta vor 1.4-Rolling-YYYYMMDDHHMM gültig" + +#: ../../configuration/firewall/general.rst:79 +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 "**Wichtiger Hinweis zu Standardaktionen: ** Wenn die Standardaktion für eine Kette nicht definiert ist, ist die Standardaktion für diese Kette auf ** accept** gesetzt. Nur für benutzerdefinierte Ketten ist die Standardaktion auf **drop** gesetzt." + +#: ../../configuration/firewall/general.rst:409 +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 `_" +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 `_" + +#: ../../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:184 +msgid "**Leaf2 configuration:**" +msgstr "**Leaf2 configuration:**" + +#: ../../configuration/interfaces/vxlan.rst:209 +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 \"/\" 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 \"/\" 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:272 +msgid "**Setting up IPSec**" +msgstr "**Setting up IPSec**" + +#: ../../configuration/vpn/ipsec.rst:248 +msgid "**Setting up the GRE tunnel**" +msgstr "**Setting up the GRE tunnel**" + +#: ../../configuration/interfaces/vxlan.rst:161 +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:106 +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 ": Extended community list regular expression." +msgstr ": Extended community list regular expression." + +#: ../../configuration/policy/route.rst:71 +msgid ": IPv6 prefix to match." +msgstr ": IPv6 prefix to match." + +#: ../../configuration/policy/route.rst:72 +msgid "-: IPv6 range to match." +msgstr "-: IPv6 range to match." + +#: ../../configuration/policy/route.rst:70 +msgid ": IPv6 address to match." +msgstr ": IPv6 address to match." + +#: ../../configuration/system/syslog.rst:230 +msgid "" +msgstr "" + +#: ../../configuration/interfaces/wireless.rst:251 +msgid " must be from 34 - 173. For 80 MHz channels it should be channel + 6." +msgstr " must be from 34 - 173. For 80 MHz channels it should be channel + 6." + +#: ../../configuration/protocols/ospf.rst:346 +msgid " – area identifier through which a virtual link goes. – ABR router-id with which a virtual link is established. Virtual link must be configured on both routers." +msgstr " – area identifier through which a virtual link goes. – ABR router-id with which a virtual link is established. Virtual link must be configured on both routers." + +#: ../../configuration/policy/route.rst:97 +msgid ": Named port (any name in /etc/services, e.g., http)." +msgstr ": Named port (any name in /etc/services, e.g., http)." + +#: ../../configuration/policy/extcommunity-list.rst:39 +msgid ": Route Target regular expression." +msgstr ": Route Target regular expression." + +#: ../../configuration/policy/extcommunity-list.rst:40 +msgid ": Site of Origin regular expression." +msgstr ": Site of Origin regular expression." + +#: ../../configuration/policy/route.rst:99 +msgid "-: Numbered port range (e.g., 1001-1005)." +msgstr "-: Numbered port range (e.g., 1001-1005)." + +#: ../../configuration/policy/route.rst:63 +msgid ": Subnet to match." +msgstr ": Subnet to match." + +#: ../../configuration/policy/route.rst:64 +msgid "-: IP range to match." +msgstr "-: IP range to match." + +#: ../../configuration/policy/route.rst:62 +msgid ": IP address to match." +msgstr ": IP address to match." + +#: ../../configuration/protocols/static.rst:150 +msgid "ARP" +msgstr "ARP" + +#: ../../configuration/firewall/general.rst:309 +#: ../../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:291 +#: ../../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:266 +#: ../../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:746 +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/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:486 +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 `." +msgstr "A full example of a Tunnelbroker.net config can be found at :ref:`here `." + +#: ../../configuration/service/dhcp-server.rst:187 +msgid "A generic `` referencing this sync service." +msgstr "A generic `` 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:766 +#: ../../configuration/firewall/general-legacy.rst:503 +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:22 +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 `` on TCP port ``. After successfull authentication the user will be directly dropped to the connected serial device." +msgstr "Accept SSH connections for the given `` on TCP 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:334 +#: ../../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/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:363 +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:199 +#: ../../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:287 +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/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:25 +msgid "All traffic between zones is affected by existing policies" +msgstr "All traffic between zones is affected by existing policies" + +#: ../../configuration/firewall/zone.rst:24 +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:1142 +#: ../../configuration/firewall/general-legacy.rst:691 +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. `` will be the next-hop interface where traffic is routed for the given ``." +msgstr "Allows you to configure the next-hop interface for an interface-based IPv4 static route. `` will be the next-hop interface where traffic is routed for the given ``." + +#: ../../configuration/protocols/static.rst:89 +msgid "Allows you to configure the next-hop interface for an interface-based IPv6 static route. `` will be the next-hop interface where traffic is routed for the given ``." +msgstr "Allows you to configure the next-hop interface for an interface-based IPv6 static route. `` will be the next-hop interface where traffic is routed for the given ``." + +#: ../../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:382 +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:291 +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:248 +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 `` 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 `` 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 `_)" +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 `_)" + +#: ../../configuration/firewall/general.rst:624 +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 `_)" +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 `_)" + +#: ../../configuration/firewall/zone.rst:43 +msgid "An basic introduction to zone-based firewalls can be found `here `_, and an example at :ref:`examples-zone-policy`." +msgstr "An basic introduction to zone-based firewalls can be found `here `_, 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:71 +msgid "Applying a Rule-Set to a Zone" +msgstr "Applying a Rule-Set to a Zone" + +#: ../../configuration/firewall/general-legacy.rst:744 +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:614 +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:38 +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/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/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:234 +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:767 +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 `` interface to bridge ``. 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 `` interface to bridge ``. 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 `` to VRF named ``." +msgstr "Assign interface identified by `` to VRF named ``." + +#: ../../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 `` account." +msgstr "Assign static IP address to `` account." + +#: ../../configuration/service/dhcp-server.rst:111 +msgid "Assign the IP address to this machine for `