From: Will Hawkins <hawkinsw@obs.cr>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] "Market" information about CPE from residential ISPs
Date: Tue, 14 Jun 2022 19:40:12 -0400 [thread overview]
Message-ID: <CADx9qWia44pRX06u+PMDk6a2nBjD4KH5Seh8VK0rJywW6=iOpg@mail.gmail.com> (raw)
In-Reply-To: <B8E23BC7-7208-45A2-817D-B214EA6BC87A@gmail.com>
Really appreciate that! Thank you!
Will
On Tue, Jun 14, 2022 at 5:53 PM Rich Brown <richb.hanover@gmail.com> wrote:
>
>
> On Jun 14, 2022, at 5:35 PM, Will Hawkins via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> Does anyone know where we could get information on the most common
> hardware configurations for CPEs?
>
>
> OpenWrt has an automated build machine that creates a binary on-the-fly, pulling in a list of requested packages. The package selection isn't necessarily interesting for your study, but the variation of manufacturer/models could be.
>
> You can see the stats at: https://sysupgrade.openwrt.org/stats
>
> There are all kinds of things "wrong" with this data:
>
> - It's not used (yet) by the general OpenWrt community
> - This server use is skewed toward developers
> - Those people may have more powerful machines
> - What the heck is going on with the Linksys_e8450?
>
> But maybe it's a useful quick-look at various semi-popular models. You can look up device specs in the OpenWrt Table of Hardware: https://openwrt.org/toh/start
>
> Have fun!
>
> Rich
prev parent reply other threads:[~2022-06-14 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 21:35 Will Hawkins
2022-06-14 21:53 ` Rich Brown
2022-06-14 23:40 ` Will Hawkins [this message]
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADx9qWia44pRX06u+PMDk6a2nBjD4KH5Seh8VK0rJywW6=iOpg@mail.gmail.com' \
--to=hawkinsw@obs.cr \
--cc=richb.hanover@gmail.com \
--cc=rpm@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