public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: NicoEchániz <nicoechaniz@altermundi.net>
To: 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.] Latency Related Problem
Date: Tue, 08 Jan 2013 13:33:43 -0300	[thread overview]
Message-ID: <50EC4A67.2000107@altermundi.net> (raw)
In-Reply-To: <201301082052.12517.lindner_marek@yahoo.de>

On 01/08/2013 09:52 AM, Marek Lindner wrote:
> 
> Hi,
> 
> you don't like the mailing list ? Why do you keep mailing me privately ? this 
> is the last time I respond to mails you send to me privately concerning 
> batman-adv. Use the mailing list!
> 
> On Tuesday, January 08, 2013 19:36:45 you wrote:
>> I am not comparing the ping between two nodes.
>>
>> I am just concerned about the ping latency between nodes.
>>
>> As per my experiment, I am getting 100ms delay between one hop(SPK3
>> –to-SPK2) and 200 ms delay between two hops (SPK3-to-SPK1) and so on.
>>
>> Even 100ms delay seems a lot, some applications may not work properly.
>>
>> Is there any delay (buffer) involved in local packet delivery from  bat0 to
>> local mesh interfaces (wlan0)?
> 
> yes, there is standard wifi buffering. Consider this:
> 
> ping time from node1 to node2: ~100ms
> ping time from node2 to node3: ~100ms
> 
> => ping time from node1 to node3: ~200ms
> 
> The delays simply add up because wifi is a shared medium. The node in the 
> middle can only forward the packet while it does not receive. That is due to 
> how wifi works and has nothing to do with batman-adv.
> 
> If you wish to mitigate the delay you should not use a shared medium. For 
> example using multiple wifi cards on different channels is a solution.


There must be some other problem involved here. We have very good ping
times with batman advanced in working networks as well as test setups.
See this article for example:

http://blog.altermundi.net/article/multiple-hop-mesh-performance-with-multi-band-dual/




      reply	other threads:[~2013-01-08 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHQ_bgg4rRDVAhNce9SdONkFbF946EYrMgvT79kyp_bxk8T8NQ@mail.gmail.com>
2013-01-08  7:44 ` [B.A.T.M.A.N.] Latency Related Problem Marek Lindner
     [not found] ` <201301081906.33146.lindner_marek@yahoo.de>
     [not found]   ` <CAHQ_bgiL+tEz+3Lz+CFWH3Q-n7JhcDqSxRCQRxx-gcd=nYwjEw@mail.gmail.com>
2013-01-08 12:52     ` Marek Lindner
2013-01-08 16:33       ` NicoEchániz [this message]

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=50EC4A67.2000107@altermundi.net \
    --to=nicoechaniz@altermundi.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.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