diff options
| author | rebortg <github@ghlr.de> | 2022-10-24 21:49:31 +0200 |
|---|---|---|
| committer | rebortg <github@ghlr.de> | 2022-10-24 21:49:31 +0200 |
| commit | b18aa2f9d853b92e193269a53c1b00c9f48dd73f (patch) | |
| tree | f5b33453ef9ffcbe6567ce9220a785fdc8236220 /docs/_locale/de_DE/LC_MESSAGES/configexamples | |
| parent | 99ccd5cd0e0ac2efdc50f3eda88744601a0a996a (diff) | |
| download | vyos-documentation-b18aa2f9d853b92e193269a53c1b00c9f48dd73f.tar.gz vyos-documentation-b18aa2f9d853b92e193269a53c1b00c9f48dd73f.zip | |
migrate to new transifex client
Diffstat (limited to 'docs/_locale/de_DE/LC_MESSAGES/configexamples')
15 files changed, 0 insertions, 3806 deletions
diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po deleted file mode 100644 index 78dd752d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.po +++ /dev/null @@ -1,108 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:3 -#: b6d67f49feb24b3fa122917d1713c0ba -msgid "DHCP Relay trough GRE-Bridge" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:6 -#: 1d016bc7120144c1a698121e631b88ce -msgid "Testdate: 2022-10-09" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:7 -#: 6e048b6b5d1e4ed6b4f25e94edecf47b -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:10 -#: 127597ad8c8f4e5eb5d2b85948c155dd -msgid "" -"This simple structure shows how to configure a DHCP Relay over a GRE Bridge " -"interface." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:15 -#: 836e04717d9b453d93aa06d489e25a0d -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:17 -#: 153ef16cb87c40c29370123457b2278c -msgid "" -"The topology has 3 VyOS routers and one client. Between the DHCP Server and " -"the DHCP Relay is a GRE tunnel. The `transport` VyOS represent a large " -"Network." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rstNone -#: e3f84da3f42e4d51862669dd2cb899b2 -msgid "Ansible Example topology image" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:26 -#: 78c31c77e3374b9287e0f46c5547ff07 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:28 -#: 85735f69fefc4e47a6eeb0a79631ea61 -msgid "First, we configure the transport network and the Tunnel interface." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:31 -#: 635c882d632a43dc83f0f02362c57f56 -msgid "Transport:" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:37 -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:55 -#: e87f4b14b9ae4bfda9bbf5436e2580ee cd57953b80374d54ae35108ce6357ed2 -msgid "DHCP-Server" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:44 -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:62 -#: 379e70552a164cfe986786970522535d 77e16e1cf47f416d9877c94023f07a85 -msgid "DHCP-Relay" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:51 -#: d6c3ef6fe4d84842af6b47146a6bf09d -msgid "" -"After this, we need the DHCP-Server and Relay configuration. To get a " -"testable result, we just have one IP in the DHCP range. Expand it as you " -"need it." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:71 -#: cf696a295396415b829948546d904674 -msgid "Test the result" -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:73 -#: 1c9009bcb8ef4063a0dbc89927cb394e -msgid "Ping the Client from the DHCP Server." -msgstr "" - -#: ../../configexamples/autotest/DHCPRelay_through_GRE/DHCPRelay_through_GRE.rst:90 -#: 7deadd4f386f48b48429ebd1d788fbf9 -msgid "And show all DHCP Leases" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po deleted file mode 100644 index 9584018f..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.po +++ /dev/null @@ -1,248 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:4 -#: dca7066243a64ac9bb911c232c07a55c -msgid "L3VPN EVPN with VyOS" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:6 -#: 40009f7cec44488b973f2aa05da6cf76 -msgid "Testdate: 2022-10-10" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:7 -#: 259b38aa4a6447c4bd22d3d881ef6445 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:9 -#: a18b811d628d480a83d2d5a41fa905db -msgid "" -"I spun up a new lab in EVE-NG, which represents this as the \"Foo Bar - " -"Service Provider Inc.\" that has 3 points of presence (PoP) in random " -"datacenters/sites named PE1, PE2, and PE3. Each PoP aggregates at least two " -"customers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:14 -#: c847a6183ba6486095e722083c3f7a6d -msgid "" -"I named the customers blue, red and green which is common practice in VRF " -"(Virtual Routing and Forwarding) documentation scenarios." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:17 -#: 59b7c95414774841abc20f1e2f4202d2 -msgid "" -"PE1 is located in an industrial area that holds multiple office buildings. " -"All customers have a site in this area." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:19 -#: 6fffa1cde14c4de0a3264303ddab2209 -msgid "" -"PE2 is located in a smaller area where by coincidence two customers (blue " -"and red) share an office building." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:21 -#: 84cea04906cc4f6cafbb0a5b05df5eb8 -msgid "" -"PE3 is located in a smaller area where by coincidence two customers (blue " -"and green) are located." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:26 -#: 2984bd561ad44a85b369de655fc4c04f -msgid "Management VRF" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:28 -#: e0c8580baf144bec8f6652c6226fa5d5 -msgid "" -"A brief excursion into VRFs: This has been one of the longest-standing " -"feature requests of VyOS (dating back to 2016) which can be described as \"a" -" VLAN for layer 2 is what a VRF is for layer 3\". With VRFs, a router/system" -" can hold multiple, isolated routing tables on the same system. If you " -"wonder what's the difference between multiple tables that people used for " -"policy-based routing since forever, it's that a VRF also isolates connected " -"routes rather than just static and dynamically learned routes, so it allows " -"NICs in different VRFs to use conflicting network ranges without issues." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:38 -#: 1a678edb2c814554987d969567cb843d -msgid "" -"VyOS 1.3 added initial support for VRFs (including IPv4/IPv6 static routing)" -" and VyOS 1.4 now enables full dynamic routing protocol support for OSPF, " -"IS-IS, and BGP for individual VRFs." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:42 -#: 8308ef8d3eef4bf583ba6ae20941f9e5 -msgid "" -"The lab I built is using a VRF (called **mgmt**) to provide out-of-band SSH " -"access to the PE (Provider Edge) routers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:52 -#: eba9ea05ad7841849983d2705c9410d6 -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:54 -#: e2986d31e7ee4bffa5b2e115a952b7ae -msgid "We use the following network topology in this example:" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rstNone -#: cec7142cd4c146bf944e487d1c071124 -msgid "L3VPN EVPN with VyOS topology image" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:62 -#: dc04d5ec28614dd58ed11e537c255941 -msgid "Core network" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:64 -#: 79db8a2ac0774a52805405daab666a6e -msgid "" -"I chose to run OSPF as the IGP (Interior Gateway Protocol). All required BGP" -" sessions are established via a dummy interfaces (similar to the loopback, " -"but in Linux you can have only one loopback, while there can be many dummy " -"interfaces) on the PE routers. In case of a link failure, traffic is " -"diverted in the other direction in this triangle setup and BGP sessions will" -" not go down. One could even enable BFD (Bidirectional Forwarding Detection)" -" on the links for a faster failover and resilience in the network." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:73 -#: c03653c3a768410a8ba4e3f35a9df6f8 -msgid "" -"Regular VyOS users will notice that the BGP syntax has changed in VyOS 1.4 " -"from even the prior post about this subject. This is due to T1711, where it " -"was finally decided to get rid of the redundant BGP ASN (Autonomous System " -"Number) specification on the CLI and move it to a single leaf node (set " -"protocols bgp local-as)." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:79 -#: b54e76d59f2a4879ad57e4d751f44534 -msgid "" -"It's important to note that all your existing configurations will be " -"migrated automatically on image upgrade. Nothing to do on your side." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:82 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:123 -#: 778bcf8867dd4742b90af58c3c2974f9 03e0d184dd814620b0ebf2066fe5cd54 -msgid "PE1" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:88 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:129 -#: feca16238d384858bde862fcffc4f668 e764ab9f7c1c464fb6b8ad766e9a97da -msgid "PE2" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:94 -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:135 -#: 418db537cb7e4646b396025335c225fb 34e53a71b2a6421992ee83f3d458883a -msgid "PE3" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:103 -#: 5a2fa388fab34210972487efc12cc05f -msgid "Tenant networks (VRFs)" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:105 -#: 54d85baae8274726b442dabf00d643bc -msgid "" -"Once all routers can be safely remotely managed and the core network is " -"operational, we can now setup the tenant networks." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:108 -#: d1d790f73bb545edbcb20f8ded69e5f7 -msgid "" -"Every tenant is assigned an individual VRF that would support overlapping " -"address ranges for customers blue, red and green. In our example, we do not " -"use overlapping ranges to make it easier when showing debug commands." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:112 -#: 6e4c009e66714b06982495a718d7bed4 -msgid "Thus you can easily match it to one of the devices/networks below." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:114 -#: 8eda9841785d48eaa53e33b241c5dfb6 -msgid "" -"Every router that provides access to a customer network needs to have the " -"customer network (VRF + VNI) configured. To make our own lives easier, we " -"utilize the same VRF table id (local routing table number) and VNI (Virtual " -"Network Identifier) per tenant on all our routers." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:119 -#: 5acd5a7623b2476d9e2e2c66ccb740b4 -msgid "blue uses local routing table id and VNI 2000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:120 -#: c79bdaa44fb94e9284a8043361262dde -msgid "red uses local routing table id and VNI 3000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:121 -#: 2afb2d9e933344099bf7b103aa2f4187 -msgid "green uses local routing table id and VNI 4000" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:143 -#: 6cefa7e52add4fe1a75562495292efe0 -msgid "Testing and debugging" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:145 -#: 4be9bdc170984b6ab7e3ee7e60617ff4 -msgid "" -"You managed to come this far, now we want to see the network and routing " -"tables in action." -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:148 -#: c5321083829e4286b93d550d75d5060f -msgid "Show routes for all VRFs" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:189 -#: 4b9a7dc8ae3849178c5061f8c9e40b00 -msgid "Information about Ethernet Virtual Private Networks" -msgstr "" - -#: ../../configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst:236 -#: 0464a050fc0e428bbf2d160f31fa2225 -msgid "" -"If we need to retrieve information about a specific host/network inside the " -"EVPN network we need to run" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po deleted file mode 100644 index 5f469405..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/Wireguard/Wireguard.po +++ /dev/null @@ -1,120 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:3 -#: 1112b498492f4f97b47ca5315651543c -msgid "Wireguard" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:6 -#: cad83059fc954e2f9797528e77ae3265 -msgid "Testdate: 2022-10-09" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:7 -#: b8317168f5c34dacac426bbf160099c2 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:10 -#: ff88b0392e1342eda89e21f06001f593 -msgid "" -"This simple structure show how to connect two offices. One remote branch and" -" the central office." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:15 -#: fa805f515da84e8eae724617bc7f6a2b -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:17 -#: 7954fa9a77a346759a5b29c935061602 -msgid "" -"The topology have a central and a branch VyOS router and one client, to " -"test, in each site." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rstNone -#: 2fb68483c1724b5ab8b9fd6d3929e5f3 -msgid "Ansible Example topology image" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:25 -#: 13f50b70eced428b8cf14ab4dbf1569d -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:27 -#: 762f0d7725dd4ddcb4c8f6abd1cd7185 -msgid "" -"Set the local subnet on eth2 and the public ip address eth1 on each site." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:29 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:55 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:71 -#: 5b82506aea5a4d4383ed66f8751497e5 c06020215f594cdf94351ebe8149581e -#: 56ed8089bd3a4ece8b90b56a21269698 -msgid "Central" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:35 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:61 -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:77 -#: 958fa8e6ae9742c4a8c9f7000989d8f0 08cfff8b32b744379d8d6526dfd47ec1 -#: 4ba49eec7bc4436d8d4841fb437ee866 -msgid "Branch" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:42 -#: 37eddc3053d14cbf9fcf84a5e2e47bff -msgid "" -"Next thing to do, is to create a wireguard keypair on each side. After this," -" the public key can be displayed, to save for later." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:52 -#: 898c59cc02ef490a88ddd78faaeeb42e -msgid "After you have each public key. The wireguard interfaces can be setup." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:68 -#: 403a421f999b4d2b99e5a45f8fcc58bb -msgid "" -"To reach the network, a route must be set on each VyOS host. In this " -"structure, a static interface route will fit the requirements." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:85 -#: 75c272fbdcdb40028fb502ba388339e7 -msgid "Testing and debugging" -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:87 -#: fcbab0e2725d4fd3b59226ef41192888 -msgid "" -"After all is done and commit, let's take a look if the Wireguard interface " -"is up and running." -msgstr "" - -#: ../../configexamples/autotest/Wireguard/Wireguard.rst:99 -#: 1f323a79c53143b7b93f62946f16329c -msgid "And ping the Branch PC from your central router to check the response." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po deleted file mode 100644 index 14accc87..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/autotest/tunnelbroker/tunnelbroker.po +++ /dev/null @@ -1,282 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:5 -#: e858d6875b1c46cbaece3f265eebe9cb -msgid "Tunnelbroker.net (IPv6)" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:7 -#: 43c9e137b1d64397b43509cefc6afbde -msgid "Testdate: 2022-10-10" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:8 -#: 1f2dc4f37d04432da5f6c54a33f566d7 -msgid "Version: 1.4-rolling-202210090955" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:10 -#: 0e33bf12fa6a4b59bff76e91b4f74173 -msgid "" -"This guide walks through the setup of https://www.tunnelbroker.net/ for an " -"IPv6 Tunnel." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:14 -#: 4510e8e67ecf46b48da0836bd31fdfd7 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:16 -#: e4f40532bb684bddae9a98badaa6f494 -msgid "" -"A public, routable IPv4 address. This does not necessarily need to be " -"static, but you will need to update the tunnel endpoint when/if your IP " -"address changes, which can be done with a script and a scheduled task." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:19 -#: bf9411243d594a209d8e5233a911faca -msgid "Account at https://www.tunnelbroker.net/" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:20 -#: 3384e179dd6b47fbb4bbcc549b558601 -msgid "" -"Requested a \"Regular Tunnel\". You want to choose a location that is " -"closest to your physical location for the best response time." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:26 -#: 4beeca87d8534dbaaa908be33faa6199 -msgid "Topology" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:28 -#: 1fae284fcce641af8a51074758c69698 -msgid "" -"The example topology has 2 VyOS routers. One as The WAN Router and on as a " -"Client, to test a single LAN setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rstNone -#: bb725568726e4e059b23a99e4c66a6cd -msgid "Tunnelbroker topology image" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:37 -#: 30329a3d8a1c4912965057dbcf802832 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:39 -#: bae83b5f1ac1460ea11b8864f65ffd79 -msgid "First, we configure the ``vyos-wan`` interface to get a DHCP address." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:45 -#: 51ab034c5a6a42ce821332f22f016579 -msgid "Now we are able to setup the tunnel interface." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:51 -#: a07ed24d74054c0d9c83a9f732ddd57e -msgid "Setup the ipv6 default route to the tunnel interface" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:57 -#: 2a5666024df949d2b4235f6df9bbeb54 -msgid "Now you should be able to ping a public IPv6 Address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:74 -#: b35fbadb6df74e5b83c5e1416d1afede -msgid "" -"Assuming the pings are successful, you need to add some DNS servers. Some " -"options:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:81 -#: aeed9b7f61534e3f95b805dde17b42dd -msgid "You should now be able to ping something by IPv6 DNS name:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:100 -#: a736ca5cd747403e8c14e673245d821e -msgid "LAN Configuration" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:102 -#: 1112b0d0ef1d4918a7ebca59efac58e4 -msgid "" -"At this point, your VyOS install should have full IPv6, but now your LAN " -"devices need access." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:105 -#: 1a65570c0367426c9a4f873d63f4942e -msgid "With Tunnelbroker.net, you have two options:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:107 -#: 3c6a7c5ec4ea449fa91711d03dac4c3b -msgid "" -"Routed /64. This is the default assignment. In IPv6-land, it's good for a " -"single \"LAN\", and is somewhat equivalent to a /24." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:110 -#: 29591255e2fd43a8b7fa1644284d59e1 -msgid "" -"Routed /48. This is something you can request by clicking the \"Assign /48\"" -" link in the Tunnelbroker.net tunnel config. It allows you to have up to 65k" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:113 -#: 67cd1fd9c371469c86c53c680bb79daf -msgid "" -"Unlike IPv4, IPv6 is really not designed to be broken up smaller than /64. " -"So if you ever want to have multiple LANs, VLANs, DMZ, etc, you'll want to " -"ignore the assigned /64, and request the /48 and use that." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:119 -#: 4f74d70dd2874430ae4b1614cd2d2739 -msgid "Single LAN Setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:121 -#: 2df56212558149feb9fd81bb336775fa -msgid "" -"Single LAN setup where eth2 is your LAN interface. Use the Tunnelbroker " -"Routed /64 prefix:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:128 -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:195 -#: 13574cf1c9174aa6b9237ea264787b9a 1c15190bf24244529f6ed886c2ef9c2e -msgid "" -"Please note, 'autonomous-flag' and 'on-link-flag' are enabled by default, " -"'valid-lifetime' and 'preferred-lifetime' are set to default values of 30 " -"days and 4 hours respectively." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:132 -#: 023eef0d8ac74055a7706a8605b9a7eb -msgid "" -"And the ``client`` to receive an IPv6 address with stateless autoconfig." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:137 -#: f83b8f3084da425dbc98cb5a735692d9 -msgid "This accomplishes a few things:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:139 -#: 10c4928833d54de2905620ff414d3954 -msgid "Sets your LAN interface's IP address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:140 -#: 49ca773f9de54f74b956dae477d7e0a8 -msgid "" -"Enables router advertisements. This is an IPv6 alternative for DHCP (though " -"DHCPv6 can still be used). With RAs, Your devices will automatically find " -"the information they need for routing and DNS." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:144 -#: b7b7e14f124c43be8e51f03ad82aaff1 -msgid "Now the Client is able to ping a public IPv6 address" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:162 -#: d73b8a6e7c8a47b8a0b44b9542eb3945 -msgid "Multiple LAN/DMZ Setup" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:164 -#: 17df49416ec247fdb8f8862ec2ec8dc3 -msgid "" -"That's how you can expand the example above. Use the `Routed /48` " -"information. This allows you to assign a different /64 to every interface, " -"LAN, or even device. Or you could break your network into smaller chunks " -"like /56 or /60." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:169 -#: e4872a8b039f4965ba7db797feb6ce70 -msgid "The format of these addresses:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:171 -#: a680481984ce4e3cba3147ace39339f2 -msgid "" -"`2001:470:xxxx::/48`: The whole subnet. xxxx should come from Tunnelbroker." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:172 -#: 8811a6910f0d41029f75986a4051e439 -msgid "`2001:470:xxxx:1::/64`: A subnet suitable for a LAN" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:173 -#: 0be6cdcfbf9b494d972beb120cbff231 -msgid "`2001:470:xxxx:2::/64`: Another subnet" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:174 -#: 048263091af848179c2b55a901b94f6f -msgid "`2001:470:xxxx:ffff:/64`: The last usable /64 subnet." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:176 -#: 1544240be6e040c3b2316d2bb28a83b9 -msgid "" -"In the above examples, 1,2,ffff are all chosen by you. You can use 1-ffff " -"(1-65535)." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:179 -#: 9555909b8f964a02a14bf995b7370a81 -msgid "" -"So, when your LAN is eth1, your DMZ is eth2, your cameras are on eth3, etc:" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:200 -#: 79d2a568ce054e6f82dcd8208b682cd4 -msgid "Firewall" -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:202 -#: bdb36fc61be6473681e2d4013d05cc20 -msgid "" -"Finally, don't forget the :ref:`firewall`. The usage is identical, except " -"for instead of `set firewall name NAME`, you would use `set firewall " -"ipv6-name NAME`." -msgstr "" - -#: ../../configexamples/autotest/tunnelbroker/tunnelbroker.rst:206 -#: 45493d140daa4adb80535f448eebc499 -msgid "" -"Similarly, to attach the firewall, you would use `set interfaces ethernet " -"eth0 firewall in ipv6-name` or `set firewall zone LOCAL from WAN firewall " -"ipv6-name`." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po deleted file mode 100644 index 78b45e28..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-bgp.po +++ /dev/null @@ -1,179 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/azure-vpn-bgp.rst:6 f83fa44add8c41fab8110d1f2e321206 -msgid "Route-Based Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:8 534f72f752e84afb8b770ad8a53a1bd5 -msgid "" -"This guide shows an example of a route-based IKEv2 site-to-site VPN to Azure" -" using VTI and BGP for dynamic routing updates." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:11 049d04f68cd44accb87923158043df03 -msgid "" -"For redundant / active-active configurations see :ref:`examples-azure-vpn-" -"dual-bgp`" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:16 54fc3df452904c5ea43d99c856544676 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:18 abec6e0963af4d7fbe1c1162390d4a60 -msgid "" -"A pair of Azure VNet Gateways deployed in active-passive configuration with " -"BGP enabled." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:21 22aeb09e6d9344c4be9e08c70c779758 -msgid "" -"A local network gateway deployed in Azure representing the Vyos device, " -"matching the below Vyos settings except for address space, which only " -"requires the Vyos private IP, in this example 10.10.0.5/32" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:26 e6783a61f8d54c33a95e58407aea2c46 -msgid "" -"A connection resource deployed in Azure linking the Azure VNet gateway and " -"the local network gateway representing the Vyos device." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:31 f6198f4f4b574ab7b36ae8f6ee5dc732 -msgid "Example" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:34 cc5a2912e07c44bfb396b9262365fc92 -msgid "WAN Interface" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:34 df85aea4568748798a33025246e4f9ff -msgid "eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:36 20ce51d06a40433d84365d4573b1c4bd -msgid "On-premises address space" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:36 46b911f0e0634cd99a4106fb467df923 -msgid "10.10.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:38 e7d5f286aec147fcaee08602adc1d133 -msgid "Azure address space" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:38 69d765b32e0f4434ab5158857004439d -msgid "10.0.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:40 806362f58c034acbb2ccd5390bfa3a3f -msgid "Vyos public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:40 a09e867c84484ac0b7c657ce599b4d76 -msgid "198.51.100.3" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:42 6680466007f8459b8859bba84a6ef5f0 -msgid "Vyos private IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:42 05581a563fb248cfbce55b48fc9b516c -msgid "10.10.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:44 ab851443a7a74c0dbd76a3d9c2b741ae -msgid "Azure VNet Gateway public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:44 76422c1c147445248b6990ab012ca135 -msgid "203.0.113.2" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:46 aca3077ca2d946bbb13bfe1d5bc3b9fd -msgid "Azure VNet Gateway BGP IP" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:46 4d0cb52280314731a2b791c9ac669e5f -msgid "10.0.0.4" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:48 4170c65ca13340a49596468c75bfeb01 -msgid "Pre-shared key" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:48 240e9cc921f447b897bdbf946b707747 -msgid "ch00s3-4-s3cur3-psk" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:50 4eb2ac883ece41aa9e8d90fb835c8f29 -msgid "Vyos ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:50 f19b0284d6d747f1abea3cd22b340a78 -msgid "64499" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:52 7592137fa3bf405d9bc5c9a66d0c91ec -msgid "Azure ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:52 1a542064bc174d668ec6c1701490a076 -msgid "65540" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:56 bca5f6372b374ec19f70a3d2ec0ca67e -msgid "Vyos configuration" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:58 e2d8a5f4046240d0a23ca4e3fd684639 -msgid "" -"Configure the IKE and ESP settings to match a subset of those supported by " -"Azure:" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:80 6d547d6d1fa14ccc8948bceef68615b4 -msgid "Enable IPsec on eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:86 62b5ee4ee0924f2cab8739de17862612 -msgid "Configure a VTI with a dummy IP address" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:93 75d6082877044b21a8352a52d5887883 -msgid "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:99 3a6c4bc871fe4c048e7ead2f2d1eda9a -msgid "Configure the VPN tunnel" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:115 f49b5c5e37e24e1689dddc469c4608ea -msgid "**Important**: Add an interface route to reach Azure's BGP listener" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:121 7714f19656884885a022c6df481adf48 -msgid "Configure your BGP settings" -msgstr "" - -#: ../../configexamples/azure-vpn-bgp.rst:131 a3b60878de2a436a895eac195a191428 -msgid "**Important**: Disable connected check \\" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po deleted file mode 100644 index c734bab6..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/azure-vpn-dual-bgp.po +++ /dev/null @@ -1,222 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:6 -#: 9b9db6fa09124662b2a7c3335dbc144a -msgid "Route-Based Redundant Site-to-Site VPN to Azure (BGP over IKEv2/IPsec)" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:8 -#: 759fb45f3bf44f8fa56771e2b1d8299f -msgid "" -"This guide shows an example of a redundant (active-active) route-based IKEv2" -" site-to-site VPN to Azure using VTI and BGP for dynamic routing updates." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:13 -#: 73abec87c3ca4f83b32d667d2263bfa1 -msgid "Prerequisites" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:15 -#: 18c0980f9b09457f82b75d3473ff7764 -msgid "" -"A pair of Azure VNet Gateways deployed in active-active configuration with " -"BGP enabled." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:18 -#: 5c5653cb683f464fb3b5880c79c617ac -msgid "" -"A local network gateway deployed in Azure representing the Vyos device, " -"matching the below Vyos settings except for address space, which only " -"requires the Vyos private IP, in this example 10.10.0.5/32" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:23 -#: bbfc8956ac7443eba627417fdf67d024 -msgid "" -"A connection resource deployed in Azure linking the Azure VNet gateway and " -"the local network gateway representing the Vyos device." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:28 -#: e6ff621563b042338d4425002ae8a78b -msgid "Example" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:31 -#: 716721a06b7f4669a9b2409eb2aac65d -msgid "WAN Interface" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:31 -#: dfcb3352016049a98f1d3c0b0be32998 -msgid "eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:33 -#: 5d959b80a81f430f9d86a26a9ad19c3e -msgid "On-premises address space" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:33 -#: a3ceef7fc78c48949eb6c0eeae0b667a -msgid "10.10.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:35 -#: 80e725a06e004cc69f8ee875fcc6dfa8 -msgid "Azure address space" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:35 -#: 6d16c5efb5d745cf95e8ff423757616b -msgid "10.0.0.0/16" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:37 -#: ee5c0ac6e9014725a3fd16837ae0e288 -msgid "Vyos public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:37 -#: fc806f5176d946a9805e3f7baf40c7ce -msgid "198.51.100.3" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:39 -#: e846499ba5d248af818ff80cd6910265 -msgid "Vyos private IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:39 -#: 5e6a6539cd5e45ac9e8f1f9b07c0fc86 -msgid "10.10.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:41 -#: 90a33f04bce84814be2fb2de47ee9af5 -msgid "Azure VNet Gateway 1 public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:41 -#: 0559c71d81a6400fb5029149976df8d7 -msgid "203.0.113.2" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:43 -#: b834b0cd721542aba5842057601df99e -msgid "Azure VNet Gateway 2 public IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:43 -#: 494e561c165342a995c23b36a38b97f4 -msgid "203.0.113.3" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:45 -#: 801eca976a174615b5cd752c1646d5b6 -msgid "Azure VNet Gateway BGP IP" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:45 -#: 1dd2e30409cb4e1da1af32da8e2ef380 -msgid "10.0.0.4,10.0.0.5" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:47 -#: 500be57e62db42f5a73ba13af5f90661 -msgid "Pre-shared key" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:47 -#: f4e179a9bbd249d0b23c6d6e252a1365 -msgid "ch00s3-4-s3cur3-psk" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:49 -#: 16b7665d8270452080540cc94e6ee8fa -msgid "Vyos ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:49 -#: 9250aa14f188401d9e4778537e44a36d -msgid "64499" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:51 -#: 4f57f84278e84e15af808cd47888d74c -msgid "Azure ASN" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:51 -#: c583b170be9e4aeaaff113835ebee4e1 -msgid "65540" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:55 -#: 58d06a64237740d5921366d353c0cc2e -msgid "Vyos configuration" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:57 -#: 8752f9b33a9745629c606f160f9f2e18 -msgid "" -"Configure the IKE and ESP settings to match a subset of those supported by " -"Azure:" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:79 -#: f91c7ac88fd64a51afaa2497ea5c97a0 -msgid "Enable IPsec on eth0" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:85 -#: b00fe5e7ffe24f7caf9c9ec2145cf006 -msgid "Configure two VTIs with a dummy IP address each" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:95 -#: c78f7df8e90f48d398ddfdf6f25403a1 -msgid "Clamp the VTI's MSS to 1350 to avoid PMTU blackholes." -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:102 -#: 6bad30973bc846639ab878dcf67cbb4f -msgid "Configure the VPN tunnels" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:130 -#: 44e9904045894f43baea76edb6326273 -msgid "" -"**Important**: Add an interface route to reach both Azure's BGP listeners" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:137 -#: e86362b48b914a9285d07293c4dfc900 -msgid "Configure your BGP settings" -msgstr "" - -#: ../../configexamples/azure-vpn-dual-bgp.rst:152 -#: 8eff32668c1d4fef849d705526783f9d -msgid "" -"**Important**: Disable connected check, otherwise the routes learned from " -"Azure will not be imported into the routing table." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po deleted file mode 100644 index d6106abd..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/bgp-ipv6-unnumbered.po +++ /dev/null @@ -1,50 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:7 -#: d09ae8126681462993e92d093899abfd -msgid "BGP IPv6 unnumbered with extended nexthop" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:9 -#: 32a43eae8561459abb680e6c4ed1e083 -msgid "General information can be found in the :ref:`routing-bgp` chapter." -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:12 -#: 79b61cb0a1b049fdbe7cd106aeefbc98 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:14 -#: ../../configexamples/bgp-ipv6-unnumbered.rst:57 -#: 4cec5409b9554b65a3f193999725cc79 4e82bbee18eb49fca04f67464cd968e1 -msgid "Router A:" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:34 -#: ../../configexamples/bgp-ipv6-unnumbered.rst:118 -#: 56a2def17e61479c80767f815f9c2c34 4a9918e9212a49ca8899c41058c15724 -msgid "Router B:" -msgstr "" - -#: ../../configexamples/bgp-ipv6-unnumbered.rst:55 -#: 4abe7ac3ae0b4dd79f948dc26d129037 -msgid "Results" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po deleted file mode 100644 index 0bcd885d..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ha.po +++ /dev/null @@ -1,598 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/ha.rst:7 6635636e1b2848cdaff0110647b1a93a -msgid "High Availability Walkthrough" -msgstr "" - -#: ../../configexamples/ha.rst:9 328dc19e47f3451c94a92ab9fd1d91be -msgid "" -"This document walks you through a complete HA setup of two VyOS machines. " -"This design is based on a VM as the primary router and a physical machine as" -" a backup, using VRRP, BGP, OSPF, and conntrack sharing." -msgstr "" - -#: ../../configexamples/ha.rst:13 f3fa38c6974646a1bee041f198e3bc34 -msgid "" -"This document aims to walk you through setting everything up, so at a point " -"where you can reboot any machine and not lose more than a few seconds worth " -"of connectivity." -msgstr "" - -#: ../../configexamples/ha.rst:18 cd75d9827a5e47f0b243e5ac7c9c1526 -msgid "Design" -msgstr "" - -#: ../../configexamples/ha.rst:20 e7dd91e9f3b84f5f8b058f7ec1f550e3 -msgid "" -"This is based on a real-life production design. One of the complex issues is" -" ensuring you have redundant data INTO your network. We do this with a pair " -"of Cisco Nexus switches and using Virtual PortChannels that are spanned " -"across them. As a bonus, this also allows for complete switch failure " -"without an outage. How you achieve this yourself is left as an exercise to " -"the reader. But our setup is documented here." -msgstr "" - -#: ../../configexamples/ha.rst:28 a8c9be49e8834a5989d661c13939f74d -msgid "Walkthrough suggestion" -msgstr "" - -#: ../../configexamples/ha.rst:30 5107a6fd819845d6bfe5da4bbc5cd410 -msgid "" -"The ``commit`` command is implied after every section. If you make an error," -" ``commit`` will warn you and you can fix it before getting too far into " -"things. Please ensure you commit early and commit often." -msgstr "" - -#: ../../configexamples/ha.rst:34 9b466ae1e3084c2487fa455690176700 -msgid "" -"If you are following through this document, it is strongly suggested you " -"complete the entire document, ONLY doing the virtual router1 steps, and then" -" come back and walk through it AGAIN on the backup hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:38 45de19cee0d54c2b8dcc4e176eb9cf7a -msgid "" -"This ensures you don't go too fast or miss a step. However, it will make " -"your life easier to configure the fixed IP address and default route now on " -"the hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:43 4ff61bf6bb484462be110aba531c24ad -msgid "Example Network" -msgstr "" - -#: ../../configexamples/ha.rst:45 e5762566a37b47e9956fce030e9219eb -msgid "" -"In this document, we have been allocated 203.0.113.0/24 by our upstream " -"provider, which we are publishing on VLAN100." -msgstr "" - -#: ../../configexamples/ha.rst:48 f8c62807293d4310af27b812215c71eb -msgid "" -"They want us to establish a BGP session to their routers on 192.0.2.11 and " -"192.0.2.12 from our routers 192.0.2.21 and 192.0.2.22. They are AS 65550 and" -" we are AS 65551." -msgstr "" - -#: ../../configexamples/ha.rst:52 f5c58c9d490245f8a4a137b7e716a599 -msgid "" -"Our routers are going to have a floating IP address of 203.0.113.1, and use " -".2 and .3 as their fixed IPs." -msgstr "" - -#: ../../configexamples/ha.rst:55 858e51844e7a46ae8f90e89347793ba7 -msgid "" -"We are going to use 10.200.201.0/24 for an 'internal' network on VLAN201." -msgstr "" - -#: ../../configexamples/ha.rst:57 ad0d8fa61ad84a79bcda13f5c24035f6 -msgid "" -"When traffic is originated from the 10.200.201.0/24 network, it will be " -"masqueraded to 203.0.113.1" -msgstr "" - -#: ../../configexamples/ha.rst:60 8c41661f7f0d47909e9cd9b41488f2fb -msgid "" -"For connection between sites, we are running a WireGuard link to two REMOTE " -"routers and using OSPF over those links to distribute routes. That remote " -"site is expected to send traffic from anything in 10.201.0.0/16" -msgstr "" - -#: ../../configexamples/ha.rst:65 61fe940554c040708bee57444169fa8e -msgid "VLANs" -msgstr "" - -#: ../../configexamples/ha.rst:67 8e8acb9d0feb48a48864e4d5a334b49c -msgid "These are the vlans we will be using:" -msgstr "" - -#: ../../configexamples/ha.rst:69 1d1fdf6d8f2248ee80b33f9c4156323b -msgid "50: Upstream, using the 192.0.2.0/24 network allocated by them." -msgstr "" - -#: ../../configexamples/ha.rst:70 1c606178267146308a748c1680340a5b -msgid "100: 'Public' network, using our 203.0.113.0/24 network." -msgstr "" - -#: ../../configexamples/ha.rst:71 ceb5aa6290cb496e8862dbdc9810eeed -msgid "201: 'Internal' network, using 10.200.201.0/24" -msgstr "" - -#: ../../configexamples/ha.rst:74 ed3303e4df4f47a6a44b1c4e563eef9f -msgid "Hardware" -msgstr "" - -#: ../../configexamples/ha.rst:76 6c8cc0e1d2ba4e068a9a56edab17035e -msgid "switch1 (Nexus 10gb Switch)" -msgstr "" - -#: ../../configexamples/ha.rst:77 2b8ca1bfc14b4f889f6250d8bb9cefd1 -msgid "switch2 (Nexus 10gb Switch)" -msgstr "" - -#: ../../configexamples/ha.rst:78 24ba0c7bad77467fa78e8b78dc3e6511 -msgid "compute1 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:79 cb94b9b3258a4e499cc77606f027e53e -msgid "compute2 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:80 e8bfef4d8cf744f785f31e6fab83f0e2 -msgid "compute3 (VMware ESXi 6.5)" -msgstr "" - -#: ../../configexamples/ha.rst:81 3201e0706ae44014a8c66fbcdf98396d -msgid "router2 (Random 1RU machine with 4 NICs)" -msgstr "" - -#: ../../configexamples/ha.rst:83 1fcc6ca17f1c43c7a8f06987e57f9b0e -msgid "Note that router1 is a VM that runs on one of the compute nodes." -msgstr "" - -#: ../../configexamples/ha.rst:86 0de10057e9b6488e829ed5a52d9ddbc9 -msgid "Network Cabling" -msgstr "" - -#: ../../configexamples/ha.rst:88 c635e244c7954a5b9a920bb7d5eee4ff -msgid "" -"From Datacenter - This connects into port 1 on both switches, and is tagged " -"as VLAN 50" -msgstr "" - -#: ../../configexamples/ha.rst:90 3db2a959fe2b43c389856f9ec845c94a -msgid "Cisco VPC Crossconnect - Ports 39 and 40 bonded between each switch" -msgstr "" - -#: ../../configexamples/ha.rst:91 887ffd05a80d4ed3b8237e0937efd045 -msgid "Hardware Router - Port 8 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:92 dbcb6bca65914da7828f17d1cd0012cb -msgid "compute1 - Port 9 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:93 58f7491bce3049d4b855c840bbd278c2 -msgid "compute2 - Port 10 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:94 67b8ad69203a49f6a1f3f51db1340ba0 -msgid "compute3 - Port 11 of each switch" -msgstr "" - -#: ../../configexamples/ha.rst:96 922733c2845c439281cf4ae28367406d -msgid "" -"This is ignoring the extra Out-of-band management networking, which should " -"be on totally different switches, and a different feed into the rack, and is" -" out of scope of this." -msgstr "" - -#: ../../configexamples/ha.rst:100 ff780c97cb90413796269eb194ae6b07 -msgid "" -"Our implementation uses VMware's Distributed Port Groups, which allows " -"VMware to use LACP. This is a part of the ENTERPRISE licence, and is not " -"available on a free licence. If you are implementing this and do not have " -"access to DPGs, you should not use VMware, and use some other virtualization" -" platform instead." -msgstr "" - -#: ../../configexamples/ha.rst:108 a84f52e0e1d64b0aa9fc5a0c773d7602 -msgid "Basic Setup (via console)" -msgstr "" - -#: ../../configexamples/ha.rst:110 200c203631fd4a4b8aaebed5bf35b9fb -msgid "" -"Create your router1 VM. So it can withstand a VM Host failing or a network " -"link failing. Using VMware, this is achieved by enabling vSphere DRS, " -"vSphere Availability, and creating a Distributed Port Group that uses LACP." -msgstr "" - -#: ../../configexamples/ha.rst:114 56302a6a7a91496b8b2812c697f399f2 -msgid "" -"Many other Hypervisors do this, and I'm hoping that this document will be " -"expanded to document how to do this for others." -msgstr "" - -#: ../../configexamples/ha.rst:117 16738dc1523d4c9d89cd0721071045e1 -msgid "" -"Create an 'All VLANs' network group, that passes all trunked traffic through" -" to the VM. Attach this network group to router1 as eth0." -msgstr "" - -#: ../../configexamples/ha.rst:120 c95508528a7b44baa796c0145a6f1c82 -msgid "" -"VMware: You must DISABLE SECURITY on this Port group. Make sure that " -"``Promiscuous Mode``\\ , ``MAC address changes`` and ``Forged transmits`` " -"are enabled. All of these will be done as part of failover." -msgstr "" - -#: ../../configexamples/ha.rst:125 e73697b70e1146d895921faf43c2af71 -msgid "Bonding on Hardware Router" -msgstr "" - -#: ../../configexamples/ha.rst:127 ddaaa893a69f44cb984a0c51e15a6e5f -msgid "" -"Create a LACP bond on the hardware router. We are assuming that eth0 and " -"eth1 are connected to port 8 on both switches, and that those ports are " -"configured as a Port-Channel." -msgstr "" - -#: ../../configexamples/ha.rst:141 169cb700875f4be98c4dce46ffa51ca5 -msgid "Assign external IP addresses" -msgstr "" - -#: ../../configexamples/ha.rst:143 968533e09d8e4ff2a10eced097e77e09 -msgid "" -"VLAN 100 and 201 will have floating IP addresses, but VLAN50 does not, as " -"this is talking directly to upstream. Create our IP address on vlan50." -msgstr "" - -#: ../../configexamples/ha.rst:146 66ee1b962118455aa159df42da77deb1 -msgid "" -"For the hardware router, replace ``eth0`` with ``bond0``. As (almost) every " -"command is identical, this will not be specified unless different things " -"need to be performed on different hosts." -msgstr "" - -#: ../../configexamples/ha.rst:154 59a6738568c540f1949fe02d4fcf34cc -msgid "In this case, the hardware router has a different IP, so it would be" -msgstr "" - -#: ../../configexamples/ha.rst:161 3e40d84c53a04d9eb0d6809ccc20b7b2 -msgid "Add (temporary) default route" -msgstr "" - -#: ../../configexamples/ha.rst:163 de5087605cf546c68ee58e5687e5f92a -msgid "" -"It is assumed that the routers provided by upstream are capable of acting as" -" a default router, add that as a static route." -msgstr "" - -#: ../../configexamples/ha.rst:174 a79c996cc6f64b5eb9fbdee8f7a226cf -msgid "Enable SSH" -msgstr "" - -#: ../../configexamples/ha.rst:176 551ce6f349f647d2b9d4ea9deff17487 -msgid "" -"Enable SSH so you can now SSH into the routers, rather than using the " -"console." -msgstr "" - -#: ../../configexamples/ha.rst:184 fada2faa8d5046bd96ca04b615f816b3 -msgid "" -"At this point, you should be able to SSH into both of them, and will no " -"longer need access to the console (unless you break something!)" -msgstr "" - -#: ../../configexamples/ha.rst:189 874f028d74c2487e872a241eedb25679 -msgid "VRRP Configuration" -msgstr "" - -#: ../../configexamples/ha.rst:191 5cb0eca9555b466eb78c771fbec62eba -msgid "" -"We are setting up VRRP so that it does NOT fail back when a machine returns " -"into service, and it prioritizes router1 over router2." -msgstr "" - -#: ../../configexamples/ha.rst:195 134f86480d6846d19b2a5c475d9a09f9 -msgid "Internal Network" -msgstr "" - -#: ../../configexamples/ha.rst:197 f5ecaa7e6a99408cbc48e6191f936e12 -msgid "" -"This has a floating IP address of 10.200.201.1/24, using virtual router ID " -"201. The difference between them is the interface name, hello-source-" -"address, and peer-address." -msgstr "" - -#: ../../configexamples/ha.rst:201 ../../configexamples/ha.rst:237 -#: ../../configexamples/ha.rst:366 ../../configexamples/ha.rst:540 -#: 024e10c2ef1d45538b14d1441b2aba12 4ff23649975144ea8761a1f0db9fc38b -#: ead03513ccf349d69a72ad719341ccc0 3b0bc4b0e37242ea9b06d4a5fd523b51 -msgid "**router1**" -msgstr "" - -#: ../../configexamples/ha.rst:215 ../../configexamples/ha.rst:250 -#: ../../configexamples/ha.rst:581 64a85b10ff4940fe834992340e3d79e9 -#: d5a58d53fb57403a93d109ea8f0499b8 b0c10d042e1b4aa7aebd7cbbb4359cff -msgid "**router2**" -msgstr "" - -#: ../../configexamples/ha.rst:230 c02ad28f7389436488aa2f0667a4c92a -msgid "Public Network" -msgstr "" - -#: ../../configexamples/ha.rst:232 6ba11351d94e405ca551816733f5d6a7 -msgid "" -"This has a floating IP address of 203.0.113.1/24, using virtual router ID " -"113. The virtual router ID is just a random number between 1 and 254, and " -"can be set to whatever you want. Best practices suggest you try to keep them" -" unique enterprise-wide." -msgstr "" - -#: ../../configexamples/ha.rst:265 5cc83f7b616a4ba094220576cb889002 -msgid "Create VRRP sync-group" -msgstr "" - -#: ../../configexamples/ha.rst:267 7ecafb24ca98488b8f1415f33752a416 -msgid "" -"The sync group is used to replicate connection tracking. It needs to be " -"assigned to a random VRRP group, and we are creating a sync group called " -"``sync`` using the vrrp group ``int``." -msgstr "" - -#: ../../configexamples/ha.rst:276 ../../configexamples/ha.rst:337 -#: 0c50ea68a8144106bada8d98ee2c0b35 ce7487619dbe4873a0e344be20f23baf -msgid "Testing" -msgstr "" - -#: ../../configexamples/ha.rst:278 8bfcd793743d4ff0a4b8de2e4d72977d -msgid "" -"At this point, you should be able to see both IP addresses when you run " -"``show interfaces``\\ , and ``show vrrp`` should show both interfaces in " -"MASTER state (and SLAVE state on router2)." -msgstr "" - -#: ../../configexamples/ha.rst:292 0fb62e4241214eb89230fb03c7372d34 -msgid "You should be able to ping to and from all the IPs you have allocated." -msgstr "" - -#: ../../configexamples/ha.rst:295 aa72fecb45c44884a1139c0375451e82 -msgid "NAT and conntrack-sync" -msgstr "" - -#: ../../configexamples/ha.rst:297 eded51367628479d8b4117240d6478eb -msgid "" -"Masquerade Traffic originating from 10.200.201.0/24 that is heading out the " -"public interface." -msgstr "" - -#: ../../configexamples/ha.rst:300 5451f8ac48d346bda205c19c2c4691bd -msgid "" -"We explicitly exclude the primary upstream network so that BGP or OSPF " -"traffic doesn't accidentally get NAT'ed." -msgstr "" - -#: ../../configexamples/ha.rst:312 5d204005a8004750afc2d562b5dc1a33 -msgid "Configure conntrack-sync and enable helpers" -msgstr "" - -#: ../../configexamples/ha.rst:314 43870f92ca894847be0108d6643fdbf0 -msgid "" -"Conntrack helper modules are enabled by default, but they tend to cause more" -" problems than they're worth in complex networks. You can disable all of " -"them at one go." -msgstr "" - -#: ../../configexamples/ha.rst:322 f38092677ae4464187fe29eda38f2ae8 -msgid "" -"Now enable replication between nodes. Replace eth0.201 with bond0.201 on the" -" hardware router." -msgstr "" - -#: ../../configexamples/ha.rst:339 2860f289aac74a5687ebd85c0487d8e9 -msgid "" -"The simplest way to test is to look at the connection tracking stats on the " -"standby hardware router with the command ``show conntrack-sync statistics``." -" The numbers should be very close to the numbers on the primary router." -msgstr "" - -#: ../../configexamples/ha.rst:343 2754bcacb8b141ffb07a28ac712e5f0f -msgid "" -"When you have both routers up, you should be able to establish a connection " -"from a NAT'ed machine out to the internet, reboot the active machine, and " -"that connection should be preserved, and will not drop out." -msgstr "" - -#: ../../configexamples/ha.rst:348 7926537525124f4ba89416e2b9c2b296 -msgid "OSPF Over WireGuard" -msgstr "" - -#: ../../configexamples/ha.rst:350 eb10c0fc01ad4eadbd69a27512fa8cff -msgid "" -"Wireguard doesn't have the concept of an up or down link, due to its design." -" This complicates AND simplifies using it for network transport, as for " -"reliable state detection you need to use SOMETHING to detect when the link " -"is down." -msgstr "" - -#: ../../configexamples/ha.rst:354 34792be20b6a4dc2a479d4fd1eb38c5a -msgid "" -"If you use a routing protocol itself, you solve two problems at once. This " -"is only a basic example, and is provided as a starting point." -msgstr "" - -#: ../../configexamples/ha.rst:358 07fe314c1d244c58918fbec62add102c -msgid "Configure Wireguard" -msgstr "" - -#: ../../configexamples/ha.rst:360 79d18f239c9d47e89a9ea9d3e6c8b7d6 -msgid "" -"There is plenty of instructions and documentation on setting up Wireguard. " -"The only important thing you need to remember is to only use one WireGuard " -"interface per OSPF connection." -msgstr "" - -#: ../../configexamples/ha.rst:364 6e2c049a5e2b4d6b9c9de79ba7dcfcc3 -msgid "We use small /30's from 10.254.60/24 for the point-to-point links." -msgstr "" - -#: ../../configexamples/ha.rst:368 6313ed08caa34dfa8dc53630ad69e9cb -msgid "" -"Replace the 203.0.113.3 with whatever the other router's IP address is." -msgstr "" - -#: ../../configexamples/ha.rst:389 82b6b6db1dc44350b4cbc8e8a314eae6 -msgid "**offsite1**" -msgstr "" - -#: ../../configexamples/ha.rst:391 b355d228c62349df8cff68502b2d1b29 -msgid "This is connecting back to the STATIC IP of router1, not the floating." -msgstr "" - -#: ../../configexamples/ha.rst:412 d625b918b5054ea1be331cc13b37e9f2 -msgid "Test WireGuard" -msgstr "" - -#: ../../configexamples/ha.rst:414 79ca90a7810649a39de3f4757d54fe5f -msgid "Make sure you can ping 10.254.60.1 and .2 from both routers." -msgstr "" - -#: ../../configexamples/ha.rst:417 ea2eda10fd404f6eb09c00f3a56609d1 -msgid "Create Export Filter" -msgstr "" - -#: ../../configexamples/ha.rst:419 1781368cc3fb4fa8a7fef2ca50fd2238 -msgid "" -"We only want to export the networks we know. Always do a whitelist on your " -"route filters, both importing and exporting. A good rule of thumb is **'If " -"you are not the default router for a network, don't advertise it'**. This " -"means we explicitly do not want to advertise the 192.0.2.0/24 network (but " -"do want to advertise 10.200.201.0 and 203.0.113.0, which we ARE the default " -"route for). This filter is applied to ``redistribute connected``. If we WERE" -" to advertise it, the remote machines would see 192.0.2.21 available via " -"their default route, establish the connection, and then OSPF would say " -"'192.0.2.0/24 is available via this tunnel', at which point the tunnel would" -" break, OSPF would drop the routes, and then 192.0.2.0/24 would be reachable" -" via default again. This is called 'flapping'." -msgstr "" - -#: ../../configexamples/ha.rst:448 3fa81ded7b2b4191977371b88e9c359c -msgid "Create Import Filter" -msgstr "" - -#: ../../configexamples/ha.rst:450 3908a1799dea49648304c5e91a236abf -msgid "" -"We only want to import networks we know. Our OSPF peer should only be " -"advertising networks in the 10.201.0.0/16 range. Note that this is an " -"INVERSE MATCH. You deny in access-list 100 to accept the route." -msgstr "" - -#: ../../configexamples/ha.rst:470 0d63d8b7e349423689b890c3fbe79241 -msgid "Enable OSPF" -msgstr "" - -#: ../../configexamples/ha.rst:472 9d6650db6fd84a4b91a026c32f4cb9fd -msgid "" -"Every router **must** have a unique router-id. The 'reference-bandwidth' is " -"used because when OSPF was originally designed, the idea of a link faster " -"than 1gbit was unheard of, and it does not scale correctly." -msgstr "" - -#: ../../configexamples/ha.rst:489 6ebb88d1d9ca46488180f5a76ef013d9 -msgid "Test OSPF" -msgstr "" - -#: ../../configexamples/ha.rst:491 812917c76e66417e8eb1ae6a4a48b711 -msgid "" -"When you have enabled OSPF on both routers, you should be able to see each " -"other with the command ``show ip ospf neighbour``. The state must be 'Full' " -"or '2-Way'. If it is not, then there is a network connectivity issue between" -" the hosts. This is often caused by NAT or MTU issues. You should not see " -"any new routes (unless this is the second pass) in the output of ``show ip " -"route``" -msgstr "" - -#: ../../configexamples/ha.rst:498 fc0e4249dc1449e2b16c6ed4d2970097 -msgid "Advertise connected routes" -msgstr "" - -#: ../../configexamples/ha.rst:500 30a19b02b06842b5854ddffa7b0f3ad9 -msgid "" -"As a reminder, only advertise routes that you are the default router for. " -"This is why we are NOT announcing the 192.0.2.0/24 network, because if that " -"was announced into OSPF, the other routers would try to connect to that " -"network over a tunnel that connects to that network!" -msgstr "" - -#: ../../configexamples/ha.rst:511 fdefb152353a413e8238054e3c158d8e -msgid "" -"You should now be able to see the advertised network on the other host." -msgstr "" - -#: ../../configexamples/ha.rst:514 76e146cffb1a47fdaae34f9c1a74d2a7 -msgid "Duplicate configuration" -msgstr "" - -#: ../../configexamples/ha.rst:516 9af13c626127489190a5475e554d0027 -msgid "" -"At this point, you now need to create the X link between all four routers. " -"Use amdifferent /30 for each link." -msgstr "" - -#: ../../configexamples/ha.rst:520 44602b1155fc4647a8d3de483e9f37c5 -msgid "Priorities" -msgstr "" - -#: ../../configexamples/ha.rst:522 bb7300e02c254e0bbae13bf9e5106d59 -msgid "" -"Set the cost on the secondary links to be 200. This means that they will not" -" be used unless the primary links are down." -msgstr "" - -#: ../../configexamples/ha.rst:531 9fe545f2929b484f83077b7c0a5c3a5e -msgid "This will be visible in 'show ip route'." -msgstr "" - -#: ../../configexamples/ha.rst:534 114fb5790b9c49fb8133c2a9fd5d2465 -msgid "BGP" -msgstr "" - -#: ../../configexamples/ha.rst:536 ec4424a0b26f40e985a844767d8916ee -msgid "" -"BGP is an extremely complex network protocol. An example is provided here." -msgstr "" - -#: ../../configexamples/ha.rst:538 db63ce80f3a14d99914fc0eeff1d8c29 -msgid "Router id's must be unique." -msgstr "" - -#: ../../configexamples/ha.rst:543 0d5527a10ee54fea8be1fd010b1b3af8 -msgid "" -"The ``redistribute ospf`` command is there purely as an example of how this " -"can be expanded. In this walkthrough, it will be filtered by BGPOUT rule " -"10000, as it is not 203.0.113.0/24." -msgstr "" - -#: ../../configexamples/ha.rst:583 569496a685d24d70a371a91381b90bf3 -msgid "" -"This is identical, but you use the BGPPREPENDOUT route-map to advertise the " -"route with a longer path." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po deleted file mode 100644 index ecf47379..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/index.po +++ /dev/null @@ -1,74 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/index.rst:4 221cdd3e723548398440f0bbb733d7d3 -msgid "Configuration Blueprints" -msgstr "" - -#: ../../configexamples/index.rst:6 af362a0bbe0343efb3c18e916f6eb5fa -msgid "This chapter contains various configuration examples:" -msgstr "" - -#: ../../configexamples/index.rst:24 6078e9736f7a4bf3871932455e83b281 -msgid "Configuration Blueprints (autotest)" -msgstr "" - -#: ../../configexamples/index.rst:26 7356a0291dfd4eef8b3548ffe16c6c3d -msgid "The next pages contains automatic full tested configuration examples." -msgstr "" - -#: ../../configexamples/index.rst:28 76e850e3a0b149f79fd0256fa46bd4b2 -msgid "" -"Each lab will build an test from an external script. The page content will " -"generate, so changes will not take an effect." -msgstr "" - -#: ../../configexamples/index.rst:31 d07c374b439e49e3bc9896a7315fe837 -msgid "" -"A host ``vyos-oobm`` will use as a ssh proxy. This host is just necessary " -"for the Lab test." -msgstr "" - -#: ../../configexamples/index.rst:34 886c86ce28bc41d8911370caa26d877f -msgid "The process will do the following steps:" -msgstr "" - -#: ../../configexamples/index.rst:36 5856e3be60d54e04bed197f4afccdd20 -msgid "create the lab on a eve-ng server" -msgstr "" - -#: ../../configexamples/index.rst:37 d942be2969a045e5a2a68b24d7ffccbe -msgid "configure each host in the lab" -msgstr "" - -#: ../../configexamples/index.rst:38 cc5afea66c11467fb2d0f65f86aeb8f3 -msgid "do some defined tests" -msgstr "" - -#: ../../configexamples/index.rst:39 c416622bee5e41aa82b6eaaef4d3ca15 -msgid "optional do an upgrade to a higher version and do step 3 again." -msgstr "" - -#: ../../configexamples/index.rst:40 448ae7b0c859456f81c549a1cf2e3a78 -msgid "generate the documentation and include files" -msgstr "" - -#: ../../configexamples/index.rst:41 50da447b745c4d14a81d72608448b992 -msgid "shutdown and destroy the lab, if there is no error" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po deleted file mode 100644 index dc6efef0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po +++ /dev/null @@ -1,575 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:3 -#: eb41ae1b116f44aca5187f22bd6e3c38 -msgid "Inter-VRF Routing over VRF Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:5 -#: f0616081b9784167ab9c07a7350cb12c -msgid "" -"**Virtual Routing and Forwarding** is a technology that allow multiple " -"instance of a routing table to exist within a single device. One of the key " -"aspect of **VRFs** is that do not share the same routes or interfaces, " -"therefore packets are forwarded between interfaces that belong to the same " -"VRF only." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:10 -#: ea59f5e8a5e6486d80e4e4d65d0de34c -msgid "" -"Any information related to a VRF is not exchanged between devices -or in the" -" same device- by default, this is a technique called **VRF-Lite**." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:13 -#: ac294973fcec422ea2769beb2f586a5d -msgid "" -"Keep networks isolated is -in general- a good principle, but there are cases" -" where you might need that some network can access other in a different VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:16 -#: 8b47e55fd64d400b96bd14a41ba2f2cd -msgid "" -"The scope of this document is to cover such cases in a dynamic way without " -"the use of MPLS-LDP." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:19 -#: 0a4d0fe3ed8948c685128f24ac43b5e2 -msgid "" -"General information about L3VPNs can be found in the " -":ref:`configuration/vrf/index:L3VPN VRFs` chapter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:23 -#: 4c8919e0683e407e853338762e005b73 -msgid "Overview" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:25 -#: 4649bebe3b9c452a983b440677eef8ef -msgid "Let’s say we have a requirement to have multiple networks." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:27 -#: 4adf12c76e3042d1aa0615aa93f6c028 -msgid "LAN 1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:28 -#: 2bb42d1b9104415db47557052928d2e8 -msgid "LAN 2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:29 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:727 -#: 9e0ca4a0df5f4fb88e8aeb21241714a2 7eecdf4e5fe844e39ce8c9bd6e275a30 -#: e12f1fbf318148dda9a8468e462ec0f0 9da4873cd37c45d2a1e9e6c8cce272f7 -msgid "Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:30 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: c81a9b48a8c045e2aed48642d26b13ab 091224a1afed4eac89b75bb783b866c4 -msgid "Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:32 -#: 99888ffd849e412cbad21c08b326160e -msgid "" -"Both LANs have to be able to route between each other, both will have " -"managed devices through a dedicated management network and both will need " -"Internet access yet the LAN2 will need access to some set of outside " -"networks, not all. The management network will need access to both LANs but " -"cannot have access to/from the outside." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:38 -#: 0f23fd96749846889ded22c066ef1961 -msgid "" -"This scenario could be a nightmare applying regular routing and might need " -"filtering in multiple interfaces." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:41 -#: 6ab38930088d40d7828f23898bd381d1 -msgid "" -"A simple solution could be using different routing tables, or VRFs for all " -"the networks so we can keep the routing restrictions. But for us to route " -"between the different VRFs we would need a cable or a logical connection " -"between each other:" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:46 -#: 5a813032fce9458eb29d0498989614da -msgid "One cable/logical connection between LAN1 and LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:47 -#: ef9bfefcf4104ea0b95f1a3b7a9ee796 -msgid "One cable/logical connection between LAN1 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:48 -#: 6462901ab71c4c9ba3bdd5ed60994278 -msgid "One cable/logical connection between LAN2 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:49 -#: d3f6c4a564e741508c3095bd738b4e0b -msgid "One cable/logical connection between LAN1 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:50 -#: 50efd8066bcb420fbf4f3e43a4b2ac4a -msgid "One cable/logical connection between LAN2 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:52 -#: 12a6f2d5993647ca884f54b7ea65424d -msgid "As we can see this is unpractical." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:54 -#: 86964e2fdcfe42b1acef7ebe5f6be8e7 -msgid "" -"To address this scenario we will use to our advantage an extension of the " -"BGP routing protocol that will help us in the “Export” between VRFs without " -"the need for MPLS." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:58 -#: 67c99502bfe344c18b2772fead0bfdef -msgid "" -"MP-BGP or MultiProtocol BGP introduces two main concepts to solve this " -"limitation: - Route Distinguisher (RD): Is used to distinguish between " -"different VRFs –called VPNs- inside the BGP Process. The RD is appended to " -"each IPv4 Network that is advertised into BGP for that VPN making it a " -"unique VPNv4 route. - Route Target (RT): This is an extended BGP community " -"append to the VPNv4 route in the Import/Export process. When a route passes " -"from the VRF routing table into the BGP process it will add the configured " -"export extended community(ies) for that VPN. When that route needs to go " -"from BGP into the VRF routing table will only pass if that given VPN import " -"policy matches any of the appended community(ies) into that prefix." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:72 -#: de34231c61084297b36ddb578477b67d -msgid "Topology" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rstNone -#: cdc1520b038842a68babb2a9a2525fc4 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:82 -#: 16f28c31e1f143c5986ab85cc840b32b -msgid "IP Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 40ae6d91025b43babf6a28156ac7500b -msgid "Device-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: c35074ba59f949b8a2a46f3811869080 -msgid "Device-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: bc3f51095ca3484f863d2762794aa0f8 -msgid "IPv4 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 72b11e54e57a4b439f2b75faa92ce102 -msgid "IPv6 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:616 -#: 3f41e5bfa21947be87ec7081d7ee8ba2 b54901e4a8b249f89f67b364fa24663d -#: 19cc658588fd4ebf9502ea26ea498d7a 02ad5c6d77bf461396340263ef2d3420 -#: 900ff739e58e4f79bf99a1f561c405b4 -msgid "Core" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:701 -#: 56574650a4194ff79d5645140cf03d6b f25b32ec296c44b7aa3458a0f9b44760 -#: 9b5243427ba34f7cbf9939103226d9b1 -msgid "LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: 2d1e1dc89c1f40318ed9748de6273f9f -msgid "10.1.1.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: cbe4082191094f4bab8916aef6f9a5c0 -msgid "2001:db8::/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:713 -#: 65ddfdbbfa3b4c349173b73a2fa3356f b7f31fe8dd854681bb11900e87d1f179 -#: 5734149a4be547639059a2cdd24050e8 -msgid "LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: b7c3c79b8c4842cca5336eb1b94dff85 -msgid "172.16.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: f4007f87de1f4bada7ce0e55633d427b -msgid "2001:db8::2/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1daaf01c8340423d93f96757bf6041ed -msgid "192.168.3.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1b4913f318a04b02a17c852a5f28e312 -msgid "2001:db8::4/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:739 -#: f9c8ebe5ce5f46d5ae5f6a311ec9ce1c 1a78a58c2a3d41d8aa2f998dc8bfa291 -msgid "ISP" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: e5138de5b6844fb4bc208ad2d66aec94 -msgid "10.2.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: c048ed3059334c8c964fc7c9595d8062 -msgid "2001:db8::6/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:97 -#: a4c3a66971e240858d9343a409da32e9 -msgid "RD & RT Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 129b297c60754ac498ec18058a07dcee -msgid "VRF" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 935cb9b1a2e0495fb580d674e4a9e3d0 -msgid "RD" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: edb2eabdd1284a7dbe82d4544b8616b6 -msgid "RT" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: 79ca3a7d0fa14923bfca6af65dff61e9 b49d97869905413e8df40c8e1abb1b3b -msgid "64496:1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: 81afc720df0d48a0b9df047a6543aeea 0e1ffef8c627472daa211f00b436b220 -msgid "64496:2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: 471376839df44e6a98853fbe83f8c302 3b9f6979c3374fb7a754201c21604f75 -msgid "64496:50" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: 901fb99798914a7ba27ae0b4e7e2af72 c22fb6bacd9f4f178ebc8d64e28967fe -msgid "64496:100" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:113 -#: 37b3b1695a5142b8b4eb0f4eda8e9392 -msgid "Configurations" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:115 -#: 8fcddacdabb347938fdddd5df33ef082 -msgid "" -"We use a static route configuration in between the Core and each LAN and " -"Management router, and BGP between the Core router and the ISP router but " -"any dynamic routing protocol can be used." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:120 -#: d0ba532920c146b58e8609eeb52a9351 -msgid "Remote Networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:122 -#: 2370f525c998496dae1e93ecb14ef1d2 -msgid "" -"The following template configuration can be used in each remote router based" -" in our topology." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:134 -#: a3a69aba21694a54945c258e54511f4c -msgid "Core Router" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:137 -#: 1d698f00b16644879ae215618bc43467 -msgid "Step 1: VRF and Configurations to remote networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:139 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:231 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:290 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:774 -#: e37f8f84308849c193ca0456b07b9e12 7a85dc42dbe8467c93d1259f5c8a2831 -#: 00c29f4758af4aa6bdb6ae7100df73c1 2b99ef8b24734d5ca80591ca6fdd5b75 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:143 -#: 9d83ffd71ed3407584a88fe68993f486 -msgid "" -"Set the VRF name and Table ID, set interface address and bind it to the VRF." -" Last add the static route to the remote network." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:160 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:248 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:320 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:829 -#: 3aba84af46df47cc9fd2ae84f9b503da da748005d3874b4480b7bbd9d591e27a -#: 1ecb9ec20cdc4c2893ee6fca2ee51358 a280fb687cdc40178d509af90951189b -msgid "Verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:164 -#: 37ce0e67288f45fe9ef9c08369138fb2 -msgid "" -"Checking the routing table of the VRF should reveal both static and " -"connected entries active. A PING test between the Core and remote router is " -"a way to validate connectivity within the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:228 -#: c75588c0d4934b26bc2191593d95078c -msgid "Step 2: BGP Configuration for VRF-Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:235 -#: 1b8331d7180b4c1fa784335dc8a73fb7 -msgid "" -"Setting BGP global local-as as well inside the VRF. Redistribute static " -"routes to inject configured networks into the BGP process but still inside " -"the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:252 -#: 23fba5b0b23849658c56bfe042cba29a -msgid "" -"Check the BGP VRF table and verify if the static routes are injected showing" -" the correct next-hop information." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:287 -#: 43ff822c83a548f1bfc03261deb495b8 -msgid "Step 3: VPN Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:293 -#: c4ae33aea35c4a3f9deaff43b955090e -msgid "" -"Within the VRF we set the Route-Distinguisher (RD) and Route-Targets (RT), " -"then we enable the export/import VPN." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:312 -#: 4186090c0eb4432aa7763a11232d7c73 -msgid "" -"A key point to understand is that if we need two VRFs to communicate between" -" each other EXPORT rt from VRF1 has to be in the IMPORT rt list from VRF2. " -"But this is only in ONE direction, to complete the communication the EXPORT " -"rt from VRF2 has to be in the IMPORT rt list from VRF1." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:317 -#: dbff84d09cf543e78ef3bedf22f4cce0 -msgid "" -"There are some cases where this is not needed -for example, in some DDoS " -"appliance- but most inter-vrf routing designs use the above configurations." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:324 -#: 20333d5d9494441a974b2c7b031c3620 -msgid "" -"After configured all the VRFs involved in this topology we take a deeper " -"look at both BGP and Routing table for the VRF LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:417 -#: 50932524836549ed803143fff7ca704a -msgid "" -"As we can see in the BGP table any imported route has been injected with a " -"\"@\" followed by the VPN id; In the routing table of the VRF, if the route " -"was installed, we can see -between round brackets- the exported VRF table." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:422 -#: 040c2e2ba85b4694b54fc037d8e22e62 -msgid "Step 4: End to End verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:425 -#: 56ca70dcbe824d18ad0daeed1283e2cb -msgid "Now we perform some end-to-end testing" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:427 -#: 5f0852ffedff48d0b4b2996888183b7a -msgid "From Management to LAN1/LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:469 -#: 6ce8210eb4d24cceb40d4b8940231d99 -msgid "From Management to Outside (fails as intended)" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:520 -#: c1d07bc3b8de4706bd224c06ee17dbbe -msgid "LAN1 to Outside" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:571 -#: 3db16afd744a4f0bb44dfcf01987a098 -msgid "" -"we are using \"source-address\" option cause we are not redistributing " -"connected interfaces into BGP on the Core router hence there is no comeback " -"route and ping will fail." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:575 -#: cfb5c05281f242db8863602ddb0693f9 -msgid "LAN1 to LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:601 -#: bf275914b4ec4567b5fecc55c805c298 -msgid "Conclusions" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:603 -#: 066850a20fcf43a8a9f17c58e2038810 -msgid "" -"Inter-VRF routing is a well-known solution to address complex routing " -"scenarios that enable -in a dynamic way- to leak routes between VRFs. Is " -"recommended to take special consideration while designing route-targets and " -"its application as it can minimize future interventions while creating a new" -" VRF will automatically take the desired effect in its propagation." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:611 -#: 8683a9d3f2104a9db49b0a0907555f32 -msgid "Appendix-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:614 -#: 5abc7d4aebac4e02af6886aac14cf1ce -msgid "Full configuration from all devices" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:764 -#: 41e37392648b4e2da99de7267631749e -msgid "Appendix-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:767 -#: 8f882d02b8fa437f87c5f3e7520c95c5 -msgid "Route-Filtering" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:770 -#: bf9c4776ac3e43c180cf5abb70bfa7aa -msgid "" -"When importing routes using MP-BGP it is possible to filter a subset of them" -" before are injected in the BGP table. One of the most common case is to use" -" a route-map with an prefix-list." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:778 -#: 68fcdc98c6d246099510635b49afe34e -msgid "We create a prefix-list first and add all the routes we need to." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:803 -#: e7a748ac55dc4c02b90fea5c37b64b9b -msgid "" -"Then add a route-map and reference to above prefix. Consider that the " -"actions taken inside the prefix will MATCH the routes that will be affected " -"by the actions inside the rules of the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:815 -#: 1bb8831212be41398444370636f0f441 -msgid "" -"We are using a \"white list\" approach by allowing only what is necessary. " -"In case that need to implement a \"black list\" approach then you will need " -"to change the action in the route-map for a deny BUT you need to add a rule " -"that permits the rest due to the implicit deny in the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:820 -#: 384686127eda49c39439e379043fd224 -msgid "" -"Then we need to attach the policy to the BGP process. This needs to be under" -" the import statement in the vrf we need to filter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:853 -#: e9beeb420b0e42cf8fe71412b1255dc0 -msgid "" -"As we can see even if both VRF LAN1 and LAN2 has the same import RTs we are " -"able to select which routes are effectively imported and installed." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po deleted file mode 100644 index 5f113413..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/l3vpn-hub-and-spoke.po +++ /dev/null @@ -1,588 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:4 -#: 998a7d4fc7604358b63c64b7e10c9256 -msgid "L3VPN for Hub-and-Spoke connectivity with VyOS" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:6 -#: 686abf9e6407494ea9f8adb1e6a38ba4 -msgid "" -"IP/MPLS technology is widely used by various service providers and large " -"enterprises in order to achieve better network scalability, manageability " -"and flexibility. It also provides the possibility to deliver different " -"services for the customers in a seamless manner. Layer 3 VPN (L3VPN) is a " -"type of VPN mode that is built and delivered through OSI layer 3 networking " -"technologies. Often the border gateway protocol (BGP) is used to send and " -"receive VPN-related data that is responsible for the control plane. L3VPN " -"utilizes virtual routing and forwarding (VRF) techniques to receive and " -"deliver user data as well as separate data planes of the end-users. It is " -"built using a combination of IP- and MPLS-based information. Generally, " -"L3VPNs are used to send data on back-end VPN infrastructures, such as for " -"VPN connections between data centres, HQs and branches." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:20 -#: 890e7aea999d499bbcd0cdf856d99266 -msgid "" -"An L3VPN consists of multiple access links, multiple VPN routing and " -"forwarding (VRF) tables, and multiple MPLS paths or multiple P2MP LSPs. An " -"L3VPN can be configured to connect two or more customer sites. In hub-and-" -"spoke MPLS L3VPN environments, the spoke routers need to have unique Route " -"Distinguishers (RDs). In order to use the hub site as a transit point for " -"connectivity in such an environment, the spoke sites export their routes to " -"the hub. Spokes can talk to hubs, but never have direct paths to other " -"spokes. All traffic between spokes is controlled and delivered over the hub " -"site." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:31 -#: e546c7fa938240fbb028a21e16cd21bd -msgid "" -"To deploy a Layer3 VPN with MPLS on VyOS, we should meet a couple " -"requirements in order to properly implement the solution. We'll use the " -"following nodes in our LAB environment:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:35 -#: 98565fe6ffb947e09692e9b7b1fb9912 -msgid "2 x Route reflectors (VyOS-RRx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:36 -#: 56560e4d5b514b569eb498d80ccfd796 -msgid "4 x Provider routers (VyOS-Px)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:37 -#: 29e234d5eff54c03b262f561d6ba4308 -msgid "3 x Provider Edge (VyOs-PEx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:38 -#: b6d0c34166be4ebeb304f7da74c8fedf -msgid "3 x Customer Edge (VyOS-CEx)" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:40 -#: 95ddfbd9c6d14f0284add13b0b318aeb -msgid "The following software was used in the creation of this document:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:42 -#: 2e1ff92ea1d34b3380b4735f9231bbaa -msgid "Operating system: VyOS" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:43 -#: 1a1845ca31364523ac85c14afed17a6b -msgid "Version: 1.4-rolling-202110310317" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:44 -#: be17aee6c8e24d0a9c81a719c92b962c -msgid "Image name: vyos-1.4-rolling-202110310317-amd64.iso" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:46 -#: 94e4d99e94914c41b8f5a501b90a9c1a -msgid "" -"**NOTE:** VyOS Router (tested with VyOS 1.4-rolling-202110310317) – The " -"configurations below are specifically for VyOS 1.4.x." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:49 -#: cf278ef398a348f19de9082189238ad3 -msgid "" -"General information can be found in the :ref:`configuration/vrf/index:L3VPN " -"VRFs` chapter." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:55 -#: b78300c0062d4f20adb7a5a718366771 -msgid "Topology" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rstNone -#: 1f165bb067114d18877f62c65d93df63 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:65 -#: 8a0c9d1b570c4c7cbe2de877527a2c8d -msgid "How does it work?" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:67 -#: cb4349ce8fa34bd391aeef02ba55c8c9 -msgid "" -"As we know the main assumption of L3VPN “Hub and Spoke” is, that the traffic" -" between spokes have to pass via hub, in our scenario VyOS-PE2 is the Hub PE" -" and the VyOS-CE1-HUB is the central customer office device that is " -"responsible for controlling access between all spokes and announcing its " -"network prefixes (10.0.0.100/32). VyOS-PE2 has the main VRF (its name is " -"BLUE_HUB), its own Route-Distinguisher(RD) and route-target import/export " -"lists. Multiprotocol-BGP(MP-BGP) delivers L3VPN related control-plane " -"information to the nodes across network where PEs Spokes import the route-" -"target 60535:1030 (this is export route-target of vrf BLUE_HUB) and export " -"its own route-target 60535:1011(this is vrf BLUE_SPOKE export route-target)." -" Therefore, the Customer edge nodes can only learn the network prefixes of " -"the HUB site [10.0.0.100/32]. For this example VyOS-CE1 has network prefixes" -" [10.0.0.80/32] / VyOS-CE2 has network prefixes [10.0.0.90/32]. Route-" -"Reflector devices VyOS-RR1 and VyOS-RR2 are used to simplify network routes " -"exchange and minimize iBGP peerings between devices." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:83 -#: 60dd546b31004b06af47f4a1ce701957 -msgid "L3VPN configuration parameters table:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 565d53c1b26a4de38feaa86b567c6b4e -msgid "Node" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 34eba7825ea54979a42f178e9dcd15bf -msgid "Role" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: b89d4c69529d4488b011d8e8db5aa4b4 -msgid "VRF" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: f55441b962624fd6b5c1538290091f7e -msgid "RD" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: 6e72edabaf07419ea0abb13bb7789540 -msgid "RT import" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:86 -#: e547d56f80ca46f1ac625b270ab02628 -msgid "RT export" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: ea3d4c4a18ec433b8c7f3ac03981f8c2 -msgid "VyOS-PE2" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 55bc9c2598064d92a3b9fae0fc6a1154 -msgid "Hub" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 1291d942846d4c6cae1e8833e139cb5d -msgid "BLUE_HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: 27596f3bee3d43f28a16a42174e74667 -msgid "10.80.80.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: a4ca55dd19b14bd9a3b02fddeaf7eb11 -msgid "65035:1011 65035:1030" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:88 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 21adc69cf2bf4575ae4476a8cb6d056c 4862295b4bae4ea1baac2124700b1236 -#: 5a80925f27574dddb9d476febf102516 -msgid "65035:1030" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: a0fdcadaac2946a1bad9533989517a9c -msgid "VyOS-PE1" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: b4744ce92c634f65b6558eb37e536454 c98d8778bb984c8eab3202150c36d157 -msgid "Spoke" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: bce236afe7fb4c15b1adff31ccdaeea6 b1801511514c4b169d55b38e25b0a021 -msgid "BLUE_SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: cc8eb3ef69e94ebf81b298848a74f246 -msgid "10.50.50.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:91 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: b234869593f9450bb4866570315fb225 93a1e9117a7041a4ab0ec98cdde1a35d -msgid "65035:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 60fdfd315f2a4711a0f2b53299b51566 -msgid "VyOS-PE3" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:93 -#: 23c8e2bb64ab41d593c0e2aa6e921fbe -msgid "10.60.60.1:1011" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:100 -#: 9e879fff2f324772adfe0bc310edc4a4 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:105 -#: 7477a6ffa308480fbee1b135a33ae15a -msgid "Step-1: Configuring IGP and enabling MPLS LDP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:107 -#: 15b715d0ed4248cf9593d4c8c72bc20c -msgid "" -"At the first step we need to configure the IP/MPLS backbone network using " -"OSPF as IGP protocol and LDP as label-switching protocol for the base " -"connectivity between **P** (rovider), **P** (rovider) **E** (dge) and **R** " -"(oute) **R** (eflector) nodes:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:112 -#: 0fdd2f02198142519dfa1b13c7a87d43 -msgid "VyOS-P1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:142 -#: 6fa7d00718fa44eea0355cfc8d67d9af -msgid "VyOS-P2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:168 -#: 405ddfb3d90241e6b9791a694e8c02fc -msgid "VyOS-P3:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:194 -#: f214a604b9194bceb30e7ad4dcc9cc04 -msgid "VyOS-P4:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:224 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:362 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:413 -#: ed57672a54e540168ca1cb343c953144 91ace2d281b24fd5b0ea37e1876978bc -#: de90bc4f836b493cad00b4ef434ed1ee -msgid "VyOS-PE1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:241 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:376 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:435 -#: 2b0b8e09b36c4192905fd8fcadb3317e a4e9cf5d0fbb4537addb56d6ecff66e3 -#: b6016d3b47a549e0bcfba58d5fa86717 -msgid "VyOS-PE2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:262 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:390 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:457 -#: dc7cd8343e6743a0815e02f3d65df79a 0d769e475d9c4846ae32e22f5bf3d91c -#: 77fe05eee30a4adf9df916a5462cd9a5 -msgid "VyOS-PE3:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:279 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:328 -#: 61d86fc34fbd4aed98036cf60f0dd615 fd431069d9f24c3084c24124059724d4 -msgid "VyOS-RR1:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:299 -#: ../../configexamples/l3vpn-hub-and-spoke.rst:345 -#: 55304b8d06834fc69cdb07738e63e625 f8923e269249490fa37cc90c7b1342ec -msgid "VyOS-RR2:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:322 -#: 2e846b31f9c44dfbab01271d60e398c6 -msgid "Step-2: Configuring iBGP for L3VPN control-plane" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:324 -#: 7b89e4318dec4188b74b6b3f5dab7b59 -msgid "" -"At this step we are going to enable iBGP protocol on MPLS nodes and Route " -"Reflectors (two routers for redundancy) that will deliver IPv4 VPN (L3VPN) " -"routes between them:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:407 -#: 58d3377a35da4d30a1cdb7229a5fe29c -msgid "Step-3: Configuring L3VPN VRFs on PE nodes" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:409 -#: fe4e7c69c7424e24888c3f3706d8c8b0 -msgid "" -"This section provides configuration steps for setting up VRFs on our PE " -"nodes including CE facing interfaces, BGP, rd and route-target import/export" -" based on the pre-defined parameters." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:482 -#: fc9f63f8aca0444da7ec55ff854e4676 -msgid "Step-4: Configuring CE nodes" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:484 -#: 925625dcfa774f7f9934408b8214a7f1 -msgid "" -"Dynamic routing used between CE and PE nodes and eBGP peering established " -"for the route exchanging between them. All routes received by PEs are then " -"exported to L3VPN and delivered from Spoke sites to Hub and vise-versa based" -" on previously configured L3VPN parameters." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:490 -#: 47a7f4d1ffeb4def9c259e4e6e629cd2 -msgid "VyOS-CE1-SPOKE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:507 -#: 8f961af78f9b4d888bd12c34cf65ec60 -msgid "VyOS-CE1-HUB:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:525 -#: a41c0ae5954a4760acf3b56323072447 -msgid "VyOS-CE2-SPOKE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:545 -#: 4c4149624eba4d5b903a371d003f6dba -msgid "Step-5: Verification" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:547 -#: a82f92d1466d41e994f0679d05553320 -msgid "" -"This section describes verification commands for MPLS/BGP/LDP protocols and " -"L3VPN related routes as well as diagnosis and reachability checks between CE" -" nodes." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:551 -#: d87f385db4c442eea1c679e29862e55f -msgid "" -"Let’s check IPv4 routing and MPLS information on provider nodes (same " -"procedure for all P nodes):" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:554 -#: 387768aa305a4d89bf9504179b279283 -msgid "“show ip ospf neighbor” for checking ospf relationship" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:567 -#: 14d1985bcdcc43e4a9381ab7d746af1f -msgid "“show mpls ldp neighbor “ for checking ldp neighbors" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:579 -#: 14f7b630eb854181a68a201cd4ff573b -msgid "“show mpls ldp binding” for checking mpls label assignment" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:636 -#: 9f0c750511f44cac99373cc626930b21 -msgid "" -"Now we’re checking iBGP status and routes from route-reflector nodes to " -"other devices:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:639 -#: 27aef0ad05464cc59458e0f4d7785462 -msgid "“show bgp ipv4 vpn summary” for checking BGP VPNv4 neighbors:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:658 -#: dc50a484ccb14f9ca7e7dec858073973 -msgid "“show bgp ipv4 vpn” for checking all VPNv4 prefixes information:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:698 -#: fc808be9ede24f739e02e5129eba3963 -msgid "" -"“show bgp ipv4 vpn x.x.x.x/x” for checking best path selected for specific " -"VPNv4 destination" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:716 -#: 528fe8121f4640fb96768623ce8ca51d -msgid "" -"Also we can verify how PE devices receives VPNv4 networks from the RRs and " -"installing them to the specific customer VRFs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:719 -#: ef0c4185fb5d4547b3e2c790769f104d -msgid "" -"“show bgp ipv4 vpn summary” for checking iBGP neighbors against route-" -"reflector devices:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 -#: 1f1dbb0745cc43278c22ba38335200df -msgid "“show bgp vrf all” for checking all the prefix learning on BGP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:736 -#: 3705f8a528294628a4b27fa3913af275 -msgid "within VRFs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 -#: c668ee5332604c59a958d6d9565e2cfe -msgid "“show bgp vrf BLUE_SPOKE summary” for checking EBGP neighbor" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:764 -#: 82b64c97c93a4f7c901153092449c801 -msgid "information between PE and CE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:784 -#: 0ca40736901446fcad91df434b158fb5 -msgid "“show ip route vrf BLUE_SPOKE” for viewing the RIB in our Spoke PE." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:783 -#: 388ba3e42cfb453682eff0522884b664 -msgid "" -"Using this command we are also able to check the transport and customer " -"label (inner/outer) for Hub network prefix (10.0.0.100/32):" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:807 -#: df85772519284579bf2097c0313d76b2 -msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking the best-path to the" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:806 -#: 3ded1eaa580b4d75a1aebdd4248776fe -msgid "" -"specific VPNv4 destination including extended community and remotelabel " -"information. This procedure is the same on all Spoke nodes:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:831 -#: dbb5f2aa2caa4f5aa52ca697597e0f4c -msgid "Now, let’s check routing information on out Hub PE:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 -#: 1e4f350b52274f58ae7a54adaff0b412 -msgid "“show bgp ipv4 vpn summary” for checking iBGP neighbors again" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:834 -#: 8a347810b376407ba2c69b3f23fce640 -msgid "VyOS-RR1/RR2" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:851 -#: 9bc7d0b71fba42b281873b8a1be783d8 -msgid "“show bgp vrf all” for checking all the prefixes learning on BGP" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 -#: 118b9f4e005f4e04b1632e4589ddfa17 -msgid "“show bgp vrf BLUE_HUB summary” for checking EBGP neighbor" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:891 -#: 93c455e1b8874441adba6171d4381d59 -msgid "CE Hub device" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:909 -#: 0137b1e74074467495469f4604661c56 -msgid "“show ip route vrf BLUE_HUB” to view the RIB in our Hub PE." -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:907 -#: 54511e5d16824c21a9eeb419cf668caa -msgid "" -"With this command we are able to check the transport and customer label " -"(inner/outer) for network spokes prefixes 10.0.0.80/32 - 10.0.0.90/32" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 -#: 0e7f267bff6140e598dee3231a8eadc5 -msgid "“show bgp ipv4 vpn x.x.x.x/32” for checking best-path," -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:941 -#: 2d0e3c0fc3c74b058df139a5fb208aa0 -msgid "extended community and remote label of specific destination" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:985 -#: 3d25f766a7a743f289fdb81b7bbe3168 -msgid "Finally, let’s check the reachability between CEs:" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:987 -#: 08b5c6d6886144fa86ad19ea63c1afb2 -msgid "VyOS-CE1-SPOKE -----> VyOS-CE-HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1025 -#: 9cbd876b3f4d48b78595fcb0300221cf -msgid "VyOS-CE-HUB -------> VyOS-CE1-SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1026 -#: 368f34ba9eb84e7ebeca0b2dafdff68a -msgid "VyOS-CE-HUB -------> VyOS-CE2-SPOKE" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1085 -#: 17a80175953c4e24916458908f8443e1 -msgid "VyOS-CE2-SPOKE -------> VyOS-CE-HUB" -msgstr "" - -#: ../../configexamples/l3vpn-hub-and-spoke.rst:1123 -#: 062bae083b9c48369539bf248ef35b6f -msgid "" -"**Note:** At the moment, trace mpls doesn’t show labels/paths. So we’ll see " -"* * * for the transit routers of the mpls backbone." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po deleted file mode 100644 index df1aa330..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/ospf-unnumbered.po +++ /dev/null @@ -1,48 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/ospf-unnumbered.rst:7 29d634a6af9c469eb9fd48424a9f3d5c -msgid "OSPF unnumbered with ECMP" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:9 c3072bd445424325bf17c2296e1d44e1 -msgid "General information can be found in the :ref:`routing-ospf` chapter." -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:12 -#: 9aa3a8a8aff941979fa7396c8509d31c -msgid "Configuration" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:14 -#: ../../configexamples/ospf-unnumbered.rst:52 -#: f9990c6209254eddae5cf323b898db68 7615801deebe40a6b1b55c8cd441ef0e -msgid "Router A:" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:31 -#: ../../configexamples/ospf-unnumbered.rst:87 -#: a6c539b6f0ad42d7ae958feb6f19b9b3 9cb799c9efc549b0a72113e8514dc7b6 -msgid "Router B:" -msgstr "" - -#: ../../configexamples/ospf-unnumbered.rst:50 -#: a5b67b9fc6ba4a79a42835e8a06ea49c -msgid "Results" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po deleted file mode 100644 index e49e10f8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/pppoe-ipv6-basic.po +++ /dev/null @@ -1,172 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/pppoe-ipv6-basic.rst:7 -#: d01a18dec1a142a8855a0bc03a82e72d -msgid "PPPoE IPv6 Basic Setup for Home Network" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:9 -#: 9ef7b0d68dd9494faf9502d86502f352 -msgid "" -"This document is to describe a basic setup using PPPoE with DHCPv6-PD + " -"SLAAC to construct a typical home network. The user can follow the steps " -"described here to quickly setup a working network and use this as a starting" -" point to further configure or fine-tune other settings." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:14 -#: 1bc45c10d4a248f6998a8a90665ee73a -msgid "" -"To achieve this, your ISP is required to support DHCPv6-PD. If you're not " -"sure, please contact your ISP for more information." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:18 -#: e57a18b57aac4b5ebe79cd1b5a249be4 -msgid "Network Topology" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rstNone -#: 7d29b5deb46f4dd5ba8c411ff15c3580 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:26 -#: 9b4e35fc5bf949f6a08a601e0f85b41f -msgid "Configurations" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:29 -#: e2264f3deb0f48e3be8d824b4558bdf6 -msgid "PPPoE Setup" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:38 -#: 0fb2a3f4a82946bc801f42aea42116a9 -msgid "" -"Fill ``password`` and ``user`` with the credential provided by your ISP." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:39 -#: 37defbee2b744b67a69c4393ca546d72 -msgid "``service-name`` can be an arbitrary string." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:42 -#: 5ae65ec790db46bbbfe7d471f2f7ebd2 -msgid "DHCPv6-PD Setup" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:44 -#: 0abfd09ecb7a423196d7010533a9eef5 -msgid "" -"During address configuration, in addition to assigning an address to the WAN" -" interface, ISP also provides a prefix to allow the router to configure " -"addresses of LAN interface and other nodes connecting to LAN, which is " -"called prefix delegation (PD)." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:54 -#: f09a5ec22ab24c12907d90a279d89a13 -msgid "" -"Here we use the prefix to configure the address of eth1 (LAN) to form " -"``<prefix>::64``, where ``64`` is hexadecimal of address 100." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:56 -#: 1f554d13466d467d9d8a1aa4480dec52 -msgid "" -"For home network users, most of time ISP only provides /64 prefix, hence " -"there is no need to set SLA ID and prefix length. See :ref:`pppoe-interface`" -" for more information." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:61 -#: 37a4fe866ce44dd6a82988da55311a6a -msgid "Router Advertisement" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:63 -#: 5d74e570a4be470e951a4fe806442c2d -msgid "" -"We need to enable router advertisement for LAN network so that PC can " -"receive the prefix and use SLAAC to configure the address automatically." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:72 -#: 1922e24702884c2289071ab9cc0053e5 -msgid "Set MTU in advertisement to 1492 because of PPPoE header overhead." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:73 -#: 4efc1c1477cf49399f430202782675f3 -msgid "" -"Set DNS server address in the advertisement so that clients can obtain it by" -" using RDNSS option. Most operating systems (Windows, Linux, Mac) should " -"already support it." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:76 -#: ba3687f3d52e4e0dad78491c4827825e -msgid "" -"Here we set the prefix to ``::/64`` to indicate advertising any /64 prefix " -"the LAN interface is assigned." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:78 -#: ed8c9fcabb584dd28037b2deb6954f8e -msgid "" -"Since some ISPs disconnects continuous connection for every 2~3 days, we set" -" ``valid-lifetime`` to 2 days to allow PC for phasing out old address." -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:82 -#: 7de4b4c573da4409bceb27abd04c4063 -msgid "Basic Firewall" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:84 -#: bbe045c3a1fb403385b959777dfdfe8c -msgid "" -"To have basic protection while keeping IPv6 network functional, we need to:" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:86 -#: 9cb07d9a5372428d883056ccd6073d79 -msgid "Allow all established and related traffic for router and LAN" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:87 -#: f98467c842b64dbc948d17d120011d65 -msgid "Allow all icmpv6 packets for router and LAN" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:88 -#: a6cc69dd5a304905844a5ff7218dca13 -msgid "Allow DHCPv6 packets for router" -msgstr "" - -#: ../../configexamples/pppoe-ipv6-basic.rst:111 -#: b101c4ec16274088a7a102a7ebe1bb82 -msgid "" -"Note to allow the router to receive DHCPv6 response from ISP. We need to " -"allow packets with source port 547 (server) and destination port 546 " -"(client)." -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po deleted file mode 100644 index 976e43a8..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/wan-load-balancing.po +++ /dev/null @@ -1,219 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/wan-load-balancing.rst:8 -#: 9f05f08a64a4424292daad78fad5a6e2 -msgid "WAN Load Balancer examples" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:12 -#: ced8dacc57da404fb3d767a8fa5f199b -msgid "Example 1: Distributing load evenly" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:14 -#: 71129440d8fa4e80958dde7df43ed1db -msgid "The setup used in this example is shown in the following diagram:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rstNone -#: ../../configexamples/wan-load-balancing.rstNone -#: eef518f424234b9e877063b444e4715e 36a842a81f0e40eb8491f2b78a82b3d0 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:23 -#: ../../configexamples/wan-load-balancing.rst:75 -#: ../../configexamples/wan-load-balancing.rst:104 -#: ../../configexamples/wan-load-balancing.rst:135 -#: f84efa18552041ddb93b10d114806dbc c05f3e6b75614f619891c902ea58dad2 -#: 290135d81ebf4d28a6c79ac052c171f6 cf186aa1226e49a38af1fbfe6ba85e1b -msgid "Overview" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:24 -#: d6df93a47c7f48b5b195b2f219a88bb3 -msgid "" -"All traffic coming in through eth2 is balanced between eth0 and eth1 on the " -"router." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:26 -#: 9cbde66a8bff45f2b23af438df71dd36 -msgid "" -"Pings will be sent to four targets for health testing (33.44.55.66, " -"44.55.66.77, 55.66.77.88 and 66.77.88.99)." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:28 -#: 77ed08f8b1454a09ad8eeffdefdf17b2 -msgid "" -"All outgoing packets are assigned the source address of the assigned " -"interface (SNAT)." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:30 -#: 08426bfc131c48d6bc2162479ec7b56d -msgid "" -"eth0 is set to be removed from the load balancer's interface pool after 5 " -"ping failures, eth1 will be removed after 4 ping failures." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:34 -#: 11f1d3c652c54f049e9af334fa38a106 -msgid "Create static routes to ping targets" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:35 -#: f973a670c56346c2926c9be556660bd4 -msgid "" -"Create static routes through the two ISPs towards the ping targets and " -"commit the changes:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:46 -#: a9cb47e088ac44c19325a69295109a9d -msgid "Configure the load balancer" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:47 -#: d5f35bfbdbb9448e9082c8598285675e -msgid "Configure the WAN load balancer with the parameters described above:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:68 -#: 384337b95dcc4f60ad417e0e7fc93f82 -msgid "Example 2: Failover based on interface weights" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:70 -#: f414970795f740d49d837fe9561c7d72 -msgid "This example uses the failover mode." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:76 -#: a14f9000d16c4cf2a6dc8db548872845 -msgid "" -"In this example, eth0 is the primary interface and eth1 is the secondary " -"interface. To provide simple failover functionality. If eth0 fails, eth1 " -"takes over." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:81 -#: a709f9da975d434d83d8d1ecccfae31f -msgid "Create interface weight based configuration" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:82 -#: 122b99f9d9274c83b31f16ac0ddf7f07 -msgid "" -"The configuration steps are the same as in the previous example, except rule" -" 10. So we keep the configuration, remove rule 10 and add a new rule for the" -" failover mode:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:95 -#: 9470dd8d60da4a6fb676059fc12c2e1c -msgid "Example 3: Failover based on rule order" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:97 -#: c32d2814f74240a1807a5295a10b21de -msgid "" -"The previous example used the failover command to send traffic through eth1 " -"if eth0 fails. In this example, failover functionality is provided by rule " -"order." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:105 -#: 855bce2604b44db0be549937bd437e78 -msgid "" -"Two rules will be created, the first rule directs traffic coming in from " -"eth2 to eth0 and the second rule directs the traffic to eth1. If eth0 fails " -"the first rule is bypassed and the second rule matches, directing traffic to" -" eth1." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:111 -#: 2825af09d2bb40deb7ab2b0b4425a37f -msgid "Create rule order based configuration" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:112 -#: 42e71205c1374e30b236fd3c33d88d07 -msgid "" -"We keep the configuration from the previous example, delete rule 10 and " -"create the two new rules as described:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:124 -#: f4162881a62d48769911ff1fec82ee95 -msgid "Example 4: Failover based on rule order - priority traffic" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:126 -#: ../../configexamples/wan-load-balancing.rst:136 -#: e3e9af1e73994f4ab2d38a9e67a7fdf5 2888de594abc4c1ebea9fd2c1b3189bf -msgid "" -"A rule order for prioritizing traffic is useful in scenarios where the " -"secondary link has a lower speed and should only carry high priority " -"traffic. It is assumed for this example that eth1 is connected to a slower " -"connection than eth0 and should prioritize VoIP traffic." -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:142 -#: c255dbcebfcd4beaac19f746a4516531 -msgid "Create rule order based configuration with low speed secondary link" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:143 -#: dd2df2f8dbc3418b8a56fccef4db961f -msgid "" -"We keep the configuration from the previous example, delete rule 20 and " -"create a new rule as described:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:156 -#: a16b4fa634b5462eb57dac3d1700cffe -msgid "Example 5: Exclude traffic from load balancing" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:158 -#: fc3846b150314a348e795d7bffdfbcea -msgid "" -"In this example two LAN interfaces exist in different subnets instead of one" -" like in the previous examples:" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:167 -#: d3071c91cb44411f98bf1f4db5206a4f -msgid "Adding a rule for the second interface" -msgstr "" - -#: ../../configexamples/wan-load-balancing.rst:169 -#: c06ffdabeef740e182701946afb4b6ec -msgid "" -"Based on the previous example, another rule for traffic from the second " -"interface eth3 can be added to the load balancer. However, traffic meant to " -"flow between the LAN subnets will be sent to eth0 and eth1 as well. To " -"prevent this, another rule is required. This rule excludes traffic between " -"the local subnets from the load balancer. It also excludes locally-sources " -"packets (required for web caching with load balancing). eth+ is used as an " -"alias that refers to all ethernet interfaces:" -msgstr "" diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po deleted file mode 100644 index 7ae4c684..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/zone-policy.po +++ /dev/null @@ -1,323 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/zone-policy.rst:6 3c76f26421954ac884480d0cffe55150 -msgid "Zone-Policy example" -msgstr "" - -#: ../../configexamples/zone-policy.rst:8 b000af62a2ff45e3bea0983ff08c6ca9 -msgid "" -"In :vytask:`T2199` the syntax of the zone configuration was changed. The " -"zone configuration moved from ``zone-policy zone <name>`` to ``firewall zone" -" <name>``." -msgstr "" - -#: ../../configexamples/zone-policy.rst:13 518ed4192332498b988ad701dbe4ae94 -msgid "Native IPv4 and IPv6" -msgstr "" - -#: ../../configexamples/zone-policy.rst:15 e785499caee9483ebbfa8fea63bd3f60 -msgid "We have three networks." -msgstr "" - -#: ../../configexamples/zone-policy.rst:24 d5184c69966f41c5acd57ba576316df4 -msgid "" -"**This specific example is for a router on a stick, but is very easily " -"adapted for however many NICs you have**:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:28 dc181a02a98a45da8888bc017de3ea1f -msgid "Internet - 192.168.200.100 - TCP/80" -msgstr "" - -#: ../../configexamples/zone-policy.rst:29 4e066389682c40048d57dec2c83a5aae -msgid "Internet - 192.168.200.100 - TCP/443" -msgstr "" - -#: ../../configexamples/zone-policy.rst:30 99c22b93805b4a9d97c17590c0d1ff93 -msgid "Internet - 192.168.200.100 - TCP/25" -msgstr "" - -#: ../../configexamples/zone-policy.rst:31 98671bd795584e58ab09f67a17c41bf1 -msgid "Internet - 192.168.200.100 - TCP/53" -msgstr "" - -#: ../../configexamples/zone-policy.rst:32 132e6aa544e14ab68d588186821b0cf1 -msgid "VyOS acts as DHCP, DNS forwarder, NAT, router and firewall." -msgstr "" - -#: ../../configexamples/zone-policy.rst:33 378d3439fdd441d0b598dee31369da95 -msgid "" -"192.168.200.200/2001:0DB8:0:BBBB::200 is an internal/external DNS, web and " -"mail (SMTP/IMAP) server." -msgstr "" - -#: ../../configexamples/zone-policy.rst:35 45a4384bc0fc4bd1a25c98a27c2a81ce -msgid "" -"192.168.100.10/2001:0DB8:0:AAAA::10 is the administrator's console. It can " -"SSH to VyOS." -msgstr "" - -#: ../../configexamples/zone-policy.rst:37 5cc8e033a70c48bcbc424e36c169c4af -msgid "LAN and DMZ hosts have basic outbound access: Web, FTP, SSH." -msgstr "" - -#: ../../configexamples/zone-policy.rst:38 7345f3e3a5874d65b6922d88f3117ecd -msgid "LAN can access DMZ resources." -msgstr "" - -#: ../../configexamples/zone-policy.rst:39 2413bb4e87ee4a92922530672b633c3c -msgid "DMZ cannot access LAN resources." -msgstr "" - -#: ../../configexamples/zone-policy.rst:40 604e13042cc6421fa69f297748ae55ab -msgid "Inbound WAN connect to DMZ host." -msgstr "" - -#: ../../configexamples/zone-policy.rstNone c296c8f6b6874d18872c119a8cc8ee57 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/zone-policy.rst:47 8aacd45be8534832803d7d08a1a8b19d -msgid "" -"The VyOS interface is assigned the .1/:1 address of their respective " -"networks. WAN is on VLAN 10, LAN on VLAN 20, and DMZ on VLAN 30." -msgstr "" - -#: ../../configexamples/zone-policy.rst:50 5e0f72b4b2db4789ac8dd371ba669517 -msgid "It will look something like this:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:79 74742cf5724e4f2cb3049240b8b10f52 -msgid "Zones Basics" -msgstr "" - -#: ../../configexamples/zone-policy.rst:81 634e5b24c3f749cc9428984dd8206b28 -msgid "" -"Each interface is assigned to a zone. The interface can be physical or " -"virtual such as tunnels (VPN, PPTP, GRE, etc) and are treated exactly the " -"same." -msgstr "" - -#: ../../configexamples/zone-policy.rst:85 6224d85ed139427b8bec0f53015beeb3 -msgid "" -"Traffic flows from zone A to zone B. That flow is what I refer to as a zone-" -"pair-direction. eg. A->B and B->A are two zone-pair-destinations." -msgstr "" - -#: ../../configexamples/zone-policy.rst:88 8cfb35f32511467cb39a75b1d6cd9548 -msgid "Ruleset are created per zone-pair-direction." -msgstr "" - -#: ../../configexamples/zone-policy.rst:90 ab2f3b9301084a50ac3c4342abfc2cfa -msgid "" -"I name rule sets to indicate which zone-pair-direction they represent. eg. " -"ZoneA-ZoneB or ZoneB-ZoneA. LAN-DMZ, DMZ-LAN." -msgstr "" - -#: ../../configexamples/zone-policy.rst:93 c7c352c3ba8341ee9563ded10b507dd9 -msgid "" -"In VyOS, you have to have unique Ruleset names. In the event of overlap, I " -"add a \"-6\" to the end of v6 rulesets. eg. LAN-DMZ, LAN-DMZ-6. This allows " -"for each auto-completion and uniqueness." -msgstr "" - -#: ../../configexamples/zone-policy.rst:97 c0ee89a6de5b40e8b7b1f41327938ce7 -msgid "" -"In this example we have 4 zones. LAN, WAN, DMZ, Local. The local zone is the" -" firewall itself." -msgstr "" - -#: ../../configexamples/zone-policy.rst:100 25d67004a0b34f2d80fe07eb586b31eb -msgid "" -"If your computer is on the LAN and you need to SSH into your VyOS box, you " -"would need a rule to allow it in the LAN-Local ruleset. If you want to " -"access a webpage from your VyOS box, you need a rule to allow it in the " -"Local-LAN ruleset." -msgstr "" - -#: ../../configexamples/zone-policy.rst:105 074031ebe23742cf9ab553c1d3c89851 -msgid "" -"In rules, it is good to keep them named consistently. As the number of rules" -" you have grows, the more consistency you have, the easier your life will " -"be." -msgstr "" - -#: ../../configexamples/zone-policy.rst:123 36212be96d234f809e3aa0635b224e23 -msgid "" -"The first two rules are to deal with the idiosyncrasies of VyOS and " -"iptables." -msgstr "" - -#: ../../configexamples/zone-policy.rst:126 cdaf927567ba470a843b6daed8e148a5 -msgid "" -"Zones and Rulesets both have a default action statement. When using Zone-" -"Policies, the default action is set by the zone-policy statement and is " -"represented by rule 10000." -msgstr "" - -#: ../../configexamples/zone-policy.rst:130 b923769f3fa648cabd265468da6f0ed8 -msgid "" -"It is good practice to log both accepted and denied traffic. It can save you" -" significant headaches when trying to troubleshoot a connectivity issue." -msgstr "" - -#: ../../configexamples/zone-policy.rst:134 8cdbfa157d0c40c5aaa5ce98e2e10eba -msgid "To add logging to the default rule, do:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:141 8370b1669e3244a6a370ab9344a5e114 -msgid "" -"By default, iptables does not allow traffic for established sessions to " -"return, so you must explicitly allow this. I do this by adding two rules to " -"every ruleset. 1 allows established and related state packets through and " -"rule 2 drops and logs invalid state packets. We place the " -"established/related rule at the top because the vast majority of traffic on " -"a network is established and the invalid rule to prevent invalid state " -"packets from mistakenly being matched against other rules. Having the most " -"matched rule listed first reduces CPU load in high volume environments. " -"Note: I have filed a bug to have this added as a default action as well." -msgstr "" - -#: ../../configexamples/zone-policy.rst:152 b98728b4c0444251a8ddd9aae0061313 -msgid "" -"''It is important to note, that you do not want to add logging to the " -"established state rule as you will be logging both the inbound and outbound " -"packets for each session instead of just the initiation of the session. Your" -" logs will be massive in a very short period of time.''" -msgstr "" - -#: ../../configexamples/zone-policy.rst:157 5731588a00a1445aae957e1dfca6f6a9 -msgid "" -"In VyOS you must have the interfaces created before you can apply it to the " -"zone and the rulesets must be created prior to applying it to a zone-policy." -msgstr "" - -#: ../../configexamples/zone-policy.rst:161 214fa70e97f947ecb6bcb6ee8a95f7d7 -msgid "" -"I create/configure the interfaces first. Build out the rulesets for each " -"zone-pair-direction which includes at least the three state rules. Then I " -"setup the zone-policies." -msgstr "" - -#: ../../configexamples/zone-policy.rst:165 ff4bfdb0fea6403bbb05ec6ea9fa65b7 -msgid "" -"Zones do not allow for a default action of accept; either drop or reject. It" -" is important to remember this because if you apply an interface to a zone " -"and commit, any active connections will be dropped. Specifically, if you are" -" SSH’d into VyOS and add local or the interface you are connecting through " -"to a zone and do not have rulesets in place to allow SSH and established " -"sessions, you will not be able to connect." -msgstr "" - -#: ../../configexamples/zone-policy.rst:172 217de4fa5abe448d8c381c002f97e539 -msgid "" -"The following are the rules that were created for this example (may not be " -"complete), both in IPv4 and IPv6. If there is no IP specified, then the " -"source/destination address is not explicit." -msgstr "" - -#: ../../configexamples/zone-policy.rst:226 68c0c6d0b20b468f99608f851ae72f5f -msgid "Since we have 4 zones, we need to setup the following rulesets." -msgstr "" - -#: ../../configexamples/zone-policy.rst:243 5b84e1b04a934648956fa3d46c7d7ab3 -msgid "" -"Even if the two zones will never communicate, it is a good idea to create " -"the zone-pair-direction rulesets and set enable-default-log. This will allow" -" you to log attempts to access the networks. Without it, you will never see " -"the connection attempts." -msgstr "" - -#: ../../configexamples/zone-policy.rst:248 633e0ef63aa44eb68b1f92674e715140 -msgid "This is an example of the three base rules." -msgstr "" - -#: ../../configexamples/zone-policy.rst:272 617108f6e8a04def8d089d3373c5fdc4 -msgid "Here is an example of an IPv6 DMZ-WAN ruleset." -msgstr "" - -#: ../../configexamples/zone-policy.rst:345 a17a13e6dca3416fb9c3d5fa95aff51b -msgid "" -"Once you have all of your rulesets built, then you need to create your zone-" -"policy." -msgstr "" - -#: ../../configexamples/zone-policy.rst:348 2570cdfd598542d4ab4b7e38b8fb7d1e -msgid "Start by setting the interface and default action for each zone." -msgstr "" - -#: ../../configexamples/zone-policy.rst:355 ac4dd0fd6ee24b81a3d208db070b0029 -msgid "" -"In this case, we are setting the v6 ruleset that represents traffic sourced " -"from the LAN, destined for the DMZ. Because the zone-policy firewall syntax " -"is a little awkward, I keep it straight by thinking of it backwards." -msgstr "" - -#: ../../configexamples/zone-policy.rst:364 ded641d51758415e9f0cf27ae1e9b3c4 -msgid "" -"DMZ-LAN policy is LAN-DMZ. You can get a rhythm to it when you build out a " -"bunch at one time." -msgstr "" - -#: ../../configexamples/zone-policy.rst:367 f3adf536211a4f12817bf30695b1b65f -msgid "" -"In the end, you will end up with something like this config. I took out " -"everything but the Firewall, Interfaces, and zone-policy sections. It is " -"long enough as is." -msgstr "" - -#: ../../configexamples/zone-policy.rst:373 d4a2cf9526ec4602822a592145060277 -msgid "IPv6 Tunnel" -msgstr "" - -#: ../../configexamples/zone-policy.rst:375 44a092c185cb4956b7b4bec83f6da9b6 -msgid "" -"If you are using a IPv6 tunnel from HE.net or someone else, the basis is the" -" same except you have two WAN interfaces. One for v4 and one for v6." -msgstr "" - -#: ../../configexamples/zone-policy.rst:378 a9091d4fcd5b424088a2352f008d5947 -msgid "" -"You would have 5 zones instead of just 4 and you would configure your v6 " -"ruleset between your tunnel interface and your LAN/DMZ zones instead of to " -"the WAN." -msgstr "" - -#: ../../configexamples/zone-policy.rst:382 eb7fd578bb60426f8d96fd0016a0d005 -msgid "LAN, WAN, DMZ, local and TUN (tunnel)" -msgstr "" - -#: ../../configexamples/zone-policy.rst:384 c4c7ca9af6244fcf9b0b9ff4ad49cd10 -msgid "v6 pairs would be:" -msgstr "" - -#: ../../configexamples/zone-policy.rst:401 28572036af8b4fd4b48436a393b06d90 -msgid "Notice, none go to WAN since WAN wouldn't have a v6 address on it." -msgstr "" - -#: ../../configexamples/zone-policy.rst:403 0c5f292540b24741a12114027008fe61 -msgid "" -"You would have to add a couple of rules on your wan-local ruleset to allow " -"protocol 41 in." -msgstr "" - -#: ../../configexamples/zone-policy.rst:406 36b65f4c07e644a7b2d18c4ca8639c83 -msgid "Something like:" -msgstr "" |