[Feature Request]: Change router behaviour

[kallisti5]

Platform

Cross-Platform

Description

So, I have a node in one of those "ideal locations" (height is pretty close to highest point for 30+ miles, tips of mountains are competing.) The area doesn't have cell coverage, but I do have Starlink to forward local chatter to MQTT.

As a user, with the removal of router_client, I lost the following key features I used a lot:

• MQTT Forwarding of local chatter where internet connectivity is weak
• Administration of a node not easily accessible via bluetooth
• My router showing up on maps like meshmap (no MQTT)

Proposal:

• Allow bluetooth management of nodes in a router role (optional.. I know of the "admin network", just don't know how to use it)
• Allow receiving and forwarding messages (and telematics) to MQTT via ethernet / wifi.
• Block sending local messages from router nodes.

If I understand the reasons for router_client getting removed, wouldn't the proposal above address the concerns most folks have in threads like #4185 (people running router_client, and getting rapid network priority over client nodes), while enabling use of critical features important to people with "nodes in ideal locations"