Serial interface woes

[deavmi]

I have all the right permissions and have tested, using picocom, communication between the two devices and it works (I have a null-modem).

I have added the interface as per https://reticulum.network/manual/interfaces.html#serial-interface however when I start rnsd it says the serial interface is brought up yet i never see any traffic between my two rnsd daemons. Maybe I am doing something wrong, I just assumed placing both on the same link with interface configuration on either side would show something in the log, even when set to loglevel 7.

---

I am not doing anything yet between the nodes. I presume this may be the issue? Like I may need to generate some announcement that gets placed in an LXMF message and then routed as a reticulum packet through to the other node. I feel as though this may very well be the case. What is a good way to test then, perhaps?

[markqvist]

Reticulum is by default very quiet on configured physical links and interface, and will not send anything unless it absolutely needs to.

To see any traffic, the minimum thing you can do is send an announce from something. That should propagate out over any configured interface, and you should see it in the log of other device. You can use any existing application, or just fire up the Announce.py example and hit enter to send a couple of example announces.

[deavmi]

Perfect, going to give this a try.

[deavmi]

Will report back when done

[deavmi]

I did a few of these:

Yet on the other node I don't see much:

[deavmi]

I take that back, I see logs after restart (sen, my docker CLI is retarded):

[deavmi]

This is quite epic then. Thanks so far for the help!

I will come back to this soon, marked as good tho!

[deavmi]

Machine generating announces:

Machine receiving it (over serial):

[markqvist]

Very nice! Looks like it's all working then!

[deavmi]

Indeed, you don't know how happy I am about this 😆

[deavmi]

Also I know what was causing the lag, I think docker buffers stdout (because it saves logs to its own data store) and it only flushes to that data store after a large amount buffered. Hence why i would only "see announces" when I sent enough, when infact they were all there. Epic

[markqvist]

Ah, of course, I've run into that before with docker. As far as I remember, there is an option to flush at much lower intervals or immediately, but can't remember what is is :P