Documentation/ABI/testing/sysfs-class-net-mesh

   1
   2 What:           /sys/class/net/<mesh_iface>/mesh/aggregated_ogms
   3 Date:           May 2010
   4 Contact:        Marek Lindner <lindner_marek@yahoo.de>
   5 Description:
   6                 Indicates whether the batman protocol messages of the
   7                 mesh <mesh_iface> shall be aggregated or not.
   8
   9 What:           /sys/class/net/<mesh_iface>/mesh/ap_isolation
  10 Date:           May 2011
  11 Contact:        Antonio Quartulli <ordex@autistici.org>
  12 Description:
  13                 Indicates whether the data traffic going from a
  14                 wireless client to another wireless client will be
  15                 silently dropped.
  16
  17 What:           /sys/class/net/<mesh_iface>/mesh/bonding
  18 Date:           June 2010
  19 Contact:        Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
  20 Description:
  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
  25 What:           /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
  26 Date:           November 2011
  27 Contact:        Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
  28 Description:
  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
  34 What:           /sys/class/net/<mesh_iface>/mesh/fragmentation
  35 Date:           October 2010
  36 Contact:        Andreas Langer <an.langer@gmx.de>
  37 Description:
  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
  42 What:           /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
  43 Date:           October 2010
  44 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  45 Description:
  46                 Defines the bandwidth which is propagated by this
  47                 node if gw_mode was set to 'server'.
  48
  49 What:           /sys/class/net/<mesh_iface>/mesh/gw_mode
  50 Date:           October 2010
  51 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  52 Description:
  53                 Defines the state of the gateway features. Can be
  54                 either 'off', 'client' or 'server'.
  55
  56 What:           /sys/class/net/<mesh_iface>/mesh/gw_sel_class
  57 Date:           October 2010
  58 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  59 Description:
  60                 Defines the selection criteria this node will use
  61                 to choose a gateway if gw_mode was set to 'client'.
  62
  63 What:           /sys/class/net/<mesh_iface>/mesh/hop_penalty
  64 Date:           Oct 2010
  65 Contact:        Linus Lüssing <linus.luessing@web.de>
  66 Description:
  67                 Defines the penalty which will be applied to an
  68                 originator message's tq-field on every hop.
  69
  70 What:           /sys/class/net/<mesh_iface>/mesh/orig_interval
  71 Date:           May 2010
  72 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  73 Description:
  74                 Defines the interval in milliseconds in which batman
  75                 sends its protocol messages.
  76
  77 What:           /sys/class/net/<mesh_iface>/mesh/routing_algo
  78 Date:           Dec 2011
  79 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  80 Description:
  81                 Defines the routing procotol this mesh instance
  82                 uses to find the optimal paths through the mesh.
  83
  84 What:           /sys/class/net/<mesh_iface>/mesh/vis_mode
  85 Date:           May 2010
  86 Contact:        Marek Lindner <lindner_marek@yahoo.de>
  87 Description:
  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.