Hi all,
Very nice setup Andrew :)
On Fri, Jan 27, 2012 at 08:13:34 +0100, Andrew Lunn wrote:
So, you had to reduce the default value of 10 to something even smaller ? A
hop penalty of 10 results in a penatly of 4% per hop. A rough equivalent of
2
lost packets (62/64). Does not sound
On Fri, Jan 27, 2012 at 11:54:25PM +0800, Marek Lindner wrote:
Hi Andrew,
Do you have any performance analysis to show this is really helpful
and not harmful?
I've seen indoor results where i had to reduce the hop penalty,
otherwise BATMAN was taking a short path which worked
Hi,
In my honest opinion we are mixing two different issues:
1) current hop penalty value not really significant
2) OGM link quality measurements do not reflect the metric we'd like it to
be
problem 2 is not going to be solved by hacking the hop penalty. It needs
further
On Saturday, January 28, 2012 03:13:34 Andrew Lunn wrote:
When iperf was used to measure the traffic from one end of the chain
to the other. With the default hop penalty we got poor
performance. With the traceroute facility of batctl, we could see it
was route flipping between 3 hops and 4
Hi,
I have experencied the same situation in some tests, and I agree with
Andrew when he says that some form of justification is necessary.
you also have seen that a hop penalty of 10 is too high ? Can you explain your
setup a bit more ?
The problems of TQ emerges when the rate of devices
