User's Guide
Although all BreadCrumbs can be access points, most access points do not provide mesh capability.
Traditional access points simply allow wireless devices within range to connect to a wired network;
they do not extend range through other access points.
1.2 The Mesh Network
The key component of a BreadCrumb Mesh network is the ability for BreadCrumbs to connect, or mesh
with each other. While this is generally handled automatically by BreadCrumbs, complex deploymen
t
scenarios require a basic understanding of how BreadCrumbs establish and maintain a mesh.
1.2.1 Mesh – A Definition
A mesh is a collection of BreadCrumbs (or other network devices), each of which is linked to one o
r
more other BreadCrumbs. Data can move between BreadCrumbs via these links, possibly passin
g
through several intermediate BreadCrumbs before arriving at its final destination.
The intelligence of a BreadCrumb network is in how it adapts rapidly to the creation or destruction o
f
the links in the mesh as devices are moved, switched OFF or ON, blocked by obstructions, interfered
with by other devices, or otherwise affected. This adaptation takes place automatically and
immediately as needed.
1.2.2 BreadCrumb Mesh Connections
In order for two BreadCrumbs to establish a mesh link to each other, they must be set to the sam
e
radio channel and have the same Network ID. The Network ID is computed from:
z Network Name (simply a configurable name for the network, default is “Rajant Mesh
Network”)
z Network Key (a passphrase or key used for establishing mesh connections and obfuscatin
g
unencrypted network management traffic)
z Packet cipher setting
z MAC cipher setting
z Perhop verification setting
z Key Sequence Number (defaults to 0)
To modify these settings via BC|Commander, the administrator must be logged in using the Crypt
o
Officer credentials.