Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit ed26d2b4024f9580a426d63bbf514e2b729d77d8 Author: Marek Lindner mareklindner@neomailbox.ch Date: Mon Nov 22 01:11:09 2010 +0000
doc: batman-adv/Tweaking
ed26d2b4024f9580a426d63bbf514e2b729d77d8 batman-adv/Tweaking.textile | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/batman-adv/Tweaking.textile b/batman-adv/Tweaking.textile index 5760e328..089a163d 100644 --- a/batman-adv/Tweaking.textile +++ b/batman-adv/Tweaking.textile @@ -9,7 +9,7 @@ __Note__: Although this document focusses on the "raw" /sys/ configuration inter
=== Interface handling ===
-To better understand the background of the new interface configuration concept (as of batman-adv 2010.0.0), it is helpful to see in which direction batman-adv is heading: Until now, batman aggregated all configured interface into a single mesh cloud (manifested in a single bat0 interface). In the future it will be possible to let a single mesh node participate in mutliple mesh clouds at the same time which makes it necessary to assign interfaces to individual mesh clouds and having multiple batX interfaces. Although the "multiple mesh cloud" feature is not complete yet, the configuration interface support is already available. +To better understand the background of the new interface configuration concept (as of batman-adv 2010.0.0), it is helpful to see in which direction batman-adv is heading: Until now, batman aggregated all configured interface into a single mesh cloud (manifested in a single bat0 interface). As of 2010.2.0 it is possible to let a single mesh node participate in mutliple mesh clouds at the same time which makes it necessary to assign interfaces to individual mesh clouds and having multiple batX interfaces.
After loading batman-adv, it will scan your systems interfaces to search for compatible interfaces. Once found, it will create subfolders in the /sys/class/net/<iface> directories of each supported interface, e.g.
@@ -21,7 +21,7 @@ iface_status mesh_iface If an interface does not have the "batman_adv" subfolder it probably is not supported. Not supported interfaces are: loopback, non-ethernet and batman's own interfaces.[[BR]] __Note__: After the module was loaded it will continuously watch for new interfaces to verify the compatibility. There is no need to reload the module if you plug your USB wifi adapter into your machine after batman advanced was initially loaded.
-To activate a given interface on a mesh cloud simply write the mesh clouds interface name into its "mesh_iface" file inside the batman_adv subfolder. Since the "multiple mesh cloud" feature is currently disabled, you can only write "bat0" but later on you can freely choose the interface name. +To activate a given interface on a mesh cloud simply write the mesh clouds interface name into its "mesh_iface" file inside the batman_adv subfolder. You can freely choose the interface name but for the sake of simplicity we continue to use "bat0".
{{{ echo bat0 > /sys/class/net/eth0/batman_adv/mesh_iface @@ -46,7 +46,7 @@ After having added interfaces to a mesh cloud, batman-adv automatically creates
{{{ ls /sys/class/net/bat0/mesh/ -aggregated_ogms bonding log_level orig_interval vis_mode +aggregated_ogms bonding fragmentation log_level orig_interval vis_mode }}}
'''aggregate originator messages''' @@ -71,6 +71,19 @@ cat /sys/class/net/bat0/mesh/bonding disabled }}}
+'''fragmentation''' + +Available since: batman-adv 2010.2.0 + +Batman-adv has a built-in layer 2 fragmentation for unicast data flowing through the mesh which will allow to run batman-adv over interfaces / connections that don't allow to increase the MTU beyond the standard Ethernet packet size of 1500 bytes. When the fragmentation is enabled batman-adv will automatically fragment over-sized packets and defragment them on the other end. Per default fragmentation is enabled and inactive if the packet fits but it is possible to deactivate the fragmentation entirely. + +__Note__: Although the fragmentation is rather handy it comes with a severe performance penalty (as every fragmentation does), therefore it should be avoided to make use of this feature whenever possible. + +{{{ +cat /sys/class/net/bat0/mesh/fragmentation +enabled +}}} + '''log level'''
Available since: batman-adv 2010.1.0 (if debugging has been compiled-in)