From: Dave Taht <dave.taht@gmail.com>
To: Jordan Szuch <jordan@inacomptc.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] some mikrotik comments
Date: Sun, 10 Oct 2021 09:11:25 -0700 [thread overview]
Message-ID: <CAA93jw5cefvMNe-6+gAWLVVsTYXE6JDpPXvYGrthNa-kjX-ixg@mail.gmail.com> (raw)
In-Reply-To: <003001d7bdf0$97282430$c5786c90$@inacomptc.com>
It's flent.org rrul test output that I love.
On Sun, Oct 10, 2021 at 9:05 AM Jordan Szuch via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> Hi Dave,
>
> Interesting that you should send this out; I recently picked up a unit (this one specifically: https://mikrotik.com/product/hap_ac2) to do some testing of the v7 firmware. Nothing super high end but enough to do a little testing. I have CAKE set to do some shaping and so far seems functional. At least the bufferbloat speed tests from DSLReports and WaveForm indicate some shaping is happening. If you'd like any information about the unit, the v7 firmware, or particular tests run then I'd be happy to help out.
>
> Jordan
>
> -----Original Message-----
> From: Bloat <bloat-bounces@lists.bufferbloat.net> On Behalf Of Dave Taht
> Sent: Sunday, October 10, 2021 11:39 AM
> To: Cake List <cake@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
> Subject: [Bloat] some mikrotik comments
>
> the v7 beta gained doc and more os support for fq_codel and cake recently
>
> https://forum.mikrotik.com/viewtopic.php?p=885000#p885000
>
> anyone out there actively testing mikrotik?
>
> --
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-10-10 16:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 15:39 [Cake] " Dave Taht
2021-10-10 16:05 ` [Cake] [Bloat] " Jordan Szuch
2021-10-10 16:11 ` Dave Taht [this message]
2021-10-10 16:18 ` Jordan Szuch
2021-10-10 17:51 ` Dave Taht
2021-10-10 20:39 ` Jordan Szuch
2021-10-10 21:37 ` Dave Taht
2021-10-10 23:01 ` Jordan Szuch
2021-10-11 0:40 ` Dave Taht
2021-10-11 1:05 ` Dave Taht
2021-10-11 1:18 ` Jordan Szuch
2021-10-11 1:23 ` Dave Taht
2021-10-11 1:31 ` Dave Taht
2021-10-11 1:37 ` Dave Taht
2021-10-11 1:41 ` Jordan Szuch
2021-10-11 1:54 ` Jordan Szuch
2021-10-11 2:05 ` Dave Taht
2021-10-11 2:30 ` Dave Taht
2021-10-11 2:41 ` Jordan Szuch
2021-10-11 2:59 ` Dave Taht
2021-10-11 3:24 ` Jordan Szuch
2021-10-14 17:08 ` Dave Taht
2021-10-14 18:27 ` Jordan Szuch
2021-10-14 22:18 ` Thomas Croghan
2021-10-14 22:33 ` Dave Taht
2021-10-15 15:17 ` Thomas Croghan
2021-10-27 21:56 ` Dave Taht
2021-10-11 0:53 ` [Cake] " Thomas Croghan
2021-10-11 1:16 ` Dave Taht
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5cefvMNe-6+gAWLVVsTYXE6JDpPXvYGrthNa-kjX-ixg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=jordan@inacomptc.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