From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?
Date: Wed, 25 Jul 2018 16:17:45 -0400 [thread overview]
Message-ID: <CAGhGL2CO6ZBapnj05YuoSnv14w0ztMEd2sh0Xz=Ta9iRGyVVXQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6TetZ9JSfw0ZFDMm5nxixV4Y6pycCqMKYa2uNseegSzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
I've surveyed firmware twice; once at the beginning of the bufferbloat
effort and most recently again a couple or three years ago. The first time
was with 3-4 routers, and the second time 5-6 routers.
The typical *minimum* age of any software package inside for the vendors I
happened to choose were around 4 years old, on "latest and greatest"
routers. I did not see significant change between the two surveys. Also
"amusing" (not) were finding things like versions of telnet included that
had not had a maintainer for over a decade, and similar disasters.
5-7 is still my guess for most routers sold, on this limited data sets.
- Jim
On Wed, Jul 25, 2018 at 2:50 PM Dave Taht <dave.taht@gmail.com> wrote:
> back in 2011, 2012 jim and I and others looked hard at the kernels and
> software being sold then to end-users.
>
> We concluded that the embedded router world was running 5-7 years
> behind linux mainline, sometimes as much as 10, and that the embedded
> linux world had been decimated by the great recession causing the
> collapse of companies like montavista.
>
> I recently took apart verizon FIOS's current firmware for one of their
> more popular routers. It's still running 2.6.21, which shipped in
> june, 2007. Overgeneralizing from this one data point, I am wondering
> if the trendline for new routing products tracking current software
> has got worse or better? I have generally assumed that "new wifi
> features" was a fundamental driver for semi-newer kernel versions in
> new products, and not much else. Edgerouters are still 3.10. I know of
> more than a few pre-bufferbloat-era things going back even further
> than that, but most hackerboards I've played with also don't go back
> very far. Odroid C2 was still 3.10 last I looked.
>
> There are still a few companies alive in this space (openrg being one
> that I know nothing about), but...
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3369 bytes --]
next prev parent reply other threads:[~2018-07-25 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 18:50 Dave Taht
2018-07-25 19:14 ` valdis.kletnieks
2018-07-25 19:49 ` dpreed
2018-07-25 20:00 ` Dave Taht
2018-07-25 20:17 ` Jim Gettys [this message]
2018-07-26 8:53 ` Mikael Abrahamsson
2018-07-26 14:13 ` Jonathan Morton
2018-07-26 16:48 ` dpreed
2018-07-26 20:15 ` Dave Taht
2018-07-26 20:34 ` Joel Wirāmu Pauling
2018-07-27 9:31 ` Mikael Abrahamsson
2018-07-26 13:13 [Cerowrt-devel] So how far behind is the embedded router world,still? dpreed
2018-07-26 13:56 ` [Cerowrt-devel] So how far behind is the embedded router world, still? Mikael Abrahamsson
2018-07-26 16:45 ` valdis.kletnieks
2018-07-27 12:18 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/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='CAGhGL2CO6ZBapnj05YuoSnv14w0ztMEd2sh0Xz=Ta9iRGyVVXQ@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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