public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: cmsv <cmsv@wirelesspt.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: openwrt-users <openwrt-users@lists.openwrt.org>,
	Battlemesh Ninux <battlemesh@ml.ninux.org>
Subject: [B.A.T.M.A.N.] Batman-adv high TQ and Low throughput
Date: Thu, 24 Apr 2014 04:34:44 -0400	[thread overview]
Message-ID: <5358CCA4.2050203@wirelesspt.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

Recently i have experienced something quite usual to my experience and
that was not happening previously in the same scenario where it is
happening now.

Here is the example:
2 nodes at with adhoc at 2.4ghz at a distance of 415 meters
one uses an omni 15 dbi antenna at 18dbi and another 24 dbi grid at 16 dbi.

This link was previously providing up to 21 mbit being 17 mbit a the
lowest. Batman-adv TQ value was always around 230 being many times above
250.

However this has recently changed the same link with 230~250 TQ and the
same txpower is now outputting 1.93 Mbits/sec

I have used iperf for bandwidth tests. Batman-adv version is 2013.4.
Although i have considered several types of scenarios that can be
causing this issue i have also tested against some which leaves me
puzzled in regards to the presented TQ quality and dBm values as the
nodes dBm are sometimes bad (ie: -80 ~ -90)

One of the main questions is: shouldn't batman-adv TQ reflect or be
influenced by dBm values ? How come with -90 dBm i get batman-adv to
show me 230 TQ ?

Also any feedback based on your experience regarding this type of
scenario is welcome. This situation happened overnight without any
access point new configurations or physical setup changes.






-- 


Site: http://wirelesspt.net
Mesh: http://tinyurl.com/wirelesspt
Admin: http://wirelesspt.net/wiki/Cmsv
Twitter: http://twitter.com/wirelesspt
Youtube: https://youtube.com/wirelesspt
Facebook: https://www.facebook.com/wirelesspt
Suporte técnico via sms: 91 19 11 798
Donativos/Paypal: http://tinyurl.com/doar-verba
Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk
Email ao abrigo de: https://creativecommons.org/licenses/by-nc-sa/3.0/pt/


[-- Attachment #2: 0x15C4B382.asc --]
[-- Type: application/pgp-keys, Size: 36238 bytes --]

             reply	other threads:[~2014-04-24  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  8:34 cmsv [this message]
2014-04-24  9:48 ` [B.A.T.M.A.N.] Batman-adv high TQ and Low throughput Simon Wunderlich
2014-04-24 11:57   ` Thijs van Veen
2014-04-24 12:58     ` [B.A.T.M.A.N.] [Battlemesh] " Bastian Bittorf
2014-04-24 13:38       ` Thijs van Veen
2014-04-30 14:24   ` [B.A.T.M.A.N.] " cmsv
     [not found] ` <5358D919.3010700@altermundi.net>
     [not found]   ` <53618E04.2010404@wirelesspt.net>
     [not found]     ` <CADSh-SOhXxvhV1_mMPcfQJAPxaRMpsTqCgnP7k4P0firBH4ZiA@mail.gmail.com>
2014-05-02 14:30       ` [B.A.T.M.A.N.] [OpenWrt-Users] [Battlemesh] " cmsv

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=5358CCA4.2050203@wirelesspt.net \
    --to=cmsv@wirelesspt.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=battlemesh@ml.ninux.org \
    --cc=openwrt-users@lists.openwrt.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