rns.recipes

Anyone has a clear documentation or tutorial on how to configure microreticulum as a transport node for remote administration? i got very confused by the "provisioning" parts of the documentation, and my experience so far has been frustrating: serial links and browsers not detecting the device... double-reset supposed to spawn a wifi AP that i never detected, etc. is there a reliable way through command line, and standard reticulum tools to probe the device? So far all i achieved is to set as --tnc and let it run autonomously, but i am sure there is more than that... feedback, personal experience and useful docs all very welcome! thanks!

I haven't even found clear documentation on how to configure the reference Python rnsd as a transport node for remote administration.

ARF wrote:

I haven't even found clear documentation on how to configure the reference Python rnsd as a transport node for remote administration.

# It is possible to allow remote management of Reticulum
# systems using the various built-in utilities, such as
# rnstatus and rnpath. You will need to specify one or
# more Reticulum Identity hashes for authenticating the
# queries from client programs. For this purpose, you can
# use existing identity files, or generate new ones with
# the rnid utility.

# enable_remote_management = yes
# remote_management_allowed = 9fb6d773498fb3feda407ed8ef2c3229, 2d882c5586e548d79b5af27bca1776dc

It can be confusing, I've found the console in the source files (webconsole/index.html) to work, but if the version isn't exactly the same it doesn't show all the tabs (eg the 'Transport Config' tab doesn't appear). I'm able to connect to my MicroReticulum node via serial with this tool, and also via RNS when ReticulumAPI is running. There's also a Nomadnet page the MicroReticulum node hosts you can browse to which allows you to see basic information about it, but you need to add your identity beforehand to use it. I've not used any CLI tools to manage my node.

thanks! that's things i tried and failed (once i manage to establish communication, but never saw the "transport config" tab... now i cannot even connect to the device...) so it's in transport config that -when you get there- you input an identity and then you can use a nomadnet page! thanks. i'll try again (and again)

"Failed to fetch device info: privisioning request timeout" is the sort of messages i see after hitting "connect" in the webconsole/index.html file...

Try building from source and flashing that. Send me a message on LXMF if you get stuck and we can go through it. lxma://532a4e8665af3b037406c15d580c7390:8bb8eb9a950507ef459ed7d631e65aa1761d550c2223d701edf1d51b319f8f6801bd8394caa52e21adaa160536c402544636b49fe6a46e0d8271219a7ab6dad1

Thank you so much for your help! wow this is arcane indeed! i compiled it and it worked... i wish these things were documented and more accessible... now i added a bunch of identities for admin and still those pages cant seem to load... i guess i need much more tinkering and experimenting still...

Anonymous wrote:

It is possible to allow remote management

Sure, the default config comments have a hint that it's possible, but where are there any documentation or examples about how to actually do it?

jmeshy wrote:

i wish these things were documented and more accessible.

If you have the time, could you make a wiki page about how you got it to work for others to learn from?

If you ever get it to run via rns with his api thing, it would be amazing if you made a short thread here on how you set it up.

We are running microReticulum Firmware via ReticulumAPI remote administration via Reticulum itself via LoRa successfully here in Innsbruck, can write up some stuff soon.

Dayle M0OUE wrote:

It can be confusing, I've found the console in the source files (webconsole/index.html) to work, but if the version isn't exactly the same it doesn't show all the tabs (eg the 'Transport Config' tab doesn't appear). I'm able to connect to my MicroReticulum node via serial with this tool, and also via RNS when ReticulumAPI is running. There's also a Nomadnet page the MicroReticulum node hosts you can browse to which allows you to see basic information about it, but you need to add your identity beforehand to use it. I've not used any CLI tools to manage my node.

I think the problem with the transport-config tab lies with the webconsole/index.html file. I tried it first and had the same result. I think you are supposed to use the console.html from the release assets. At least thats what worked for me.