Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Occasionally I feel ornery
Date: Sat, 30 Oct 2021 18:01:50 -0700	[thread overview]
Message-ID: <CAA93jw6qFRg3BQsXR4L+1C6sCz+b+Gn4xfyen_3qqHaaAuEE1A@mail.gmail.com> (raw)

And my scars have mostly faded from the heyday of cerowrt. That said,
I really don't know what the world needs anymore on this front, most
of my take on things is ISPs need to deploy what we've had running for
8 years, adopting prplwrt, or something. That said, I'd like some
feedback over here:

https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554

If anyone has any ideas.

-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2021-10-31  1:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw6qFRg3BQsXR4L+1C6sCz+b+Gn4xfyen_3qqHaaAuEE1A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --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