rns.recipes

Hi everyone, I've activated rnprobe responder in RTnode config page but with the given node hash I only get timeouts when I send a rnprobe request from a connected device using meshchatx or nprobe rntransport.probe <hash>. any hints on debugging this? thanks in advance

the RTnode config page offers a "probe destination" (10 byte) which can't be used the the nprobe command as it only accecpts 16 byte hashes as destination. So I'm confused how to actually use the probe destination hash when it's only 10 byte.

Is the RNode configured as Transport Node?

yes, thats my intention. I'm using https://github.com/jrl290/RTNode-HeltecV4, not the original Rnode

i have the same issue with the incomplete hash.
didn't figire it out yet, and abandoned the idea of using rnprobe due to this.

i managed to validate that it works by counting hops for connections. however sometimes it seems to not route at all.
rnprobe would be very helpful if it'll work.

i'm also thinking to switch to microreticulum due to this, maybe that one is more reliable as a transport node

rn_hedonist wrote:

the RTnode config page offers a "probe destination" (10 byte) which can't be used the the nprobe command as it only accecpts 16 byte hashes as destination. So I'm confused how to actually use the probe destination hash when it's only 10 byte.

You have to have a full node within a few hops, to be able to get the full hash displayed in rnpath, then use the 10 char has as a key to the whole hash. The use rnprobe rnstransport.probe <hash>

thanks for writing. why is it necessary to resolve the 10byte hash? \n why can't i use the full hash of the node which is shown on the config page?

rn_hedonist wrote:

thanks for writing. why is it necessary to resolve the 10byte hash? \n why can't i use the full hash of the node which is shown on the config page?

Sorry I missed your response. The config page only displays the first 20 char of the 32 char hash string. So you need to match that against an available list of announced hashes to find the last 12 chars. The rnpath -t command, run on a node that is within 2 hops should have path entry for the probe destination hash, so you can get the full hash from there.