From 98ef6ffff59861f74cbced391ec8028da27029d6 Mon Sep 17 00:00:00 2001
From: Martin Schanzenbach <schanzen@gnunet.org>
Date: Fri, 2 Jun 2023 19:24:20 +0200
Subject: temporarily change logo to gnu40

---
 locale/ja/LC_MESSAGES/messages.po | 455 ++++++++++++++++++++++++++++----------
 1 file changed, 343 insertions(+), 112 deletions(-)

(limited to 'locale/ja/LC_MESSAGES/messages.po')

diff --git a/locale/ja/LC_MESSAGES/messages.po b/locale/ja/LC_MESSAGES/messages.po
index 4b66ba39..af77d500 100644
--- a/locale/ja/LC_MESSAGES/messages.po
+++ b/locale/ja/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2023-04-01 13:56+0200\n"
+"POT-Creation-Date: 2023-06-02 19:17+0200\n"
 "PO-Revision-Date: 2021-04-15 10:31+0000\n"
 "Last-Translator: Kanoko Kondo <yves0625@gmail.com>\n"
 "Language-Team: Japanese <http://weblate.taler.net/projects/gnunet/website/ja/"
@@ -78,7 +78,7 @@ msgstr "概要"
 msgid "News"
 msgstr "更新情報"
 
-#: common/navigation.j2.inc:36 template/index.html.j2:337
+#: common/navigation.j2.inc:36 template/index.html.j2:338
 msgid "Applications"
 msgstr "アプリケーション"
 
@@ -86,7 +86,7 @@ msgstr "アプリケーション"
 msgid "Community"
 msgstr "コミュニティ"
 
-#: common/navigation.j2.inc:43 template/index.html.j2:340
+#: common/navigation.j2.inc:43 template/index.html.j2:341
 msgid "Engage"
 msgstr "参加する"
 
@@ -2945,19 +2945,19 @@ msgstr ""
 msgid "The Internet of tomorrow needs GNUnet today"
 msgstr ""
 
-#: template/index.html.j2:27
+#: template/index.html.j2:28
 msgid "Latest news"
 msgstr ""
 
-#: template/index.html.j2:33
+#: template/index.html.j2:34
 msgid "Older news entries"
 msgstr ""
 
-#: template/index.html.j2:48
+#: template/index.html.j2:49
 msgid "The Internet is broken"
 msgstr ""
 
-#: template/index.html.j2:50
+#: template/index.html.j2:51
 msgid ""
 "The conventional Internet is currently like a system of roads with deep "
 "potholes and highwaymen all over the place. Even if you still can use the "
@@ -2980,11 +2980,11 @@ msgid ""
 "vulnerable for multiple attacks massively threatening our freedom. -->"
 msgstr ""
 
-#: template/index.html.j2:95
+#: template/index.html.j2:96
 msgid "GNUnet helps building a new Internet"
 msgstr ""
 
-#: template/index.html.j2:97
+#: template/index.html.j2:98
 msgid ""
 "GNUnet is a network protocol stack for building secure, distributed, and "
 "privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
@@ -2993,11 +2993,11 @@ msgid ""
 "internet\">old insecure Internet</a> protocol stack."
 msgstr ""
 
-#: template/index.html.j2:120
+#: template/index.html.j2:121
 msgid "Metadata is exposed"
 msgstr ""
 
-#: template/index.html.j2:122
+#: template/index.html.j2:123
 msgid ""
 "Your metadata is just as revealing as the actual content; and it gets "
 "exposed on the Internet.<br> Even though transport encryption is "
@@ -3006,11 +3006,11 @@ msgid ""
 "frequency and the volume of communication are all still revealed.<br>"
 msgstr ""
 
-#: template/index.html.j2:151
+#: template/index.html.j2:152
 msgid "GNUnet provides privacy-by design"
 msgstr ""
 
-#: template/index.html.j2:153
+#: template/index.html.j2:154
 msgid ""
 "It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/"
 "papers/65.pdf\"> improving addressing, routing, naming and content "
@@ -3021,11 +3021,11 @@ msgid ""
 "routing, naming and content distribution in a technically robust manner. -->"
 msgstr ""
 
-#: template/index.html.j2:178
+#: template/index.html.j2:179
 msgid "Freedoms are not respected"
 msgstr ""
 
-#: template/index.html.j2:180
+#: template/index.html.j2:181
 msgid ""
 "Today, monitoring increasingly centralized infrastructure, proprietary "
 "implementations, traffic shapers and firewalls restrict all of the <a "
@@ -3033,11 +3033,11 @@ msgid ""
 "html\">essential freedoms</a> to various degrees."
 msgstr ""
 
-#: template/index.html.j2:204
+#: template/index.html.j2:205
 msgid "GNUnet supports a free and open society"
 msgstr ""
 
-#: template/index.html.j2:206
+#: template/index.html.j2:207
 msgid ""
 "GNUnet is a self-organizing network and it is <a class=\"link\" "
 "href=\"https://www.gnu.org/philosophy/free-sw.html\">free software</a> as in "
@@ -3049,21 +3049,21 @@ msgid ""
 "applications (\"modify\")."
 msgstr ""
 
-#: template/index.html.j2:230
+#: template/index.html.j2:231
 msgid "The state of the art is inefficient"
 msgstr ""
 
-#: template/index.html.j2:232
+#: template/index.html.j2:233
 msgid ""
 "The ongoing hype around distributed ledgers and blockchains is detrimental "
 "to the health of our planet."
 msgstr ""
 
-#: template/index.html.j2:253
+#: template/index.html.j2:254
 msgid "Sustainability"
 msgstr ""
 
-#: template/index.html.j2:255
+#: template/index.html.j2:256
 #, python-format
 msgid ""
 "GNUnet does not require a decentralized, public ledger. This eliminates the "
@@ -3073,11 +3073,11 @@ msgid ""
 "and use more efficient technology stacks where needed</a>."
 msgstr ""
 
-#: template/index.html.j2:277
+#: template/index.html.j2:278
 msgid "Decentralization is the key, but hard"
 msgstr ""
 
-#: template/index.html.j2:280
+#: template/index.html.j2:281
 msgid ""
 "<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
 "distributed or P2P project develops its own library stack, covering "
@@ -3088,11 +3088,11 @@ msgid ""
 "potential number of vulnerabilities."
 msgstr ""
 
-#: template/index.html.j2:312
+#: template/index.html.j2:313
 msgid "GNUnet is a framework"
 msgstr ""
 
-#: template/index.html.j2:314
+#: template/index.html.j2:315
 msgid ""
 "It offers a metadata-preserving foundation for your application. It offers "
 "components for addressing, reliable encrypted channels with advanced routing "
@@ -3100,13 +3100,13 @@ msgid ""
 "spanning almost two decades."
 msgstr ""
 
-#: template/index.html.j2:334
+#: template/index.html.j2:335
 #, fuzzy
 #| msgid "read more"
 msgid "Learn more"
 msgstr "詳細"
 
-#: template/index.html.j2:343
+#: template/index.html.j2:344
 msgid "Get started"
 msgstr ""
 
@@ -3244,6 +3244,7 @@ msgstr ""
 #: template/install-on-openwrt.html.j2:48 template/l2o/mile1.html.j2:114
 #: template/l2o/mile2.html.j2:64 template/l2o/mile3.html.j2:93
 #: template/l2o/mile4.html.j2:71 template/l2o/mile5.html.j2:63
+#: template/l2o/mile6.html.j2:45
 #, fuzzy
 #| msgid "Continuous Integration"
 msgid "Configuration"
@@ -3453,87 +3454,40 @@ msgstr ""
 
 #: template/dev_pages/t3sserakt.html.j2:26
 msgid ""
-"At the moment I am working on Transport Next Generation (TNG). The current "
-"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
-"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
-"bandwidth allocation and choosing plugins has several issues with its "
-"design. With the Layer-2-Overlay project we like to implement the design "
-"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
-"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
-"\">project page</a>."
-msgstr ""
-
-#: template/dev_pages/t3sserakt.html.j2:41
-msgid "Future Work"
-msgstr ""
-
-#: template/dev_pages/t3sserakt.html.j2:43
-msgid ""
-"The next project I will work on is named \"Probabilistic NAT Traversal\"."
-msgstr ""
-
-#: template/dev_pages/t3sserakt.html.j2:48
-msgid ""
 "Today consumer devices are behind a NAT quite often, restricting internet "
 "connectivity. There are several methods to reach peers being behind a NAT, "
 "but there are as many reasons those existing methods might fail. We will "
 "implement a new way of NAT traversal that we think of being independent from "
 "the existing network configuration, and does not require a third party which "
-"is not natted helping two peers to connect to each other. Two peers trying "
-"to connect to each other will send out a burst of connection attempts to the "
-"other peer on different ports. The sheer vast amount of connections attempts "
-"from both side will lead to a high probability that two connection attempts "
-"from both peers onto the same port will be at the same time leading to a "
-"successful connection between those peers."
-msgstr ""
-
-#: template/dev_pages/t3sserakt.html.j2:58
-msgid ""
-"There are two problems a NAT traversal method has to solve. First there "
-"needs to be a method to know the global IP address of a peer A another peer "
-"B wants to connect to. Second – because inbound connections from the outside "
-"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
-"connection attempt by peer B. The most common solution for both problems is "
-"to have a third party C which is not behind a NAT. This third party C "
-"obviously knows the global IP address of natted peers, after peer A is "
-"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
-"informs A about it. Using this method for a privacy preserving network like "
-"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
-"can be used for deanonymization attacks and cencorship. Also any additional "
-"infrastructure needed to provide some kind of functionality has to be "
-"maintained by someone, becoming a target and/or point of failure. Therefore "
-"this method is not suitable. More sophisticated methods like \"Autonomous "
-"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
-"party for the initiation of the connection, are not successful in all "
-"circumstances, because this method depend on the behavior of the NAT "
-"firewall."
+"is not natted helping two peers to connect to each other. For details have a "
+"look on the <a href=\"../probnat/\">project page</a>"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:44
+#, fuzzy
+#| msgid "GSoC Projects"
+msgid "Past Project"
+msgstr "GSoC プロジェクト"
+
+#: template/dev_pages/t3sserakt.html.j2:46
+msgid "Transport Next Generation"
 msgstr ""
 
-#: template/dev_pages/t3sserakt.html.j2:72
+#: template/dev_pages/t3sserakt.html.j2:48
 msgid ""
-"If two natted peers are using the method to start a burst of connection "
-"attempts, this method still needs the global IP of the other peer and a "
-"“start signal” to coordinate. In the NGI Assure project L2O we are "
-"establishing a backchannel with neighbourhood routing over an ad- hoc "
-"distance vector protocol to solve the problem of not directly connected "
-"peers. The peers serving as hops to a distant peer which are a direct "
-"neighbour of the start or end peer on that path do know the global IP "
-"address of the start or end peer. If those two peers like to use the burst "
-"method for hole punching the global IP address is known. Via the distance "
-"vector protocol we are also able to communicate the \"start signal\". Also "
-"in the L2O project we introduced a new test framework for GNUnet to test "
-"network setups with peers having restricted connectivity. This test "
-"framework will be used to create test setups suitable to test possible NAT "
-"configurations. A challenge for this NAT traversal method will be how to "
-"handle the burst in terms of network load, thus we need to experiment with "
-"different frequencies and the amount of connection attempts."
+"The current GNUnet TRANSPORT architecture with its pluggable transport "
+"mechanism (TCP, UDP, HTTP(S) and other protocols) together with the ATS "
+"subsystem for bandwidth allocation and choosing plugins has several issues "
+"with its design. With the Layer-2-Overlay project we like to implement the "
+"design goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. "
+"For details have a look on the <a href=\"../l2o/\">project page</a>."
 msgstr ""
 
-#: template/dev_pages/t3sserakt.html.j2:94
-msgid "Past Work"
+#: template/dev_pages/t3sserakt.html.j2:63
+msgid "Voluntary Work"
 msgstr ""
 
-#: template/dev_pages/t3sserakt.html.j2:96
+#: template/dev_pages/t3sserakt.html.j2:65
 msgid ""
 "In the past I have tried to help making the vision of the <a href=\"http://"
 "secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
@@ -3548,7 +3502,7 @@ msgid ""
 "that they can be used prouctively."
 msgstr ""
 
-#: template/dev_pages/t3sserakt.html.j2:111
+#: template/dev_pages/t3sserakt.html.j2:80
 #, fuzzy
 #| msgid "Contact information"
 msgid "Contact Information"
@@ -3557,11 +3511,12 @@ msgstr "お問い合わせ"
 #: template/l2o/index.html.j2:7 template/l2o/mile1.html.j2:7
 #: template/l2o/mile2.html.j2:7 template/l2o/mile3.html.j2:7
 #: template/l2o/mile4.html.j2:7 template/l2o/mile5.html.j2:7
-#: template/l2o/testng.html.j2:7
+#: template/l2o/mile6.html.j2:7 template/l2o/testng.html.j2:7
 msgid "NGI Assure project: Layer-2-Overlay"
 msgstr ""
 
 #: template/l2o/index.html.j2:13 template/l2o/index.html.j2:35
+#: template/probnat/index.html.j2:13 template/probnat/index.html.j2:35
 #, fuzzy
 #| msgid "Documentation"
 msgid "Project motivation"
@@ -3572,30 +3527,31 @@ msgid "New Test Framework"
 msgstr ""
 
 #: template/l2o/index.html.j2:15 template/l2o/index.html.j2:75
+#: template/probnat/index.html.j2:14 template/probnat/index.html.j2:64
 msgid "Milestones"
 msgstr ""
 
-#: template/l2o/index.html.j2:16
+#: template/l2o/index.html.j2:16 template/probnat/index.html.j2:15
 msgid "Milestone 1"
 msgstr ""
 
-#: template/l2o/index.html.j2:17
+#: template/l2o/index.html.j2:17 template/probnat/index.html.j2:16
 msgid "Milestone 2"
 msgstr ""
 
-#: template/l2o/index.html.j2:18
+#: template/l2o/index.html.j2:18 template/probnat/index.html.j2:17
 msgid "Milestone 3"
 msgstr ""
 
-#: template/l2o/index.html.j2:19
+#: template/l2o/index.html.j2:19 template/probnat/index.html.j2:18
 msgid "Milestone 4"
 msgstr ""
 
-#: template/l2o/index.html.j2:20
+#: template/l2o/index.html.j2:20 template/probnat/index.html.j2:19
 msgid "Milestone 5"
 msgstr ""
 
-#: template/l2o/index.html.j2:21
+#: template/l2o/index.html.j2:21 template/probnat/index.html.j2:20
 msgid "Milestone 6"
 msgstr ""
 
@@ -3804,13 +3760,14 @@ msgstr ""
 msgid ""
 "The test cases in the CI are measuring the performance gains. This "
 "measurement can be compared with the measurement of milestone 5. Again one "
-"outcome of this milestone will be a stable release. Documentation of the "
-"interpeer project analysis."
+"outcome of this milestone will be a stable release.<br/> Documentation of "
+"the interpeer project analysis. More <a href=\"mile6.html\">Details</a>."
 msgstr ""
 
 #: template/l2o/mile1.html.j2:13 template/l2o/mile2.html.j2:13
 #: template/l2o/mile3.html.j2:13 template/l2o/mile4.html.j2:13
-#: template/l2o/mile5.html.j2:13 template/l2o/testng.html.j2:13
+#: template/l2o/mile5.html.j2:13 template/l2o/mile6.html.j2:13
+#: template/l2o/testng.html.j2:13
 msgid "Project main page"
 msgstr ""
 
@@ -4011,6 +3968,7 @@ msgid ""
 msgstr ""
 
 #: template/l2o/mile4.html.j2:21 template/l2o/mile5.html.j2:32
+#: template/l2o/mile6.html.j2:21
 msgid "TNG Service"
 msgstr ""
 
@@ -4139,7 +4097,7 @@ msgid ""
 "</ul>"
 msgstr ""
 
-#: template/l2o/mile5.html.j2:130
+#: template/l2o/mile5.html.j2:130 template/l2o/mile6.html.j2:57
 #, fuzzy
 #| msgid "Performance Analysis"
 msgid "Performance Measurement"
@@ -4147,23 +4105,99 @@ msgstr "パフォーマンス分析"
 
 #: template/l2o/mile5.html.j2:132
 msgid ""
-"The outcome of the performance measurement was 20 MByte/s for packet size of "
-"65000 bytes. For this measurement the TNG layer was using tcp only, because "
+"The outcome of the performance measurement was ~24 MByte/s for packets with "
+"size of 65000 bytes. To follow up on this measurement one has to get the "
+"mean time the packets of 65000 bytes needed to reach another peer, to "
+"calculate the data rate, by doing<br/><br/> <code>grep \"mean time "
+"traveled\" 1b8b9ebe2_test.out|tail -1</code><br/><br/> on the log file <a "
+"href=\"/l2o/1b8b9ebe2_test.out\">1b8b9ebe2_test.out</a> of the performance "
+"test case. For this measurement the TNG layer was using tcp only, because "
 "there was an unfixed bug, if running tcp and udp in parallel."
 msgstr ""
 
-#: template/l2o/mile5.html.j2:140
+#: template/l2o/mile5.html.j2:142
 #, fuzzy
 #| msgid "Documentation"
 msgid "API Documentation"
 msgstr "資料"
 
-#: template/l2o/mile5.html.j2:142
+#: template/l2o/mile5.html.j2:144
 msgid ""
 "Documentation of the new <a href='https://docs.gnunet.org/doxygen/d2/dc4/"
 "group__TNG.html'>TNG Api</a>."
 msgstr ""
 
+#: template/l2o/mile6.html.j2:23
+msgid ""
+"<ul> <li>Introduced frags_in_flight flag. With this flag we check if "
+"fragments of a PendingMessage are being send right now, to not resend single "
+"fragments, but the PendingMessage at once.</li> <li>The time to wait for "
+"resending a PendingMessage - which was fragmented - is calculated, depending "
+"on the number of fragments present, and how much of the PendingMessage was "
+"already fragmented.</li> <li>ValidationState now contains the addres prefix "
+"of the address being validated, because we have to check which communicator "
+"gave us the validation response.</li> <li>Handling flow control takes used "
+"window size into account, together with data loss.</li> <li>We do not update "
+"queue performance if PendingMessage was resend.</li> <li>Changed test case "
+"to except 0.5% packet loss.</li> <li>Removed misplaced sending of an "
+"acknowlegement in udp communicator.</li> <li>GNUNET_SERVICE_client_continue "
+"was misplaced after receiving CORE Ack, blocking the service.</li> <li>Fixed "
+"bug when checking, if fragment sub tree is done.</li> <li>Fixed bug in "
+"calculation of delay for PendingAcknowledgement.</li> <li>Fixed bug in "
+"calculation of subtree fragment message size.</li> <li>Fixed bug that "
+"additional queues for the same communicator inherit the validity period.</"
+"li> <li>Fixed logic bug when searching for QueueEntry matching "
+"acknowledgement.</li> <li>Fixed misplaced increase of queue length.</li> </"
+"ul>"
+msgstr ""
+
+#: template/l2o/mile6.html.j2:47
+msgid ""
+"<table width=\"100%\"> <tr> <td width=\"60%\" style=\"vertical-align: top;"
+"\">src/transport/test_transport_simple_send_performance_topo.conf</td><td "
+"width=\"40%\" style=\"vertical-align: top;\">Changed configuration to use "
+"TCP and UDP together.</td> </tr> </table>"
+msgstr ""
+
+#: template/l2o/mile6.html.j2:59
+msgid ""
+"The outcome of the performance measurement was ~66 MByte/s for packets with "
+"size of 65000 bytes. To follow up on this measurement one has to get the "
+"mean time the packets of 65000 bytes needed to reach another peer, to "
+"calculate the data rate, by doing<br/><br/> <code>grep \"mean time "
+"traveled\" 811c040a2_test.out|tail -1</code><br/><br/> on the log file <a "
+"href=\"/l2o/811c040a2_test.out\">811c040a2_test.out</a> of the performance "
+"test case. The performance increased from ~24 MByte/s measured with the code "
+"revision of milestone 5 by using TCP only to ~66 MByte/s measured with the "
+"code revision of milestone 6 for packet size of 65000 bytes using TCP and "
+"UDP together. There are still possibilities to increase performance "
+"documented as TODOs in the source code."
+msgstr ""
+
+#: template/l2o/mile6.html.j2:70
+msgid "Synergie with Interpeer Channeler project."
+msgstr ""
+
+#: template/l2o/mile6.html.j2:72
+msgid ""
+"The Interpeer library Channeler and the L2O project have some goals in "
+"common. These include independence of the transmission protocol used, "
+"congestion control, reliability. Other goals of the Channeler project are "
+"not goals of the L2O project, but are already implemented or planned for "
+"other layers of GNUnet, such as multiplexing and ordered delivery of "
+"packages. There are also goals of the L2O project that are not goals of the "
+"Channeler project, such as metadata protection and identity assurance of "
+"communication partners. Due to these half overlapping half disjoint targets "
+"it is not reasonable that on project makes use of the other as a whole. "
+"However, parts of one project may well be applicable in the other. Since the "
+"Channeler project is not yet completed, it is not yet possible to identify "
+"the interesting parts beyond doubt. Interesting for the further development "
+"of L2O is the \"Zero-Copy and Buffering\" functionality of the Channeler "
+"project. This is also planned for future versions of L2O. In conclusion, "
+"both projects can benefit from each other. At this point in time, it is "
+"still too early to tackle this concretely."
+msgstr ""
+
 #: template/l2o/testng.html.j2:21
 msgid "Netjail setup and execution"
 msgstr ""
@@ -4295,6 +4329,203 @@ msgstr ""
 msgid "News archives:"
 msgstr "アーカイブ"
 
+#: template/probnat/index.html.j2:7
+msgid "NGI Assure project: Probabilistic NAT Traversal"
+msgstr ""
+
+#: template/probnat/index.html.j2:21
+msgid "Milestone 7"
+msgstr ""
+
+#: template/probnat/index.html.j2:28
+msgid ""
+"This project was funded through the NGI Assure Fund, a fund established by "
+"<a href=\"https://nlnet.nl/project/ProbabilisticNAT\">NLnet</a>.</br>"
+msgstr ""
+
+#: template/probnat/index.html.j2:40
+msgid ""
+"For establishing a peer to peer (p2p) network among regular internet users, "
+"unhindered connectivity is anything but self-evident. Today consumer devices "
+"are often not directly reachable via the internet but quite often are behind "
+"a so called NAT delivering only indirect internet connectivity."
+msgstr ""
+
+#: template/probnat/index.html.j2:49
+msgid ""
+"There are several methods to reach peers who are behind a NAT, but there are "
+"as many reasons those existing methods might fail. Manual configuration for "
+"example, as it is possible for example with home routers, often does not "
+"work for mobile devices like mobile phones. A further category of methods is "
+"subsumed under the term NAT hole punching. This exploits a behavior of the "
+"gateway that keeps the port of an outgoing packet open for a potential "
+"response. To make this port known to another peer a third peer is needed who "
+"is not behind a NAT. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall. All methods have in common that the external IP address of the "
+"peer behind the NAT must be known."
+msgstr ""
+
+#: template/probnat/index.html.j2:58
+msgid ""
+"Two peers trying to connect to each other will send out a burst of "
+"connection attempts to the other peer on different ports. The sheer vast "
+"amount of connections attempts from both side will lead to a high "
+"probability that two connection attempts from both peers onto the same port "
+"will be at the same time leading to a successful connection between those "
+"peers. If two natted peers are using the method to start a burst of "
+"connection attempts, this method still needs the global IP of the other peer "
+"and a “start signal” to coordinate. In the NGI Assure project <a href=\"../"
+"l2o\">L2O</a> we are establishing a backchannel with neighbourhood routing "
+"over an ad-hoc distance vector protocol to solve the problem of not directly "
+"connected peers. The peers serving as hops to a distant peer which are a "
+"direct neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\"."
+msgstr ""
+
+#: template/probnat/index.html.j2:68
+msgid "Milestone 1 Test Infrastructure"
+msgstr ""
+
+#: template/probnat/index.html.j2:71
+msgid ""
+"Extending the testing framework, which was already designed and implemented "
+"for the L2O project. <ul> <li>Enhance the testing framework with a new kind "
+"of component (NAT component).</li> <li>Implement logic to keep ports open "
+"used during network translation.</li> <li>Extend the test framework "
+"configuration to configure the new components.</li> </ul></br>"
+msgstr ""
+
+#: template/probnat/index.html.j2:84
+msgid ""
+"Test case which tests the new testing functionality. Adding documentation."
+msgstr ""
+
+#: template/probnat/index.html.j2:90
+msgid "Milestone 2 Synchronization"
+msgstr ""
+
+#: template/probnat/index.html.j2:93
+msgid ""
+"This task is to implement the protocol that is doing the signaling for "
+"synchronizing two peers which do like to connect to each other. <ul> <li>Two "
+"peers which got connected via DV signaling each other being behind a NAT.</"
+"li> <li>Learning the external IP address+port from already connected peers, "
+"exchange with the peers that want to connect.</li> <li>Set a common start "
+"time. One peer is selected to be leading (comparing peer ids like it is done "
+"in CADET)</li> </ul>"
+msgstr ""
+
+#: template/probnat/index.html.j2:107
+msgid ""
+"Deliverable of this milestone is integrating the protocol implementation "
+"into the GNUnet stack, a test case which tests that two peers successfully "
+"exchange the messages of the implemented protocol until the condition is "
+"reached that both nodes are ready for the burst mode. Additionally there "
+"will be a protocol documentation."
+msgstr ""
+
+#: template/probnat/index.html.j2:116
+msgid "Milestone 3 Burst Protocol"
+msgstr ""
+
+#: template/probnat/index.html.j2:119
+msgid ""
+"Burst to establish connectivity (IP_RAW, SYN send for TCP; normal for UDP). "
+"A burst of synchronized (same ports on each peer) connection attempts on all "
+"available ports will lead to a high probability for a successful connection."
+"The connection in the TCP case is not final, because the TCP connection is "
+"only done in the user space."
+msgstr ""
+
+#: template/probnat/index.html.j2:128
+msgid ""
+"The protocol implementation will be integrated into the GNUnet stack, one "
+"Test case will test two peers are finaly connected (UDP case), another test "
+"case for TCP tests if both peers end up at the same port and the protocol "
+"will be documented."
+msgstr ""
+
+#: template/probnat/index.html.j2:136
+msgid "Milestone 4 TCP Repair"
+msgstr ""
+
+#: template/probnat/index.html.j2:139
+msgid ""
+"For the TCP case the connection was established sending packages from user "
+"space using raw sockets. To let the kernel know about the TCP connection we "
+"will use the “repair mode” of the setsockopt() system call."
+msgstr ""
+
+#: template/probnat/index.html.j2:147
+msgid ""
+"Integration into the GNUnet stack and a test case testing two peers are "
+"finaly (kernel TCP socket) connected."
+msgstr ""
+
+#: template/probnat/index.html.j2:154
+msgid "Milestone 5 Privilege Minimization"
+msgstr ""
+
+#: template/probnat/index.html.j2:157
+msgid ""
+"Privilege minimization, using SUID/SGID helpers with required capabilities. "
+"We need privileged access to system resources for some parts of the "
+"protocol, e.g. the TCP repair mode. This task will implement helper "
+"executables which are doing this privileged access, to be used by other "
+"components not having special privileges. (see § 2.2.1 Access Control, The "
+"GNUnet System, https://grothoff.org/christian/habil.pdf)"
+msgstr ""
+
+#: template/probnat/index.html.j2:167
+msgid ""
+"Helper executables and cli applications using the helpers. Integration into "
+"the GNUnet stack. Man pages for the cli applications. First release of all "
+"the implementation."
+msgstr ""
+
+#: template/probnat/index.html.j2:174
+msgid "Milestone 6 Port Range Optimization"
+msgstr ""
+
+#: template/probnat/index.html.j2:177
+msgid ""
+"Detect likely port ranges (peers exchanging lists of 'working' IP+Port "
+"combinations)."
+msgstr ""
+
+#: template/probnat/index.html.j2:183
+msgid ""
+"Test case with setup using specific port ranges testing use of port subset. "
+"First optimization release."
+msgstr ""
+
+#: template/probnat/index.html.j2:190
+msgid "Milestone 7 Optimization"
+msgstr ""
+
+#: template/probnat/index.html.j2:193
+msgid ""
+"Prioritize likely working IP addresses (no point in trying to go from 10.x "
+"to 192.168.x). There might be optimization we do not know anything about yet."
+msgstr ""
+
+#: template/probnat/index.html.j2:200
+msgid ""
+"Test case with setup using specific IP addresses testing if not all "
+"available IP addresses are used. Test cases testing general optimization. "
+"Second optimization release."
+msgstr ""
+
 #: template/reclaim/faq.html.j2:6
 msgid "Frequently asked questions"
 msgstr ""
-- 
cgit v1.2.3