Specifications

Discovered mesh routes timeout after a configurable period of inactivity (see #23), but this timeout
sets an upper limit on how long a route will be used, even if it is being used heavily. By forcing routes
to be rediscovered periodically, the nodes will use the shortest routes possible.
Note that you can set this timeout to zero (which will disable it) if you know for certain that your
nodes are stationary, or have some other reason for needing to avoid periodic route re-discovery.
You can use getInfo(14) to determine the size of a node’s route table, and getInfo(15) to monitor its
use.
ID 21 – Mesh Routing Minimum Timeout
This is the minimum time (in milliseconds) a route will be kept. This defaults to 1000, or one second.
ID 22 – Mesh Routing New Timeout
This is the grace period (in milliseconds) that a newly discovered route will be kept, even if it is never
actually used. This defaults to 5000, or five seconds.
ID 23 – Mesh Routing Used Timeout
This is how many additional milliseconds of “life” a route gets whenever it is used. This defaults to
5000, or five seconds.
Every time a known route gets used, its timeout gets reset to this parameter. This prevents active
routes from timing out as often, but allows inactive routes to go away sooner. See also Parameter #20,
which takes precedence over this timeout.
ID 24 – Mesh Routing Delete Timeout
This timeout (in milliseconds) controls how long “expired” routes are kept around for bookkeeping
purposes. This defaults to 10000, or 10 seconds.
ID 25 – Mesh Routing RREQ Retries
This parameter controls the total number of retries that will be made when attempting to “discover” a
route (a multi-hop path) over the mesh. This defaults to 3.
ID 26 – Mesh Routing RREQ Wait Time
This parameter (in milliseconds) controls how long a node will wait for a response to a Route Request
(RREQ) before trying again. This defaults to 500, or a half second.
Not that subsequent retries use longer and longer timeouts (the timeout is doubled each time). This
allows nodes from further and further away time to respond to the RREQ packet.
ID 27 – Mesh Routing Initial Hop Limit
This parameter controls how far the initial “discovery broadcast” message is propagated across the
mesh.
SNAP Reference Manual Document Number 600-0007K Page 99 of 202