GNUnet/Website — German @ GNU Taler Weblate: News archives:

Zen

	English	German	Actions
	Although netjail_exec.sh can execute an arbitrary command in the ng testing framework a special command is used: gnunet-cmds-helper This commands itself is of a special kind named helper processes which communicates via GNUNET_MessageHeaders on stdin/stdout with the process that started the helper. The gnunet-cmds-helper is used to load testcase plugins. Those plugins are implementations of an api which is used to start different test cases. Those plugins are dynamically loaded by gnunet-cmds-helper. Each plugin defines the commands which are running in a local interpreter loop started by the helper on that specific network namespace node. The plugins are also responsible for the communication via the helper with the master interpreter loop.
	Command Pattern
	The testing framework borrowed from the <a href="https://docs.taler.net/developers-manual.html#testing-library">GNU Taler testing library</a> was extended to handle asychronous commands. Therefore a struct GNUNET_TESTING_AsyncContext was added to struct GNUNET_TESTING_Command. By default the continuation function of GNUNET_TESTING_AsyncContext is the interpreter_next function of the interpreter loop (blocking asynchronous command) which will be executed calling GNUNET_TESTING_async_finish, when the asynchronous task finished, but also can be any other function to be executed when the asynchronous task is non blocking.
	Topology Configuration	Konfiguration
	The topology of the netjail setup can be configured via a configuration file, or with a configuration string handed over to the generic binary for starting netjail based tests.</br></br> Both method can be examined in two example test scripts</br></br> test_transport_send_simple.sh</br></br> and</br></br> test_transport_send_simple_string.sh</br></br> The Syntax of the configuration is as follows.</br></br> The configuration string is structured by lines and the delimiter ':' used for seperating key/value(s) pairs and the chars '{' and '}' for grouping several key/value pairs as value and '\|' to separate a group of values from the key/value(s) pair identifying a line. Below you find the EBNF of the configuration syntax.</br></br> config = line, {line} ;<br/><br/> line = ( "M:", NumberOfNodesPerSubnet ) \| ( "N:", NumberOfSubnets ) \| ( "X:", NumberOfGlobalNodes ) \| NumberOfAdditionalConnections \| ( "T:", GlobalPluginName ) \| ( GlobalPeer, "\|", KValue ) \| ( "R:", IndexOfSubnetRouter, "\|", RValue ) \| ( SubnetPeer, "\|", PValue ) ;<br/><br/> NumberOfNodesPerSubnet = Zero \| NaturalNumber ;<br/><br/> NumberOfSubnets = NaturalNumber ;<br/><br/> NumberOfGlobalNodes = NaturalNumber ;<br/><br/> NumberOfAdditionalConnections = "AC:", NaturalNumber GlobalPluginName = "libgnunet_test_transport_plugin_cmd_", PluginName ;<br/><br/> GlobalPeer = "K", ":", IndexOfGlobalNode ;<br/><br/> KValue = EstablishConnectionToPeerViaProtocol ;<br/><br/> IndexOfSubnetRouter = Zero \| NaturalNumber ;<br/><br/> RValue = OpenTCP, "\|", OpenUDP ;<br/><br/> SubnetPeer = "P:", SubnetIndex, ":", NodeIndexInSubnet ;<br/><br/> PValue = EstablishConnectionToPeerViaProtocol, { "\|", "{", NumberOfAdditionalConnections, "}" } ;<br/><br/> Zero = "0" ;<br/><br/> NaturalNumber = NumeralWithoutZero, { Numeral } ;<br/><br/> PluginName = Letter , { ( Letter \| "_" ) } ;<br/><br/> IndexOfGlobalNode = Zero \| NaturalNumber ;<br/><br/> EstablishConnectionToPeerViaProtocol = "{" "connect", ":" EstablishConnectionToPeerViaProtocolValues "}" ;<br/><br/> OpenTCP = OpenTCPNoSource \| OpenTCPWithSource ;<br/><br/> OpenUDP = OpenUDPNoSource \| OpenUDPWithSource ;<br/><br/> SubnetIndex = NaturalNumber ;<br/><br/> NodeIndexInSubnet = NaturalNumber ;<br/><br/> NumeralWithoutZero = "0" \| Numeral ;<br/><br/> Numeral = "1" \| "2" \| "3" \| "4" \| "5" \| "6" \| "7" \| "8" \| "9" ;<br/><br/> Letter = "A" \| "B" \| ... \| "Z" \| "a" \| ... \| "z";<br/><br/> EstablishConnectionToPeerViaProtocolValues = EstablishConnectionToPeerViaProtocolValue { "\|", EstablishConnectionToPeerViaProtocolValue } OpenTCPNoSource = "{tcp_port:", switch, "}" ;<br/><br/> OpenUDPNoSource = "{udp_port:", switch, "}" ;<br/><br/> OpenTCPWithSource = "{tcp_port:", SubnetPeer, { "tcp_port", SubnetPeer } ;<br/><br/> OpenTUDWithSource = "{udp_port:", SubnetPeer, { "udp_port", SubnetPeer } ;<br/><br/> EstablishConnectionToPeerViaProtocolValue = "{", ( GlobalPeer \| SubnetPeer ), ":", Protocol, "}" ;<br/><br/> switch = On \| Off ;<br/><br/> Protocol = "tcp" \| "udp" ;<br/><br/> On = 1 ;<br/><br/> Off = 0 ;<br/><br/>
	News archives:	Nachrichten-Archive
	To use the probabilistic NAT traversal library, the peers to be connected must first be synchronized. For that, each peer has to use two API calls.<br/><br/> enum GNUNET_GenericReturnValue<br/> GNUNET_is_burst_ready (struct GNUNET_TIME_Relative rtt_avarage,<br/> &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; struct GNUNET_BurstSync burst_sync,<br/> &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; GNUNET_SCHEDULER_TaskCallback task,<br/> &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; struct GNUNET_StartBurstCls task_cls)<br/><br/> and<br/><br/> struct GNUNET_BurstSync *<br/> GNUNET_get_burst_sync_msg (struct GNUNET_TIME_Relative rtt_avarage,<br/> &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; enum GNUNET_GenericReturnValue sync_ready)<br/><br/> The second is to create the synchronisation message which the caller has to send to the other peer. Within GNUnet the Distance Vector DV protocol is used for sending the synchronisation message. Applications which do not want to use the complete GNUnet stack have to use transportion by other means.<br/><br/> The API call needs two parameters. The avarage round trip time rtt_avarage has to be provided by the callers application. In GNUnet this information is constantly calculated from messages delivered by DV. Again, applications not using the GNUnet stack have to assemble this information by themself. The round trip time has to be calculated as the time a message needs to arrive at another peer plus the time a response to this message needs to travel back. The messages used to measure this time needs to be send via the same transportion mechanism like the burst synchromisation method. The value used in the API should be an average over several RTTs. rtt_average is measured in microseconds. <br/><br/> The second parameter is returned by the first API call and must be temporarily stored to use it in the second. This is the burst synchromisation method, which encapsulates the RTT calculated by the sending peer, and if that peer is ready to sync.<br/><br/> The first API call also needs the avarage RTT and the synchronisation message received from another peer. The callback is called, if both peers are ready to synchronize. Therefore the callback should start the burst mode which will finally do the hole punch for NAT traversal. One can find an example in the GNUnet code src/service/transport/gnunet-service-transport.c in the function handle_flow_control. <br/><br/>
	After the to peers were synchronized each peer starts the burst mode. The burst mode is started by calling the function<br/><br/> struct GNUNET_SCHEDULER_Task <br/> GNUNET_get_udp_socket (struct GNUNET_UdpSocketInfo sock_info,<br/> &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; GNUNET_NotifyUdpSocket nus);<br/><br/> this function shall be called from within the callback function<br/><br/> GNUNET_SCHEDULER_TaskCallback task<br/><br/> which was a parameter of the function<br/><br/> GNUNET_is_burst_ready<br/><br/> we used to check if the peers are synchronized. The first parameter is the default socket the application is using. The second parameter the callback to call, if the hole punching was successful. The callback is a function with one parameter GNUNET_NotifyUdpSocket which holds information about the socket we received a message from the other peer and the address we can reach the other peer. The socket can be used to receive further message.<br/><br/> The function<br/><br/> void<br/> GNUNET_stop_burst (struct GNUNET_NETWORK_Handle *do_not_touch);<br/><br/> must be called, if the hole punch message was received via the default socked, because the library does not recognize this. It also must be called, before one starts a new burst to be sure an old one is not running anymore. A third case is, when the system shuts down. <br/><br/> Again, one can find an example in the GNUnet code src/service/transport/gnunet-service-transport.c
	NGI Assure project: Probabilistic NAT Traversal
	This project was funded through the NGI Assure Fund, a fund established by <a href="https://nlnet.nl/project/ProbabilisticNAT">NLnet</a>.</br>
	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.

Loading…

Ariane

Translation changed

English

German 12 characters edited Current translation

3 years ago

None

Source string changed

English 7 characters edited

3 years ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Glossary

English	German
No related strings found in the glossary.

String information

Source string location

template/news/index.html.j2:46

String age

3 years ago

Last updated

4 months ago

Source string age

3 years ago

Translation file

locale/de/LC_MESSAGES/messages.po, string 588