From: Dave Taht <dave@taht.net>
To: Ali <dukecrow@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] eero using fq_codel and Cake
Date: Mon, 22 Oct 2018 09:33:46 -0700 [thread overview]
Message-ID: <87d0s2ym8l.fsf@taht.net> (raw)
In-Reply-To: <CALr-W4Y5VpvC4tRS-zapNKWNuWvKrVTaD_pK3Vi2NKNnNVH9=w@mail.gmail.com> (Ali's message of "Fri, 19 Oct 2018 13:25:07 -0400")
Ali <dukecrow@gmail.com> writes:
> I've been reading this list for a while but never subscribed bc I
> don't really have anything to contribute.
>
> Well, I saw this on the eero subreddit and thought it was worth
> posting about.
>
> https://www.reddit.com/r/eero/comments/9nvuk8/comment/e7qgg4c?st=JNGA5S6H&sh=04ae8c47
> "It's fq-codel inside the mesh, and then CAKE on the uplink, if your
> gateway is a second generation eero. If your gateway is a first
> generation eero, then it's codel on the uplink too."
>
> The user 6roybatty6 is an engineer at eero who is active in the
> subreddit (the CEO and founder is active, too). Great to see one of
> the wireless mesh products out there using fq_codel in their WiFi
> implementation and Cake at the router/gateway.
thank you for the heads up. I joined that thread. It's great to see our
stuff more "out there" and being refined into something mere mortals
can use, and hopefully, more often enabled by default.
User feedback is valuable. For example the poster asked if "sqm got
smarter over time" - and, yea, some deployments are doing that.
https://www.reddit.com/r/eero/comments/9nvuk8/does_sqm_get_smarter/
>
> Regards,
> Ali
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2018-10-22 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 17:25 Ali
2018-10-22 16:33 ` Dave Taht [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/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=87d0s2ym8l.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dukecrow@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