sysfs-class-net-mesh 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  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/ap_isolation
  22. Date: May 2011
  23. Contact: Antonio Quartulli <ordex@autistici.org>
  24. Description:
  25. Indicates whether the data traffic going from a
  26. wireless client to another wireless client will be
  27. silently dropped.
  28. What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth
  29. Date: October 2010
  30. Contact: Marek Lindner <lindner_marek@yahoo.de>
  31. Description:
  32. Defines the bandwidth which is propagated by this
  33. node if gw_mode was set to 'server'.
  34. What: /sys/class/net/<mesh_iface>/mesh/gw_mode
  35. Date: October 2010
  36. Contact: Marek Lindner <lindner_marek@yahoo.de>
  37. Description:
  38. Defines the state of the gateway features. Can be
  39. either 'off', 'client' or 'server'.
  40. What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class
  41. Date: October 2010
  42. Contact: Marek Lindner <lindner_marek@yahoo.de>
  43. Description:
  44. Defines the selection criteria this node will use
  45. to choose a gateway if gw_mode was set to 'client'.
  46. What: /sys/class/net/<mesh_iface>/mesh/orig_interval
  47. Date: May 2010
  48. Contact: Marek Lindner <lindner_marek@yahoo.de>
  49. Description:
  50. Defines the interval in milliseconds in which batman
  51. sends its protocol messages.
  52. What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
  53. Date: Oct 2010
  54. Contact: Linus Lüssing <linus.luessing@web.de>
  55. Description:
  56. Defines the penalty which will be applied to an
  57. originator message's tq-field on every hop.
  58. What: /sys/class/net/<mesh_iface>/mesh/vis_mode
  59. Date: May 2010
  60. Contact: Marek Lindner <lindner_marek@yahoo.de>
  61. Description:
  62. Each batman node only maintains information about its
  63. own local neighborhood, therefore generating graphs
  64. showing the topology of the entire mesh is not easily
  65. feasible without having a central instance to collect
  66. the local topologies from all nodes. This file allows
  67. to activate the collecting (server) mode.