From: David Lang <david@lang.hm>
To: Outback Dingo <outbackdingo@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
Jonathan Morton <chromatix99@gmail.com>,
Paul Vixie <paul@redbarn.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bufferbloat-fcc-discuss
<bufferbloat-fcc-discuss@lists.redbarn.org>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] On building your own routers and the mass market
Date: Sun, 13 Mar 2016 05:04:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1603130458360.1510@nftneq.ynat.uz> (raw)
In-Reply-To: <CAKYr3zydM+DXVRmL4y9vWu=RTZNFDLjRdNf8nR1Rn9Tg8wT2=A@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 706 bytes --]
On Sat, 12 Mar 2016, Outback Dingo wrote:
>> ... and I'm going to order a couple, 'cause their wifi is not as good
>> as it could be (nobody's is), and he said I could visit periodically
>> with make-wifi-fast's upcoming fixes. https://eero.com/
>>
>>> the cznic team has already done this.
>>>
>>> https://omnia.turris.cz/en/
>
>
>
> Looks like a nice device, though can you buy one now, or is this another
> smoke and mirrors, they did get a ton of funding. now lets see if they
> deliver. Can you source the devices now?
No, they are not shipping yet, but they are expecting to start delivering them
next month (April 2016)
They have several thousand to deliver based on existing orders.
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
prev parent reply other threads:[~2016-03-13 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 20:09 [Make-wifi-fast] " Dave Taht
2016-03-11 20:47 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Jay Maynard
2016-03-12 16:21 ` [Make-wifi-fast] [Cerowrt-devel] " Outback Dingo
2016-03-13 12:04 ` David Lang [this message]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1603130458360.1510@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bufferbloat-fcc-discuss@lists.redbarn.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=outbackdingo@gmail.com \
--cc=paul@redbarn.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