From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] another contender for WNDR replacement
Date: Wed, 18 Feb 2015 01:30:10 -0800 [thread overview]
Message-ID: <CAA93jw6CGc7NTXR+DXokEXyXfg=XL3U3FLfeGS_YP4g1CUQR6w@mail.gmail.com> (raw)
In-Reply-To: <B19F9B19-AA39-476E-BF46-93283AED525B@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
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/
>
>
I just ordered one of these to play with. I am otherwise quite depressed
about how the home gateway industry arbitrarily switches out products and
software with the same brand for something else, usually inferior.
Today´s news:
http://forums.dlink.com/index.php?topic=61634.msg250538#msg250538
> > 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
[-- Attachment #2: Type: text/html, Size: 3586 bytes --]
next prev parent reply other threads:[~2015-02-18 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:46 Sebastian Moeller
2015-01-19 16:37 ` Dave Taht
2015-01-19 23:44 ` Sebastian Moeller
2015-01-25 11:09 ` Felix Fietkau
2015-01-25 19:16 ` Dave Taht
2015-01-25 19:28 ` Felix Fietkau
2015-02-18 9:28 ` Sebastian Moeller
2015-02-18 9:30 ` Dave Taht [this message]
2015-02-18 9:38 ` 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='CAA93jw6CGc7NTXR+DXokEXyXfg=XL3U3FLfeGS_YP4g1CUQR6w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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