rns.recipes

@gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it.

@gdane Thanks for the work you're doing on this. Any plans for microReticulum nodes to support discoverble=yes so that they appear on maps?

I'd love to see the public RNS LoRa network grow over time. But its hard to show growth due to standalone LoRa nodes being invisible.

Anonymous wrote:

One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces?

That's a case I haven't tested, but it should behave the same as Python RNS. If you want to DM me some logs I'll take a look.

daylight-hub wrote:

So, the last microReticulum firmware for the Heltec V4 that I was able to flash using Liam Cottle's RNode flasher was 1.86.1. When I try to flash 1.86.2 or 1.86.3 using the flasher it shows up as missing config.

That is odd that you could flash 1.86.1 but not 1.86.3. The amount of spurious out-of-frame logging is much less on rev 3 than on rev 1 so it should be less likely to hose the initial provisioning.
I know there's a bit more work I need to do silence all of the spurious logs or move them into KISS framing. I'll make this a point before I release rev 4 and hopefully that will resolve the install issue.
BTW, did you try manually provisioning after install with rnodeconf, and if so any trouble with that?

Anonymous wrote:

@gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it.

Three things to know here:

First, the nomadnet page is currently only informational and was intended as more of a placeholder for a legitimate provisioning and monitoring interface. So I don't really plan on extending it. Ultimately I plan to make it just a general page server that will server user-configured content instead of transport node stats.

Second, there is an existing legitimate provisioning and monitoring interface in the form of a web app. It's available in 1.86.3 but you have to either download it from the repo or run from the public url I have made available RNode Console. This (very experimental) interface exposes both rnodeconf-type config and microReticulum transport node config and metrics, as well as logging.

Lastly, the console web app does not yet support configuration over RNS, but it's coming. It's actually in the final phases of testing and refining now. It will also be a feature in 1.86.4 so stay tuned!

x2tyfi wrote:

@gdane Thanks for the work you're doing on this. Any plans for microReticulum nodes to support discoverble=yes so that they appear on maps?

I'd love to see the public RNS LoRa network grow over time. But its hard to show growth due to standalone LoRa nodes being invisible.

It's not on my radar, but it's a good idea. I'll look into the lift required. Likely won't be in the next release but possibly in the following one.

gdane wrote:

Anonymous wrote:
> One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces?

That's a case I haven't tested, but it should behave the same as Python RNS. If you want to DM me some logs I'll take a look.

Ok, I will. I am a bit unsure when the site is supposed to announce, but I expected at least at bootup?

gdane wrote:

Anonymous wrote:
> @gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it.

Three things to know here:

First, the nomadnet page is currently only informational and was intended as more of a placeholder for a legitimate provisioning and monitoring interface. So I don't really plan on extending it. Ultimately I plan to make it just a general page server that will server user-configured content instead of transport node stats.

Second, there is an existing legitimate provisioning and monitoring interface in the form of a web app. It's available in 1.86.3 but you have to either download it from the repo or run from the public url I have made available RNode Console. This (very experimental) interface exposes both rnodeconf-type config and microReticulum transport node config and metrics, as well as logging.

Lastly, the console web app does not yet support configuration over RNS, but it's coming. It's actually in the final phases of testing and refining now. It will also be a feature in 1.86.4 so stay tuned!

Amazing, thank you! I discovered the console. Thats why I was wondering what the "remote management" checkbox was actually doing, and what the identities I could enter for it were for. The nomadnet site needed it set for me to get a look at the mettics, thats why I thought its maybe connected. Management over reticulum would be so nice, happy to wait for it, thank you!