meshtastic
[Bug]: After reordering Channels, messages "leak" into the wrong channels
Contact Details
What happened?
I moved an encrypted channel to be primary, and messages from the default LongFast started showing up in that channel.
App Version
2.5.16
Phone
Pixel 7 pro
Device
heltec v3
Firmware
2.6.4
Relevant log output
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Also seen in 2.6.19 on Android and Metadata: { "firmwareVersion": "2.6.4.b89355f", "deviceStateVersion": 24, "canShutdown": true, "hasBluetooth": true, "hasEthernet": true, "positionFlags": 2, "hwModel": "RAK4631", "hasPKC": true, "excludedModules": 4480, "hasWifi": false, "role": "CLIENT", "hasRemoteHardware": false }
In my experience it doesn't look like they leak into other channels, messages just aren't received on non reordered nodes
I did the same re-ordering on 3 nodes, and after leaving them on overnight, all three nodes only see each other as online. Normally, I get up to 30 nodes or more showing up online in this area. So it looks to me as though communication with other nodes has been broken by the re-ordering.
When I send messages to the public "LongFast" channel, only my 3 re-ordered nodes receive the message. Other nodes that I have not re-ordered don't receive the message on any channel.
This makes it impossible to do things like only share precise locations with a private network and still be able to talk on the public channel.
Ok, i didn't do step 4 here and change the slot back to the default for my region after re-ordering channels. It looks like if you do this, the messages are sent to the default public channel. Kinda sneaky to change a lora radio setting in a totally different part of the interface when you rename the primary channel without some sort of warning or pop-up.
