Re: [B.A.T.M.A.N.] batctl bw performance

["Gabriel Tolón" <gtolon@inti.gob.ar>]

Sorry, I sent the mail incomplete,

So these are the routes:

Equipo1:

root@Equipo 1:~# batctl o
[B.A.T.M.A.N. adv 5ffa8f2, MainIF/MAC: wlan0-1/66:70:02:4e:d9:42 (bat0)]
   Originator      last-seen (#/255)           Nexthop [outgoingIF]: 
Potential nexthops ...
           E3-5GHz    0.680s   (251)           E3-5GHz [   wlan1-1]: 
        E3-5GHz (251)
           E3-2GHz    0.430s   (255)           E3-5GHz [   wlan1-1]: 
        E3-5GHz (255)           E3-2GHz (252)


Equipo3:

root@Equipo 3:~# batctl o
[B.A.T.M.A.N. adv 5ffa8f2, MainIF/MAC: wlan0-1/66:70:02:4e:d9:d6 (bat0)]
   Originator      last-seen (#/255)           Nexthop [outgoingIF]: 
Potential nexthops ...
           E1-2GHz    0.310s   (255)           E1-5GHz [   wlan1-1]: 
        E1-5GHz (255)           E1-2GHz (255)
           E1-5GHz    0.550s   (255)           E1-5GHz [   wlan1-1]: 
        E1-5GHz (255)



The results of batctl pings:

Equipo1:

root@Equipo 1:~# batctl ping E3-2GHz
PING E3-2GHz (66:70:02:4e:d9:d6) 20(48) bytes of data
Reply from host E3-2GHz timed out
Reply from host E3-2GHz timed out

root@Equipo 1:~# batctl ping E3-5GHz
PING E3-5GHz (66:70:02:4e:d9:d7) 20(48) bytes of data
Reply from host E3-5GHz timed out
Reply from host E3-5GHz timed out



Equipo3:

root@Equipo 3:~# batctl ping E1-2GHz
PING E1-2GHz (66:70:02:4e:d9:42) 20(48) bytes of data
Reply from host E1-2GHz timed out
Reply from host E1-2GHz timed out


root@Equipo 3:~# batctl ping E1-5GHz
PING E1-5GHz (66:70:02:4e:d9:43) 20(48) bytes of data
Reply from host E1-5GHz timed out
Reply from host E1-5GHz timed out


If there is more info I could send you just tell me.

Regards

Gabriel





El 05/06/13 12:17, Gabriel Tolón escribió:
> Hi,
>
> Now I'm with batman-adv 5ffa8f201d085764365d202ace14675032cc3a74, batctl
> 6d3d4d1f80dca31b6400f3794772016cdbc19a73, and openwrt r36826.
>
> The results are almost the same, no batctl pings, and batctl bw much
> slower than iperfs. wdr3500 have 2 radios, these are the routes:
>
>
>
>
>
> El 04/06/13 02:38, Antonio Quartulli escribió:
>> On Tue, Jun 04, 2013 at 07:13:26AM +0200, Antonio Quartulli wrote:
>>> On Mon, Jun 03, 2013 at 05:54:15PM -0300, Gabriel Tolón wrote:
>>>> So, in menuconfig I should select that id for batman-adv-devel right? I
>>>> wanted to see that  commit on the git page using the search field but I
>>>> couldn't. By the way, how to know which batctl version use with each
>>>> batman-adv-devel commit? Sorry if all these questions are too basic,
>>>> but
>>>> I've tried to compile with this d672369 version and I got some errors,
>>>> so I'd like to understand if it was related to these things.
>>>
>>> no problems. These are not basic questions :) Actually the user
>>> usually do not
>>> enter these dev details and therefore it is normal to find issues.
>>>
>>> For batctl, you should use the last commit ID in this branch
>>> (ordex/bw_meter)
>>> http://git.open-mesh.org/batctl.git/shortlog/refs/heads/ordex/bw_meter
>>>
>>>>
>>>>>
>>>>>
>>>>> By the way, your iperf tests have been done on top of batman-adv?
>>>>> or directly on
>>>>> the wifi interface?
>>>>>
>>>>> Cheers,
>>>>>
>>>>
>>>> I got the results mentioned using interfaces managed by batman-adv.
>>>
>>> mh...maybe the pign is not working because of some changes brought by
>>> the
>>> bw_meter in the icmp packets. I'll check and I'll let you know.
>>
>> I juested the current ordex/bw_meter branches (batctl and batman-adv)
>> and the
>> ping works fine.
>>
>> Please, let me know your results.
>>
>> Cheers,
>>
>>