RNS β 0.3.1

This is a small maintenance and update release of Reticulum, including a few improvements. It also adds support for using ESP32-based T-Beam devices.

Improvements:

• Added support for using T-Beam devices using the RNodeInterface
• Improved AutoInterface on Android
• Improved platform handling
• Improved malformed packet handling

RNS β 0.3.0

This is a major release of Reticulum, including a range of stability and performance improvements, along with important new features, expanding the connectivity of Reticulum.

An important improvement in this release is the addition of the AutoInterface, that will now be configured as the default interface on new installs. This interface automatically meshes with other Reticulum peers over any available system network devices, and doesn't require any existing IP infrastructure like a DHCP server or a router. For more information, consult the relevant section of the manual.

Improvements

• Added new AutoInterface as default interface for new installs
• Serial port interfaces now automatically attempt to reconnect devices that are unplugged and replugged
• Added support for KISS over TCP in the TCPClientInterface
• Added support for running Reticulum as a systemd service
• Initial support for the Android operating system
• Added documentation for installing Reticulum on Android in Termux
• Improved documentation and manual
• Better path request handling for shared instances
• Better shutdown handling on external interrupts
• Many small stability and reliability improvements
• Fine-tuned various timing parameters for different link types

RNS β 0.2.9

This beta release adds the fundamentals of RSSI and SNR functionality. It also implements timing improvements, allowing Reticulum to function on even lower bitrate physical links.

Improvements

• Added RSSI and SNR reporting on supported interfaces
• Added RSSI and SNR to rnprobe utility
• Added RSSI and SNR to Echo example
• Support for physical layer throughput down to 500 bits per second.
• Improved callback handling

RNS β 0.2.8

This beta release brings a single, but important improvement. Paths are now updated much more fluidly for peers moving around the network.

Since updates were made to how tunnels and path table entries are represented in this release, it is recommended to delete the following files on Transport Nodes:

~/.reticulum/storage/destination_table
~/.reticulum/storage/packet_hashlist
~/.reticulum/storage/tunnels
~/.reticulum/storage/cache/*

The files will be recreated when Reticulum is started.

Improvements

• Improved path updates for peers moving around the network

RNS β 0.2.7

This beta release brings a range of stability improvements and one bugfix.

Improvements

• Improved output of the rnstatus utility
• Improved shared instance and local client handling
• Improved documentation
• Improved path restoration on tunnels
• Added log rotation

Fixed bugs

• Fixed incorrect interface detachment on TCP client interfaces

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.