From: Jim Gettys <jg@freedesktop.org>
To: David Lang <david@lang.hm>
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:57:22 -0400 [thread overview]
Message-ID: <CAGhGL2CxbsgyK2O8zDS-mjuwXZSCS66hQ3wgX+DFmh=KLZwm5g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1508181229160.27696@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
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.
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
>
[-- Attachment #2: Type: text/html, Size: 2744 bytes --]
next prev parent reply other threads:[~2015-08-19 1:57 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 [this message]
2015-08-19 4:16 ` David Lang
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='CAGhGL2CxbsgyK2O8zDS-mjuwXZSCS66hQ3wgX+DFmh=KLZwm5g@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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