RNS β 0.2.6

This beta release brings a range of improvements and a few bugfixes.

Improvements

• Added the "rnsd" utility for running Reticulum as a service
• Added the "rnstatus" utility for viewing interface status
• Added the "rnpath" utility for path lookups
• Added the "rnprobe" utility for testing connectivity
• Documentation has been improved and expanded
• Improved shutdown handling for shared instances
• Improved default configuration
• Improved recovery of TCP interfaces over unreliable links

Fixed bugs

• Fixed a bug in reverse table culling
• Fixed a regression in TCP interface client spawner

RNS β 0.2.5

This beta release brings a range of improvements and bugfixes.

Improvements

• Added endpoint tunneling for path restoration over intermittent or roving link layer connections.
• Added ability for TCP client interfaces to automatically reconnect if TCP socket drops.
• Improved link teardown handling.
• Improved interface error handling on non-recoverable / hardware errors.

Fixed bugs

• Fixed a bug that could cause path table entries to be culled two times in rare cases.
• Fixed a bug that could lead to the "outgoing" directive of interface configuration entries not being parsed correctly.

RNS β 0.2.4

This beta release brings a range of improvements and bugfixes.

Improvements

• Increased link MDU from 415 to 431 bytes by optimising transfer of Fernet tokens.
• All data lengths are now calculated dynamically from Reticulums base MTU, laying the groundwork for dynamic MTU interoperability.
• Disabled option to allow unencrypted links.
• Improved documentation.
• Improved request timeouts and handling.
• Improved link establishment.
• Improved resource transfer timing.

Fixed bugs

• Fixed a race condition in inbound proof handling.
• Fixed sequencing errors caused by duplicate HMU/request packets not being filtered.

RNS β 0.2.3

This beta release brings a range of improvements and bugfixes.

Improvements

• Improved resource handling.
• Improved timeout calculation for packets, links, resources and requests.
• Improved announce handling for shared instances.
• Improved default configuration template.
• Added example "Speedtest".

Fixed bugs

• Fixed an issue that caused request timeout even though response had occurred.
• Fixed an issue that caused identity files to be written incorrectly.
• Fixed resource sequencing errors not being handled gracefully.

RNS β 0.2.2

This beta release brings several new features to Reticulum along with two bugfixes.

IMPORTANT! This version breaks wire-format compatibility with all previous versions of Reticulum. You must update all of your nodes at the same time.

New features

• Link initiators can now identify to the remote peer over the link, once it has been set up. This can be used for authentication, amongst other things.
• Requests and responses of arbitrary sizes can now be carried out over links.
• UDP and TCP interfaces can now be bound to network device names (eth0, wlan0, etc.) instead of manually specifying listen IPs.

Fixed bugs

• Fixed a race condition in outbound transport packet filtering.
• Fixed an issue where local UDP broadcast echoes could get processed as inbound packets.

RNS β 0.2.1

This beta release sees significant improvements to bandwidth utilization and efficiency, while improving security by dropping RSA and moving completely to Curve25519.

• All asymmetric cryptography migrated to X25519/Ed25519. This has greatly improved efficiency and reduced protocol overhead significantly.
• Work has continued on the documentation, and the "Understanding Reticulum" chapters have been improved significantly in this release.
• Class methods dealing with setting callbacks have been renamed to be more intuitive.

As a few examples of the improved efficiency, a complete link establishment now only costs 240 bytes, down from 409 in the previous RSA version. An announce takes up 151 bytes vs 323.

RNS β 0.2.0

This is the first beta release of RNS. This release also marks the publication of the Reticulum documentation, manual, and API documentation. All core features of Reticulum are now implemented, functional and ready to use in external programs. The wire-format and API will only change if there is a very good reason, though internals are still likely to be altered and optimised, and features are likely to be added.