Started by wbknl ·
Hi,
New to Reticulum, I would like to know how can I, in MeshChat, make available a bridge from my WiFi LAN (Default Interface) to the configured TCP clients. The goal is to use a smartphone only connected to the WiFi LAN and be able to reach users outside the LAN.
Thanks
wbknl
you need a transport node connected to both interfaces for a device on the LAN to reach other devices which are connected to said TCP clients and vice-versa
anon wrote:
you need a transport node connected to both interfaces for a device on the LAN to reach other devices which are connected to said TCP clients and vice-versa
how can I configure that? Is there any tutorial? Thanks for your reply and kindness.
wbknl wrote:
anon wrote:
you need a transport node connected to both interfaces for a device on the LAN to reach other devices which are connected to said TCP clients and vice-versa
how can I configure that? Is there any tutorial? Thanks for your reply and kindness.
Basically you need another device thats connected to both, so you would either need your meshchat node to be a transport node connected to both, or another device to do that, it’s pretty easy to do in the interfaces and settings areas of meshchat
Yeah, if you want to do TCPServer <-> Internet <-> Meshchat <-> local Wifi <-> RNS on Smartphone
go to Settings -> Network -> Transport Mode -> Enable Transport Mode in MeshchatX. Than restart MeshchatX and it should work.
On the machine that has both the internal wifi interface (AutoInterface) and connections to nodes on the internet (BackboneInterface or TCPClientInterface), just enable transport, and you're good to go, the smartphone can now reach anything the transport node can reach.
However, to improve your configuration, you should at least set AutoInterface on the transport node to gateway or internal mode, so clients on your internal WiFi can recursively resolve paths (makes getting paths much faster).
Another option is (if you don't want to see the constant stream of incoming announces from the wide world on your internal network) to set the interfaces that connect to the wide world to boundary mode. If you do that, your internal clients will still be able to resolve paths and connect to anything else, but you will only get announces for the destinations they ask for.
Thanks for all your help. I've made it work.
Thanks for all your help. I've made it work.
