GlcoinCore/ud3tn
1
0
Fork 0
mirror of https://gitlab.com/d3tn/ud3tn.git synced 2026-08-13 12:33:27 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: testing: Adjust to using aap2-* tools

Browse source 
Signed-off-by: Felix Walter <felix.walter@d3tn.com>
This commit is contained in:
Felix Walter 2026-05-12 11:04:40 +02:00
parent bf1e32e4fc
commit 050b105cef
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/testing.md
View file

@ -148,8 +148,8 @@ All tests expect an environment with ION and µD3TN (incl. Python dependencies)
This test, provided in [`test/ion_interoperability/minimal_forwarding_test`](https://gitlab.com/d3tn/ud3tn/-/blob/master/test/ion_interoperability/minimal_forwarding_test), checks the following aspects:
- forwarding bundles from µD3TN to another instance of µD3TN via an ION instance using TCPCL
- receiving bundles sent by ION (via `bpsource`) in µD3TN (via `aap-receive`)
- receiving bundles sent by µD3TN (via `aap-send`) in ION (via `bprecvfile`)
- receiving bundles sent by ION (via `bpsource`) in µD3TN (via `aap2-receive`)
- receiving bundles sent by µD3TN (via `aap2-send`) in ION (via `bprecvfile`)
The script [`run.sh`](https://gitlab.com/d3tn/ud3tn/-/blob/master/test/ion_interoperability/minimal_forwarding_test/run.sh?ref_type=heads) expects two arguments:
@ -192,29 +192,29 @@ In summary:
3. Start µD3TN instances as needed. If you want to test with multiple instances, don't forget to specify different sockets/ports for AAP (via `-s` or `-a`/`-p`) and the CLAs (via `-c`). Refer to the [README.md](https://gitlab.com/d3tn/ud3tn/-/blob/master/README.md?ref_type=heads#usage) concerning the command line syntax. You can also find some pointers on running multiple instances in the [Quick Start Guide](./posix_quick_start_guide.md).
4. Configure the µD3TN instance(s) as needed:
Especially, add all outgoing contacts to other µD3TN or ION instances using `aap-config`, e.g.:
Especially, add all outgoing contacts to other µD3TN or ION instances using `aap2-config`, e.g.:
```sh
aap-config --tcp <aap-host> <aap-port> \
aap2-config --tcp <aap2-host> <aap2-port> \
--schedule <start> <duration> <rate> \
<eid> tcpclv3:<host>:<port>
```
5. Start the receiving end(s). If you want to receive bundles sent to a µD3TN instance, attach an `aap-receive` sink, e.g. via:
5. Start the receiving end(s). If you want to receive bundles sent to a µD3TN instance, attach an `aap2-receive` sink, e.g. via:
```sh
aap-receive --tcp <aap-host> <aap-port> \
aap2-receive --tcp <aap2-host> <aap2-port> \
-a <demux|service-number> -v
```
See the help output of `aap-receive` (via `-h`) for additional options to verify received payload data, etc.
See the help output of `aap2-receive` (via `-h`) for additional options to verify received payload data, etc.
If you want to receive data in ION, you can start an instance of `bprecvfile` or `bpsink` (see ION's documentation).
6. Inject bundles / run your tests. For sending a bundle through µD3TN, you can use `aap-send`, e.g. via:
6. Inject bundles / run your tests. For sending a bundle through µD3TN, you can use `aap2-send`, e.g. via:
```sh
aap-send --tcp <aap-host> <aap-port> \
aap2-send --tcp <aap2-host> <aap2-port> \
--agentid <demux|service-number> <dest-eid> "<payload-data>" -v
```