Replies: 2 comments 2 replies
-
|
I´ve added these proposals to #8820 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
That's still essentially just router (or router_late) mode then. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I`ve been losing messages on LongFast that won´t reach my indoor node, because my roof node won´t rebroadcast them for some reason.
As far as I understand, this changes apply only to DMs to and from a fav node. This makes the function of CLIENT_BASE only valid and useful for DMs.
I propose that in CLIENT_BASE ALL broadcast channel packets should be rebroadcasted at least ONE MORE TIME, so to ensure proper reach of LongFast messages and the like to the indoor nodes.
For packets that the algorithm decided should not be rebroadcasted, I propose to do so BUT after subtracting the remaining hops on the packet (making it 0) so it won´t congest the mesh but ensure reach to the indoor nodes.
Another solution could be, make the roof CLIENT_BASE node act as a S&F server for the indoor node, and make a mechanism to automatically pull missing broadcast messages from the roof node.
Hope this gets a workaround!
Thanks
Beta Was this translation helpful? Give feedback.
All reactions