Same as demo, tests expect a clean work directory, otherwise weird behavior will occur.

Those usually indicate that we're decoding something we shouldn't be, or that something wrong happened during decryption.

Nemu previously had an issue with PIDs above 4 hex digits (> 65535) where created network interfaces would have names of length exceeding IFNAMSIZ. These fixes have been upstreamed in nemu3.

Python3 added automatic detection of leaked resources, which causes lots of warnings in Re6st, mostly because of unclosed subprocess streams.

In the end, we should migrate completely to cryptography. A lot of bits of the legacy OpenSSL module are being deprecated, some that we use (notably signature and verification tools) already are.

The demo expects its storage directory to be clean at start, otherwise undefined behavior will occur.

See
https://manpages.debian.org/testing/systemd/systemd.service.5.en.html
and
https://manpages.debian.org/testing/systemd/systemd.unit.5.en.html

No need for more logging since the culprit is visible everywhere
in routing tables.

See https://github.com/git/git/commit/8959555cee7ec045958f9b6dd62e541affb7e7d9

This fixes default packet redirection when merging multiple re6st
networks. Nodes will then install multiple default routes for each re6st
network with the correspond src-prefix.

The changes include:

- redistribute default route with src prefix on gateways
- remove the now obsolete default option
- if subtrees is not available in the kernel, delete src prefix from
  the default route and don't advertise the default route to other
  nodes
- if there is no src prefix in the redistributed default route, add
  one to be retro-compatible with the old gateway behaviour