From: Dan Denson <dandenson@gmail.com>
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.] any throughput mechanism or plans?
Date: Sat, 31 Mar 2012 20:53:41 -0600 [thread overview]
Message-ID: <-6553061881251442485@unknownmsgid> (raw)
In-Reply-To: <CAHD-aqJEvYHpiMBZE5Sp8QzcHJfLVuwzK9Wh4Bf0rN6BA6t0OQ@mail.gmail.com>
>
> That sounds like a nice start!
> I'm not sure, though, if that number includes retransmissions and/or
> unacknowledged frames.
> IIRC i think i've seen that TX number grow in an interface with such a
> lossy link that was just sending traffic (trying to reach the distant
> ap) but getting nothing in return (ap couldn't hear me)
>
> So far, with openwrt and ath9k / ath9k_htc, i've found the "tx
> bitrate" (or MCS level) a fair indicator of the link capacity.
> if it says "65.0 MBit/s MCS 7" i cannot tell exactly how much goodput
> it will have, but i can be pretty confident that it will be better
> than when it says "6.5 MBit/s MCS 1"
Good point on ifconfigs potential limitations.
One issue with using the wireless sync rate is that fresnel zone
infractions will allow you to sync at one rate but for the link to
fall apart as the throughput grows. I have seen a 130Mb link degrade
to 54Mb as soon as it started passing significant traffic.
next prev parent reply other threads:[~2012-04-01 2:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 22:22 [B.A.T.M.A.N.] any throughput mechanism or plans? dan
2012-03-31 20:43 ` Antonio Quartulli
2012-04-01 2:02 ` dan
2012-04-01 2:39 ` Guido Iribarren
2012-04-01 2:53 ` Guido Iribarren
2012-04-01 2:53 ` Dan Denson [this message]
2012-04-01 21:35 ` Marek Lindner
2012-04-01 21:32 ` Marek Lindner
2012-04-01 22:23 ` dan
2012-04-02 9:32 ` Marek Lindner
2012-04-02 13:35 ` dan
2012-04-02 15:29 ` Marek Lindner
2012-04-02 18:21 ` dan
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=-6553061881251442485@unknownmsgid \
--to=dandenson@gmail.com \
--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