Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2019-09-14,master
commit 16958dc252c4bcaa2de9dff5fdacf1ba8fba54e0 Author: Sven Eckelmann sven@narfation.org Date: Sun Mar 3 19:37:36 2019 +0000
doc: batman-adv/Fragmentation-technical: don't reference deprecated sysfs files
16958dc252c4bcaa2de9dff5fdacf1ba8fba54e0 batman-adv/Fragmentation-technical.textile | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/batman-adv/Fragmentation-technical.textile b/batman-adv/Fragmentation-technical.textile index e02114b..e452192 100644 --- a/batman-adv/Fragmentation-technical.textile +++ b/batman-adv/Fragmentation-technical.textile @@ -61,17 +61,13 @@ h2. Configuration
First of all, fragmentation shouldn't be needed (except for tt-tables, see below). It is a fix for drivers/hardware that is unable to handle MTU's greater than 1528 bytes, it is slow (due to increase is packets), and is susceptible to packet loss.
-It can be enabled and disabled in the sysfs file: +It can be enabled and disabled via batctl: <pre> -%25 echo 1 > /sys/class/net/bat0/mesh/fragmentation # enable (default) -%25 echo 0 > /sys/class/net/bat0/mesh/fragmentation # disable -</pre> -or by using @batctl@: -<pre> -%25 batctl f 1 # enable -%25 batctl f 0 # disable +% batctl -m bat0 fragmentation 1 # enable (default) +% batctl -m bat0 fragmentation 0 # disable </pre>
+ h2. Limitations
If an intermediate node with an unexpectedly lower MTU exists, this scheme breaks. In the scenario "A <-> B <-> C", where A and C have MTU=1550 and B has MTU=1000 bytes, B cannot respond with nor forward very-big-full-tables from A to C. At the moment, batman-adv simply forwards the requests and hopes for the best.