Re: [B.A.T.M.A.N.] Batman-adv high TQ and Low throughput

[Simon Wunderlich <sw@simonwunderlich.de>]

> Recently i have experienced something quite usual to my experience and
> that was not happening previously in the same scenario where it is
> happening now.
> 
> Here is the example:
> 2 nodes at with adhoc at 2.4ghz at a distance of 415 meters
> one uses an omni 15 dbi antenna at 18dbi and another 24 dbi grid at 16 dbi.
> 
> This link was previously providing up to 21 mbit being 17 mbit a the
> lowest. Batman-adv TQ value was always around 230 being many times above
> 250.
> 
> However this has recently changed the same link with 230~250 TQ and the
> same txpower is now outputting 1.93 Mbits/sec
> 
> I have used iperf for bandwidth tests. Batman-adv version is 2013.4.
> Although i have considered several types of scenarios that can be
> causing this issue i have also tested against some which leaves me
> puzzled in regards to the presented TQ quality and dBm values as the
> nodes dBm are sometimes bad (ie: -80 ~ -90)
> 
> One of the main questions is: shouldn't batman-adv TQ reflect or be
> influenced by dBm values ? How come with -90 dBm i get batman-adv to
> show me 230 TQ ?

The current implementation in batman-adv counts broadcast packets to compute 
the TQ. Therefore this number reflects (more or less) the transmit success 
probability on whatever wifi broadcast modulation rate you have configured 
(default the lowest, e.g. 1M in 2.4 GHz). A common tweak is to set the 
broadcast rate (also called multicast rate) to something higher, e.g. 18M or 
36M, to get a better analysis on these modulation rates. This should also help 
in your scenario, but might affect the range of your batman-adv network.

Cheers,
    Simon