Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

announcements are not sent when rnsd is running #752

Open
acatabc opened this issue Mar 11, 2025 · 3 comments
Open

announcements are not sent when rnsd is running #752

acatabc opened this issue Mar 11, 2025 · 3 comments

Comments

@acatabc
Copy link

acatabc commented Mar 11, 2025

The rnid CLI tool does not send an announcement on the link if rnsd is running with reticulum version 0.9.2.
In version 0.9.1 this issue does not occur.

Steps to reproduce:
reticulum config:

[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 1:
Open wireshark (or packet capture program of your choice) on the configured interface.

Step 2:
Generate Identity:

rnid -g id

Step 3:
Start rnsd with the configuration above.

rnsd

Step 4:
In another shell, send an announcement

rnid -i id -a test.test

Expected behavior:
In reticulum version 0.9.1 you will see the respective UDP announcement packet in the packet capture.

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

Expected behavior:
In reticulum version 0.9.1 you will see the respective UDP announcement packet in the packet capture.

System Information

  • Debian 12
  • python 3.11.2
  • Reticulum version 0.9.2

Additional context
If rnsd is not running the announcement can be observed on the link.

@markqvist
Copy link
Owner

Thank you for the detailed report! I will look into it.

@mkirc
Copy link

mkirc commented Mar 12, 2025

To chime in on this issue: @acatabc and me found the described behavior yesterday while performing some networking tests. For that we used local virtual networks with namespaces (and also did some fuzzing-around with Contiainernet ). The virtual network setup could possibly act as a starting point for a regression test harness. Would you be interested in the code?

@markqvist
Copy link
Owner

Yes, absolutely, that would be very helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants