You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
The
rnid
CLI tool does not send an announcement on the link ifrnsd
is running with reticulum version 0.9.2.In version 0.9.1 this issue does not occur.
Steps to reproduce:
reticulum config:
Step 1:
Open wireshark (or packet capture program of your choice) on the configured interface.
Step 2:
Generate Identity:
Step 3:
Start rnsd with the configuration above.
Step 4:
In another shell, send an announcement
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
Additional context
If
rnsd
is not running the announcement can be observed on the link.The text was updated successfully, but these errors were encountered: