1 2What: /sys/class/net/<mesh_iface>/mesh/aggregated_ogms 3Date: May 2010 4Contact: Marek Lindner <mareklindner@neomailbox.ch> 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/<vlan_subdir>/ap_isolation 10Date: May 2011 11Contact: Antonio Quartulli <a@unstable.cc> 12Description: 13 Indicates whether the data traffic going from a 14 wireless client to another wireless client will be 15 silently dropped. <vlan_subdir> is empty when referring 16 to the untagged lan. 17 18What: /sys/class/net/<mesh_iface>/mesh/bonding 19Date: June 2010 20Contact: Simon Wunderlich <sw@simonwunderlich.de> 21Description: 22 Indicates whether the data traffic going through the 23 mesh will be sent using multiple interfaces at the 24 same time (if available). 25 26What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance 27Date: November 2011 28Contact: Simon Wunderlich <sw@simonwunderlich.de> 29Description: 30 Indicates whether the bridge loop avoidance feature 31 is enabled. This feature detects and avoids loops 32 between the mesh and devices bridged with the soft 33 interface <mesh_iface>. 34 35What: /sys/class/net/<mesh_iface>/mesh/fragmentation 36Date: October 2010 37Contact: Andreas Langer <an.langer@gmx.de> 38Description: 39 Indicates whether the data traffic going through the 40 mesh will be fragmented or silently discarded if the 41 packet size exceeds the outgoing interface MTU. 42 43What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth 44Date: October 2010 45Contact: Marek Lindner <mareklindner@neomailbox.ch> 46Description: 47 Defines the bandwidth which is propagated by this 48 node if gw_mode was set to 'server'. 49 50What: /sys/class/net/<mesh_iface>/mesh/gw_mode 51Date: October 2010 52Contact: Marek Lindner <mareklindner@neomailbox.ch> 53Description: 54 Defines the state of the gateway features. Can be 55 either 'off', 'client' or 'server'. 56 57What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class 58Date: October 2010 59Contact: Marek Lindner <mareklindner@neomailbox.ch> 60Description: 61 Defines the selection criteria this node will use 62 to choose a gateway if gw_mode was set to 'client'. 63 64What: /sys/class/net/<mesh_iface>/mesh/hop_penalty 65Date: Oct 2010 66Contact: Linus Lüssing <linus.luessing@web.de> 67Description: 68 Defines the penalty which will be applied to an 69 originator message's tq-field on every hop. 70 71What: /sys/class/net/<mesh_iface>/mesh/isolation_mark 72Date: Nov 2013 73Contact: Antonio Quartulli <a@unstable.cc> 74Description: 75 Defines the isolation mark (and its bitmask) which 76 is used to classify clients as "isolated" by the 77 Extended Isolation feature. 78 79What: /sys/class/net/<mesh_iface>/mesh/multicast_mode 80Date: Feb 2014 81Contact: Linus Lüssing <linus.luessing@web.de> 82Description: 83 Indicates whether multicast optimizations are enabled 84 or disabled. If set to zero then all nodes in the 85 mesh are going to use classic flooding for any 86 multicast packet with no optimizations. 87 88What: /sys/class/net/<mesh_iface>/mesh/network_coding 89Date: Nov 2012 90Contact: Martin Hundeboll <martin@hundeboll.net> 91Description: 92 Controls whether Network Coding (using some magic 93 to send fewer wifi packets but still the same 94 content) is enabled or not. 95 96What: /sys/class/net/<mesh_iface>/mesh/orig_interval 97Date: May 2010 98Contact: Marek Lindner <mareklindner@neomailbox.ch> 99Description: 100 Defines the interval in milliseconds in which batman 101 sends its protocol messages. 102 103What: /sys/class/net/<mesh_iface>/mesh/routing_algo 104Date: Dec 2011 105Contact: Marek Lindner <mareklindner@neomailbox.ch> 106Description: 107 Defines the routing procotol this mesh instance 108 uses to find the optimal paths through the mesh. 109
