Incorrect acting as client with transport enbled on its host

[AMajor-C]

Describe the Bug
on all nodes(except D) flashed last firmware 1.86.4
Tested it on 3 nodes:
node A - LoRa only standalone TNC router(works correct)
node B - client node connected via USB to MeshchatX which have also connection to a internet backbone and enabled transport
node C - LoRa only client node connected via BT to Sideband on Android and also enabled transport
node D - client node using original RNode_firmware with host MeshchatX

There are problems:
From node C we cannot reach any peers behind the backbone.
Node C doesnt receives announces from node D

Expected Behavior
We should have same behavior as original RNode_firmware. If using original RNode_firmware instead there are no issue.

[wnhre2ur8cxx8]

Not a developer here, but most probably you need to include more details. For example interface modes. You could also rebuild your network with this tool here to check if things work the same in pure rnsd, and even share your exact setup so its easier to know what you talk about: https://github.com/RFnexus/reticulated

[AMajor-C]

Not a developer here, but most probably you need to include more details. For example interface modes. You could also rebuild your network with this tool here to check if things work the same in pure rnsd, and even share your exact setup so its easier to know what you talk about: https://github.com/RFnexus/reticulated

Interface modes are by Default.
In fact if replace firmware to original RNode (except TNC router) then no issues