From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] pfsense fq_codel tutorial
Date: Thu, 18 Feb 2021 07:00:49 -0800 [thread overview]
Message-ID: <CAA93jw5KJTa+hKNE4-zNePH7u0PrtHPY00M3kfiyw3oYFWND_g@mail.gmail.com> (raw)
https://isc.sans.edu/diary/Securing+and+Optimizing+Networks%3A+Using+pfSense+Traffic+Shaper+Limiters+to+Combat+Bufferbloat/27102
I do wish they had link compensation in there, and this is the first
time ever I've seen a suggestion to use
64k queues. I honestly have never tried that many....
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
reply other threads:[~2021-02-18 15:01 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/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=CAA93jw5KJTa+hKNE4-zNePH7u0PrtHPY00M3kfiyw3oYFWND_g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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