Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu
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 15:14:29 -0400	[thread overview]
Message-ID: <63972.1532546069@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAA93jw6TetZ9JSfw0ZFDMm5nxixV4Y6pycCqMKYa2uNseegSzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

On Wed, 25 Jul 2018 11:50:31 -0700, Dave Taht said:

> 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 to admit I bought a Linksys WRT1200AC and it didn't stay on
factory firmware long enough for me to check, it got Lede installed
right over the top before it got swapped in for the old router....

Friends don't let friends run factory firmware... :)

[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]

  reply	other threads:[~2018-07-25 19:14 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 [this message]
2018-07-25 19:49   ` dpreed
2018-07-25 20:00     ` Dave Taht
2018-07-25 20:17 ` Jim Gettys
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=63972.1532546069@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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