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/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 33What: /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 68What: /sys/class/net/<mesh_iface>/mesh/vis_mode 69Date: May 2010 70Contact: Marek Lindner <lindner_marek@yahoo.de> 71Description: 72 Each batman node only maintains information about its 73 own local neighborhood, therefore generating graphs 74 showing the topology of the entire mesh is not easily 75 feasible without having a central instance to collect 76 the local topologies from all nodes. This file allows 77 to activate the collecting (server) mode. 78