From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Two d-link products tested for bloat...
Date: Thu, 19 Feb 2015 18:04:00 -0800 [thread overview]
Message-ID: <CAA93jw4kZGLOFMAkTRD_9y5346MXg4x_4U3CsC7eu7hiU_ijag@mail.gmail.com> (raw)
I ordered a d-link DGL-5500 from amazon this week. It arrived today.
This is their almost top of the line 802.11ac router.
Their streamboost QoS feature - the first thing you see on their
configuration page - LOVELY gui, actually! - was entirely broken in
the uplink direction.
Admittedly that was the first generation firmware. I know how hard it
is to get that right. So I tried to update it. My attempt to update
the firmware for it from their website, bricked it. And it appears the
only way to update it, or to update it to openwrt, is via a gui, not
tftp.
ok.... so...
In an orgy of giving companies that don´t deserve my money, money,
I also got the DIR-860L. It was the "A1" model, which of course, has
no support in openwrt, and there is no way to figure out if an online
retailer is selling the entirely different B model or not.
Their version of the QoS system was entirely broken in *both
directions*. While I was mildly happy that it used weighted fair
queuing by default, bandwidth limitation failed to work *at all*,
except, that it did classify CS1 traffic, as *higher* priority than
best effort.
So in both cases, no matter what you did, even if you tried to do the
right thing... you had bufferbloat induced on the next hop (if, I was
trying to actually test this on a cablemodem or dsl link)
I would really to flush this crap from the marketplace, and the only
way left, I think, is to stop being a nice guy.
My problem is, that I really am a nice guy, and the only way I could
possibly do that is put on a persona, do a blog, call it something
like the angry engineer, or something like that.
But I am pretty sure that venom I would have to summon on a daily
basis would be bad for my blood pressure. Maybe we could all get
together on it, and only raise our collective BP by a point or three
each? The Avenging Engineers?
the relevant netperf-wrapper data is in each of these dirs:
http://snapon.lab.bufferbloat.net/~d/DIR-860L/dir-860L-bandwidth-broke-in-both-directions.png
http://snapon.lab.bufferbloat.net/~d/dgl-5500/totalfailure-to-control-the-upload.png
On Wed, Feb 18, 2015 at 1:28 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Felix, hi List,
>
>
> On Jan 25, 2015, at 12:09 , Felix Fietkau <nbd@openwrt.org> wrote:
>
>> Here's another candidate:
>> http://us.dlink.com/products/connect/wireless-ac1200-dual-band-gigabit-cloud-router-dir-860l/
>>
>> CPU: MT7621 (dual-core MIPS, 880 MHz, 4 virtual CPUs)
>> The device has preliminary OpenWrt support already. In my tests, handles
>> ~820 Mbit/s NAT without any special acceleration features (with fq_codel,
>> no shaping). Haven't done any tests with shaping yet.
>> Wifi (MT7612E) is still buggy with my mt76 driver, but I'll fix that in
>> March when I get back from vacation.
>>
>> - Felix
>
> I am currently searching for a replacement for my wndr3700v2 as it is running out of steam on my temporary 100/40 Mbps link. This thing looks quite decent, but I notice between https://wikidevi.com/wiki/D-Link_DIR-860L_rev_A1 and https://wikidevi.com/wiki/D-Link_DIR-860L_rev_B1 that d-link reused the sam name for quite different hardware implementations, and only the more recent B1 revision will work for us. (Is it just me or do you also find this tendency to not even add the revision to the official name a bit annoying?)
> So, does anybody here now how to order a specific revision in Germany? Or is the only way to wait a bit and hope the A1 revision clears the retail channel so only B1’s are left? I notice that from looking at the internal photos for both devices posted on the FCC site that the old A1 Broadcom revision has its USB port "above" the ethernet ports while the B1 Mediatek revision has the USB port between DC in and below the ethernet ports. Am I correct in assuming that deployed hardware needs to match the FCC design exactly (that is, in case of revision a new FCC submission with new photos is required)?
>
> Best Regards
> Sebastian
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next reply other threads:[~2015-02-20 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 2:04 Dave Taht [this message]
2015-02-20 5:32 ` Aaron Wood
2015-02-20 8:47 ` Jonathan Morton
2015-02-20 9:03 ` Dave Taht
2015-02-20 17:20 ` [Bloat] [Cerowrt-devel] " dpreed
2015-02-26 0:00 ` [Bloat] " Isaac Konikoff
2015-02-26 0:18 ` Jonathan Morton
2015-02-26 0:23 ` Dave Taht
2015-02-26 4:22 ` Isaac Konikoff
2015-02-26 4:37 ` Dave Taht
2015-02-27 5:00 ` Isaac Konikoff
2015-02-27 5:12 ` Dave Taht
2015-02-27 19:15 ` Isaac Konikoff
2015-02-26 16:56 ` Stephen John Smoogen
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4kZGLOFMAkTRD_9y5346MXg4x_4U3CsC7eu7hiU_ijag@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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