ud3tn

mirror of https://gitlab.com/d3tn/ud3tn.git synced 2026-08-15 12:50:49 +02:00

History

Felix Walter 87be9749af Re-integrate v0.13.0 routing code as "integrated default BDM" This makes µD3TN behave the same as v0.13.0 when executed without an additional commandline argument. A new commandline argument `-d` / `--external-dispatch` is added, which enables the use of external BDMs. The default forwarding implementation is now again provided using the v0.13 code, extracted from `e1621765a4` and adapted to the new agent-based forwarding implementation. Central changes to the old code include: - A new "Routing Agent" that handles incoming configuration commands, FIB updates, and BDM dispatch requests. - The use of the BDM authorization flag to authorize contact configuration commands. - The Contact Manager now only triggers the creation and removal of links / FIB entries; bundle dispatch is triggered through the FIB and BDM callback functions of the Routing Agent. - The fragmentation logic is adapted to store the original bundle along with an offset and length value, instead of pre-creating and storing the fragments. - The bundle re-scheduling logic integrated into the Routing Agent is simplified and does not support changing the fragmentation parameters. A new function is added to the Router that searches for a new route for such fragments that were already scheduled at some point, considering them as un-fragmentable bundle with overridden fragment offset and length. Signed-off-by: Felix Walter <felix.walter@d3tn.com>	2024-07-15 00:46:14 +02:00
..
default.nix	nix: Add SPDX-License-Identifier	2024-07-01 11:04:04 +02:00
multiple-services.nix	Re-integrate v0.13.0 routing code as "integrated default BDM"	2024-07-15 00:46:14 +02:00

Felix Walter 87be9749af Re-integrate v0.13.0 routing code as "integrated default BDM"

This makes µD3TN behave the same as v0.13.0 when executed without an
additional commandline argument. A new commandline argument `-d` /
`--external-dispatch` is added, which enables the use of external BDMs.
The default forwarding implementation is now again provided using the
v0.13 code, extracted from e1621765a4 and
adapted to the new agent-based forwarding implementation.

Central changes to the old code include:

- A new "Routing Agent" that handles incoming configuration commands,
  FIB updates, and BDM dispatch requests.
- The use of the BDM authorization flag to authorize contact
  configuration commands.
- The Contact Manager now only triggers the creation and removal of
  links / FIB entries; bundle dispatch is triggered through the FIB and
  BDM callback functions of the Routing Agent.
- The fragmentation logic is adapted to store the original bundle along
  with an offset and length value, instead of pre-creating and storing
  the fragments.
- The bundle re-scheduling logic integrated into the Routing Agent is
  simplified and does not support changing the fragmentation parameters.
  A new function is added to the Router that searches for a new route
  for such fragments that were already scheduled at some point,
  considering them as un-fragmentable bundle with overridden fragment
  offset and length.

Signed-off-by: Felix Walter <felix.walter@d3tn.com>

2024-07-15 00:46:14 +02:00

default.nix nix: Add SPDX-License-Identifier 2024-07-01 11:04:04 +02:00

multiple-services.nix Re-integrate v0.13.0 routing code as "integrated default BDM" 2024-07-15 00:46:14 +02:00