Skip to contentSkip to conversation

batctl.8 suggested correction.

B.A.T.M.A.N. cmsv 2 participants 2 messages Mar 3, 2013

lore
Share & tools
lore

cmsv

author
#0 lore raw

Having in mind that throughput and bandwidth are not the same and do not necessarily match; the use of the word "throughput" in batman-adv (Layer2) is misleading and can cause confusion when in measuring the real throughput on layer3 with L3 software.

As far as i know; at the moment batman-adv (L2) has no way to know what is the real throughput that the announced gateway bandwidth (l3) actually allows therefore the " throughput" should be changed to announced bandwidth.

Example:

If the node is a gateway client the parameter will decide which criterias to consider when the batman-adv module has to choose between different internet connections announced by the afore- mentioned servers.
default: 20 -> late switch (TQ 20)
examples: 1 -> fast connection
consider the gateway's advertised bandwidth as well as the link quality towards the gateway and stick with the selection until the gateway disappears
2 -> stable connection
chooses the gateway with the best link quality and sticks with it (ignore the advertised bandwidth)
3 -> fast switch connection
chooses the gateway with the best link quality but switches to another gateway as soon as a better one is found
XX -> late switch connection
chooses the gateway with the best link quality but switches to another gateway as soon as a better one is found which is at least XX TQ better than the cur- rently selected gateway (XX has to be a number between 3 and 256).

Signature · 2 lines
Redes wireless
http://wirelesspt.net
#1 lore raw

Hello,

Quoted 6 lines · cmsv

Having in mind that throughput and bandwidth are not the same and do not necessarily match; the use of the word "throughput" in batman-adv (Layer2) is misleading and can cause confusion when in measuring the real throughput on layer3 with L3 software.

As far as i know; at the moment batman-adv (L2) has no way to know what is the real throughput that the announced gateway bandwidth (l3) actually allows therefore the " throughput" should be changed to announced bandwidth.

Yeah, batman-adv does not know anything about the real throughput.

Quoted 19 lines

Example:

If the node is a gateway client the parameter will decide which criterias to consider when the batman-adv module has to choose between different internet connections announced by the afore- mentioned servers.
default: 20 -> late switch (TQ 20)
examples: 1 -> fast connection
consider the gateway's advertised bandwidth as well as the link quality towards the gateway and stick with the selection until the gateway disappears
2 -> stable connection
chooses the gateway with the best link quality and sticks with it (ignore the advertised bandwidth)
3 -> fast switch connection
chooses the gateway with the best link quality but switches to another gateway

Quoted 10 lines

as soon as a better one is found
XX -> late switch connection
chooses the gateway with the best link quality but switches to another gateway as soon as a better one is found which is at least XX TQ better than the cur- rently selected gateway (XX has to be a number between 3 and 256).

I think this change is correct. Why not sending a patch that we can directly apply in the batctl repository?

Thanks.
Cheers,

Signature · 4 lines
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara