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/fragmentation
18Date:           October 2010
19Contact:        Andreas Langer <an.langer@gmx.de>
20Description:
21                Indicates whether the data traffic going through the
22                mesh will be fragmented or silently discarded if the
23                packet size exceeds the outgoing interface MTU.
24
25What:           /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
26Date:           October 2010
27Contact:        Marek Lindner <lindner_marek@yahoo.de>
28Description:
29                Defines the bandwidth which is propagated by this
30                node if gw_mode was set to 'server'.
31
32What:           /sys/class/net/<mesh_iface>/mesh/gw_mode
33Date:           October 2010
34Contact:        Marek Lindner <lindner_marek@yahoo.de>
35Description:
36                Defines the state of the gateway features. Can be
37                either 'off', 'client' or 'server'.
38
39What:           /sys/class/net/<mesh_iface>/mesh/gw_sel_class
40Date:           October 2010
41Contact:        Marek Lindner <lindner_marek@yahoo.de>
42Description:
43                Defines the selection criteria this node will use
44                to choose a gateway if gw_mode was set to 'client'.
45
46What:           /sys/class/net/<mesh_iface>/mesh/orig_interval
47Date:           May 2010
48Contact:        Marek Lindner <lindner_marek@yahoo.de>
49Description:
50                Defines the interval in milliseconds in which batman
51                sends its protocol messages.
52
53What:           /sys/class/net/<mesh_iface>/mesh/hop_penalty
54Date:           Oct 2010
55Contact:        Linus Lüssing <linus.luessing@web.de>
56Description:
57		Defines the penalty which will be applied to an
58		originator message's tq-field on every hop.
59
60What:           /sys/class/net/<mesh_iface>/mesh/vis_mode
61Date:           May 2010
62Contact:        Marek Lindner <lindner_marek@yahoo.de>
63Description:
64                Each batman node only maintains information about its
65                own local neighborhood, therefore generating graphs
66                showing the topology of the entire mesh is not easily
67                feasible without having a central instance to collect
68                the local topologies from all nodes. This file allows
69                to activate the collecting (server) mode.