Hello Gabriel,
first of all thank you very much for testing the bw meter :-) answers follow inline.
On Mon, Jun 03, 2013 at 12:57:24PM -0300, Gabriel Tolón wrote:
Hi Antonio,
As you suggested, I've tested the bandwidth meter with batman-adv-devel 38a1b72. I've installed it on two TP-Link WDR-3500 routers.
oky. However, since the bw_meter has not been merged yet, its branch changes from time to time because it gets rebased on top of the very latest development code. Therefore, when you decide to update your testbed, I'd suggest you to look at: http://git.open-mesh.org/batman-adv.git/shortlog/refs/heads/ordex/bw_meter and pick the commit ID of the last patch at the top.
If you have problems in doing this, please ask.
Running normal iperf inside the routers, and without unloading any kernel module, I get 60 Mbps using UDP, 80 Mbps using TCP (I don't understand why TCP works better), and about 4 Mbps with batctl bw -t 10000. Any ideas? By the way, the batctl ping between routers doesn't work, I get time-out. Besides, there's another strange behaviour, when I try to pass traffic from a PC client connected to one router, to the other router using iperf, if I use UDP values of about 100 Mbps, the router that receives the traffic and redirects it, reboots. Thanks.
Ok..well, first of all I'd rather check what is wrong in the mesh. If batctl ping does not work, then it means that there is something else which is not working/configured properly.
For this reason I'll first suggest you to update to this commit id: d672369 . Then, does "batctl o" properly shows the other node with a "reasonable TQ"?
By the way, your iperf tests have been done on top of batman-adv? or directly on the wifi interface?
Cheers,