Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit c4701c26693645482111dcf78173962d2db2650f Author: Martin Hundebøll martin@hundeboll.net Date: Fri Dec 2 16:54:06 2011 +0000

doc: batman-adv/Using-batctl

c4701c26693645482111dcf78173962d2db2650f batman-adv/Using-batctl.textile | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index 7a4a8ce5..6060ea22 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -13,7 +13,12 @@ A quick overview of the config options available with batctl:

h2. Using batctl for debugging

-batctl offers a great deal of tools for monitoring the state of your mesh node/network. For many of the features to be available, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: +batctl offers a great deal of tools for monitoring the state of your mesh node/network: +* Ping and traceroute nodes based on their MAC-addresses. +* Parse logfiles to discover routing loops. +* Retrieve live information from the batman-adv module. + +To retrieve information, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: <pre> mount -t debugfs none /sys/kernel/debug </pre> @@ -22,4 +27,4 @@ With debugfs mounted, you can use batctl to, among other, seeing the following: * A list of other mesh nodes in the network (originators). * Lists of none-mesh nodes connected to the network (clients or neighbors). * A list of available gateways in the network. -* Log messages from the batman-adv module (if debug \ No newline at end of file +* Log messages from the batman-adv module (if debug is compiled into the module). \ No newline at end of file