Announcements Are Not Sent When Rnsd Is Running

by ADMIN 48 views

Introduction

In this article, we will discuss an issue that arises when using the rnid CLI tool in conjunction with the rnsd service in Reticulum version 0.9.2. Specifically, we will explore the problem of announcements not being sent when rnsd is running. We will delve into the steps to reproduce this issue, the expected and observed behavior, and provide additional context to help resolve this problem.

Understanding the Issue

The rnid CLI tool is designed to send announcements on a link when a specific identity is generated. However, when rnsd is running with Reticulum version 0.9.2, the announcement is not sent. This issue does not occur in version 0.9.1, indicating that it is a regression in the newer version.

Steps to Reproduce

To reproduce this issue, follow these steps:

Step 1: Configure Reticulum

First, configure Reticulum with the following settings:

[reticulum]
enable_transport = False
panic_on_interface_error = No

[logging]
loglevel = 4

[interfaces]
[[UDP Interface]]
type = UDPInterface
interface_enabled = True
device = <Your Interface>
port = 4242

Step 2: Open Wireshark

Open Wireshark (or your preferred packet capture program) on the configured interface.

Step 3: Generate Identity

Generate an identity using the rnid CLI tool:

rnid -g id

Step 4: Start RNSD

Start the rnsd service with the configured settings:

rnsd

Step 5: Send Announcement

In another shell, send an announcement using the rnid CLI tool:

rnid -i id -a test.test

Expected Behavior

In Reticulum version 0.9.1, you should see the respective UDP announcement packet in the packet capture.

Observed Behavior

However, in version 0.9.2, you will observe that there is no UDP packet sent out over the link in the packet capture.

System Information

The following system information is relevant to this issue:

  • Debian 12
  • Python 3.11.2
  • Reticulum version 0.9.2

Additional Context

It is worth noting that if rnsd is not running, the announcement can be observed on the link. This suggests that the issue is specific to the interaction between rnid and rnsd in Reticulum version 0.9.2.

Conclusion

Introduction

In our previous article, we discussed an issue that arises when using the rnid CLI tool in conjunction with the rnsd service in Reticulum version 0.9.2. Specifically, we explored the problem of announcements not being sent when rnsd is running. In this article, we will provide a Q&A section to help answer some of the most frequently asked questions related to this issue.

Q: What is the cause of this issue?

A: The cause of this issue is a regression in Reticulum version 0.9.2. Specifically, the interaction between rnid and rnsd is not functioning correctly, resulting in announcements not being sent.

Q: Is this issue specific to Reticulum version 0.9.2?

A: Yes, this issue is specific to Reticulum version 0.9.2. In version 0.9.1, the issue does not occur, indicating that it is a regression in the newer version.

Q: What are the steps to reproduce this issue?

A: To reproduce this issue, follow these steps:

  1. Configure Reticulum with the following settings:
[reticulum]
enable_transport = False
panic_on_interface_error = No

[logging]
loglevel = 4

[interfaces]
[[UDP Interface]]
type = UDPInterface
interface_enabled = True
device = <Your Interface>
port = 4242
  1. Open Wireshark (or your preferred packet capture program) on the configured interface.
  2. Generate an identity using the rnid CLI tool:
rnid -g id
  1. Start the rnsd service with the configured settings:
rnsd
  1. In another shell, send an announcement using the rnid CLI tool:
rnid -i id -a test.test

Q: What is the expected behavior?

A: In Reticulum version 0.9.1, you should see the respective UDP announcement packet in the packet capture.

Q: What is the observed behavior?

A: In version 0.9.2, you will observe that there is no UDP packet sent out over the link in the packet capture.

Q: What system information is relevant to this issue?

A: The following system information is relevant to this issue:

  • Debian 12
  • Python 3.11.2
  • Reticulum version 0.9.2

Q: Is there any additional context that is relevant to this issue?

A: Yes, it is worth noting that if rnsd is not running, the announcement can be observed on the link. This suggests that the issue is specific to the interaction between rnid and rnsd in Reticulum version 0.9.2.

Q: How can I resolve this issue?

A: To resolve this issue, you can try the following:

  1. Upgrade to Reticulum version 0.9.1, which does not exhibit this issue.
  2. Modify the rnsd configuration to disable the interaction with rnid.
  3. Contact the Reticulum development team for further assistance.

Conclusion

In conclusion, the Q&A section above provides additional information and answers to frequently asked questions related to the issue of announcements not being sent when rnsd is running in Reticulum version 0.9.2. We hope that this information will be helpful in resolving this problem and ensuring that announcements are sent correctly in Reticulum.