sysfs-class-net-mesh 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. What: /sys/class/net/<mesh_iface>/mesh/aggregated_ogms
  2. Date: May 2010
  3. Contact: Marek Lindner <lindner_marek@yahoo.de>
  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/bonding
  8. Date: June 2010
  9. Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
  10. Description:
  11. Indicates whether the data traffic going through the
  12. mesh will be sent using multiple interfaces at the
  13. same time (if available).
  14. What: /sys/class/net/<mesh_iface>/mesh/fragmentation
  15. Date: October 2010
  16. Contact: Andreas Langer <an.langer@gmx.de>
  17. Description:
  18. Indicates whether the data traffic going through the
  19. mesh will be fragmented or silently discarded if the
  20. packet size exceeds the outgoing interface MTU.
  21. What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
  22. Date: October 2010
  23. Contact: Marek Lindner <lindner_marek@yahoo.de>
  24. Description:
  25. Defines the bandwidth which is propagated by this
  26. node if gw_mode was set to 'server'.
  27. What: /sys/class/net/<mesh_iface>/mesh/gw_mode
  28. Date: October 2010
  29. Contact: Marek Lindner <lindner_marek@yahoo.de>
  30. Description:
  31. Defines the state of the gateway features. Can be
  32. either 'off', 'client' or 'server'.
  33. What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class
  34. Date: October 2010
  35. Contact: Marek Lindner <lindner_marek@yahoo.de>
  36. Description:
  37. Defines the selection criteria this node will use
  38. to choose a gateway if gw_mode was set to 'client'.
  39. What: /sys/class/net/<mesh_iface>/mesh/orig_interval
  40. Date: May 2010
  41. Contact: Marek Lindner <lindner_marek@yahoo.de>
  42. Description:
  43. Defines the interval in milliseconds in which batman
  44. sends its protocol messages.
  45. What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
  46. Date: Oct 2010
  47. Contact: Linus Lüssing <linus.luessing@web.de>
  48. Description:
  49. Defines the penalty which will be applied to an
  50. originator message's tq-field on every hop.
  51. What: /sys/class/net/<mesh_iface>/mesh/vis_mode
  52. Date: May 2010
  53. Contact: Marek Lindner <lindner_marek@yahoo.de>
  54. Description:
  55. Each batman node only maintains information about its
  56. own local neighborhood, therefore generating graphs
  57. showing the topology of the entire mesh is not easily
  58. feasible without having a central instance to collect
  59. the local topologies from all nodes. This file allows
  60. to activate the collecting (server) mode.