Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Jordan Szuch" <jordan@inacomptc.com>
To: "'Dave Taht'" <dave.taht@gmail.com>
Cc: "'Cake List'" <cake@lists.bufferbloat.net>,
	"'bloat'" <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] some mikrotik comments
Date: Thu, 14 Oct 2021 14:27:42 -0400	[thread overview]
Message-ID: <006001d7c129$2de82f10$89b88d30$@inacomptc.com> (raw)
In-Reply-To: <CAA93jw5dJ_=5OzPrcQYmFQtKLXJcfb7TWUW-jKMqfxZCpD3cZQ@mail.gmail.com>

Awesome, thanks! I went and subscribed to that topic so I'll get notifications when people reply. Hope to jump in once I'm less busy with my day to day work.

Regarding more powerful hardware, I think someone replied to the mailing list earlier offering to run some tests. Sounded like he might have some bigger hardware to test out. Thomas Croghan back on Monday morning it looks like.

Might also be worth reaching out to these guys to do some testing or evangelizing at least: https://thebrotherswisp.com/ They run a podcast with a rotating cast of network operators, WISPS, etc. And they seem pretty clued into the MIkrotik world specifically. I recall that you've jumped onto a podcast or two recently so that's why I bring it up.

Anyway, I listen from time to time and one of the hosts brought up being very interested in using fq_codel and CAKE in a Multi Dwelling Unit scenario (mentioned here after a 3-4 minutes https://www.youtube.com/watch?v=yFKG_cXGPrE&t=4444s). Actually, I think they even name check you in an earlier episode (found it: https://www.youtube.com/watch?v=Q1QitymNZTo&t=4285s), although one host was a bit skeptical of everything.

-----Original Message-----
From: Dave Taht <dave.taht@gmail.com> 
Sent: Thursday, October 14, 2021 1:09 PM
To: Jordan Szuch <jordan@inacomptc.com>
Cc: Cake List <cake@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] some mikrotik comments

Thx. I put the discussion and plots over here:

https://forum.mikrotik.com/viewtopic.php?t=179307

I might - should I feel like expounding more later this week - go back to the flent.gz files to discuss other features. Ironically the chromebook I have in front of me doesn't want to let me download a file via email and make it visible in the real filesystem. I'm vm'd off from myself for some reason.

But my big goal, honestly, was to get some mikrotik users to test their bigger iron...

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


  reply	other threads:[~2021-10-14 18:27 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
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 [this message]
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='006001d7c129$2de82f10$89b88d30$@inacomptc.com' \
    --to=jordan@inacomptc.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@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