Ray,
On Tuesday 12 August 2014 11:21:18 Ray Gibson wrote:
I've put all the output in a pastebin as to not clog up everyone's inbox:
Thanks! The output actually looks fine. I've tried a little bit myself in a few VMs and noticed two problems which were preventing bonding to work, at least for me:
* There was a trivial (and rather stupid) logic bug in the check whether bonding should be considered or not. See "[PATCH] batman-adv: fix and simplify condition when bonding should be used" * Another not so trivial problem is that bonding with the multi interface optimization checks the originator tables for the different interfaces. However since you don't use WiFi and all links appear perfect, the same router is often chosen for the different interfaces and the bonding has not enough candidates to choose and do round robin. I've sent an experimental patch "[RFC] batman-adv: experimental sysfs variable to always apply half duplex penalty" which allows to turn on the interface / half duplex penalty for all interfaces, not just wifi interfaces. That patch will most probably not make it upstream, but should be good enough for testing. Enable it with:
echo 1 > /sys/devices/virtual/net/bat0/mesh/always_half_duplex_penalty
Please apply these two patches, set the new option and try again!
[...]
Regardless of its potential impact on performance, I think it's worth a look and test to see if there may be some potential benefit. Currently this setup is working nice in that it's a true case of point to point redundant links. If additional links could be added or removed at will to enhance throughput I would see this useful in a variety of applications. Currently, I'd like to just reproduce what the function was originally designed to do and then go from there.
OK, sure, it can't hurt to try it out - maybe you can even find ways to optimize it. In any case, we would be happy to hear about your test results and experiences. :)
Thanks, Simon