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/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 17What: /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 25What: /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 34What: /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 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/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 70What: /sys/class/net/<mesh_iface>/mesh/network_coding 71Date: Nov 2012 72Contact: Martin Hundeboll <martin@hundeboll.net> 73Description: 74 Controls whether Network Coding (using some magic 75 to send fewer wifi packets but still the same 76 content) is enabled or not. 77 78What: /sys/class/net/<mesh_iface>/mesh/orig_interval 79Date: May 2010 80Contact: Marek Lindner <lindner_marek@yahoo.de> 81Description: 82 Defines the interval in milliseconds in which batman 83 sends its protocol messages. 84 85What: /sys/class/net/<mesh_iface>/mesh/routing_algo 86Date: Dec 2011 87Contact: Marek Lindner <lindner_marek@yahoo.de> 88Description: 89 Defines the routing procotol this mesh instance 90 uses to find the optimal paths through the mesh. 91 92What: /sys/class/net/<mesh_iface>/mesh/vis_mode 93Date: May 2010 94Contact: Marek Lindner <lindner_marek@yahoo.de> 95Description: 96 Each batman node only maintains information about its 97 own local neighborhood, therefore generating graphs 98 showing the topology of the entire mesh is not easily 99 feasible without having a central instance to collect 100 the local topologies from all nodes. This file allows 101 to activate the collecting (server) mode. 102