From: David Lang <david@lang.hm>
To: Steven Barth <cyrus@openwrt.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] anyone have real info on the google router?
Date: Wed, 19 Aug 2015 10:55:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1508191054030.10162@nftneq.ynat.uz> (raw)
In-Reply-To: <55D450B7.6090404@openwrt.org>
On Wed, 19 Aug 2015, Steven Barth wrote:
> Wow, I must imagine it to be especially painful to reinvent the wheel
> for all things QoS, WiFi optimizations, IPv6, Firewalling etc. and
> rebuilding that on top of ChromeOS.
It's all Linux under the covers, so there's probably far less reinventing than
you think.
I'll bet a lot of that stuff is either used as-is (with a different config
system), or they just don't implement it (I doubt it has QoS for example)
David Lang
next prev parent reply other threads:[~2015-08-19 17:55 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
2015-08-19 6:02 ` Mikael Abrahamsson
2015-08-19 9:47 ` Steven Barth
2015-08-19 17:55 ` David Lang [this message]
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.1508191054030.10162@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.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