From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: Richard Brown <richard.e.brown@dartware.com>,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] WNDR3700v4 is out...
Date: Sun, 23 Dec 2012 11:38:37 -0500 [thread overview]
Message-ID: <CAA93jw4xc06EAo2aFmiquvB4VwsU8jxxc8MaKnZ9GazsvQ09jQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212230814070.15987@nftneq.ynat.uz>
On Sun, Dec 23, 2012 at 11:14 AM, David Lang <david@lang.hm> wrote:
> In looking at their products, they seem to have almost nothing that's dual
> band, am I missing something?
Nope. I went single channel for the yurtlab backbone in part because I
wanted "hardware flow control" (the 100Mbit ethernet connected to a
300Mbit radio) to work and to be able to look at what the
"microqueues" in the ethernet driver formed by packet de-aggregation
did under fq_codel.
Doing it all in one box with (nonexistent) software flow control
between 2.4ghz, 5ghz, and gigE ethernet in a single unit - seemed
likely to do nothing more than pass bursts of packets around. I like
the software-fq-on-de-aggregation idea I talked about a week or so
back, but haven't done anything about it.
I'd thought hard about using the http://www.ubnt.com/rspro rather than
the netgears at one point, but thought the BOM would put people off,
and at the price tag for a full box, there seemed to be several x86
alternatives, and either way, we ended up with no micro queues to
break up.
A typical configuration at the yurtlab is two nano station M5s and a
single omni 2HP.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-12-23 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4.1356033603.24143.cerowrt-devel@lists.bufferbloat.net>
2012-12-20 21:21 ` Richard Brown
2012-12-23 7:27 ` David Lang
2012-12-23 13:02 ` Dave Taht
2012-12-23 14:45 ` dpreed
2012-12-23 15:16 ` David Lang
2012-12-23 15:22 ` Outback Dingo
2012-12-23 15:50 ` David Lang
2012-12-23 15:53 ` Dave Taht
2012-12-23 16:14 ` David Lang
2012-12-23 16:38 ` Dave Taht [this message]
2012-12-23 16:57 ` David Lang
2012-12-23 17:08 ` Dave Taht
2013-01-03 19:56 ` David Lang
2013-01-03 20:03 ` 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=CAA93jw4xc06EAo2aFmiquvB4VwsU8jxxc8MaKnZ9GazsvQ09jQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=richard.e.brown@dartware.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