blob: bc41da61608d5dfc22e0c2836aa00c56499c9d98 [file] [log] [blame]
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +00001
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
Marek Lindner60d8cce2012-10-21 17:02:25 +08009What: /sys/class/net/<mesh_iface>/mesh/ap_isolation
10Date: May 2011
11Contact: Antonio Quartulli <ordex@autistici.org>
12Description:
13 Indicates whether the data traffic going from a
14 wireless client to another wireless client will be
15 silently dropped.
16
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000017What: /sys/class/net/<mesh_iface>/mesh/bonding
18Date: June 2010
19Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
20Description:
21 Indicates whether the data traffic going through the
22 mesh will be sent using multiple interfaces at the
23 same time (if available).
24
Simon Wunderlichc8673052012-01-22 20:00:20 +010025What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
26Date: November 2011
27Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
28Description:
29 Indicates whether the bridge loop avoidance feature
30 is enabled. This feature detects and avoids loops
31 between the mesh and devices bridged with the soft
32 interface <mesh_iface>.
33
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000034What: /sys/class/net/<mesh_iface>/mesh/fragmentation
35Date: October 2010
36Contact: Andreas Langer <an.langer@gmx.de>
37Description:
38 Indicates whether the data traffic going through the
39 mesh will be fragmented or silently discarded if the
40 packet size exceeds the outgoing interface MTU.
41
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000042What: /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
Marek Lindner60d8cce2012-10-21 17:02:25 +080063What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
64Date: Oct 2010
65Contact: Linus LΓΌssing <linus.luessing@web.de>
66Description:
67 Defines the penalty which will be applied to an
68 originator message's tq-field on every hop.
69
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000070What: /sys/class/net/<mesh_iface>/mesh/orig_interval
71Date: May 2010
72Contact: Marek Lindner <lindner_marek@yahoo.de>
73Description:
74 Defines the interval in milliseconds in which batman
75 sends its protocol messages.
76
Marek Lindner60d8cce2012-10-21 17:02:25 +080077What: /sys/class/net/<mesh_iface>/mesh/routing_algo
78Date: Dec 2011
79Contact: Marek Lindner <lindner_marek@yahoo.de>
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000080Description:
Marek Lindner60d8cce2012-10-21 17:02:25 +080081 Defines the routing procotol this mesh instance
82 uses to find the optimal paths through the mesh.
Marek Lindnerea3d2fd2011-11-29 00:15:37 +080083
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000084What: /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.