[Feature Request]: More control of bridging between protocols - a sort of oktomqtt++ for UDP, BLE, rs485, rs232, IrDA, etc.

[NomDeTom]

As there are more methods to bridge nodes, an improved control over what and how interfaces are bridged is required.

At present, UDP bridging hasn't got the same level of control as MQTT, but it can often be serving the same purpose.

Other bridging methods have been proposed or have working PoC: RS485, serial, etc. Allowing control and filtering of these bridges would also be expected.

[wlockwood]

I'm not sure this makes as much sense. If my neighbor has a dual-radio node where they're bridged by UDP or RS485 or a tiny demon in a box, how am I supposed to make meaningful decisions based on that? MQTT is more like an escape to the Internet and less of a bridge. It's functionally a very different question to ask the user: "do you want to show up in reporting stuff?"

[NomDeTom]

There's meshes out there that have bridging across presets, and they're struggling with how to filter content across without either dropping some packets, or flooding the slower channels.

Other interfaces are more 1:1, such as the rs485 for the cave folk.

I'm hoping one of the meshes that has tackled this will chime in.

[github-actions[bot]]

This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.

[github-actions[bot]]

This issue has not had any comment since the last notice. It has been closed automatically. If this is incorrect, or the issue becomes relevant again, please request that it is reopened.