blob: b218e0f8bdb389eaaa6c14c6c071bb5d033289bc [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
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
Antonio Quartulli59b699c2011-07-07 15:35:36 +020025What: /sys/class/net/<mesh_iface>/mesh/ap_isolation
26Date: May 2011
27Contact: Antonio Quartulli <ordex@autistici.org>
28Description:
29 Indicates whether the data traffic going from a
30 wireless client to another wireless client will be
31 silently dropped.
32
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000033What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
34Date: October 2010
35Contact: Marek Lindner <lindner_marek@yahoo.de>
36Description:
37 Defines the bandwidth which is propagated by this
38 node if gw_mode was set to 'server'.
39
40What: /sys/class/net/<mesh_iface>/mesh/gw_mode
41Date: October 2010
42Contact: Marek Lindner <lindner_marek@yahoo.de>
43Description:
44 Defines the state of the gateway features. Can be
45 either 'off', 'client' or 'server'.
46
47What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class
48Date: October 2010
49Contact: Marek Lindner <lindner_marek@yahoo.de>
50Description:
51 Defines the selection criteria this node will use
52 to choose a gateway if gw_mode was set to 'client'.
53
54What: /sys/class/net/<mesh_iface>/mesh/orig_interval
55Date: May 2010
56Contact: Marek Lindner <lindner_marek@yahoo.de>
57Description:
58 Defines the interval in milliseconds in which batman
59 sends its protocol messages.
60
61What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
62Date: Oct 2010
63Contact: Linus LΓΌssing <linus.luessing@web.de>
64Description:
65 Defines the penalty which will be applied to an
66 originator message's tq-field on every hop.
67
Marek Lindnerea3d2fd2011-11-29 00:15:37 +080068What: /sys/class/net/<mesh_iface>/mesh/routing_algo
69Date: Dec 2011
70Contact: Marek Lindner <lindner_marek@yahoo.de>
71Description:
72 Defines the routing procotol this mesh instance
73 uses to find the optimal paths through the mesh.
74
Sven Eckelmannc6c8fea2010-12-13 11:19:28 +000075What: /sys/class/net/<mesh_iface>/mesh/vis_mode
76Date: May 2010
77Contact: Marek Lindner <lindner_marek@yahoo.de>
78Description:
79 Each batman node only maintains information about its
80 own local neighborhood, therefore generating graphs
81 showing the topology of the entire mesh is not easily
82 feasible without having a central instance to collect
83 the local topologies from all nodes. This file allows
84 to activate the collecting (server) mode.