Discussion
Since i had success with a direct #lora #rnode link before i wantet to step the #reticulum game up by one!
Laptop connected to Server via TCP, Mobile connected to Server via LoRa RNode.
Laptop - full - TCP - Gateway - Server - Infernal - LoRa - full - mobile
No success so far sadly 😐 gona let it sit for a while, maybe it fixes it self again. but still a bit annoying. (Server has one hop path to both via the correct medium tho)
@Hiajen have both nodes announced themselves so that they know each-other's latest route?
@temporary
yes, i did exchange mesaages before. and on laptop i also dropped the Route over the now non existant Route.
issue seemed that the Server quickly went over its airtime limit :/
@Hiajen @temporary yes it seems that if you don't set your LoRa interface (rnode) to "access point" mode (which seems to be the default now), in any other modes if there is a TCP server interface somewhere in the mix, lora will end up attempting to forward all the route requests and announces it sees, which is bound, with its limited bandwidth to excess the airtime... your own "legitimate" traffic may end up being stuck in an endless queue... it may eventually arrive though, that's an intersting experiment...
but fundamentally i think lora interface non-"access point" cannot work given the current size of the #reticulum mesh (including all of TCP nodes...)
Install bonfire.cafe
Get the full app experience
