From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] Finally, CBQ nearly completely documented
Date: Sat, 01 Dec 2001 00:33:41 +0000 [thread overview]
Message-ID: <marc-lartc-100716668806245@msgid-missing> (raw)
Hi,
After preparing my talk on CBQ/HTB (http://ds9a.nl/cbq-presentation ), I
finally understood how CBQ and filters etc truly work. And I wrote it down.
Check out the Linux Advanced Routing & Shaping HOWTO, it's changed a lot!
Especially this part is very new, please check it for mistakes and
inconsistencies:
http://ds9a.nl/2.4Routing/HOWTO//cvs/2.4routing/output/2.4routing-9.html
I even got 'split' and 'defmap' figured out, which should be a first. There
is not a single other page online that tells you correctly what these do.
One thing - does *anybody* understand how hash tables work in tc filter, and
what they do? Furthermore, I could use some help with the tc filter police
things.
So if you do understand how these work, please drop me a line.
Thanks!
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-12-01 0:33 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-100716668806245@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.org \
/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