Flood routing tweak for private channels

[peter9421]

Imagine a private primary channel with a crew of 3 (Alice, Bob and Charlie) .. away on a camping trip using default long fast in CLIENT role.

There are distant foreign nodes around on the public mesh. Alice and Charlie can't reach each other directly yet Bob can talk to both Alice and Charlie.

Charlie sends a message, Bob hears a distant foreign node repeating it. Alice can't hear the message from the foreign nodes. Bob doesn't rebroadcast because a foreign node on the mesh already has. Alice doesn't receive Charlie's message.

Currently if everyone uses broadcast mode KNOWN_ONLY foreign broadcasts from foreign nodes not in the crews nodelist are ignored for rebroadcast and so when Bob hears Charlie's message he ignores the foreign nodes broadcast for the purpose of rebroadcasting and rebroadcasts it himself allowing Alice to receive it.

The downside of this arrangement KNOWN_ONLY also prevents Alice, Bob and Charlie from participating in the larger mesh.

Asking to consider a new setting that would tweak flood routing so that a node on the private channel can use broadcast mode of ALL. When receiving broadcasts from outside of the crews nodelist to the private channel or destination node prevent receipt of foreign broadcasts from inhibiting flood routing rebroadcast amongst the crew.

[peter9421]

Checking more of the firmware code I didn't realize rebroadcast means rebroadcast as in the entire packet (inc source node). You can filter based on what you can decrypt or original sender yet there is no information in the message to discern which node is actually doing the repeating.

The only way left I can see to pull this off is a setting to bias CW such that members of private group/nodelist flood private group messages before the external mesh.

My main interest is chatting in small groups where there is no cell coverage and not getting blindsided by impacts of foreign nodes. Originally started with a t-echo up high in the rafters and a t1000e sitting on a desk. The two can communicate with each other perfectly being some 50 meters apart. Yet when I sent messages from a few miles away only the t-echo reliably received anything. The general expectation is you have your nodes and they will bounce signals off of each other. The intention of the setting is to prevent chance of whatever node that is out there with the poorest signal from overriding the expectations of users.