ACK is expensive.


  • I test my Ranger all of the time for specific nodes, and get "Message delivered to Unknown Broadcast."  Or some such...  It would be nice to get an indication that the message was NOT delivered, like request just an ACK from a Node to Node comm upon request.  I've attempted 'traceroute' to see the hops to those 8 mile nodes and nothing comes back. For me, traceroute only works on my channel, because I set my encrypted channel to the primary channel.  I have my home node as an S&F so that messages can be sent when passersby want their message dump.  (It is strange that S&F does stores Broadcast messages.) Maybe add a special tag to enroll in the S&F for your particular messages,.  So when an enrolled node enters the S&F Mesh, it can pick up its (encrypted) messages.  Set a bit in the message header, indicating you want broadcast traffic.  If one is a consistent commuter in an area, it would become more of a sparse network mesh node.  Then, that "carrier pigeon" node could carry a few messages on its particular, merry way.  Maybe an S&F node can be logged by passing nodes so that its general location could generate an automatic ping into its mesh.

    So, ACK could be expensive unless the ACK is requested, not generated.



Please login to reply this topic!