1
 2What:           /sys/class/net/<mesh_iface>/mesh/aggregated_ogms
 3Date:           May 2010
 4Contact:        Marek Lindner <lindner_marek@yahoo.de>
 5Description:
 6                Indicates whether the batman protocol messages of the
 7                mesh <mesh_iface> shall be aggregated or not.
 8
 9What:           /sys/class/net/<mesh_iface>/mesh/bonding
10Date:           June 2010
11Contact:        Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
12Description:
13                Indicates whether the data traffic going through the
14                mesh will be sent using multiple interfaces at the
15                same time (if available).
16
17What:           /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
18Date:           November 2011
19Contact:        Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
20Description:
21                Indicates whether the bridge loop avoidance feature
22                is enabled. This feature detects and avoids loops
23                between the mesh and devices bridged with the soft
24                interface <mesh_iface>.
25
26What:           /sys/class/net/<mesh_iface>/mesh/fragmentation
27Date:           October 2010
28Contact:        Andreas Langer <an.langer@gmx.de>
29Description:
30                Indicates whether the data traffic going through the
31                mesh will be fragmented or silently discarded if the
32                packet size exceeds the outgoing interface MTU.
33
34What:		/sys/class/net/<mesh_iface>/mesh/ap_isolation
35Date:		May 2011
36Contact:	Antonio Quartulli <ordex@autistici.org>
37Description:
38		Indicates whether the data traffic going from a
39		wireless client to another wireless client will be
40		silently dropped.
41
42What:           /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
43Date:           October 2010
44Contact:        Marek Lindner <lindner_marek@yahoo.de>
45Description:
46                Defines the bandwidth which is propagated by this
47                node if gw_mode was set to 'server'.
48
49What:           /sys/class/net/<mesh_iface>/mesh/gw_mode
50Date:           October 2010
51Contact:        Marek Lindner <lindner_marek@yahoo.de>
52Description:
53                Defines the state of the gateway features. Can be
54                either 'off', 'client' or 'server'.
55
56What:           /sys/class/net/<mesh_iface>/mesh/gw_sel_class
57Date:           October 2010
58Contact:        Marek Lindner <lindner_marek@yahoo.de>
59Description:
60                Defines the selection criteria this node will use
61                to choose a gateway if gw_mode was set to 'client'.
62
63What:           /sys/class/net/<mesh_iface>/mesh/orig_interval
64Date:           May 2010
65Contact:        Marek Lindner <lindner_marek@yahoo.de>
66Description:
67                Defines the interval in milliseconds in which batman
68                sends its protocol messages.
69
70What:           /sys/class/net/<mesh_iface>/mesh/hop_penalty
71Date:           Oct 2010
72Contact:        Linus Lüssing <linus.luessing@web.de>
73Description:
74		Defines the penalty which will be applied to an
75		originator message's tq-field on every hop.
76
77What:		/sys/class/net/<mesh_iface>/mesh/routing_algo
78Date:		Dec 2011
79Contact:	Marek Lindner <lindner_marek@yahoo.de>
80Description:
81		Defines the routing procotol this mesh instance
82		uses to find the optimal paths through the mesh.
83
84What:           /sys/class/net/<mesh_iface>/mesh/vis_mode
85Date:           May 2010
86Contact:        Marek Lindner <lindner_marek@yahoo.de>
87Description:
88                Each batman node only maintains information about its
89                own local neighborhood, therefore generating graphs
90                showing the topology of the entire mesh is not easily
91                feasible without having a central instance to collect
92                the local topologies from all nodes. This file allows
93                to activate the collecting (server) mode.