NodesMeshingInWiana

back to http://scratchpad.wikia.com/wiki/Sasecurity

{{{

Your mesh isn't really very close to the one it stumbled into - it hit mine which is 60 miles away over in neighboring Louisiana. My node on the TV tower is 1350 feet above ground, and has "mesh with any ESSID" turned ON, as I run 2 different ESSID's. I already spotted it and I alerted LocustWorld as I thought it was a rogue node. I also immediately blocked your network from mine. Since then, LocustWorld has advised me on what to do to prevent this from happening and I will implement the necessary changes over the next few days as I do some network upgrades to a "clustered" dual node system on that tower.

The amazing thing is that our meshes established a connection over 60 miles that was good enough to pass some traffic such as a Wiana checkin. Kyle Batts and I have sucessfully setup a connection at 21 miles or so, but this one just blew me away!

It's funny what we "pioneers" are stumbling into!

> A strange thing occured two days ago. I was extending my present > commercial > mesh when i accidently got too close to another adjacent commerical > mesh. > Although both my nodes that were suppose to mesh are on towers over > 155 feet > and on very high ground there was a hill between that apparently > blocked the > signal. So for some reason my node messed with the other commercial > mesh. > Apparantly by no design of my own there are 4 seperate commercial > meshes > using the same CHANNEL in this area. To my astonishment even though > the > NODE didnt mess with its proper mesh it DID communicate with the OTHER > commercial mesh(not surprising) and did so to the point that it > actually > checked into WIANA thru that mesh system even though it isnt > registered to > it. THIS IS SOMETHING I NEVER WANT TO HAPPEN AGAIN! Is there a > setting or > settings that can keep this from occuring other than changing > channels(i > have too much infrastructure to make that fesible at this point). My > appoligies to Kenny Bain and or Klye Batts or whoever owns FASTLINE > for > this unfortunate occurance and in no way was intentional. Any help > with this > matter would be appreciated. This particular node never acheived an > internet > uplink that could be accessed from the public and to my knowledge > passed no > traffic other than the wiana checkins.

Nodes are not tied to a wiana account and will mesh if they can see one another and have the same ESSID, also if somebody starts up a node on their own wiana account they can join your network without your permission but they will show up in the wiana map.

As long as you use different ESSID's the two mesh's will not mesh, if any part of your network shares a common ESSID and can they see one another, they will mesh. They will also mesh is you have "Mesh with any ESSID" set to yes in wiana (not good idea).

To stop the meshing and increase security you should have a look at "mesh routing IPsec" and "Privacy cipher" in the WiKi

none registered nodes using anothers bandwidth
> A strange thing occured two days ago. I was extending my present commercial > mesh when i accidently got too close to another adjacent commerical mesh. > Although both my nodes that were suppose to mesh are on towers over 155 feet > and on very high ground there was a hill between that apparently blocked the > signal. So for some reason my node messed with the other commercial mesh. > Apparantly by no design of my own there are 4 seperate commercial meshes > using the same CHANNEL in this area. To my astonishment even though the > NODE didnt mess with its proper mesh it DID communicate with the OTHER > commercial mesh(not surprising) and did so to the point that it actually > checked into WIANA thru that mesh system even though it isnt registered to > it. THIS IS SOMETHING I NEVER WANT TO HAPPEN AGAIN! Is there a setting > or > settings that can keep this from occuring other than changing channels(i > have too much infrastructure to make that fesible at this point). My > appoligies to Kenny Bain and or Klye Batts or whoever owns FASTLINE for > this unfortunate occurance and in no way was intentional. Any help with this > matter would be appreciated. This particular node never acheived an internet > uplink that could be accessed from the public and to my knowledge passed no > traffic other than the wiana checkins. }}}

* MeshRoutingIpsec * PrivacyCipher