sysfs-class-net-mesh 3.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. What: /sys/class/net/<mesh_iface>/mesh/aggregated_ogms
  2. Date: May 2010
  3. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  4. Description:
  5. Indicates whether the batman protocol messages of the
  6. mesh <mesh_iface> shall be aggregated or not.
  7. What: /sys/class/net/<mesh_iface>/mesh/<vlan_subdir>/ap_isolation
  8. Date: May 2011
  9. Contact: Antonio Quartulli <antonio@meshcoding.com>
  10. Description:
  11. Indicates whether the data traffic going from a
  12. wireless client to another wireless client will be
  13. silently dropped. <vlan_subdir> is empty when referring
  14. to the untagged lan.
  15. What: /sys/class/net/<mesh_iface>/mesh/bonding
  16. Date: June 2010
  17. Contact: Simon Wunderlich <sw@simonwunderlich.de>
  18. Description:
  19. Indicates whether the data traffic going through the
  20. mesh will be sent using multiple interfaces at the
  21. same time (if available).
  22. What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
  23. Date: November 2011
  24. Contact: Simon Wunderlich <sw@simonwunderlich.de>
  25. Description:
  26. Indicates whether the bridge loop avoidance feature
  27. is enabled. This feature detects and avoids loops
  28. between the mesh and devices bridged with the soft
  29. interface <mesh_iface>.
  30. What: /sys/class/net/<mesh_iface>/mesh/fragmentation
  31. Date: October 2010
  32. Contact: Andreas Langer <an.langer@gmx.de>
  33. Description:
  34. Indicates whether the data traffic going through the
  35. mesh will be fragmented or silently discarded if the
  36. packet size exceeds the outgoing interface MTU.
  37. What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
  38. Date: October 2010
  39. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  40. Description:
  41. Defines the bandwidth which is propagated by this
  42. node if gw_mode was set to 'server'.
  43. What: /sys/class/net/<mesh_iface>/mesh/gw_mode
  44. Date: October 2010
  45. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  46. Description:
  47. Defines the state of the gateway features. Can be
  48. either 'off', 'client' or 'server'.
  49. What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class
  50. Date: October 2010
  51. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  52. Description:
  53. Defines the selection criteria this node will use
  54. to choose a gateway if gw_mode was set to 'client'.
  55. What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
  56. Date: Oct 2010
  57. Contact: Linus Lüssing <linus.luessing@web.de>
  58. Description:
  59. Defines the penalty which will be applied to an
  60. originator message's tq-field on every hop.
  61. What: /sys/class/net/<mesh_iface>/mesh/network_coding
  62. Date: Nov 2012
  63. Contact: Martin Hundeboll <martin@hundeboll.net>
  64. Description:
  65. Controls whether Network Coding (using some magic
  66. to send fewer wifi packets but still the same
  67. content) is enabled or not.
  68. What: /sys/class/net/<mesh_iface>/mesh/orig_interval
  69. Date: May 2010
  70. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  71. Description:
  72. Defines the interval in milliseconds in which batman
  73. sends its protocol messages.
  74. What: /sys/class/net/<mesh_iface>/mesh/routing_algo
  75. Date: Dec 2011
  76. Contact: Marek Lindner <mareklindner@neomailbox.ch>
  77. Description:
  78. Defines the routing procotol this mesh instance
  79. uses to find the optimal paths through the mesh.