Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Jim Gettys <jg@freedesktop.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] anyone have real info on the google router?
Date: Tue, 18 Aug 2015 21:16:48 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1508182114400.23683@nftneq.ynat.uz> (raw)
In-Reply-To: <CAGhGL2CxbsgyK2O8zDS-mjuwXZSCS66hQ3wgX+DFmh=KLZwm5g@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1603 bytes --]

On Tue, 18 Aug 2015, Jim Gettys wrote:

> On Tue, Aug 18, 2015 at 3:31 PM, David Lang <david@lang.hm> wrote:
>
>>
>> http://googleblog.blogspot.com/2015/08/meet-onhub-new-router-for-new-way-to-wi.html
>>
>> specifically the issues of firmware and drivers?
>
>
> ​
> It runs a very recent kernel (3.18, IIRC).
> ​  The devel prototype originally ran OpenWrt; should be pretty easy to
> make OpenWrt run on it again.  Has a speaker on it (so you can do proof of
> actual presence to help bootstrap security stuff).  Ath10k wireless.  Has a
> TPM module on board, so you could do a poor man's hsm for storing keys.​

IIRC the Ath10k wireless is not very hackable (big binary blob), so that would 
mean that unless Google has been able to do something new here, it's not very 
hackable for make-wifi-fast.

Am I remembering correctly?

otherwise it sounds like a nice device for the price.

David Lang

> ​
>
> ​ Android style unlockable bootloader.​  The intent is it be an open
> platform. Has a hardware packet assist engine: there will be the usual
> issues of latency vs. bandwidth; not much use of that this instant.
>
> Current software admin is done entirely via Android apps and a google back
> end: no web gui for it at the moment (Trond isn't comfortable with a web
> server on the router).  Secure upgrade of the firmware.
>                                                    - Jim
>
>
>>
>> David Lang
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>

  reply	other threads:[~2015-08-19  4:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 19:31 David Lang
2015-08-19  1:57 ` Jim Gettys
2015-08-19  4:16   ` David Lang [this message]
2015-08-19  6:02     ` Mikael Abrahamsson
2015-08-19  9:47   ` Steven Barth
2015-08-19 17:55     ` David Lang
2015-08-19 18:10       ` Mikael Abrahamsson
2015-08-19 18:49       ` Steven Barth

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=alpine.DEB.2.02.1508182114400.23683@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.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