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

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