Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodes outside range of gateway but within range of another node #53

Open
leahcornelius opened this issue Jul 11, 2024 · 0 comments
Open

Comments

@leahcornelius
Copy link

I am wondering if EnigmalOT supports something in the following situation:

  • Node A and B are within range of and connected to the gateway
  • Node C is OUT of the range of the gateway and node B
  • Node C is IN of the range of node A

Now in this situation can Node C:

  • Connect to node A
  • Use the connection to node A to connect to the network/gateway (by node A relaying messages from node C)
  • Send a message to Node B (using the same function node A could use to send a msg to node B), this would mean node A automatically routing the message to node B (or to gateway which then routes to node B if your implementation doesn't use P2P)

Essentially i am asking if nodes outside the range of the root node/gateway can join the network through another node(s) which ARE connected to the root node/gateway and use the functions like a node within range of the gateway. Or would i have to implement this myself (EG a layer on top of your layer of ESP now - sounds inefficient to me).

I know this has been done with ESP-MESH (aka ESP-NOW) but cant find a "easy" to use wrapper/library and i really like the other features this library offers so hoping this is the case (as i need this for my application).

Sorry if this is confusingly worded or already addressed but saw no mention of it in the docs, technical spec or current/closed issues so wanted to ask. Many thanks, Leah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant