From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Where does the Bandwidth Management taking place
Date: Wed, 08 Jan 2003 14:01:23 +0000 [thread overview]
Message-ID: <marc-lartc-104203469118183@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104202046703231@msgid-missing>
Srikanth,
: I want to know exactly how the packet flow is occuring in BW management?
Eh? Seems a bit of a general question....can this not be answered by some
study of the queueing discipline you are using?
If you don't know where to start reading about the queueing discipline you
are using, start at http://lartc.org/ and http://www.docum.org/ and, of
course, a google search.
: Where does the Bandwidth Management taking place after/before routing?
Study the kernel packet travelling diagram, and you'll have a better idea
of the answer to your question.
http://www.docum.org/stef.coene/qos/kptd/
The short answer is:
- egress traffic control occurs after all of the IP filtering, mangling
and rewriting
- ingress traffic control occurs after iptables PREROUTING hooks (if
you are using iptables) or ipchains input (if you are using ipchains)
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-08 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 10:07 [LARTC] Where does the Bandwidth Management taking place after/before Srikanth W
2003-01-08 10:19 ` Tobias Geiger
2003-01-08 14:01 ` Martin A. Brown [this message]
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-104203469118183@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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