Post date: Jul 4, 2011 1:59:01 PM
blocknode command
In build25, the meshAPs will test links to other nodes to see if there are stable links. If there are too many errors, then the link will be blocked and the meshAP will try and route via other nodes in the mesh.
Blocked nodes can be seen in /proc/aodv/blocked.
Nodes can also be blocked manually by issuing the command
blocknode 1.x.x.x
or unblocked using
unblock 1.x.x.x
The unblock retest wiana parameter determines how often nodes will retest the links.
Occasionally, solid links between nodes may become blocked for a variety of reasons. To force nodes to retest the links, you can issue the command
broadunblock
which will initiate a link test to all nodes that it can hear.
doubleunblock 1.x.x.x
will initiate a link test to the specific node and instruct that node to do the same back to the node from which this command was typed.
December 12, 2004 -
There is a new node blocking facility which is generally intended for experienced users and is only likely to be useful in very specific situations. In general the automated signal testing and minsig parameter should be all the tools required to block out interconnections between nodes which have poor signals etc.
If you have a situation where you have a node showing as a neighbor to another node and you don't want that to ever happen, but the automated signal testing does not block this other node then you can use permanent blocking. A situation I can imagine for this would be for example when joining networks with "Mesh Any Essid" but where you only want cross mesh linking in very specific places etc.
To utilize permanent blocking, there is a section in the "Firewalling Menu" where you can list the 1.x.x.x addresses of nodes you wish to block from the node in question. These can be delimited with a new line, space or comma. This feature will be supported in the next dev release but you can apply a patch which adds this support to any recent build25 release using the following:
getandverify permablockupdate
Use this blocking facility with care and consideration as to what effect any blockings you make will have. These permanent blockings cannot be undone with broadunblock or unblocknode. They can only be removed by deleting the entries from the firewalling menu and making changes to the node.
I've done troubleshooting for a few networks recently where signal testing had been disabled (it is enabled by default). I strongly advise keeping the automated signal testing enabled as it will greatly improve network performance anywhere there are marginal signals.