From: cm@tahina.priv.at (christian mock)
To: lartc@vger.kernel.org
Subject: [LARTC] Q about "overlimit", and IMQ/NAT trick
Date: Wed, 11 Dec 2002 09:39:12 +0000 [thread overview]
Message-ID: <marc-lartc-103959966030087@msgid-missing> (raw)
hi,
I've successfully implemented shaping and policing with HTB for my
SDSL line.
Some tips&tricks I discovered which were not covered in the FAQs and
docs I read:
- To discover the appropriate rate for your line, flood it with
traffic and reduce the rate until the matching class starts to show
a consistent backlog -- only then you've managed to take the queue
away from your modems/routers and into the shaping box.
- The docs only speak about the IMQ device in connection with the
PREROUTING chain -- the problem is that at that point, incoming
packets are not de-masqueraded yet, so you can't fwmark and shape
depending on the internal address; I use
<iptables packet marking>
iptables -i $EXT_IF -A FORWARD -t mangle -j IMQ
without problems.
Questions:
I'm not quite sure if I shoot myself in the foot with that IMQ setup
-- packets get stuffed into the IMQ device from the mangle table, but
where and how do they "reappear" after shaping?
The other question that remains is: with "tc qdisc show", I see
overlimit!=0 only for the root qdisc -- I would have expected it to
increase on the queues or classes where actual rate > configured
rate... why is that?
ciao,
cm.
--
Actually, I found New Zealanders to be the most akin to Canadians.
They also feel the looming presense of a next door neighbour country
full of loud, excessively happy and somewhat simple people, and are a
little intimidated by it. -- Paul Tomblin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-12-11 9:39 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-103959966030087@msgid-missing \
--to=cm@tahina.priv.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.