Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 21cb3904bd0facee3d7e69f0e305d465722c3b48 Author: Martin Hundebøll martin@hundeboll.net Date: Fri Dec 2 17:23:15 2011 +0000
doc: batman-adv/Using-batctl
21cb3904bd0facee3d7e69f0e305d465722c3b48 batman-adv/Using-batctl.textile | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index e5e12136..dcc86707 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -18,12 +18,9 @@ batctl offers a great deal of tools for monitoring the state of your mesh node/n * 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> +To retrieve information, you must compile your kernel with debugfs (it usually is by default)
-With debugfs mounted, you can use batctl to, among others, seeing the following: +With debugfs compiled in, you can use batctl to, among others, 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.