From: "Gabriel Tolón" <gtolon@inti.gob.ar>
To: Antonio Quartulli <ordex@autistici.org>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batctl bw performance
Date: Thu, 06 Jun 2013 16:04:35 -0300 [thread overview]
Message-ID: <51B0DD43.6090500@inti.gob.ar> (raw)
In-Reply-To: <20130606182954.GI1789@ritirata.org>
El 06/06/13 15:29, Antonio Quartulli escribió:
> On Thu, Jun 06, 2013 at 03:19:00PM -0300, Gabriel Tolón wrote:
>> Hi Antonio,
>>
>>
>> El 06/06/13 02:51, Antonio Quartulli escribió:
>>> Hello Gabriel,
>>>
>>> On Wed, Jun 05, 2013 at 12:27:48PM -0300, Gabriel Tolón wrote:
>>>>
>>>> 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)
>>>>
>>>
>>> routing tables look good. I am wondering where the problem can be..
>>> Can you try to do a "batctl td wlan0-1" while pinging? this may help to
>>> understand where the process is blocking.
>>> It would be helpful if you could do that on both the nodes while pinging in only
>>> one direction This way we see who receives what.
>>
>> I did it, but the text files for the logs of the nodes with "batctl td"
>> have a size of about 250 kB each one, with just 1 or 2 seconds logging.
>> Is that too much for sending them to the list?
>
> maybe you can upload them somewhere and then send the link here?
>
Yes, should be here:
http://pastebin.com/GNSC2Pmn
http://pastebin.com/m3xtjchX
the batctl ping was from E1 to E3.
Regards
Gabriel
next prev parent reply other threads:[~2013-06-06 19:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A3C7E9.7080208@inti.gob.ar>
[not found] ` <20130528070057.GC3333@ritirata.org>
[not found] ` <51ACBCE4.8000506@inti.gob.ar>
2013-06-03 16:08 ` [B.A.T.M.A.N.] batctl bw performance Antonio Quartulli
2013-06-03 20:54 ` Gabriel Tolón
2013-06-04 5:13 ` Antonio Quartulli
2013-06-04 5:38 ` Antonio Quartulli
2013-06-05 15:17 ` Gabriel Tolón
2013-06-05 15:27 ` Gabriel Tolón
2013-06-06 5:51 ` Antonio Quartulli
2013-06-06 18:19 ` Gabriel Tolón
2013-06-06 18:29 ` Antonio Quartulli
2013-06-06 19:04 ` Gabriel Tolón [this message]
2013-06-06 19:18 ` Antonio Quartulli
2013-06-07 13:49 ` Gabriel Tolón
2013-06-07 13:57 ` Antonio Quartulli
2013-06-07 14:38 ` Gabriel Tolón
2013-06-07 14:40 ` Antonio Quartulli
2013-06-07 17:13 ` Gabriel Tolón
2013-06-07 17:27 ` Antonio Quartulli
2013-06-07 18:39 ` Antonio Quartulli
2013-06-07 18:57 ` Gabriel Tolón
2013-06-08 12:29 ` Antonio Quartulli
2013-06-08 20:20 ` Antonio Quartulli
2013-06-09 0:26 ` NicoEchániz
2013-06-10 13:12 ` Gabriel Tolón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51B0DD43.6090500@inti.gob.ar \
--to=gtolon@inti.gob.ar \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ordex@autistici.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox