Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Managed to break 802.11n (on a 3800)
Date: Thu, 16 Jan 2014 18:20:12 +0100	[thread overview]
Message-ID: <957858c7-f436-47ec-a55f-d46c6441212a@email.android.com> (raw)
In-Reply-To: <CALQXh-PETSVD9cTJLr-yfdwpypZgHnV6+XyTcDD3iNOaO-La+g@mail.gmail.com>

Aaron Wood <woody77@gmail.com> wrote:
>>
>> > The 5GHz radio on my 3800 seems to be in a very odd state.  I'm not
>> quire sure what state it's in, but it seems to be only doing HT20
>1x1.  And
>> in a fairly broken manner at that.
>> >
>> > Running the rrul test (over wifi directly to the router as the
>> netserver), tcp uploads were 25Mbps or so, but download was 5Mbps.
>>
>>         This is with your mac? Try rrul_noclassification, macosx (at
>least
>> 10.8) will not do RRUL fair to a fast host. Why I do not know… it
>always
>> prioritizes the upload, as if it did not see/trust the downstream
>markings
>> (heck maybe it is busy using all bandwidth for upstream so that it
>> literally never sees the markings on the downstream packets..)
>>
>> About the other issue I do not know anything...
>
>
>
>Sebastian, after sorting out the router, it's still biased, but far
>less
>so, about a 2:1 ratio between upload and download.

So I See offen 10:1 and worse @165Mbit/s raw wireless rate.


>
>Also, my understanding was that with rts/cts, the router was in control
>of
>that aspect of things?  

      That is what I thought AS well, but it is not what I See with osx 10.8.

So the AP should be able to balance those?  (or
>perhaps the swamped load on the router is interfering, I'd need another
>full-size machine on the wired side of the AP to know for sure.

      So if I RRUL from wireless over cerowrt to a wired host in my network I still get the imbalance from macosx, so I assume it is a macos thing...


Best 
Sebastian


>
>-Aaron

Hi Aaron
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2014-01-16 17:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 15:03 Aaron Wood
2014-01-16 15:29 ` Sebastian Moeller
2014-01-16 15:46   ` Aaron Wood
2014-01-16 17:20     ` Sebastian Moeller [this message]
2014-01-16 19:08       ` Aaron Wood
2014-01-16 20:10         ` Sebastian Moeller
2014-01-16 21:33           ` Aaron Wood
2014-01-16 22:50           ` Dave Taht
2014-01-16 23:15             ` Sebastian Moeller
2014-01-16 23:40               ` Dave Taht
2014-01-17 20:15                 ` Toke Høiland-Jørgensen
2014-01-17 20:17                   ` Dave Taht
2014-01-19 19:01                     ` Toke Høiland-Jørgensen
2014-01-19 20:01                       ` Sebastian Moeller
2014-01-19 20:58                         ` Toke Høiland-Jørgensen
2014-01-19 21:12                           ` Sebastian Moeller
2014-01-16 22:35         ` Dave Taht
2014-01-16 22:30   ` Dave Taht
2014-01-16 22:56     ` Sebastian Moeller
2014-01-16 23:12       ` Dave Taht
2014-01-16 23:25         ` Sebastian Moeller
2014-01-16 15:38 ` Robert Bradley
2014-01-16 15:46   ` Aaron Wood
2014-01-16 22:08 ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=957858c7-f436-47ec-a55f-d46c6441212a@email.android.com \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@gmail.com \
    /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