Re: [B.A.T.M.A.N.] Traffic Control in batman-adv

[gtolon@inti.gob.ar]

Hi Sven, thanks for replying.

El 25/04/2012 05:51 p.m., Sven Eckelmann escribió:
> On Wednesday 25 April 2012 17:27:03 gtolon@inti.gob.ar wrote:
>> Hi,
> First thing: Don't reply to random messages when you actually want to start a
> new topic.

Ok.

>> We are doing some tests with Traffic Control (tc) in routers with
>> Openwrt running batman-adv, want to be able to share the bandwidth with
>> some degree of fairness between users, so we think that SFQ could help,
>> differentiating the flows depending on ip addresses and ports.
>>
>> The problem is that when adding the SFQ qdisc to the wireless interface
>> managed by batman it doesn't work as expected. We tested the SFQ in
>> other configurations and it worked fine, in full queues, the dropped
>> packets affected the big flows, allowing the others to pass, but in the
>> interface managed by batman-adv when packets are dropped, the result
>> affects all flows almost equally. We thought this could be related with
>> the bridge we use to connect the batman with the non-batman interfaces,
>> but in a wireless Acces Point bridged to bat0 it also worked fine. Maybe
>> it's related with the way bat0 works with it's managed interface? We'd
>> appreciate any advices. Thanks in advance!
> Why do you add the sfq qdisc to the wireless device instead to the bat0
> device? It doesn't really makes sense to me.
I also tryed with bat0, but the packets continued to dropp on the 
wireless device, not in bat0, so i thought that the qdisc of bat0 was 
not being used. Anyway, i'll try again.


> Also your statement about "batman-adv bridged with non-batman-adv" doesn't
> work, but "batman-adv bridged with non-batman-adv interface" works statement
> is slightly irritating. Please explain it a little bit more verbose to help us
> understand what is the difference.
Sorry for the bad explanation,what i wanted to say is:

We have a bridge with bat0, eth0 and wlan0 attached. wlan0 is in ap 
mode. There's another wireless interface, wlan0-1 in ad-hoc mode, 
managed by bat0. When SFQ qdisc is applied to wlan0, it works as 
expected. When it's aplied to wlan0-1, it doesn't. In both cases there's 
a bridge involved, that´s what i was trying to point. I hope now it's 
more clear.

Best regards

Gabriel