From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] meraki gets bought for 1.2b today
Date: Mon, 19 Nov 2012 22:48:24 +0100 [thread overview]
Message-ID: <CAA93jw7-SXVkGu7RKVwa-mm6hX2rosi_cUobF4EDTLVcvF4VvQ@mail.gmail.com> (raw)
http://www.meraki.com/
years ago I thought the srcRR routing protocol was quite innovative
(batman seems very similar) at layer 2...
http://pdos.csail.mit.edu/rtm/srcrr-draft.pdf
Then they went commercial and kind of dark.
And they got bought today by cisco for 1.2B.
http://www.zdnet.com/cisco-acquires-meraki-for-1-2-billion-to-move-in-on-mid-market-cloud-customers-7000007612/
Sometimes, in trying to fix home routers, I think we aimed too low.
There is not a lot available on their current mesh routing
implementation, this is old: http://pdos.csail.mit.edu/roofnet/design/
And it does appear their stuff is almost entirely openwrt based.
http://dl.meraki.net/linux/
Their most recent kernel in their tarball, is 2.6.32.59 - which is
pretty current of the backports of the oldest stable kernel, which
makes me reasonably happy vs a vs CVEs. But I assume their ipv6
support is lousy, and they have bufferbloat issues.Anybody got any of
this gear?
Their dnsmasq is relatively current (2.63), as seems to be many of
their utilities that I checked. While their binary firmware is locked
down, they seem to do frequent updates, which also makes me happy.
(and staying current probably contributed to their market rise, IMHO)
They sure have a nice set of guis.
And meanwhile, the core bufferbloat, openwrt and cerowrt development
teams labor on, on no funding, fixing the next generation of
problems...
Some days, it's not worth getting up in the morning.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2012-11-19 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 21:48 Dave Taht [this message]
2012-11-20 2:08 ` [Bloat] [Cerowrt-devel] " dpreed
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7-SXVkGu7RKVwa-mm6hX2rosi_cUobF4EDTLVcvF4VvQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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