search

nRF24 / RF24Mesh

OSI Layer 7 Mesh Networking for RF24Network & nrf24L01+ & nrf52x devices
http://nrf24.github.io/RF24Mesh
GNU General Public License v2.0
422 stars 153 forks source link

Second RF24Mesh in the vicinity / rogue detection #115

Closed rumbero71 closed 5 years ago

rumbero71 commented 7 years ago

Hi, coming from a WIFI-perspective, I was wondering what happens if e.g. a neighbour was to set up his own Mesh. From what I understand is that there is no such thing as a Mesh ID so I would assume that the two meshes end up interfering with one another and -although perhaps not understanding the others' data format- crippling its operation. Is that correct or did I miss something ? If correct, how can this situation be mitigated, resp. how would something like a rogue detection work ? Anyways...great work ! Regards Markus

Avamander commented 7 years ago

Yes, meshes on the same channels end up interfering with each other. How to detect? Well, if you could make master listen for packets that only a master node is supposed to send that would be one way. Though it would require modifications to the library itself.

rumbero71 commented 7 years ago

Ok then. So how do I limit my mesh to a dedicated channel. I tried radio.setChannel before or after mesh.begin on both Master and Slave Node besides running my "productive" mesh without those limits (is there a default channel ?) and -strangely enough- "productive" master has the NodeID of the "limited" slave, but not seeing packets, whilst the "limited" master does see the packets without having the "limited" slave's NodeID. Where is my error in thinking ?

TMRh20 commented 5 years ago

Call mesh.begin(channelNumber);